]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # Block device driver configuration | |
3 | # | |
4 | ||
afd44034 | 5 | menuconfig MD |
1da177e4 | 6 | bool "Multiple devices driver support (RAID and LVM)" |
afd44034 | 7 | depends on BLOCK |
83fe27ea | 8 | select SRCU |
1da177e4 LT |
9 | help |
10 | Support multiple physical spindles through a single logical device. | |
11 | Required for RAID and logical volume management. | |
12 | ||
afd44034 JE |
13 | if MD |
14 | ||
1da177e4 LT |
15 | config BLK_DEV_MD |
16 | tristate "RAID support" | |
1da177e4 LT |
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 | ||
a364092a AV |
34 | config MD_AUTODETECT |
35 | bool "Autodetect RAID arrays during kernel boot" | |
ce52aebd | 36 | depends on BLK_DEV_MD=y |
a364092a AV |
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 | ||
1da177e4 LT |
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 | |
08fb730c N |
104 | tristate "RAID-10 (mirrored striping) mode" |
105 | depends on BLK_DEV_MD | |
1da177e4 LT |
106 | ---help--- |
107 | RAID-10 provides a combination of striping (RAID-0) and | |
4d2554d0 | 108 | mirroring (RAID-1) with easier configuration and more flexible |
1da177e4 LT |
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 | ||
4f6cce39 | 118 | https://www.kernel.org/pub/linux/utils/raid/mdadm/ |
1da177e4 LT |
119 | |
120 | If unsure, say Y. | |
121 | ||
16a53ecc N |
122 | config MD_RAID456 |
123 | tristate "RAID-4/RAID-5/RAID-6 mode" | |
1da177e4 | 124 | depends on BLK_DEV_MD |
f5e70d0f | 125 | select RAID6_PQ |
14f09e2f | 126 | select LIBCRC32C |
9bc89cd8 DW |
127 | select ASYNC_MEMCPY |
128 | select ASYNC_XOR | |
ac6b53b6 DW |
129 | select ASYNC_PQ |
130 | select ASYNC_RAID6_RECOV | |
1da177e4 LT |
131 | ---help--- |
132 | A RAID-5 set of N drives with a capacity of C MB per drive provides | |
133 | the capacity of C * (N - 1) MB, and protects against a failure | |
134 | of a single drive. For a given sector (row) number, (N - 1) drives | |
135 | contain data sectors, and one drive contains the parity protection. | |
136 | For a RAID-4 set, the parity blocks are present on a single drive, | |
137 | while a RAID-5 set distributes the parity across the drives in one | |
138 | of the available parity distribution methods. | |
139 | ||
16a53ecc N |
140 | A RAID-6 set of N drives with a capacity of C MB per drive |
141 | provides the capacity of C * (N - 2) MB, and protects | |
142 | against a failure of any two drives. For a given sector | |
143 | (row) number, (N - 2) drives contain data sectors, and two | |
144 | drives contains two independent redundancy syndromes. Like | |
145 | RAID-5, RAID-6 distributes the syndromes across the drives | |
146 | in one of the available parity distribution methods. | |
147 | ||
1da177e4 LT |
148 | Information about Software RAID on Linux is contained in the |
149 | Software-RAID mini-HOWTO, available from | |
150 | <http://www.tldp.org/docs.html#howto>. There you will also | |
151 | learn where to get the supporting user space utilities raidtools. | |
152 | ||
16a53ecc | 153 | If you want to use such a RAID-4/RAID-5/RAID-6 set, say Y. To |
1da177e4 | 154 | compile this code as a module, choose M here: the module |
16a53ecc | 155 | will be called raid456. |
1da177e4 LT |
156 | |
157 | If unsure, say Y. | |
158 | ||
1da177e4 LT |
159 | config MD_MULTIPATH |
160 | tristate "Multipath I/O support" | |
161 | depends on BLK_DEV_MD | |
162 | help | |
93bd89a6 N |
163 | MD_MULTIPATH provides a simple multi-path personality for use |
164 | the MD framework. It is not under active development. New | |
165 | projects should consider using DM_MULTIPATH which has more | |
166 | features and more testing. | |
1da177e4 LT |
167 | |
168 | If unsure, say N. | |
169 | ||
170 | config MD_FAULTY | |
171 | tristate "Faulty test module for MD" | |
172 | depends on BLK_DEV_MD | |
173 | help | |
174 | The "faulty" module allows for a block device that occasionally returns | |
175 | read or write errors. It is useful for testing. | |
176 | ||
177 | In unsure, say N. | |
178 | ||
8e854e9c GR |
179 | |
180 | config MD_CLUSTER | |
f0e230ad | 181 | tristate "Cluster Support for MD" |
8e854e9c GR |
182 | depends on BLK_DEV_MD |
183 | depends on DLM | |
184 | default n | |
185 | ---help--- | |
186 | Clustering support for MD devices. This enables locking and | |
187 | synchronization across multiple systems on the cluster, so all | |
188 | nodes in the cluster can access the MD devices simultaneously. | |
189 | ||
190 | This brings the redundancy (and uptime) of RAID levels across the | |
f0e230ad GJ |
191 | nodes of the cluster. Currently, it can work with raid1 and raid10 |
192 | (limited support). | |
8e854e9c GR |
193 | |
194 | If unsure, say N. | |
195 | ||
cafe5635 KO |
196 | source "drivers/md/bcache/Kconfig" |
197 | ||
2995fa78 | 198 | config BLK_DEV_DM_BUILTIN |
6341e62b | 199 | bool |
2995fa78 | 200 | |
1da177e4 LT |
201 | config BLK_DEV_DM |
202 | tristate "Device mapper support" | |
2995fa78 | 203 | select BLK_DEV_DM_BUILTIN |
976431b0 | 204 | depends on DAX || DAX=n |
1da177e4 LT |
205 | ---help--- |
206 | Device-mapper is a low level volume manager. It works by allowing | |
207 | people to specify mappings for ranges of logical sectors. Various | |
208 | mapping types are available, in addition people may write their own | |
209 | modules containing custom mappings if they wish. | |
210 | ||
211 | Higher level volume managers such as LVM2 use this driver. | |
212 | ||
213 | To compile this as a module, choose M here: the module will be | |
214 | called dm-mod. | |
215 | ||
216 | If unsure, say N. | |
217 | ||
cc109201 | 218 | config DM_DEBUG |
6341e62b | 219 | bool "Device mapper debugging support" |
0149e57f | 220 | depends on BLK_DEV_DM |
cc109201 BR |
221 | ---help--- |
222 | Enable this for messages that may help debug device-mapper problems. | |
223 | ||
224 | If unsure, say N. | |
225 | ||
95d402f0 MP |
226 | config DM_BUFIO |
227 | tristate | |
d57916a0 | 228 | depends on BLK_DEV_DM |
95d402f0 MP |
229 | ---help--- |
230 | This interface allows you to do buffered I/O on a device and acts | |
231 | as a cache, holding recently-read blocks in memory and performing | |
232 | delayed writes. | |
233 | ||
2e8ed711 JT |
234 | config DM_DEBUG_BLOCK_MANAGER_LOCKING |
235 | bool "Block manager locking" | |
236 | depends on DM_BUFIO | |
237 | ---help--- | |
238 | Block manager locking can catch various metadata corruption issues. | |
239 | ||
240 | If unsure, say N. | |
241 | ||
86bad0c7 MP |
242 | config DM_DEBUG_BLOCK_STACK_TRACING |
243 | bool "Keep stack trace of persistent data block lock holders" | |
2e8ed711 | 244 | depends on STACKTRACE_SUPPORT && DM_DEBUG_BLOCK_MANAGER_LOCKING |
86bad0c7 MP |
245 | select STACKTRACE |
246 | ---help--- | |
247 | Enable this for messages that may help debug problems with the | |
248 | block manager locking used by thin provisioning and caching. | |
249 | ||
250 | If unsure, say N. | |
3f068040 | 251 | |
4f81a417 MS |
252 | config DM_BIO_PRISON |
253 | tristate | |
d57916a0 | 254 | depends on BLK_DEV_DM |
4f81a417 MS |
255 | ---help--- |
256 | Some bio locking schemes used by other device-mapper targets | |
257 | including thin provisioning. | |
258 | ||
991d9fa0 JT |
259 | source "drivers/md/persistent-data/Kconfig" |
260 | ||
18a5bf27 SB |
261 | config DM_UNSTRIPED |
262 | tristate "Unstriped target" | |
263 | depends on BLK_DEV_DM | |
264 | ---help--- | |
265 | Unstripes I/O so it is issued solely on a single drive in a HW | |
266 | RAID0 or dm-striped target. | |
267 | ||
1da177e4 LT |
268 | config DM_CRYPT |
269 | tristate "Crypt target support" | |
0149e57f | 270 | depends on BLK_DEV_DM |
1da177e4 | 271 | select CRYPTO |
3263263f | 272 | select CRYPTO_CBC |
1da177e4 LT |
273 | ---help--- |
274 | This device-mapper target allows you to create a device that | |
275 | transparently encrypts the data on it. You'll need to activate | |
276 | the ciphers you're going to use in the cryptoapi configuration. | |
277 | ||
cf352487 | 278 | For further information on dm-crypt and userspace tools see: |
6ed443c0 | 279 | <https://gitlab.com/cryptsetup/cryptsetup/wikis/DMCrypt> |
1da177e4 LT |
280 | |
281 | To compile this code as a module, choose M here: the module will | |
282 | be called dm-crypt. | |
283 | ||
284 | If unsure, say N. | |
285 | ||
286 | config DM_SNAPSHOT | |
0149e57f AK |
287 | tristate "Snapshot target" |
288 | depends on BLK_DEV_DM | |
55494bf2 | 289 | select DM_BUFIO |
1da177e4 | 290 | ---help--- |
4d2554d0 | 291 | Allow volume managers to take writable snapshots of a device. |
1da177e4 | 292 | |
991d9fa0 | 293 | config DM_THIN_PROVISIONING |
d57916a0 AK |
294 | tristate "Thin provisioning target" |
295 | depends on BLK_DEV_DM | |
991d9fa0 | 296 | select DM_PERSISTENT_DATA |
4f81a417 | 297 | select DM_BIO_PRISON |
991d9fa0 JT |
298 | ---help--- |
299 | Provides thin provisioning and snapshots that share a data store. | |
300 | ||
c6b4fcba JT |
301 | config DM_CACHE |
302 | tristate "Cache target (EXPERIMENTAL)" | |
303 | depends on BLK_DEV_DM | |
304 | default n | |
305 | select DM_PERSISTENT_DATA | |
306 | select DM_BIO_PRISON | |
307 | ---help--- | |
308 | dm-cache attempts to improve performance of a block device by | |
309 | moving frequently used data to a smaller, higher performance | |
310 | device. Different 'policy' plugins can be used to change the | |
311 | algorithms used to select which blocks are promoted, demoted, | |
312 | cleaned etc. It supports writeback and writethrough modes. | |
313 | ||
66a63635 JT |
314 | config DM_CACHE_SMQ |
315 | tristate "Stochastic MQ Cache Policy (EXPERIMENTAL)" | |
316 | depends on DM_CACHE | |
317 | default y | |
318 | ---help--- | |
319 | A cache policy that uses a multiqueue ordered by recent hits | |
320 | to select which blocks should be promoted and demoted. | |
321 | This is meant to be a general purpose policy. It prioritises | |
322 | reads over writes. This SMQ policy (vs MQ) offers the promise | |
323 | of less memory utilization, improved performance and increased | |
324 | adaptability in the face of changing workloads. | |
325 | ||
48debafe MP |
326 | config DM_WRITECACHE |
327 | tristate "Writecache target" | |
328 | depends on BLK_DEV_DM | |
329 | ---help--- | |
330 | The writecache target caches writes on persistent memory or SSD. | |
331 | It is intended for databases or other programs that need extremely | |
332 | low commit latency. | |
333 | ||
334 | The writecache target doesn't cache reads because reads are supposed | |
335 | to be cached in standard RAM. | |
336 | ||
eec40579 JT |
337 | config DM_ERA |
338 | tristate "Era target (EXPERIMENTAL)" | |
339 | depends on BLK_DEV_DM | |
340 | default n | |
341 | select DM_PERSISTENT_DATA | |
342 | select DM_BIO_PRISON | |
343 | ---help--- | |
344 | dm-era tracks which parts of a block device are written to | |
345 | over time. Useful for maintaining cache coherency when using | |
346 | vendor snapshots. | |
347 | ||
1da177e4 | 348 | config DM_MIRROR |
0149e57f AK |
349 | tristate "Mirror target" |
350 | depends on BLK_DEV_DM | |
1da177e4 LT |
351 | ---help--- |
352 | Allow volume managers to mirror logical volumes, also | |
353 | needed for live data migration tools such as 'pvmove'. | |
354 | ||
5442851e MP |
355 | config DM_LOG_USERSPACE |
356 | tristate "Mirror userspace logging" | |
357 | depends on DM_MIRROR && NET | |
358 | select CONNECTOR | |
359 | ---help--- | |
360 | The userspace logging module provides a mechanism for | |
361 | relaying the dm-dirty-log API to userspace. Log designs | |
362 | which are more suited to userspace implementation (e.g. | |
363 | shared storage logs) or experimental logs can be implemented | |
364 | by leveraging this framework. | |
365 | ||
9d09e663 | 366 | config DM_RAID |
d9f691c3 | 367 | tristate "RAID 1/4/5/6/10 target" |
035220b3 | 368 | depends on BLK_DEV_DM |
7b81ef8b | 369 | select MD_RAID0 |
b12d437b | 370 | select MD_RAID1 |
d9f691c3 | 371 | select MD_RAID10 |
9d09e663 N |
372 | select MD_RAID456 |
373 | select BLK_DEV_MD | |
374 | ---help--- | |
d9f691c3 | 375 | A dm target that supports RAID1, RAID10, RAID4, RAID5 and RAID6 mappings |
9d09e663 N |
376 | |
377 | A RAID-5 set of N drives with a capacity of C MB per drive provides | |
378 | the capacity of C * (N - 1) MB, and protects against a failure | |
379 | of a single drive. For a given sector (row) number, (N - 1) drives | |
380 | contain data sectors, and one drive contains the parity protection. | |
381 | For a RAID-4 set, the parity blocks are present on a single drive, | |
382 | while a RAID-5 set distributes the parity across the drives in one | |
383 | of the available parity distribution methods. | |
384 | ||
385 | A RAID-6 set of N drives with a capacity of C MB per drive | |
386 | provides the capacity of C * (N - 2) MB, and protects | |
387 | against a failure of any two drives. For a given sector | |
388 | (row) number, (N - 2) drives contain data sectors, and two | |
389 | drives contains two independent redundancy syndromes. Like | |
390 | RAID-5, RAID-6 distributes the syndromes across the drives | |
391 | in one of the available parity distribution methods. | |
392 | ||
1da177e4 | 393 | config DM_ZERO |
0149e57f AK |
394 | tristate "Zero target" |
395 | depends on BLK_DEV_DM | |
1da177e4 LT |
396 | ---help--- |
397 | A target that discards writes, and returns all zeroes for | |
398 | reads. Useful in some recovery situations. | |
399 | ||
400 | config DM_MULTIPATH | |
0149e57f AK |
401 | tristate "Multipath target" |
402 | depends on BLK_DEV_DM | |
fe9233fb CS |
403 | # nasty syntax but means make DM_MULTIPATH independent |
404 | # of SCSI_DH if the latter isn't defined but if | |
405 | # it is, DM_MULTIPATH must depend on it. We get a build | |
406 | # error if SCSI_DH=m and DM_MULTIPATH=y | |
294ab783 | 407 | depends on !SCSI_DH || SCSI |
1da177e4 LT |
408 | ---help--- |
409 | Allow volume managers to support multipath hardware. | |
410 | ||
fd5e0339 KU |
411 | config DM_MULTIPATH_QL |
412 | tristate "I/O Path Selector based on the number of in-flight I/Os" | |
413 | depends on DM_MULTIPATH | |
414 | ---help--- | |
415 | This path selector is a dynamic load balancer which selects | |
416 | the path with the least number of in-flight I/Os. | |
417 | ||
418 | If unsure, say N. | |
419 | ||
f392ba88 KU |
420 | config DM_MULTIPATH_ST |
421 | tristate "I/O Path Selector based on the service time" | |
422 | depends on DM_MULTIPATH | |
423 | ---help--- | |
424 | This path selector is a dynamic load balancer which selects | |
425 | the path expected to complete the incoming I/O in the shortest | |
426 | time. | |
427 | ||
428 | If unsure, say N. | |
429 | ||
26b9f228 | 430 | config DM_DELAY |
d57916a0 AK |
431 | tristate "I/O delaying target" |
432 | depends on BLK_DEV_DM | |
26b9f228 HM |
433 | ---help--- |
434 | A target that delays reads and/or writes and can send | |
435 | them to different devices. Useful for testing. | |
436 | ||
437 | If unsure, say N. | |
438 | ||
e4f3fabd BG |
439 | config DM_DUST |
440 | tristate "Bad sector simulation target" | |
441 | depends on BLK_DEV_DM | |
442 | ---help--- | |
443 | A target that simulates bad sector behavior. | |
444 | Useful for testing. | |
445 | ||
446 | If unsure, say N. | |
447 | ||
6bbc923d HK |
448 | config DM_INIT |
449 | bool "DM \"dm-mod.create=\" parameter support" | |
450 | depends on BLK_DEV_DM=y | |
451 | ---help--- | |
452 | Enable "dm-mod.create=" parameter to create mapped devices at init time. | |
453 | This option is useful to allow mounting rootfs without requiring an | |
454 | initramfs. | |
455 | See Documentation/device-mapper/dm-init.txt for dm-mod.create="..." | |
456 | format. | |
457 | ||
458 | If unsure, say N. | |
459 | ||
51e5b2bd | 460 | config DM_UEVENT |
e0b215da AK |
461 | bool "DM uevents" |
462 | depends on BLK_DEV_DM | |
51e5b2bd MA |
463 | ---help--- |
464 | Generate udev events for DM events. | |
465 | ||
3407ef52 | 466 | config DM_FLAKEY |
d57916a0 AK |
467 | tristate "Flakey target" |
468 | depends on BLK_DEV_DM | |
3407ef52 JB |
469 | ---help--- |
470 | A target that intermittently fails I/O for debugging purposes. | |
471 | ||
a4ffc152 | 472 | config DM_VERITY |
d57916a0 AK |
473 | tristate "Verity target support" |
474 | depends on BLK_DEV_DM | |
a4ffc152 MP |
475 | select CRYPTO |
476 | select CRYPTO_HASH | |
477 | select DM_BUFIO | |
478 | ---help--- | |
479 | This device-mapper target creates a read-only device that | |
480 | transparently validates the data on one underlying device against | |
481 | a pre-generated tree of cryptographic checksums stored on a second | |
482 | device. | |
483 | ||
484 | You'll need to activate the digests you're going to use in the | |
485 | cryptoapi configuration. | |
486 | ||
487 | To compile this code as a module, choose M here: the module will | |
488 | be called dm-verity. | |
489 | ||
490 | If unsure, say N. | |
491 | ||
a739ff3f ST |
492 | config DM_VERITY_FEC |
493 | bool "Verity forward error correction support" | |
494 | depends on DM_VERITY | |
495 | select REED_SOLOMON | |
496 | select REED_SOLOMON_DEC8 | |
497 | ---help--- | |
498 | Add forward error correction support to dm-verity. This option | |
499 | makes it possible to use pre-generated error correction data to | |
500 | recover from corrupted blocks. | |
501 | ||
502 | If unsure, say N. | |
503 | ||
9d0eb0ab JR |
504 | config DM_SWITCH |
505 | tristate "Switch target support (EXPERIMENTAL)" | |
506 | depends on BLK_DEV_DM | |
507 | ---help--- | |
508 | This device-mapper target creates a device that supports an arbitrary | |
509 | mapping of fixed-size regions of I/O across a fixed set of paths. | |
510 | The path used for any specific region can be switched dynamically | |
511 | by sending the target a message. | |
512 | ||
513 | To compile this code as a module, choose M here: the module will | |
514 | be called dm-switch. | |
515 | ||
516 | If unsure, say N. | |
517 | ||
0e9cebe7 JB |
518 | config DM_LOG_WRITES |
519 | tristate "Log writes target support" | |
520 | depends on BLK_DEV_DM | |
521 | ---help--- | |
522 | This device-mapper target takes two devices, one device to use | |
523 | normally, one to log all write operations done to the first device. | |
524 | This is for use by file system developers wishing to verify that | |
57d42487 | 525 | their fs is writing a consistent file system at all times by allowing |
0e9cebe7 JB |
526 | them to replay the log in a variety of ways and to check the |
527 | contents. | |
528 | ||
529 | To compile this code as a module, choose M here: the module will | |
530 | be called dm-log-writes. | |
531 | ||
532 | If unsure, say N. | |
533 | ||
7eada909 | 534 | config DM_INTEGRITY |
7ab84db6 | 535 | tristate "Integrity target support" |
7eada909 MP |
536 | depends on BLK_DEV_DM |
537 | select BLK_DEV_INTEGRITY | |
538 | select DM_BUFIO | |
539 | select CRYPTO | |
540 | select ASYNC_XOR | |
541 | ---help--- | |
7ab84db6 MS |
542 | This device-mapper target emulates a block device that has |
543 | additional per-sector tags that can be used for storing | |
544 | integrity information. | |
545 | ||
546 | This integrity target is used with the dm-crypt target to | |
547 | provide authenticated disk encryption or it can be used | |
548 | standalone. | |
549 | ||
550 | To compile this code as a module, choose M here: the module will | |
551 | be called dm-integrity. | |
552 | ||
3b1a94c8 DLM |
553 | config DM_ZONED |
554 | tristate "Drive-managed zoned block device target support" | |
555 | depends on BLK_DEV_DM | |
556 | depends on BLK_DEV_ZONED | |
557 | ---help--- | |
558 | This device-mapper target takes a host-managed or host-aware zoned | |
559 | block device and exposes most of its capacity as a regular block | |
560 | device (drive-managed zoned block device) without any write | |
561 | constraints. This is mainly intended for use with file systems that | |
562 | do not natively support zoned block devices but still want to | |
563 | benefit from the increased capacity offered by SMR disks. Other uses | |
564 | by applications using raw block devices (for example object stores) | |
565 | are also possible. | |
566 | ||
567 | To compile this code as a module, choose M here: the module will | |
568 | be called dm-zoned. | |
569 | ||
7ab84db6 | 570 | If unsure, say N. |
7eada909 | 571 | |
afd44034 | 572 | endif # MD |