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

markdownlint: enable rule MD005

Browse Source 
MD005 - Inconsistent indentation for list items at the same level
Fixed all MD005 errors

Signed-off-by: wawryk <maciejx.wawryk@intel.com>
Change-Id: If6a12d6dab938094394a72c804f2a028f1c40f45
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/8995
Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>
Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
This commit is contained in:
wawryk 2021-07-30 11:55:02 +02:00 committed by Tomasz Zawadzki
parent e5b5eabe82
commit 1df1583be5
7 changed files with 140 additions and 139 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/iscsi.md
View File

@ -274,6 +274,7 @@ sde
At the iSCSI level, we provide the following support for Hotplug: At the iSCSI level, we provide the following support for Hotplug:
1. bdev/nvme: 1. bdev/nvme:
At the bdev/nvme level, we start one hotplug monitor which will call At the bdev/nvme level, we start one hotplug monitor which will call
spdk_nvme_probe() periodically to get the hotplug events. We provide the spdk_nvme_probe() periodically to get the hotplug events. We provide the
private attach_cb and remove_cb for spdk_nvme_probe(). For the attach_cb, private attach_cb and remove_cb for spdk_nvme_probe(). For the attach_cb,
@ -283,6 +284,7 @@ At the iSCSI level, we provide the following support for Hotplug:
handle the hot-remove event. handle the hot-remove event.
2. scsi/lun: 2. scsi/lun:
When the LUN receive the hot-remove notification from block device layer, When the LUN receive the hot-remove notification from block device layer,
the LUN will be marked as removed, and all the IOs after this point will the LUN will be marked as removed, and all the IOs after this point will
return with check condition status. Then the LUN starts one poller which will return with check condition status. Then the LUN starts one poller which will

16
doc/nvme.md
View File

@ -2,14 +2,14 @@
# In this document {#nvme_toc} # In this document {#nvme_toc}
* @ref nvme_intro - @ref nvme_intro
* @ref nvme_examples - @ref nvme_examples
* @ref nvme_interface - @ref nvme_interface
* @ref nvme_design - @ref nvme_design
* @ref nvme_fabrics_host - @ref nvme_fabrics_host
* @ref nvme_multi_process - @ref nvme_multi_process
* @ref nvme_hotplug - @ref nvme_hotplug
* @ref nvme_cuse - @ref nvme_cuse
# Introduction {#nvme_intro} # Introduction {#nvme_intro}

20
doc/vhost_processing.md
View File

@ -90,13 +90,13 @@ physically-discontiguous regions and Vhost-user specification puts a limit on
their number - currently 8. The driver sends a single message for each region with their number - currently 8. The driver sends a single message for each region with
the following data: the following data:
* file descriptor - for mmap - file descriptor - for mmap
* user address - for memory translations in Vhost-user messages (e.g. - user address - for memory translations in Vhost-user messages (e.g.
translating vring addresses) translating vring addresses)
* guest address - for buffers addresses translations in vrings (for QEMU this - guest address - for buffers addresses translations in vrings (for QEMU this
is a physical address inside the guest) is a physical address inside the guest)
* user offset - positive offset for the mmap - user offset - positive offset for the mmap
* size - size
The Master will send new memory regions after each memory change - usually The Master will send new memory regions after each memory change - usually
hotplug/hotremove. The previous mappings will be removed. hotplug/hotremove. The previous mappings will be removed.
@ -108,11 +108,11 @@ as they use common SCSI I/O to inquiry the underlying disk(s).
Afterwards, the driver requests the number of maximum supported queues and Afterwards, the driver requests the number of maximum supported queues and
starts sending virtqueue data, which consists of: starts sending virtqueue data, which consists of:
* unique virtqueue id - unique virtqueue id
* index of the last processed vring descriptor - index of the last processed vring descriptor
* vring addresses (from user address space) - vring addresses (from user address space)
* call descriptor (for interrupting the driver after I/O completions) - call descriptor (for interrupting the driver after I/O completions)
* kick descriptor (to listen for I/O requests - unused by SPDK) - kick descriptor (to listen for I/O requests - unused by SPDK)
If multiqueue feature has been negotiated, the driver has to send a specific If multiqueue feature has been negotiated, the driver has to send a specific
*ENABLE* message for each extra queue it wants to be polled. Other queues are *ENABLE* message for each extra queue it wants to be polled. Other queues are

1
mdl_rules.rb
View File

@ -1,7 +1,6 @@
all all
exclude_rule 'MD003' exclude_rule 'MD003'
exclude_rule 'MD004' exclude_rule 'MD004'
exclude_rule 'MD005'
exclude_rule 'MD006' exclude_rule 'MD006'
exclude_rule 'MD007' exclude_rule 'MD007'
exclude_rule 'MD009' exclude_rule 'MD009'