1 # SPDX-License-Identifier: GPL-2.0
3 # Block layer core configuration
6 bool "Enable the block layer" if EXPERT
10 Provide block layer support for the kernel.
12 Disable this option to remove the block layer support from the
13 kernel. This may be useful for embedded devices.
15 If this option is disabled:
17 - block device files will become unusable
18 - some filesystems (such as ext3) will become unavailable.
20 Also, SCSI character devices and USB storage will be disabled since
21 they make use of various block layer definitions and facilities.
23 Say Y here unless you know you really don't want to mount disks and
28 config BLOCK_LEGACY_AUTOLOAD
29 bool "Legacy autoloading support"
32 Enable loading modules and creating block device instances based on
33 accesses through their device special file. This is a historic Linux
34 feature and makes no sense in a udev world where device files are
35 created on demand, but scripts that manually create device nodes and
36 then call losetup might rely on this behavior.
38 config BLK_RQ_ALLOC_TIME
41 config BLK_CGROUP_RWSTAT
44 config BLK_DEV_BSG_COMMON
51 bool "Block layer SG support v4 helper lib"
52 select BLK_DEV_BSG_COMMON
54 Subsystems will normally enable this if needed. Users will not
55 normally need to manually enable this.
59 config BLK_DEV_INTEGRITY
60 bool "Block layer data integrity support"
62 Some storage devices allow extra information to be
63 stored/retrieved to help protect the data. The block layer
64 data integrity option provides hooks which can be used by
65 filesystems to ensure better data integrity.
67 Say yes here if you have a storage device that provides the
68 T10/SCSI Data Integrity Field or the T13/ATA External Path
69 Protection. If in doubt, say N.
71 config BLK_DEV_INTEGRITY_T10
73 depends on BLK_DEV_INTEGRITY
78 bool "Zoned block device support"
79 select MQ_IOSCHED_DEADLINE
81 Block layer zoned block device support. This option enables
82 support for ZAC/ZBC/ZNS host-managed and host-aware zoned block
85 Say yes here if you have a ZAC, ZBC, or ZNS storage device.
87 config BLK_DEV_THROTTLING
88 bool "Block layer bio throttling support"
90 select BLK_CGROUP_RWSTAT
92 Block layer bio throttling support. It can be used to limit
93 the IO rate to a device. IO rate policies are per cgroup and
94 one needs to mount and use blkio cgroup controller for creating
95 cgroups and specifying per device IO rate policies.
97 See Documentation/admin-guide/cgroup-v1/blkio-controller.rst for more information.
99 config BLK_DEV_THROTTLING_LOW
100 bool "Block throttling .low limit interface support (EXPERIMENTAL)"
101 depends on BLK_DEV_THROTTLING
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.
108 Note, this is an experimental interface and could be changed someday.
111 bool "Enable support for block device writeback throttling"
113 Enabling this option enables the block layer to throttle buffered
114 background writeback from the VM, making it more smooth and having
115 less impact on foreground operations. The throttling is done
116 dynamically on an algorithm loosely based on CoDel, factoring in
117 the realtime performance of the disk.
120 bool "Enable writeback throttling by default"
124 Enable writeback throttling by default for request-based block devices.
126 config BLK_CGROUP_IOLATENCY
127 bool "Enable support for latency based cgroup IO protection"
128 depends on BLK_CGROUP
130 Enabling this option enables the .latency interface for IO throttling.
131 The IO controller will attempt to maintain average IO latencies below
132 the configured latency target, throttling anybody with a higher latency
133 target than the victimized group.
135 Note, this is an experimental interface and could be changed someday.
137 config BLK_CGROUP_FC_APPID
138 bool "Enable support to track FC I/O Traffic across cgroup applications"
139 depends on BLK_CGROUP && NVME_FC
141 Enabling this option enables the support to track FC I/O traffic across
142 cgroup applications. It enables the Fabric and the storage targets to
143 identify, monitor, and handle FC traffic based on VM tags by inserting
144 application specific identification into the FC frame.
146 config BLK_CGROUP_IOCOST
147 bool "Enable support for cost model based cgroup IO controller"
148 depends on BLK_CGROUP
149 select BLK_RQ_ALLOC_TIME
151 Enabling this option enables the .weight interface for cost
152 model based proportional IO control. The IO controller
153 distributes IO capacity between different groups based on
154 their share of the overall weight distribution.
156 config BLK_CGROUP_IOPRIO
157 bool "Cgroup I/O controller for assigning an I/O priority class"
158 depends on BLK_CGROUP
160 Enable the .prio interface for assigning an I/O priority class to
161 requests. The I/O priority class affects the order in which an I/O
162 scheduler and block devices process requests. Only some I/O schedulers
163 and some block devices support I/O priorities.
166 bool "Block layer debugging information in debugfs"
170 Include block layer debugging information in debugfs. This information
171 is mostly useful for kernel developers, but it doesn't incur any cost
174 Unless you are building a kernel for a tiny system, you should
177 config BLK_DEBUG_FS_ZONED
179 default BLK_DEBUG_FS && BLK_DEV_ZONED
182 bool "Logic for interfacing with Opal enabled SEDs"
184 Builds Logic for interfacing with Opal enabled controllers.
185 Enabling this option enables users to setup/unlock/lock
186 Locking ranges for SED devices using the Opal protocol.
188 config BLK_INLINE_ENCRYPTION
189 bool "Enable inline encryption support in block layer"
191 Build the blk-crypto subsystem. Enabling this lets the
192 block layer handle encryption, so users can take
193 advantage of inline encryption hardware if present.
195 config BLK_INLINE_ENCRYPTION_FALLBACK
196 bool "Enable crypto API fallback for blk-crypto"
197 depends on BLK_INLINE_ENCRYPTION
199 select CRYPTO_SKCIPHER
201 Enabling this lets the block layer handle inline encryption
202 by falling back to the kernel crypto API when inline
203 encryption hardware is not present.
205 source "block/partitions/Kconfig"
217 depends on INFINIBAND
223 # do not use in new code
224 config BLOCK_HOLDER_DEPRECATED
227 config BLK_MQ_STACKING
230 source "block/Kconfig.iosched"