blob: 7cdf359d6b23a871a0e21962354b416e88b39abb [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
Linus Torvalds1da177e2005-04-16 15:20:36 -07008 help
9 Support multiple physical spindles through a single logical device.
10 Required for RAID and logical volume management.
11
Jan Engelhardtafd44032007-07-17 04:06:11 -070012if MD
13
Linus Torvalds1da177e2005-04-16 15:20:36 -070014config BLK_DEV_MD
15 tristate "RAID support"
Linus Torvalds1da177e2005-04-16 15:20:36 -070016 ---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
Arjan van de Vena3640922008-09-21 15:44:32 -070033config MD_AUTODETECT
34 bool "Autodetect RAID arrays during kernel boot"
Alan Jenkinsce52aeb2008-10-10 16:02:53 +010035 depends on BLK_DEV_MD=y
Arjan van de Vena3640922008-09-21 15:44:32 -070036 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
Linus Torvalds1da177e2005-04-16 15:20:36 -070047config 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
NeilBrown08fb7302010-05-03 13:16:56 +1000103 tristate "RAID-10 (mirrored striping) mode"
104 depends on BLK_DEV_MD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700105 ---help---
106 RAID-10 provides a combination of striping (RAID-0) and
Justin Piszcz4d2554d2006-06-26 00:27:50 -0700107 mirroring (RAID-1) with easier configuration and more flexible
Linus Torvalds1da177e2005-04-16 15:20:36 -0700108 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
NeilBrown16a53ec2006-06-26 00:27:38 -0700121config MD_RAID456
122 tristate "RAID-4/RAID-5/RAID-6 mode"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700123 depends on BLK_DEV_MD
David Woodhousef5e70d02009-07-13 11:35:12 +0100124 select RAID6_PQ
Dan Williams9bc89cd2007-01-02 11:10:44 -0700125 select ASYNC_MEMCPY
126 select ASYNC_XOR
Dan Williamsac6b53b2009-07-14 13:40:19 -0700127 select ASYNC_PQ
128 select ASYNC_RAID6_RECOV
Linus Torvalds1da177e2005-04-16 15:20:36 -0700129 ---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
NeilBrown16a53ec2006-06-26 00:27:38 -0700138 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
Linus Torvalds1da177e2005-04-16 15:20:36 -0700146 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
NeilBrown16a53ec2006-06-26 00:27:38 -0700151 If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y. To
Linus Torvalds1da177e2005-04-16 15:20:36 -0700152 compile this code as a module, choose M here: the module
NeilBrown16a53ec2006-06-26 00:27:38 -0700153 will be called raid456.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700154
155 If unsure, say Y.
156
Dan Williams07a3b412009-08-29 19:13:13 -0700157config 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
Linus Torvalds1da177e2005-04-16 15:20:36 -0700168config MD_MULTIPATH
169 tristate "Multipath I/O support"
170 depends on BLK_DEV_MD
171 help
NeilBrown93bd89a2009-12-14 12:49:59 +1100172 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.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700176
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"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700190 ---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
Bryn Reevescc109202006-10-03 01:15:35 -0700203config DM_DEBUG
204 boolean "Device mapper debugging support"
Alasdair G Kergon0149e572008-02-08 02:10:32 +0000205 depends on BLK_DEV_DM
Bryn Reevescc109202006-10-03 01:15:35 -0700206 ---help---
207 Enable this for messages that may help debug device-mapper problems.
208
209 If unsure, say N.
210
Mikulas Patocka95d402f2011-10-31 20:19:09 +0000211config DM_BUFIO
212 tristate
Alasdair G Kergond57916a2013-03-01 22:45:46 +0000213 depends on BLK_DEV_DM
Mikulas Patocka95d402f2011-10-31 20:19:09 +0000214 ---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
Mike Snitzer4f81a412012-10-12 21:02:13 +0100219config DM_BIO_PRISON
220 tristate
Alasdair G Kergond57916a2013-03-01 22:45:46 +0000221 depends on BLK_DEV_DM
Mike Snitzer4f81a412012-10-12 21:02:13 +0100222 ---help---
223 Some bio locking schemes used by other device-mapper targets
224 including thin provisioning.
225
Joe Thornber991d9fa2011-10-31 20:21:18 +0000226source "drivers/md/persistent-data/Kconfig"
227
Linus Torvalds1da177e2005-04-16 15:20:36 -0700228config DM_CRYPT
229 tristate "Crypt target support"
Alasdair G Kergon0149e572008-02-08 02:10:32 +0000230 depends on BLK_DEV_DM
Linus Torvalds1da177e2005-04-16 15:20:36 -0700231 select CRYPTO
Herbert Xu32632632006-12-10 09:50:36 +1100232 select CRYPTO_CBC
Linus Torvalds1da177e2005-04-16 15:20:36 -0700233 ---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
Alasdair G Kergon0149e572008-02-08 02:10:32 +0000248 tristate "Snapshot target"
249 depends on BLK_DEV_DM
Linus Torvalds1da177e2005-04-16 15:20:36 -0700250 ---help---
Justin Piszcz4d2554d2006-06-26 00:27:50 -0700251 Allow volume managers to take writable snapshots of a device.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700252
Joe Thornber991d9fa2011-10-31 20:21:18 +0000253config DM_THIN_PROVISIONING
Alasdair G Kergond57916a2013-03-01 22:45:46 +0000254 tristate "Thin provisioning target"
255 depends on BLK_DEV_DM
Joe Thornber991d9fa2011-10-31 20:21:18 +0000256 select DM_PERSISTENT_DATA
Mike Snitzer4f81a412012-10-12 21:02:13 +0100257 select DM_BIO_PRISON
Joe Thornber991d9fa2011-10-31 20:21:18 +0000258 ---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
Linus Torvalds1da177e2005-04-16 15:20:36 -0700271config DM_MIRROR
Alasdair G Kergon0149e572008-02-08 02:10:32 +0000272 tristate "Mirror target"
273 depends on BLK_DEV_DM
Linus Torvalds1da177e2005-04-16 15:20:36 -0700274 ---help---
275 Allow volume managers to mirror logical volumes, also
276 needed for live data migration tools such as 'pvmove'.
277
NeilBrown9d09e662011-01-13 20:00:02 +0000278config DM_RAID
NeilBrownd9f691c2012-08-02 08:35:43 +1000279 tristate "RAID 1/4/5/6/10 target"
Alasdair G Kergon035220b2012-03-28 18:41:24 +0100280 depends on BLK_DEV_DM
Jonathan Brassowb12d4372011-08-02 12:32:07 +0100281 select MD_RAID1
NeilBrownd9f691c2012-08-02 08:35:43 +1000282 select MD_RAID10
NeilBrown9d09e662011-01-13 20:00:02 +0000283 select MD_RAID456
284 select BLK_DEV_MD
285 ---help---
NeilBrownd9f691c2012-08-02 08:35:43 +1000286 A dm target that supports RAID1, RAID10, RAID4, RAID5 and RAID6 mappings
NeilBrown9d09e662011-01-13 20:00:02 +0000287
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
Jonthan Brassowf5db4af2009-06-22 10:12:35 +0100304config DM_LOG_USERSPACE
Alasdair G Kergond57916a2013-03-01 22:45:46 +0000305 tristate "Mirror userspace logging"
306 depends on DM_MIRROR && NET
Jonthan Brassowf5db4af2009-06-22 10:12:35 +0100307 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
Linus Torvalds1da177e2005-04-16 15:20:36 -0700315config DM_ZERO
Alasdair G Kergon0149e572008-02-08 02:10:32 +0000316 tristate "Zero target"
317 depends on BLK_DEV_DM
Linus Torvalds1da177e2005-04-16 15:20:36 -0700318 ---help---
319 A target that discards writes, and returns all zeroes for
320 reads. Useful in some recovery situations.
321
322config DM_MULTIPATH
Alasdair G Kergon0149e572008-02-08 02:10:32 +0000323 tristate "Multipath target"
324 depends on BLK_DEV_DM
Chandra Seetharamanfe9233f2008-05-23 18:16:40 -0700325 # 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
Linus Torvalds1da177e2005-04-16 15:20:36 -0700330 ---help---
331 Allow volume managers to support multipath hardware.
332
Kiyoshi Uedafd5e0332009-06-22 10:12:27 +0100333config 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
Kiyoshi Uedaf392ba82009-06-22 10:12:28 +0100342config 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
Heinz Mauelshagen26b9f222007-05-09 02:33:06 -0700352config DM_DELAY
Alasdair G Kergond57916a2013-03-01 22:45:46 +0000353 tristate "I/O delaying target"
354 depends on BLK_DEV_DM
Heinz Mauelshagen26b9f222007-05-09 02:33:06 -0700355 ---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
Mike Anderson51e5b2b2007-10-19 22:48:00 +0100361config DM_UEVENT
Alasdair G Kergone0b215d2012-03-28 18:41:24 +0100362 bool "DM uevents"
363 depends on BLK_DEV_DM
Mike Anderson51e5b2b2007-10-19 22:48:00 +0100364 ---help---
365 Generate udev events for DM events.
366
Josef Bacik3407ef52011-03-24 13:54:24 +0000367config DM_FLAKEY
Alasdair G Kergond57916a2013-03-01 22:45:46 +0000368 tristate "Flakey target"
369 depends on BLK_DEV_DM
Josef Bacik3407ef52011-03-24 13:54:24 +0000370 ---help---
371 A target that intermittently fails I/O for debugging purposes.
372
Mikulas Patockaa4ffc152012-03-28 18:43:38 +0100373config DM_VERITY
Alasdair G Kergond57916a2013-03-01 22:45:46 +0000374 tristate "Verity target support"
375 depends on BLK_DEV_DM
Mikulas Patockaa4ffc152012-03-28 18:43:38 +0100376 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
Jan Engelhardtafd44032007-07-17 04:06:11 -0700393endif # MD