From: Jens Axboe <axboe@kernel.dk>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
ulf.hansson@linaro.org, linus.walleij@linaro.org,
broonie@kernel.org, bfq-iosched@googlegroups.com,
oleksandr@natalenko.name
Subject: Re: [PATCH BUGFIX/IMPROVEMENT 0/3] bfq: one fix and two important improvements for throughput
Date: Fri, 14 Sep 2018 13:06:29 -0600 [thread overview]
Message-ID: <bb31b362-53a9-483f-381f-1fcf0dad32bd@kernel.dk> (raw)
In-Reply-To: <20180914142309.6789-1-paolo.valente@linaro.org>
On 9/14/18 8:23 AM, Paolo Valente wrote:
> Hi Jens,
> the second and third patch in this series provide two important
> improvements in bfq's ability to boost throughput with random I/O. The
> benefits of the second patch concern I/O control, and are described in
> detail in this LWN article [1] (and briefly in the commit message
> itself). The benefits of the other patch should be
> straightforward. Finally, the first patch fixes an I/O-control bug,
> found while making the second patch.
>
> These patches modify somehow core operations of bfq, so, before
> submitting them, I have tested them a lot, and have had them tested by
> other people too. In particular, during these months, they have been
> tested in systems ranging from PCs to development platforms.
Applied for 4.20, thanks Paolo.
--
Jens Axboe
prev parent reply other threads:[~2018-09-14 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 14:23 Paolo Valente
2018-09-14 14:23 ` [PATCH BUGFIX/IMPROVEMENT 1/3] block, bfq: correctly charge and reset entity service in all cases Paolo Valente
2018-09-14 14:23 ` [PATCH BUGFIX/IMPROVEMENT 2/3] block, bfq: inject other-queue I/O into seeky idle queues on NCQ flash Paolo Valente
2018-09-14 14:23 ` [PATCH BUGFIX/IMPROVEMENT 3/3] blok, bfq: do not plug I/O if all queues are weight-raised Paolo Valente
2018-09-14 19:06 ` Jens Axboe [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=bb31b362-53a9-483f-381f-1fcf0dad32bd@kernel.dk \
--to=axboe@kernel.dk \
--cc=bfq-iosched@googlegroups.com \
--cc=broonie@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr@natalenko.name \
--cc=paolo.valente@linaro.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®