# SPDX-License-Identifier: GPL-2.0-only
#
# Block device driver configuration
#
menuconfig [31mCONFIG_MD[0m
bool "Multiple devices driver support (RAID and LVM)"
depends on [31mCONFIG_BLOCK[0m
select [31mCONFIG_SRCU[0m
help
Support multiple physical spindles through a single logical device.
Required for RAID and logical volume management.
if [31mCONFIG_MD[0m
config [31mCONFIG_BLK_DEV_MD[0m
tristate "RAID support"
---help---
This driver lets you combine several hard disk partitions into one
logical block device. This can be used to simply append one
partition to another one or to combine several redundant hard disks
into a RAID1/4/5 device so as to provide protection against hard
disk failures. This is called "Software RAID" since the combining of
the partitions is done by the kernel. "Hardware RAID" means that the
combining is done by a dedicated controller; if you have such a
controller, you do not need to say Y here.
More information about Software RAID on Linux is contained in the
Software RAID mini-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. There you will also learn
where to get the supporting user space utilities raidtools.
If unsure, say N.
config [31mCONFIG_MD_AUTODETECT[0m
bool "Autodetect RAID arrays during kernel boot"
depends on [31mCONFIG_BLK_DEV_MD[0m=y
default y
---help---
If you say Y here, then the kernel will try to autodetect raid
arrays as part of its boot process.
If you don't use raid and say Y, this autodetection can cause
a several-second delay in the boot time due to various
synchronisation steps that are part of this step.
If unsure, say Y.
config [31mCONFIG_MD_LINEAR[0m
tristate "Linear (append) mode"
depends on [31mCONFIG_BLK_DEV_MD[0m
---help---
If you say Y here, then your multiple devices driver will be able to
use the so-called linear mode, i.e. it will combine the hard disk
partitions by simply appending one to the other.
To compile this as a module, choose [31mCONFIG_M[0m here: the module
will be called linear.
If unsure, say Y.
config [31mCONFIG_MD_RAID0[0m
tristate "RAID-0 (striping) mode"
depends on [31mCONFIG_BLK_DEV_MD[0m
---help---
If you say Y here, then your multiple devices driver will be able to
use the so-called raid0 mode, i.e. it will combine the hard disk
partitions into one logical device in such a fashion as to fill them
up evenly, one chunk here and one chunk there. This will increase
the throughput rate if the partitions reside on distinct disks.
Information about Software RAID on Linux is contained in the
Software-RAID mini-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. There you will also
learn where to get the supporting user space utilities raidtools.
To compile this as a module, choose [31mCONFIG_M[0m here: the module
will be called raid0.
If unsure, say Y.
config [31mCONFIG_MD_RAID1[0m
tristate "RAID-1 (mirroring) mode"
depends on [31mCONFIG_BLK_DEV_MD[0m
---help---
[31mCONFIG_A[0m RAID-1 set consists of several disk drives which are exact copies
of each other. In the event of a mirror failure, the RAID driver
will continue to use the operational mirrors in the set, providing
an error free [31mCONFIG_MD[0m (multiple device) to the higher levels of the
kernel. In a set with N drives, the available space is the capacity
of a single drive, and the set protects against a failure of (N - 1)
drives.
Information about Software RAID on Linux is contained in the
Software-RAID mini-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. There you will also
learn where to get the supporting user space utilities raidtools.
If you want to use such a RAID-1 set, say Y. To compile this code
as a module, choose [31mCONFIG_M[0m here: the module will be called raid1.
If unsure, say Y.
config [31mCONFIG_MD_RAID10[0m
tristate "RAID-10 (mirrored striping) mode"
depends on [31mCONFIG_BLK_DEV_MD[0m
---help---
RAID-10 provides a combination of striping (RAID-0) and
mirroring (RAID-1) with easier configuration and more flexible
layout.
Unlike RAID-0, but like RAID-1, RAID-10 requires all devices to
be the same size (or at least, only as much as the smallest device
will be used).
RAID-10 provides a variety of layouts that provide different levels
of redundancy and performance.
RAID-10 requires mdadm-1.7.0 or later, available at:
https://www.kernel.org/pub/linux/utils/raid/mdadm/
If unsure, say Y.
config [31mCONFIG_MD_RAID456[0m
tristate "RAID-4/RAID-5/RAID-6 mode"
depends on [31mCONFIG_BLK_DEV_MD[0m
select [31mCONFIG_RAID6_PQ[0m
select [31mCONFIG_LIBCRC32C[0m
select [31mCONFIG_ASYNC_MEMCPY[0m
select [31mCONFIG_ASYNC_XOR[0m
select [31mCONFIG_ASYNC_PQ[0m
select [31mCONFIG_ASYNC_RAID6_RECOV[0m
---help---
[31mCONFIG_A[0m RAID-5 set of N drives with a capacity of [31mCONFIG_C[0m MB per drive provides
the capacity of [31mCONFIG_C[0m * (N - 1) MB, and protects against a failure
of a single drive. For a given sector (row) number, (N - 1) drives
contain data sectors, and one drive contains the parity protection.
For a RAID-4 set, the parity blocks are present on a single drive,
while a RAID-5 set distributes the parity across the drives in one
of the available parity distribution methods.
[31mCONFIG_A[0m RAID-6 set of N drives with a capacity of [31mCONFIG_C[0m MB per drive
provides the capacity of [31mCONFIG_C[0m * (N - 2) MB, and protects
against a failure of any two drives. For a given sector
(row) number, (N - 2) drives contain data sectors, and two
drives contains two independent redundancy syndromes. Like
RAID-5, RAID-6 distributes the syndromes across the drives
in one of the available parity distribution methods.
Information about Software RAID on Linux is contained in the
Software-RAID mini-HOWTO, available from
<http://www.tldp.org/docs.html#howto>. There you will also
learn where to get the supporting user space utilities raidtools.
If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y. To
compile this code as a module, choose [31mCONFIG_M[0m here: the module
will be called raid456.
If unsure, say Y.
config [31mCONFIG_MD_MULTIPATH[0m
tristate "Multipath I/O support"
depends on [31mCONFIG_BLK_DEV_MD[0m
help
[31mCONFIG_MD_MULTIPATH[0m provides a simple multi-path personality for use
the [31mCONFIG_MD[0m framework. It is not under active development. New
projects should consider using [31mCONFIG_DM_MULTIPATH[0m which has more
features and more testing.
If unsure, say N.
config [31mCONFIG_MD_FAULTY[0m
tristate "Faulty test module for MD"
depends on [31mCONFIG_BLK_DEV_MD[0m
help
The "faulty" module allows for a block device that occasionally returns
read or write errors. It is useful for testing.
In unsure, say N.
config [31mCONFIG_MD_CLUSTER[0m
tristate "Cluster Support for MD"
depends on [31mCONFIG_BLK_DEV_MD[0m
depends on [31mCONFIG_DLM[0m
default n
---help---
Clustering support for [31mCONFIG_MD[0m devices. This enables locking and
synchronization across multiple systems on the cluster, so all
nodes in the cluster can access the [31mCONFIG_MD[0m devices simultaneously.
This brings the redundancy (and uptime) of RAID levels across the
nodes of the cluster. Currently, it can work with raid1 and raid10
(limited support).
If unsure, say N.
source "drivers/md/bcache/Kconfig"
config [31mCONFIG_BLK_DEV_DM_BUILTIN[0m
bool
config [31mCONFIG_BLK_DEV_DM[0m
tristate "Device mapper support"
select [31mCONFIG_BLK_DEV_DM_BUILTIN[0m
depends on [31mCONFIG_DAX[0m || [31mCONFIG_DAX[0m=n
---help---
Device-mapper is a low level volume manager. It works by allowing
people to specify mappings for ranges of logical sectors. Various
mapping types are available, in addition people may write their own
modules containing custom mappings if they wish.
Higher level volume managers such as LVM2 use this driver.
To compile this as a module, choose [31mCONFIG_M[0m here: the module will be
called dm-mod.
If unsure, say N.
config [31mCONFIG_DM_DEBUG[0m
bool "Device mapper debugging support"
depends on [31mCONFIG_BLK_DEV_DM[0m
---help---
Enable this for messages that may help debug device-mapper problems.
If unsure, say N.
config [31mCONFIG_DM_BUFIO[0m
tristate
depends on [31mCONFIG_BLK_DEV_DM[0m
---help---
This interface allows you to do buffered I/O on a device and acts
as a cache, holding recently-read blocks in memory and performing
delayed writes.
config [31mCONFIG_DM_DEBUG_BLOCK_MANAGER_LOCKING[0m
bool "Block manager locking"
depends on [31mCONFIG_DM_BUFIO[0m
---help---
Block manager locking can catch various metadata corruption issues.
If unsure, say N.
config [31mCONFIG_DM_DEBUG_BLOCK_STACK_TRACING[0m
bool "Keep stack trace of persistent data block lock holders"
depends on [31mCONFIG_STACKTRACE_SUPPORT[0m && [31mCONFIG_DM_DEBUG_BLOCK_MANAGER_LOCKING[0m
select [31mCONFIG_STACKTRACE[0m
---help---
Enable this for messages that may help debug problems with the
block manager locking used by thin provisioning and caching.
If unsure, say N.
config [31mCONFIG_DM_BIO_PRISON[0m
tristate
depends on [31mCONFIG_BLK_DEV_DM[0m
---help---
Some bio locking schemes used by other device-mapper targets
including thin provisioning.
source "drivers/md/persistent-data/Kconfig"
config [31mCONFIG_DM_UNSTRIPED[0m
tristate "Unstriped target"
depends on [31mCONFIG_BLK_DEV_DM[0m
---help---
Unstripes I/O so it is issued solely on a single drive in a HW
RAID0 or dm-striped target.
config [31mCONFIG_DM_CRYPT[0m
tristate "Crypt target support"
depends on [31mCONFIG_BLK_DEV_DM[0m
select [31mCONFIG_CRYPTO[0m
select [31mCONFIG_CRYPTO_CBC[0m
select [31mCONFIG_CRYPTO_ESSIV[0m
---help---
This device-mapper target allows you to create a device that
transparently encrypts the data on it. You'll need to activate
the ciphers you're going to use in the cryptoapi configuration.
For further information on dm-crypt and userspace tools see:
<https://gitlab.com/cryptsetup/cryptsetup/wikis/DMCrypt>
To compile this code as a module, choose [31mCONFIG_M[0m here: the module will
be called dm-crypt.
If unsure, say N.
config [31mCONFIG_DM_SNAPSHOT[0m
tristate "Snapshot target"
depends on [31mCONFIG_BLK_DEV_DM[0m
select [31mCONFIG_DM_BUFIO[0m
---help---
Allow volume managers to take writable snapshots of a device.
config [31mCONFIG_DM_THIN_PROVISIONING[0m
tristate "Thin provisioning target"
depends on [31mCONFIG_BLK_DEV_DM[0m
select [31mCONFIG_DM_PERSISTENT_DATA[0m
select [31mCONFIG_DM_BIO_PRISON[0m
---help---
Provides thin provisioning and snapshots that share a data store.
config [31mCONFIG_DM_CACHE[0m
tristate "Cache target (EXPERIMENTAL)"
depends on [31mCONFIG_BLK_DEV_DM[0m
default n
select [31mCONFIG_DM_PERSISTENT_DATA[0m
select [31mCONFIG_DM_BIO_PRISON[0m
---help---
dm-cache attempts to improve performance of a block device by
moving frequently used data to a smaller, higher performance
device. Different 'policy' plugins can be used to change the
algorithms used to select which blocks are promoted, demoted,
cleaned etc. It supports writeback and writethrough modes.
config [31mCONFIG_DM_CACHE_SMQ[0m
tristate "Stochastic MQ Cache Policy (EXPERIMENTAL)"
depends on [31mCONFIG_DM_CACHE[0m
default y
---help---
[31mCONFIG_A[0m cache policy that uses a multiqueue ordered by recent hits
to select which blocks should be promoted and demoted.
This is meant to be a general purpose policy. It prioritises
reads over writes. This SMQ policy (vs MQ) offers the promise
of less memory utilization, improved performance and increased
adaptability in the face of changing workloads.
config [31mCONFIG_DM_WRITECACHE[0m
tristate "Writecache target"
depends on [31mCONFIG_BLK_DEV_DM[0m
---help---
The writecache target caches writes on persistent memory or SSD.
It is intended for databases or other programs that need extremely
low commit latency.
The writecache target doesn't cache reads because reads are supposed
to be cached in standard RAM.
config [31mCONFIG_DM_ERA[0m
tristate "Era target (EXPERIMENTAL)"
depends on [31mCONFIG_BLK_DEV_DM[0m
default n
select [31mCONFIG_DM_PERSISTENT_DATA[0m
select [31mCONFIG_DM_BIO_PRISON[0m
---help---
dm-era tracks which parts of a block device are written to
over time. Useful for maintaining cache coherency when using
vendor snapshots.
config [31mCONFIG_DM_CLONE[0m
tristate "Clone target (EXPERIMENTAL)"
depends on [31mCONFIG_BLK_DEV_DM[0m
default n
select [31mCONFIG_DM_PERSISTENT_DATA[0m
---help---
dm-clone produces a one-to-one copy of an existing, read-only source
device into a writable destination device. The cloned device is
visible/mountable immediately and the copy of the source device to the
destination device happens in the background, in parallel with user
I/O.
If unsure, say N.
config [31mCONFIG_DM_MIRROR[0m
tristate "Mirror target"
depends on [31mCONFIG_BLK_DEV_DM[0m
---help---
Allow volume managers to mirror logical volumes, also
needed for live data migration tools such as 'pvmove'.
config [31mCONFIG_DM_LOG_USERSPACE[0m
tristate "Mirror userspace logging"
depends on [31mCONFIG_DM_MIRROR[0m && [31mCONFIG_NET[0m
select [31mCONFIG_CONNECTOR[0m
---help---
The userspace logging module provides a mechanism for
relaying the dm-dirty-log API to userspace. Log designs
which are more suited to userspace implementation (e.g.
shared storage logs) or experimental logs can be implemented
by leveraging this framework.
config [31mCONFIG_DM_RAID[0m
tristate "RAID 1/4/5/6/10 target"
depends on [31mCONFIG_BLK_DEV_DM[0m
select [31mCONFIG_MD_RAID0[0m
select [31mCONFIG_MD_RAID1[0m
select [31mCONFIG_MD_RAID10[0m
select [31mCONFIG_MD_RAID456[0m
select [31mCONFIG_BLK_DEV_MD[0m
---help---
[31mCONFIG_A[0m dm target that supports RAID1, RAID10, RAID4, RAID5 and RAID6 mappings
[31mCONFIG_A[0m RAID-5 set of N drives with a capacity of [31mCONFIG_C[0m MB per drive provides
the capacity of [31mCONFIG_C[0m * (N - 1) MB, and protects against a failure
of a single drive. For a given sector (row) number, (N - 1) drives
contain data sectors, and one drive contains the parity protection.
For a RAID-4 set, the parity blocks are present on a single drive,
while a RAID-5 set distributes the parity across the drives in one
of the available parity distribution methods.
[31mCONFIG_A[0m RAID-6 set of N drives with a capacity of [31mCONFIG_C[0m MB per drive
provides the capacity of [31mCONFIG_C[0m * (N - 2) MB, and protects
against a failure of any two drives. For a given sector
(row) number, (N - 2) drives contain data sectors, and two
drives contains two independent redundancy syndromes. Like
RAID-5, RAID-6 distributes the syndromes across the drives
in one of the available parity distribution methods.
config [31mCONFIG_DM_ZERO[0m
tristate "Zero target"
depends on [31mCONFIG_BLK_DEV_DM[0m
---help---
[31mCONFIG_A[0m target that discards writes, and returns all zeroes for
reads. Useful in some recovery situations.
config [31mCONFIG_DM_MULTIPATH[0m
tristate "Multipath target"
depends on [31mCONFIG_BLK_DEV_DM[0m
# nasty syntax but means make [31mCONFIG_DM_MULTIPATH[0m independent
# of [31mCONFIG_SCSI_DH[0m if the latter isn't defined but if
# it is, [31mCONFIG_DM_MULTIPATH[0m must depend on it. We get a build
# error if [31mCONFIG_SCSI_DH[0m=m and [31mCONFIG_DM_MULTIPATH[0m=y
depends on ![31mCONFIG_SCSI_DH[0m || [31mCONFIG_SCSI[0m
---help---
Allow volume managers to support multipath hardware.
config [31mCONFIG_DM_MULTIPATH_QL[0m
tristate "I/O Path Selector based on the number of in-flight I/Os"
depends on [31mCONFIG_DM_MULTIPATH[0m
---help---
This path selector is a dynamic load balancer which selects
the path with the least number of in-flight I/Os.
If unsure, say N.
config [31mCONFIG_DM_MULTIPATH_ST[0m
tristate "I/O Path Selector based on the service time"
depends on [31mCONFIG_DM_MULTIPATH[0m
---help---
This path selector is a dynamic load balancer which selects
the path expected to complete the incoming I/O in the shortest
time.
If unsure, say N.
config [31mCONFIG_DM_DELAY[0m
tristate "I/O delaying target"
depends on [31mCONFIG_BLK_DEV_DM[0m
---help---
[31mCONFIG_A[0m target that delays reads and/or writes and can send
them to different devices. Useful for testing.
If unsure, say N.
config [31mCONFIG_DM_DUST[0m
tristate "Bad sector simulation target"
depends on [31mCONFIG_BLK_DEV_DM[0m
---help---
[31mCONFIG_A[0m target that simulates bad sector behavior.
Useful for testing.
If unsure, say N.
config [31mCONFIG_DM_INIT[0m
bool "DM \"dm-mod.create=\" parameter support"
depends on [31mCONFIG_BLK_DEV_DM[0m=y
---help---
Enable "dm-mod.create=" parameter to create mapped devices at init time.
This option is useful to allow mounting rootfs without requiring an
initramfs.
See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
format.
If unsure, say N.
config [31mCONFIG_DM_UEVENT[0m
bool "DM uevents"
depends on [31mCONFIG_BLK_DEV_DM[0m
---help---
Generate udev events for DM events.
config [31mCONFIG_DM_FLAKEY[0m
tristate "Flakey target"
depends on [31mCONFIG_BLK_DEV_DM[0m
---help---
[31mCONFIG_A[0m target that intermittently fails I/O for debugging purposes.
config [31mCONFIG_DM_VERITY[0m
tristate "Verity target support"
depends on [31mCONFIG_BLK_DEV_DM[0m
select [31mCONFIG_CRYPTO[0m
select [31mCONFIG_CRYPTO_HASH[0m
select [31mCONFIG_DM_BUFIO[0m
---help---
This device-mapper target creates a read-only device that
transparently validates the data on one underlying device against
a pre-generated tree of cryptographic checksums stored on a second
device.
You'll need to activate the digests you're going to use in the
cryptoapi configuration.
To compile this code as a module, choose [31mCONFIG_M[0m here: the module will
be called dm-verity.
If unsure, say N.
config [31mCONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG[0m
def_bool n
bool "Verity data device root hash signature verification support"
depends on [31mCONFIG_DM_VERITY[0m
select [31mCONFIG_SYSTEM_DATA_VERIFICATION[0m
help
Add ability for dm-verity device to be validated if the
pre-generated tree of cryptographic checksums passed has a pkcs#7
signature file that can validate the roothash of the tree.
If unsure, say N.
config [31mCONFIG_DM_VERITY_FEC[0m
bool "Verity forward error correction support"
depends on [31mCONFIG_DM_VERITY[0m
select [31mCONFIG_REED_SOLOMON[0m
select [31mCONFIG_REED_SOLOMON_DEC8[0m
---help---
Add forward error correction support to dm-verity. This option
makes it possible to use pre-generated error correction data to
recover from corrupted blocks.
If unsure, say N.
config [31mCONFIG_DM_SWITCH[0m
tristate "Switch target support (EXPERIMENTAL)"
depends on [31mCONFIG_BLK_DEV_DM[0m
---help---
This device-mapper target creates a device that supports an arbitrary
mapping of fixed-size regions of I/O across a fixed set of paths.
The path used for any specific region can be switched dynamically
by sending the target a message.
To compile this code as a module, choose [31mCONFIG_M[0m here: the module will
be called dm-switch.
If unsure, say N.
config [31mCONFIG_DM_LOG_WRITES[0m
tristate "Log writes target support"
depends on [31mCONFIG_BLK_DEV_DM[0m
---help---
This device-mapper target takes two devices, one device to use
normally, one to log all write operations done to the first device.
This is for use by file system developers wishing to verify that
their fs is writing a consistent file system at all times by allowing
them to replay the log in a variety of ways and to check the
contents.
To compile this code as a module, choose [31mCONFIG_M[0m here: the module will
be called dm-log-writes.
If unsure, say N.
config [31mCONFIG_DM_INTEGRITY[0m
tristate "Integrity target support"
depends on [31mCONFIG_BLK_DEV_DM[0m
select [31mCONFIG_BLK_DEV_INTEGRITY[0m
select [31mCONFIG_DM_BUFIO[0m
select [31mCONFIG_CRYPTO[0m
select [31mCONFIG_ASYNC_XOR[0m
---help---
This device-mapper target emulates a block device that has
additional per-sector tags that can be used for storing
integrity information.
This integrity target is used with the dm-crypt target to
provide authenticated disk encryption or it can be used
standalone.
To compile this code as a module, choose [31mCONFIG_M[0m here: the module will
be called dm-integrity.
config [31mCONFIG_DM_ZONED[0m
tristate "Drive-managed zoned block device target support"
depends on [31mCONFIG_BLK_DEV_DM[0m
depends on [31mCONFIG_BLK_DEV_ZONED[0m
---help---
This device-mapper target takes a host-managed or host-aware zoned
block device and exposes most of its capacity as a regular block
device (drive-managed zoned block device) without any write
constraints. This is mainly intended for use with file systems that
do not natively support zoned block devices but still want to
benefit from the increased capacity offered by SMR disks. Other uses
by applications using raw block devices (for example object stores)
are also possible.
To compile this code as a module, choose [31mCONFIG_M[0m here: the module will
be called dm-zoned.
If unsure, say N.
endif # [31mCONFIG_MD[0m