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

doc: fix some typos and align indent when setup.sh --help

Browse Source 
Signed-off-by: Dayu Liu <liu.dayu@zte.com.cn>
Change-Id: Id0a2a3a577adfd5026b662d97d74c9ec6aebeb8e
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2396
Community-CI: Mellanox Build Bot
Reviewed-by: Changpeng Liu <changpeng.liu@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
This commit is contained in:
Dayu Liu 2020-05-11 20:08:41 +08:00 committed by Tomasz Zawadzki
parent e5f021c10e
commit 5cdab5e2e6
4 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/bdev.md
View File

@ -261,7 +261,7 @@ possibly multiple virtual bdevs.
## SPDK GPT partition table {#bdev_ug_gpt} ## SPDK GPT partition table {#bdev_ug_gpt}
The SPDK partition type GUID is `7c5222bd-8f5d-4087-9c00-bf9843c7b58c`. Existing SPDK bdevs The SPDK partition type GUID is `7c5222bd-8f5d-4087-9c00-bf9843c7b58c`. Existing SPDK bdevs
can be exposed as Linux block devices via NBD and then ca be partitioned with can be exposed as Linux block devices via NBD and then can be partitioned with
standard partitioning tools. After partitioning, the bdevs will need to be deleted and standard partitioning tools. After partitioning, the bdevs will need to be deleted and
attached again for the GPT bdev module to see any changes. NBD kernel module must be attached again for the GPT bdev module to see any changes. NBD kernel module must be
loaded first. To create NBD bdev user should use `nbd_start_disk` RPC command. loaded first. To create NBD bdev user should use `nbd_start_disk` RPC command.

2
doc/iscsi.md
View File

@ -218,7 +218,7 @@ echo "1024" > /sys/block/sdc/queue/nr_requests
### Example: Configure simple iSCSI Target with one portal and two LUNs ### Example: Configure simple iSCSI Target with one portal and two LUNs
Assuming we have one iSCSI Target server with portal at 10.0.0.1:3200, two LUNs (Malloc0 and Malloc), Assuming we have one iSCSI Target server with portal at 10.0.0.1:3200, two LUNs (Malloc0 and Malloc1),
and accepting initiators on 10.0.0.2/32, like on diagram below: and accepting initiators on 10.0.0.2/32, like on diagram below:
![Sample iSCSI configuration](iscsi_example.svg) ![Sample iSCSI configuration](iscsi_example.svg)

4
doc/vhost.md
View File

@ -105,7 +105,7 @@ app/vhost/vhost -h
## Create bdev (block device) {#vhost_bdev_create} ## Create bdev (block device) {#vhost_bdev_create}
SPDK bdevs are block devices which will be exposed to the guest OS. SPDK bdevs are block devices which will be exposed to the guest OS.
For vhost-scsi, bdevs are exposed as as SCSI LUNs on SCSI devices attached to the For vhost-scsi, bdevs are exposed as SCSI LUNs on SCSI devices attached to the
vhost-scsi controller in the guest OS. vhost-scsi controller in the guest OS.
For vhost-blk, bdevs are exposed directly as block devices in the guest OS and are For vhost-blk, bdevs are exposed directly as block devices in the guest OS and are
not associated at all with SCSI. not associated at all with SCSI.
@ -373,7 +373,7 @@ be aborted - possibly flooding a VM with syslog warnings and errors.
### Hot-attach ### Hot-attach
Hot-attach is is done by simply attaching a bdev to a vhost controller with a QEMU VM Hot-attach is done by simply attaching a bdev to a vhost controller with a QEMU VM
already started. No other extra action is necessary. already started. No other extra action is necessary.
~~~{.sh} ~~~{.sh}