Lines Matching +full:target +full:- +full:module
17 ---help---
28 Software RAID mini-HOWTO, available from
38 ---help---
43 a several-second delay in the boot time due to various
51 ---help---
53 use the so-called linear mode, i.e. it will combine the hard disk
56 To compile this as a module, choose M here: the module
62 tristate "RAID-0 (striping) mode"
64 ---help---
66 use the so-called raid0 mode, i.e. it will combine the hard disk
72 Software-RAID mini-HOWTO, available from
76 To compile this as a module, choose M here: the module
82 tristate "RAID-1 (mirroring) mode"
84 ---help---
85 A RAID-1 set consists of several disk drives which are exact copies
90 of a single drive, and the set protects against a failure of (N - 1)
94 Software-RAID mini-HOWTO, available from
98 If you want to use such a RAID-1 set, say Y. To compile this code
99 as a module, choose M here: the module will be called raid1.
104 tristate "RAID-10 (mirrored striping) mode"
106 ---help---
107 RAID-10 provides a combination of striping (RAID-0) and
108 mirroring (RAID-1) with easier configuration and more flexible
110 Unlike RAID-0, but like RAID-1, RAID-10 requires all devices to
113 RAID-10 provides a variety of layouts that provide different levels
116 RAID-10 requires mdadm-1.7.0 or later, available at:
123 tristate "RAID-4/RAID-5/RAID-6 mode"
131 ---help---
132 A RAID-5 set of N drives with a capacity of C MB per drive provides
133 the capacity of C * (N - 1) MB, and protects against a failure
134 of a single drive. For a given sector (row) number, (N - 1) drives
136 For a RAID-4 set, the parity blocks are present on a single drive,
137 while a RAID-5 set distributes the parity across the drives in one
140 A RAID-6 set of N drives with a capacity of C MB per drive
141 provides the capacity of C * (N - 2) MB, and protects
143 (row) number, (N - 2) drives contain data sectors, and two
145 RAID-5, RAID-6 distributes the syndromes across the drives
149 Software-RAID mini-HOWTO, available from
153 If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y. To
154 compile this code as a module, choose M here: the module
163 MD_MULTIPATH provides a simple multi-path personality for use
171 tristate "Faulty test module for MD"
174 The "faulty" module allows for a block device that occasionally returns
185 ---help---
205 ---help---
206 Device-mapper is a low level volume manager. It works by allowing
213 To compile this as a module, choose M here: the module will be
214 called dm-mod.
219 bool "request-based DM: use blk-mq I/O path by default"
221 ---help---
222 This option enables the blk-mq based I/O path for request-based
224 module/boot option defaults to Y, without it to N, but it can
232 ---help---
233 Enable this for messages that may help debug device-mapper problems.
240 ---help---
242 as a cache, holding recently-read blocks in memory and performing
248 ---help---
257 ---help---
266 ---help---
267 Some bio locking schemes used by other device-mapper targets
270 source "drivers/md/persistent-data/Kconfig"
273 tristate "Unstriped target"
275 ---help---
277 RAID0 or dm-striped target.
280 tristate "Crypt target support"
284 ---help---
285 This device-mapper target allows you to create a device that
289 For further information on dm-crypt and userspace tools see:
292 To compile this code as a module, choose M here: the module will
293 be called dm-crypt.
298 tristate "Snapshot target"
301 ---help---
305 tristate "Thin provisioning target"
309 ---help---
313 tristate "Cache target (EXPERIMENTAL)"
318 ---help---
319 dm-cache attempts to improve performance of a block device by
329 ---help---
338 tristate "Writecache target"
340 ---help---
341 The writecache target caches writes on persistent memory or SSD.
345 The writecache target doesn't cache reads because reads are supposed
349 tristate "Era target (EXPERIMENTAL)"
354 ---help---
355 dm-era tracks which parts of a block device are written to
360 tristate "Mirror target"
362 ---help---
370 ---help---
371 The userspace logging module provides a mechanism for
372 relaying the dm-dirty-log API to userspace. Log designs
378 tristate "RAID 1/4/5/6/10 target"
385 ---help---
386 A dm target that supports RAID1, RAID10, RAID4, RAID5 and RAID6 mappings
388 A RAID-5 set of N drives with a capacity of C MB per drive provides
389 the capacity of C * (N - 1) MB, and protects against a failure
390 of a single drive. For a given sector (row) number, (N - 1) drives
392 For a RAID-4 set, the parity blocks are present on a single drive,
393 while a RAID-5 set distributes the parity across the drives in one
396 A RAID-6 set of N drives with a capacity of C MB per drive
397 provides the capacity of C * (N - 2) MB, and protects
399 (row) number, (N - 2) drives contain data sectors, and two
401 RAID-5, RAID-6 distributes the syndromes across the drives
405 tristate "Zero target"
407 ---help---
408 A target that discards writes, and returns all zeroes for
412 tristate "Multipath target"
419 ---help---
423 tristate "I/O Path Selector based on the number of in-flight I/Os"
425 ---help---
427 the path with the least number of in-flight I/Os.
434 ---help---
442 tristate "I/O delaying target"
444 ---help---
445 A target that delays reads and/or writes and can send
453 ---help---
457 tristate "Flakey target"
459 ---help---
460 A target that intermittently fails I/O for debugging purposes.
463 tristate "Verity target support"
468 ---help---
469 This device-mapper target creates a read-only device that
471 a pre-generated tree of cryptographic checksums stored on a second
477 To compile this code as a module, choose M here: the module will
478 be called dm-verity.
487 ---help---
488 Add forward error correction support to dm-verity. This option
489 makes it possible to use pre-generated error correction data to
495 tristate "Switch target support (EXPERIMENTAL)"
497 ---help---
498 This device-mapper target creates a device that supports an arbitrary
499 mapping of fixed-size regions of I/O across a fixed set of paths.
501 by sending the target a message.
503 To compile this code as a module, choose M here: the module will
504 be called dm-switch.
509 tristate "Log writes target support"
511 ---help---
512 This device-mapper target takes two devices, one device to use
519 To compile this code as a module, choose M here: the module will
520 be called dm-log-writes.
525 tristate "Integrity target support"
531 ---help---
532 This device-mapper target emulates a block device that has
533 additional per-sector tags that can be used for storing
536 This integrity target is used with the dm-crypt target to
540 To compile this code as a module, choose M here: the module will
541 be called dm-integrity.
544 tristate "Drive-managed zoned block device target support"
547 ---help---
548 This device-mapper target takes a host-managed or host-aware zoned
550 device (drive-managed zoned block device) without any write
557 To compile this code as a module, choose M here: the module will
558 be called dm-zoned.