Lines Matching +full:on +full:- +full:device
1 # SPDX-License-Identifier: GPL-2.0-only
3 # Block device driver configuration
8 depends on BLOCK
10 Support multiple physical spindles through a single logical device.
20 # after relevant mdadm enhancements - to make "names=yes"
21 # the default - are widely available.
25 logical block device. This can be used to simply append one
27 into a RAID1/4/5 device so as to provide protection against hard
33 More information about Software RAID on Linux is contained in the
34 Software RAID mini-HOWTO, available from
42 depends on BLK_DEV_MD=y
49 a several-second delay in the boot time due to various
58 If you say Y here, support for write intent bitmaps in files on an
61 various kernel APIs and can only work with files on a file system not
62 actually sitting on the MD device.
66 depends on BLK_DEV_MD
69 use the so-called linear mode, i.e. it will combine the hard disk
78 tristate "RAID-0 (striping) mode"
79 depends on BLK_DEV_MD
82 use the so-called raid0 mode, i.e. it will combine the hard disk
83 partitions into one logical device in such a fashion as to fill them
85 the throughput rate if the partitions reside on distinct disks.
87 Information about Software RAID on Linux is contained in the
88 Software-RAID mini-HOWTO, available from
98 tristate "RAID-1 (mirroring) mode"
99 depends on BLK_DEV_MD
101 A RAID-1 set consists of several disk drives which are exact copies
104 an error free MD (multiple device) to the higher levels of the
106 of a single drive, and the set protects against a failure of (N - 1)
109 Information about Software RAID on Linux is contained in the
110 Software-RAID mini-HOWTO, available from
114 If you want to use such a RAID-1 set, say Y. To compile this code
120 tristate "RAID-10 (mirrored striping) mode"
121 depends on BLK_DEV_MD
123 RAID-10 provides a combination of striping (RAID-0) and
124 mirroring (RAID-1) with easier configuration and more flexible
126 Unlike RAID-0, but like RAID-1, RAID-10 requires all devices to
127 be the same size (or at least, only as much as the smallest device
129 RAID-10 provides a variety of layouts that provide different levels
132 RAID-10 requires mdadm-1.7.0 or later, available at:
139 tristate "RAID-4/RAID-5/RAID-6 mode"
140 depends on BLK_DEV_MD
148 A RAID-5 set of N drives with a capacity of C MB per drive provides
149 the capacity of C * (N - 1) MB, and protects against a failure
150 of a single drive. For a given sector (row) number, (N - 1) drives
152 For a RAID-4 set, the parity blocks are present on a single drive,
153 while a RAID-5 set distributes the parity across the drives in one
156 A RAID-6 set of N drives with a capacity of C MB per drive
157 provides the capacity of C * (N - 2) MB, and protects
159 (row) number, (N - 2) drives contain data sectors, and two
161 RAID-5, RAID-6 distributes the syndromes across the drives
164 Information about Software RAID on Linux is contained in the
165 Software-RAID mini-HOWTO, available from
169 If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y. To
177 depends on BLK_DEV_MD
178 depends on DLM
182 synchronization across multiple systems on the cluster, so all
197 tristate "Device mapper support"
201 depends on DAX || DAX=n
203 Device-mapper is a low level volume manager. It works by allowing
211 called dm-mod.
216 bool "Device mapper debugging support"
217 depends on BLK_DEV_DM
219 Enable this for messages that may help debug device-mapper problems.
225 depends on BLK_DEV_DM
227 This interface allows you to do buffered I/O on a device and acts
228 as a cache, holding recently-read blocks in memory and performing
233 depends on DM_BUFIO
241 depends on STACKTRACE_SUPPORT && DM_DEBUG_BLOCK_MANAGER_LOCKING
251 depends on BLK_DEV_DM
253 Some bio locking schemes used by other device-mapper targets
256 source "drivers/md/persistent-data/Kconfig"
260 depends on BLK_DEV_DM
262 Unstripes I/O so it is issued solely on a single drive in a HW
263 RAID0 or dm-striped target.
267 depends on BLK_DEV_DM
268 depends on (ENCRYPTED_KEYS || ENCRYPTED_KEYS=n)
269 depends on (TRUSTED_KEYS || TRUSTED_KEYS=n)
274 This device-mapper target allows you to create a device that
275 transparently encrypts the data on it. You'll need to activate
278 For further information on dm-crypt and userspace tools see:
282 be called dm-crypt.
288 depends on BLK_DEV_DM
291 Allow volume managers to take writable snapshots of a device.
295 depends on BLK_DEV_DM
303 depends on BLK_DEV_DM
308 dm-cache attempts to improve performance of a block device by
310 device. Different 'policy' plugins can be used to change the
316 depends on DM_CACHE
328 depends on BLK_DEV_DM
330 The writecache target caches writes on persistent memory or SSD.
339 depends on BLK_DEV_DM && !HIGHMEM
342 dm-ebs emulates smaller logical block size on backing devices
343 with larger ones (e.g. 512 byte sectors on 4K native disks).
347 depends on BLK_DEV_DM
352 dm-era tracks which parts of a block device are written to
358 depends on BLK_DEV_DM
362 dm-clone produces a one-to-one copy of an existing, read-only source
363 device into a writable destination device. The cloned device is
364 visible/mountable immediately and the copy of the source device to the
365 destination device happens in the background, in parallel with user
372 depends on BLK_DEV_DM
379 depends on DM_MIRROR && NET
383 relaying the dm-dirty-log API to userspace. Log designs
390 depends on BLK_DEV_DM
399 A RAID-5 set of N drives with a capacity of C MB per drive provides
400 the capacity of C * (N - 1) MB, and protects against a failure
401 of a single drive. For a given sector (row) number, (N - 1) drives
403 For a RAID-4 set, the parity blocks are present on a single drive,
404 while a RAID-5 set distributes the parity across the drives in one
407 A RAID-6 set of N drives with a capacity of C MB per drive
408 provides the capacity of C * (N - 2) MB, and protects
410 (row) number, (N - 2) drives contain data sectors, and two
412 RAID-5, RAID-6 distributes the syndromes across the drives
417 depends on BLK_DEV_DM
424 depends on BLK_DEV_DM
427 # it is, DM_MULTIPATH must depend on it. We get a build
429 depends on !SCSI_DH || SCSI
434 tristate "I/O Path Selector based on the number of in-flight I/Os"
435 depends on DM_MULTIPATH
438 the path with the least number of in-flight I/Os.
443 tristate "I/O Path Selector based on the service time"
444 depends on DM_MULTIPATH
453 tristate "I/O Path Selector based on historical service time"
454 depends on DM_MULTIPATH
458 time by comparing estimated service time (based on historical
464 tristate "I/O Path Selector based on CPU submission"
465 depends on DM_MULTIPATH
467 This path selector selects the path based on the CPU the IO is
468 executed on and the CPU to path mapping setup at path addition time.
474 depends on BLK_DEV_DM
483 depends on BLK_DEV_DM
491 bool "DM \"dm-mod.create=\" parameter support"
492 depends on BLK_DEV_DM=y
494 Enable "dm-mod.create=" parameter to create mapped devices at init time.
497 See Documentation/admin-guide/device-mapper/dm-init.rst for dm-mod.create="..."
504 depends on BLK_DEV_DM
510 depends on BLK_DEV_DM
516 depends on BLK_DEV_DM
521 This device-mapper target creates a read-only device that
522 transparently validates the data on one underlying device against
523 a pre-generated tree of cryptographic checksums stored on a second
524 device.
530 be called dm-verity.
535 bool "Verity data device root hash signature verification support"
536 depends on DM_VERITY
539 Add ability for dm-verity device to be validated if the
540 pre-generated tree of cryptographic checksums passed has a pkcs#7
543 By default, rely on the builtin trusted keyring.
548 bool "Verity data device root hash signature verification with secondary keyring"
549 depends on DM_VERITY_VERIFY_ROOTHASH_SIG
550 depends on SECONDARY_TRUSTED_KEYRING
552 Rely on the secondary trusted keyring to verify dm-verity signatures.
557 bool "Verity data device root hash signature verification with platform keyring"
559 depends on DM_VERITY_VERIFY_ROOTHASH_SIG
560 depends on INTEGRITY_PLATFORM_KEYRING
562 Rely also on the platform keyring to verify dm-verity signatures.
568 depends on DM_VERITY
572 Add forward error correction support to dm-verity. This option
573 makes it possible to use pre-generated error correction data to
580 depends on BLK_DEV_DM
582 This device-mapper target creates a device that supports an arbitrary
583 mapping of fixed-size regions of I/O across a fixed set of paths.
588 be called dm-switch.
594 depends on BLK_DEV_DM
596 This device-mapper target takes two devices, one device to use
597 normally, one to log all write operations done to the first device.
604 be called dm-log-writes.
610 depends on BLK_DEV_DM
618 This device-mapper target emulates a block device that has
619 additional per-sector tags that can be used for storing
622 This integrity target is used with the dm-crypt target to
627 be called dm-integrity.
630 tristate "Drive-managed zoned block device target support"
631 depends on BLK_DEV_DM
632 depends on BLK_DEV_ZONED
635 This device-mapper target takes a host-managed or host-aware zoned
636 block device and exposes most of its capacity as a regular block
637 device (drive-managed zoned block device) without any write
645 be called dm-zoned.
651 depends on BLK_DEV_DM
652 depends on AUDIT
654 Generate audit events for device-mapper.
657 particular device-mapper targets, especially the integrity target.
659 source "drivers/md/dm-vdo/Kconfig"