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 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 <<
46 bool <<
47 <<
48 config BLK_DEV_BSG_COMMON 45 config BLK_DEV_BSG_COMMON
49 tristate 46 tristate
50 47
51 config BLK_ICQ 48 config BLK_ICQ
52 bool 49 bool
53 50
54 config BLK_DEV_BSGLIB 51 config BLK_DEV_BSGLIB
55 bool "Block layer SG support v4 helper 52 bool "Block layer SG support v4 helper lib"
56 select BLK_DEV_BSG_COMMON 53 select BLK_DEV_BSG_COMMON
57 help 54 help
58 Subsystems will normally enable this 55 Subsystems will normally enable this if needed. Users will not
59 normally need to manually enable thi 56 normally need to manually enable this.
60 57
61 If unsure, say N. 58 If unsure, say N.
62 59
63 config BLK_DEV_INTEGRITY 60 config BLK_DEV_INTEGRITY
64 bool "Block layer data integrity suppo 61 bool "Block layer data integrity support"
65 select CRC_T10DIF <<
66 select CRC64_ROCKSOFT <<
67 help 62 help
68 Some storage devices allow extra infor 63 Some storage devices allow extra information to be
69 stored/retrieved to help protect the d 64 stored/retrieved to help protect the data. The block layer
70 data integrity option provides hooks w 65 data integrity option provides hooks which can be used by
71 filesystems to ensure better data inte 66 filesystems to ensure better data integrity.
72 67
73 Say yes here if you have a storage dev 68 Say yes here if you have a storage device that provides the
74 T10/SCSI Data Integrity Field or the T 69 T10/SCSI Data Integrity Field or the T13/ATA External Path
75 Protection. If in doubt, say N. 70 Protection. If in doubt, say N.
76 71
77 config BLK_DEV_WRITE_MOUNTED !! 72 config BLK_DEV_INTEGRITY_T10
78 bool "Allow writing to mounted block d !! 73 tristate
79 default y !! 74 depends on BLK_DEV_INTEGRITY
80 help !! 75 select CRC_T10DIF
81 When a block device is mounted, writin !! 76 select CRC64_ROCKSOFT
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 77
97 config BLK_DEV_ZONED 78 config BLK_DEV_ZONED
98 bool "Zoned block device support" 79 bool "Zoned block device support"
>> 80 select MQ_IOSCHED_DEADLINE
99 help 81 help
100 Block layer zoned block device support 82 Block layer zoned block device support. This option enables
101 support for ZAC/ZBC/ZNS host-managed a 83 support for ZAC/ZBC/ZNS host-managed and host-aware zoned block
102 devices. 84 devices.
103 85
104 Say yes here if you have a ZAC, ZBC, o 86 Say yes here if you have a ZAC, ZBC, or ZNS storage device.
105 87
106 config BLK_DEV_THROTTLING 88 config BLK_DEV_THROTTLING
107 bool "Block layer bio throttling suppo 89 bool "Block layer bio throttling support"
108 depends on BLK_CGROUP 90 depends on BLK_CGROUP
109 select BLK_CGROUP_RWSTAT 91 select BLK_CGROUP_RWSTAT
110 help 92 help
111 Block layer bio throttling support. It 93 Block layer bio throttling support. It can be used to limit
112 the IO rate to a device. IO rate polic 94 the IO rate to a device. IO rate policies are per cgroup and
113 one needs to mount and use blkio cgrou 95 one needs to mount and use blkio cgroup controller for creating
114 cgroups and specifying per device IO r 96 cgroups and specifying per device IO rate policies.
115 97
116 See Documentation/admin-guide/cgroup-v 98 See Documentation/admin-guide/cgroup-v1/blkio-controller.rst for more information.
117 99
>> 100 config BLK_DEV_THROTTLING_LOW
>> 101 bool "Block throttling .low limit interface support (EXPERIMENTAL)"
>> 102 depends on BLK_DEV_THROTTLING
>> 103 help
>> 104 Add .low limit interface for block throttling. The low limit is a best
>> 105 effort limit to prioritize cgroups. Depending on the setting, the limit
>> 106 can be used to protect cgroups in terms of bandwidth/iops and better
>> 107 utilize disk resource.
>> 108
>> 109 Note, this is an experimental interface and could be changed someday.
>> 110
118 config BLK_WBT 111 config BLK_WBT
119 bool "Enable support for block device 112 bool "Enable support for block device writeback throttling"
120 help 113 help
121 Enabling this option enables the block 114 Enabling this option enables the block layer to throttle buffered
122 background writeback from the VM, maki 115 background writeback from the VM, making it more smooth and having
123 less impact on foreground operations. 116 less impact on foreground operations. The throttling is done
124 dynamically on an algorithm loosely ba 117 dynamically on an algorithm loosely based on CoDel, factoring in
125 the realtime performance of the disk. 118 the realtime performance of the disk.
126 119
127 config BLK_WBT_MQ 120 config BLK_WBT_MQ
128 bool "Enable writeback throttling by d 121 bool "Enable writeback throttling by default"
129 default y 122 default y
130 depends on BLK_WBT 123 depends on BLK_WBT
131 help 124 help
132 Enable writeback throttling by default 125 Enable writeback throttling by default for request-based block devices.
133 126
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
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 138 config BLK_CGROUP_FC_APPID
146 bool "Enable support to track FC I/O T 139 bool "Enable support to track FC I/O Traffic across cgroup applications"
147 depends on BLK_CGROUP && NVME_FC 140 depends on BLK_CGROUP && NVME_FC
148 help 141 help
149 Enabling this option enables the sup 142 Enabling this option enables the support to track FC I/O traffic across
150 cgroup applications. It enables the 143 cgroup applications. It enables the Fabric and the storage targets to
151 identify, monitor, and handle FC tra 144 identify, monitor, and handle FC traffic based on VM tags by inserting
152 application specific identification 145 application specific identification into the FC frame.
153 146
154 config BLK_CGROUP_IOCOST 147 config BLK_CGROUP_IOCOST
155 bool "Enable support for cost model ba 148 bool "Enable support for cost model based cgroup IO controller"
156 depends on BLK_CGROUP 149 depends on BLK_CGROUP
157 select BLK_RQ_ALLOC_TIME 150 select BLK_RQ_ALLOC_TIME
158 help 151 help
159 Enabling this option enables the .weig 152 Enabling this option enables the .weight interface for cost
160 model based proportional IO control. 153 model based proportional IO control. The IO controller
161 distributes IO capacity between differ 154 distributes IO capacity between different groups based on
162 their share of the overall weight dist 155 their share of the overall weight distribution.
163 156
164 config BLK_CGROUP_IOPRIO 157 config BLK_CGROUP_IOPRIO
165 bool "Cgroup I/O controller for assign 158 bool "Cgroup I/O controller for assigning an I/O priority class"
166 depends on BLK_CGROUP 159 depends on BLK_CGROUP
167 help 160 help
168 Enable the .prio interface for assigni 161 Enable the .prio interface for assigning an I/O priority class to
169 requests. The I/O priority class affec 162 requests. The I/O priority class affects the order in which an I/O
170 scheduler and block devices process re 163 scheduler and block devices process requests. Only some I/O schedulers
171 and some block devices support I/O pri 164 and some block devices support I/O priorities.
172 165
173 config BLK_DEBUG_FS 166 config BLK_DEBUG_FS
174 bool "Block layer debugging informatio 167 bool "Block layer debugging information in debugfs"
175 default y 168 default y
176 depends on DEBUG_FS 169 depends on DEBUG_FS
177 help 170 help
178 Include block layer debugging informat 171 Include block layer debugging information in debugfs. This information
179 is mostly useful for kernel developers 172 is mostly useful for kernel developers, but it doesn't incur any cost
180 at runtime. 173 at runtime.
181 174
182 Unless you are building a kernel for a 175 Unless you are building a kernel for a tiny system, you should
183 say Y here. 176 say Y here.
184 177
>> 178 config BLK_DEBUG_FS_ZONED
>> 179 bool
>> 180 default BLK_DEBUG_FS && BLK_DEV_ZONED
>> 181
185 config BLK_SED_OPAL 182 config BLK_SED_OPAL
186 bool "Logic for interfacing with Opal 183 bool "Logic for interfacing with Opal enabled SEDs"
187 depends on KEYS <<
188 select PSERIES_PLPKS if PPC_PSERIES <<
189 select PSERIES_PLPKS_SED if PPC_PSERIE <<
190 help 184 help
191 Builds Logic for interfacing with Opal 185 Builds Logic for interfacing with Opal enabled controllers.
192 Enabling this option enables users to 186 Enabling this option enables users to setup/unlock/lock
193 Locking ranges for SED devices using t 187 Locking ranges for SED devices using the Opal protocol.
194 188
195 config BLK_INLINE_ENCRYPTION 189 config BLK_INLINE_ENCRYPTION
196 bool "Enable inline encryption support 190 bool "Enable inline encryption support in block layer"
197 help 191 help
198 Build the blk-crypto subsystem. Enab 192 Build the blk-crypto subsystem. Enabling this lets the
199 block layer handle encryption, so us 193 block layer handle encryption, so users can take
200 advantage of inline encryption hardw 194 advantage of inline encryption hardware if present.
201 195
202 config BLK_INLINE_ENCRYPTION_FALLBACK 196 config BLK_INLINE_ENCRYPTION_FALLBACK
203 bool "Enable crypto API fallback for b 197 bool "Enable crypto API fallback for blk-crypto"
204 depends on BLK_INLINE_ENCRYPTION 198 depends on BLK_INLINE_ENCRYPTION
205 select CRYPTO 199 select CRYPTO
206 select CRYPTO_SKCIPHER 200 select CRYPTO_SKCIPHER
207 help 201 help
208 Enabling this lets the block layer h 202 Enabling this lets the block layer handle inline encryption
209 by falling back to the kernel crypto 203 by falling back to the kernel crypto API when inline
210 encryption hardware is not present. 204 encryption hardware is not present.
211 205
212 source "block/partitions/Kconfig" 206 source "block/partitions/Kconfig"
213 207
>> 208 config BLOCK_COMPAT
>> 209 def_bool COMPAT
>> 210
214 config BLK_MQ_PCI 211 config BLK_MQ_PCI
215 def_bool PCI 212 def_bool PCI
216 213
217 config BLK_MQ_VIRTIO 214 config BLK_MQ_VIRTIO
218 bool 215 bool
219 depends on VIRTIO 216 depends on VIRTIO
>> 217 default y
>> 218
>> 219 config BLK_MQ_RDMA
>> 220 bool
>> 221 depends on INFINIBAND
220 default y 222 default y
221 223
222 config BLK_PM 224 config BLK_PM
223 def_bool PM 225 def_bool PM
224 226
225 # do not use in new code 227 # do not use in new code
226 config BLOCK_HOLDER_DEPRECATED 228 config BLOCK_HOLDER_DEPRECATED
227 bool 229 bool
228 230
229 config BLK_MQ_STACKING 231 config BLK_MQ_STACKING
230 bool 232 bool
231 233
232 source "block/Kconfig.iosched" 234 source "block/Kconfig.iosched"
233 235
234 endif # BLOCK 236 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.