Commit 7a71ae51 authored by Monica Kenguva's avatar Monica Kenguva Committed by Tomasz Zawadzki
Browse files

doc: Moved RAID section in alphabetical order 



Signed-off-by: default avatarMonica Kenguva <monica.kenguva@intel.com>
Change-Id: I9db49b40a4d8276ae754f89257cbcdeae7a50914
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/3683


Tested-by: default avatarSPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: default avatarTomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: default avatarBen Walker <benjamin.walker@intel.com>
Reviewed-by: default avatarShuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com>
Reviewed-by: default avatarJim Harris <james.r.harris@intel.com>
parent 7a660b30

doc/bdev.md

+20 −20
Original line number Diff line number Diff line
@@ -443,26 +443,6 @@ Example commands 


`rpc.py bdev_lvol_create lvol2 25 -u 330a6ab2-f468-11e7-983e-001e67edf35d`



# RAID {#bdev_ug_raid}



RAID virtual bdev module provides functionality to combine any SPDK bdevs into

one RAID bdev. Currently SPDK supports only RAID 0. RAID functionality does not

store on-disk metadata on the member disks, so user must recreate the RAID

volume when restarting application. User may specify member disks to create RAID

volume event if they do not exists yet - as the member disks are registered at

a later time, the RAID module will claim them and will surface the RAID volume

after all of the member disks are available. It is allowed to use disks of

different sizes - the smallest disk size will be the amount of space used on

each member disk.



Example commands



`rpc.py bdev_raid_create -n Raid0 -z 64 -r 0 -b "lvol0 lvol1 lvol2 lvol3"`



`rpc.py bdev_raid_get_bdevs`



`rpc.py bdev_raid_delete Raid0`



# Passthru {#bdev_config_passthru}



The SPDK Passthru virtual block device module serves as an example of how to write a
@@ -512,6 +492,26 @@ To remove a block device representation use the bdev_pmem_delete command. 


`rpc.py bdev_pmem_delete pmem`



# RAID {#bdev_ug_raid}



RAID virtual bdev module provides functionality to combine any SPDK bdevs into

one RAID bdev. Currently SPDK supports only RAID 0. RAID functionality does not

store on-disk metadata on the member disks, so user must recreate the RAID

volume when restarting application. User may specify member disks to create RAID

volume event if they do not exists yet - as the member disks are registered at

a later time, the RAID module will claim them and will surface the RAID volume

after all of the member disks are available. It is allowed to use disks of

different sizes - the smallest disk size will be the amount of space used on

each member disk.



Example commands



`rpc.py bdev_raid_create -n Raid0 -z 64 -r 0 -b "lvol0 lvol1 lvol2 lvol3"`



`rpc.py bdev_raid_get_bdevs`



`rpc.py bdev_raid_delete Raid0`



# Uring {#bdev_ug_uring}



The uring bdev module issues I/O to kernel block devices using the io_uring Linux kernel API. This module requires liburing.