# SPDX-License-Identifier: GPL-2.0
#
# Block layer core configuration
#
menuconfig [31mCONFIG_BLOCK[0m
bool "Enable the block layer" if [31mCONFIG_EXPERT[0m
default y
select [31mCONFIG_SBITMAP[0m
select [31mCONFIG_SRCU[0m
help
Provide block layer support for the kernel.
Disable this option to remove the block layer support from the
kernel. This may be useful for embedded devices.
If this option is disabled:
- block device files will become unusable
- some filesystems (such as ext3) will become unavailable.
Also, [31mCONFIG_SCSI[0m character devices and [31mCONFIG_USB[0m storage will be disabled since
they make use of various block layer definitions and facilities.
Say Y here unless you know you really don't want to mount disks and
suchlike.
if [31mCONFIG_BLOCK[0m
config [31mCONFIG_BLK_RQ_ALLOC_TIME[0m
bool
config [31mCONFIG_BLK_SCSI_REQUEST[0m
bool
config [31mCONFIG_BLK_DEV_BSG[0m
bool "Block layer SG support v4"
default y
select [31mCONFIG_BLK_SCSI_REQUEST[0m
help
Saying Y here will enable generic SG ([31mCONFIG_SCSI[0m generic) v4 support
for any block device.
Unlike SG v3 (aka block/scsi_ioctl.c drivers/scsi/sg.c), SG v4
can handle complicated [31mCONFIG_SCSI[0m commands: tagged variable length cdbs
with bidirectional data transfers and generic request/response
protocols (e.g. Task Management Functions and [31mCONFIG_SMP[0m in Serial
Attached [31mCONFIG_SCSI[0m).
This option is required by recent UDEV versions to properly
access device serial numbers, etc.
If unsure, say Y.
config [31mCONFIG_BLK_DEV_BSGLIB[0m
bool "Block layer SG support v4 helper lib"
select [31mCONFIG_BLK_DEV_BSG[0m
select [31mCONFIG_BLK_SCSI_REQUEST[0m
help
Subsystems will normally enable this if needed. Users will not
normally need to manually enable this.
If unsure, say N.
config [31mCONFIG_BLK_DEV_INTEGRITY[0m
bool "Block layer data integrity support"
select [31mCONFIG_CRC_T10DIF[0m if [31mCONFIG_BLK_DEV_INTEGRITY[0m
---help---
Some storage devices allow extra information to be
stored/retrieved to help protect the data. The block layer
data integrity option provides hooks which can be used by
filesystems to ensure better data integrity.
Say yes here if you have a storage device that provides the
T10/[31mCONFIG_SCSI[0m Data Integrity Field or the T13/[31mCONFIG_ATA[0m External Path
Protection. If in doubt, say N.
config [31mCONFIG_BLK_DEV_ZONED[0m
bool "Zoned block device support"
select [31mCONFIG_MQ_IOSCHED_DEADLINE[0m
---help---
Block layer zoned block device support. This option enables
support for ZAC/ZBC host-managed and host-aware zoned block devices.
Say yes here if you have a ZAC or ZBC storage device.
config [31mCONFIG_BLK_DEV_THROTTLING[0m
bool "Block layer bio throttling support"
depends on [31mCONFIG_BLK_CGROUP[0m=y
---help---
Block layer bio throttling support. It can be used to limit
the IO rate to a device. IO rate policies are per cgroup and
one needs to mount and use blkio cgroup controller for creating
cgroups and specifying per device IO rate policies.
See Documentation/admin-guide/cgroup-v1/blkio-controller.rst for more information.
config [31mCONFIG_BLK_DEV_THROTTLING_LOW[0m
bool "Block throttling .low limit interface support (EXPERIMENTAL)"
depends on [31mCONFIG_BLK_DEV_THROTTLING[0m
---help---
Add .low limit interface for block throttling. The low limit is a best
effort limit to prioritize cgroups. Depending on the setting, the limit
can be used to protect cgroups in terms of bandwidth/iops and better
utilize disk resource.
Note, this is an experimental interface and could be changed someday.
config [31mCONFIG_BLK_CMDLINE_PARSER[0m
bool "Block device command line partition parser"
---help---
Enabling this option allows you to specify the partition layout from
the kernel boot args. This is typically of use for embedded devices
which don't otherwise have any standardized method for listing the
partitions on a block device.
See Documentation/block/cmdline-partition.rst for more information.
config [31mCONFIG_BLK_WBT[0m
bool "Enable support for block device writeback throttling"
---help---
Enabling this option enables the block layer to throttle buffered
background writeback from the VM, making it more smooth and having
less impact on foreground operations. The throttling is done
dynamically on an algorithm loosely based on CoDel, factoring in
the realtime performance of the disk.
config [31mCONFIG_BLK_CGROUP_IOLATENCY[0m
bool "Enable support for latency based cgroup IO protection"
depends on [31mCONFIG_BLK_CGROUP[0m=y
---help---
Enabling this option enables the .latency interface for IO throttling.
The IO controller will attempt to maintain average IO latencies below
the configured latency target, throttling anybody with a higher latency
target than the victimized group.
Note, this is an experimental interface and could be changed someday.
config [31mCONFIG_BLK_CGROUP_IOCOST[0m
bool "Enable support for cost model based cgroup IO controller"
depends on [31mCONFIG_BLK_CGROUP[0m=y
select [31mCONFIG_BLK_RQ_ALLOC_TIME[0m
---help---
Enabling this option enables the .weight interface for cost
model based proportional IO control. The IO controller
distributes IO capacity between different groups based on
their share of the overall weight distribution.
config [31mCONFIG_BLK_WBT_MQ[0m
bool "Multiqueue writeback throttling"
default y
depends on [31mCONFIG_BLK_WBT[0m
---help---
Enable writeback throttling by default on multiqueue devices.
Multiqueue currently doesn't have support for IO scheduling,
enabling this option is recommended.
config [31mCONFIG_BLK_DEBUG_FS[0m
bool "Block layer debugging information in debugfs"
default y
depends on [31mCONFIG_DEBUG_FS[0m
---help---
Include block layer debugging information in debugfs. This information
is mostly useful for kernel developers, but it doesn't incur any cost
at runtime.
Unless you are building a kernel for a tiny system, you should
say Y here.
config [31mCONFIG_BLK_DEBUG_FS_ZONED[0m
bool
default [31mCONFIG_BLK_DEBUG_FS[0m && [31mCONFIG_BLK_DEV_ZONED[0m
config [31mCONFIG_BLK_SED_OPAL[0m
bool "Logic for interfacing with Opal enabled SEDs"
---help---
Builds Logic for interfacing with Opal enabled controllers.
Enabling this option enables users to setup/unlock/lock
Locking ranges for SED devices using the Opal protocol.
menu "Partition Types"
source "block/partitions/Kconfig"
endmenu
endif # [31mCONFIG_BLOCK[0m
config [31mCONFIG_BLOCK_COMPAT[0m
bool
depends on [31mCONFIG_BLOCK[0m && [31mCONFIG_COMPAT[0m
default y
config [31mCONFIG_BLK_MQ_PCI[0m
bool
depends on [31mCONFIG_BLOCK[0m && [31mCONFIG_PCI[0m
default y
config [31mCONFIG_BLK_MQ_VIRTIO[0m
bool
depends on [31mCONFIG_BLOCK[0m && [31mCONFIG_VIRTIO[0m
default y
config [31mCONFIG_BLK_MQ_RDMA[0m
bool
depends on [31mCONFIG_BLOCK[0m && [31mCONFIG_INFINIBAND[0m
default y
config [31mCONFIG_BLK_PM[0m
def_bool [31mCONFIG_BLOCK[0m && [31mCONFIG_PM[0m
source "block/Kconfig.iosched"