Lines Matching +full:allow +full:- +full:set +full:- +full:time
1 # SPDX-License-Identifier: GPL-2.0-only
20 # after relevant mdadm enhancements - to make "names=yes"
21 # the default - are widely available.
34 Software RAID mini-HOWTO, available from
49 a several-second delay in the boot time due to various
69 use the so-called linear mode, i.e. it will combine the hard disk
78 tristate "RAID-0 (striping) mode"
82 use the so-called raid0 mode, i.e. it will combine the hard disk
88 Software-RAID mini-HOWTO, available from
98 tristate "RAID-1 (mirroring) mode"
101 A RAID-1 set consists of several disk drives which are exact copies
103 will continue to use the operational mirrors in the set, providing
105 kernel. In a set with N drives, the available space is the capacity
106 of a single drive, and the set protects against a failure of (N - 1)
110 Software-RAID mini-HOWTO, available from
114 If you want to use such a RAID-1 set, say Y. To compile this code
120 tristate "RAID-10 (mirrored striping) mode"
123 RAID-10 provides a combination of striping (RAID-0) and
124 mirroring (RAID-1) with easier configuration and more flexible
126 Unlike RAID-0, but like RAID-1, RAID-10 requires all devices to
129 RAID-10 provides a variety of layouts that provide different levels
132 RAID-10 requires mdadm-1.7.0 or later, available at:
139 tristate "RAID-4/RAID-5/RAID-6 mode"
148 A RAID-5 set of N drives with a capacity of C MB per drive provides
149 the capacity of C * (N - 1) MB, and protects against a failure
150 of a single drive. For a given sector (row) number, (N - 1) drives
152 For a RAID-4 set, the parity blocks are present on a single drive,
153 while a RAID-5 set distributes the parity across the drives in one
156 A RAID-6 set of N drives with a capacity of C MB per drive
157 provides the capacity of C * (N - 2) MB, and protects
159 (row) number, (N - 2) drives contain data sectors, and two
161 RAID-5, RAID-6 distributes the syndromes across the drives
165 Software-RAID mini-HOWTO, available from
169 If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y. To
203 Device-mapper is a low level volume manager. It works by allowing
211 called dm-mod.
219 Enable this for messages that may help debug device-mapper problems.
228 as a cache, holding recently-read blocks in memory and performing
253 Some bio locking schemes used by other device-mapper targets
256 source "drivers/md/persistent-data/Kconfig"
263 RAID0 or dm-striped target.
274 This device-mapper target allows you to create a device that
278 For further information on dm-crypt and userspace tools see:
282 be called dm-crypt.
291 Allow volume managers to take writable snapshots of a device.
308 dm-cache attempts to improve performance of a block device by
342 dm-ebs emulates smaller logical block size on backing devices
352 dm-era tracks which parts of a block device are written to
353 over time. Useful for maintaining cache coherency when using
362 dm-clone produces a one-to-one copy of an existing, read-only source
374 Allow volume managers to mirror logical volumes, also
383 relaying the dm-dirty-log API to userspace. Log designs
399 A RAID-5 set of N drives with a capacity of C MB per drive provides
400 the capacity of C * (N - 1) MB, and protects against a failure
401 of a single drive. For a given sector (row) number, (N - 1) drives
403 For a RAID-4 set, the parity blocks are present on a single drive,
404 while a RAID-5 set distributes the parity across the drives in one
407 A RAID-6 set of N drives with a capacity of C MB per drive
408 provides the capacity of C * (N - 2) MB, and protects
410 (row) number, (N - 2) drives contain data sectors, and two
412 RAID-5, RAID-6 distributes the syndromes across the drives
431 Allow volume managers to support multipath hardware.
434 tristate "I/O Path Selector based on the number of in-flight I/Os"
438 the path with the least number of in-flight I/Os.
443 tristate "I/O Path Selector based on the service time"
448 time.
453 tristate "I/O Path Selector based on historical service time"
458 time by comparing estimated service time (based on historical
459 service time).
468 executed on and the CPU to path mapping setup at path addition time.
491 bool "DM \"dm-mod.create=\" parameter support"
494 Enable "dm-mod.create=" parameter to create mapped devices at init time.
495 This option is useful to allow mounting rootfs without requiring an
497 See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
521 This device-mapper target creates a read-only device that
523 a pre-generated tree of cryptographic checksums stored on a second
530 be called dm-verity.
539 Add ability for dm-verity device to be validated if the
540 pre-generated tree of cryptographic checksums passed has a pkcs#7
552 Rely on the secondary trusted keyring to verify dm-verity signatures.
562 Rely also on the platform keyring to verify dm-verity signatures.
572 Add forward error correction support to dm-verity. This option
573 makes it possible to use pre-generated error correction data to
582 This device-mapper target creates a device that supports an arbitrary
583 mapping of fixed-size regions of I/O across a fixed set of paths.
588 be called dm-switch.
596 This device-mapper target takes two devices, one device to use
604 be called dm-log-writes.
618 This device-mapper target emulates a block device that has
619 additional per-sector tags that can be used for storing
622 This integrity target is used with the dm-crypt target to
627 be called dm-integrity.
630 tristate "Drive-managed zoned block device target support"
635 This device-mapper target takes a host-managed or host-aware zoned
637 device (drive-managed zoned block device) without any write
645 be called dm-zoned.
654 Generate audit events for device-mapper.
657 particular device-mapper targets, especially the integrity target.
659 source "drivers/md/dm-vdo/Kconfig"