1 # SPDX-License-Identifier: GPL-2.0 <<
2 # 1 #
3 # Block layer core configuration 2 # Block layer core configuration
4 # 3 #
5 menuconfig BLOCK 4 menuconfig BLOCK
6 bool "Enable the block layer" if EXPERT 5 bool "Enable the block layer" if EXPERT
7 default y 6 default y
8 select FS_IOMAP <<
9 select SBITMAP 7 select SBITMAP
>> 8 select SRCU
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 LBDAF
30 bool "Legacy autoloading support" !! 29 bool "Support for large (2TB+) block devices and files"
>> 30 depends on !64BIT
31 default y 31 default y
32 help 32 help
33 Enable loading modules and creating !! 33 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 34
39 config BLK_RQ_ALLOC_TIME !! 35 This option is required to support the full capacity of large
40 bool !! 36 (2TB+) block devices, including RAID, disk, Network Block Device,
>> 37 Logical Volume Manager (LVM) and loopback.
>> 38
>> 39 This option also enables support for single files larger than
>> 40 2TB.
>> 41
>> 42 The ext4 filesystem requires that this feature be enabled in
>> 43 order to support filesystems that have the huge_file feature
>> 44 enabled. Otherwise, it will refuse to mount in the read-write
>> 45 mode any filesystems that use the huge_file feature, which is
>> 46 enabled by default by mke2fs.ext4.
41 47
42 config BLK_CGROUP_RWSTAT !! 48 The GFS2 filesystem also requires this feature.
43 bool <<
44 49
45 config BLK_CGROUP_PUNT_BIO !! 50 If unsure, say Y.
46 bool <<
47 51
48 config BLK_DEV_BSG_COMMON !! 52 config BLK_DEV_BSG
49 tristate !! 53 bool "Block layer SG support v4"
>> 54 default y
>> 55 help
>> 56 Saying Y here will enable generic SG (SCSI generic) v4 support
>> 57 for any block device.
50 58
51 config BLK_ICQ !! 59 Unlike SG v3 (aka block/scsi_ioctl.c drivers/scsi/sg.c), SG v4
52 bool !! 60 can handle complicated SCSI commands: tagged variable length cdbs
>> 61 with bidirectional data transfers and generic request/response
>> 62 protocols (e.g. Task Management Functions and SMP in Serial
>> 63 Attached SCSI).
>> 64
>> 65 This option is required by recent UDEV versions to properly
>> 66 access device serial numbers, etc.
>> 67
>> 68 If unsure, say Y.
53 69
54 config BLK_DEV_BSGLIB 70 config BLK_DEV_BSGLIB
55 bool "Block layer SG support v4 helper 71 bool "Block layer SG support v4 helper lib"
56 select BLK_DEV_BSG_COMMON !! 72 default n
>> 73 select BLK_DEV_BSG
57 help 74 help
58 Subsystems will normally enable this 75 Subsystems will normally enable this if needed. Users will not
59 normally need to manually enable thi 76 normally need to manually enable this.
60 77
61 If unsure, say N. 78 If unsure, say N.
62 79
63 config BLK_DEV_INTEGRITY 80 config BLK_DEV_INTEGRITY
64 bool "Block layer data integrity suppo 81 bool "Block layer data integrity support"
65 select CRC_T10DIF !! 82 select CRC_T10DIF if BLK_DEV_INTEGRITY
66 select CRC64_ROCKSOFT !! 83 ---help---
67 help <<
68 Some storage devices allow extra infor 84 Some storage devices allow extra information to be
69 stored/retrieved to help protect the d 85 stored/retrieved to help protect the data. The block layer
70 data integrity option provides hooks w 86 data integrity option provides hooks which can be used by
71 filesystems to ensure better data inte 87 filesystems to ensure better data integrity.
72 88
73 Say yes here if you have a storage dev 89 Say yes here if you have a storage device that provides the
74 T10/SCSI Data Integrity Field or the T 90 T10/SCSI Data Integrity Field or the T13/ATA External Path
75 Protection. If in doubt, say N. 91 Protection. If in doubt, say N.
76 92
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 93 config BLK_DEV_ZONED
98 bool "Zoned block device support" 94 bool "Zoned block device support"
99 help !! 95 ---help---
100 Block layer zoned block device support 96 Block layer zoned block device support. This option enables
101 support for ZAC/ZBC/ZNS host-managed a !! 97 support for ZAC/ZBC host-managed and host-aware zoned block devices.
102 devices. <<
103 98
104 Say yes here if you have a ZAC, ZBC, o !! 99 Say yes here if you have a ZAC or ZBC storage device.
105 100
106 config BLK_DEV_THROTTLING 101 config BLK_DEV_THROTTLING
107 bool "Block layer bio throttling suppo 102 bool "Block layer bio throttling support"
108 depends on BLK_CGROUP !! 103 depends on BLK_CGROUP=y
109 select BLK_CGROUP_RWSTAT !! 104 default n
110 help !! 105 ---help---
111 Block layer bio throttling support. It 106 Block layer bio throttling support. It can be used to limit
112 the IO rate to a device. IO rate polic 107 the IO rate to a device. IO rate policies are per cgroup and
113 one needs to mount and use blkio cgrou 108 one needs to mount and use blkio cgroup controller for creating
114 cgroups and specifying per device IO r 109 cgroups and specifying per device IO rate policies.
115 110
116 See Documentation/admin-guide/cgroup-v !! 111 See Documentation/cgroups/blkio-controller.txt for more information.
>> 112
>> 113 config BLK_CMDLINE_PARSER
>> 114 bool "Block device command line partition parser"
>> 115 default n
>> 116 ---help---
>> 117 Enabling this option allows you to specify the partition layout from
>> 118 the kernel boot args. This is typically of use for embedded devices
>> 119 which don't otherwise have any standardized method for listing the
>> 120 partitions on a block device.
>> 121
>> 122 See Documentation/block/cmdline-partition.txt for more information.
117 123
118 config BLK_WBT 124 config BLK_WBT
119 bool "Enable support for block device 125 bool "Enable support for block device writeback throttling"
120 help !! 126 default n
>> 127 ---help---
121 Enabling this option enables the block 128 Enabling this option enables the block layer to throttle buffered
122 background writeback from the VM, maki 129 background writeback from the VM, making it more smooth and having
123 less impact on foreground operations. 130 less impact on foreground operations. The throttling is done
124 dynamically on an algorithm loosely ba 131 dynamically on an algorithm loosely based on CoDel, factoring in
125 the realtime performance of the disk. 132 the realtime performance of the disk.
126 133
127 config BLK_WBT_MQ !! 134 config BLK_WBT_SQ
128 bool "Enable writeback throttling by d !! 135 bool "Single queue writeback throttling"
129 default y !! 136 default n
130 depends on BLK_WBT 137 depends on BLK_WBT
131 help !! 138 ---help---
132 Enable writeback throttling by default !! 139 Enable writeback throttling by default on legacy single queue devices
133 140
134 config BLK_CGROUP_IOLATENCY !! 141 config BLK_WBT_MQ
135 bool "Enable support for latency based !! 142 bool "Multiqueue writeback throttling"
136 depends on BLK_CGROUP <<
137 help <<
138 Enabling this option enables the .late <<
139 The IO controller will attempt to main <<
140 the configured latency target, throttl <<
141 target than the victimized group. <<
142 <<
143 Note, this is an experimental interfac <<
144 <<
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 <<
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 <<
173 config BLK_DEBUG_FS <<
174 bool "Block layer debugging informatio <<
175 default y 143 default y
176 depends on DEBUG_FS !! 144 depends on BLK_WBT
177 help !! 145 ---help---
178 Include block layer debugging informat !! 146 Enable writeback throttling by default on multiqueue devices.
179 is mostly useful for kernel developers !! 147 Multiqueue currently doesn't have support for IO scheduling,
180 at runtime. !! 148 enabling this option is recommended.
181 <<
182 Unless you are building a kernel for a <<
183 say Y here. <<
184 <<
185 config BLK_SED_OPAL <<
186 bool "Logic for interfacing with Opal <<
187 depends on KEYS <<
188 select PSERIES_PLPKS if PPC_PSERIES <<
189 select PSERIES_PLPKS_SED if PPC_PSERIE <<
190 help <<
191 Builds Logic for interfacing with Opal <<
192 Enabling this option enables users to <<
193 Locking ranges for SED devices using t <<
194 149
195 config BLK_INLINE_ENCRYPTION !! 150 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 151
212 source "block/partitions/Kconfig" 152 source "block/partitions/Kconfig"
213 153
214 config BLK_MQ_PCI !! 154 endmenu
215 def_bool PCI <<
216 155
217 config BLK_MQ_VIRTIO !! 156 endif # BLOCK
218 bool <<
219 depends on VIRTIO <<
220 default y <<
221 <<
222 config BLK_PM <<
223 def_bool PM <<
224 157
225 # do not use in new code !! 158 config BLOCK_COMPAT
226 config BLOCK_HOLDER_DEPRECATED <<
227 bool 159 bool
>> 160 depends on BLOCK && COMPAT
>> 161 default y
228 162
229 config BLK_MQ_STACKING !! 163 config BLK_MQ_PCI
230 bool 164 bool
>> 165 depends on BLOCK && PCI
>> 166 default y
231 167
232 source "block/Kconfig.iosched" !! 168 source block/Kconfig.iosched
233 <<
234 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.