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