2019-05-19 12:07:45 +00:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2005-04-16 22:20:36 +00:00
|
|
|
#
|
|
|
|
|
# Block device driver configuration
|
|
|
|
|
#
|
|
|
|
|
|
2007-07-17 11:06:11 +00:00
|
|
|
menuconfig MD
|
2005-04-16 22:20:36 +00:00
|
|
|
bool "Multiple devices driver support (RAID and LVM)"
|
2007-07-17 11:06:11 +00:00
|
|
|
depends on BLOCK
|
2014-12-05 16:24:45 +00:00
|
|
|
select SRCU
|
2005-04-16 22:20:36 +00:00
|
|
|
help
|
|
|
|
|
Support multiple physical spindles through a single logical device.
|
|
|
|
|
Required for RAID and logical volume management.
|
|
|
|
|
|
2007-07-17 11:06:11 +00:00
|
|
|
if MD
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config BLK_DEV_MD
|
|
|
|
|
tristate "RAID support"
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2005-04-16 22:20:36 +00:00
|
|
|
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
|
2020-06-27 10:31:38 +00:00
|
|
|
<https://www.tldp.org/docs.html#howto>. There you will also learn
|
2005-04-16 22:20:36 +00:00
|
|
|
where to get the supporting user space utilities raidtools.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2008-09-21 22:44:32 +00:00
|
|
|
config MD_AUTODETECT
|
|
|
|
|
bool "Autodetect RAID arrays during kernel boot"
|
2008-10-10 15:02:53 +00:00
|
|
|
depends on BLK_DEV_MD=y
|
2008-09-21 22:44:32 +00:00
|
|
|
default y
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2008-09-21 22:44:32 +00:00
|
|
|
If you say Y here, then the kernel will try to autodetect raid
|
2019-11-20 13:41:10 +00:00
|
|
|
arrays as part of its boot process.
|
2008-09-21 22:44:32 +00:00
|
|
|
|
2019-11-20 13:41:10 +00:00
|
|
|
If you don't use raid and say Y, this autodetection can cause
|
2008-09-21 22:44:32 +00:00
|
|
|
a several-second delay in the boot time due to various
|
|
|
|
|
synchronisation steps that are part of this step.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config MD_LINEAR
|
|
|
|
|
tristate "Linear (append) mode"
|
|
|
|
|
depends on BLK_DEV_MD
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2005-04-16 22:20:36 +00:00
|
|
|
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 M here: the module
|
|
|
|
|
will be called linear.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
|
|
|
|
config MD_RAID0
|
|
|
|
|
tristate "RAID-0 (striping) mode"
|
|
|
|
|
depends on BLK_DEV_MD
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2005-04-16 22:20:36 +00:00
|
|
|
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
|
2020-06-27 10:31:38 +00:00
|
|
|
<https://www.tldp.org/docs.html#howto>. There you will also
|
2005-04-16 22:20:36 +00:00
|
|
|
learn where to get the supporting user space utilities raidtools.
|
|
|
|
|
|
|
|
|
|
To compile this as a module, choose M here: the module
|
|
|
|
|
will be called raid0.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
|
|
|
|
config MD_RAID1
|
|
|
|
|
tristate "RAID-1 (mirroring) mode"
|
|
|
|
|
depends on BLK_DEV_MD
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2005-04-16 22:20:36 +00:00
|
|
|
A 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 MD (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
|
2020-06-27 10:31:38 +00:00
|
|
|
<https://www.tldp.org/docs.html#howto>. There you will also
|
2005-04-16 22:20:36 +00:00
|
|
|
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 M here: the module will be called raid1.
|
|
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
|
|
|
|
config MD_RAID10
|
2010-05-03 03:16:56 +00:00
|
|
|
tristate "RAID-10 (mirrored striping) mode"
|
|
|
|
|
depends on BLK_DEV_MD
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2005-04-16 22:20:36 +00:00
|
|
|
RAID-10 provides a combination of striping (RAID-0) and
|
2006-06-26 07:27:50 +00:00
|
|
|
mirroring (RAID-1) with easier configuration and more flexible
|
2005-04-16 22:20:36 +00:00
|
|
|
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:
|
|
|
|
|
|
2017-03-27 12:44:06 +00:00
|
|
|
https://www.kernel.org/pub/linux/utils/raid/mdadm/
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
2006-06-26 07:27:38 +00:00
|
|
|
config MD_RAID456
|
|
|
|
|
tristate "RAID-4/RAID-5/RAID-6 mode"
|
2005-04-16 22:20:36 +00:00
|
|
|
depends on BLK_DEV_MD
|
2009-07-13 10:35:12 +00:00
|
|
|
select RAID6_PQ
|
2015-11-03 14:12:01 +00:00
|
|
|
select LIBCRC32C
|
async_tx: add the async_tx api
The async_tx api provides methods for describing a chain of asynchronous
bulk memory transfers/transforms with support for inter-transactional
dependencies. It is implemented as a dmaengine client that smooths over
the details of different hardware offload engine implementations. Code
that is written to the api can optimize for asynchronous operation and the
api will fit the chain of operations to the available offload resources.
I imagine that any piece of ADMA hardware would register with the
'async_*' subsystem, and a call to async_X would be routed as
appropriate, or be run in-line. - Neil Brown
async_tx exploits the capabilities of struct dma_async_tx_descriptor to
provide an api of the following general format:
struct dma_async_tx_descriptor *
async_<operation>(..., struct dma_async_tx_descriptor *depend_tx,
dma_async_tx_callback cb_fn, void *cb_param)
{
struct dma_chan *chan = async_tx_find_channel(depend_tx, <operation>);
struct dma_device *device = chan ? chan->device : NULL;
int int_en = cb_fn ? 1 : 0;
struct dma_async_tx_descriptor *tx = device ?
device->device_prep_dma_<operation>(chan, len, int_en) : NULL;
if (tx) { /* run <operation> asynchronously */
...
tx->tx_set_dest(addr, tx, index);
...
tx->tx_set_src(addr, tx, index);
...
async_tx_submit(chan, tx, flags, depend_tx, cb_fn, cb_param);
} else { /* run <operation> synchronously */
...
<operation>
...
async_tx_sync_epilog(flags, depend_tx, cb_fn, cb_param);
}
return tx;
}
async_tx_find_channel() returns a capable channel from its pool. The
channel pool is organized as a per-cpu array of channel pointers. The
async_tx_rebalance() routine is tasked with managing these arrays. In the
uniprocessor case async_tx_rebalance() tries to spread responsibility
evenly over channels of similar capabilities. For example if there are two
copy+xor channels, one will handle copy operations and the other will
handle xor. In the SMP case async_tx_rebalance() attempts to spread the
operations evenly over the cpus, e.g. cpu0 gets copy channel0 and xor
channel0 while cpu1 gets copy channel 1 and xor channel 1. When a
dependency is specified async_tx_find_channel defaults to keeping the
operation on the same channel. A xor->copy->xor chain will stay on one
channel if it supports both operation types, otherwise the transaction will
transition between a copy and a xor resource.
Currently the raid5 implementation in the MD raid456 driver has been
converted to the async_tx api. A driver for the offload engines on the
Intel Xscale series of I/O processors, iop-adma, is provided in a later
commit. With the iop-adma driver and async_tx, raid456 is able to offload
copy, xor, and xor-zero-sum operations to hardware engines.
On iop342 tiobench showed higher throughput for sequential writes (20 - 30%
improvement) and sequential reads to a degraded array (40 - 55%
improvement). For the other cases performance was roughly equal, +/- a few
percentage points. On a x86-smp platform the performance of the async_tx
implementation (in synchronous mode) was also +/- a few percentage points
of the original implementation. According to 'top' on iop342 CPU
utilization drops from ~50% to ~15% during a 'resync' while the speed
according to /proc/mdstat doubles from ~25 MB/s to ~50 MB/s.
The tiobench command line used for testing was: tiobench --size 2048
--block 4096 --block 131072 --dir /mnt/raid --numruns 5
* iop342 had 1GB of memory available
Details:
* if CONFIG_DMA_ENGINE=n the asynchronous path is compiled away by making
async_tx_find_channel a static inline routine that always returns NULL
* when a callback is specified for a given transaction an interrupt will
fire at operation completion time and the callback will occur in a
tasklet. if the the channel does not support interrupts then a live
polling wait will be performed
* the api is written as a dmaengine client that requests all available
channels
* In support of dependencies the api implicitly schedules channel-switch
interrupts. The interrupt triggers the cleanup tasklet which causes
pending operations to be scheduled on the next channel
* Xor engines treat an xor destination address differently than a software
xor routine. To the software routine the destination address is an implied
source, whereas engines treat it as a write-only destination. This patch
modifies the xor_blocks routine to take a an explicit destination address
to mirror the hardware.
Changelog:
* fixed a leftover debug print
* don't allow callbacks in async_interrupt_cond
* fixed xor_block changes
* fixed usage of ASYNC_TX_XOR_DROP_DEST
* drop dma mapping methods, suggested by Chris Leech
* printk warning fixups from Andrew Morton
* don't use inline in C files, Adrian Bunk
* select the API when MD is enabled
* BUG_ON xor source counts <= 1
* implicitly handle hardware concerns like channel switching and
interrupts, Neil Brown
* remove the per operation type list, and distribute operation capabilities
evenly amongst the available channels
* simplify async_tx_find_channel to optimize the fast path
* introduce the channel_table_initialized flag to prevent early calls to
the api
* reorganize the code to mimic crypto
* include mm.h as not all archs include it in dma-mapping.h
* make the Kconfig options non-user visible, Adrian Bunk
* move async_tx under crypto since it is meant as 'core' functionality, and
the two may share algorithms in the future
* move large inline functions into c files
* checkpatch.pl fixes
* gpl v2 only correction
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Acked-By: NeilBrown <neilb@suse.de>
2007-01-02 18:10:44 +00:00
|
|
|
select ASYNC_MEMCPY
|
|
|
|
|
select ASYNC_XOR
|
2009-07-14 20:40:19 +00:00
|
|
|
select ASYNC_PQ
|
|
|
|
|
select ASYNC_RAID6_RECOV
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2005-04-16 22:20:36 +00:00
|
|
|
A RAID-5 set of N drives with a capacity of C MB per drive provides
|
|
|
|
|
the capacity of C * (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.
|
|
|
|
|
|
2006-06-26 07:27:38 +00:00
|
|
|
A RAID-6 set of N drives with a capacity of C MB per drive
|
|
|
|
|
provides the capacity of C * (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.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
Information about Software RAID on Linux is contained in the
|
|
|
|
|
Software-RAID mini-HOWTO, available from
|
2020-06-27 10:31:38 +00:00
|
|
|
<https://www.tldp.org/docs.html#howto>. There you will also
|
2005-04-16 22:20:36 +00:00
|
|
|
learn where to get the supporting user space utilities raidtools.
|
|
|
|
|
|
2006-06-26 07:27:38 +00:00
|
|
|
If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y. To
|
2005-04-16 22:20:36 +00:00
|
|
|
compile this code as a module, choose M here: the module
|
2006-06-26 07:27:38 +00:00
|
|
|
will be called raid456.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
|
|
|
|
config MD_MULTIPATH
|
|
|
|
|
tristate "Multipath I/O support"
|
|
|
|
|
depends on BLK_DEV_MD
|
|
|
|
|
help
|
2009-12-14 01:49:59 +00:00
|
|
|
MD_MULTIPATH provides a simple multi-path personality for use
|
|
|
|
|
the MD framework. It is not under active development. New
|
|
|
|
|
projects should consider using DM_MULTIPATH which has more
|
|
|
|
|
features and more testing.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config MD_FAULTY
|
|
|
|
|
tristate "Faulty test module for MD"
|
|
|
|
|
depends on BLK_DEV_MD
|
|
|
|
|
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.
|
|
|
|
|
|
2014-03-07 17:21:15 +00:00
|
|
|
|
|
|
|
|
config MD_CLUSTER
|
2017-10-24 07:11:53 +00:00
|
|
|
tristate "Cluster Support for MD"
|
2014-03-07 17:21:15 +00:00
|
|
|
depends on BLK_DEV_MD
|
|
|
|
|
depends on DLM
|
|
|
|
|
default n
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2014-03-07 17:21:15 +00:00
|
|
|
Clustering support for MD devices. This enables locking and
|
|
|
|
|
synchronization across multiple systems on the cluster, so all
|
|
|
|
|
nodes in the cluster can access the MD devices simultaneously.
|
|
|
|
|
|
|
|
|
|
This brings the redundancy (and uptime) of RAID levels across the
|
2017-10-24 07:11:53 +00:00
|
|
|
nodes of the cluster. Currently, it can work with raid1 and raid10
|
|
|
|
|
(limited support).
|
2014-03-07 17:21:15 +00:00
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2013-03-23 23:11:31 +00:00
|
|
|
source "drivers/md/bcache/Kconfig"
|
|
|
|
|
|
2014-01-14 00:37:54 +00:00
|
|
|
config BLK_DEV_DM_BUILTIN
|
2014-12-20 20:41:11 +00:00
|
|
|
bool
|
2014-01-14 00:37:54 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config BLK_DEV_DM
|
|
|
|
|
tristate "Device mapper support"
|
2014-01-14 00:37:54 +00:00
|
|
|
select BLK_DEV_DM_BUILTIN
|
2018-03-30 00:22:13 +00:00
|
|
|
depends on DAX || DAX=n
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2005-04-16 22:20:36 +00:00
|
|
|
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 M here: the module will be
|
|
|
|
|
called dm-mod.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2006-10-03 08:15:35 +00:00
|
|
|
config DM_DEBUG
|
2014-12-20 20:41:11 +00:00
|
|
|
bool "Device mapper debugging support"
|
2008-02-08 02:10:32 +00:00
|
|
|
depends on BLK_DEV_DM
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2006-10-03 08:15:35 +00:00
|
|
|
Enable this for messages that may help debug device-mapper problems.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2011-10-31 20:19:09 +00:00
|
|
|
config DM_BUFIO
|
|
|
|
|
tristate
|
2013-03-01 22:45:46 +00:00
|
|
|
depends on BLK_DEV_DM
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2011-10-31 20:19:09 +00:00
|
|
|
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.
|
|
|
|
|
|
2015-11-19 13:50:32 +00:00
|
|
|
config DM_DEBUG_BLOCK_MANAGER_LOCKING
|
|
|
|
|
bool "Block manager locking"
|
|
|
|
|
depends on DM_BUFIO
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2015-11-19 13:50:32 +00:00
|
|
|
Block manager locking can catch various metadata corruption issues.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2015-11-24 00:20:06 +00:00
|
|
|
config DM_DEBUG_BLOCK_STACK_TRACING
|
|
|
|
|
bool "Keep stack trace of persistent data block lock holders"
|
2015-11-19 13:50:32 +00:00
|
|
|
depends on STACKTRACE_SUPPORT && DM_DEBUG_BLOCK_MANAGER_LOCKING
|
2015-11-24 00:20:06 +00:00
|
|
|
select STACKTRACE
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2015-11-24 00:20:06 +00:00
|
|
|
Enable this for messages that may help debug problems with the
|
|
|
|
|
block manager locking used by thin provisioning and caching.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
2016-03-04 19:37:16 +00:00
|
|
|
|
2012-10-12 20:02:13 +00:00
|
|
|
config DM_BIO_PRISON
|
|
|
|
|
tristate
|
2013-03-01 22:45:46 +00:00
|
|
|
depends on BLK_DEV_DM
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2012-10-12 20:02:13 +00:00
|
|
|
Some bio locking schemes used by other device-mapper targets
|
|
|
|
|
including thin provisioning.
|
|
|
|
|
|
2011-10-31 20:21:18 +00:00
|
|
|
source "drivers/md/persistent-data/Kconfig"
|
|
|
|
|
|
2017-12-18 17:28:08 +00:00
|
|
|
config DM_UNSTRIPED
|
|
|
|
|
tristate "Unstriped target"
|
|
|
|
|
depends on BLK_DEV_DM
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2017-12-18 17:28:08 +00:00
|
|
|
Unstripes I/O so it is issued solely on a single drive in a HW
|
|
|
|
|
RAID0 or dm-striped target.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config DM_CRYPT
|
|
|
|
|
tristate "Crypt target support"
|
2008-02-08 02:10:32 +00:00
|
|
|
depends on BLK_DEV_DM
|
2020-04-20 13:46:59 +00:00
|
|
|
depends on (ENCRYPTED_KEYS || ENCRYPTED_KEYS=n)
|
2005-04-16 22:20:36 +00:00
|
|
|
select CRYPTO
|
2006-12-09 22:50:36 +00:00
|
|
|
select CRYPTO_CBC
|
2019-08-19 14:17:37 +00:00
|
|
|
select CRYPTO_ESSIV
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2005-04-16 22:20:36 +00:00
|
|
|
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.
|
|
|
|
|
|
2014-12-15 21:18:43 +00:00
|
|
|
For further information on dm-crypt and userspace tools see:
|
2015-07-05 06:55:44 +00:00
|
|
|
<https://gitlab.com/cryptsetup/cryptsetup/wikis/DMCrypt>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
To compile this code as a module, choose M here: the module will
|
|
|
|
|
be called dm-crypt.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config DM_SNAPSHOT
|
2008-02-08 02:10:32 +00:00
|
|
|
tristate "Snapshot target"
|
|
|
|
|
depends on BLK_DEV_DM
|
2014-01-14 00:12:36 +00:00
|
|
|
select DM_BUFIO
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2019-11-20 13:41:10 +00:00
|
|
|
Allow volume managers to take writable snapshots of a device.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2011-10-31 20:21:18 +00:00
|
|
|
config DM_THIN_PROVISIONING
|
2013-03-01 22:45:46 +00:00
|
|
|
tristate "Thin provisioning target"
|
|
|
|
|
depends on BLK_DEV_DM
|
2011-10-31 20:21:18 +00:00
|
|
|
select DM_PERSISTENT_DATA
|
2012-10-12 20:02:13 +00:00
|
|
|
select DM_BIO_PRISON
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2019-11-20 13:41:10 +00:00
|
|
|
Provides thin provisioning and snapshots that share a data store.
|
2011-10-31 20:21:18 +00:00
|
|
|
|
2013-03-01 22:45:51 +00:00
|
|
|
config DM_CACHE
|
|
|
|
|
tristate "Cache target (EXPERIMENTAL)"
|
|
|
|
|
depends on BLK_DEV_DM
|
|
|
|
|
default n
|
|
|
|
|
select DM_PERSISTENT_DATA
|
|
|
|
|
select DM_BIO_PRISON
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2019-11-20 13:41:10 +00:00
|
|
|
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.
|
2013-03-01 22:45:51 +00:00
|
|
|
|
2015-05-15 14:33:34 +00:00
|
|
|
config DM_CACHE_SMQ
|
|
|
|
|
tristate "Stochastic MQ Cache Policy (EXPERIMENTAL)"
|
|
|
|
|
depends on DM_CACHE
|
|
|
|
|
default y
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2019-11-20 13:41:10 +00:00
|
|
|
A 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.
|
2015-05-15 14:33:34 +00:00
|
|
|
|
2018-03-08 13:25:24 +00:00
|
|
|
config DM_WRITECACHE
|
|
|
|
|
tristate "Writecache target"
|
|
|
|
|
depends on BLK_DEV_DM
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2018-03-08 13:25:24 +00:00
|
|
|
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.
|
|
|
|
|
|
2020-03-09 22:26:38 +00:00
|
|
|
config DM_EBS
|
|
|
|
|
tristate "Emulated block size target (EXPERIMENTAL)"
|
|
|
|
|
depends on BLK_DEV_DM
|
|
|
|
|
select DM_BUFIO
|
|
|
|
|
help
|
|
|
|
|
dm-ebs emulates smaller logical block size on backing devices
|
|
|
|
|
with larger ones (e.g. 512 byte sectors on 4K native disks).
|
|
|
|
|
|
2014-03-03 15:23:15 +00:00
|
|
|
config DM_ERA
|
|
|
|
|
tristate "Era target (EXPERIMENTAL)"
|
|
|
|
|
depends on BLK_DEV_DM
|
|
|
|
|
default n
|
|
|
|
|
select DM_PERSISTENT_DATA
|
|
|
|
|
select DM_BIO_PRISON
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2019-11-20 13:41:10 +00:00
|
|
|
dm-era tracks which parts of a block device are written to
|
|
|
|
|
over time. Useful for maintaining cache coherency when using
|
|
|
|
|
vendor snapshots.
|
2014-03-03 15:23:15 +00:00
|
|
|
|
dm: add clone target
Add the dm-clone target, which allows cloning of arbitrary block
devices.
dm-clone produces a one-to-one copy of an existing, read-only source
device into a writable destination device: It presents a virtual block
device which makes all data appear immediately, and redirects reads and
writes accordingly.
The main use case of dm-clone is to clone a potentially remote,
high-latency, read-only, archival-type block device into a writable,
fast, primary-type device for fast, low-latency I/O. 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.
When the cloning completes, the dm-clone table can be removed altogether
and be replaced, e.g., by a linear table, mapping directly to the
destination device.
For further information and examples of how to use dm-clone, please read
Documentation/admin-guide/device-mapper/dm-clone.rst
Suggested-by: Vangelis Koukis <vkoukis@arrikto.com>
Co-developed-by: Ilias Tsitsimpis <iliastsi@arrikto.com>
Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com>
Signed-off-by: Nikos Tsironis <ntsironis@arrikto.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2019-09-11 14:36:40 +00:00
|
|
|
config DM_CLONE
|
|
|
|
|
tristate "Clone target (EXPERIMENTAL)"
|
|
|
|
|
depends on BLK_DEV_DM
|
|
|
|
|
default n
|
|
|
|
|
select DM_PERSISTENT_DATA
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2019-11-20 13:41:10 +00:00
|
|
|
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.
|
dm: add clone target
Add the dm-clone target, which allows cloning of arbitrary block
devices.
dm-clone produces a one-to-one copy of an existing, read-only source
device into a writable destination device: It presents a virtual block
device which makes all data appear immediately, and redirects reads and
writes accordingly.
The main use case of dm-clone is to clone a potentially remote,
high-latency, read-only, archival-type block device into a writable,
fast, primary-type device for fast, low-latency I/O. 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.
When the cloning completes, the dm-clone table can be removed altogether
and be replaced, e.g., by a linear table, mapping directly to the
destination device.
For further information and examples of how to use dm-clone, please read
Documentation/admin-guide/device-mapper/dm-clone.rst
Suggested-by: Vangelis Koukis <vkoukis@arrikto.com>
Co-developed-by: Ilias Tsitsimpis <iliastsi@arrikto.com>
Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com>
Signed-off-by: Nikos Tsironis <ntsironis@arrikto.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2019-09-11 14:36:40 +00:00
|
|
|
|
2019-11-20 13:41:10 +00:00
|
|
|
If unsure, say N.
|
dm: add clone target
Add the dm-clone target, which allows cloning of arbitrary block
devices.
dm-clone produces a one-to-one copy of an existing, read-only source
device into a writable destination device: It presents a virtual block
device which makes all data appear immediately, and redirects reads and
writes accordingly.
The main use case of dm-clone is to clone a potentially remote,
high-latency, read-only, archival-type block device into a writable,
fast, primary-type device for fast, low-latency I/O. 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.
When the cloning completes, the dm-clone table can be removed altogether
and be replaced, e.g., by a linear table, mapping directly to the
destination device.
For further information and examples of how to use dm-clone, please read
Documentation/admin-guide/device-mapper/dm-clone.rst
Suggested-by: Vangelis Koukis <vkoukis@arrikto.com>
Co-developed-by: Ilias Tsitsimpis <iliastsi@arrikto.com>
Signed-off-by: Ilias Tsitsimpis <iliastsi@arrikto.com>
Signed-off-by: Nikos Tsironis <ntsironis@arrikto.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2019-09-11 14:36:40 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config DM_MIRROR
|
2008-02-08 02:10:32 +00:00
|
|
|
tristate "Mirror target"
|
|
|
|
|
depends on BLK_DEV_DM
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2019-11-20 13:41:10 +00:00
|
|
|
Allow volume managers to mirror logical volumes, also
|
|
|
|
|
needed for live data migration tools such as 'pvmove'.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2013-11-08 15:47:12 +00:00
|
|
|
config DM_LOG_USERSPACE
|
|
|
|
|
tristate "Mirror userspace logging"
|
|
|
|
|
depends on DM_MIRROR && NET
|
|
|
|
|
select CONNECTOR
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2013-11-08 15:47:12 +00:00
|
|
|
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.
|
|
|
|
|
|
dm: raid456 basic support
This patch is the skeleton for the DM target that will be
the bridge from DM to MD (initially RAID456 and later RAID1). It
provides a way to use device-mapper interfaces to the MD RAID456
drivers.
As with all device-mapper targets, the nominal public interfaces are the
constructor (CTR) tables and the status outputs (both STATUSTYPE_INFO
and STATUSTYPE_TABLE). The CTR table looks like the following:
1: <s> <l> raid \
2: <raid_type> <#raid_params> <raid_params> \
3: <#raid_devs> <meta_dev1> <dev1> .. <meta_devN> <devN>
Line 1 contains the standard first three arguments to any device-mapper
target - the start, length, and target type fields. The target type in
this case is "raid".
Line 2 contains the arguments that define the particular raid
type/personality/level, the required arguments for that raid type, and
any optional arguments. Possible raid types include: raid4, raid5_la,
raid5_ls, raid5_rs, raid6_zr, raid6_nr, and raid6_nc. (again, raid1 is
planned for the future.) The list of required and optional parameters
is the same for all the current raid types. The required parameters are
positional, while the optional parameters are given as key/value pairs.
The possible parameters are as follows:
<chunk_size> Chunk size in sectors.
[[no]sync] Force/Prevent RAID initialization
[rebuild <idx>] Rebuild the drive indicated by the index
[daemon_sleep <ms>] Time between bitmap daemon work to clear bits
[min_recovery_rate <kB/sec/disk>] Throttle RAID initialization
[max_recovery_rate <kB/sec/disk>] Throttle RAID initialization
[max_write_behind <value>] See '-write-behind=' (man mdadm)
[stripe_cache <sectors>] Stripe cache size for higher RAIDs
Line 3 contains the list of devices that compose the array in
metadata/data device pairs. If the metadata is stored separately, a '-'
is given for the metadata device position. If a drive has failed or is
missing at creation time, a '-' can be given for both the metadata and
data drives for a given position.
Examples:
# RAID4 - 4 data drives, 1 parity
# No metadata devices specified to hold superblock/bitmap info
# Chunk size of 1MiB
# (Lines separated for easy reading)
0 1960893648 raid \
raid4 1 2048 \
5 - 8:17 - 8:33 - 8:49 - 8:65 - 8:81
# RAID4 - 4 data drives, 1 parity (no metadata devices)
# Chunk size of 1MiB, force RAID initialization,
# min recovery rate at 20 kiB/sec/disk
0 1960893648 raid \
raid4 4 2048 min_recovery_rate 20 sync\
5 - 8:17 - 8:33 - 8:49 - 8:65 - 8:81
Performing a 'dmsetup table' should display the CTR table used to
construct the mapping (with possible reordering of optional
parameters).
Performing a 'dmsetup status' will yield information on the state and
health of the array. The output is as follows:
1: <s> <l> raid \
2: <raid_type> <#devices> <1 health char for each dev> <resync_ratio>
Line 1 is standard DM output. Line 2 is best shown by example:
0 1960893648 raid raid4 5 AAAAA 2/490221568
Here we can see the RAID type is raid4, there are 5 devices - all of
which are 'A'live, and the array is 2/490221568 complete with recovery.
Cc: linux-raid@vger.kernel.org
Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: Jonathan Brassow <jbrassow@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Alasdair G Kergon <agk@redhat.com>
2011-01-13 20:00:02 +00:00
|
|
|
config DM_RAID
|
2012-08-01 22:35:43 +00:00
|
|
|
tristate "RAID 1/4/5/6/10 target"
|
2012-03-28 17:41:24 +00:00
|
|
|
depends on BLK_DEV_DM
|
2017-03-28 16:53:39 +00:00
|
|
|
select MD_RAID0
|
2011-08-02 11:32:07 +00:00
|
|
|
select MD_RAID1
|
2012-08-01 22:35:43 +00:00
|
|
|
select MD_RAID10
|
dm: raid456 basic support
This patch is the skeleton for the DM target that will be
the bridge from DM to MD (initially RAID456 and later RAID1). It
provides a way to use device-mapper interfaces to the MD RAID456
drivers.
As with all device-mapper targets, the nominal public interfaces are the
constructor (CTR) tables and the status outputs (both STATUSTYPE_INFO
and STATUSTYPE_TABLE). The CTR table looks like the following:
1: <s> <l> raid \
2: <raid_type> <#raid_params> <raid_params> \
3: <#raid_devs> <meta_dev1> <dev1> .. <meta_devN> <devN>
Line 1 contains the standard first three arguments to any device-mapper
target - the start, length, and target type fields. The target type in
this case is "raid".
Line 2 contains the arguments that define the particular raid
type/personality/level, the required arguments for that raid type, and
any optional arguments. Possible raid types include: raid4, raid5_la,
raid5_ls, raid5_rs, raid6_zr, raid6_nr, and raid6_nc. (again, raid1 is
planned for the future.) The list of required and optional parameters
is the same for all the current raid types. The required parameters are
positional, while the optional parameters are given as key/value pairs.
The possible parameters are as follows:
<chunk_size> Chunk size in sectors.
[[no]sync] Force/Prevent RAID initialization
[rebuild <idx>] Rebuild the drive indicated by the index
[daemon_sleep <ms>] Time between bitmap daemon work to clear bits
[min_recovery_rate <kB/sec/disk>] Throttle RAID initialization
[max_recovery_rate <kB/sec/disk>] Throttle RAID initialization
[max_write_behind <value>] See '-write-behind=' (man mdadm)
[stripe_cache <sectors>] Stripe cache size for higher RAIDs
Line 3 contains the list of devices that compose the array in
metadata/data device pairs. If the metadata is stored separately, a '-'
is given for the metadata device position. If a drive has failed or is
missing at creation time, a '-' can be given for both the metadata and
data drives for a given position.
Examples:
# RAID4 - 4 data drives, 1 parity
# No metadata devices specified to hold superblock/bitmap info
# Chunk size of 1MiB
# (Lines separated for easy reading)
0 1960893648 raid \
raid4 1 2048 \
5 - 8:17 - 8:33 - 8:49 - 8:65 - 8:81
# RAID4 - 4 data drives, 1 parity (no metadata devices)
# Chunk size of 1MiB, force RAID initialization,
# min recovery rate at 20 kiB/sec/disk
0 1960893648 raid \
raid4 4 2048 min_recovery_rate 20 sync\
5 - 8:17 - 8:33 - 8:49 - 8:65 - 8:81
Performing a 'dmsetup table' should display the CTR table used to
construct the mapping (with possible reordering of optional
parameters).
Performing a 'dmsetup status' will yield information on the state and
health of the array. The output is as follows:
1: <s> <l> raid \
2: <raid_type> <#devices> <1 health char for each dev> <resync_ratio>
Line 1 is standard DM output. Line 2 is best shown by example:
0 1960893648 raid raid4 5 AAAAA 2/490221568
Here we can see the RAID type is raid4, there are 5 devices - all of
which are 'A'live, and the array is 2/490221568 complete with recovery.
Cc: linux-raid@vger.kernel.org
Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: Jonathan Brassow <jbrassow@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Alasdair G Kergon <agk@redhat.com>
2011-01-13 20:00:02 +00:00
|
|
|
select MD_RAID456
|
|
|
|
|
select BLK_DEV_MD
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2012-08-01 22:35:43 +00:00
|
|
|
A dm target that supports RAID1, RAID10, RAID4, RAID5 and RAID6 mappings
|
dm: raid456 basic support
This patch is the skeleton for the DM target that will be
the bridge from DM to MD (initially RAID456 and later RAID1). It
provides a way to use device-mapper interfaces to the MD RAID456
drivers.
As with all device-mapper targets, the nominal public interfaces are the
constructor (CTR) tables and the status outputs (both STATUSTYPE_INFO
and STATUSTYPE_TABLE). The CTR table looks like the following:
1: <s> <l> raid \
2: <raid_type> <#raid_params> <raid_params> \
3: <#raid_devs> <meta_dev1> <dev1> .. <meta_devN> <devN>
Line 1 contains the standard first three arguments to any device-mapper
target - the start, length, and target type fields. The target type in
this case is "raid".
Line 2 contains the arguments that define the particular raid
type/personality/level, the required arguments for that raid type, and
any optional arguments. Possible raid types include: raid4, raid5_la,
raid5_ls, raid5_rs, raid6_zr, raid6_nr, and raid6_nc. (again, raid1 is
planned for the future.) The list of required and optional parameters
is the same for all the current raid types. The required parameters are
positional, while the optional parameters are given as key/value pairs.
The possible parameters are as follows:
<chunk_size> Chunk size in sectors.
[[no]sync] Force/Prevent RAID initialization
[rebuild <idx>] Rebuild the drive indicated by the index
[daemon_sleep <ms>] Time between bitmap daemon work to clear bits
[min_recovery_rate <kB/sec/disk>] Throttle RAID initialization
[max_recovery_rate <kB/sec/disk>] Throttle RAID initialization
[max_write_behind <value>] See '-write-behind=' (man mdadm)
[stripe_cache <sectors>] Stripe cache size for higher RAIDs
Line 3 contains the list of devices that compose the array in
metadata/data device pairs. If the metadata is stored separately, a '-'
is given for the metadata device position. If a drive has failed or is
missing at creation time, a '-' can be given for both the metadata and
data drives for a given position.
Examples:
# RAID4 - 4 data drives, 1 parity
# No metadata devices specified to hold superblock/bitmap info
# Chunk size of 1MiB
# (Lines separated for easy reading)
0 1960893648 raid \
raid4 1 2048 \
5 - 8:17 - 8:33 - 8:49 - 8:65 - 8:81
# RAID4 - 4 data drives, 1 parity (no metadata devices)
# Chunk size of 1MiB, force RAID initialization,
# min recovery rate at 20 kiB/sec/disk
0 1960893648 raid \
raid4 4 2048 min_recovery_rate 20 sync\
5 - 8:17 - 8:33 - 8:49 - 8:65 - 8:81
Performing a 'dmsetup table' should display the CTR table used to
construct the mapping (with possible reordering of optional
parameters).
Performing a 'dmsetup status' will yield information on the state and
health of the array. The output is as follows:
1: <s> <l> raid \
2: <raid_type> <#devices> <1 health char for each dev> <resync_ratio>
Line 1 is standard DM output. Line 2 is best shown by example:
0 1960893648 raid raid4 5 AAAAA 2/490221568
Here we can see the RAID type is raid4, there are 5 devices - all of
which are 'A'live, and the array is 2/490221568 complete with recovery.
Cc: linux-raid@vger.kernel.org
Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: Jonathan Brassow <jbrassow@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Alasdair G Kergon <agk@redhat.com>
2011-01-13 20:00:02 +00:00
|
|
|
|
|
|
|
|
A RAID-5 set of N drives with a capacity of C MB per drive provides
|
|
|
|
|
the capacity of C * (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.
|
|
|
|
|
|
|
|
|
|
A RAID-6 set of N drives with a capacity of C MB per drive
|
|
|
|
|
provides the capacity of C * (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.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config DM_ZERO
|
2008-02-08 02:10:32 +00:00
|
|
|
tristate "Zero target"
|
|
|
|
|
depends on BLK_DEV_DM
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2005-04-16 22:20:36 +00:00
|
|
|
A target that discards writes, and returns all zeroes for
|
|
|
|
|
reads. Useful in some recovery situations.
|
|
|
|
|
|
|
|
|
|
config DM_MULTIPATH
|
2008-02-08 02:10:32 +00:00
|
|
|
tristate "Multipath target"
|
|
|
|
|
depends on BLK_DEV_DM
|
2008-05-24 01:16:40 +00:00
|
|
|
# nasty syntax but means make DM_MULTIPATH independent
|
|
|
|
|
# of SCSI_DH if the latter isn't defined but if
|
|
|
|
|
# it is, DM_MULTIPATH must depend on it. We get a build
|
|
|
|
|
# error if SCSI_DH=m and DM_MULTIPATH=y
|
2015-09-09 16:04:18 +00:00
|
|
|
depends on !SCSI_DH || SCSI
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2005-04-16 22:20:36 +00:00
|
|
|
Allow volume managers to support multipath hardware.
|
|
|
|
|
|
2009-06-22 09:12:27 +00:00
|
|
|
config DM_MULTIPATH_QL
|
|
|
|
|
tristate "I/O Path Selector based on the number of in-flight I/Os"
|
|
|
|
|
depends on DM_MULTIPATH
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2009-06-22 09:12:27 +00:00
|
|
|
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.
|
|
|
|
|
|
2009-06-22 09:12:28 +00:00
|
|
|
config DM_MULTIPATH_ST
|
|
|
|
|
tristate "I/O Path Selector based on the service time"
|
|
|
|
|
depends on DM_MULTIPATH
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2009-06-22 09:12:28 +00:00
|
|
|
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.
|
|
|
|
|
|
2020-04-30 20:48:30 +00:00
|
|
|
config DM_MULTIPATH_HST
|
|
|
|
|
tristate "I/O Path Selector based on historical service time"
|
|
|
|
|
depends on DM_MULTIPATH
|
|
|
|
|
help
|
|
|
|
|
This path selector is a dynamic load balancer which selects
|
|
|
|
|
the path expected to complete the incoming I/O in the shortest
|
|
|
|
|
time by comparing estimated service time (based on historical
|
|
|
|
|
service time).
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2020-10-23 00:27:50 +00:00
|
|
|
config DM_MULTIPATH_IOA
|
|
|
|
|
tristate "I/O Path Selector based on CPU submission"
|
|
|
|
|
depends on DM_MULTIPATH
|
|
|
|
|
help
|
|
|
|
|
This path selector selects the path based on the CPU the IO is
|
|
|
|
|
executed on and the CPU to path mapping setup at path addition time.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2007-05-09 09:33:06 +00:00
|
|
|
config DM_DELAY
|
2013-03-01 22:45:46 +00:00
|
|
|
tristate "I/O delaying target"
|
|
|
|
|
depends on BLK_DEV_DM
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2007-05-09 09:33:06 +00:00
|
|
|
A target that delays reads and/or writes and can send
|
|
|
|
|
them to different devices. Useful for testing.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
dm: add dust target
Add the dm-dust target, which simulates the behavior of bad sectors
at arbitrary locations, and the ability to enable the emulation of
the read failures at an arbitrary time.
This target behaves similarly to a linear target. At a given time,
the user can send a message to the target to start failing read
requests on specific blocks. When the failure behavior is enabled,
reads of blocks configured "bad" will fail with EIO.
Writes of blocks configured "bad" will result in the following:
1. Remove the block from the "bad block list".
2. Successfully complete the write.
After this point, the block will successfully contain the written
data, and will service reads and writes normally. This emulates the
behavior of a "remapped sector" on a hard disk drive.
dm-dust provides logging of which blocks have been added or removed
to the "bad block list", as well as logging when a block has been
removed from the bad block list. These messages can be used
alongside the messages from the driver using a dm-dust device to
analyze the driver's behavior when a read fails at a given time.
(This logging can be reduced via a "quiet" mode, if desired.)
NOTE: If the block size is larger than 512 bytes, only the first sector
of each "dust block" is detected. Placing a limiting layer above a dust
target, to limit the minimum I/O size to the dust block size, will
ensure proper emulation of the given large block size.
Signed-off-by: Bryan Gurney <bgurney@redhat.com>
Co-developed-by: Joe Shimkus <jshimkus@redhat.com>
Co-developed-by: John Dorminy <jdorminy@redhat.com>
Co-developed-by: John Pittman <jpittman@redhat.com>
Co-developed-by: Thomas Jaskiewicz <tjaskiew@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2019-03-07 20:42:39 +00:00
|
|
|
config DM_DUST
|
|
|
|
|
tristate "Bad sector simulation target"
|
|
|
|
|
depends on BLK_DEV_DM
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
dm: add dust target
Add the dm-dust target, which simulates the behavior of bad sectors
at arbitrary locations, and the ability to enable the emulation of
the read failures at an arbitrary time.
This target behaves similarly to a linear target. At a given time,
the user can send a message to the target to start failing read
requests on specific blocks. When the failure behavior is enabled,
reads of blocks configured "bad" will fail with EIO.
Writes of blocks configured "bad" will result in the following:
1. Remove the block from the "bad block list".
2. Successfully complete the write.
After this point, the block will successfully contain the written
data, and will service reads and writes normally. This emulates the
behavior of a "remapped sector" on a hard disk drive.
dm-dust provides logging of which blocks have been added or removed
to the "bad block list", as well as logging when a block has been
removed from the bad block list. These messages can be used
alongside the messages from the driver using a dm-dust device to
analyze the driver's behavior when a read fails at a given time.
(This logging can be reduced via a "quiet" mode, if desired.)
NOTE: If the block size is larger than 512 bytes, only the first sector
of each "dust block" is detected. Placing a limiting layer above a dust
target, to limit the minimum I/O size to the dust block size, will
ensure proper emulation of the given large block size.
Signed-off-by: Bryan Gurney <bgurney@redhat.com>
Co-developed-by: Joe Shimkus <jshimkus@redhat.com>
Co-developed-by: John Dorminy <jdorminy@redhat.com>
Co-developed-by: John Pittman <jpittman@redhat.com>
Co-developed-by: Thomas Jaskiewicz <tjaskiew@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2019-03-07 20:42:39 +00:00
|
|
|
A target that simulates bad sector behavior.
|
|
|
|
|
Useful for testing.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
dm: add support to directly boot to a mapped device
Add a "create" module parameter, which allows device-mapper targets to
be configured at boot time. This enables early use of DM targets in the
boot process (as the root device or otherwise) without the need of an
initramfs.
The syntax used in the boot param is based on the concise format from
the dmsetup tool to follow the rule of least surprise:
dmsetup table --concise /dev/mapper/lroot
Which is:
dm-mod.create=<name>,<uuid>,<minor>,<flags>,<table>[,<table>+][;<name>,<uuid>,<minor>,<flags>,<table>[,<table>+]+]
Where,
<name> ::= The device name.
<uuid> ::= xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx | ""
<minor> ::= The device minor number | ""
<flags> ::= "ro" | "rw"
<table> ::= <start_sector> <num_sectors> <target_type> <target_args>
<target_type> ::= "verity" | "linear" | ...
For example, the following could be added in the boot parameters:
dm-mod.create="lroot,,,rw, 0 4096 linear 98:16 0, 4096 4096 linear 98:32 0" root=/dev/dm-0
Only the targets that were tested are allowed and the ones that don't
change any block device when the device is create as read-only. For
example, mirror and cache targets are not allowed. The rationale behind
this is that if the user makes a mistake, choosing the wrong device to
be the mirror or the cache can corrupt data.
The only targets initially allowed are:
* crypt
* delay
* linear
* snapshot-origin
* striped
* verity
Co-developed-by: Will Drewry <wad@chromium.org>
Co-developed-by: Kees Cook <keescook@chromium.org>
Co-developed-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Signed-off-by: Helen Koike <helen.koike@collabora.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2019-02-21 20:33:34 +00:00
|
|
|
config DM_INIT
|
|
|
|
|
bool "DM \"dm-mod.create=\" parameter support"
|
|
|
|
|
depends on BLK_DEV_DM=y
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
dm: add support to directly boot to a mapped device
Add a "create" module parameter, which allows device-mapper targets to
be configured at boot time. This enables early use of DM targets in the
boot process (as the root device or otherwise) without the need of an
initramfs.
The syntax used in the boot param is based on the concise format from
the dmsetup tool to follow the rule of least surprise:
dmsetup table --concise /dev/mapper/lroot
Which is:
dm-mod.create=<name>,<uuid>,<minor>,<flags>,<table>[,<table>+][;<name>,<uuid>,<minor>,<flags>,<table>[,<table>+]+]
Where,
<name> ::= The device name.
<uuid> ::= xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx | ""
<minor> ::= The device minor number | ""
<flags> ::= "ro" | "rw"
<table> ::= <start_sector> <num_sectors> <target_type> <target_args>
<target_type> ::= "verity" | "linear" | ...
For example, the following could be added in the boot parameters:
dm-mod.create="lroot,,,rw, 0 4096 linear 98:16 0, 4096 4096 linear 98:32 0" root=/dev/dm-0
Only the targets that were tested are allowed and the ones that don't
change any block device when the device is create as read-only. For
example, mirror and cache targets are not allowed. The rationale behind
this is that if the user makes a mistake, choosing the wrong device to
be the mirror or the cache can corrupt data.
The only targets initially allowed are:
* crypt
* delay
* linear
* snapshot-origin
* striped
* verity
Co-developed-by: Will Drewry <wad@chromium.org>
Co-developed-by: Kees Cook <keescook@chromium.org>
Co-developed-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Signed-off-by: Helen Koike <helen.koike@collabora.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2019-02-21 20:33:34 +00:00
|
|
|
Enable "dm-mod.create=" parameter to create mapped devices at init time.
|
|
|
|
|
This option is useful to allow mounting rootfs without requiring an
|
|
|
|
|
initramfs.
|
2019-06-18 15:40:23 +00:00
|
|
|
See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
|
dm: add support to directly boot to a mapped device
Add a "create" module parameter, which allows device-mapper targets to
be configured at boot time. This enables early use of DM targets in the
boot process (as the root device or otherwise) without the need of an
initramfs.
The syntax used in the boot param is based on the concise format from
the dmsetup tool to follow the rule of least surprise:
dmsetup table --concise /dev/mapper/lroot
Which is:
dm-mod.create=<name>,<uuid>,<minor>,<flags>,<table>[,<table>+][;<name>,<uuid>,<minor>,<flags>,<table>[,<table>+]+]
Where,
<name> ::= The device name.
<uuid> ::= xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx | ""
<minor> ::= The device minor number | ""
<flags> ::= "ro" | "rw"
<table> ::= <start_sector> <num_sectors> <target_type> <target_args>
<target_type> ::= "verity" | "linear" | ...
For example, the following could be added in the boot parameters:
dm-mod.create="lroot,,,rw, 0 4096 linear 98:16 0, 4096 4096 linear 98:32 0" root=/dev/dm-0
Only the targets that were tested are allowed and the ones that don't
change any block device when the device is create as read-only. For
example, mirror and cache targets are not allowed. The rationale behind
this is that if the user makes a mistake, choosing the wrong device to
be the mirror or the cache can corrupt data.
The only targets initially allowed are:
* crypt
* delay
* linear
* snapshot-origin
* striped
* verity
Co-developed-by: Will Drewry <wad@chromium.org>
Co-developed-by: Kees Cook <keescook@chromium.org>
Co-developed-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Signed-off-by: Helen Koike <helen.koike@collabora.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2019-02-21 20:33:34 +00:00
|
|
|
format.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2007-10-19 21:48:00 +00:00
|
|
|
config DM_UEVENT
|
2012-03-28 17:41:24 +00:00
|
|
|
bool "DM uevents"
|
|
|
|
|
depends on BLK_DEV_DM
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2007-10-19 21:48:00 +00:00
|
|
|
Generate udev events for DM events.
|
|
|
|
|
|
2011-03-24 13:54:24 +00:00
|
|
|
config DM_FLAKEY
|
2013-03-01 22:45:46 +00:00
|
|
|
tristate "Flakey target"
|
|
|
|
|
depends on BLK_DEV_DM
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2019-11-20 13:41:10 +00:00
|
|
|
A target that intermittently fails I/O for debugging purposes.
|
2011-03-24 13:54:24 +00:00
|
|
|
|
2012-03-28 17:43:38 +00:00
|
|
|
config DM_VERITY
|
2013-03-01 22:45:46 +00:00
|
|
|
tristate "Verity target support"
|
|
|
|
|
depends on BLK_DEV_DM
|
2012-03-28 17:43:38 +00:00
|
|
|
select CRYPTO
|
|
|
|
|
select CRYPTO_HASH
|
|
|
|
|
select DM_BUFIO
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2012-03-28 17:43:38 +00:00
|
|
|
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 M here: the module will
|
|
|
|
|
be called dm-verity.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2019-07-18 00:46:15 +00:00
|
|
|
config DM_VERITY_VERIFY_ROOTHASH_SIG
|
|
|
|
|
def_bool n
|
|
|
|
|
bool "Verity data device root hash signature verification support"
|
|
|
|
|
depends on DM_VERITY
|
|
|
|
|
select SYSTEM_DATA_VERIFICATION
|
2020-10-23 17:05:12 +00:00
|
|
|
help
|
2019-07-18 00:46:15 +00:00
|
|
|
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.
|
|
|
|
|
|
2020-10-23 17:05:12 +00:00
|
|
|
By default, rely on the builtin trusted keyring.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
|
|
config DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING
|
|
|
|
|
bool "Verity data device root hash signature verification with secondary keyring"
|
|
|
|
|
depends on DM_VERITY_VERIFY_ROOTHASH_SIG
|
|
|
|
|
depends on SECONDARY_TRUSTED_KEYRING
|
|
|
|
|
help
|
|
|
|
|
Rely on the secondary trusted keyring to verify dm-verity signatures.
|
|
|
|
|
|
2019-07-18 00:46:15 +00:00
|
|
|
If unsure, say N.
|
|
|
|
|
|
2015-12-03 14:26:30 +00:00
|
|
|
config DM_VERITY_FEC
|
|
|
|
|
bool "Verity forward error correction support"
|
|
|
|
|
depends on DM_VERITY
|
|
|
|
|
select REED_SOLOMON
|
|
|
|
|
select REED_SOLOMON_DEC8
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2015-12-03 14:26:30 +00:00
|
|
|
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.
|
|
|
|
|
|
2013-07-10 22:41:19 +00:00
|
|
|
config DM_SWITCH
|
|
|
|
|
tristate "Switch target support (EXPERIMENTAL)"
|
|
|
|
|
depends on BLK_DEV_DM
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2013-07-10 22:41:19 +00:00
|
|
|
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 M here: the module will
|
|
|
|
|
be called dm-switch.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2015-03-20 14:50:37 +00:00
|
|
|
config DM_LOG_WRITES
|
|
|
|
|
tristate "Log writes target support"
|
|
|
|
|
depends on BLK_DEV_DM
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2015-03-20 14:50:37 +00:00
|
|
|
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
|
2015-07-06 13:39:17 +00:00
|
|
|
their fs is writing a consistent file system at all times by allowing
|
2015-03-20 14:50:37 +00:00
|
|
|
them to replay the log in a variety of ways and to check the
|
|
|
|
|
contents.
|
|
|
|
|
|
|
|
|
|
To compile this code as a module, choose M here: the module will
|
|
|
|
|
be called dm-log-writes.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
2017-01-04 19:23:53 +00:00
|
|
|
config DM_INTEGRITY
|
2017-05-04 14:32:07 +00:00
|
|
|
tristate "Integrity target support"
|
2017-01-04 19:23:53 +00:00
|
|
|
depends on BLK_DEV_DM
|
|
|
|
|
select BLK_DEV_INTEGRITY
|
|
|
|
|
select DM_BUFIO
|
|
|
|
|
select CRYPTO
|
2020-12-14 17:18:11 +00:00
|
|
|
select CRYPTO_SKCIPHER
|
2017-01-04 19:23:53 +00:00
|
|
|
select ASYNC_XOR
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2017-05-04 14:32:07 +00:00
|
|
|
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 M here: the module will
|
|
|
|
|
be called dm-integrity.
|
|
|
|
|
|
2017-06-07 06:55:39 +00:00
|
|
|
config DM_ZONED
|
|
|
|
|
tristate "Drive-managed zoned block device target support"
|
|
|
|
|
depends on BLK_DEV_DM
|
|
|
|
|
depends on BLK_DEV_ZONED
|
2021-01-03 21:40:51 +00:00
|
|
|
select CRC32
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2017-06-07 06:55:39 +00:00
|
|
|
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 M here: the module will
|
|
|
|
|
be called dm-zoned.
|
|
|
|
|
|
2017-05-04 14:32:07 +00:00
|
|
|
If unsure, say N.
|
2017-01-04 19:23:53 +00:00
|
|
|
|
2007-07-17 11:06:11 +00:00
|
|
|
endif # MD
|
