From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Paolo Valente <paolo.valente@linaro.org>,
Jens Axboe <axboe@kernel.dk>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-block@vger.kernel.org
Subject: Re: Playing with BFQ
Date: Tue, 2 May 2017 14:16:05 +0200 [thread overview]
Message-ID: <20170502121605.GA294@x4> (raw)
In-Reply-To: <CA+icZUXVtBnDZd--nB8xZx0wQAiPAHp9QWhCxo2t62Q0SCui5Q@mail.gmail.com>
On 2017.05.02 at 14:07 +0200, Sedat Dilek wrote:
> On Tue, May 2, 2017 at 10:00 AM, Markus Trippelsdorf
> <markus@trippelsdorf.de> wrote:
> > On 2017.05.02 at 09:54 +0200, Sedat Dilek wrote:
> >> Hi,
> >>
> >> I want to play with BFQ.
> >>
> >> My base is block-next as of 28-Apr-2017.
> [...]
> >> Not sure if the attached patches make sense (right now).
> >
> > No, it doesn't make sense at all.
>
> Hmm, I looked at 4.11.0-v8r11 and 0001 has exactly what my 2 patches do :-).
BFQ started as a conventional scheduler. But because mq is the way of
the future it was ported before it was accepted into mainline.
--
Markus
next prev parent reply other threads:[~2017-05-02 12:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 7:54 Playing with BFQ Sedat Dilek
2017-05-02 8:00 ` Markus Trippelsdorf
2017-05-02 8:07 ` Sedat Dilek
2017-05-02 9:14 ` Sedat Dilek
2017-05-02 12:07 ` Sedat Dilek
2017-05-02 12:16 ` Markus Trippelsdorf [this message]
2017-05-03 8:00 ` Sedat Dilek
2017-05-03 9:16 ` Markus Trippelsdorf
2017-05-03 9:24 ` Paolo Valente
2017-05-13 7:54 ` Sedat Dilek
2017-05-13 8:00 ` Sedat Dilek
2017-05-03 9:21 ` Paolo Valente
2017-05-13 7:50 ` Sedat Dilek
2017-05-16 8:45 ` Paolo Valente
2017-05-16 13:22 ` Sedat Dilek
2017-05-16 13:28 ` Paolo Valente
2017-05-16 13:38 ` Sedat Dilek
2017-05-16 13:41 ` Paolo Valente
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=20170502121605.GA294@x4 \
--to=markus@trippelsdorf.de \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=paolo.valente@linaro.org \
--cc=sedat.dilek@gmail.com \
--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