Lines Matching +full:target +full:- +full:module
1 # SPDX-License-Identifier: GPL-2.0-only
20 # after relevant mdadm enhancements - to make "names=yes"
21 # the default - are widely available.
34 Software RAID mini-HOWTO, available from
49 a several-second delay in the boot time due to various
69 use the so-called linear mode, i.e. it will combine the hard disk
72 To compile this as a module, choose M here: the module
78 tristate "RAID-0 (striping) mode"
82 use the so-called raid0 mode, i.e. it will combine the hard disk
88 Software-RAID mini-HOWTO, available from
92 To compile this as a module, choose M here: the module
98 tristate "RAID-1 (mirroring) mode"
101 A RAID-1 set consists of several disk drives which are exact copies
106 of a single drive, and the set protects against a failure of (N - 1)
110 Software-RAID mini-HOWTO, available from
114 If you want to use such a RAID-1 set, say Y. To compile this code
115 as a module, choose M here: the module will be called raid1.
120 tristate "RAID-10 (mirrored striping) mode"
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
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"
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
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
170 compile this code as a module, choose M here: the module
203 Device-mapper is a low level volume manager. It works by allowing
210 To compile this as a module, choose M here: the module will be
211 called dm-mod.
219 Enable this for messages that may help debug device-mapper problems.
228 as a cache, holding recently-read blocks in memory and performing
253 Some bio locking schemes used by other device-mapper targets
256 source "drivers/md/persistent-data/Kconfig"
259 tristate "Unstriped target"
263 RAID0 or dm-striped target.
266 tristate "Crypt target support"
275 This device-mapper target allows you to create a device that
279 For further information on dm-crypt and userspace tools see:
282 To compile this code as a module, choose M here: the module will
283 be called dm-crypt.
288 tristate "Snapshot target"
295 tristate "Thin provisioning target"
303 tristate "Cache target (EXPERIMENTAL)"
309 dm-cache attempts to improve performance of a block device by
328 tristate "Writecache target"
331 The writecache target caches writes on persistent memory or SSD.
335 The writecache target doesn't cache reads because reads are supposed
339 tristate "Emulated block size target (EXPERIMENTAL)"
343 dm-ebs emulates smaller logical block size on backing devices
347 tristate "Era target (EXPERIMENTAL)"
353 dm-era tracks which parts of a block device are written to
358 tristate "Clone target (EXPERIMENTAL)"
363 dm-clone produces a one-to-one copy of an existing, read-only source
372 tristate "Mirror target"
383 The userspace logging module provides a mechanism for
384 relaying the dm-dirty-log API to userspace. Log designs
390 tristate "RAID 1/4/5/6/10 target"
398 A dm target that supports RAID1, RAID10, RAID4, RAID5 and RAID6 mappings
400 A RAID-5 set of N drives with a capacity of C MB per drive provides
401 the capacity of C * (N - 1) MB, and protects against a failure
402 of a single drive. For a given sector (row) number, (N - 1) drives
404 For a RAID-4 set, the parity blocks are present on a single drive,
405 while a RAID-5 set distributes the parity across the drives in one
408 A RAID-6 set of N drives with a capacity of C MB per drive
409 provides the capacity of C * (N - 2) MB, and protects
411 (row) number, (N - 2) drives contain data sectors, and two
413 RAID-5, RAID-6 distributes the syndromes across the drives
417 tristate "Zero target"
420 A target that discards writes, and returns all zeroes for
424 tristate "Multipath target"
435 tristate "I/O Path Selector based on the number of in-flight I/Os"
439 the path with the least number of in-flight I/Os.
474 tristate "I/O delaying target"
477 A target that delays reads and/or writes and can send
483 tristate "Bad sector simulation target"
486 A target that simulates bad sector behavior.
492 bool "DM \"dm-mod.create=\" parameter support"
495 Enable "dm-mod.create=" parameter to create mapped devices at init time.
498 See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
510 tristate "Flakey target"
513 A target that intermittently fails I/O for debugging purposes.
516 tristate "Verity target support"
522 This device-mapper target creates a read-only device that
524 a pre-generated tree of cryptographic checksums stored on a second
530 To compile this code as a module, choose M here: the module will
531 be called dm-verity.
540 Add ability for dm-verity device to be validated if the
541 pre-generated tree of cryptographic checksums passed has a pkcs#7
553 Rely on the secondary trusted keyring to verify dm-verity signatures.
563 Rely also on the platform keyring to verify dm-verity signatures.
573 Add forward error correction support to dm-verity. This option
574 makes it possible to use pre-generated error correction data to
580 tristate "Switch target support (EXPERIMENTAL)"
583 This device-mapper target creates a device that supports an arbitrary
584 mapping of fixed-size regions of I/O across a fixed set of paths.
586 by sending the target a message.
588 To compile this code as a module, choose M here: the module will
589 be called dm-switch.
594 tristate "Log writes target support"
597 This device-mapper target takes two devices, one device to use
604 To compile this code as a module, choose M here: the module will
605 be called dm-log-writes.
610 tristate "Integrity target support"
619 This device-mapper target emulates a block device that has
620 additional per-sector tags that can be used for storing
623 This integrity target is used with the dm-crypt target to
627 To compile this code as a module, choose M here: the module will
628 be called dm-integrity.
631 tristate "Drive-managed zoned block device target support"
636 This device-mapper target takes a host-managed or host-aware zoned
638 device (drive-managed zoned block device) without any write
645 To compile this code as a module, choose M here: the module will
646 be called dm-zoned.
655 Generate audit events for device-mapper.
658 particular device-mapper targets, especially the integrity target.
660 source "drivers/md/dm-vdo/Kconfig"