| Kconfig (51acbcec6c42b24482bac18e42befc822524535d) | Kconfig (d57916a00fd749ccd354a7f754c2aba98f86d064) |
|---|---|
| 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 --- 140 unchanged lines hidden (view full) --- 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 | 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 --- 140 unchanged lines hidden (view full) --- 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 |
|
| 157config MD_MULTIPATH 158 tristate "Multipath I/O support" 159 depends on BLK_DEV_MD 160 help 161 MD_MULTIPATH provides a simple multi-path personality for use 162 the MD framework. It is not under active development. New 163 projects should consider using DM_MULTIPATH which has more 164 features and more testing. --- 29 unchanged lines hidden (view full) --- 194 depends on BLK_DEV_DM 195 ---help--- 196 Enable this for messages that may help debug device-mapper problems. 197 198 If unsure, say N. 199 200config DM_BUFIO 201 tristate | 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. --- 29 unchanged lines hidden (view full) --- 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 |
| 202 depends on BLK_DEV_DM && EXPERIMENTAL | 213 depends on BLK_DEV_DM |
| 203 ---help--- 204 This interface allows you to do buffered I/O on a device and acts 205 as a cache, holding recently-read blocks in memory and performing 206 delayed writes. 207 208config DM_BIO_PRISON 209 tristate | 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 |
| 210 depends on BLK_DEV_DM && EXPERIMENTAL | 221 depends on BLK_DEV_DM |
| 211 ---help--- 212 Some bio locking schemes used by other device-mapper targets 213 including thin provisioning. 214 215source "drivers/md/persistent-data/Kconfig" 216 217config DM_CRYPT 218 tristate "Crypt target support" --- 16 unchanged lines hidden (view full) --- 235 236config DM_SNAPSHOT 237 tristate "Snapshot target" 238 depends on BLK_DEV_DM 239 ---help--- 240 Allow volume managers to take writable snapshots of a device. 241 242config DM_THIN_PROVISIONING | 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" --- 16 unchanged lines hidden (view full) --- 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 |
| 243 tristate "Thin provisioning target (EXPERIMENTAL)" 244 depends on BLK_DEV_DM && EXPERIMENTAL | 254 tristate "Thin provisioning target" 255 depends on BLK_DEV_DM |
| 245 select DM_PERSISTENT_DATA 246 select DM_BIO_PRISON 247 ---help--- 248 Provides thin provisioning and snapshots that share a data store. 249 250config DM_DEBUG_BLOCK_STACK_TRACING 251 boolean "Keep stack trace of thin provisioning block lock holders" 252 depends on STACKTRACE_SUPPORT && DM_THIN_PROVISIONING --- 33 unchanged lines hidden (view full) --- 286 provides the capacity of C * (N - 2) MB, and protects 287 against a failure of any two drives. For a given sector 288 (row) number, (N - 2) drives contain data sectors, and two 289 drives contains two independent redundancy syndromes. Like 290 RAID-5, RAID-6 distributes the syndromes across the drives 291 in one of the available parity distribution methods. 292 293config DM_LOG_USERSPACE | 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 --- 33 unchanged lines hidden (view full) --- 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 |
| 294 tristate "Mirror userspace logging (EXPERIMENTAL)" 295 depends on DM_MIRROR && EXPERIMENTAL && NET | 305 tristate "Mirror userspace logging" 306 depends on DM_MIRROR && NET |
| 296 select CONNECTOR 297 ---help--- 298 The userspace logging module provides a mechanism for 299 relaying the dm-dirty-log API to userspace. Log designs 300 which are more suited to userspace implementation (e.g. 301 shared storage logs) or experimental logs can be implemented 302 by leveraging this framework. 303 --- 30 unchanged lines hidden (view full) --- 334 ---help--- 335 This path selector is a dynamic load balancer which selects 336 the path expected to complete the incoming I/O in the shortest 337 time. 338 339 If unsure, say N. 340 341config DM_DELAY | 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 --- 30 unchanged lines hidden (view full) --- 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 |
| 342 tristate "I/O delaying target (EXPERIMENTAL)" 343 depends on BLK_DEV_DM && EXPERIMENTAL | 353 tristate "I/O delaying target" 354 depends on BLK_DEV_DM |
| 344 ---help--- 345 A target that delays reads and/or writes and can send 346 them to different devices. Useful for testing. 347 348 If unsure, say N. 349 350config DM_UEVENT 351 bool "DM uevents" 352 depends on BLK_DEV_DM 353 ---help--- 354 Generate udev events for DM events. 355 356config DM_FLAKEY | 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 |
| 357 tristate "Flakey target (EXPERIMENTAL)" 358 depends on BLK_DEV_DM && EXPERIMENTAL | 368 tristate "Flakey target" 369 depends on BLK_DEV_DM |
| 359 ---help--- 360 A target that intermittently fails I/O for debugging purposes. 361 362config DM_VERITY | 370 ---help--- 371 A target that intermittently fails I/O for debugging purposes. 372 373config DM_VERITY |
| 363 tristate "Verity target support (EXPERIMENTAL)" 364 depends on BLK_DEV_DM && EXPERIMENTAL | 374 tristate "Verity target support" 375 depends on BLK_DEV_DM |
| 365 select CRYPTO 366 select CRYPTO_HASH 367 select DM_BUFIO 368 ---help--- 369 This device-mapper target creates a read-only device that 370 transparently validates the data on one underlying device against 371 a pre-generated tree of cryptographic checksums stored on a second 372 device. 373 374 You'll need to activate the digests you're going to use in the 375 cryptoapi configuration. 376 377 To compile this code as a module, choose M here: the module will 378 be called dm-verity. 379 380 If unsure, say N. 381 382endif # MD | 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 |