blob: d5415eedba86738dcf23f72d6b6369eab0e0ea9d [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# Block device driver configuration
3#
4
Jan Engelhardtafd44032007-07-17 04:06:11 -07005menuconfig MD
Linus Torvalds1da177e2005-04-16 15:20:36 -07006 bool "Multiple devices driver support (RAID and LVM)"
Jan Engelhardtafd44032007-07-17 04:06:11 -07007 depends on BLOCK
Pranith Kumar83fe27e2014-12-05 11:24:45 -05008 select SRCU
Linus Torvalds1da177e2005-04-16 15:20:36 -07009 help
10 Support multiple physical spindles through a single logical device.
11 Required for RAID and logical volume management.
12
Jan Engelhardtafd44032007-07-17 04:06:11 -070013if MD
14
Linus Torvalds1da177e2005-04-16 15:20:36 -070015config BLK_DEV_MD
16 tristate "RAID support"
Linus Torvalds1da177e2005-04-16 15:20:36 -070017 ---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 Vena3640922008-09-21 15:44:32 -070034config MD_AUTODETECT
35 bool "Autodetect RAID arrays during kernel boot"
Alan Jenkinsce52aeb2008-10-10 16:02:53 +010036 depends on BLK_DEV_MD=y
Arjan van de Vena3640922008-09-21 15:44:32 -070037 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 Torvalds1da177e2005-04-16 15:20:36 -070048config 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
61config 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
81config 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
103config MD_RAID10
NeilBrown08fb7302010-05-03 13:16:56 +1000104 tristate "RAID-10 (mirrored striping) mode"
105 depends on BLK_DEV_MD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700106 ---help---
107 RAID-10 provides a combination of striping (RAID-0) and
Justin Piszcz4d2554d2006-06-26 00:27:50 -0700108 mirroring (RAID-1) with easier configuration and more flexible
Linus Torvalds1da177e2005-04-16 15:20:36 -0700109 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
NeilBrown16a53ec2006-06-26 00:27:38 -0700122config MD_RAID456
123 tristate "RAID-4/RAID-5/RAID-6 mode"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700124 depends on BLK_DEV_MD
David Woodhousef5e70d02009-07-13 11:35:12 +0100125 select RAID6_PQ
Dan Williams9bc89cd2007-01-02 11:10:44 -0700126 select ASYNC_MEMCPY
127 select ASYNC_XOR
Dan Williamsac6b53b2009-07-14 13:40:19 -0700128 select ASYNC_PQ
129 select ASYNC_RAID6_RECOV
Linus Torvalds1da177e2005-04-16 15:20:36 -0700130 ---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
NeilBrown16a53ec2006-06-26 00:27:38 -0700139 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 Torvalds1da177e2005-04-16 15:20:36 -0700147 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
NeilBrown16a53ec2006-06-26 00:27:38 -0700152 If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y. To
Linus Torvalds1da177e2005-04-16 15:20:36 -0700153 compile this code as a module, choose M here: the module
NeilBrown16a53ec2006-06-26 00:27:38 -0700154 will be called raid456.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700155
156 If unsure, say Y.
157
Linus Torvalds1da177e2005-04-16 15:20:36 -0700158config MD_MULTIPATH
159 tristate "Multipath I/O support"
160 depends on BLK_DEV_MD
161 help
NeilBrown93bd89a2009-12-14 12:49:59 +1100162 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 Torvalds1da177e2005-04-16 15:20:36 -0700166
167 If unsure, say N.
168
169config 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
Goldwyn Rodrigues8e854e92014-03-07 11:21:15 -0600178
179config MD_CLUSTER
180 tristate "Cluster Support for MD (EXPERIMENTAL)"
181 depends on BLK_DEV_MD
182 depends on DLM
183 default n
184 ---help---
185 Clustering support for MD devices. This enables locking and
186 synchronization across multiple systems on the cluster, so all
187 nodes in the cluster can access the MD devices simultaneously.
188
189 This brings the redundancy (and uptime) of RAID levels across the
190 nodes of the cluster.
191
192 If unsure, say N.
193
Kent Overstreetcafe5632013-03-23 16:11:31 -0700194source "drivers/md/bcache/Kconfig"
195
Mikulas Patocka2995fa72014-01-13 19:37:54 -0500196config BLK_DEV_DM_BUILTIN
Christoph Jaeger6341e622014-12-20 15:41:11 -0500197 bool
Mikulas Patocka2995fa72014-01-13 19:37:54 -0500198
Linus Torvalds1da177e2005-04-16 15:20:36 -0700199config BLK_DEV_DM
200 tristate "Device mapper support"
Mikulas Patocka2995fa72014-01-13 19:37:54 -0500201 select BLK_DEV_DM_BUILTIN
Linus Torvalds1da177e2005-04-16 15:20:36 -0700202 ---help---
203 Device-mapper is a low level volume manager. It works by allowing
204 people to specify mappings for ranges of logical sectors. Various
205 mapping types are available, in addition people may write their own
206 modules containing custom mappings if they wish.
207
208 Higher level volume managers such as LVM2 use this driver.
209
210 To compile this as a module, choose M here: the module will be
211 called dm-mod.
212
213 If unsure, say N.
214
Mike Snitzer17e149b2015-03-11 15:01:09 -0400215config DM_MQ_DEFAULT
216 bool "request-based DM: use blk-mq I/O path by default"
217 depends on BLK_DEV_DM
218 ---help---
219 This option enables the blk-mq based I/O path for request-based
220 DM devices by default. With the option the dm_mod.use_blk_mq
221 module/boot option defaults to Y, without it to N, but it can
222 still be overriden either way.
223
224 If unsure say N.
225
Bryn Reevescc109202006-10-03 01:15:35 -0700226config DM_DEBUG
Christoph Jaeger6341e622014-12-20 15:41:11 -0500227 bool "Device mapper debugging support"
Alasdair G Kergon0149e572008-02-08 02:10:32 +0000228 depends on BLK_DEV_DM
Bryn Reevescc109202006-10-03 01:15:35 -0700229 ---help---
230 Enable this for messages that may help debug device-mapper problems.
231
232 If unsure, say N.
233
Mikulas Patocka95d402f2011-10-31 20:19:09 +0000234config DM_BUFIO
235 tristate
Alasdair G Kergond57916a2013-03-01 22:45:46 +0000236 depends on BLK_DEV_DM
Mikulas Patocka95d402f2011-10-31 20:19:09 +0000237 ---help---
238 This interface allows you to do buffered I/O on a device and acts
239 as a cache, holding recently-read blocks in memory and performing
240 delayed writes.
241
Mike Snitzer4f81a412012-10-12 21:02:13 +0100242config DM_BIO_PRISON
243 tristate
Alasdair G Kergond57916a2013-03-01 22:45:46 +0000244 depends on BLK_DEV_DM
Mike Snitzer4f81a412012-10-12 21:02:13 +0100245 ---help---
246 Some bio locking schemes used by other device-mapper targets
247 including thin provisioning.
248
Joe Thornber991d9fa2011-10-31 20:21:18 +0000249source "drivers/md/persistent-data/Kconfig"
250
Linus Torvalds1da177e2005-04-16 15:20:36 -0700251config DM_CRYPT
252 tristate "Crypt target support"
Alasdair G Kergon0149e572008-02-08 02:10:32 +0000253 depends on BLK_DEV_DM
Linus Torvalds1da177e2005-04-16 15:20:36 -0700254 select CRYPTO
Herbert Xu32632632006-12-10 09:50:36 +1100255 select CRYPTO_CBC
Linus Torvalds1da177e2005-04-16 15:20:36 -0700256 ---help---
257 This device-mapper target allows you to create a device that
258 transparently encrypts the data on it. You'll need to activate
259 the ciphers you're going to use in the cryptoapi configuration.
260
Loic Pefferkorncf352482014-12-15 22:18:43 +0100261 For further information on dm-crypt and userspace tools see:
Baruch Siach6ed443c2015-07-05 09:55:44 +0300262 <https://gitlab.com/cryptsetup/cryptsetup/wikis/DMCrypt>
Linus Torvalds1da177e2005-04-16 15:20:36 -0700263
264 To compile this code as a module, choose M here: the module will
265 be called dm-crypt.
266
267 If unsure, say N.
268
269config DM_SNAPSHOT
Alasdair G Kergon0149e572008-02-08 02:10:32 +0000270 tristate "Snapshot target"
271 depends on BLK_DEV_DM
Mikulas Patocka55494bf2014-01-13 19:12:36 -0500272 select DM_BUFIO
Linus Torvalds1da177e2005-04-16 15:20:36 -0700273 ---help---
Justin Piszcz4d2554d2006-06-26 00:27:50 -0700274 Allow volume managers to take writable snapshots of a device.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700275
Joe Thornber991d9fa2011-10-31 20:21:18 +0000276config DM_THIN_PROVISIONING
Alasdair G Kergond57916a2013-03-01 22:45:46 +0000277 tristate "Thin provisioning target"
278 depends on BLK_DEV_DM
Joe Thornber991d9fa2011-10-31 20:21:18 +0000279 select DM_PERSISTENT_DATA
Mike Snitzer4f81a412012-10-12 21:02:13 +0100280 select DM_BIO_PRISON
Joe Thornber991d9fa2011-10-31 20:21:18 +0000281 ---help---
282 Provides thin provisioning and snapshots that share a data store.
283
Joe Thornberc6b4fcb2013-03-01 22:45:51 +0000284config DM_CACHE
285 tristate "Cache target (EXPERIMENTAL)"
286 depends on BLK_DEV_DM
287 default n
288 select DM_PERSISTENT_DATA
289 select DM_BIO_PRISON
290 ---help---
291 dm-cache attempts to improve performance of a block device by
292 moving frequently used data to a smaller, higher performance
293 device. Different 'policy' plugins can be used to change the
294 algorithms used to select which blocks are promoted, demoted,
295 cleaned etc. It supports writeback and writethrough modes.
296
Joe Thornberf2836352013-03-01 22:45:51 +0000297config DM_CACHE_MQ
298 tristate "MQ Cache Policy (EXPERIMENTAL)"
299 depends on DM_CACHE
300 default y
301 ---help---
302 A cache policy that uses a multiqueue ordered by recent hit
303 count to select which blocks should be promoted and demoted.
304 This is meant to be a general purpose policy. It prioritises
305 reads over writes.
306
Joe Thornber66a63632015-05-15 15:33:34 +0100307config DM_CACHE_SMQ
308 tristate "Stochastic MQ Cache Policy (EXPERIMENTAL)"
309 depends on DM_CACHE
310 default y
311 ---help---
312 A cache policy that uses a multiqueue ordered by recent hits
313 to select which blocks should be promoted and demoted.
314 This is meant to be a general purpose policy. It prioritises
315 reads over writes. This SMQ policy (vs MQ) offers the promise
316 of less memory utilization, improved performance and increased
317 adaptability in the face of changing workloads.
318
Heinz Mauelshagen8735a812013-03-01 22:45:52 +0000319config DM_CACHE_CLEANER
320 tristate "Cleaner Cache Policy (EXPERIMENTAL)"
321 depends on DM_CACHE
322 default y
323 ---help---
324 A simple cache policy that writes back all data to the
325 origin. Used when decommissioning a dm-cache.
326
Joe Thornbereec40572014-03-03 10:23:15 -0500327config DM_ERA
328 tristate "Era target (EXPERIMENTAL)"
329 depends on BLK_DEV_DM
330 default n
331 select DM_PERSISTENT_DATA
332 select DM_BIO_PRISON
333 ---help---
334 dm-era tracks which parts of a block device are written to
335 over time. Useful for maintaining cache coherency when using
336 vendor snapshots.
337
Linus Torvalds1da177e2005-04-16 15:20:36 -0700338config DM_MIRROR
Alasdair G Kergon0149e572008-02-08 02:10:32 +0000339 tristate "Mirror target"
340 depends on BLK_DEV_DM
Linus Torvalds1da177e2005-04-16 15:20:36 -0700341 ---help---
342 Allow volume managers to mirror logical volumes, also
343 needed for live data migration tools such as 'pvmove'.
344
Mikulas Patocka54428512013-11-08 10:47:12 -0500345config DM_LOG_USERSPACE
346 tristate "Mirror userspace logging"
347 depends on DM_MIRROR && NET
348 select CONNECTOR
349 ---help---
350 The userspace logging module provides a mechanism for
351 relaying the dm-dirty-log API to userspace. Log designs
352 which are more suited to userspace implementation (e.g.
353 shared storage logs) or experimental logs can be implemented
354 by leveraging this framework.
355
NeilBrown9d09e662011-01-13 20:00:02 +0000356config DM_RAID
NeilBrownd9f691c2012-08-02 08:35:43 +1000357 tristate "RAID 1/4/5/6/10 target"
Alasdair G Kergon035220b2012-03-28 18:41:24 +0100358 depends on BLK_DEV_DM
Jonathan Brassowb12d4372011-08-02 12:32:07 +0100359 select MD_RAID1
NeilBrownd9f691c2012-08-02 08:35:43 +1000360 select MD_RAID10
NeilBrown9d09e662011-01-13 20:00:02 +0000361 select MD_RAID456
362 select BLK_DEV_MD
363 ---help---
NeilBrownd9f691c2012-08-02 08:35:43 +1000364 A dm target that supports RAID1, RAID10, RAID4, RAID5 and RAID6 mappings
NeilBrown9d09e662011-01-13 20:00:02 +0000365
366 A RAID-5 set of N drives with a capacity of C MB per drive provides
367 the capacity of C * (N - 1) MB, and protects against a failure
368 of a single drive. For a given sector (row) number, (N - 1) drives
369 contain data sectors, and one drive contains the parity protection.
370 For a RAID-4 set, the parity blocks are present on a single drive,
371 while a RAID-5 set distributes the parity across the drives in one
372 of the available parity distribution methods.
373
374 A RAID-6 set of N drives with a capacity of C MB per drive
375 provides the capacity of C * (N - 2) MB, and protects
376 against a failure of any two drives. For a given sector
377 (row) number, (N - 2) drives contain data sectors, and two
378 drives contains two independent redundancy syndromes. Like
379 RAID-5, RAID-6 distributes the syndromes across the drives
380 in one of the available parity distribution methods.
381
Linus Torvalds1da177e2005-04-16 15:20:36 -0700382config DM_ZERO
Alasdair G Kergon0149e572008-02-08 02:10:32 +0000383 tristate "Zero target"
384 depends on BLK_DEV_DM
Linus Torvalds1da177e2005-04-16 15:20:36 -0700385 ---help---
386 A target that discards writes, and returns all zeroes for
387 reads. Useful in some recovery situations.
388
389config DM_MULTIPATH
Alasdair G Kergon0149e572008-02-08 02:10:32 +0000390 tristate "Multipath target"
391 depends on BLK_DEV_DM
Chandra Seetharamanfe9233f2008-05-23 18:16:40 -0700392 # nasty syntax but means make DM_MULTIPATH independent
393 # of SCSI_DH if the latter isn't defined but if
394 # it is, DM_MULTIPATH must depend on it. We get a build
395 # error if SCSI_DH=m and DM_MULTIPATH=y
396 depends on SCSI_DH || !SCSI_DH
Linus Torvalds1da177e2005-04-16 15:20:36 -0700397 ---help---
398 Allow volume managers to support multipath hardware.
399
Kiyoshi Uedafd5e0332009-06-22 10:12:27 +0100400config DM_MULTIPATH_QL
401 tristate "I/O Path Selector based on the number of in-flight I/Os"
402 depends on DM_MULTIPATH
403 ---help---
404 This path selector is a dynamic load balancer which selects
405 the path with the least number of in-flight I/Os.
406
407 If unsure, say N.
408
Kiyoshi Uedaf392ba82009-06-22 10:12:28 +0100409config DM_MULTIPATH_ST
410 tristate "I/O Path Selector based on the service time"
411 depends on DM_MULTIPATH
412 ---help---
413 This path selector is a dynamic load balancer which selects
414 the path expected to complete the incoming I/O in the shortest
415 time.
416
417 If unsure, say N.
418
Heinz Mauelshagen26b9f222007-05-09 02:33:06 -0700419config DM_DELAY
Alasdair G Kergond57916a2013-03-01 22:45:46 +0000420 tristate "I/O delaying target"
421 depends on BLK_DEV_DM
Heinz Mauelshagen26b9f222007-05-09 02:33:06 -0700422 ---help---
423 A target that delays reads and/or writes and can send
424 them to different devices. Useful for testing.
425
426 If unsure, say N.
427
Mike Anderson51e5b2b2007-10-19 22:48:00 +0100428config DM_UEVENT
Alasdair G Kergone0b215d2012-03-28 18:41:24 +0100429 bool "DM uevents"
430 depends on BLK_DEV_DM
Mike Anderson51e5b2b2007-10-19 22:48:00 +0100431 ---help---
432 Generate udev events for DM events.
433
Josef Bacik3407ef52011-03-24 13:54:24 +0000434config DM_FLAKEY
Alasdair G Kergond57916a2013-03-01 22:45:46 +0000435 tristate "Flakey target"
436 depends on BLK_DEV_DM
Josef Bacik3407ef52011-03-24 13:54:24 +0000437 ---help---
438 A target that intermittently fails I/O for debugging purposes.
439
Mikulas Patockaa4ffc152012-03-28 18:43:38 +0100440config DM_VERITY
Alasdair G Kergond57916a2013-03-01 22:45:46 +0000441 tristate "Verity target support"
442 depends on BLK_DEV_DM
Mikulas Patockaa4ffc152012-03-28 18:43:38 +0100443 select CRYPTO
444 select CRYPTO_HASH
445 select DM_BUFIO
446 ---help---
447 This device-mapper target creates a read-only device that
448 transparently validates the data on one underlying device against
449 a pre-generated tree of cryptographic checksums stored on a second
450 device.
451
452 You'll need to activate the digests you're going to use in the
453 cryptoapi configuration.
454
455 To compile this code as a module, choose M here: the module will
456 be called dm-verity.
457
458 If unsure, say N.
459
Jim Ramsay9d0eb0a2013-07-10 23:41:19 +0100460config DM_SWITCH
461 tristate "Switch target support (EXPERIMENTAL)"
462 depends on BLK_DEV_DM
463 ---help---
464 This device-mapper target creates a device that supports an arbitrary
465 mapping of fixed-size regions of I/O across a fixed set of paths.
466 The path used for any specific region can be switched dynamically
467 by sending the target a message.
468
469 To compile this code as a module, choose M here: the module will
470 be called dm-switch.
471
472 If unsure, say N.
473
Josef Bacik0e9cebe2015-03-20 10:50:37 -0400474config DM_LOG_WRITES
475 tristate "Log writes target support"
476 depends on BLK_DEV_DM
477 ---help---
478 This device-mapper target takes two devices, one device to use
479 normally, one to log all write operations done to the first device.
480 This is for use by file system developers wishing to verify that
Geert Uytterhoeven57d42482015-07-06 15:39:17 +0200481 their fs is writing a consistent file system at all times by allowing
Josef Bacik0e9cebe2015-03-20 10:50:37 -0400482 them to replay the log in a variety of ways and to check the
483 contents.
484
485 To compile this code as a module, choose M here: the module will
486 be called dm-log-writes.
487
488 If unsure, say N.
489
Jan Engelhardtafd44032007-07-17 04:06:11 -0700490endif # MD