Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | # |
| 2 | # Block device driver configuration |
| 3 | # |
| 4 | |
Jan Engelhardt | afd4403 | 2007-07-17 04:06:11 -0700 | [diff] [blame] | 5 | menuconfig MD |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 6 | bool "Multiple devices driver support (RAID and LVM)" |
Jan Engelhardt | afd4403 | 2007-07-17 04:06:11 -0700 | [diff] [blame] | 7 | depends on BLOCK |
Pranith Kumar | 83fe27e | 2014-12-05 11:24:45 -0500 | [diff] [blame] | 8 | select SRCU |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 9 | help |
| 10 | Support multiple physical spindles through a single logical device. |
| 11 | Required for RAID and logical volume management. |
| 12 | |
Jan Engelhardt | afd4403 | 2007-07-17 04:06:11 -0700 | [diff] [blame] | 13 | if MD |
| 14 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 15 | config BLK_DEV_MD |
| 16 | tristate "RAID support" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 17 | ---help--- |
| 18 | This driver lets you combine several hard disk partitions into one |
| 19 | logical block device. This can be used to simply append one |
| 20 | partition to another one or to combine several redundant hard disks |
| 21 | into a RAID1/4/5 device so as to provide protection against hard |
| 22 | disk failures. This is called "Software RAID" since the combining of |
| 23 | the partitions is done by the kernel. "Hardware RAID" means that the |
| 24 | combining is done by a dedicated controller; if you have such a |
| 25 | controller, you do not need to say Y here. |
| 26 | |
| 27 | More information about Software RAID on Linux is contained in the |
| 28 | Software RAID mini-HOWTO, available from |
| 29 | <http://www.tldp.org/docs.html#howto>. There you will also learn |
| 30 | where to get the supporting user space utilities raidtools. |
| 31 | |
| 32 | If unsure, say N. |
| 33 | |
Arjan van de Ven | a364092 | 2008-09-21 15:44:32 -0700 | [diff] [blame] | 34 | config MD_AUTODETECT |
| 35 | bool "Autodetect RAID arrays during kernel boot" |
Alan Jenkins | ce52aeb | 2008-10-10 16:02:53 +0100 | [diff] [blame] | 36 | depends on BLK_DEV_MD=y |
Arjan van de Ven | a364092 | 2008-09-21 15:44:32 -0700 | [diff] [blame] | 37 | default y |
| 38 | ---help--- |
| 39 | If you say Y here, then the kernel will try to autodetect raid |
| 40 | arrays as part of its boot process. |
| 41 | |
| 42 | If you don't use raid and say Y, this autodetection can cause |
| 43 | a several-second delay in the boot time due to various |
| 44 | synchronisation steps that are part of this step. |
| 45 | |
| 46 | If unsure, say Y. |
| 47 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 48 | config MD_LINEAR |
| 49 | tristate "Linear (append) mode" |
| 50 | depends on BLK_DEV_MD |
| 51 | ---help--- |
| 52 | If you say Y here, then your multiple devices driver will be able to |
| 53 | use the so-called linear mode, i.e. it will combine the hard disk |
| 54 | partitions by simply appending one to the other. |
| 55 | |
| 56 | To compile this as a module, choose M here: the module |
| 57 | will be called linear. |
| 58 | |
| 59 | If unsure, say Y. |
| 60 | |
| 61 | config MD_RAID0 |
| 62 | tristate "RAID-0 (striping) mode" |
| 63 | depends on BLK_DEV_MD |
| 64 | ---help--- |
| 65 | If you say Y here, then your multiple devices driver will be able to |
| 66 | use the so-called raid0 mode, i.e. it will combine the hard disk |
| 67 | partitions into one logical device in such a fashion as to fill them |
| 68 | up evenly, one chunk here and one chunk there. This will increase |
| 69 | the throughput rate if the partitions reside on distinct disks. |
| 70 | |
| 71 | Information about Software RAID on Linux is contained in the |
| 72 | Software-RAID mini-HOWTO, available from |
| 73 | <http://www.tldp.org/docs.html#howto>. There you will also |
| 74 | learn where to get the supporting user space utilities raidtools. |
| 75 | |
| 76 | To compile this as a module, choose M here: the module |
| 77 | will be called raid0. |
| 78 | |
| 79 | If unsure, say Y. |
| 80 | |
| 81 | config MD_RAID1 |
| 82 | tristate "RAID-1 (mirroring) mode" |
| 83 | depends on BLK_DEV_MD |
| 84 | ---help--- |
| 85 | A RAID-1 set consists of several disk drives which are exact copies |
| 86 | of each other. In the event of a mirror failure, the RAID driver |
| 87 | will continue to use the operational mirrors in the set, providing |
| 88 | an error free MD (multiple device) to the higher levels of the |
| 89 | kernel. In a set with N drives, the available space is the capacity |
| 90 | of a single drive, and the set protects against a failure of (N - 1) |
| 91 | drives. |
| 92 | |
| 93 | Information about Software RAID on Linux is contained in the |
| 94 | Software-RAID mini-HOWTO, available from |
| 95 | <http://www.tldp.org/docs.html#howto>. There you will also |
| 96 | learn where to get the supporting user space utilities raidtools. |
| 97 | |
| 98 | If you want to use such a RAID-1 set, say Y. To compile this code |
| 99 | as a module, choose M here: the module will be called raid1. |
| 100 | |
| 101 | If unsure, say Y. |
| 102 | |
| 103 | config MD_RAID10 |
NeilBrown | 08fb730 | 2010-05-03 13:16:56 +1000 | [diff] [blame] | 104 | tristate "RAID-10 (mirrored striping) mode" |
| 105 | depends on BLK_DEV_MD |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 106 | ---help--- |
| 107 | RAID-10 provides a combination of striping (RAID-0) and |
Justin Piszcz | 4d2554d | 2006-06-26 00:27:50 -0700 | [diff] [blame] | 108 | mirroring (RAID-1) with easier configuration and more flexible |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 109 | layout. |
| 110 | Unlike RAID-0, but like RAID-1, RAID-10 requires all devices to |
| 111 | be the same size (or at least, only as much as the smallest device |
| 112 | will be used). |
| 113 | RAID-10 provides a variety of layouts that provide different levels |
| 114 | of redundancy and performance. |
| 115 | |
| 116 | RAID-10 requires mdadm-1.7.0 or later, available at: |
| 117 | |
| 118 | ftp://ftp.kernel.org/pub/linux/utils/raid/mdadm/ |
| 119 | |
| 120 | If unsure, say Y. |
| 121 | |
NeilBrown | 16a53ec | 2006-06-26 00:27:38 -0700 | [diff] [blame] | 122 | config MD_RAID456 |
| 123 | tristate "RAID-4/RAID-5/RAID-6 mode" |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 124 | depends on BLK_DEV_MD |
David Woodhouse | f5e70d0 | 2009-07-13 11:35:12 +0100 | [diff] [blame] | 125 | select RAID6_PQ |
Dan Williams | 9bc89cd | 2007-01-02 11:10:44 -0700 | [diff] [blame] | 126 | select ASYNC_MEMCPY |
| 127 | select ASYNC_XOR |
Dan Williams | ac6b53b | 2009-07-14 13:40:19 -0700 | [diff] [blame] | 128 | select ASYNC_PQ |
| 129 | select ASYNC_RAID6_RECOV |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 130 | ---help--- |
| 131 | A RAID-5 set of N drives with a capacity of C MB per drive provides |
| 132 | the capacity of C * (N - 1) MB, and protects against a failure |
| 133 | of a single drive. For a given sector (row) number, (N - 1) drives |
| 134 | contain data sectors, and one drive contains the parity protection. |
| 135 | For a RAID-4 set, the parity blocks are present on a single drive, |
| 136 | while a RAID-5 set distributes the parity across the drives in one |
| 137 | of the available parity distribution methods. |
| 138 | |
NeilBrown | 16a53ec | 2006-06-26 00:27:38 -0700 | [diff] [blame] | 139 | A RAID-6 set of N drives with a capacity of C MB per drive |
| 140 | provides the capacity of C * (N - 2) MB, and protects |
| 141 | against a failure of any two drives. For a given sector |
| 142 | (row) number, (N - 2) drives contain data sectors, and two |
| 143 | drives contains two independent redundancy syndromes. Like |
| 144 | RAID-5, RAID-6 distributes the syndromes across the drives |
| 145 | in one of the available parity distribution methods. |
| 146 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 147 | Information about Software RAID on Linux is contained in the |
| 148 | Software-RAID mini-HOWTO, available from |
| 149 | <http://www.tldp.org/docs.html#howto>. There you will also |
| 150 | learn where to get the supporting user space utilities raidtools. |
| 151 | |
NeilBrown | 16a53ec | 2006-06-26 00:27:38 -0700 | [diff] [blame] | 152 | If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y. To |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 153 | compile this code as a module, choose M here: the module |
NeilBrown | 16a53ec | 2006-06-26 00:27:38 -0700 | [diff] [blame] | 154 | will be called raid456. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 155 | |
| 156 | If unsure, say Y. |
| 157 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 158 | config MD_MULTIPATH |
| 159 | tristate "Multipath I/O support" |
| 160 | depends on BLK_DEV_MD |
| 161 | help |
NeilBrown | 93bd89a | 2009-12-14 12:49:59 +1100 | [diff] [blame] | 162 | MD_MULTIPATH provides a simple multi-path personality for use |
| 163 | the MD framework. It is not under active development. New |
| 164 | projects should consider using DM_MULTIPATH which has more |
| 165 | features and more testing. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 166 | |
| 167 | If unsure, say N. |
| 168 | |
| 169 | config MD_FAULTY |
| 170 | tristate "Faulty test module for MD" |
| 171 | depends on BLK_DEV_MD |
| 172 | help |
| 173 | The "faulty" module allows for a block device that occasionally returns |
| 174 | read or write errors. It is useful for testing. |
| 175 | |
| 176 | In unsure, say N. |
| 177 | |
Kent Overstreet | cafe563 | 2013-03-23 16:11:31 -0700 | [diff] [blame] | 178 | source "drivers/md/bcache/Kconfig" |
| 179 | |
Mikulas Patocka | 2995fa7 | 2014-01-13 19:37:54 -0500 | [diff] [blame] | 180 | config BLK_DEV_DM_BUILTIN |
Christoph Jaeger | 6341e62 | 2014-12-20 15:41:11 -0500 | [diff] [blame] | 181 | bool |
Mikulas Patocka | 2995fa7 | 2014-01-13 19:37:54 -0500 | [diff] [blame] | 182 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 183 | config BLK_DEV_DM |
| 184 | tristate "Device mapper support" |
Mikulas Patocka | 2995fa7 | 2014-01-13 19:37:54 -0500 | [diff] [blame] | 185 | select BLK_DEV_DM_BUILTIN |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 186 | ---help--- |
| 187 | Device-mapper is a low level volume manager. It works by allowing |
| 188 | people to specify mappings for ranges of logical sectors. Various |
| 189 | mapping types are available, in addition people may write their own |
| 190 | modules containing custom mappings if they wish. |
| 191 | |
| 192 | Higher level volume managers such as LVM2 use this driver. |
| 193 | |
| 194 | To compile this as a module, choose M here: the module will be |
| 195 | called dm-mod. |
| 196 | |
| 197 | If unsure, say N. |
| 198 | |
Bryn Reeves | cc10920 | 2006-10-03 01:15:35 -0700 | [diff] [blame] | 199 | config DM_DEBUG |
Christoph Jaeger | 6341e62 | 2014-12-20 15:41:11 -0500 | [diff] [blame] | 200 | bool "Device mapper debugging support" |
Alasdair G Kergon | 0149e57 | 2008-02-08 02:10:32 +0000 | [diff] [blame] | 201 | depends on BLK_DEV_DM |
Bryn Reeves | cc10920 | 2006-10-03 01:15:35 -0700 | [diff] [blame] | 202 | ---help--- |
| 203 | Enable this for messages that may help debug device-mapper problems. |
| 204 | |
| 205 | If unsure, say N. |
| 206 | |
Mikulas Patocka | 95d402f | 2011-10-31 20:19:09 +0000 | [diff] [blame] | 207 | config DM_BUFIO |
| 208 | tristate |
Alasdair G Kergon | d57916a | 2013-03-01 22:45:46 +0000 | [diff] [blame] | 209 | depends on BLK_DEV_DM |
Mikulas Patocka | 95d402f | 2011-10-31 20:19:09 +0000 | [diff] [blame] | 210 | ---help--- |
| 211 | This interface allows you to do buffered I/O on a device and acts |
| 212 | as a cache, holding recently-read blocks in memory and performing |
| 213 | delayed writes. |
| 214 | |
Mike Snitzer | 4f81a41 | 2012-10-12 21:02:13 +0100 | [diff] [blame] | 215 | config DM_BIO_PRISON |
| 216 | tristate |
Alasdair G Kergon | d57916a | 2013-03-01 22:45:46 +0000 | [diff] [blame] | 217 | depends on BLK_DEV_DM |
Mike Snitzer | 4f81a41 | 2012-10-12 21:02:13 +0100 | [diff] [blame] | 218 | ---help--- |
| 219 | Some bio locking schemes used by other device-mapper targets |
| 220 | including thin provisioning. |
| 221 | |
Joe Thornber | 991d9fa | 2011-10-31 20:21:18 +0000 | [diff] [blame] | 222 | source "drivers/md/persistent-data/Kconfig" |
| 223 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 224 | config DM_CRYPT |
| 225 | tristate "Crypt target support" |
Alasdair G Kergon | 0149e57 | 2008-02-08 02:10:32 +0000 | [diff] [blame] | 226 | depends on BLK_DEV_DM |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 227 | select CRYPTO |
Herbert Xu | 3263263 | 2006-12-10 09:50:36 +1100 | [diff] [blame] | 228 | select CRYPTO_CBC |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 229 | ---help--- |
| 230 | This device-mapper target allows you to create a device that |
| 231 | transparently encrypts the data on it. You'll need to activate |
| 232 | the ciphers you're going to use in the cryptoapi configuration. |
| 233 | |
Loic Pefferkorn | cf35248 | 2014-12-15 22:18:43 +0100 | [diff] [blame] | 234 | For further information on dm-crypt and userspace tools see: |
| 235 | <http://code.google.com/p/cryptsetup/wiki/DMCrypt> |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 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 |
Alasdair G Kergon | 0149e57 | 2008-02-08 02:10:32 +0000 | [diff] [blame] | 243 | tristate "Snapshot target" |
| 244 | depends on BLK_DEV_DM |
Mikulas Patocka | 55494bf | 2014-01-13 19:12:36 -0500 | [diff] [blame] | 245 | select DM_BUFIO |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 246 | ---help--- |
Justin Piszcz | 4d2554d | 2006-06-26 00:27:50 -0700 | [diff] [blame] | 247 | Allow volume managers to take writable snapshots of a device. |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 248 | |
Joe Thornber | 991d9fa | 2011-10-31 20:21:18 +0000 | [diff] [blame] | 249 | config DM_THIN_PROVISIONING |
Alasdair G Kergon | d57916a | 2013-03-01 22:45:46 +0000 | [diff] [blame] | 250 | tristate "Thin provisioning target" |
| 251 | depends on BLK_DEV_DM |
Joe Thornber | 991d9fa | 2011-10-31 20:21:18 +0000 | [diff] [blame] | 252 | select DM_PERSISTENT_DATA |
Mike Snitzer | 4f81a41 | 2012-10-12 21:02:13 +0100 | [diff] [blame] | 253 | select DM_BIO_PRISON |
Joe Thornber | 991d9fa | 2011-10-31 20:21:18 +0000 | [diff] [blame] | 254 | ---help--- |
| 255 | Provides thin provisioning and snapshots that share a data store. |
| 256 | |
Joe Thornber | c6b4fcb | 2013-03-01 22:45:51 +0000 | [diff] [blame] | 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 | |
Joe Thornber | f283635 | 2013-03-01 22:45:51 +0000 | [diff] [blame] | 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 | |
Heinz Mauelshagen | 8735a81 | 2013-03-01 22:45:52 +0000 | [diff] [blame] | 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 | |
Joe Thornber | eec4057 | 2014-03-03 10:23:15 -0500 | [diff] [blame] | 288 | config DM_ERA |
| 289 | tristate "Era target (EXPERIMENTAL)" |
| 290 | depends on BLK_DEV_DM |
| 291 | default n |
| 292 | select DM_PERSISTENT_DATA |
| 293 | select DM_BIO_PRISON |
| 294 | ---help--- |
| 295 | dm-era tracks which parts of a block device are written to |
| 296 | over time. Useful for maintaining cache coherency when using |
| 297 | vendor snapshots. |
| 298 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 299 | config DM_MIRROR |
Alasdair G Kergon | 0149e57 | 2008-02-08 02:10:32 +0000 | [diff] [blame] | 300 | tristate "Mirror target" |
| 301 | depends on BLK_DEV_DM |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 302 | ---help--- |
| 303 | Allow volume managers to mirror logical volumes, also |
| 304 | needed for live data migration tools such as 'pvmove'. |
| 305 | |
Mikulas Patocka | 5442851 | 2013-11-08 10:47:12 -0500 | [diff] [blame] | 306 | config DM_LOG_USERSPACE |
| 307 | tristate "Mirror userspace logging" |
| 308 | depends on DM_MIRROR && NET |
| 309 | select CONNECTOR |
| 310 | ---help--- |
| 311 | The userspace logging module provides a mechanism for |
| 312 | relaying the dm-dirty-log API to userspace. Log designs |
| 313 | which are more suited to userspace implementation (e.g. |
| 314 | shared storage logs) or experimental logs can be implemented |
| 315 | by leveraging this framework. |
| 316 | |
NeilBrown | 9d09e66 | 2011-01-13 20:00:02 +0000 | [diff] [blame] | 317 | config DM_RAID |
NeilBrown | d9f691c | 2012-08-02 08:35:43 +1000 | [diff] [blame] | 318 | tristate "RAID 1/4/5/6/10 target" |
Alasdair G Kergon | 035220b | 2012-03-28 18:41:24 +0100 | [diff] [blame] | 319 | depends on BLK_DEV_DM |
Jonathan Brassow | b12d437 | 2011-08-02 12:32:07 +0100 | [diff] [blame] | 320 | select MD_RAID1 |
NeilBrown | d9f691c | 2012-08-02 08:35:43 +1000 | [diff] [blame] | 321 | select MD_RAID10 |
NeilBrown | 9d09e66 | 2011-01-13 20:00:02 +0000 | [diff] [blame] | 322 | select MD_RAID456 |
| 323 | select BLK_DEV_MD |
| 324 | ---help--- |
NeilBrown | d9f691c | 2012-08-02 08:35:43 +1000 | [diff] [blame] | 325 | A dm target that supports RAID1, RAID10, RAID4, RAID5 and RAID6 mappings |
NeilBrown | 9d09e66 | 2011-01-13 20:00:02 +0000 | [diff] [blame] | 326 | |
| 327 | A RAID-5 set of N drives with a capacity of C MB per drive provides |
| 328 | the capacity of C * (N - 1) MB, and protects against a failure |
| 329 | of a single drive. For a given sector (row) number, (N - 1) drives |
| 330 | contain data sectors, and one drive contains the parity protection. |
| 331 | For a RAID-4 set, the parity blocks are present on a single drive, |
| 332 | while a RAID-5 set distributes the parity across the drives in one |
| 333 | of the available parity distribution methods. |
| 334 | |
| 335 | A RAID-6 set of N drives with a capacity of C MB per drive |
| 336 | provides the capacity of C * (N - 2) MB, and protects |
| 337 | against a failure of any two drives. For a given sector |
| 338 | (row) number, (N - 2) drives contain data sectors, and two |
| 339 | drives contains two independent redundancy syndromes. Like |
| 340 | RAID-5, RAID-6 distributes the syndromes across the drives |
| 341 | in one of the available parity distribution methods. |
| 342 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 343 | config DM_ZERO |
Alasdair G Kergon | 0149e57 | 2008-02-08 02:10:32 +0000 | [diff] [blame] | 344 | tristate "Zero target" |
| 345 | depends on BLK_DEV_DM |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 346 | ---help--- |
| 347 | A target that discards writes, and returns all zeroes for |
| 348 | reads. Useful in some recovery situations. |
| 349 | |
| 350 | config DM_MULTIPATH |
Alasdair G Kergon | 0149e57 | 2008-02-08 02:10:32 +0000 | [diff] [blame] | 351 | tristate "Multipath target" |
| 352 | depends on BLK_DEV_DM |
Chandra Seetharaman | fe9233f | 2008-05-23 18:16:40 -0700 | [diff] [blame] | 353 | # nasty syntax but means make DM_MULTIPATH independent |
| 354 | # of SCSI_DH if the latter isn't defined but if |
| 355 | # it is, DM_MULTIPATH must depend on it. We get a build |
| 356 | # error if SCSI_DH=m and DM_MULTIPATH=y |
| 357 | depends on SCSI_DH || !SCSI_DH |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 358 | ---help--- |
| 359 | Allow volume managers to support multipath hardware. |
| 360 | |
Kiyoshi Ueda | fd5e033 | 2009-06-22 10:12:27 +0100 | [diff] [blame] | 361 | config DM_MULTIPATH_QL |
| 362 | tristate "I/O Path Selector based on the number of in-flight I/Os" |
| 363 | depends on DM_MULTIPATH |
| 364 | ---help--- |
| 365 | This path selector is a dynamic load balancer which selects |
| 366 | the path with the least number of in-flight I/Os. |
| 367 | |
| 368 | If unsure, say N. |
| 369 | |
Kiyoshi Ueda | f392ba8 | 2009-06-22 10:12:28 +0100 | [diff] [blame] | 370 | config DM_MULTIPATH_ST |
| 371 | tristate "I/O Path Selector based on the service time" |
| 372 | depends on DM_MULTIPATH |
| 373 | ---help--- |
| 374 | This path selector is a dynamic load balancer which selects |
| 375 | the path expected to complete the incoming I/O in the shortest |
| 376 | time. |
| 377 | |
| 378 | If unsure, say N. |
| 379 | |
Heinz Mauelshagen | 26b9f22 | 2007-05-09 02:33:06 -0700 | [diff] [blame] | 380 | config DM_DELAY |
Alasdair G Kergon | d57916a | 2013-03-01 22:45:46 +0000 | [diff] [blame] | 381 | tristate "I/O delaying target" |
| 382 | depends on BLK_DEV_DM |
Heinz Mauelshagen | 26b9f22 | 2007-05-09 02:33:06 -0700 | [diff] [blame] | 383 | ---help--- |
| 384 | A target that delays reads and/or writes and can send |
| 385 | them to different devices. Useful for testing. |
| 386 | |
| 387 | If unsure, say N. |
| 388 | |
Mike Anderson | 51e5b2b | 2007-10-19 22:48:00 +0100 | [diff] [blame] | 389 | config DM_UEVENT |
Alasdair G Kergon | e0b215d | 2012-03-28 18:41:24 +0100 | [diff] [blame] | 390 | bool "DM uevents" |
| 391 | depends on BLK_DEV_DM |
Mike Anderson | 51e5b2b | 2007-10-19 22:48:00 +0100 | [diff] [blame] | 392 | ---help--- |
| 393 | Generate udev events for DM events. |
| 394 | |
Josef Bacik | 3407ef5 | 2011-03-24 13:54:24 +0000 | [diff] [blame] | 395 | config DM_FLAKEY |
Alasdair G Kergon | d57916a | 2013-03-01 22:45:46 +0000 | [diff] [blame] | 396 | tristate "Flakey target" |
| 397 | depends on BLK_DEV_DM |
Josef Bacik | 3407ef5 | 2011-03-24 13:54:24 +0000 | [diff] [blame] | 398 | ---help--- |
| 399 | A target that intermittently fails I/O for debugging purposes. |
| 400 | |
Mikulas Patocka | a4ffc15 | 2012-03-28 18:43:38 +0100 | [diff] [blame] | 401 | config DM_VERITY |
Alasdair G Kergon | d57916a | 2013-03-01 22:45:46 +0000 | [diff] [blame] | 402 | tristate "Verity target support" |
| 403 | depends on BLK_DEV_DM |
Mikulas Patocka | a4ffc15 | 2012-03-28 18:43:38 +0100 | [diff] [blame] | 404 | select CRYPTO |
| 405 | select CRYPTO_HASH |
| 406 | select DM_BUFIO |
| 407 | ---help--- |
| 408 | This device-mapper target creates a read-only device that |
| 409 | transparently validates the data on one underlying device against |
| 410 | a pre-generated tree of cryptographic checksums stored on a second |
| 411 | device. |
| 412 | |
| 413 | You'll need to activate the digests you're going to use in the |
| 414 | cryptoapi configuration. |
| 415 | |
| 416 | To compile this code as a module, choose M here: the module will |
| 417 | be called dm-verity. |
| 418 | |
| 419 | If unsure, say N. |
| 420 | |
Jim Ramsay | 9d0eb0a | 2013-07-10 23:41:19 +0100 | [diff] [blame] | 421 | config DM_SWITCH |
| 422 | tristate "Switch target support (EXPERIMENTAL)" |
| 423 | depends on BLK_DEV_DM |
| 424 | ---help--- |
| 425 | This device-mapper target creates a device that supports an arbitrary |
| 426 | mapping of fixed-size regions of I/O across a fixed set of paths. |
| 427 | The path used for any specific region can be switched dynamically |
| 428 | by sending the target a message. |
| 429 | |
| 430 | To compile this code as a module, choose M here: the module will |
| 431 | be called dm-switch. |
| 432 | |
| 433 | If unsure, say N. |
| 434 | |
Jan Engelhardt | afd4403 | 2007-07-17 04:06:11 -0700 | [diff] [blame] | 435 | endif # MD |