Commit dc6d84cc authored by Tomasz Kulasek's avatar Tomasz Kulasek Committed by Tomasz Zawadzki
Browse files

doc/nvme: fix NVMe CUSE device node path 



Change-Id: I1601e1985cd24aea283ce3d17ffb8de2fb4a687e
Signed-off-by: default avatarTomasz 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: default avatarSPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: default avatarTomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: default avatarJim Harris <james.r.harris@intel.com>
Reviewed-by: default avatarShuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
parent be4a5602

doc/nvme.md

+3 −2
Original line number Diff line number Diff line
@@ -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