From: "yukuai (C)" <yukuai3@huawei.com>
To: <paolo.valente@linaro.org>, <axboe@kernel.dk>
Cc: <linux-block@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<yi.zhang@huawei.com>
Subject: Re: [PATCH 0/3] optimize the queue idle judgment
Date: Tue, 20 Jul 2021 20:33:50 +0800 [thread overview]
Message-ID: <bad3d311-b232-1969-bb16-00ab6a64a951@huawei.com> (raw)
In-Reply-To: <20210714094529.758808-1-yukuai3@huawei.com>
On 2021/07/14 17:45, Yu Kuai wrote:
> bfqq might plug I/O dispatch when it remains temporarily empty while
> being served, this will benefit for both sequence io bandwidth and relative
> sync io control.
>
> This path set tries to extend the two special cases that idle is not
> needed, and can get better bandwidth.
>
> 1) only one group is activated.
> 2) when more than one groups are activated, all queues are issuring
> requests with same size.
>
> Yu Kuai (3):
> block, bfq: do not idle if only one cgroup is activated
> block, bfq: add support to record request size information
> block, bfq: consider request size in bfq_asymmetric_scenario()
>
> block/bfq-iosched.c | 50 +++++++++++++++++++++++++++++++++++++--------
> block/bfq-iosched.h | 16 +++++++++++++++
> 2 files changed, 57 insertions(+), 9 deletions(-)
>
ping ...
prev parent reply other threads:[~2021-07-20 12:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 9:45 [PATCH 0/3] optimize the queue idle judgment Yu Kuai
2021-07-14 9:45 ` [PATCH 1/3] block, bfq: do not idle if only one cgroup is activated Yu Kuai
2021-07-24 7:12 ` Paolo Valente
2021-07-26 1:15 ` yukuai (C)
2021-07-31 7:10 ` yukuai (C)
2021-08-03 7:07 ` Paolo Valente
2021-08-03 11:30 ` yukuai (C)
2021-07-14 9:45 ` [PATCH 2/3] block, bfq: add support to record request size information Yu Kuai
2021-07-14 9:45 ` [PATCH 3/3] block, bfq: consider request size in bfq_asymmetric_scenario() Yu Kuai
2021-07-20 12:33 ` yukuai (C) [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=bad3d311-b232-1969-bb16-00ab6a64a951@huawei.com \
--to=yukuai3@huawei.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.valente@linaro.org \
--cc=yi.zhang@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).