From: oleksandr@natalenko.name
To: Paolo Valente <paolo.valente@linaro.org>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
ulf.hansson@linaro.org, broonie@kernel.org,
mgorman@techsingularity.net, lee.tibbert@gmail.com
Subject: Re: [PATCH BUGFIX/IMPROVEMENT 0/3] three bfq fixes restoring service guarantees with random sync writes in bg
Date: Thu, 31 Aug 2017 08:41:18 +0200 [thread overview]
Message-ID: <8b2ad38d79334a156f18904cc2dd3509@natalenko.name> (raw)
In-Reply-To: <20170831061020.4426-1-paolo.valente@linaro.org>
> Tested-by: Oleksander Natalenko <oleksandr@natalenko.name>
I'm "Oleksandr" :).
31.08.2017 08:10, Paolo Valente wrote:
> Hi,
> while testing the read-write unfairness issues reported by Mel, I
> found BFQ failing to guarantee good responsiveness against heavy
> random sync writes in the background, i.e., multiple writers doing
> random writes and systematic fdatasync [1]. The failure was caused by
> three related bugs, because of which BFQ failed to guarantee to
> high-weight processes the expected fraction of the throughput.
>
> The three patches in this series fix these bugs. These fixes restore
> the usual BFQ service guarantees (and thus optimal responsiveness
> too), against the above background workload and, probably, against
> other similar workloads.
>
> Thanks,
> Paolo
>
> [1] https://lkml.org/lkml/2017/8/9/957
>
> Paolo Valente (3):
> block, bfq: make lookup_next_entity push up vtime on expirations
> block, bfq: remove direct switch to an entity in higher class
> block, bfq: guarantee update_next_in_service always returns an
> eligible entity
>
> block/bfq-iosched.c | 4 +--
> block/bfq-iosched.h | 4 +--
> block/bfq-wf2q.c | 91
> ++++++++++++++++++++++++++++++++---------------------
> 3 files changed, 60 insertions(+), 39 deletions(-)
>
> --
> 2.10.0
next prev parent reply other threads:[~2017-08-31 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 6:10 Paolo Valente
2017-08-31 6:10 ` [PATCH BUGFIX/IMPROVEMENT 1/3] block, bfq: make lookup_next_entity push up vtime on expirations Paolo Valente
2017-08-31 6:10 ` [PATCH BUGFIX/IMPROVEMENT 2/3] block, bfq: remove direct switch to an entity in higher class Paolo Valente
2017-08-31 6:10 ` [PATCH BUGFIX/IMPROVEMENT 3/3] block, bfq: guarantee update_next_in_service always returns an eligible entity Paolo Valente
2017-08-31 6:41 ` oleksandr [this message]
2017-08-31 6:45 ` [PATCH BUGFIX/IMPROVEMENT 0/3] three bfq fixes restoring service guarantees with random sync writes in bg 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=8b2ad38d79334a156f18904cc2dd3509@natalenko.name \
--to=oleksandr@natalenko.name \
--cc=axboe@kernel.dk \
--cc=broonie@kernel.org \
--cc=lee.tibbert@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--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®