Kconfig - OpenGrok cross reference for /linux-6.12.1/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.
65 	tristate "RAID-0 (striping) mode"
66 	depends on BLK_DEV_MD
69 	  use the so-called raid0 mode, i.e. it will combine the hard disk
70 	  partitions into one logical device in such a fashion as to fill them
72 	  the throughput rate if the partitions reside on distinct disks.
74 	  Information about Software RAID on Linux is contained in the
75 	  Software-RAID mini-HOWTO, available from
85 	tristate "RAID-1 (mirroring) mode"
86 	depends on BLK_DEV_MD
88 	  A RAID-1 set consists of several disk drives which are exact copies
91 	  an error free MD (multiple device) to the higher levels of the
93 	  of a single drive, and the set protects against a failure of (N - 1)
96 	  Information about Software RAID on Linux is contained in the
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"
108 	depends on BLK_DEV_MD
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
114 	  be the same size (or at least, only as much as the smallest device
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"
127 	depends on BLK_DEV_MD
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
151 	  Information about Software RAID on Linux is contained in the
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
164 	depends on BLK_DEV_MD
165 	depends on DLM
169 	synchronization across multiple systems on the cluster, so all
184 	tristate "Device mapper support"
188 	depends on DAX || DAX=n
190 	  Device-mapper is a low level volume manager.  It works by allowing
198 	  called dm-mod.
203 	bool "Device mapper debugging support"
204 	depends on BLK_DEV_DM
206 	  Enable this for messages that may help debug device-mapper problems.
212        depends on BLK_DEV_DM
214 	 This interface allows you to do buffered I/O on a device and acts
215 	 as a cache, holding recently-read blocks in memory and performing
220        depends on DM_BUFIO
228        depends on STACKTRACE_SUPPORT && DM_DEBUG_BLOCK_MANAGER_LOCKING
238        depends on BLK_DEV_DM
240 	 Some bio locking schemes used by other device-mapper targets
243 source "drivers/md/persistent-data/Kconfig"
247        depends on BLK_DEV_DM
249 	  Unstripes I/O so it is issued solely on a single drive in a HW
250 	  RAID0 or dm-striped target.
254 	depends on BLK_DEV_DM
255 	depends on (ENCRYPTED_KEYS || ENCRYPTED_KEYS=n)
256 	depends on (TRUSTED_KEYS || TRUSTED_KEYS=n)
261 	  This device-mapper target allows you to create a device that
262 	  transparently encrypts the data on it. You'll need to activate
265 	  For further information on dm-crypt and userspace tools see:
269 	  be called dm-crypt.
275        depends on BLK_DEV_DM
278 	 Allow volume managers to take writable snapshots of a device.
282        depends on BLK_DEV_DM
290        depends on BLK_DEV_DM
295 	 dm-cache attempts to improve performance of a block device by
297 	 device.  Different 'policy' plugins can be used to change the
303        depends on DM_CACHE
315 	depends on BLK_DEV_DM
317 	   The writecache target caches writes on persistent memory or SSD.
326 	depends on BLK_DEV_DM && !HIGHMEM
329 	  dm-ebs emulates smaller logical block size on backing devices
330 	  with larger ones (e.g. 512 byte sectors on 4K native disks).
334        depends on BLK_DEV_DM
339 	 dm-era tracks which parts of a block device are written to
345        depends on BLK_DEV_DM
349 	 dm-clone produces a one-to-one copy of an existing, read-only source
350 	 device into a writable destination device. The cloned device is
351 	 visible/mountable immediately and the copy of the source device to the
352 	 destination device happens in the background, in parallel with user
359        depends on BLK_DEV_DM
366 	depends on DM_MIRROR && NET
370 	  relaying the dm-dirty-log API to userspace.  Log designs
377        depends on BLK_DEV_DM
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
404 	depends on BLK_DEV_DM
411 	depends on BLK_DEV_DM
414 	# it is, DM_MULTIPATH must depend on it.  We get a build
416 	depends on !SCSI_DH || SCSI
421 	tristate "I/O Path Selector based on the number of in-flight I/Os"
422 	depends on DM_MULTIPATH
425 	  the path with the least number of in-flight I/Os.
430 	tristate "I/O Path Selector based on the service time"
431 	depends on DM_MULTIPATH
440 	tristate "I/O Path Selector based on historical service time"
441 	depends on DM_MULTIPATH
445 	  time by comparing estimated service time (based on historical
451 	tristate "I/O Path Selector based on CPU submission"
452 	depends on DM_MULTIPATH
454 	  This path selector selects the path based on the CPU the IO is
455 	  executed on and the CPU to path mapping setup at path addition time.
461 	depends on BLK_DEV_DM
470 	depends on BLK_DEV_DM
478 	bool "DM \"dm-mod.create=\" parameter support"
479 	depends on BLK_DEV_DM=y
481 	Enable "dm-mod.create=" parameter to create mapped devices at init time.
484 	See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
491 	depends on BLK_DEV_DM
497        depends on BLK_DEV_DM
503 	depends on BLK_DEV_DM
508 	  This device-mapper target creates a read-only device that
509 	  transparently validates the data on one underlying device against
510 	  a pre-generated tree of cryptographic checksums stored on a second
511 	  device.
517 	  be called dm-verity.
522 	bool "Verity data device root hash signature verification support"
523 	depends on 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
530 	  By default, rely on the builtin trusted keyring.
535 	bool "Verity data device root hash signature verification with secondary keyring"
536 	depends on DM_VERITY_VERIFY_ROOTHASH_SIG
537 	depends on SECONDARY_TRUSTED_KEYRING
539 	  Rely on the secondary trusted keyring to verify dm-verity signatures.
544 	bool "Verity data device root hash signature verification with platform keyring"
546 	depends on DM_VERITY_VERIFY_ROOTHASH_SIG
547 	depends on INTEGRITY_PLATFORM_KEYRING
549 	  Rely also on the platform keyring to verify dm-verity signatures.
555 	depends on DM_VERITY
559 	  Add forward error correction support to dm-verity. This option
560 	  makes it possible to use pre-generated error correction data to
567 	depends on BLK_DEV_DM
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.
581 	depends on BLK_DEV_DM
583 	  This device-mapper target takes two devices, one device to use
584 	  normally, one to log all write operations done to the first device.
591 	  be called dm-log-writes.
597 	depends on BLK_DEV_DM
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"
618 	depends on BLK_DEV_DM
619 	depends on BLK_DEV_ZONED
622 	  This device-mapper target takes a host-managed or host-aware zoned
623 	  block device and exposes most of its capacity as a regular block
624 	  device (drive-managed zoned block device) without any write
632 	  be called dm-zoned.
638 	depends on BLK_DEV_DM
639 	depends on AUDIT
641 	  Generate audit events for device-mapper.
644 	  particular device-mapper targets, especially the integrity target.
646 source "drivers/md/dm-vdo/Kconfig"