1 # SPDX-License-Identifier: GPL-2.0 1 # SPDX-License-Identifier: GPL-2.0
2 # 2 #
3 # Block layer core configuration 3 # Block layer core configuration
4 # 4 #
5 menuconfig BLOCK 5 menuconfig BLOCK
6 bool "Enable the block layer" if EXPERT 6 bool "Enable the block layer" if EXPERT
7 default y 7 default y
8 select FS_IOMAP <<
9 select SBITMAP 8 select SBITMAP
>> 9 select SRCU
10 help 10 help
11 Provide block layer support for the k 11 Provide block layer support for the kernel.
12 12
13 Disable this option to remove the blo 13 Disable this option to remove the block layer support from the
14 kernel. This may be useful for embedd 14 kernel. This may be useful for embedded devices.
15 15
16 If this option is disabled: 16 If this option is disabled:
17 17
18 - block device files will become un 18 - block device files will become unusable
19 - some filesystems (such as ext3) w 19 - some filesystems (such as ext3) will become unavailable.
20 20
21 Also, SCSI character devices and USB 21 Also, SCSI character devices and USB storage will be disabled since
22 they make use of various block layer 22 they make use of various block layer definitions and facilities.
23 23
24 Say Y here unless you know you really 24 Say Y here unless you know you really don't want to mount disks and
25 suchlike. 25 suchlike.
26 26
27 if BLOCK 27 if BLOCK
28 28
29 config BLOCK_LEGACY_AUTOLOAD <<
30 bool "Legacy autoloading support" <<
31 default y <<
32 help <<
33 Enable loading modules and creating <<
34 accesses through their device specia <<
35 feature and makes no sense in a udev <<
36 created on demand, but scripts that <<
37 then call losetup might rely on this <<
38 <<
39 config BLK_RQ_ALLOC_TIME 29 config BLK_RQ_ALLOC_TIME
40 bool 30 bool
41 31
42 config BLK_CGROUP_RWSTAT !! 32 config BLK_SCSI_REQUEST
43 bool 33 bool
44 34
45 config BLK_CGROUP_PUNT_BIO !! 35 config BLK_DEV_BSG
46 bool !! 36 bool "Block layer SG support v4"
>> 37 default y
>> 38 select BLK_SCSI_REQUEST
>> 39 help
>> 40 Saying Y here will enable generic SG (SCSI generic) v4 support
>> 41 for any block device.
47 42
48 config BLK_DEV_BSG_COMMON !! 43 Unlike SG v3 (aka block/scsi_ioctl.c drivers/scsi/sg.c), SG v4
49 tristate !! 44 can handle complicated SCSI commands: tagged variable length cdbs
>> 45 with bidirectional data transfers and generic request/response
>> 46 protocols (e.g. Task Management Functions and SMP in Serial
>> 47 Attached SCSI).
50 48
51 config BLK_ICQ !! 49 This option is required by recent UDEV versions to properly
52 bool !! 50 access device serial numbers, etc.
>> 51
>> 52 If unsure, say Y.
53 53
54 config BLK_DEV_BSGLIB 54 config BLK_DEV_BSGLIB
55 bool "Block layer SG support v4 helper 55 bool "Block layer SG support v4 helper lib"
56 select BLK_DEV_BSG_COMMON !! 56 select BLK_DEV_BSG
>> 57 select BLK_SCSI_REQUEST
57 help 58 help
58 Subsystems will normally enable this 59 Subsystems will normally enable this if needed. Users will not
59 normally need to manually enable thi 60 normally need to manually enable this.
60 61
61 If unsure, say N. 62 If unsure, say N.
62 63
63 config BLK_DEV_INTEGRITY 64 config BLK_DEV_INTEGRITY
64 bool "Block layer data integrity suppo 65 bool "Block layer data integrity support"
65 select CRC_T10DIF !! 66 select CRC_T10DIF if BLK_DEV_INTEGRITY
66 select CRC64_ROCKSOFT !! 67 ---help---
67 help <<
68 Some storage devices allow extra infor 68 Some storage devices allow extra information to be
69 stored/retrieved to help protect the d 69 stored/retrieved to help protect the data. The block layer
70 data integrity option provides hooks w 70 data integrity option provides hooks which can be used by
71 filesystems to ensure better data inte 71 filesystems to ensure better data integrity.
72 72
73 Say yes here if you have a storage dev 73 Say yes here if you have a storage device that provides the
74 T10/SCSI Data Integrity Field or the T 74 T10/SCSI Data Integrity Field or the T13/ATA External Path
75 Protection. If in doubt, say N. 75 Protection. If in doubt, say N.
76 76
77 config BLK_DEV_WRITE_MOUNTED <<
78 bool "Allow writing to mounted block d <<
79 default y <<
80 help <<
81 When a block device is mounted, writin <<
82 likely going to cause filesystem corru <<
83 crash the kernel in this way since the <<
84 of detecting these writes to buffer ca <<
85 integrity. However there are some setu <<
86 like running fsck on read-only mounted <<
87 features on mounted ext4 filesystem, a <<
88 kernel will prevent processes from wri <<
89 mounted by filesystems which provides <<
90 privileged processes and generally mak <<
91 filesystem drivers. Note however that <<
92 underlying device(s) from being modifi <<
93 directly submitting SCSI commands or t <<
94 storage stack. If in doubt, say Y. The <<
95 with the bdev_allow_write_mounted boot <<
96 <<
97 config BLK_DEV_ZONED 77 config BLK_DEV_ZONED
98 bool "Zoned block device support" 78 bool "Zoned block device support"
99 help !! 79 select MQ_IOSCHED_DEADLINE
>> 80 ---help---
100 Block layer zoned block device support 81 Block layer zoned block device support. This option enables
101 support for ZAC/ZBC/ZNS host-managed a !! 82 support for ZAC/ZBC host-managed and host-aware zoned block devices.
102 devices. <<
103 83
104 Say yes here if you have a ZAC, ZBC, o !! 84 Say yes here if you have a ZAC or ZBC storage device.
105 85
106 config BLK_DEV_THROTTLING 86 config BLK_DEV_THROTTLING
107 bool "Block layer bio throttling suppo 87 bool "Block layer bio throttling support"
108 depends on BLK_CGROUP !! 88 depends on BLK_CGROUP=y
109 select BLK_CGROUP_RWSTAT !! 89 ---help---
110 help <<
111 Block layer bio throttling support. It 90 Block layer bio throttling support. It can be used to limit
112 the IO rate to a device. IO rate polic 91 the IO rate to a device. IO rate policies are per cgroup and
113 one needs to mount and use blkio cgrou 92 one needs to mount and use blkio cgroup controller for creating
114 cgroups and specifying per device IO r 93 cgroups and specifying per device IO rate policies.
115 94
116 See Documentation/admin-guide/cgroup-v 95 See Documentation/admin-guide/cgroup-v1/blkio-controller.rst for more information.
117 96
>> 97 config BLK_DEV_THROTTLING_LOW
>> 98 bool "Block throttling .low limit interface support (EXPERIMENTAL)"
>> 99 depends on BLK_DEV_THROTTLING
>> 100 ---help---
>> 101 Add .low limit interface for block throttling. The low limit is a best
>> 102 effort limit to prioritize cgroups. Depending on the setting, the limit
>> 103 can be used to protect cgroups in terms of bandwidth/iops and better
>> 104 utilize disk resource.
>> 105
>> 106 Note, this is an experimental interface and could be changed someday.
>> 107
>> 108 config BLK_CMDLINE_PARSER
>> 109 bool "Block device command line partition parser"
>> 110 ---help---
>> 111 Enabling this option allows you to specify the partition layout from
>> 112 the kernel boot args. This is typically of use for embedded devices
>> 113 which don't otherwise have any standardized method for listing the
>> 114 partitions on a block device.
>> 115
>> 116 See Documentation/block/cmdline-partition.rst for more information.
>> 117
118 config BLK_WBT 118 config BLK_WBT
119 bool "Enable support for block device 119 bool "Enable support for block device writeback throttling"
120 help !! 120 ---help---
121 Enabling this option enables the block 121 Enabling this option enables the block layer to throttle buffered
122 background writeback from the VM, maki 122 background writeback from the VM, making it more smooth and having
123 less impact on foreground operations. 123 less impact on foreground operations. The throttling is done
124 dynamically on an algorithm loosely ba 124 dynamically on an algorithm loosely based on CoDel, factoring in
125 the realtime performance of the disk. 125 the realtime performance of the disk.
126 126
127 config BLK_WBT_MQ <<
128 bool "Enable writeback throttling by d <<
129 default y <<
130 depends on BLK_WBT <<
131 help <<
132 Enable writeback throttling by default <<
133 <<
134 config BLK_CGROUP_IOLATENCY 127 config BLK_CGROUP_IOLATENCY
135 bool "Enable support for latency based 128 bool "Enable support for latency based cgroup IO protection"
136 depends on BLK_CGROUP !! 129 depends on BLK_CGROUP=y
137 help !! 130 ---help---
138 Enabling this option enables the .late 131 Enabling this option enables the .latency interface for IO throttling.
139 The IO controller will attempt to main 132 The IO controller will attempt to maintain average IO latencies below
140 the configured latency target, throttl 133 the configured latency target, throttling anybody with a higher latency
141 target than the victimized group. 134 target than the victimized group.
142 135
143 Note, this is an experimental interfac 136 Note, this is an experimental interface and could be changed someday.
144 137
145 config BLK_CGROUP_FC_APPID <<
146 bool "Enable support to track FC I/O T <<
147 depends on BLK_CGROUP && NVME_FC <<
148 help <<
149 Enabling this option enables the sup <<
150 cgroup applications. It enables the <<
151 identify, monitor, and handle FC tra <<
152 application specific identification <<
153 <<
154 config BLK_CGROUP_IOCOST 138 config BLK_CGROUP_IOCOST
155 bool "Enable support for cost model ba 139 bool "Enable support for cost model based cgroup IO controller"
156 depends on BLK_CGROUP !! 140 depends on BLK_CGROUP=y
157 select BLK_RQ_ALLOC_TIME 141 select BLK_RQ_ALLOC_TIME
158 help !! 142 ---help---
159 Enabling this option enables the .weig 143 Enabling this option enables the .weight interface for cost
160 model based proportional IO control. 144 model based proportional IO control. The IO controller
161 distributes IO capacity between differ 145 distributes IO capacity between different groups based on
162 their share of the overall weight dist 146 their share of the overall weight distribution.
163 147
164 config BLK_CGROUP_IOPRIO !! 148 config BLK_WBT_MQ
165 bool "Cgroup I/O controller for assign !! 149 bool "Multiqueue writeback throttling"
166 depends on BLK_CGROUP !! 150 default y
167 help !! 151 depends on BLK_WBT
168 Enable the .prio interface for assigni !! 152 ---help---
169 requests. The I/O priority class affec !! 153 Enable writeback throttling by default on multiqueue devices.
170 scheduler and block devices process re !! 154 Multiqueue currently doesn't have support for IO scheduling,
171 and some block devices support I/O pri !! 155 enabling this option is recommended.
172 156
173 config BLK_DEBUG_FS 157 config BLK_DEBUG_FS
174 bool "Block layer debugging informatio 158 bool "Block layer debugging information in debugfs"
175 default y 159 default y
176 depends on DEBUG_FS 160 depends on DEBUG_FS
177 help !! 161 ---help---
178 Include block layer debugging informat 162 Include block layer debugging information in debugfs. This information
179 is mostly useful for kernel developers 163 is mostly useful for kernel developers, but it doesn't incur any cost
180 at runtime. 164 at runtime.
181 165
182 Unless you are building a kernel for a 166 Unless you are building a kernel for a tiny system, you should
183 say Y here. 167 say Y here.
184 168
>> 169 config BLK_DEBUG_FS_ZONED
>> 170 bool
>> 171 default BLK_DEBUG_FS && BLK_DEV_ZONED
>> 172
185 config BLK_SED_OPAL 173 config BLK_SED_OPAL
186 bool "Logic for interfacing with Opal 174 bool "Logic for interfacing with Opal enabled SEDs"
187 depends on KEYS !! 175 ---help---
188 select PSERIES_PLPKS if PPC_PSERIES <<
189 select PSERIES_PLPKS_SED if PPC_PSERIE <<
190 help <<
191 Builds Logic for interfacing with Opal 176 Builds Logic for interfacing with Opal enabled controllers.
192 Enabling this option enables users to 177 Enabling this option enables users to setup/unlock/lock
193 Locking ranges for SED devices using t 178 Locking ranges for SED devices using the Opal protocol.
194 179
195 config BLK_INLINE_ENCRYPTION !! 180 menu "Partition Types"
196 bool "Enable inline encryption support <<
197 help <<
198 Build the blk-crypto subsystem. Enab <<
199 block layer handle encryption, so us <<
200 advantage of inline encryption hardw <<
201 <<
202 config BLK_INLINE_ENCRYPTION_FALLBACK <<
203 bool "Enable crypto API fallback for b <<
204 depends on BLK_INLINE_ENCRYPTION <<
205 select CRYPTO <<
206 select CRYPTO_SKCIPHER <<
207 help <<
208 Enabling this lets the block layer h <<
209 by falling back to the kernel crypto <<
210 encryption hardware is not present. <<
211 181
212 source "block/partitions/Kconfig" 182 source "block/partitions/Kconfig"
213 183
214 config BLK_MQ_PCI !! 184 endmenu
215 def_bool PCI <<
216 185
217 config BLK_MQ_VIRTIO !! 186 endif # BLOCK
>> 187
>> 188 config BLOCK_COMPAT
218 bool 189 bool
219 depends on VIRTIO !! 190 depends on BLOCK && COMPAT
220 default y 191 default y
221 192
222 config BLK_PM !! 193 config BLK_MQ_PCI
223 def_bool PM !! 194 bool
>> 195 depends on BLOCK && PCI
>> 196 default y
224 197
225 # do not use in new code !! 198 config BLK_MQ_VIRTIO
226 config BLOCK_HOLDER_DEPRECATED <<
227 bool 199 bool
>> 200 depends on BLOCK && VIRTIO
>> 201 default y
228 202
229 config BLK_MQ_STACKING !! 203 config BLK_MQ_RDMA
230 bool 204 bool
>> 205 depends on BLOCK && INFINIBAND
>> 206 default y
231 207
232 source "block/Kconfig.iosched" !! 208 config BLK_PM
>> 209 def_bool BLOCK && PM
233 210
234 endif # BLOCK !! 211 source "block/Kconfig.iosched"
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.