Lines Matching +full:on +full:- +full:device
1 # SPDX-License-Identifier: GPL-2.0-only
3 # Block device driver configuration
8 depends on BLOCK
11 Support multiple physical spindles through a single logical device.
21 logical block device. This can be used to simply append one
23 into a RAID1/4/5 device so as to provide protection against hard
29 More information about Software RAID on Linux is contained in the
30 Software RAID mini-HOWTO, available from
38 depends on BLK_DEV_MD=y
45 a several-second delay in the boot time due to various
52 depends on BLK_DEV_MD
55 use the so-called linear mode, i.e. it will combine the hard disk
64 tristate "RAID-0 (striping) mode"
65 depends on BLK_DEV_MD
68 use the so-called raid0 mode, i.e. it will combine the hard disk
69 partitions into one logical device in such a fashion as to fill them
71 the throughput rate if the partitions reside on distinct disks.
73 Information about Software RAID on Linux is contained in the
74 Software-RAID mini-HOWTO, available from
84 tristate "RAID-1 (mirroring) mode"
85 depends on BLK_DEV_MD
87 A RAID-1 set consists of several disk drives which are exact copies
90 an error free MD (multiple device) to the higher levels of the
92 of a single drive, and the set protects against a failure of (N - 1)
95 Information about Software RAID on Linux is contained in the
96 Software-RAID mini-HOWTO, available from
100 If you want to use such a RAID-1 set, say Y. To compile this code
106 tristate "RAID-10 (mirrored striping) mode"
107 depends on BLK_DEV_MD
109 RAID-10 provides a combination of striping (RAID-0) and
110 mirroring (RAID-1) with easier configuration and more flexible
112 Unlike RAID-0, but like RAID-1, RAID-10 requires all devices to
113 be the same size (or at least, only as much as the smallest device
115 RAID-10 provides a variety of layouts that provide different levels
118 RAID-10 requires mdadm-1.7.0 or later, available at:
125 tristate "RAID-4/RAID-5/RAID-6 mode"
126 depends on BLK_DEV_MD
134 A RAID-5 set of N drives with a capacity of C MB per drive provides
135 the capacity of C * (N - 1) MB, and protects against a failure
136 of a single drive. For a given sector (row) number, (N - 1) drives
138 For a RAID-4 set, the parity blocks are present on a single drive,
139 while a RAID-5 set distributes the parity across the drives in one
142 A RAID-6 set of N drives with a capacity of C MB per drive
143 provides the capacity of C * (N - 2) MB, and protects
145 (row) number, (N - 2) drives contain data sectors, and two
147 RAID-5, RAID-6 distributes the syndromes across the drives
150 Information about Software RAID on Linux is contained in the
151 Software-RAID mini-HOWTO, available from
155 If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y. To
163 depends on BLK_DEV_MD
165 MD_MULTIPATH provides a simple multi-path personality for use
174 depends on BLK_DEV_MD
176 The "faulty" module allows for a block device that occasionally returns
184 depends on BLK_DEV_MD
185 depends on DLM
189 synchronization across multiple systems on the cluster, so all
204 tristate "Device mapper support"
207 depends on DAX || DAX=n
209 Device-mapper is a low level volume manager. It works by allowing
217 called dm-mod.
222 bool "Device mapper debugging support"
223 depends on BLK_DEV_DM
225 Enable this for messages that may help debug device-mapper problems.
231 depends on BLK_DEV_DM
233 This interface allows you to do buffered I/O on a device and acts
234 as a cache, holding recently-read blocks in memory and performing
239 depends on DM_BUFIO
247 depends on STACKTRACE_SUPPORT && DM_DEBUG_BLOCK_MANAGER_LOCKING
257 depends on BLK_DEV_DM
259 Some bio locking schemes used by other device-mapper targets
262 source "drivers/md/persistent-data/Kconfig"
266 depends on BLK_DEV_DM
268 Unstripes I/O so it is issued solely on a single drive in a HW
269 RAID0 or dm-striped target.
273 depends on BLK_DEV_DM
274 depends on (ENCRYPTED_KEYS || ENCRYPTED_KEYS=n)
275 depends on (TRUSTED_KEYS || TRUSTED_KEYS=n)
280 This device-mapper target allows you to create a device that
281 transparently encrypts the data on it. You'll need to activate
284 For further information on dm-crypt and userspace tools see:
288 be called dm-crypt.
294 depends on BLK_DEV_DM
297 Allow volume managers to take writable snapshots of a device.
301 depends on BLK_DEV_DM
309 depends on BLK_DEV_DM
314 dm-cache attempts to improve performance of a block device by
316 device. Different 'policy' plugins can be used to change the
322 depends on DM_CACHE
334 depends on BLK_DEV_DM
336 The writecache target caches writes on persistent memory or SSD.
345 depends on BLK_DEV_DM && !HIGHMEM
348 dm-ebs emulates smaller logical block size on backing devices
349 with larger ones (e.g. 512 byte sectors on 4K native disks).
353 depends on BLK_DEV_DM
358 dm-era tracks which parts of a block device are written to
364 depends on BLK_DEV_DM
368 dm-clone produces a one-to-one copy of an existing, read-only source
369 device into a writable destination device. The cloned device is
370 visible/mountable immediately and the copy of the source device to the
371 destination device happens in the background, in parallel with user
378 depends on BLK_DEV_DM
385 depends on DM_MIRROR && NET
389 relaying the dm-dirty-log API to userspace. Log designs
396 depends on BLK_DEV_DM
405 A RAID-5 set of N drives with a capacity of C MB per drive provides
406 the capacity of C * (N - 1) MB, and protects against a failure
407 of a single drive. For a given sector (row) number, (N - 1) drives
409 For a RAID-4 set, the parity blocks are present on a single drive,
410 while a RAID-5 set distributes the parity across the drives in one
413 A RAID-6 set of N drives with a capacity of C MB per drive
414 provides the capacity of C * (N - 2) MB, and protects
416 (row) number, (N - 2) drives contain data sectors, and two
418 RAID-5, RAID-6 distributes the syndromes across the drives
423 depends on BLK_DEV_DM
430 depends on BLK_DEV_DM
433 # it is, DM_MULTIPATH must depend on it. We get a build
435 depends on !SCSI_DH || SCSI
440 tristate "I/O Path Selector based on the number of in-flight I/Os"
441 depends on DM_MULTIPATH
444 the path with the least number of in-flight I/Os.
449 tristate "I/O Path Selector based on the service time"
450 depends on DM_MULTIPATH
459 tristate "I/O Path Selector based on historical service time"
460 depends on DM_MULTIPATH
464 time by comparing estimated service time (based on historical
470 tristate "I/O Path Selector based on CPU submission"
471 depends on DM_MULTIPATH
473 This path selector selects the path based on the CPU the IO is
474 executed on and the CPU to path mapping setup at path addition time.
480 depends on BLK_DEV_DM
489 depends on BLK_DEV_DM
497 bool "DM \"dm-mod.create=\" parameter support"
498 depends on BLK_DEV_DM=y
500 Enable "dm-mod.create=" parameter to create mapped devices at init time.
503 See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
510 depends on BLK_DEV_DM
516 depends on BLK_DEV_DM
522 depends on BLK_DEV_DM
527 This device-mapper target creates a read-only device that
528 transparently validates the data on one underlying device against
529 a pre-generated tree of cryptographic checksums stored on a second
530 device.
536 be called dm-verity.
542 bool "Verity data device root hash signature verification support"
543 depends on DM_VERITY
546 Add ability for dm-verity device to be validated if the
547 pre-generated tree of cryptographic checksums passed has a pkcs#7
550 By default, rely on the builtin trusted keyring.
555 bool "Verity data device root hash signature verification with secondary keyring"
556 depends on DM_VERITY_VERIFY_ROOTHASH_SIG
557 depends on SECONDARY_TRUSTED_KEYRING
559 Rely on the secondary trusted keyring to verify dm-verity signatures.
565 depends on DM_VERITY
569 Add forward error correction support to dm-verity. This option
570 makes it possible to use pre-generated error correction data to
577 depends on BLK_DEV_DM
579 This device-mapper target creates a device that supports an arbitrary
580 mapping of fixed-size regions of I/O across a fixed set of paths.
585 be called dm-switch.
591 depends on BLK_DEV_DM
593 This device-mapper target takes two devices, one device to use
594 normally, one to log all write operations done to the first device.
601 be called dm-log-writes.
607 depends on BLK_DEV_DM
614 This device-mapper target emulates a block device that has
615 additional per-sector tags that can be used for storing
618 This integrity target is used with the dm-crypt target to
623 be called dm-integrity.
626 tristate "Drive-managed zoned block device target support"
627 depends on BLK_DEV_DM
628 depends on BLK_DEV_ZONED
631 This device-mapper target takes a host-managed or host-aware zoned
632 block device and exposes most of its capacity as a regular block
633 device (drive-managed zoned block device) without any write
641 be called dm-zoned.