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

1 # SPDX-License-Identifier: GPL-2.0-only
3 # Block device driver configuration
8 	depends on BLOCK
10 	  Support multiple physical spindles through a single logical device.
20 	# after relevant mdadm enhancements - to make "names=yes"
21 	# the default - are widely available.
25 	  logical block device. This can be used to simply append one
27 	  into a RAID1/4/5 device so as to provide protection against hard
33 	  More information about Software RAID on Linux is contained in the
34 	  Software RAID mini-HOWTO, available from
42 	depends on BLK_DEV_MD=y
49 	  a several-second delay in the boot time due to various
58 	  If you say Y here, support for write intent bitmaps in files on an
61 	  various kernel APIs and can only work with files on a file system not
62 	  actually sitting on the MD device.
66 	depends on BLK_DEV_MD
69 	  use the so-called linear mode, i.e. it will combine the hard disk
78 	tristate "RAID-0 (striping) mode"
79 	depends on BLK_DEV_MD
82 	  use the so-called raid0 mode, i.e. it will combine the hard disk
83 	  partitions into one logical device in such a fashion as to fill them
85 	  the throughput rate if the partitions reside on distinct disks.
87 	  Information about Software RAID on Linux is contained in the
88 	  Software-RAID mini-HOWTO, available from
98 	tristate "RAID-1 (mirroring) mode"
99 	depends on BLK_DEV_MD
101 	  A RAID-1 set consists of several disk drives which are exact copies
104 	  an error free MD (multiple device) to the higher levels of the
106 	  of a single drive, and the set protects against a failure of (N - 1)
109 	  Information about Software RAID on Linux is contained in the
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"
121 	depends on BLK_DEV_MD
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
127 	  be the same size (or at least, only as much as the smallest device
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"
140 	depends on BLK_DEV_MD
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
164 	  Information about Software RAID on Linux is contained in the
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
177 	depends on BLK_DEV_MD
178 	depends on DLM
182 	synchronization across multiple systems on the cluster, so all
197 	tristate "Device mapper support"
201 	depends on DAX || DAX=n
203 	  Device-mapper is a low level volume manager.  It works by allowing
211 	  called dm-mod.
216 	bool "Device mapper debugging support"
217 	depends on BLK_DEV_DM
219 	  Enable this for messages that may help debug device-mapper problems.
225        depends on BLK_DEV_DM
227 	 This interface allows you to do buffered I/O on a device and acts
228 	 as a cache, holding recently-read blocks in memory and performing
233        depends on DM_BUFIO
241        depends on STACKTRACE_SUPPORT && DM_DEBUG_BLOCK_MANAGER_LOCKING
251        depends on BLK_DEV_DM
253 	 Some bio locking schemes used by other device-mapper targets
256 source "drivers/md/persistent-data/Kconfig"
260        depends on BLK_DEV_DM
262 	  Unstripes I/O so it is issued solely on a single drive in a HW
263 	  RAID0 or dm-striped target.
267 	depends on BLK_DEV_DM
268 	depends on (ENCRYPTED_KEYS || ENCRYPTED_KEYS=n)
269 	depends on (TRUSTED_KEYS || TRUSTED_KEYS=n)
275 	  This device-mapper target allows you to create a device that
276 	  transparently encrypts the data on it. You'll need to activate
279 	  For further information on dm-crypt and userspace tools see:
283 	  be called dm-crypt.
289        depends on BLK_DEV_DM
292 	 Allow volume managers to take writable snapshots of a device.
296        depends on BLK_DEV_DM
304        depends on BLK_DEV_DM
309 	 dm-cache attempts to improve performance of a block device by
311 	 device.  Different 'policy' plugins can be used to change the
317        depends on DM_CACHE
329 	depends on BLK_DEV_DM
331 	   The writecache target caches writes on persistent memory or SSD.
340 	depends on BLK_DEV_DM && !HIGHMEM
343 	  dm-ebs emulates smaller logical block size on backing devices
344 	  with larger ones (e.g. 512 byte sectors on 4K native disks).
348        depends on BLK_DEV_DM
353 	 dm-era tracks which parts of a block device are written to
359        depends on BLK_DEV_DM
363 	 dm-clone produces a one-to-one copy of an existing, read-only source
364 	 device into a writable destination device. The cloned device is
365 	 visible/mountable immediately and the copy of the source device to the
366 	 destination device happens in the background, in parallel with user
373        depends on BLK_DEV_DM
380 	depends on DM_MIRROR && NET
384 	  relaying the dm-dirty-log API to userspace.  Log designs
391        depends on BLK_DEV_DM
400 	 A RAID-5 set of N drives with a capacity of C MB per drive provides
401 	 the capacity of C * (N - 1) MB, and protects against a failure
402 	 of a single drive. For a given sector (row) number, (N - 1) drives
404 	 For a RAID-4 set, the parity blocks are present on a single drive,
405 	 while a RAID-5 set distributes the parity across the drives in one
408 	 A RAID-6 set of N drives with a capacity of C MB per drive
409 	 provides the capacity of C * (N - 2) MB, and protects
411 	 (row) number, (N - 2) drives contain data sectors, and two
413 	 RAID-5, RAID-6 distributes the syndromes across the drives
418 	depends on BLK_DEV_DM
425 	depends on BLK_DEV_DM
428 	# it is, DM_MULTIPATH must depend on it.  We get a build
430 	depends on !SCSI_DH || SCSI
435 	tristate "I/O Path Selector based on the number of in-flight I/Os"
436 	depends on DM_MULTIPATH
439 	  the path with the least number of in-flight I/Os.
444 	tristate "I/O Path Selector based on the service time"
445 	depends on DM_MULTIPATH
454 	tristate "I/O Path Selector based on historical service time"
455 	depends on DM_MULTIPATH
459 	  time by comparing estimated service time (based on historical
465 	tristate "I/O Path Selector based on CPU submission"
466 	depends on DM_MULTIPATH
468 	  This path selector selects the path based on the CPU the IO is
469 	  executed on and the CPU to path mapping setup at path addition time.
475 	depends on BLK_DEV_DM
484 	depends on BLK_DEV_DM
492 	bool "DM \"dm-mod.create=\" parameter support"
493 	depends on BLK_DEV_DM=y
495 	Enable "dm-mod.create=" parameter to create mapped devices at init time.
498 	See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
505 	depends on BLK_DEV_DM
511        depends on BLK_DEV_DM
517 	depends on BLK_DEV_DM
522 	  This device-mapper target creates a read-only device that
523 	  transparently validates the data on one underlying device against
524 	  a pre-generated tree of cryptographic checksums stored on a second
525 	  device.
531 	  be called dm-verity.
536 	bool "Verity data device root hash signature verification support"
537 	depends on DM_VERITY
540 	  Add ability for dm-verity device to be validated if the
541 	  pre-generated tree of cryptographic checksums passed has a pkcs#7
544 	  By default, rely on the builtin trusted keyring.
549 	bool "Verity data device root hash signature verification with secondary keyring"
550 	depends on DM_VERITY_VERIFY_ROOTHASH_SIG
551 	depends on SECONDARY_TRUSTED_KEYRING
553 	  Rely on the secondary trusted keyring to verify dm-verity signatures.
558 	bool "Verity data device root hash signature verification with platform keyring"
560 	depends on DM_VERITY_VERIFY_ROOTHASH_SIG
561 	depends on INTEGRITY_PLATFORM_KEYRING
563 	  Rely also on the platform keyring to verify dm-verity signatures.
569 	depends on DM_VERITY
573 	  Add forward error correction support to dm-verity. This option
574 	  makes it possible to use pre-generated error correction data to
581 	depends on BLK_DEV_DM
583 	  This device-mapper target creates a device that supports an arbitrary
584 	  mapping of fixed-size regions of I/O across a fixed set of paths.
589 	  be called dm-switch.
595 	depends on BLK_DEV_DM
597 	  This device-mapper target takes two devices, one device to use
598 	  normally, one to log all write operations done to the first device.
605 	  be called dm-log-writes.
611 	depends on BLK_DEV_DM
619 	  This device-mapper target emulates a block device that has
620 	  additional per-sector tags that can be used for storing
623 	  This integrity target is used with the dm-crypt target to
628 	  be called dm-integrity.
631 	tristate "Drive-managed zoned block device target support"
632 	depends on BLK_DEV_DM
633 	depends on BLK_DEV_ZONED
636 	  This device-mapper target takes a host-managed or host-aware zoned
637 	  block device and exposes most of its capacity as a regular block
638 	  device (drive-managed zoned block device) without any write
646 	  be called dm-zoned.
652 	depends on BLK_DEV_DM
653 	depends on AUDIT
655 	  Generate audit events for device-mapper.
658 	  particular device-mapper targets, especially the integrity target.
660 source "drivers/md/dm-vdo/Kconfig"