Kconfig (87a0b2fafc09766d8c55461a18345a1cfb10a7fe) | Kconfig (248c793359daacd826a7507a258ffe41653efef7) |
---|---|
1# SPDX-License-Identifier: GPL-2.0-only 2# 3# Block device driver configuration 4# 5 6menuconfig MD 7 bool "Multiple devices driver support (RAID and LVM)" 8 depends on BLOCK --- 190 unchanged lines hidden (view full) --- 199 200config BLK_DEV_DM_BUILTIN 201 bool 202 203config BLK_DEV_DM 204 tristate "Device mapper support" 205 select BLOCK_HOLDER_DEPRECATED if SYSFS 206 select BLK_DEV_DM_BUILTIN | 1# SPDX-License-Identifier: GPL-2.0-only 2# 3# Block device driver configuration 4# 5 6menuconfig MD 7 bool "Multiple devices driver support (RAID and LVM)" 8 depends on BLOCK --- 190 unchanged lines hidden (view full) --- 199 200config BLK_DEV_DM_BUILTIN 201 bool 202 203config BLK_DEV_DM 204 tristate "Device mapper support" 205 select BLOCK_HOLDER_DEPRECATED if SYSFS 206 select BLK_DEV_DM_BUILTIN |
207 select BLK_MQ_STACKING |
|
207 depends on DAX || DAX=n 208 help 209 Device-mapper is a low level volume manager. It works by allowing 210 people to specify mappings for ranges of logical sectors. Various 211 mapping types are available, in addition people may write their own 212 modules containing custom mappings if they wish. 213 214 Higher level volume managers such as LVM2 use this driver. --- 441 unchanged lines hidden --- | 208 depends on DAX || DAX=n 209 help 210 Device-mapper is a low level volume manager. It works by allowing 211 people to specify mappings for ranges of logical sectors. Various 212 mapping types are available, in addition people may write their own 213 modules containing custom mappings if they wish. 214 215 Higher level volume managers such as LVM2 use this driver. --- 441 unchanged lines hidden --- |