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 0/7] blk-mq: introduce new queue attribute async_depth
Date: Fri, 10 Oct 2025 10:28:02 +0800 [thread overview]
Message-ID: <20251010022812.2985286-1-yukuai@kernel.org> (raw)
From: Yu Kuai <yukuai3@huawei.com>
Changes in v3:
- use guard()/scope_guard() in patch 3;
- add review tag other than patch 3;
Changes in v2:
- keep limit_depth() method for kyber and mq-deadline in patch 3;
- add description about sysfs api change for kyber and mq-deadline;
- improve documentation in patch 7;
- add review tag for patch 1;
Background and motivation:
At first, we test a performance regression from 5.10 to 6.6 in
downstream kernel(described in patch 5), the regression is related to
async_depth in mq-dealine.
While trying to fix this regression, Bart suggests add a new attribute
to request_queue, and I think this is a good idea because all elevators
have similar logical, however only mq-deadline allow user to configure
async_depth.
patch 1-3 add new queue attribute async_depth;
patch 4 convert kyber to use request_queue->async_depth;
patch 5 covnert mq-dedaline to use request_queue->async_depth, also the
performance regression will be fixed;
patch 6 convert bfq to use request_queue->async_depth;
Yu Kuai (7):
block: convert nr_requests to unsigned int
blk-mq-sched: unify elevators checking for async requests
blk-mq: add a new queue sysfs attribute async_depth
kyber: covert to use request_queue->async_depth
mq-deadline: covert to use request_queue->async_depth
block, bfq: convert to use request_queue->async_depth
blk-mq: add documentation for new queue attribute async_dpeth
Documentation/ABI/stable/sysfs-block | 34 +++++++++++++++
block/bfq-iosched.c | 45 ++++++++-----------
block/blk-core.c | 1 +
block/blk-mq-sched.h | 5 +++
block/blk-mq.c | 64 +++++++++++++++++-----------
block/blk-sysfs.c | 42 ++++++++++++++++++
block/elevator.c | 1 +
block/kyber-iosched.c | 33 +++-----------
block/mq-deadline.c | 39 +++--------------
include/linux/blkdev.h | 3 +-
10 files changed, 152 insertions(+), 115 deletions(-)
--
2.51.0
next 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 Yu Kuai [this message]
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 ` [PATCH v3 7/7] blk-mq: add documentation for new queue attribute async_dpeth Yu Kuai
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-1-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®