Skip to content
Snippets Groups Projects
Commit 7ba54897 authored by Jay Freyensee's avatar Jay Freyensee Committed by Christoph Hellwig
Browse files

nvmetcli: README description of discovery


Some blurbs on discovery and the connection
between using nvmetcli to set up an NVMe target and
what gets seen by an NVMe Host when accessing
the discovery controller.

Signed-off-by: default avatarJay Freyensee <james_p_freyensee@linux.intel.com>
parent be4d196b
No related branches found
No related tags found
No related merge requests found
......@@ -111,8 +111,23 @@ The following walks through an example using interactive mode.
...> cd subsystems/
...> create testnqn
Referrals/Discovery
--------------------
Discovery
----------
Each NVMe Target has a discovery controller mechanism that an NVMe
Host can use to determine the NVM subsystems it has access too.
nvmetcli can be used to add a new record to the discovery controller
upon each new subsystem entry and port entry that the newly
created subsystem entry binds too (see the '/port/' and
'/subystem/' nvmetcli walk-through earlier in this README). Each NVMe
Host only gets to see the discovery entries defined in
/subsystems/[NQN NAME]/allowed_hosts and the IP port it is connected
to the NVMe Target.
A Host can retrieve these discovery logs via the nvme-cli tool
(https://github.com/linux-nvme/nvme-cli).
Referrals
---------
TBD
Saving and restoring the configuration
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment