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 8 select FS_IOMAP
9 select SBITMAP 9 select SBITMAP
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 29 config BLOCK_LEGACY_AUTOLOAD
30 bool "Legacy autoloading support" 30 bool "Legacy autoloading support"
31 default y 31 default y
32 help 32 help
33 Enable loading modules and creating 33 Enable loading modules and creating block device instances based on
34 accesses through their device specia 34 accesses through their device special file. This is a historic Linux
35 feature and makes no sense in a udev 35 feature and makes no sense in a udev world where device files are
36 created on demand, but scripts that 36 created on demand, but scripts that manually create device nodes and
37 then call losetup might rely on this 37 then call losetup might rely on this behavior.
38 38
39 config BLK_RQ_ALLOC_TIME 39 config BLK_RQ_ALLOC_TIME
40 bool 40 bool
41 41
42 config BLK_CGROUP_RWSTAT 42 config BLK_CGROUP_RWSTAT
43 bool 43 bool
44 44
45 config BLK_CGROUP_PUNT_BIO 45 config BLK_CGROUP_PUNT_BIO
46 bool 46 bool
47 47
48 config BLK_DEV_BSG_COMMON 48 config BLK_DEV_BSG_COMMON
49 tristate 49 tristate
50 50
51 config BLK_ICQ 51 config BLK_ICQ
52 bool 52 bool
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_COMMON
57 help 57 help
58 Subsystems will normally enable this 58 Subsystems will normally enable this if needed. Users will not
59 normally need to manually enable thi 59 normally need to manually enable this.
60 60
61 If unsure, say N. 61 If unsure, say N.
62 62
63 config BLK_DEV_INTEGRITY 63 config BLK_DEV_INTEGRITY
64 bool "Block layer data integrity suppo 64 bool "Block layer data integrity support"
65 select CRC_T10DIF <<
66 select CRC64_ROCKSOFT <<
67 help 65 help
68 Some storage devices allow extra infor 66 Some storage devices allow extra information to be
69 stored/retrieved to help protect the d 67 stored/retrieved to help protect the data. The block layer
70 data integrity option provides hooks w 68 data integrity option provides hooks which can be used by
71 filesystems to ensure better data inte 69 filesystems to ensure better data integrity.
72 70
73 Say yes here if you have a storage dev 71 Say yes here if you have a storage device that provides the
74 T10/SCSI Data Integrity Field or the T 72 T10/SCSI Data Integrity Field or the T13/ATA External Path
75 Protection. If in doubt, say N. 73 Protection. If in doubt, say N.
76 74
>> 75 config BLK_DEV_INTEGRITY_T10
>> 76 tristate
>> 77 depends on BLK_DEV_INTEGRITY
>> 78 select CRC_T10DIF
>> 79 select CRC64_ROCKSOFT
>> 80
77 config BLK_DEV_WRITE_MOUNTED 81 config BLK_DEV_WRITE_MOUNTED
78 bool "Allow writing to mounted block d 82 bool "Allow writing to mounted block devices"
79 default y 83 default y
80 help 84 help
81 When a block device is mounted, writin 85 When a block device is mounted, writing to its buffer cache is very
82 likely going to cause filesystem corru 86 likely going to cause filesystem corruption. It is also rather easy to
83 crash the kernel in this way since the 87 crash the kernel in this way since the filesystem has no practical way
84 of detecting these writes to buffer ca 88 of detecting these writes to buffer cache and verifying its metadata
85 integrity. However there are some setu 89 integrity. However there are some setups that need this capability
86 like running fsck on read-only mounted 90 like running fsck on read-only mounted root device, modifying some
87 features on mounted ext4 filesystem, a 91 features on mounted ext4 filesystem, and similar. If you say N, the
88 kernel will prevent processes from wri 92 kernel will prevent processes from writing to block devices that are
89 mounted by filesystems which provides 93 mounted by filesystems which provides some more protection from runaway
90 privileged processes and generally mak 94 privileged processes and generally makes it much harder to crash
91 filesystem drivers. Note however that 95 filesystem drivers. Note however that this does not prevent
92 underlying device(s) from being modifi 96 underlying device(s) from being modified by other means, e.g. by
93 directly submitting SCSI commands or t 97 directly submitting SCSI commands or through access to lower layers of
94 storage stack. If in doubt, say Y. The 98 storage stack. If in doubt, say Y. The configuration can be overridden
95 with the bdev_allow_write_mounted boot 99 with the bdev_allow_write_mounted boot option.
96 100
97 config BLK_DEV_ZONED 101 config BLK_DEV_ZONED
98 bool "Zoned block device support" 102 bool "Zoned block device support"
>> 103 select MQ_IOSCHED_DEADLINE
99 help 104 help
100 Block layer zoned block device support 105 Block layer zoned block device support. This option enables
101 support for ZAC/ZBC/ZNS host-managed a 106 support for ZAC/ZBC/ZNS host-managed and host-aware zoned block
102 devices. 107 devices.
103 108
104 Say yes here if you have a ZAC, ZBC, o 109 Say yes here if you have a ZAC, ZBC, or ZNS storage device.
105 110
106 config BLK_DEV_THROTTLING 111 config BLK_DEV_THROTTLING
107 bool "Block layer bio throttling suppo 112 bool "Block layer bio throttling support"
108 depends on BLK_CGROUP 113 depends on BLK_CGROUP
109 select BLK_CGROUP_RWSTAT 114 select BLK_CGROUP_RWSTAT
110 help 115 help
111 Block layer bio throttling support. It 116 Block layer bio throttling support. It can be used to limit
112 the IO rate to a device. IO rate polic 117 the IO rate to a device. IO rate policies are per cgroup and
113 one needs to mount and use blkio cgrou 118 one needs to mount and use blkio cgroup controller for creating
114 cgroups and specifying per device IO r 119 cgroups and specifying per device IO rate policies.
115 120
116 See Documentation/admin-guide/cgroup-v 121 See Documentation/admin-guide/cgroup-v1/blkio-controller.rst for more information.
117 122
>> 123 config BLK_DEV_THROTTLING_LOW
>> 124 bool "Block throttling .low limit interface support (EXPERIMENTAL)"
>> 125 depends on BLK_DEV_THROTTLING
>> 126 help
>> 127 Add .low limit interface for block throttling. The low limit is a best
>> 128 effort limit to prioritize cgroups. Depending on the setting, the limit
>> 129 can be used to protect cgroups in terms of bandwidth/iops and better
>> 130 utilize disk resource.
>> 131
>> 132 Note, this is an experimental interface and could be changed someday.
>> 133
118 config BLK_WBT 134 config BLK_WBT
119 bool "Enable support for block device 135 bool "Enable support for block device writeback throttling"
120 help 136 help
121 Enabling this option enables the block 137 Enabling this option enables the block layer to throttle buffered
122 background writeback from the VM, maki 138 background writeback from the VM, making it more smooth and having
123 less impact on foreground operations. 139 less impact on foreground operations. The throttling is done
124 dynamically on an algorithm loosely ba 140 dynamically on an algorithm loosely based on CoDel, factoring in
125 the realtime performance of the disk. 141 the realtime performance of the disk.
126 142
127 config BLK_WBT_MQ 143 config BLK_WBT_MQ
128 bool "Enable writeback throttling by d 144 bool "Enable writeback throttling by default"
129 default y 145 default y
130 depends on BLK_WBT 146 depends on BLK_WBT
131 help 147 help
132 Enable writeback throttling by default 148 Enable writeback throttling by default for request-based block devices.
133 149
134 config BLK_CGROUP_IOLATENCY 150 config BLK_CGROUP_IOLATENCY
135 bool "Enable support for latency based 151 bool "Enable support for latency based cgroup IO protection"
136 depends on BLK_CGROUP 152 depends on BLK_CGROUP
137 help 153 help
138 Enabling this option enables the .late 154 Enabling this option enables the .latency interface for IO throttling.
139 The IO controller will attempt to main 155 The IO controller will attempt to maintain average IO latencies below
140 the configured latency target, throttl 156 the configured latency target, throttling anybody with a higher latency
141 target than the victimized group. 157 target than the victimized group.
142 158
143 Note, this is an experimental interfac 159 Note, this is an experimental interface and could be changed someday.
144 160
145 config BLK_CGROUP_FC_APPID 161 config BLK_CGROUP_FC_APPID
146 bool "Enable support to track FC I/O T 162 bool "Enable support to track FC I/O Traffic across cgroup applications"
147 depends on BLK_CGROUP && NVME_FC 163 depends on BLK_CGROUP && NVME_FC
148 help 164 help
149 Enabling this option enables the sup 165 Enabling this option enables the support to track FC I/O traffic across
150 cgroup applications. It enables the 166 cgroup applications. It enables the Fabric and the storage targets to
151 identify, monitor, and handle FC tra 167 identify, monitor, and handle FC traffic based on VM tags by inserting
152 application specific identification 168 application specific identification into the FC frame.
153 169
154 config BLK_CGROUP_IOCOST 170 config BLK_CGROUP_IOCOST
155 bool "Enable support for cost model ba 171 bool "Enable support for cost model based cgroup IO controller"
156 depends on BLK_CGROUP 172 depends on BLK_CGROUP
157 select BLK_RQ_ALLOC_TIME 173 select BLK_RQ_ALLOC_TIME
158 help 174 help
159 Enabling this option enables the .weig 175 Enabling this option enables the .weight interface for cost
160 model based proportional IO control. 176 model based proportional IO control. The IO controller
161 distributes IO capacity between differ 177 distributes IO capacity between different groups based on
162 their share of the overall weight dist 178 their share of the overall weight distribution.
163 179
164 config BLK_CGROUP_IOPRIO 180 config BLK_CGROUP_IOPRIO
165 bool "Cgroup I/O controller for assign 181 bool "Cgroup I/O controller for assigning an I/O priority class"
166 depends on BLK_CGROUP 182 depends on BLK_CGROUP
167 help 183 help
168 Enable the .prio interface for assigni 184 Enable the .prio interface for assigning an I/O priority class to
169 requests. The I/O priority class affec 185 requests. The I/O priority class affects the order in which an I/O
170 scheduler and block devices process re 186 scheduler and block devices process requests. Only some I/O schedulers
171 and some block devices support I/O pri 187 and some block devices support I/O priorities.
172 188
173 config BLK_DEBUG_FS 189 config BLK_DEBUG_FS
174 bool "Block layer debugging informatio 190 bool "Block layer debugging information in debugfs"
175 default y 191 default y
176 depends on DEBUG_FS 192 depends on DEBUG_FS
177 help 193 help
178 Include block layer debugging informat 194 Include block layer debugging information in debugfs. This information
179 is mostly useful for kernel developers 195 is mostly useful for kernel developers, but it doesn't incur any cost
180 at runtime. 196 at runtime.
181 197
182 Unless you are building a kernel for a 198 Unless you are building a kernel for a tiny system, you should
183 say Y here. 199 say Y here.
>> 200
>> 201 config BLK_DEBUG_FS_ZONED
>> 202 bool
>> 203 default BLK_DEBUG_FS && BLK_DEV_ZONED
184 204
185 config BLK_SED_OPAL 205 config BLK_SED_OPAL
186 bool "Logic for interfacing with Opal 206 bool "Logic for interfacing with Opal enabled SEDs"
187 depends on KEYS 207 depends on KEYS
188 select PSERIES_PLPKS if PPC_PSERIES 208 select PSERIES_PLPKS if PPC_PSERIES
189 select PSERIES_PLPKS_SED if PPC_PSERIE 209 select PSERIES_PLPKS_SED if PPC_PSERIES
190 help 210 help
191 Builds Logic for interfacing with Opal 211 Builds Logic for interfacing with Opal enabled controllers.
192 Enabling this option enables users to 212 Enabling this option enables users to setup/unlock/lock
193 Locking ranges for SED devices using t 213 Locking ranges for SED devices using the Opal protocol.
194 214
195 config BLK_INLINE_ENCRYPTION 215 config BLK_INLINE_ENCRYPTION
196 bool "Enable inline encryption support 216 bool "Enable inline encryption support in block layer"
197 help 217 help
198 Build the blk-crypto subsystem. Enab 218 Build the blk-crypto subsystem. Enabling this lets the
199 block layer handle encryption, so us 219 block layer handle encryption, so users can take
200 advantage of inline encryption hardw 220 advantage of inline encryption hardware if present.
201 221
202 config BLK_INLINE_ENCRYPTION_FALLBACK 222 config BLK_INLINE_ENCRYPTION_FALLBACK
203 bool "Enable crypto API fallback for b 223 bool "Enable crypto API fallback for blk-crypto"
204 depends on BLK_INLINE_ENCRYPTION 224 depends on BLK_INLINE_ENCRYPTION
205 select CRYPTO 225 select CRYPTO
206 select CRYPTO_SKCIPHER 226 select CRYPTO_SKCIPHER
207 help 227 help
208 Enabling this lets the block layer h 228 Enabling this lets the block layer handle inline encryption
209 by falling back to the kernel crypto 229 by falling back to the kernel crypto API when inline
210 encryption hardware is not present. 230 encryption hardware is not present.
211 231
212 source "block/partitions/Kconfig" 232 source "block/partitions/Kconfig"
213 233
214 config BLK_MQ_PCI 234 config BLK_MQ_PCI
215 def_bool PCI 235 def_bool PCI
216 236
217 config BLK_MQ_VIRTIO 237 config BLK_MQ_VIRTIO
218 bool 238 bool
219 depends on VIRTIO 239 depends on VIRTIO
220 default y 240 default y
221 241
222 config BLK_PM 242 config BLK_PM
223 def_bool PM 243 def_bool PM
224 244
225 # do not use in new code 245 # do not use in new code
226 config BLOCK_HOLDER_DEPRECATED 246 config BLOCK_HOLDER_DEPRECATED
227 bool 247 bool
228 248
229 config BLK_MQ_STACKING 249 config BLK_MQ_STACKING
230 bool 250 bool
231 251
232 source "block/Kconfig.iosched" 252 source "block/Kconfig.iosched"
233 253
234 endif # BLOCK 254 endif # BLOCK
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.