From 102a0743326a03cd1a1202ceda21e175b7d3575c Mon Sep 17 00:00:00 2001 From: hc <hc@nodka.com> Date: Tue, 20 Feb 2024 01:20:52 +0000 Subject: [PATCH] add new system file --- kernel/block/Kconfig | 115 ++++++++++++++++++++++++++++----------------------------- 1 files changed, 56 insertions(+), 59 deletions(-) diff --git a/kernel/block/Kconfig b/kernel/block/Kconfig index d4f96c7..aabfb85 100644 --- a/kernel/block/Kconfig +++ b/kernel/block/Kconfig @@ -26,31 +26,13 @@ if BLOCK -config LBDAF - bool "Support for large (2TB+) block devices and files" - depends on !64BIT - default y - help - Enable block devices or files of size 2TB and larger. - - This option is required to support the full capacity of large - (2TB+) block devices, including RAID, disk, Network Block Device, - Logical Volume Manager (LVM) and loopback. - - This option also enables support for single files larger than - 2TB. - - The ext4 filesystem requires that this feature be enabled in - order to support filesystems that have the huge_file feature - enabled. Otherwise, it will refuse to mount in the read-write - mode any filesystems that use the huge_file feature, which is - enabled by default by mke2fs.ext4. - - The GFS2 filesystem also requires this feature. - - If unsure, say Y. +config BLK_RQ_ALLOC_TIME + bool config BLK_SCSI_REQUEST + bool + +config BLK_CGROUP_RWSTAT bool config BLK_DEV_BSG @@ -74,7 +56,6 @@ config BLK_DEV_BSGLIB bool "Block layer SG support v4 helper lib" - default n select BLK_DEV_BSG select BLK_SCSI_REQUEST help @@ -85,8 +66,7 @@ config BLK_DEV_INTEGRITY bool "Block layer data integrity support" - select CRC_T10DIF if BLK_DEV_INTEGRITY - ---help--- + 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 @@ -96,31 +76,37 @@ T10/SCSI Data Integrity Field or the T13/ATA External Path Protection. If in doubt, say N. +config BLK_DEV_INTEGRITY_T10 + tristate + depends on BLK_DEV_INTEGRITY + select CRC_T10DIF + config BLK_DEV_ZONED bool "Zoned block device support" - ---help--- + select MQ_IOSCHED_DEADLINE + help Block layer zoned block device support. This option enables - support for ZAC/ZBC host-managed and host-aware zoned block devices. + support for ZAC/ZBC/ZNS host-managed and host-aware zoned block + devices. - Say yes here if you have a ZAC or ZBC storage device. + Say yes here if you have a ZAC, ZBC, or ZNS storage device. config BLK_DEV_THROTTLING bool "Block layer bio throttling support" depends on BLK_CGROUP=y - default n - ---help--- + select BLK_CGROUP_RWSTAT + 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/cgroup-v1/blkio-controller.txt for more information. + See Documentation/admin-guide/cgroup-v1/blkio-controller.rst for more information. config BLK_DEV_THROTTLING_LOW bool "Block throttling .low limit interface support (EXPERIMENTAL)" depends on BLK_DEV_THROTTLING - default n - ---help--- + 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 @@ -130,30 +116,34 @@ config BLK_CMDLINE_PARSER bool "Block device command line partition parser" - default n - ---help--- + 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.txt for more information. + See Documentation/block/cmdline-partition.rst for more information. config BLK_WBT bool "Enable support for block device writeback throttling" - default n - ---help--- + 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 BLK_WBT_MQ + bool "Enable writeback throttling by default" + default y + depends on BLK_WBT + help + Enable writeback throttling by default for request-based block devices. + config BLK_CGROUP_IOLATENCY bool "Enable support for latency based cgroup IO protection" depends on BLK_CGROUP=y - default n - ---help--- + 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 @@ -161,27 +151,31 @@ Note, this is an experimental interface and could be changed someday. -config BLK_WBT_SQ - bool "Single queue writeback throttling" - default n - depends on BLK_WBT - ---help--- - Enable writeback throttling by default on legacy single queue devices +config BLK_CGROUP_IOCOST + bool "Enable support for cost model based cgroup IO controller" + depends on BLK_CGROUP=y + select BLK_RQ_IO_DATA_LEN + select BLK_RQ_ALLOC_TIME + 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 BLK_WBT_MQ - bool "Multiqueue writeback throttling" - default y - depends on BLK_WBT - ---help--- - Enable writeback throttling by default on multiqueue devices. - Multiqueue currently doesn't have support for IO scheduling, - enabling this option is recommended. +config BLK_CGROUP_IOPRIO + bool "Cgroup I/O controller for assigning an I/O priority class" + depends on BLK_CGROUP + help + Enable the .prio interface for assigning an I/O priority class to + requests. The I/O priority class affects the order in which an I/O + scheduler and block devices process requests. Only some I/O schedulers + and some block devices support I/O priorities. config BLK_DEBUG_FS bool "Block layer debugging information in debugfs" default y depends on DEBUG_FS - ---help--- + 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. @@ -195,7 +189,7 @@ config BLK_SED_OPAL bool "Logic for interfacing with Opal enabled SEDs" - ---help--- + 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. @@ -211,7 +205,7 @@ bool "Enable crypto API fallback for blk-crypto" depends on BLK_INLINE_ENCRYPTION select CRYPTO - select CRYPTO_BLKCIPHER + select CRYPTO_SKCIPHER help Enabling this lets the block layer handle inline encryption by falling back to the kernel crypto API when inline @@ -245,4 +239,7 @@ depends on BLOCK && INFINIBAND default y -source block/Kconfig.iosched +config BLK_PM + def_bool BLOCK && PM + +source "block/Kconfig.iosched" -- Gitblit v1.6.2