From: "yukuai (C)" <yukuai3@huawei.com>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: Jens Axboe <axboe@kernel.dk>, Ming Lei <ming.lei@redhat.com>,
"Christoph Hellwig" <hch@lst.de>,
linux-block <linux-block@vger.kernel.org>,
chenzhou <chenzhou10@huawei.com>,
"houtao (A)" <houtao1@huawei.com>
Subject: Re: question about relative control for sync io using bfq
Date: Wed, 24 Feb 2021 17:30:31 +0800 [thread overview]
Message-ID: <591785c0-d762-8a96-8d54-d52b6ac3595e@huawei.com> (raw)
In-Reply-To: <9E3D68B7-35D3-412E-8196-BF5AACDB1377@linaro.org>
On 2021/02/23 18:52, Paolo Valente wrote:
> In a sense, my solution is an evolution of your initial solution. It
> is conceptually very simple: just track whether all weights and all
> I/O sizes are equal. When this condition holds true, no idling is
> needed. When it does not hold, idling is needed. Your case would be
> solved, service guarantees would be always preserved.
Hi,
The solution sounds good, and it's ture that my case would be solved.
Thank you very much!
Yu Kuai
prev parent reply other threads:[~2021-02-24 9:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 13:15 question about relative control for sync io using bfq yukuai (C)
[not found] ` <b4163392-0462-ff6f-b958-1f96f33d69e6-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2021-01-14 12:24 ` [PATCH] bfq: don't check active group if bfq.weight is not changed Yu Kuai
2021-01-14 12:24 ` Yu Kuai
2021-01-15 13:35 ` kernel test robot
2021-01-15 13:35 ` kernel test robot
2021-01-15 13:35 ` kernel test robot
2021-01-15 13:35 ` kernel test robot
2021-01-15 13:35 ` kernel test robot
2021-01-15 13:35 ` kernel test robot
[not found] ` <20210114122426.603813-1-yukuai3-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2021-01-22 9:46 ` Paolo Valente
2021-01-22 9:46 ` Paolo Valente
2021-01-16 8:59 ` question about relative control for sync io using bfq yukuai (C)
2021-01-16 10:45 ` Paolo Valente
2021-01-22 10:09 ` Paolo Valente
[not found] ` <7c28a80f-dea9-d701-0399-a22522c4509b@huawei.com>
2021-02-05 7:49 ` Paolo Valente
2021-02-07 12:49 ` yukuai (C)
2021-02-08 19:05 ` Paolo Valente
2021-02-19 12:03 ` yukuai (C)
2021-02-23 10:52 ` Paolo Valente
2021-02-24 9:30 ` 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=591785c0-d762-8a96-8d54-d52b6ac3595e@huawei.com \
--to=yukuai3@huawei.com \
--cc=axboe@kernel.dk \
--cc=chenzhou10@huawei.com \
--cc=hch@lst.de \
--cc=houtao1@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=paolo.valente@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.