Lines Matching +full:linear +full:- +full:mapping +full:- +full:mode
1 # SPDX-License-Identifier: GPL-2.0-only
29 Software RAID mini-HOWTO, available from
44 a several-second delay in the boot time due to various
50 tristate "Linear (append) mode"
54 use the so-called linear mode, i.e. it will combine the hard disk
58 will be called linear.
63 tristate "RAID-0 (striping) mode"
67 use the so-called raid0 mode, i.e. it will combine the hard disk
73 Software-RAID mini-HOWTO, available from
83 tristate "RAID-1 (mirroring) mode"
86 A RAID-1 set consists of several disk drives which are exact copies
91 of a single drive, and the set protects against a failure of (N - 1)
95 Software-RAID mini-HOWTO, available from
99 If you want to use such a RAID-1 set, say Y. To compile this code
105 tristate "RAID-10 (mirrored striping) mode"
108 RAID-10 provides a combination of striping (RAID-0) and
109 mirroring (RAID-1) with easier configuration and more flexible
111 Unlike RAID-0, but like RAID-1, RAID-10 requires all devices to
114 RAID-10 provides a variety of layouts that provide different levels
117 RAID-10 requires mdadm-1.7.0 or later, available at:
124 tristate "RAID-4/RAID-5/RAID-6 mode"
133 A RAID-5 set of N drives with a capacity of C MB per drive provides
134 the capacity of C * (N - 1) MB, and protects against a failure
135 of a single drive. For a given sector (row) number, (N - 1) drives
137 For a RAID-4 set, the parity blocks are present on a single drive,
138 while a RAID-5 set distributes the parity across the drives in one
141 A RAID-6 set of N drives with a capacity of C MB per drive
142 provides the capacity of C * (N - 2) MB, and protects
144 (row) number, (N - 2) drives contain data sectors, and two
146 RAID-5, RAID-6 distributes the syndromes across the drives
150 Software-RAID mini-HOWTO, available from
154 If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y. To
164 MD_MULTIPATH provides a simple multi-path personality for use
207 Device-mapper is a low level volume manager. It works by allowing
209 mapping types are available, in addition people may write their own
215 called dm-mod.
223 Enable this for messages that may help debug device-mapper problems.
232 as a cache, holding recently-read blocks in memory and performing
257 Some bio locking schemes used by other device-mapper targets
260 source "drivers/md/persistent-data/Kconfig"
267 RAID0 or dm-striped target.
277 This device-mapper target allows you to create a device that
281 For further information on dm-crypt and userspace tools see:
285 be called dm-crypt.
290 tristate "Default-key target support"
293 # dm-default-key doesn't require -o inlinecrypt, but it does currently
297 This device-mapper target allows you to create a device that
301 This ensures that all blocks on-disk will be encrypted with
303 encrypted twice when fscrypt (File-Based Encryption) is used.
305 It is only appropriate to use dm-default-key when key
332 dm-cache attempts to improve performance of a block device by
366 dm-ebs emulates smaller logical block size on backing devices
376 dm-era tracks which parts of a block device are written to
386 dm-clone produces a one-to-one copy of an existing, read-only source
407 relaying the dm-dirty-log API to userspace. Log designs
423 A RAID-5 set of N drives with a capacity of C MB per drive provides
424 the capacity of C * (N - 1) MB, and protects against a failure
425 of a single drive. For a given sector (row) number, (N - 1) drives
427 For a RAID-4 set, the parity blocks are present on a single drive,
428 while a RAID-5 set distributes the parity across the drives in one
431 A RAID-6 set of N drives with a capacity of C MB per drive
432 provides the capacity of C * (N - 2) MB, and protects
434 (row) number, (N - 2) drives contain data sectors, and two
436 RAID-5, RAID-6 distributes the syndromes across the drives
458 tristate "I/O Path Selector based on the number of in-flight I/Os"
462 the path with the least number of in-flight I/Os.
506 bool "DM \"dm-mod.create=\" parameter support"
509 Enable "dm-mod.create=" parameter to create mapped devices at init time.
512 See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
536 This device-mapper target creates a read-only device that
538 a pre-generated tree of cryptographic checksums stored on a second
545 be called dm-verity.
555 Add ability for dm-verity device to be validated if the
556 pre-generated tree of cryptographic checksums passed has a pkcs#7
567 Add forward error correction support to dm-verity. This option
568 makes it possible to use pre-generated error correction data to
577 This device-mapper target creates a device that supports an arbitrary
578 mapping of fixed-size regions of I/O across a fixed set of paths.
583 be called dm-switch.
591 This device-mapper target takes two devices, one device to use
599 be called dm-log-writes.
612 This device-mapper target emulates a block device that has
613 additional per-sector tags that can be used for storing
616 This integrity target is used with the dm-crypt target to
621 be called dm-integrity.
624 tristate "Drive-managed zoned block device target support"
629 This device-mapper target takes a host-managed or host-aware zoned
631 device (drive-managed zoned block device) without any write
639 be called dm-zoned.
648 This device-mapper target takes a device and keeps a log of all
660 This device-mapper target allows a userspace daemon to provide the
662 <file:Documentation/block/dm-user.rst> for more information.
665 called dm-user.