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_CGROUP_RWSTAT
46 bool 36 bool
47 37
48 config BLK_DEV_BSG_COMMON !! 38 config BLK_DEV_BSG
49 tristate !! 39 bool "Block layer SG support v4"
>> 40 default y
>> 41 select BLK_SCSI_REQUEST
>> 42 help
>> 43 Saying Y here will enable generic SG (SCSI generic) v4 support
>> 44 for any block device.
50 45
51 config BLK_ICQ !! 46 Unlike SG v3 (aka block/scsi_ioctl.c drivers/scsi/sg.c), SG v4
52 bool !! 47 can handle complicated SCSI commands: tagged variable length cdbs
>> 48 with bidirectional data transfers and generic request/response
>> 49 protocols (e.g. Task Management Functions and SMP in Serial
>> 50 Attached SCSI).
>> 51
>> 52 This option is required by recent UDEV versions to properly
>> 53 access device serial numbers, etc.
>> 54
>> 55 If unsure, say Y.
53 56
54 config BLK_DEV_BSGLIB 57 config BLK_DEV_BSGLIB
55 bool "Block layer SG support v4 helper 58 bool "Block layer SG support v4 helper lib"
56 select BLK_DEV_BSG_COMMON !! 59 select BLK_DEV_BSG
>> 60 select BLK_SCSI_REQUEST
57 help 61 help
58 Subsystems will normally enable this 62 Subsystems will normally enable this if needed. Users will not
59 normally need to manually enable thi 63 normally need to manually enable this.
60 64
61 If unsure, say N. 65 If unsure, say N.
62 66
63 config BLK_DEV_INTEGRITY 67 config BLK_DEV_INTEGRITY
64 bool "Block layer data integrity suppo 68 bool "Block layer data integrity support"
65 select CRC_T10DIF <<
66 select CRC64_ROCKSOFT <<
67 help 69 help
68 Some storage devices allow extra infor 70 Some storage devices allow extra information to be
69 stored/retrieved to help protect the d 71 stored/retrieved to help protect the data. The block layer
70 data integrity option provides hooks w 72 data integrity option provides hooks which can be used by
71 filesystems to ensure better data inte 73 filesystems to ensure better data integrity.
72 74
73 Say yes here if you have a storage dev 75 Say yes here if you have a storage device that provides the
74 T10/SCSI Data Integrity Field or the T 76 T10/SCSI Data Integrity Field or the T13/ATA External Path
75 Protection. If in doubt, say N. 77 Protection. If in doubt, say N.
76 78
77 config BLK_DEV_WRITE_MOUNTED !! 79 config BLK_DEV_INTEGRITY_T10
78 bool "Allow writing to mounted block d !! 80 tristate
79 default y !! 81 depends on BLK_DEV_INTEGRITY
80 help !! 82 select CRC_T10DIF
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 83
97 config BLK_DEV_ZONED 84 config BLK_DEV_ZONED
98 bool "Zoned block device support" 85 bool "Zoned block device support"
>> 86 select MQ_IOSCHED_DEADLINE
99 help 87 help
100 Block layer zoned block device support 88 Block layer zoned block device support. This option enables
101 support for ZAC/ZBC/ZNS host-managed a !! 89 support for ZAC/ZBC host-managed and host-aware zoned block devices.
102 devices. <<
103 90
104 Say yes here if you have a ZAC, ZBC, o !! 91 Say yes here if you have a ZAC or ZBC storage device.
105 92
106 config BLK_DEV_THROTTLING 93 config BLK_DEV_THROTTLING
107 bool "Block layer bio throttling suppo 94 bool "Block layer bio throttling support"
108 depends on BLK_CGROUP !! 95 depends on BLK_CGROUP=y
109 select BLK_CGROUP_RWSTAT 96 select BLK_CGROUP_RWSTAT
110 help 97 help
111 Block layer bio throttling support. It 98 Block layer bio throttling support. It can be used to limit
112 the IO rate to a device. IO rate polic 99 the IO rate to a device. IO rate policies are per cgroup and
113 one needs to mount and use blkio cgrou 100 one needs to mount and use blkio cgroup controller for creating
114 cgroups and specifying per device IO r 101 cgroups and specifying per device IO rate policies.
115 102
116 See Documentation/admin-guide/cgroup-v 103 See Documentation/admin-guide/cgroup-v1/blkio-controller.rst for more information.
117 104
>> 105 config BLK_DEV_THROTTLING_LOW
>> 106 bool "Block throttling .low limit interface support (EXPERIMENTAL)"
>> 107 depends on BLK_DEV_THROTTLING
>> 108 help
>> 109 Add .low limit interface for block throttling. The low limit is a best
>> 110 effort limit to prioritize cgroups. Depending on the setting, the limit
>> 111 can be used to protect cgroups in terms of bandwidth/iops and better
>> 112 utilize disk resource.
>> 113
>> 114 Note, this is an experimental interface and could be changed someday.
>> 115
>> 116 config BLK_CMDLINE_PARSER
>> 117 bool "Block device command line partition parser"
>> 118 help
>> 119 Enabling this option allows you to specify the partition layout from
>> 120 the kernel boot args. This is typically of use for embedded devices
>> 121 which don't otherwise have any standardized method for listing the
>> 122 partitions on a block device.
>> 123
>> 124 See Documentation/block/cmdline-partition.rst for more information.
>> 125
118 config BLK_WBT 126 config BLK_WBT
119 bool "Enable support for block device 127 bool "Enable support for block device writeback throttling"
120 help 128 help
121 Enabling this option enables the block 129 Enabling this option enables the block layer to throttle buffered
122 background writeback from the VM, maki 130 background writeback from the VM, making it more smooth and having
123 less impact on foreground operations. 131 less impact on foreground operations. The throttling is done
124 dynamically on an algorithm loosely ba 132 dynamically on an algorithm loosely based on CoDel, factoring in
125 the realtime performance of the disk. 133 the realtime performance of the disk.
126 134
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 135 config BLK_CGROUP_IOLATENCY
135 bool "Enable support for latency based 136 bool "Enable support for latency based cgroup IO protection"
136 depends on BLK_CGROUP !! 137 depends on BLK_CGROUP=y
137 help 138 help
138 Enabling this option enables the .late 139 Enabling this option enables the .latency interface for IO throttling.
139 The IO controller will attempt to main 140 The IO controller will attempt to maintain average IO latencies below
140 the configured latency target, throttl 141 the configured latency target, throttling anybody with a higher latency
141 target than the victimized group. 142 target than the victimized group.
142 143
143 Note, this is an experimental interfac 144 Note, this is an experimental interface and could be changed someday.
144 145
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 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=y
>> 149 select BLK_RQ_IO_DATA_LEN
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_WBT_MQ
165 bool "Cgroup I/O controller for assign !! 158 bool "Multiqueue writeback throttling"
166 depends on BLK_CGROUP !! 159 default y
167 help !! 160 depends on BLK_WBT
168 Enable the .prio interface for assigni !! 161 help
169 requests. The I/O priority class affec !! 162 Enable writeback throttling by default on multiqueue devices.
170 scheduler and block devices process re !! 163 Multiqueue currently doesn't have support for IO scheduling,
171 and some block devices support I/O pri !! 164 enabling this option is recommended.
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
>> 206 menu "Partition Types"
>> 207
212 source "block/partitions/Kconfig" 208 source "block/partitions/Kconfig"
213 209
214 config BLK_MQ_PCI !! 210 endmenu
215 def_bool PCI <<
216 211
217 config BLK_MQ_VIRTIO !! 212 endif # BLOCK
>> 213
>> 214 config BLOCK_COMPAT
218 bool 215 bool
219 depends on VIRTIO !! 216 depends on BLOCK && COMPAT
220 default y 217 default y
221 218
222 config BLK_PM !! 219 config BLK_MQ_PCI
223 def_bool PM !! 220 bool
>> 221 depends on BLOCK && PCI
>> 222 default y
224 223
225 # do not use in new code !! 224 config BLK_MQ_VIRTIO
226 config BLOCK_HOLDER_DEPRECATED <<
227 bool 225 bool
>> 226 depends on BLOCK && VIRTIO
>> 227 default y
228 228
229 config BLK_MQ_STACKING !! 229 config BLK_MQ_RDMA
230 bool 230 bool
>> 231 depends on BLOCK && INFINIBAND
>> 232 default y
231 233
232 source "block/Kconfig.iosched" !! 234 config BLK_PM
>> 235 def_bool BLOCK && PM
233 236
234 endif # BLOCK !! 237 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.