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