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