drivers/md/Kconfig

   1 #
   2 # Block device driver configuration
   3 #
   4
   5 menuconfig MD
   6         bool "Multiple devices driver support (RAID and LVM)"
   7         depends on BLOCK
   8         help
   9           Support multiple physical spindles through a single logical device.
  10           Required for RAID and logical volume management.
  11
  12 if MD
  13
  14 config BLK_DEV_MD
  15         tristate "RAID support"
  16         ---help---
  17           This driver lets you combine several hard disk partitions into one
  18           logical block device. This can be used to simply append one
  19           partition to another one or to combine several redundant hard disks
  20           into a RAID1/4/5 device so as to provide protection against hard
  21           disk failures. This is called "Software RAID" since the combining of
  22           the partitions is done by the kernel. "Hardware RAID" means that the
  23           combining is done by a dedicated controller; if you have such a
  24           controller, you do not need to say Y here.
  25
  26           More information about Software RAID on Linux is contained in the
  27           Software RAID mini-HOWTO, available from
  28           <http://www.tldp.org/docs.html#howto>. There you will also learn
  29           where to get the supporting user space utilities raidtools.
  30
  31           If unsure, say N.
  32
  33 config MD_AUTODETECT
  34         bool "Autodetect RAID arrays during kernel boot"
  35         depends on BLK_DEV_MD=y
  36         default y
  37         ---help---
  38           If you say Y here, then the kernel will try to autodetect raid
  39           arrays as part of its boot process.
  40
  41           If you don't use raid and say Y, this autodetection can cause
  42           a several-second delay in the boot time due to various
  43           synchronisation steps that are part of this step.
  44
  45           If unsure, say Y.
  46
  47 config MD_LINEAR
  48         tristate "Linear (append) mode"
  49         depends on BLK_DEV_MD
  50         ---help---
  51           If you say Y here, then your multiple devices driver will be able to
  52           use the so-called linear mode, i.e. it will combine the hard disk
  53           partitions by simply appending one to the other.
  54
  55           To compile this as a module, choose M here: the module
  56           will be called linear.
  57
  58           If unsure, say Y.
  59
  60 config MD_RAID0
  61         tristate "RAID-0 (striping) mode"
  62         depends on BLK_DEV_MD
  63         ---help---
  64           If you say Y here, then your multiple devices driver will be able to
  65           use the so-called raid0 mode, i.e. it will combine the hard disk
  66           partitions into one logical device in such a fashion as to fill them
  67           up evenly, one chunk here and one chunk there. This will increase
  68           the throughput rate if the partitions reside on distinct disks.
  69
  70           Information about Software RAID on Linux is contained in the
  71           Software-RAID mini-HOWTO, available from
  72           <http://www.tldp.org/docs.html#howto>. There you will also
  73           learn where to get the supporting user space utilities raidtools.
  74
  75           To compile this as a module, choose M here: the module
  76           will be called raid0.
  77
  78           If unsure, say Y.
  79
  80 config MD_RAID1
  81         tristate "RAID-1 (mirroring) mode"
  82         depends on BLK_DEV_MD
  83         ---help---
  84           A RAID-1 set consists of several disk drives which are exact copies
  85           of each other.  In the event of a mirror failure, the RAID driver
  86           will continue to use the operational mirrors in the set, providing
  87           an error free MD (multiple device) to the higher levels of the
  88           kernel.  In a set with N drives, the available space is the capacity
  89           of a single drive, and the set protects against a failure of (N - 1)
  90           drives.
  91
  92           Information about Software RAID on Linux is contained in the
  93           Software-RAID mini-HOWTO, available from
  94           <http://www.tldp.org/docs.html#howto>.  There you will also
  95           learn where to get the supporting user space utilities raidtools.
  96
  97           If you want to use such a RAID-1 set, say Y.  To compile this code
  98           as a module, choose M here: the module will be called raid1.
  99
 100           If unsure, say Y.
 101
 102 config MD_RAID10
 103         tristate "RAID-10 (mirrored striping) mode"
 104         depends on BLK_DEV_MD
 105         ---help---
 106           RAID-10 provides a combination of striping (RAID-0) and
 107           mirroring (RAID-1) with easier configuration and more flexible
 108           layout.
 109           Unlike RAID-0, but like RAID-1, RAID-10 requires all devices to
 110           be the same size (or at least, only as much as the smallest device
 111           will be used).
 112           RAID-10 provides a variety of layouts that provide different levels
 113           of redundancy and performance.
 114
 115           RAID-10 requires mdadm-1.7.0 or later, available at:
 116
 117           ftp://ftp.kernel.org/pub/linux/utils/raid/mdadm/
 118
 119           If unsure, say Y.
 120
 121 config MD_RAID456
 122         tristate "RAID-4/RAID-5/RAID-6 mode"
 123         depends on BLK_DEV_MD
 124         select RAID6_PQ
 125         select ASYNC_MEMCPY
 126         select ASYNC_XOR
 127         select ASYNC_PQ
 128         select ASYNC_RAID6_RECOV
 129         ---help---
 130           A RAID-5 set of N drives with a capacity of C MB per drive provides
 131           the capacity of C * (N - 1) MB, and protects against a failure
 132           of a single drive. For a given sector (row) number, (N - 1) drives
 133           contain data sectors, and one drive contains the parity protection.
 134           For a RAID-4 set, the parity blocks are present on a single drive,
 135           while a RAID-5 set distributes the parity across the drives in one
 136           of the available parity distribution methods.
 137
 138           A RAID-6 set of N drives with a capacity of C MB per drive
 139           provides the capacity of C * (N - 2) MB, and protects
 140           against a failure of any two drives. For a given sector
 141           (row) number, (N - 2) drives contain data sectors, and two
 142           drives contains two independent redundancy syndromes.  Like
 143           RAID-5, RAID-6 distributes the syndromes across the drives
 144           in one of the available parity distribution methods.
 145
 146           Information about Software RAID on Linux is contained in the
 147           Software-RAID mini-HOWTO, available from
 148           <http://www.tldp.org/docs.html#howto>. There you will also
 149           learn where to get the supporting user space utilities raidtools.
 150
 151           If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y.  To
 152           compile this code as a module, choose M here: the module
 153           will be called raid456.
 154
 155           If unsure, say Y.
 156
 157 config MD_MULTIPATH
 158         tristate "Multipath I/O support"
 159         depends on BLK_DEV_MD
 160         help
 161           MD_MULTIPATH provides a simple multi-path personality for use
 162           the MD framework.  It is not under active development.  New
 163           projects should consider using DM_MULTIPATH which has more
 164           features and more testing.
 165
 166           If unsure, say N.
 167
 168 config MD_FAULTY
 169         tristate "Faulty test module for MD"
 170         depends on BLK_DEV_MD
 171         help
 172           The "faulty" module allows for a block device that occasionally returns
 173           read or write errors.  It is useful for testing.
 174
 175           In unsure, say N.
 176
 177 source "drivers/md/bcache/Kconfig"
 178
 179 config BLK_DEV_DM_BUILTIN
 180         boolean
 181
 182 config BLK_DEV_DM
 183         tristate "Device mapper support"
 184         select BLK_DEV_DM_BUILTIN
 185         ---help---
 186           Device-mapper is a low level volume manager.  It works by allowing
 187           people to specify mappings for ranges of logical sectors.  Various
 188           mapping types are available, in addition people may write their own
 189           modules containing custom mappings if they wish.
 190
 191           Higher level volume managers such as LVM2 use this driver.
 192
 193           To compile this as a module, choose M here: the module will be
 194           called dm-mod.
 195
 196           If unsure, say N.
 197
 198 config DM_DEBUG
 199         boolean "Device mapper debugging support"
 200         depends on BLK_DEV_DM
 201         ---help---
 202           Enable this for messages that may help debug device-mapper problems.
 203
 204           If unsure, say N.
 205
 206 config DM_BUFIO
 207        tristate
 208        depends on BLK_DEV_DM
 209        ---help---
 210          This interface allows you to do buffered I/O on a device and acts
 211          as a cache, holding recently-read blocks in memory and performing
 212          delayed writes.
 213
 214 config DM_BIO_PRISON
 215        tristate
 216        depends on BLK_DEV_DM
 217        ---help---
 218          Some bio locking schemes used by other device-mapper targets
 219          including thin provisioning.
 220
 221 source "drivers/md/persistent-data/Kconfig"
 222
 223 config DM_CRYPT
 224         tristate "Crypt target support"
 225         depends on BLK_DEV_DM
 226         select CRYPTO
 227         select CRYPTO_CBC
 228         ---help---
 229           This device-mapper target allows you to create a device that
 230           transparently encrypts the data on it. You'll need to activate
 231           the ciphers you're going to use in the cryptoapi configuration.
 232
 233           Information on how to use dm-crypt can be found on
 234
 235           <http://www.saout.de/misc/dm-crypt/>
 236
 237           To compile this code as a module, choose M here: the module will
 238           be called dm-crypt.
 239
 240           If unsure, say N.
 241
 242 config DM_SNAPSHOT
 243        tristate "Snapshot target"
 244        depends on BLK_DEV_DM
 245        select DM_BUFIO
 246        ---help---
 247          Allow volume managers to take writable snapshots of a device.
 248
 249 config DM_THIN_PROVISIONING
 250        tristate "Thin provisioning target"
 251        depends on BLK_DEV_DM
 252        select DM_PERSISTENT_DATA
 253        select DM_BIO_PRISON
 254        ---help---
 255          Provides thin provisioning and snapshots that share a data store.
 256
 257 config DM_CACHE
 258        tristate "Cache target (EXPERIMENTAL)"
 259        depends on BLK_DEV_DM
 260        default n
 261        select DM_PERSISTENT_DATA
 262        select DM_BIO_PRISON
 263        ---help---
 264          dm-cache attempts to improve performance of a block device by
 265          moving frequently used data to a smaller, higher performance
 266          device.  Different 'policy' plugins can be used to change the
 267          algorithms used to select which blocks are promoted, demoted,
 268          cleaned etc.  It supports writeback and writethrough modes.
 269
 270 config DM_CACHE_MQ
 271        tristate "MQ Cache Policy (EXPERIMENTAL)"
 272        depends on DM_CACHE
 273        default y
 274        ---help---
 275          A cache policy that uses a multiqueue ordered by recent hit
 276          count to select which blocks should be promoted and demoted.
 277          This is meant to be a general purpose policy.  It prioritises
 278          reads over writes.
 279
 280 config DM_CACHE_CLEANER
 281        tristate "Cleaner Cache Policy (EXPERIMENTAL)"
 282        depends on DM_CACHE
 283        default y
 284        ---help---
 285          A simple cache policy that writes back all data to the
 286          origin.  Used when decommissioning a dm-cache.
 287
 288 config DM_MIRROR
 289        tristate "Mirror target"
 290        depends on BLK_DEV_DM
 291        ---help---
 292          Allow volume managers to mirror logical volumes, also
 293          needed for live data migration tools such as 'pvmove'.
 294
 295 config DM_LOG_USERSPACE
 296         tristate "Mirror userspace logging"
 297         depends on DM_MIRROR && NET
 298         select CONNECTOR
 299         ---help---
 300           The userspace logging module provides a mechanism for
 301           relaying the dm-dirty-log API to userspace.  Log designs
 302           which are more suited to userspace implementation (e.g.
 303           shared storage logs) or experimental logs can be implemented
 304           by leveraging this framework.
 305
 306 config DM_RAID
 307        tristate "RAID 1/4/5/6/10 target"
 308        depends on BLK_DEV_DM
 309        select MD_RAID1
 310        select MD_RAID10
 311        select MD_RAID456
 312        select BLK_DEV_MD
 313        ---help---
 314          A dm target that supports RAID1, RAID10, RAID4, RAID5 and RAID6 mappings
 315
 316          A RAID-5 set of N drives with a capacity of C MB per drive provides
 317          the capacity of C * (N - 1) MB, and protects against a failure
 318          of a single drive. For a given sector (row) number, (N - 1) drives
 319          contain data sectors, and one drive contains the parity protection.
 320          For a RAID-4 set, the parity blocks are present on a single drive,
 321          while a RAID-5 set distributes the parity across the drives in one
 322          of the available parity distribution methods.
 323
 324          A RAID-6 set of N drives with a capacity of C MB per drive
 325          provides the capacity of C * (N - 2) MB, and protects
 326          against a failure of any two drives. For a given sector
 327          (row) number, (N - 2) drives contain data sectors, and two
 328          drives contains two independent redundancy syndromes.  Like
 329          RAID-5, RAID-6 distributes the syndromes across the drives
 330          in one of the available parity distribution methods.
 331
 332 config DM_ZERO
 333         tristate "Zero target"
 334         depends on BLK_DEV_DM
 335         ---help---
 336           A target that discards writes, and returns all zeroes for
 337           reads.  Useful in some recovery situations.
 338
 339 config DM_MULTIPATH
 340         tristate "Multipath target"
 341         depends on BLK_DEV_DM
 342         # nasty syntax but means make DM_MULTIPATH independent
 343         # of SCSI_DH if the latter isn't defined but if
 344         # it is, DM_MULTIPATH must depend on it.  We get a build
 345         # error if SCSI_DH=m and DM_MULTIPATH=y
 346         depends on SCSI_DH || !SCSI_DH
 347         ---help---
 348           Allow volume managers to support multipath hardware.
 349
 350 config DM_MULTIPATH_QL
 351         tristate "I/O Path Selector based on the number of in-flight I/Os"
 352         depends on DM_MULTIPATH
 353         ---help---
 354           This path selector is a dynamic load balancer which selects
 355           the path with the least number of in-flight I/Os.
 356
 357           If unsure, say N.
 358
 359 config DM_MULTIPATH_ST
 360         tristate "I/O Path Selector based on the service time"
 361         depends on DM_MULTIPATH
 362         ---help---
 363           This path selector is a dynamic load balancer which selects
 364           the path expected to complete the incoming I/O in the shortest
 365           time.
 366
 367           If unsure, say N.
 368
 369 config DM_DELAY
 370         tristate "I/O delaying target"
 371         depends on BLK_DEV_DM
 372         ---help---
 373         A target that delays reads and/or writes and can send
 374         them to different devices.  Useful for testing.
 375
 376         If unsure, say N.
 377
 378 config DM_UEVENT
 379         bool "DM uevents"
 380         depends on BLK_DEV_DM
 381         ---help---
 382         Generate udev events for DM events.
 383
 384 config DM_FLAKEY
 385        tristate "Flakey target"
 386        depends on BLK_DEV_DM
 387        ---help---
 388          A target that intermittently fails I/O for debugging purposes.
 389
 390 config DM_VERITY
 391         tristate "Verity target support"
 392         depends on BLK_DEV_DM
 393         select CRYPTO
 394         select CRYPTO_HASH
 395         select DM_BUFIO
 396         ---help---
 397           This device-mapper target creates a read-only device that
 398           transparently validates the data on one underlying device against
 399           a pre-generated tree of cryptographic checksums stored on a second
 400           device.
 401
 402           You'll need to activate the digests you're going to use in the
 403           cryptoapi configuration.
 404
 405           To compile this code as a module, choose M here: the module will
 406           be called dm-verity.
 407
 408           If unsure, say N.
 409
 410 config DM_SWITCH
 411         tristate "Switch target support (EXPERIMENTAL)"
 412         depends on BLK_DEV_DM
 413         ---help---
 414           This device-mapper target creates a device that supports an arbitrary
 415           mapping of fixed-size regions of I/O across a fixed set of paths.
 416           The path used for any specific region can be switched dynamically
 417           by sending the target a message.
 418
 419           To compile this code as a module, choose M here: the module will
 420           be called dm-switch.
 421
 422           If unsure, say N.
 423
 424 endif # MD