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 LBDAF
30 bool "Legacy autoloading support" !! 30 bool "Support for large (2TB+) block devices and files"
>> 31 depends on !64BIT
31 default y 32 default y
32 help 33 help
33 Enable loading modules and creating !! 34 Enable block devices or files of size 2TB and larger.
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 35
39 config BLK_RQ_ALLOC_TIME !! 36 This option is required to support the full capacity of large
40 bool !! 37 (2TB+) block devices, including RAID, disk, Network Block Device,
>> 38 Logical Volume Manager (LVM) and loopback.
>> 39
>> 40 This option also enables support for single files larger than
>> 41 2TB.
41 42
42 config BLK_CGROUP_RWSTAT !! 43 The ext4 filesystem requires that this feature be enabled in
43 bool !! 44 order to support filesystems that have the huge_file feature
>> 45 enabled. Otherwise, it will refuse to mount in the read-write
>> 46 mode any filesystems that use the huge_file feature, which is
>> 47 enabled by default by mke2fs.ext4.
44 48
45 config BLK_CGROUP_PUNT_BIO !! 49 The GFS2 filesystem also requires this feature.
46 bool <<
47 50
48 config BLK_DEV_BSG_COMMON !! 51 If unsure, say Y.
49 tristate <<
50 52
51 config BLK_ICQ !! 53 config BLK_SCSI_REQUEST
52 bool 54 bool
53 55
>> 56 config BLK_DEV_BSG
>> 57 bool "Block layer SG support v4"
>> 58 default y
>> 59 select BLK_SCSI_REQUEST
>> 60 help
>> 61 Saying Y here will enable generic SG (SCSI generic) v4 support
>> 62 for any block device.
>> 63
>> 64 Unlike SG v3 (aka block/scsi_ioctl.c drivers/scsi/sg.c), SG v4
>> 65 can handle complicated SCSI commands: tagged variable length cdbs
>> 66 with bidirectional data transfers and generic request/response
>> 67 protocols (e.g. Task Management Functions and SMP in Serial
>> 68 Attached SCSI).
>> 69
>> 70 This option is required by recent UDEV versions to properly
>> 71 access device serial numbers, etc.
>> 72
>> 73 If unsure, say Y.
>> 74
54 config BLK_DEV_BSGLIB 75 config BLK_DEV_BSGLIB
55 bool "Block layer SG support v4 helper 76 bool "Block layer SG support v4 helper lib"
56 select BLK_DEV_BSG_COMMON !! 77 select BLK_DEV_BSG
>> 78 select BLK_SCSI_REQUEST
57 help 79 help
58 Subsystems will normally enable this 80 Subsystems will normally enable this if needed. Users will not
59 normally need to manually enable thi 81 normally need to manually enable this.
60 82
61 If unsure, say N. 83 If unsure, say N.
62 84
63 config BLK_DEV_INTEGRITY 85 config BLK_DEV_INTEGRITY
64 bool "Block layer data integrity suppo 86 bool "Block layer data integrity support"
65 select CRC_T10DIF !! 87 select CRC_T10DIF if BLK_DEV_INTEGRITY
66 select CRC64_ROCKSOFT !! 88 ---help---
67 help <<
68 Some storage devices allow extra infor 89 Some storage devices allow extra information to be
69 stored/retrieved to help protect the d 90 stored/retrieved to help protect the data. The block layer
70 data integrity option provides hooks w 91 data integrity option provides hooks which can be used by
71 filesystems to ensure better data inte 92 filesystems to ensure better data integrity.
72 93
73 Say yes here if you have a storage dev 94 Say yes here if you have a storage device that provides the
74 T10/SCSI Data Integrity Field or the T 95 T10/SCSI Data Integrity Field or the T13/ATA External Path
75 Protection. If in doubt, say N. 96 Protection. If in doubt, say N.
76 97
77 config BLK_DEV_WRITE_MOUNTED <<
78 bool "Allow writing to mounted block d <<
79 default y <<
80 help <<
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 <<
97 config BLK_DEV_ZONED 98 config BLK_DEV_ZONED
98 bool "Zoned block device support" 99 bool "Zoned block device support"
99 help !! 100 ---help---
100 Block layer zoned block device support 101 Block layer zoned block device support. This option enables
101 support for ZAC/ZBC/ZNS host-managed a !! 102 support for ZAC/ZBC host-managed and host-aware zoned block devices.
102 devices. <<
103 103
104 Say yes here if you have a ZAC, ZBC, o !! 104 Say yes here if you have a ZAC or ZBC storage device.
105 105
106 config BLK_DEV_THROTTLING 106 config BLK_DEV_THROTTLING
107 bool "Block layer bio throttling suppo 107 bool "Block layer bio throttling support"
108 depends on BLK_CGROUP !! 108 depends on BLK_CGROUP=y
109 select BLK_CGROUP_RWSTAT !! 109 ---help---
110 help <<
111 Block layer bio throttling support. It 110 Block layer bio throttling support. It can be used to limit
112 the IO rate to a device. IO rate polic 111 the IO rate to a device. IO rate policies are per cgroup and
113 one needs to mount and use blkio cgrou 112 one needs to mount and use blkio cgroup controller for creating
114 cgroups and specifying per device IO r 113 cgroups and specifying per device IO rate policies.
115 114
116 See Documentation/admin-guide/cgroup-v !! 115 See Documentation/cgroup-v1/blkio-controller.txt for more information.
>> 116
>> 117 config BLK_DEV_THROTTLING_LOW
>> 118 bool "Block throttling .low limit interface support (EXPERIMENTAL)"
>> 119 depends on BLK_DEV_THROTTLING
>> 120 ---help---
>> 121 Add .low limit interface for block throttling. The low limit is a best
>> 122 effort limit to prioritize cgroups. Depending on the setting, the limit
>> 123 can be used to protect cgroups in terms of bandwidth/iops and better
>> 124 utilize disk resource.
>> 125
>> 126 Note, this is an experimental interface and could be changed someday.
>> 127
>> 128 config BLK_CMDLINE_PARSER
>> 129 bool "Block device command line partition parser"
>> 130 ---help---
>> 131 Enabling this option allows you to specify the partition layout from
>> 132 the kernel boot args. This is typically of use for embedded devices
>> 133 which don't otherwise have any standardized method for listing the
>> 134 partitions on a block device.
>> 135
>> 136 See Documentation/block/cmdline-partition.txt for more information.
117 137
118 config BLK_WBT 138 config BLK_WBT
119 bool "Enable support for block device 139 bool "Enable support for block device writeback throttling"
120 help !! 140 ---help---
121 Enabling this option enables the block 141 Enabling this option enables the block layer to throttle buffered
122 background writeback from the VM, maki 142 background writeback from the VM, making it more smooth and having
123 less impact on foreground operations. 143 less impact on foreground operations. The throttling is done
124 dynamically on an algorithm loosely ba 144 dynamically on an algorithm loosely based on CoDel, factoring in
125 the realtime performance of the disk. 145 the realtime performance of the disk.
126 146
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 147 config BLK_CGROUP_IOLATENCY
135 bool "Enable support for latency based 148 bool "Enable support for latency based cgroup IO protection"
136 depends on BLK_CGROUP !! 149 depends on BLK_CGROUP=y
137 help !! 150 ---help---
138 Enabling this option enables the .late 151 Enabling this option enables the .latency interface for IO throttling.
139 The IO controller will attempt to main 152 The IO controller will attempt to maintain average IO latencies below
140 the configured latency target, throttl 153 the configured latency target, throttling anybody with a higher latency
141 target than the victimized group. 154 target than the victimized group.
142 155
143 Note, this is an experimental interfac 156 Note, this is an experimental interface and could be changed someday.
144 157
145 config BLK_CGROUP_FC_APPID !! 158 config BLK_WBT_MQ
146 bool "Enable support to track FC I/O T !! 159 bool "Multiqueue writeback throttling"
147 depends on BLK_CGROUP && NVME_FC !! 160 default y
148 help !! 161 depends on BLK_WBT
149 Enabling this option enables the sup !! 162 ---help---
150 cgroup applications. It enables the !! 163 Enable writeback throttling by default on multiqueue devices.
151 identify, monitor, and handle FC tra !! 164 Multiqueue currently doesn't have support for IO scheduling,
152 application specific identification !! 165 enabling this option is recommended.
153 <<
154 config BLK_CGROUP_IOCOST <<
155 bool "Enable support for cost model ba <<
156 depends on BLK_CGROUP <<
157 select BLK_RQ_ALLOC_TIME <<
158 help <<
159 Enabling this option enables the .weig <<
160 model based proportional IO control. <<
161 distributes IO capacity between differ <<
162 their share of the overall weight dist <<
163 <<
164 config BLK_CGROUP_IOPRIO <<
165 bool "Cgroup I/O controller for assign <<
166 depends on BLK_CGROUP <<
167 help <<
168 Enable the .prio interface for assigni <<
169 requests. The I/O priority class affec <<
170 scheduler and block devices process re <<
171 and some block devices support I/O pri <<
172 166
173 config BLK_DEBUG_FS 167 config BLK_DEBUG_FS
174 bool "Block layer debugging informatio 168 bool "Block layer debugging information in debugfs"
175 default y 169 default y
176 depends on DEBUG_FS 170 depends on DEBUG_FS
177 help !! 171 ---help---
178 Include block layer debugging informat 172 Include block layer debugging information in debugfs. This information
179 is mostly useful for kernel developers 173 is mostly useful for kernel developers, but it doesn't incur any cost
180 at runtime. 174 at runtime.
181 175
182 Unless you are building a kernel for a 176 Unless you are building a kernel for a tiny system, you should
183 say Y here. 177 say Y here.
184 178
>> 179 config BLK_DEBUG_FS_ZONED
>> 180 bool
>> 181 default BLK_DEBUG_FS && BLK_DEV_ZONED
>> 182
185 config BLK_SED_OPAL 183 config BLK_SED_OPAL
186 bool "Logic for interfacing with Opal 184 bool "Logic for interfacing with Opal enabled SEDs"
187 depends on KEYS !! 185 ---help---
188 select PSERIES_PLPKS if PPC_PSERIES <<
189 select PSERIES_PLPKS_SED if PPC_PSERIE <<
190 help <<
191 Builds Logic for interfacing with Opal 186 Builds Logic for interfacing with Opal enabled controllers.
192 Enabling this option enables users to 187 Enabling this option enables users to setup/unlock/lock
193 Locking ranges for SED devices using t 188 Locking ranges for SED devices using the Opal protocol.
194 189
195 config BLK_INLINE_ENCRYPTION !! 190 menu "Partition Types"
196 bool "Enable inline encryption support <<
197 help <<
198 Build the blk-crypto subsystem. Enab <<
199 block layer handle encryption, so us <<
200 advantage of inline encryption hardw <<
201 <<
202 config BLK_INLINE_ENCRYPTION_FALLBACK <<
203 bool "Enable crypto API fallback for b <<
204 depends on BLK_INLINE_ENCRYPTION <<
205 select CRYPTO <<
206 select CRYPTO_SKCIPHER <<
207 help <<
208 Enabling this lets the block layer h <<
209 by falling back to the kernel crypto <<
210 encryption hardware is not present. <<
211 191
212 source "block/partitions/Kconfig" 192 source "block/partitions/Kconfig"
213 193
214 config BLK_MQ_PCI !! 194 endmenu
215 def_bool PCI <<
216 195
217 config BLK_MQ_VIRTIO !! 196 endif # BLOCK
>> 197
>> 198 config BLOCK_COMPAT
218 bool 199 bool
219 depends on VIRTIO !! 200 depends on BLOCK && COMPAT
220 default y 201 default y
221 202
222 config BLK_PM !! 203 config BLK_MQ_PCI
223 def_bool PM !! 204 bool
>> 205 depends on BLOCK && PCI
>> 206 default y
224 207
225 # do not use in new code !! 208 config BLK_MQ_VIRTIO
226 config BLOCK_HOLDER_DEPRECATED <<
227 bool 209 bool
>> 210 depends on BLOCK && VIRTIO
>> 211 default y
228 212
229 config BLK_MQ_STACKING !! 213 config BLK_MQ_RDMA
230 bool 214 bool
>> 215 depends on BLOCK && INFINIBAND
>> 216 default y
231 217
232 source "block/Kconfig.iosched" !! 218 config BLK_PM
>> 219 def_bool BLOCK && PM
233 220
234 endif # BLOCK !! 221 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.