Kconfig - OpenGrok cross reference for /linux-6.12.1/drivers/md/Kconfig

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
65 	tristate "RAID-0 (striping) mode"
69 	  use the so-called raid0 mode, i.e. it will combine the hard disk
75 	  Software-RAID mini-HOWTO, available from
85 	tristate "RAID-1 (mirroring) mode"
88 	  A RAID-1 set consists of several disk drives which are exact copies
90 	  will continue to use the operational mirrors in the set, providing
92 	  kernel.  In a set with N drives, the available space is the capacity
93 	  of a single drive, and the set protects against a failure of (N - 1)
97 	  Software-RAID mini-HOWTO, available from
101 	  If you want to use such a RAID-1 set, say Y.  To compile this code
107 	tristate "RAID-10 (mirrored striping) mode"
110 	  RAID-10 provides a combination of striping (RAID-0) and
111 	  mirroring (RAID-1) with easier configuration and more flexible
113 	  Unlike RAID-0, but like RAID-1, RAID-10 requires all devices to
116 	  RAID-10 provides a variety of layouts that provide different levels
119 	  RAID-10 requires mdadm-1.7.0 or later, available at:
126 	tristate "RAID-4/RAID-5/RAID-6 mode"
135 	  A RAID-5 set of N drives with a capacity of C MB per drive provides
136 	  the capacity of C * (N - 1) MB, and protects against a failure
137 	  of a single drive. For a given sector (row) number, (N - 1) drives
139 	  For a RAID-4 set, the parity blocks are present on a single drive,
140 	  while a RAID-5 set distributes the parity across the drives in one
143 	  A RAID-6 set of N drives with a capacity of C MB per drive
144 	  provides the capacity of C * (N - 2) MB, and protects
146 	  (row) number, (N - 2) drives contain data sectors, and two
148 	  RAID-5, RAID-6 distributes the syndromes across the drives
152 	  Software-RAID mini-HOWTO, available from
156 	  If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y.  To
190 	  Device-mapper is a low level volume manager.  It works by allowing
198 	  called dm-mod.
206 	  Enable this for messages that may help debug device-mapper problems.
215 	 as a cache, holding recently-read blocks in memory and performing
240 	 Some bio locking schemes used by other device-mapper targets
243 source "drivers/md/persistent-data/Kconfig"
250 	  RAID0 or dm-striped target.
261 	  This device-mapper target allows you to create a device that
265 	  For further information on dm-crypt and userspace tools see:
269 	  be called dm-crypt.
278 	 Allow volume managers to take writable snapshots of a device.
295 	 dm-cache attempts to improve performance of a block device by
329 	  dm-ebs emulates smaller logical block size on backing devices
339 	 dm-era tracks which parts of a block device are written to
340 	 over time.  Useful for maintaining cache coherency when using
349 	 dm-clone produces a one-to-one copy of an existing, read-only source
361 	 Allow volume managers to mirror logical volumes, also
370 	  relaying the dm-dirty-log API to userspace.  Log designs
386 	 A RAID-5 set of N drives with a capacity of C MB per drive provides
387 	 the capacity of C * (N - 1) MB, and protects against a failure
388 	 of a single drive. For a given sector (row) number, (N - 1) drives
390 	 For a RAID-4 set, the parity blocks are present on a single drive,
391 	 while a RAID-5 set distributes the parity across the drives in one
394 	 A RAID-6 set of N drives with a capacity of C MB per drive
395 	 provides the capacity of C * (N - 2) MB, and protects
397 	 (row) number, (N - 2) drives contain data sectors, and two
399 	 RAID-5, RAID-6 distributes the syndromes across the drives
418 	  Allow volume managers to support multipath hardware.
421 	tristate "I/O Path Selector based on the number of in-flight I/Os"
425 	  the path with the least number of in-flight I/Os.
430 	tristate "I/O Path Selector based on the service time"
435 	  time.
440 	tristate "I/O Path Selector based on historical service time"
445 	  time by comparing estimated service time (based on historical
446 	  service time).
455 	  executed on and the CPU to path mapping setup at path addition time.
478 	bool "DM \"dm-mod.create=\" parameter support"
481 	Enable "dm-mod.create=" parameter to create mapped devices at init time.
482 	This option is useful to allow mounting rootfs without requiring an
484 	See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
508 	  This device-mapper target creates a read-only device that
510 	  a pre-generated tree of cryptographic checksums stored on a second
517 	  be called dm-verity.
526 	  Add ability for dm-verity device to be validated if the
527 	  pre-generated tree of cryptographic checksums passed has a pkcs#7
539 	  Rely on the secondary trusted keyring to verify dm-verity signatures.
549 	  Rely also on the platform keyring to verify dm-verity signatures.
559 	  Add forward error correction support to dm-verity. This option
560 	  makes it possible to use pre-generated error correction data to
569 	  This device-mapper target creates a device that supports an arbitrary
570 	  mapping of fixed-size regions of I/O across a fixed set of paths.
575 	  be called dm-switch.
583 	  This device-mapper target takes two devices, one device to use
591 	  be called dm-log-writes.
605 	  This device-mapper target emulates a block device that has
606 	  additional per-sector tags that can be used for storing
609 	  This integrity target is used with the dm-crypt target to
614 	  be called dm-integrity.
617 	tristate "Drive-managed zoned block device target support"
622 	  This device-mapper target takes a host-managed or host-aware zoned
624 	  device (drive-managed zoned block device) without any write
632 	  be called dm-zoned.
641 	  Generate audit events for device-mapper.
644 	  particular device-mapper targets, especially the integrity target.
646 source "drivers/md/dm-vdo/Kconfig"