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