From dc6d84ccc2099e2fc7c1648bc98400041262d39c Mon Sep 17 00:00:00 2001
From: Tomasz Kulasek <tomaszx.kulasek@intel.com>
Date: Mon, 30 Dec 2019 10:00:21 -0500
Subject: [PATCH] doc/nvme: fix NVMe CUSE device node path

Change-Id: I1601e1985cd24aea283ce3d17ffb8de2fb4a687e
Signed-off-by: Tomasz Kulasek <tomaszx.kulasek@intel.com>
Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/478952
Community-CI: SPDK CI Jenkins <sys_sgci@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
---
 doc/nvme.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/doc/nvme.md b/doc/nvme.md
index e82031526..88828ee30 100644
--- a/doc/nvme.md
+++ b/doc/nvme.md
@@ -277,10 +277,11 @@ This feature is considered as experimental.
 For each controller as well as namespace, character devices are created in the
 locations:
 ~~~{.sh}
-    /dev/'dev_path'
-    /dev/'dev_path'nY
+    /dev/spdk/nvmeX
+    /dev/spdk/nvmeXnY
     ...
 ~~~
+Where X is unique SPDK NVMe controller index and Y is namespace id.
 
 Requests from CUSE are handled by pthreads when controller and namespaces are created.
 Those pass the I/O or admin commands via a ring to a thread that processes them using