From: Jeff Moyer <jmoyer@redhat.com>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: axboe@kernel.dk, bvanassche@acm.org, ming.lei@redhat.com,
nilay@linux.ibm.com, 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: Re: [PATCH 5/7] mq-deadline: covert to use request_queue->async_depth
Date: Thu, 02 Oct 2025 14:56:11 -0400 [thread overview]
Message-ID: <x497bxdrv3o.fsf@segfault.usersys.redhat.com> (raw)
In-Reply-To: <20250930071111.1218494-6-yukuai1@huaweicloud.com> (Yu Kuai's message of "Tue, 30 Sep 2025 15:11:09 +0800")
Yu Kuai <yukuai1@huaweicloud.com> writes:
> Fix this problem by converting to request_queue->async_depth, where
> min_shallow_depth is set each time async_depth is updated.
Removing the iosched/async_depth attribute may cause problems for
existing scripts or udev rules. I'm not sure if we care, but the
changelog does not seem to address this.
-Jeff
next prev parent reply other threads:[~2025-10-02 18:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 7:11 [PATCH 0/7] blk-mq: introduce new queue attribute async_depth Yu Kuai
2025-09-30 7:11 ` [PATCH 1/7] block: convert nr_requests to unsigned int Yu Kuai
2025-10-02 15:13 ` Nilay Shroff
2025-09-30 7:11 ` [PATCH 2/7] blk-mq-sched: unify elevators checking for async requests Yu Kuai
2025-09-30 7:11 ` [PATCH 3/7] blk-mq: add a new queue sysfs attribute async_depth Yu Kuai
2025-10-02 15:10 ` Nilay Shroff
2025-10-06 1:57 ` Yu Kuai
2025-10-09 0:48 ` Yu Kuai
2025-10-09 6:42 ` Yu Kuai
2025-09-30 7:11 ` [PATCH 4/7] kyber: covert to use request_queue->async_depth Yu Kuai
2025-09-30 7:11 ` [PATCH 5/7] mq-deadline: " Yu Kuai
2025-10-02 18:56 ` Jeff Moyer [this message]
2025-09-30 7:11 ` [PATCH 6/7] block, bfq: convert " Yu Kuai
2025-09-30 7:11 ` [PATCH 7/7] blk-mq: add documentation for new queue attribute async_dpeth Yu Kuai
2025-10-02 15:12 ` Nilay Shroff
2025-10-06 2:00 ` 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=x497bxdrv3o.fsf@segfault.usersys.redhat.com \
--to=jmoyer@redhat.com \
--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=ming.lei@redhat.com \
--cc=nilay@linux.ibm.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.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;
as well as URLs for NNTP newsgroup(s).