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"
208 depends on DAX || DAX=n
210 Device-mapper is a low level volume manager. It works by allowing
218 called dm-mod.
223 bool "Device mapper debugging support"
224 depends on BLK_DEV_DM
226 Enable this for messages that may help debug device-mapper problems.
232 depends on BLK_DEV_DM
234 This interface allows you to do buffered I/O on a device and acts
235 as a cache, holding recently-read blocks in memory and performing
240 depends on DM_BUFIO
248 depends on STACKTRACE_SUPPORT && DM_DEBUG_BLOCK_MANAGER_LOCKING
258 depends on BLK_DEV_DM
260 Some bio locking schemes used by other device-mapper targets
263 source "drivers/md/persistent-data/Kconfig"
267 depends on BLK_DEV_DM
269 Unstripes I/O so it is issued solely on a single drive in a HW
270 RAID0 or dm-striped target.
274 depends on BLK_DEV_DM
275 depends on (ENCRYPTED_KEYS || ENCRYPTED_KEYS=n)
276 depends on (TRUSTED_KEYS || TRUSTED_KEYS=n)
281 This device-mapper target allows you to create a device that
282 transparently encrypts the data on it. You'll need to activate
285 For further information on dm-crypt and userspace tools see:
289 be called dm-crypt.
295 depends on BLK_DEV_DM
298 Allow volume managers to take writable snapshots of a device.
302 depends on BLK_DEV_DM
310 depends on BLK_DEV_DM
315 dm-cache attempts to improve performance of a block device by
317 device. Different 'policy' plugins can be used to change the
323 depends on DM_CACHE
335 depends on BLK_DEV_DM
337 The writecache target caches writes on persistent memory or SSD.
346 depends on BLK_DEV_DM && !HIGHMEM
349 dm-ebs emulates smaller logical block size on backing devices
350 with larger ones (e.g. 512 byte sectors on 4K native disks).
354 depends on BLK_DEV_DM
359 dm-era tracks which parts of a block device are written to
365 depends on BLK_DEV_DM
369 dm-clone produces a one-to-one copy of an existing, read-only source
370 device into a writable destination device. The cloned device is
371 visible/mountable immediately and the copy of the source device to the
372 destination device happens in the background, in parallel with user
379 depends on BLK_DEV_DM
386 depends on DM_MIRROR && NET
390 relaying the dm-dirty-log API to userspace. Log designs
397 depends on BLK_DEV_DM
406 A RAID-5 set of N drives with a capacity of C MB per drive provides
407 the capacity of C * (N - 1) MB, and protects against a failure
408 of a single drive. For a given sector (row) number, (N - 1) drives
410 For a RAID-4 set, the parity blocks are present on a single drive,
411 while a RAID-5 set distributes the parity across the drives in one
414 A RAID-6 set of N drives with a capacity of C MB per drive
415 provides the capacity of C * (N - 2) MB, and protects
417 (row) number, (N - 2) drives contain data sectors, and two
419 RAID-5, RAID-6 distributes the syndromes across the drives
424 depends on BLK_DEV_DM
431 depends on BLK_DEV_DM
434 # it is, DM_MULTIPATH must depend on it. We get a build
436 depends on !SCSI_DH || SCSI
441 tristate "I/O Path Selector based on the number of in-flight I/Os"
442 depends on DM_MULTIPATH
445 the path with the least number of in-flight I/Os.
450 tristate "I/O Path Selector based on the service time"
451 depends on DM_MULTIPATH
460 tristate "I/O Path Selector based on historical service time"
461 depends on DM_MULTIPATH
465 time by comparing estimated service time (based on historical
471 tristate "I/O Path Selector based on CPU submission"
472 depends on DM_MULTIPATH
474 This path selector selects the path based on the CPU the IO is
475 executed on and the CPU to path mapping setup at path addition time.
481 depends on BLK_DEV_DM
490 depends on BLK_DEV_DM
498 bool "DM \"dm-mod.create=\" parameter support"
499 depends on BLK_DEV_DM=y
501 Enable "dm-mod.create=" parameter to create mapped devices at init time.
504 See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
511 depends on BLK_DEV_DM
517 depends on BLK_DEV_DM
523 depends on BLK_DEV_DM
528 This device-mapper target creates a read-only device that
529 transparently validates the data on one underlying device against
530 a pre-generated tree of cryptographic checksums stored on a second
531 device.
537 be called dm-verity.
543 bool "Verity data device root hash signature verification support"
544 depends on DM_VERITY
547 Add ability for dm-verity device to be validated if the
548 pre-generated tree of cryptographic checksums passed has a pkcs#7
551 By default, rely on the builtin trusted keyring.
556 bool "Verity data device root hash signature verification with secondary keyring"
557 depends on DM_VERITY_VERIFY_ROOTHASH_SIG
558 depends on SECONDARY_TRUSTED_KEYRING
560 Rely on the secondary trusted keyring to verify dm-verity signatures.
566 depends on DM_VERITY
570 Add forward error correction support to dm-verity. This option
571 makes it possible to use pre-generated error correction data to
578 depends on BLK_DEV_DM
580 This device-mapper target creates a device that supports an arbitrary
581 mapping of fixed-size regions of I/O across a fixed set of paths.
586 be called dm-switch.
592 depends on BLK_DEV_DM
594 This device-mapper target takes two devices, one device to use
595 normally, one to log all write operations done to the first device.
602 be called dm-log-writes.
608 depends on BLK_DEV_DM
616 This device-mapper target emulates a block device that has
617 additional per-sector tags that can be used for storing
620 This integrity target is used with the dm-crypt target to
625 be called dm-integrity.
628 tristate "Drive-managed zoned block device target support"
629 depends on BLK_DEV_DM
630 depends on BLK_DEV_ZONED
633 This device-mapper target takes a host-managed or host-aware zoned
634 block device and exposes most of its capacity as a regular block
635 device (drive-managed zoned block device) without any write
643 be called dm-zoned.
649 depends on AUDIT
651 Generate audit events for device-mapper.
654 particular device-mapper targets, especially the integrity target.