1 # SPDX-License-Identifier: GPL-2.0
3 # Block layer core configuration
6 bool "Enable the block layer" if EXPERT
11 Provide block layer support for the kernel.
13 Disable this option to remove the block layer support from the
14 kernel. This may be useful for embedded devices.
16 If this option is disabled:
18 - block device files will become unusable
19 - some filesystems (such as ext3) will become unavailable.
21 Also, SCSI character devices and USB storage will be disabled since
22 they make use of various block layer definitions and facilities.
24 Say Y here unless you know you really don't want to mount disks and
29 config BLK_RQ_ALLOC_TIME
32 config BLK_SCSI_REQUEST
35 config BLK_CGROUP_RWSTAT
39 bool "Block layer SG support v4"
41 select BLK_SCSI_REQUEST
43 Saying Y here will enable generic SG (SCSI generic) v4 support
46 Unlike SG v3 (aka block/scsi_ioctl.c drivers/scsi/sg.c), SG v4
47 can handle complicated SCSI commands: tagged variable length cdbs
48 with bidirectional data transfers and generic request/response
49 protocols (e.g. Task Management Functions and SMP in Serial
52 This option is required by recent UDEV versions to properly
53 access device serial numbers, etc.
58 bool "Block layer SG support v4 helper lib"
60 select BLK_SCSI_REQUEST
62 Subsystems will normally enable this if needed. Users will not
63 normally need to manually enable this.
67 config BLK_DEV_INTEGRITY
68 bool "Block layer data integrity support"
70 Some storage devices allow extra information to be
71 stored/retrieved to help protect the data. The block layer
72 data integrity option provides hooks which can be used by
73 filesystems to ensure better data integrity.
75 Say yes here if you have a storage device that provides the
76 T10/SCSI Data Integrity Field or the T13/ATA External Path
77 Protection. If in doubt, say N.
79 config BLK_DEV_INTEGRITY_T10
81 depends on BLK_DEV_INTEGRITY
85 bool "Zoned block device support"
86 select MQ_IOSCHED_DEADLINE
88 Block layer zoned block device support. This option enables
89 support for ZAC/ZBC host-managed and host-aware zoned block devices.
91 Say yes here if you have a ZAC or ZBC storage device.
93 config BLK_DEV_THROTTLING
94 bool "Block layer bio throttling support"
95 depends on BLK_CGROUP=y
96 select BLK_CGROUP_RWSTAT
98 Block layer bio throttling support. It can be used to limit
99 the IO rate to a device. IO rate policies are per cgroup and
100 one needs to mount and use blkio cgroup controller for creating
101 cgroups and specifying per device IO rate policies.
103 See Documentation/admin-guide/cgroup-v1/blkio-controller.rst for more information.
105 config BLK_DEV_THROTTLING_LOW
106 bool "Block throttling .low limit interface support (EXPERIMENTAL)"
107 depends on BLK_DEV_THROTTLING
109 Add .low limit interface for block throttling. The low limit is a best
110 effort limit to prioritize cgroups. Depending on the setting, the limit
111 can be used to protect cgroups in terms of bandwidth/iops and better
112 utilize disk resource.
114 Note, this is an experimental interface and could be changed someday.
116 config BLK_CMDLINE_PARSER
117 bool "Block device command line partition parser"
119 Enabling this option allows you to specify the partition layout from
120 the kernel boot args. This is typically of use for embedded devices
121 which don't otherwise have any standardized method for listing the
122 partitions on a block device.
124 See Documentation/block/cmdline-partition.rst for more information.
127 bool "Enable support for block device writeback throttling"
129 Enabling this option enables the block layer to throttle buffered
130 background writeback from the VM, making it more smooth and having
131 less impact on foreground operations. The throttling is done
132 dynamically on an algorithm loosely based on CoDel, factoring in
133 the realtime performance of the disk.
135 config BLK_CGROUP_IOLATENCY
136 bool "Enable support for latency based cgroup IO protection"
137 depends on BLK_CGROUP=y
139 Enabling this option enables the .latency interface for IO throttling.
140 The IO controller will attempt to maintain average IO latencies below
141 the configured latency target, throttling anybody with a higher latency
142 target than the victimized group.
144 Note, this is an experimental interface and could be changed someday.
146 config BLK_CGROUP_IOCOST
147 bool "Enable support for cost model based cgroup IO controller"
148 depends on BLK_CGROUP=y
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.
157 bool "Multiqueue writeback throttling"
161 Enable writeback throttling by default on multiqueue devices.
162 Multiqueue currently doesn't have support for IO scheduling,
163 enabling this option is recommended.
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 menu "Partition Types"
190 source "block/partitions/Kconfig"
198 depends on BLOCK && COMPAT
203 depends on BLOCK && PCI
208 depends on BLOCK && VIRTIO
213 depends on BLOCK && INFINIBAND
219 source "block/Kconfig.iosched"