From bcebf365253235cf21b89c0f42949486ff39838f Mon Sep 17 00:00:00 2001
From: GangCao <gang.cao@intel.com>
Date: Fri, 25 Jan 2019 15:40:54 -0500
Subject: [PATCH] doc: add a description of limitation for multi-process usage

This patch addes a new description of limitation for multiple
process usage.

Change-Id: Iaa66baf2eea3d444b29658fd4aa357ee23c7c937
Signed-off-by: GangCao <gang.cao@intel.com>
Reviewed-on: https://review.gerrithub.io/c/442026
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
Chandler-Test-Pool: SPDK Automated Test System <sys_sgsw@intel.com>
---
 doc/nvme.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/doc/nvme.md b/doc/nvme.md
index f4033406d1..c07b7be6d9 100644
--- a/doc/nvme.md
+++ b/doc/nvme.md
@@ -241,6 +241,8 @@ Example: identical shm_id and non-overlapping core masks
 2. If a primary process exits while secondary processes are still running, those processes
 will continue to run. However, a new primary process cannot be created.
 3. Applications are responsible for coordinating access to logical blocks.
+4. If a process exits unexpectedly, the allocated memory will be released when the last
+process exits.
 
 @sa spdk_nvme_probe, spdk_nvme_ctrlr_process_admin_completions