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 EMBEDDED 7 default y 6 default y 8 select FS_IOMAP << 9 select SBITMAP << 10 help 7 help 11 Provide block layer support for the k 8 Provide block layer support for the kernel. 12 9 13 Disable this option to remove the blo 10 Disable this option to remove the block layer support from the 14 kernel. This may be useful for embedd 11 kernel. This may be useful for embedded devices. 15 12 16 If this option is disabled: 13 If this option is disabled: 17 14 18 - block device files will become un 15 - block device files will become unusable 19 - some filesystems (such as ext3) w 16 - some filesystems (such as ext3) will become unavailable. 20 17 21 Also, SCSI character devices and USB 18 Also, SCSI character devices and USB storage will be disabled since 22 they make use of various block layer 19 they make use of various block layer definitions and facilities. 23 20 24 Say Y here unless you know you really 21 Say Y here unless you know you really don't want to mount disks and 25 suchlike. 22 suchlike. 26 23 27 if BLOCK 24 if BLOCK 28 25 29 config BLOCK_LEGACY_AUTOLOAD !! 26 config LBDAF 30 bool "Legacy autoloading support" !! 27 bool "Support for large (2TB+) block devices and files" >> 28 depends on !64BIT 31 default y 29 default y 32 help 30 help 33 Enable loading modules and creating !! 31 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 32 39 config BLK_RQ_ALLOC_TIME !! 33 This option is required to support the full capacity of large 40 bool !! 34 (2TB+) block devices, including RAID, disk, Network Block Device, >> 35 Logical Volume Manager (LVM) and loopback. >> 36 >> 37 This option also enables support for single files larger than >> 38 2TB. >> 39 >> 40 The ext4 filesystem requires that this feature be enabled in >> 41 order to support filesystems that have the huge_file feature >> 42 enabled. Otherwise, it will refuse to mount in the read-write >> 43 mode any filesystems that use the huge_file feature, which is >> 44 enabled by default by mke2fs.ext4. 41 45 42 config BLK_CGROUP_RWSTAT !! 46 The GFS2 filesystem also requires this feature. 43 bool << 44 47 45 config BLK_CGROUP_PUNT_BIO !! 48 If unsure, say Y. 46 bool << 47 49 48 config BLK_DEV_BSG_COMMON !! 50 config BLK_DEV_BSG 49 tristate !! 51 bool "Block layer SG support v4" >> 52 default y >> 53 help >> 54 Saying Y here will enable generic SG (SCSI generic) v4 support >> 55 for any block device. 50 56 51 config BLK_ICQ !! 57 Unlike SG v3 (aka block/scsi_ioctl.c drivers/scsi/sg.c), SG v4 52 bool !! 58 can handle complicated SCSI commands: tagged variable length cdbs >> 59 with bidirectional data transfers and generic request/response >> 60 protocols (e.g. Task Management Functions and SMP in Serial >> 61 Attached SCSI). 53 62 54 config BLK_DEV_BSGLIB !! 63 This option is required by recent UDEV versions to properly 55 bool "Block layer SG support v4 helper !! 64 access device serial numbers, etc. 56 select BLK_DEV_BSG_COMMON << 57 help << 58 Subsystems will normally enable this << 59 normally need to manually enable thi << 60 65 61 If unsure, say N. !! 66 If unsure, say Y. 62 67 63 config BLK_DEV_INTEGRITY 68 config BLK_DEV_INTEGRITY 64 bool "Block layer data integrity suppo 69 bool "Block layer data integrity support" 65 select CRC_T10DIF !! 70 ---help--- 66 select CRC64_ROCKSOFT << 67 help << 68 Some storage devices allow extra infor 71 Some storage devices allow extra information to be 69 stored/retrieved to help protect the d 72 stored/retrieved to help protect the data. The block layer 70 data integrity option provides hooks w 73 data integrity option provides hooks which can be used by 71 filesystems to ensure better data inte 74 filesystems to ensure better data integrity. 72 75 73 Say yes here if you have a storage dev 76 Say yes here if you have a storage device that provides the 74 T10/SCSI Data Integrity Field or the T 77 T10/SCSI Data Integrity Field or the T13/ATA External Path 75 Protection. If in doubt, say N. 78 Protection. If in doubt, say N. 76 79 77 config BLK_DEV_WRITE_MOUNTED !! 80 endif # BLOCK 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 << 98 bool "Zoned block device support" << 99 help << 100 Block layer zoned block device support << 101 support for ZAC/ZBC/ZNS host-managed a << 102 devices. << 103 << 104 Say yes here if you have a ZAC, ZBC, o << 105 << 106 config BLK_DEV_THROTTLING << 107 bool "Block layer bio throttling suppo << 108 depends on BLK_CGROUP << 109 select BLK_CGROUP_RWSTAT << 110 help << 111 Block layer bio throttling support. It << 112 the IO rate to a device. IO rate polic << 113 one needs to mount and use blkio cgrou << 114 cgroups and specifying per device IO r << 115 << 116 See Documentation/admin-guide/cgroup-v << 117 << 118 config BLK_WBT << 119 bool "Enable support for block device << 120 help << 121 Enabling this option enables the block << 122 background writeback from the VM, maki << 123 less impact on foreground operations. << 124 dynamically on an algorithm loosely ba << 125 the realtime performance of the disk. << 126 << 127 config BLK_WBT_MQ << 128 bool "Enable writeback throttling by d << 129 default y << 130 depends on BLK_WBT << 131 help << 132 Enable writeback throttling by default << 133 << 134 config BLK_CGROUP_IOLATENCY << 135 bool "Enable support for latency based << 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 << 176 depends on DEBUG_FS << 177 help << 178 Include block layer debugging informat << 179 is mostly useful for kernel developers << 180 at runtime. << 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 << 195 config BLK_INLINE_ENCRYPTION << 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 << 212 source "block/partitions/Kconfig" << 213 << 214 config BLK_MQ_PCI << 215 def_bool PCI << 216 81 217 config BLK_MQ_VIRTIO !! 82 config BLOCK_COMPAT 218 bool 83 bool 219 depends on VIRTIO !! 84 depends on BLOCK && COMPAT 220 default y 85 default y 221 86 222 config BLK_PM !! 87 source block/Kconfig.iosched 223 def_bool PM << 224 << 225 # do not use in new code << 226 config BLOCK_HOLDER_DEPRECATED << 227 bool << 228 << 229 config BLK_MQ_STACKING << 230 bool << 231 << 232 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.