From: Yu Kuai <yukuai@kernel.org>
To: axboe@kernel.dk, bvanassche@acm.org, nilay@linux.ibm.com
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
yukuai3@huawei.com, yi.zhang@huawei.com, yangerkun@huawei.com,
johnny.chenyi@huawei.com
Subject: [PATCH v3 7/7] blk-mq: add documentation for new queue attribute async_dpeth
Date: Fri, 10 Oct 2025 10:28:09 +0800 [thread overview]
Message-ID: <20251010022812.2985286-8-yukuai@kernel.org> (raw)
In-Reply-To: <20251010022812.2985286-1-yukuai@kernel.org>
From: Yu Kuai <yukuai3@huawei.com>
Explain the attribute and the default value in different case.
Signed-off-by: Yu Kuai <yukuai3@huawei.com>
Reviewed-by: Nilay Shroff <nilay@linux.ibm.com>
---
Documentation/ABI/stable/sysfs-block | 34 ++++++++++++++++++++++++++++
1 file changed, 34 insertions(+)
diff --git a/Documentation/ABI/stable/sysfs-block b/Documentation/ABI/stable/sysfs-block
index 0ed10aeff86b..aa1e94169666 100644
--- a/Documentation/ABI/stable/sysfs-block
+++ b/Documentation/ABI/stable/sysfs-block
@@ -609,6 +609,40 @@ Description:
enabled, and whether tags are shared.
+What: /sys/block/<disk>/queue/async_depth
+Date: August 2025
+Contact: linux-block@vger.kernel.org
+Description:
+ [RW] Controls how many asynchronous requests may be allocated in the
+ block layer. The value is always capped at nr_requests.
+
+ When no elevator is active (none):
+ - async_depth is always equal to nr_requests.
+
+ For bfq scheduler:
+ - By default, async_depth is set to 75% of nr_requests.
+ Internal limits are then derived from this value:
+ * Sync writes: limited to async_depth (≈75% of nr_requests).
+ * Async I/O: limited to ~2/3 of async_depth (≈50% of nr_requests).
+
+ If a bfq_queue is weight-raised:
+ * Sync writes: limited to ~1/2 of async_depth (≈37% of nr_requests).
+ * Async I/O: limited to ~1/4 of async_depth (≈18% of nr_requests).
+
+ - If the user writes a custom value to async_depth, BFQ will recompute
+ these limits proportionally based on the new value.
+
+ For Kyber:
+ - By default async_depth is set to 75% of nr_requests.
+ - If the user writes a custom value to async_depth, then it override the
+ default and directly control the limit for writes and async I/O.
+
+ For mq-deadline:
+ - By default async_depth is set to nr_requests.
+ - If the user writes a custom value to async_depth, then it override the
+ default and directly control the limit for writes and async I/O.
+
+
What: /sys/block/<disk>/queue/nr_zones
Date: November 2018
Contact: Damien Le Moal <damien.lemoal@wdc.com>
--
2.51.0
prev parent reply other threads:[~2025-10-10 2:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 2:28 [PATCH v3 0/7] blk-mq: introduce new queue attribute async_depth Yu Kuai
2025-10-10 2:28 ` [PATCH v3 1/7] block: convert nr_requests to unsigned int Yu Kuai
2025-10-10 2:28 ` [PATCH v3 2/7] blk-mq-sched: unify elevators checking for async requests Yu Kuai
2025-10-10 2:28 ` [PATCH v3 3/7] blk-mq: add a new queue sysfs attribute async_depth Yu Kuai
2025-10-10 4:47 ` Nilay Shroff
2025-10-10 2:28 ` [PATCH v3 4/7] kyber: covert to use request_queue->async_depth Yu Kuai
2025-10-10 2:28 ` [PATCH v3 5/7] mq-deadline: " Yu Kuai
2025-10-10 2:28 ` [PATCH v3 6/7] block, bfq: convert " Yu Kuai
2025-10-10 2:28 ` Yu Kuai [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251010022812.2985286-8-yukuai@kernel.org \
--to=yukuai@kernel.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=johnny.chenyi@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nilay@linux.ibm.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®