1# SPDX-License-Identifier: GPL-2.0 2# 3# Block layer core configuration 4# 5menuconfig BLOCK 6 bool "Enable the block layer" if EXPERT 7 default y 8 select SBITMAP 9 select SRCU 10 help 11 Provide block layer support for the kernel. 12 13 Disable this option to remove the block layer support from the 14 kernel. This may be useful for embedded devices. 15 16 If this option is disabled: 17 18 - block device files will become unusable 19 - some filesystems (such as ext3) will become unavailable. 20 21 Also, SCSI character devices and USB storage will be disabled since 22 they make use of various block layer definitions and facilities. 23 24 Say Y here unless you know you really don't want to mount disks and 25 suchlike. 26 27if BLOCK 28 29config BLOCK_LEGACY_AUTOLOAD 30 bool "Legacy autoloading support" 31 default y 32 help 33 Enable loading modules and creating block device instances based on 34 accesses through their device special file. This is a historic Linux 35 feature and makes no sense in a udev world where device files are 36 created on demand, but scripts that manually create device nodes and 37 then call losetup might rely on this behavior. 38 39config BLK_RQ_ALLOC_TIME 40 bool 41 42config BLK_CGROUP_RWSTAT 43 bool 44 45config BLK_DEV_BSG_COMMON 46 tristate 47 48config BLK_ICQ 49 bool 50 51config BLK_DEV_BSGLIB 52 bool "Block layer SG support v4 helper lib" 53 select BLK_DEV_BSG_COMMON 54 help 55 Subsystems will normally enable this if needed. Users will not 56 normally need to manually enable this. 57 58 If unsure, say N. 59 60config BLK_DEV_INTEGRITY 61 bool "Block layer data integrity support" 62 help 63 Some storage devices allow extra information to be 64 stored/retrieved to help protect the data. The block layer 65 data integrity option provides hooks which can be used by 66 filesystems to ensure better data integrity. 67 68 Say yes here if you have a storage device that provides the 69 T10/SCSI Data Integrity Field or the T13/ATA External Path 70 Protection. If in doubt, say N. 71 72config BLK_DEV_INTEGRITY_T10 73 tristate 74 depends on BLK_DEV_INTEGRITY 75 select CRC_T10DIF 76 77config BLK_DEV_ZONED 78 bool "Zoned block device support" 79 select MQ_IOSCHED_DEADLINE 80 help 81 Block layer zoned block device support. This option enables 82 support for ZAC/ZBC/ZNS host-managed and host-aware zoned block 83 devices. 84 85 Say yes here if you have a ZAC, ZBC, or ZNS storage device. 86 87config BLK_DEV_THROTTLING 88 bool "Block layer bio throttling support" 89 depends on BLK_CGROUP 90 select BLK_CGROUP_RWSTAT 91 help 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. 96 97 See Documentation/admin-guide/cgroup-v1/blkio-controller.rst for more information. 98 99config BLK_DEV_THROTTLING_LOW 100 bool "Block throttling .low limit interface support (EXPERIMENTAL)" 101 depends on BLK_DEV_THROTTLING 102 help 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. 107 108 Note, this is an experimental interface and could be changed someday. 109 110config BLK_WBT 111 bool "Enable support for block device writeback throttling" 112 help 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. 118 119config BLK_WBT_MQ 120 bool "Enable writeback throttling by default" 121 default y 122 depends on BLK_WBT 123 help 124 Enable writeback throttling by default for request-based block devices. 125 126config BLK_CGROUP_IOLATENCY 127 bool "Enable support for latency based cgroup IO protection" 128 depends on BLK_CGROUP 129 help 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. 134 135 Note, this is an experimental interface and could be changed someday. 136 137config BLK_CGROUP_FC_APPID 138 bool "Enable support to track FC I/O Traffic across cgroup applications" 139 depends on BLK_CGROUP && NVME_FC 140 help 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. 145 146config BLK_CGROUP_IOCOST 147 bool "Enable support for cost model based cgroup IO controller" 148 depends on BLK_CGROUP 149 select BLK_RQ_IO_DATA_LEN 150 select BLK_RQ_ALLOC_TIME 151 help 152 Enabling this option enables the .weight interface for cost 153 model based proportional IO control. The IO controller 154 distributes IO capacity between different groups based on 155 their share of the overall weight distribution. 156 157config BLK_CGROUP_IOPRIO 158 bool "Cgroup I/O controller for assigning an I/O priority class" 159 depends on BLK_CGROUP 160 help 161 Enable the .prio interface for assigning an I/O priority class to 162 requests. The I/O priority class affects the order in which an I/O 163 scheduler and block devices process requests. Only some I/O schedulers 164 and some block devices support I/O priorities. 165 166config BLK_DEBUG_FS 167 bool "Block layer debugging information in debugfs" 168 default y 169 depends on DEBUG_FS 170 help 171 Include block layer debugging information in debugfs. This information 172 is mostly useful for kernel developers, but it doesn't incur any cost 173 at runtime. 174 175 Unless you are building a kernel for a tiny system, you should 176 say Y here. 177 178config BLK_DEBUG_FS_ZONED 179 bool 180 default BLK_DEBUG_FS && BLK_DEV_ZONED 181 182config BLK_SED_OPAL 183 bool "Logic for interfacing with Opal enabled SEDs" 184 help 185 Builds Logic for interfacing with Opal enabled controllers. 186 Enabling this option enables users to setup/unlock/lock 187 Locking ranges for SED devices using the Opal protocol. 188 189config BLK_INLINE_ENCRYPTION 190 bool "Enable inline encryption support in block layer" 191 help 192 Build the blk-crypto subsystem. Enabling this lets the 193 block layer handle encryption, so users can take 194 advantage of inline encryption hardware if present. 195 196config BLK_INLINE_ENCRYPTION_FALLBACK 197 bool "Enable crypto API fallback for blk-crypto" 198 depends on BLK_INLINE_ENCRYPTION 199 select CRYPTO 200 select CRYPTO_SKCIPHER 201 help 202 Enabling this lets the block layer handle inline encryption 203 by falling back to the kernel crypto API when inline 204 encryption hardware is not present. 205 206source "block/partitions/Kconfig" 207 208config BLOCK_COMPAT 209 def_bool COMPAT 210 211config BLK_MQ_PCI 212 def_bool PCI 213 214config BLK_MQ_VIRTIO 215 bool 216 depends on VIRTIO 217 default y 218 219config BLK_MQ_RDMA 220 bool 221 depends on INFINIBAND 222 default y 223 224config BLK_PM 225 def_bool PM 226 227# do not use in new code 228config BLOCK_HOLDER_DEPRECATED 229 bool 230 231config BLK_MQ_STACKING 232 bool 233 234source "block/Kconfig.iosched" 235 236endif # BLOCK 237