From: Jens Axboe <axboe@kernel.dk>
To: Tejun Heo <tj@kernel.org>, Paolo Valente <paolo.valente@linaro.org>
Cc: lennart@poettering.net, linux-block <linux-block@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Mark Brown <broonie@kernel.org>,
ANGELO RUOCCO <220530@studenti.unimore.it>
Subject: Re: unify the interface of the proportional-share policy in blkio/io
Date: Tue, 9 Jan 2018 12:53:24 -0700 [thread overview]
Message-ID: <28156887-c8eb-f142-f6c4-db726680305b@kernel.dk> (raw)
In-Reply-To: <20180109195205.GP3668920@devbig577.frc2.facebook.com>
On 1/9/18 12:52 PM, Tejun Heo wrote:
> Hello, Paolo.
>
> On Thu, Jan 04, 2018 at 08:00:02PM +0100, Paolo Valente wrote:
>> The solution for the second type of parameters may prove useful to
>> unify also the computation of statistics for the throttling policy.
>>
>> Does this proposal sound reasonable?
>
> So, the above should work too but I wonder whether we could do this
> simpler. Frankly, I wouldn't mind if cfq and bfq can't be mixed on a
> system - e.g. they can be built together but you can't enable bfq on
> some devides and cfq on others. If we do that, all we need to do is
> just removing / adding cftypes when either gets activated which cgroup
> already does.
Not sure that would fly, since cfq is legacy and bfq is mq. You don't
always have a free choice of which one to use...
--
Jens Axboe
next prev parent reply other threads:[~2018-01-09 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 19:00 Paolo Valente
2018-01-09 19:52 ` Tejun Heo
2018-01-09 19:53 ` Jens Axboe [this message]
2018-01-09 22:28 ` Paolo Valente
2018-01-10 15:01 ` Tejun Heo
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=28156887-c8eb-f142-f6c4-db726680305b@kernel.dk \
--to=axboe@kernel.dk \
--cc=220530@studenti.unimore.it \
--cc=broonie@kernel.org \
--cc=lennart@poettering.net \
--cc=linus.walleij@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.valente@linaro.org \
--cc=tj@kernel.org \
--cc=ulf.hansson@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 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®