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