Kconfig - OpenGrok cross reference for /openbmc/linux/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
179 	  MD_MULTIPATH provides a simple multi-path personality for use
188 	depends on BLK_DEV_MD
190 	  The "faulty" module allows for a block device that occasionally returns
198 	depends on BLK_DEV_MD
199 	depends on DLM
203 	synchronization across multiple systems on the cluster, so all
218 	tristate "Device mapper support"
222 	depends on DAX || DAX=n
224 	  Device-mapper is a low level volume manager.  It works by allowing
232 	  called dm-mod.
237 	bool "Device mapper debugging support"
238 	depends on BLK_DEV_DM
240 	  Enable this for messages that may help debug device-mapper problems.
246        depends on BLK_DEV_DM
248 	 This interface allows you to do buffered I/O on a device and acts
249 	 as a cache, holding recently-read blocks in memory and performing
254        depends on DM_BUFIO
262        depends on STACKTRACE_SUPPORT && DM_DEBUG_BLOCK_MANAGER_LOCKING
272        depends on BLK_DEV_DM
274 	 Some bio locking schemes used by other device-mapper targets
277 source "drivers/md/persistent-data/Kconfig"
281        depends on BLK_DEV_DM
283 	  Unstripes I/O so it is issued solely on a single drive in a HW
284 	  RAID0 or dm-striped target.
288 	depends on BLK_DEV_DM
289 	depends on (ENCRYPTED_KEYS || ENCRYPTED_KEYS=n)
290 	depends on (TRUSTED_KEYS || TRUSTED_KEYS=n)
295 	  This device-mapper target allows you to create a device that
296 	  transparently encrypts the data on it. You'll need to activate
299 	  For further information on dm-crypt and userspace tools see:
303 	  be called dm-crypt.
309        depends on BLK_DEV_DM
312 	 Allow volume managers to take writable snapshots of a device.
316        depends on BLK_DEV_DM
324        depends on BLK_DEV_DM
329 	 dm-cache attempts to improve performance of a block device by
331 	 device.  Different 'policy' plugins can be used to change the
337        depends on DM_CACHE
349 	depends on BLK_DEV_DM
351 	   The writecache target caches writes on persistent memory or SSD.
360 	depends on BLK_DEV_DM && !HIGHMEM
363 	  dm-ebs emulates smaller logical block size on backing devices
364 	  with larger ones (e.g. 512 byte sectors on 4K native disks).
368        depends on BLK_DEV_DM
373 	 dm-era tracks which parts of a block device are written to
379        depends on BLK_DEV_DM
383 	 dm-clone produces a one-to-one copy of an existing, read-only source
384 	 device into a writable destination device. The cloned device is
385 	 visible/mountable immediately and the copy of the source device to the
386 	 destination device happens in the background, in parallel with user
393        depends on BLK_DEV_DM
400 	depends on DM_MIRROR && NET
404 	  relaying the dm-dirty-log API to userspace.  Log designs
411        depends on BLK_DEV_DM
420 	 A RAID-5 set of N drives with a capacity of C MB per drive provides
421 	 the capacity of C * (N - 1) MB, and protects against a failure
422 	 of a single drive. For a given sector (row) number, (N - 1) drives
424 	 For a RAID-4 set, the parity blocks are present on a single drive,
425 	 while a RAID-5 set distributes the parity across the drives in one
428 	 A RAID-6 set of N drives with a capacity of C MB per drive
429 	 provides the capacity of C * (N - 2) MB, and protects
431 	 (row) number, (N - 2) drives contain data sectors, and two
433 	 RAID-5, RAID-6 distributes the syndromes across the drives
438 	depends on BLK_DEV_DM
445 	depends on BLK_DEV_DM
448 	# it is, DM_MULTIPATH must depend on it.  We get a build
450 	depends on !SCSI_DH || SCSI
455 	tristate "I/O Path Selector based on the number of in-flight I/Os"
456 	depends on DM_MULTIPATH
459 	  the path with the least number of in-flight I/Os.
464 	tristate "I/O Path Selector based on the service time"
465 	depends on DM_MULTIPATH
474 	tristate "I/O Path Selector based on historical service time"
475 	depends on DM_MULTIPATH
479 	  time by comparing estimated service time (based on historical
485 	tristate "I/O Path Selector based on CPU submission"
486 	depends on DM_MULTIPATH
488 	  This path selector selects the path based on the CPU the IO is
489 	  executed on and the CPU to path mapping setup at path addition time.
495 	depends on BLK_DEV_DM
504 	depends on BLK_DEV_DM
512 	bool "DM \"dm-mod.create=\" parameter support"
513 	depends on BLK_DEV_DM=y
515 	Enable "dm-mod.create=" parameter to create mapped devices at init time.
518 	See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
525 	depends on BLK_DEV_DM
531        depends on BLK_DEV_DM
537 	depends on BLK_DEV_DM
542 	  This device-mapper target creates a read-only device that
543 	  transparently validates the data on one underlying device against
544 	  a pre-generated tree of cryptographic checksums stored on a second
545 	  device.
551 	  be called dm-verity.
557 	bool "Verity data device root hash signature verification support"
558 	depends on DM_VERITY
561 	  Add ability for dm-verity device to be validated if the
562 	  pre-generated tree of cryptographic checksums passed has a pkcs#7
565 	  By default, rely on the builtin trusted keyring.
570 	bool "Verity data device root hash signature verification with secondary keyring"
571 	depends on DM_VERITY_VERIFY_ROOTHASH_SIG
572 	depends on SECONDARY_TRUSTED_KEYRING
574 	  Rely on the secondary trusted keyring to verify dm-verity signatures.
580 	depends on DM_VERITY
584 	  Add forward error correction support to dm-verity. This option
585 	  makes it possible to use pre-generated error correction data to
592 	depends on BLK_DEV_DM
594 	  This device-mapper target creates a device that supports an arbitrary
595 	  mapping of fixed-size regions of I/O across a fixed set of paths.
600 	  be called dm-switch.
606 	depends on BLK_DEV_DM
608 	  This device-mapper target takes two devices, one device to use
609 	  normally, one to log all write operations done to the first device.
616 	  be called dm-log-writes.
622 	depends on BLK_DEV_DM
630 	  This device-mapper target emulates a block device that has
631 	  additional per-sector tags that can be used for storing
634 	  This integrity target is used with the dm-crypt target to
639 	  be called dm-integrity.
642 	tristate "Drive-managed zoned block device target support"
643 	depends on BLK_DEV_DM
644 	depends on BLK_DEV_ZONED
647 	  This device-mapper target takes a host-managed or host-aware zoned
648 	  block device and exposes most of its capacity as a regular block
649 	  device (drive-managed zoned block device) without any write
657 	  be called dm-zoned.
663 	depends on BLK_DEV_DM
664 	depends on AUDIT
666 	  Generate audit events for device-mapper.
669 	  particular device-mapper targets, especially the integrity target.