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 help 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. 36 37 Say N here unless booting or other functionality broke without it, in 38 which case you should also send a report to your distribution and 39 linux-block@vger.kernel.org. 40 41config BLK_RQ_ALLOC_TIME 42 bool 43 44config BLK_CGROUP_RWSTAT 45 bool 46 47config BLK_DEV_BSG_COMMON 48 tristate 49 50config BLK_ICQ 51 bool 52 53config BLK_DEV_BSGLIB 54 bool "Block layer SG support v4 helper lib" 55 select BLK_DEV_BSG_COMMON 56 help 57 Subsystems will normally enable this if needed. Users will not 58 normally need to manually enable this. 59 60 If unsure, say N. 61 62config BLK_DEV_INTEGRITY 63 bool "Block layer data integrity support" 64 help 65 Some storage devices allow extra information to be 66 stored/retrieved to help protect the data. The block layer 67 data integrity option provides hooks which can be used by 68 filesystems to ensure better data integrity. 69 70 Say yes here if you have a storage device that provides the 71 T10/SCSI Data Integrity Field or the T13/ATA External Path 72 Protection. If in doubt, say N. 73 74config BLK_DEV_INTEGRITY_T10 75 tristate 76 depends on BLK_DEV_INTEGRITY 77 select CRC_T10DIF 78 79config BLK_DEV_ZONED 80 bool "Zoned block device support" 81 select MQ_IOSCHED_DEADLINE 82 help 83 Block layer zoned block device support. This option enables 84 support for ZAC/ZBC/ZNS host-managed and host-aware zoned block 85 devices. 86 87 Say yes here if you have a ZAC, ZBC, or ZNS storage device. 88 89config BLK_DEV_THROTTLING 90 bool "Block layer bio throttling support" 91 depends on BLK_CGROUP 92 select BLK_CGROUP_RWSTAT 93 help 94 Block layer bio throttling support. It can be used to limit 95 the IO rate to a device. IO rate policies are per cgroup and 96 one needs to mount and use blkio cgroup controller for creating 97 cgroups and specifying per device IO rate policies. 98 99 See Documentation/admin-guide/cgroup-v1/blkio-controller.rst for more information. 100 101config BLK_DEV_THROTTLING_LOW 102 bool "Block throttling .low limit interface support (EXPERIMENTAL)" 103 depends on BLK_DEV_THROTTLING 104 help 105 Add .low limit interface for block throttling. The low limit is a best 106 effort limit to prioritize cgroups. Depending on the setting, the limit 107 can be used to protect cgroups in terms of bandwidth/iops and better 108 utilize disk resource. 109 110 Note, this is an experimental interface and could be changed someday. 111 112config BLK_WBT 113 bool "Enable support for block device writeback throttling" 114 help 115 Enabling this option enables the block layer to throttle buffered 116 background writeback from the VM, making it more smooth and having 117 less impact on foreground operations. The throttling is done 118 dynamically on an algorithm loosely based on CoDel, factoring in 119 the realtime performance of the disk. 120 121config BLK_WBT_MQ 122 bool "Enable writeback throttling by default" 123 default y 124 depends on BLK_WBT 125 help 126 Enable writeback throttling by default for request-based block devices. 127 128config BLK_CGROUP_IOLATENCY 129 bool "Enable support for latency based cgroup IO protection" 130 depends on BLK_CGROUP 131 help 132 Enabling this option enables the .latency interface for IO throttling. 133 The IO controller will attempt to maintain average IO latencies below 134 the configured latency target, throttling anybody with a higher latency 135 target than the victimized group. 136 137 Note, this is an experimental interface and could be changed someday. 138 139config BLK_CGROUP_FC_APPID 140 bool "Enable support to track FC I/O Traffic across cgroup applications" 141 depends on BLK_CGROUP && NVME_FC 142 help 143 Enabling this option enables the support to track FC I/O traffic across 144 cgroup applications. It enables the Fabric and the storage targets to 145 identify, monitor, and handle FC traffic based on VM tags by inserting 146 application specific identification into the FC frame. 147 148config BLK_CGROUP_IOCOST 149 bool "Enable support for cost model based cgroup IO controller" 150 depends on BLK_CGROUP 151 select BLK_RQ_IO_DATA_LEN 152 select BLK_RQ_ALLOC_TIME 153 help 154 Enabling this option enables the .weight interface for cost 155 model based proportional IO control. The IO controller 156 distributes IO capacity between different groups based on 157 their share of the overall weight distribution. 158 159config BLK_CGROUP_IOPRIO 160 bool "Cgroup I/O controller for assigning an I/O priority class" 161 depends on BLK_CGROUP 162 help 163 Enable the .prio interface for assigning an I/O priority class to 164 requests. The I/O priority class affects the order in which an I/O 165 scheduler and block devices process requests. Only some I/O schedulers 166 and some block devices support I/O priorities. 167 168config BLK_DEBUG_FS 169 bool "Block layer debugging information in debugfs" 170 default y 171 depends on DEBUG_FS 172 help 173 Include block layer debugging information in debugfs. This information 174 is mostly useful for kernel developers, but it doesn't incur any cost 175 at runtime. 176 177 Unless you are building a kernel for a tiny system, you should 178 say Y here. 179 180config BLK_DEBUG_FS_ZONED 181 bool 182 default BLK_DEBUG_FS && BLK_DEV_ZONED 183 184config BLK_SED_OPAL 185 bool "Logic for interfacing with Opal enabled SEDs" 186 help 187 Builds Logic for interfacing with Opal enabled controllers. 188 Enabling this option enables users to setup/unlock/lock 189 Locking ranges for SED devices using the Opal protocol. 190 191config BLK_INLINE_ENCRYPTION 192 bool "Enable inline encryption support in block layer" 193 help 194 Build the blk-crypto subsystem. Enabling this lets the 195 block layer handle encryption, so users can take 196 advantage of inline encryption hardware if present. 197 198config BLK_INLINE_ENCRYPTION_FALLBACK 199 bool "Enable crypto API fallback for blk-crypto" 200 depends on BLK_INLINE_ENCRYPTION 201 select CRYPTO 202 select CRYPTO_SKCIPHER 203 help 204 Enabling this lets the block layer handle inline encryption 205 by falling back to the kernel crypto API when inline 206 encryption hardware is not present. 207 208source "block/partitions/Kconfig" 209 210config BLOCK_COMPAT 211 def_bool COMPAT 212 213config BLK_MQ_PCI 214 def_bool PCI 215 216config BLK_MQ_VIRTIO 217 bool 218 depends on VIRTIO 219 default y 220 221config BLK_MQ_RDMA 222 bool 223 depends on INFINIBAND 224 default y 225 226config BLK_PM 227 def_bool PM 228 229# do not use in new code 230config BLOCK_HOLDER_DEPRECATED 231 bool 232 233source "block/Kconfig.iosched" 234 235endif # BLOCK 236