Searched full:raid0 (Results 1 – 21 of 21) sorted by relevance
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | unstriped.rst | 61 echo $DM_PARMS | dmsetup create raid0 63 echo "0 1 unstriped ${NUM} ${CHUNK} ${i} /dev/mapper/raid0 0" | dmsetup create set-${i} 75 dmsetup remove raid0
|
| H A D | dm-raid.rst | 20 raid0 RAID0 striping (no resilience) 394 1.7.0 Add support for MD RAID0 mappings.
|
| /linux/drivers/md/ |
| H A D | dm-raid.c | 65 #define __CTR_FLAG_SYNC 0 /* 1 */ /* Not with raid0! */ 66 #define __CTR_FLAG_NOSYNC 1 /* 1 */ /* Not with raid0! */ 67 #define __CTR_FLAG_REBUILD 2 /* 2 */ /* Not with raid0! */ 68 #define __CTR_FLAG_DAEMON_SLEEP 3 /* 2 */ /* Not with raid0! */ 69 #define __CTR_FLAG_MIN_RECOVERY_RATE 4 /* 2 */ /* Not with raid0! */ 70 #define __CTR_FLAG_MAX_RECOVERY_RATE 5 /* 2 */ /* Not with raid0! */ 74 #define __CTR_FLAG_REGION_SIZE 9 /* 2 */ /* Not with raid0! */ 139 /* "raid0" does only accept data offset */ 294 {"raid0", "raid0 (striping)", 0, 2, 0, 0 /* NONE */}, 400 /* Return true, if raid set in @rs is raid0 */ [all …]
|
| H A D | raid0.h | 13 * the RAID0 layout for multi-zone arrays (where devices aren't all
|
| H A D | md.c | 15 - RAID0 bugfixes: Mark Anthony Lisher <markal@iname.com> 1405 * (not needed for Linear and RAID0 as metadata doesn't in super_90_load() 3480 /* Cannot change size for RAID0 or Linear etc */ in rdev_size_store() 7627 /* Cannot trust RAID0 layout info here */ in md_set_array_info() 7680 * linear and raid0 always use whatever space is available. We can only in update_size() 9038 /* This is used by raid0 and raid10 */ 9984 * Raid personalities that don't have a thread (linear/raid0) do not
|
| /linux/Documentation/devicetree/bindings/dma/ |
| H A D | brcm,iproc-sba.yaml | 31 raid0 {
|
| /linux/include/uapi/linux/raid/ |
| H A D | md_u.h | 109 * means 'raid0', so we need something else. This is
|
| H A D | md_p.h | 328 #define MD_FEATURE_RAID0_LAYOUT 4096 /* layout is meaningful for RAID0 */
|
| /linux/arch/arm64/boot/dts/broadcom/stingray/ |
| H A D | stingray-fs4.dtsi | 55 raid0: raid@0 { label
|
| /linux/drivers/scsi/ |
| H A D | raid_class.c | 148 { RAID_LEVEL_0, "raid0" },
|
| /linux/Documentation/block/ |
| H A D | data-integrity.rst | 161 and MD linear, RAID0 and RAID1 are currently supported. RAID4/5/6
|
| /linux/drivers/scsi/mpt3sas/ |
| H A D | mpt3sas_warpdrive.c | 194 * not RAID0 in mpt3sas_init_warpdrive_properties()
|
| /linux/Documentation/driver-api/cxl/ |
| H A D | theory-of-operation.rst | 24 contrasting ways. One may choose performance (RAID0) striping memory across
|
| /linux/fs/btrfs/ |
| H A D | volumes.h | 55 * RAID0 always to be the lowest profile bit.
|
| H A D | scrub.c | 2242 * RAID0/RAID10). 2343 /* For RAID0, it's fixed to 1, for RAID10 it's 0,1,0,1... */ in simple_stripe_mirror_num() 2363 * Inside each stripe, RAID0 is just SINGLE, and RAID10 is in scrub_simple_stripe()
|
| H A D | zoned.c | 1737 * Currently, we cannot handle RAID0 or RAID10 case like this in btrfs_load_block_group_zone_info()
|
| H A D | volumes.c | 128 .raid_name = "raid0", 6573 * due to factors like zones and RAID0/5/6/10 stripe
|
| H A D | extent-tree.c | 4515 * fill raid0 from raid1. in find_free_extent()
|
| /linux/include/trace/events/ |
| H A D | btrfs.h | 137 { BTRFS_BLOCK_GROUP_RAID0, "RAID0"}, \ 1020 { BTRFS_BLOCK_GROUP_RAID0, "RAID0" }, \
|
| /linux/drivers/ata/ |
| H A D | pata_it821x.c | 615 "RAID0", "RAID1", "RAID 0+1", "JBOD", "DISK" in it821x_display_disk()
|
| /linux/drivers/scsi/megaraid/ |
| H A D | megaraid_sas_fusion.c | 3044 fpNonRWCapable, this is a single disk RAID0) */ in megasas_build_ld_nonrw_fusion()
|