doc: fix a couple of doc issues found during vhost w/ NVMe-oF testing

Signed-off-by: Jim Harris <james.r.harris@intel.com>
Change-Id: Id7e0f4b3f14e7cc18cd05df639a13843f2e85763

Reviewed-on: https://review.gerrithub.io/372346
Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com>
Tested-by: SPDK Automated Test System <sys_sgsw@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
This commit is contained in:
Jim Harris 2017-08-01 23:57:04 -07:00
parent 0158f354db
commit 5f05513bf1
2 changed files with 2 additions and 2 deletions

View File

@ -31,7 +31,7 @@ can be either locally attached SSDs or remote NVMe subsystems via NVMe-oF.
# The devices will be assigned names in the format <YourName>nY, where YourName is the
# name specified at the end of the TransportId line and Y is the namespace id, which starts at 1.
TransportID "trtype:PCIe traddr:0000:00:00.0" Nvme0
TransportID "trtype:RDMA subnqn:nqn.2016-06.io.spdk:cnode1 traddr:192.168.100.1 trsvcid:4420" Nvme1
TransportID "trtype:RDMA adrfam:IPv4 subnqn:nqn.2016-06.io.spdk:cnode1 traddr:192.168.100.1 trsvcid:4420" Nvme1
~~~
This exports block devices for all namespaces attached to the two controllers. Block devices

View File

@ -127,7 +127,7 @@
#[VhostScsi1]
# Name vhost.1
# Dev0 AIO1
# Dev 0 AIO1
# Cpumask 0x1
#[VhostBlk0]