Kconfig - OpenGrok cross reference for /OK3568_Linux_fs/kernel/drivers/md/Kconfig

1 # SPDX-License-Identifier: GPL-2.0-only
3 # Block device driver configuration
8 	depends on BLOCK
11 	  Support multiple physical spindles through a single logical device.
20 	  logical block device. This can be used to simply append one
22 	  into a RAID1/4/5 device so as to provide protection against hard
28 	  More information about Software RAID on Linux is contained in the
29 	  Software RAID mini-HOWTO, available from
37 	depends on BLK_DEV_MD=y
44 	  a several-second delay in the boot time due to various
51 	depends on BLK_DEV_MD
54 	  use the so-called linear mode, i.e. it will combine the hard disk
63 	tristate "RAID-0 (striping) mode"
64 	depends on BLK_DEV_MD
67 	  use the so-called raid0 mode, i.e. it will combine the hard disk
68 	  partitions into one logical device in such a fashion as to fill them
70 	  the throughput rate if the partitions reside on distinct disks.
72 	  Information about Software RAID on Linux is contained in the
73 	  Software-RAID mini-HOWTO, available from
83 	tristate "RAID-1 (mirroring) mode"
84 	depends on BLK_DEV_MD
86 	  A RAID-1 set consists of several disk drives which are exact copies
89 	  an error free MD (multiple device) to the higher levels of the
91 	  of a single drive, and the set protects against a failure of (N - 1)
94 	  Information about Software RAID on Linux is contained in the
95 	  Software-RAID mini-HOWTO, available from
99 	  If you want to use such a RAID-1 set, say Y.  To compile this code
105 	tristate "RAID-10 (mirrored striping) mode"
106 	depends on BLK_DEV_MD
108 	  RAID-10 provides a combination of striping (RAID-0) and
109 	  mirroring (RAID-1) with easier configuration and more flexible
111 	  Unlike RAID-0, but like RAID-1, RAID-10 requires all devices to
112 	  be the same size (or at least, only as much as the smallest device
114 	  RAID-10 provides a variety of layouts that provide different levels
117 	  RAID-10 requires mdadm-1.7.0 or later, available at:
124 	tristate "RAID-4/RAID-5/RAID-6 mode"
125 	depends on BLK_DEV_MD
133 	  A RAID-5 set of N drives with a capacity of C MB per drive provides
134 	  the capacity of C * (N - 1) MB, and protects against a failure
135 	  of a single drive. For a given sector (row) number, (N - 1) drives
137 	  For a RAID-4 set, the parity blocks are present on a single drive,
138 	  while a RAID-5 set distributes the parity across the drives in one
141 	  A RAID-6 set of N drives with a capacity of C MB per drive
142 	  provides the capacity of C * (N - 2) MB, and protects
144 	  (row) number, (N - 2) drives contain data sectors, and two
146 	  RAID-5, RAID-6 distributes the syndromes across the drives
149 	  Information about Software RAID on Linux is contained in the
150 	  Software-RAID mini-HOWTO, available from
154 	  If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y.  To
162 	depends on BLK_DEV_MD
164 	  MD_MULTIPATH provides a simple multi-path personality for use
173 	depends on BLK_DEV_MD
175 	  The "faulty" module allows for a block device that occasionally returns
183 	depends on BLK_DEV_MD
184 	depends on DLM
188 	synchronization across multiple systems on the cluster, so all
203 	tristate "Device mapper support"
205 	depends on DAX || DAX=n
207 	  Device-mapper is a low level volume manager.  It works by allowing
215 	  called dm-mod.
220 	bool "Device mapper debugging support"
221 	depends on BLK_DEV_DM
223 	  Enable this for messages that may help debug device-mapper problems.
229        depends on BLK_DEV_DM
231 	 This interface allows you to do buffered I/O on a device and acts
232 	 as a cache, holding recently-read blocks in memory and performing
237        depends on DM_BUFIO
245        depends on STACKTRACE_SUPPORT && DM_DEBUG_BLOCK_MANAGER_LOCKING
255        depends on BLK_DEV_DM
257 	 Some bio locking schemes used by other device-mapper targets
260 source "drivers/md/persistent-data/Kconfig"
264        depends on BLK_DEV_DM
266 	  Unstripes I/O so it is issued solely on a single drive in a HW
267 	  RAID0 or dm-striped target.
271 	depends on BLK_DEV_DM
272 	depends on (ENCRYPTED_KEYS || ENCRYPTED_KEYS=n)
277 	  This device-mapper target allows you to create a device that
278 	  transparently encrypts the data on it. You'll need to activate
281 	  For further information on dm-crypt and userspace tools see:
285 	  be called dm-crypt.
290 	tristate "Default-key target support"
291 	depends on BLK_DEV_DM
292 	depends on BLK_INLINE_ENCRYPTION
293 	# dm-default-key doesn't require -o inlinecrypt, but it does currently
294 	# rely on the inline encryption hooks being built into the kernel.
295 	depends on FS_ENCRYPTION_INLINE_CRYPT
297 	  This device-mapper target allows you to create a device that
301 	  This ensures that all blocks on-disk will be encrypted with
303 	  encrypted twice when fscrypt (File-Based Encryption) is used.
305 	  It is only appropriate to use dm-default-key when key
312        depends on BLK_DEV_DM
315 	 Allow volume managers to take writable snapshots of a device.
319        depends on BLK_DEV_DM
327        depends on BLK_DEV_DM
332 	 dm-cache attempts to improve performance of a block device by
334 	 device.  Different 'policy' plugins can be used to change the
340        depends on DM_CACHE
352 	depends on BLK_DEV_DM
354 	   The writecache target caches writes on persistent memory or SSD.
363 	depends on BLK_DEV_DM
366 	  dm-ebs emulates smaller logical block size on backing devices
367 	  with larger ones (e.g. 512 byte sectors on 4K native disks).
371        depends on BLK_DEV_DM
376 	 dm-era tracks which parts of a block device are written to
382        depends on BLK_DEV_DM
386 	 dm-clone produces a one-to-one copy of an existing, read-only source
387 	 device into a writable destination device. The cloned device is
388 	 visible/mountable immediately and the copy of the source device to the
389 	 destination device happens in the background, in parallel with user
396        depends on BLK_DEV_DM
403 	depends on DM_MIRROR && NET
407 	  relaying the dm-dirty-log API to userspace.  Log designs
414        depends on BLK_DEV_DM
423 	 A RAID-5 set of N drives with a capacity of C MB per drive provides
424 	 the capacity of C * (N - 1) MB, and protects against a failure
425 	 of a single drive. For a given sector (row) number, (N - 1) drives
427 	 For a RAID-4 set, the parity blocks are present on a single drive,
428 	 while a RAID-5 set distributes the parity across the drives in one
431 	 A RAID-6 set of N drives with a capacity of C MB per drive
432 	 provides the capacity of C * (N - 2) MB, and protects
434 	 (row) number, (N - 2) drives contain data sectors, and two
436 	 RAID-5, RAID-6 distributes the syndromes across the drives
441 	depends on BLK_DEV_DM
448 	depends on BLK_DEV_DM
451 	# it is, DM_MULTIPATH must depend on it.  We get a build
453 	depends on !SCSI_DH || SCSI
458 	tristate "I/O Path Selector based on the number of in-flight I/Os"
459 	depends on DM_MULTIPATH
462 	  the path with the least number of in-flight I/Os.
467 	tristate "I/O Path Selector based on the service time"
468 	depends on DM_MULTIPATH
477 	tristate "I/O Path Selector based on historical service time"
478 	depends on DM_MULTIPATH
482 	  time by comparing estimated service time (based on historical
489 	depends on BLK_DEV_DM
498 	depends on BLK_DEV_DM
506 	bool "DM \"dm-mod.create=\" parameter support"
507 	depends on BLK_DEV_DM=y
509 	Enable "dm-mod.create=" parameter to create mapped devices at init time.
512 	See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
519 	depends on BLK_DEV_DM
525        depends on BLK_DEV_DM
531 	depends on BLK_DEV_DM
536 	  This device-mapper target creates a read-only device that
537 	  transparently validates the data on one underlying device against
538 	  a pre-generated tree of cryptographic checksums stored on a second
539 	  device.
545 	  be called dm-verity.
551 	bool "Verity data device root hash signature verification support"
552 	depends on DM_VERITY
555 	  Add ability for dm-verity device to be validated if the
556 	  pre-generated tree of cryptographic checksums passed has a pkcs#7
563 	depends on DM_VERITY
567 	  Add forward error correction support to dm-verity. This option
568 	  makes it possible to use pre-generated error correction data to
575 	depends on BLK_DEV_DM
577 	  This device-mapper target creates a device that supports an arbitrary
578 	  mapping of fixed-size regions of I/O across a fixed set of paths.
583 	  be called dm-switch.
589 	depends on BLK_DEV_DM
591 	  This device-mapper target takes two devices, one device to use
592 	  normally, one to log all write operations done to the first device.
599 	  be called dm-log-writes.
605 	depends on BLK_DEV_DM
612 	  This device-mapper target emulates a block device that has
613 	  additional per-sector tags that can be used for storing
616 	  This integrity target is used with the dm-crypt target to
621 	  be called dm-integrity.
624 	tristate "Drive-managed zoned block device target support"
625 	depends on BLK_DEV_DM
626 	depends on BLK_DEV_ZONED
629 	  This device-mapper target takes a host-managed or host-aware zoned
630 	  block device and exposes most of its capacity as a regular block
631 	  device (drive-managed zoned block device) without any write
639 	  be called dm-zoned.
644 	tristate "Backup block device"
645 	depends on BLK_DEV_DM
648 	  This device-mapper target takes a device and keeps a log of all
656 	tristate "Block device in userspace"
657 	depends on BLK_DEV_DM
660 	  This device-mapper target allows a userspace daemon to provide the
661 	  contents of a block device.  See
662 	  <file:Documentation/block/dm-user.rst> for more information.
665 	  called dm-user.