ivampiresp/Spdk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc/nvme: fix NVMe CUSE device node path

Browse Source 
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>
This commit is contained in:
Tomasz Kulasek 2019-12-30 10:00:21 -05:00 committed by Tomasz Zawadzki
parent be4a5602ce
commit dc6d84ccc2
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/nvme.md
View File

@ -277,10 +277,11 @@ This feature is considered as experimental.
For each controller as well as namespace, character devices are created in the For each controller as well as namespace, character devices are created in the
locations: locations:
~~~{.sh} ~~~{.sh}
/dev/'dev_path' /dev/spdk/nvmeX
/dev/'dev_path'nY /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. 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 Those pass the I/O or admin commands via a ring to a thread that processes them using