Lines Matching +full:target +full:- +full:module
1 # SPDX-License-Identifier: GPL-2.0-only
29 Software RAID mini-HOWTO, available from
44 a several-second delay in the boot time due to various
54 use the so-called linear mode, i.e. it will combine the hard disk
57 To compile this as a module, choose M here: the module
63 tristate "RAID-0 (striping) mode"
67 use the so-called raid0 mode, i.e. it will combine the hard disk
73 Software-RAID mini-HOWTO, available from
77 To compile this as a module, choose M here: the module
83 tristate "RAID-1 (mirroring) mode"
86 A RAID-1 set consists of several disk drives which are exact copies
91 of a single drive, and the set protects against a failure of (N - 1)
95 Software-RAID mini-HOWTO, available from
99 If you want to use such a RAID-1 set, say Y. To compile this code
100 as a module, choose M here: the module will be called raid1.
105 tristate "RAID-10 (mirrored striping) mode"
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
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"
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
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
155 compile this code as a module, choose M here: the module
164 MD_MULTIPATH provides a simple multi-path personality for use
172 tristate "Faulty test module for MD"
175 The "faulty" module allows for a block device that occasionally returns
207 Device-mapper is a low level volume manager. It works by allowing
214 To compile this as a module, choose M here: the module will be
215 called dm-mod.
223 Enable this for messages that may help debug device-mapper problems.
232 as a cache, holding recently-read blocks in memory and performing
257 Some bio locking schemes used by other device-mapper targets
260 source "drivers/md/persistent-data/Kconfig"
263 tristate "Unstriped target"
267 RAID0 or dm-striped target.
270 tristate "Crypt target support"
277 This device-mapper target allows you to create a device that
281 For further information on dm-crypt and userspace tools see:
284 To compile this code as a module, choose M here: the module will
285 be called dm-crypt.
290 tristate "Default-key target support"
293 # dm-default-key doesn't require -o inlinecrypt, but it does currently
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
311 tristate "Snapshot target"
318 tristate "Thin provisioning target"
326 tristate "Cache target (EXPERIMENTAL)"
332 dm-cache attempts to improve performance of a block device by
351 tristate "Writecache target"
354 The writecache target caches writes on persistent memory or SSD.
358 The writecache target doesn't cache reads because reads are supposed
362 tristate "Emulated block size target (EXPERIMENTAL)"
366 dm-ebs emulates smaller logical block size on backing devices
370 tristate "Era target (EXPERIMENTAL)"
376 dm-era tracks which parts of a block device are written to
381 tristate "Clone target (EXPERIMENTAL)"
386 dm-clone produces a one-to-one copy of an existing, read-only source
395 tristate "Mirror target"
406 The userspace logging module provides a mechanism for
407 relaying the dm-dirty-log API to userspace. Log designs
413 tristate "RAID 1/4/5/6/10 target"
421 A dm target that supports RAID1, RAID10, RAID4, RAID5 and RAID6 mappings
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
440 tristate "Zero target"
443 A target that discards writes, and returns all zeroes for
447 tristate "Multipath target"
458 tristate "I/O Path Selector based on the number of in-flight I/Os"
462 the path with the least number of in-flight I/Os.
488 tristate "I/O delaying target"
491 A target that delays reads and/or writes and can send
497 tristate "Bad sector simulation target"
500 A target that simulates bad sector behavior.
506 bool "DM \"dm-mod.create=\" parameter support"
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="..."
524 tristate "Flakey target"
527 A target that intermittently fails I/O for debugging purposes.
530 tristate "Verity target support"
536 This device-mapper target creates a read-only device that
538 a pre-generated tree of cryptographic checksums stored on a second
544 To compile this code as a module, choose M here: the module will
545 be called 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
567 Add forward error correction support to dm-verity. This option
568 makes it possible to use pre-generated error correction data to
574 tristate "Switch target support (EXPERIMENTAL)"
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.
580 by sending the target a message.
582 To compile this code as a module, choose M here: the module will
583 be called dm-switch.
588 tristate "Log writes target support"
591 This device-mapper target takes two devices, one device to use
598 To compile this code as a module, choose M here: the module will
599 be called dm-log-writes.
604 tristate "Integrity target support"
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
620 To compile this code as a module, choose M here: the module will
621 be called dm-integrity.
624 tristate "Drive-managed zoned block device target support"
629 This device-mapper target takes a host-managed or host-aware zoned
631 device (drive-managed zoned block device) without any write
638 To compile this code as a module, choose M here: the module will
639 be called dm-zoned.
648 This device-mapper target takes a device and keeps a log of all
651 or committed by simply replacing the target.
660 This device-mapper target allows a userspace daemon to provide the
662 <file:Documentation/block/dm-user.rst> for more information.
664 To compile this code as a module, choose M here: the module will be
665 called dm-user.