Lines Matching +full:on +full:- +full:device
2 # Block device driver configuration
7 depends on BLOCK
10 Support multiple physical spindles through a single logical device.
17 ---help---
19 logical block device. This can be used to simply append one
21 into a RAID1/4/5 device so as to provide protection against hard
27 More information about Software RAID on Linux is contained in the
28 Software RAID mini-HOWTO, available from
36 depends on BLK_DEV_MD=y
38 ---help---
43 a several-second delay in the boot time due to various
50 depends on BLK_DEV_MD
51 ---help---
53 use the so-called linear mode, i.e. it will combine the hard disk
62 tristate "RAID-0 (striping) mode"
63 depends on BLK_DEV_MD
64 ---help---
66 use the so-called raid0 mode, i.e. it will combine the hard disk
67 partitions into one logical device in such a fashion as to fill them
69 the throughput rate if the partitions reside on distinct disks.
71 Information about Software RAID on Linux is contained in the
72 Software-RAID mini-HOWTO, available from
82 tristate "RAID-1 (mirroring) mode"
83 depends on BLK_DEV_MD
84 ---help---
85 A RAID-1 set consists of several disk drives which are exact copies
88 an error free MD (multiple device) to the higher levels of the
90 of a single drive, and the set protects against a failure of (N - 1)
93 Information about Software RAID on Linux is contained in the
94 Software-RAID mini-HOWTO, available from
98 If you want to use such a RAID-1 set, say Y. To compile this code
104 tristate "RAID-10 (mirrored striping) mode"
105 depends on BLK_DEV_MD
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
111 be the same size (or at least, only as much as the smallest device
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"
124 depends on BLK_DEV_MD
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
148 Information about Software RAID on Linux is contained in the
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
161 depends on BLK_DEV_MD
163 MD_MULTIPATH provides a simple multi-path personality for use
172 depends on BLK_DEV_MD
174 The "faulty" module allows for a block device that occasionally returns
182 depends on BLK_DEV_MD
183 depends on DLM
185 ---help---
187 synchronization across multiple systems on the cluster, so all
202 tristate "Device mapper support"
204 depends on DAX || DAX=n
205 ---help---
206 Device-mapper is a low level volume manager. It works by allowing
214 called dm-mod.
219 bool "request-based DM: use blk-mq I/O path by default"
220 depends on BLK_DEV_DM
221 ---help---
222 This option enables the blk-mq based I/O path for request-based
230 bool "Device mapper debugging support"
231 depends on BLK_DEV_DM
232 ---help---
233 Enable this for messages that may help debug device-mapper problems.
239 depends on BLK_DEV_DM
240 ---help---
241 This interface allows you to do buffered I/O on a device and acts
242 as a cache, holding recently-read blocks in memory and performing
247 depends on DM_BUFIO
248 ---help---
255 depends on STACKTRACE_SUPPORT && DM_DEBUG_BLOCK_MANAGER_LOCKING
257 ---help---
265 depends on BLK_DEV_DM
266 ---help---
267 Some bio locking schemes used by other device-mapper targets
270 source "drivers/md/persistent-data/Kconfig"
274 depends on BLK_DEV_DM
275 ---help---
276 Unstripes I/O so it is issued solely on a single drive in a HW
277 RAID0 or dm-striped target.
281 depends on BLK_DEV_DM
284 ---help---
285 This device-mapper target allows you to create a device that
286 transparently encrypts the data on it. You'll need to activate
289 For further information on dm-crypt and userspace tools see:
293 be called dm-crypt.
299 depends on BLK_DEV_DM
301 ---help---
302 Allow volume managers to take writable snapshots of a device.
306 depends on BLK_DEV_DM
309 ---help---
314 depends on BLK_DEV_DM
318 ---help---
319 dm-cache attempts to improve performance of a block device by
321 device. Different 'policy' plugins can be used to change the
327 depends on DM_CACHE
329 ---help---
339 depends on BLK_DEV_DM
340 ---help---
341 The writecache target caches writes on persistent memory or SSD.
350 depends on BLK_DEV_DM
354 ---help---
355 dm-era tracks which parts of a block device are written to
361 depends on BLK_DEV_DM
362 ---help---
368 depends on DM_MIRROR && NET
370 ---help---
372 relaying the dm-dirty-log API to userspace. Log designs
379 depends on BLK_DEV_DM
385 ---help---
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
406 depends on BLK_DEV_DM
407 ---help---
413 depends on BLK_DEV_DM
416 # it is, DM_MULTIPATH must depend on it. We get a build
418 depends on !SCSI_DH || SCSI
419 ---help---
423 tristate "I/O Path Selector based on the number of in-flight I/Os"
424 depends on DM_MULTIPATH
425 ---help---
427 the path with the least number of in-flight I/Os.
432 tristate "I/O Path Selector based on the service time"
433 depends on DM_MULTIPATH
434 ---help---
443 depends on BLK_DEV_DM
444 ---help---
452 depends on BLK_DEV_DM
453 ---help---
458 depends on BLK_DEV_DM
459 ---help---
464 depends on BLK_DEV_DM
468 ---help---
469 This device-mapper target creates a read-only device that
470 transparently validates the data on one underlying device against
471 a pre-generated tree of cryptographic checksums stored on a second
472 device.
478 be called dm-verity.
484 depends on 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
496 depends on BLK_DEV_DM
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.
504 be called dm-switch.
510 depends on BLK_DEV_DM
511 ---help---
512 This device-mapper target takes two devices, one device to use
513 normally, one to log all write operations done to the first device.
520 be called dm-log-writes.
526 depends on BLK_DEV_DM
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
541 be called dm-integrity.
544 tristate "Drive-managed zoned block device target support"
545 depends on BLK_DEV_DM
546 depends on BLK_DEV_ZONED
547 ---help---
548 This device-mapper target takes a host-managed or host-aware zoned
549 block device and exposes most of its capacity as a regular block
550 device (drive-managed zoned block device) without any write
558 be called dm-zoned.