linux/drivers/md/Kconfig
<<
>>
Prefs
   1#
   2# Block device driver configuration
   3#
   4
   5menuconfig 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
  12if MD
  13
  14config 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
  33config 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
  47config 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
  60config 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
  80config 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
 102config 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
 121config 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
 157config MULTICORE_RAID456
 158        bool "RAID-4/RAID-5/RAID-6 Multicore processing (EXPERIMENTAL)"
 159        depends on MD_RAID456
 160        depends on SMP
 161        depends on EXPERIMENTAL
 162        ---help---
 163          Enable the raid456 module to dispatch per-stripe raid operations to a
 164          thread pool.
 165
 166          If unsure, say N.
 167
 168config MD_MULTIPATH
 169        tristate "Multipath I/O support"
 170        depends on BLK_DEV_MD
 171        help
 172          MD_MULTIPATH provides a simple multi-path personality for use
 173          the MD framework.  It is not under active development.  New
 174          projects should consider using DM_MULTIPATH which has more
 175          features and more testing.
 176
 177          If unsure, say N.
 178
 179config MD_FAULTY
 180        tristate "Faulty test module for MD"
 181        depends on BLK_DEV_MD
 182        help
 183          The "faulty" module allows for a block device that occasionally returns
 184          read or write errors.  It is useful for testing.
 185
 186          In unsure, say N.
 187
 188config BLK_DEV_DM
 189        tristate "Device mapper support"
 190        ---help---
 191          Device-mapper is a low level volume manager.  It works by allowing
 192          people to specify mappings for ranges of logical sectors.  Various
 193          mapping types are available, in addition people may write their own
 194          modules containing custom mappings if they wish.
 195
 196          Higher level volume managers such as LVM2 use this driver.
 197
 198          To compile this as a module, choose M here: the module will be
 199          called dm-mod.
 200
 201          If unsure, say N.
 202
 203config DM_DEBUG
 204        boolean "Device mapper debugging support"
 205        depends on BLK_DEV_DM
 206        ---help---
 207          Enable this for messages that may help debug device-mapper problems.
 208
 209          If unsure, say N.
 210
 211config DM_BUFIO
 212       tristate
 213       depends on BLK_DEV_DM && EXPERIMENTAL
 214       ---help---
 215         This interface allows you to do buffered I/O on a device and acts
 216         as a cache, holding recently-read blocks in memory and performing
 217         delayed writes.
 218
 219config DM_BIO_PRISON
 220       tristate
 221       depends on BLK_DEV_DM && EXPERIMENTAL
 222       ---help---
 223         Some bio locking schemes used by other device-mapper targets
 224         including thin provisioning.
 225
 226source "drivers/md/persistent-data/Kconfig"
 227
 228config DM_CRYPT
 229        tristate "Crypt target support"
 230        depends on BLK_DEV_DM
 231        select CRYPTO
 232        select CRYPTO_CBC
 233        ---help---
 234          This device-mapper target allows you to create a device that
 235          transparently encrypts the data on it. You'll need to activate
 236          the ciphers you're going to use in the cryptoapi configuration.
 237
 238          Information on how to use dm-crypt can be found on
 239
 240          <http://www.saout.de/misc/dm-crypt/>
 241
 242          To compile this code as a module, choose M here: the module will
 243          be called dm-crypt.
 244
 245          If unsure, say N.
 246
 247config DM_SNAPSHOT
 248       tristate "Snapshot target"
 249       depends on BLK_DEV_DM
 250       ---help---
 251         Allow volume managers to take writable snapshots of a device.
 252
 253config DM_THIN_PROVISIONING
 254       tristate "Thin provisioning target (EXPERIMENTAL)"
 255       depends on BLK_DEV_DM && EXPERIMENTAL
 256       select DM_PERSISTENT_DATA
 257       select DM_BIO_PRISON
 258       ---help---
 259         Provides thin provisioning and snapshots that share a data store.
 260
 261config DM_DEBUG_BLOCK_STACK_TRACING
 262        boolean "Keep stack trace of thin provisioning block lock holders"
 263        depends on STACKTRACE_SUPPORT && DM_THIN_PROVISIONING
 264        select STACKTRACE
 265        ---help---
 266          Enable this for messages that may help debug problems with the
 267          block manager locking used by thin provisioning.
 268
 269          If unsure, say N.
 270
 271config DM_MIRROR
 272       tristate "Mirror target"
 273       depends on BLK_DEV_DM
 274       ---help---
 275         Allow volume managers to mirror logical volumes, also
 276         needed for live data migration tools such as 'pvmove'.
 277
 278config DM_RAID
 279       tristate "RAID 1/4/5/6/10 target"
 280       depends on BLK_DEV_DM
 281       select MD_RAID1
 282       select MD_RAID10
 283       select MD_RAID456
 284       select BLK_DEV_MD
 285       ---help---
 286         A dm target that supports RAID1, RAID10, RAID4, RAID5 and RAID6 mappings
 287
 288         A RAID-5 set of N drives with a capacity of C MB per drive provides
 289         the capacity of C * (N - 1) MB, and protects against a failure
 290         of a single drive. For a given sector (row) number, (N - 1) drives
 291         contain data sectors, and one drive contains the parity protection.
 292         For a RAID-4 set, the parity blocks are present on a single drive,
 293         while a RAID-5 set distributes the parity across the drives in one
 294         of the available parity distribution methods.
 295
 296         A RAID-6 set of N drives with a capacity of C MB per drive
 297         provides the capacity of C * (N - 2) MB, and protects
 298         against a failure of any two drives. For a given sector
 299         (row) number, (N - 2) drives contain data sectors, and two
 300         drives contains two independent redundancy syndromes.  Like
 301         RAID-5, RAID-6 distributes the syndromes across the drives
 302         in one of the available parity distribution methods.
 303
 304config DM_LOG_USERSPACE
 305        tristate "Mirror userspace logging (EXPERIMENTAL)"
 306        depends on DM_MIRROR && EXPERIMENTAL && NET
 307        select CONNECTOR
 308        ---help---
 309          The userspace logging module provides a mechanism for
 310          relaying the dm-dirty-log API to userspace.  Log designs
 311          which are more suited to userspace implementation (e.g.
 312          shared storage logs) or experimental logs can be implemented
 313          by leveraging this framework.
 314
 315config DM_ZERO
 316        tristate "Zero target"
 317        depends on BLK_DEV_DM
 318        ---help---
 319          A target that discards writes, and returns all zeroes for
 320          reads.  Useful in some recovery situations.
 321
 322config DM_MULTIPATH
 323        tristate "Multipath target"
 324        depends on BLK_DEV_DM
 325        # nasty syntax but means make DM_MULTIPATH independent
 326        # of SCSI_DH if the latter isn't defined but if
 327        # it is, DM_MULTIPATH must depend on it.  We get a build
 328        # error if SCSI_DH=m and DM_MULTIPATH=y
 329        depends on SCSI_DH || !SCSI_DH
 330        ---help---
 331          Allow volume managers to support multipath hardware.
 332
 333config DM_MULTIPATH_QL
 334        tristate "I/O Path Selector based on the number of in-flight I/Os"
 335        depends on DM_MULTIPATH
 336        ---help---
 337          This path selector is a dynamic load balancer which selects
 338          the path with the least number of in-flight I/Os.
 339
 340          If unsure, say N.
 341
 342config DM_MULTIPATH_ST
 343        tristate "I/O Path Selector based on the service time"
 344        depends on DM_MULTIPATH
 345        ---help---
 346          This path selector is a dynamic load balancer which selects
 347          the path expected to complete the incoming I/O in the shortest
 348          time.
 349
 350          If unsure, say N.
 351
 352config DM_DELAY
 353        tristate "I/O delaying target (EXPERIMENTAL)"
 354        depends on BLK_DEV_DM && EXPERIMENTAL
 355        ---help---
 356        A target that delays reads and/or writes and can send
 357        them to different devices.  Useful for testing.
 358
 359        If unsure, say N.
 360
 361config DM_UEVENT
 362        bool "DM uevents"
 363        depends on BLK_DEV_DM
 364        ---help---
 365        Generate udev events for DM events.
 366
 367config DM_FLAKEY
 368       tristate "Flakey target (EXPERIMENTAL)"
 369       depends on BLK_DEV_DM && EXPERIMENTAL
 370       ---help---
 371         A target that intermittently fails I/O for debugging purposes.
 372
 373config DM_VERITY
 374        tristate "Verity target support (EXPERIMENTAL)"
 375        depends on BLK_DEV_DM && EXPERIMENTAL
 376        select CRYPTO
 377        select CRYPTO_HASH
 378        select DM_BUFIO
 379        ---help---
 380          This device-mapper target creates a read-only device that
 381          transparently validates the data on one underlying device against
 382          a pre-generated tree of cryptographic checksums stored on a second
 383          device.
 384
 385          You'll need to activate the digests you're going to use in the
 386          cryptoapi configuration.
 387
 388          To compile this code as a module, choose M here: the module will
 389          be called dm-verity.
 390
 391          If unsure, say N.
 392
 393endif # MD
 394
lxr.linux.no kindly hosted by Redpill Linpro AS, provider of Linux consulting and operations services since 1995.