From: Oleksandr Natalenko <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, linus.walleij@linaro.org,
bfq-iosched@googlegroups.com
Subject: Re: [PATCH 0/4] block, bfq: series of improvements and small fixes of the injection mechanism
Date: Mon, 09 Sep 2019 08:03:47 +0200 [thread overview]
Message-ID: <9088f78edc97279e34f6a96277d088f9@natalenko.name> (raw)
In-Reply-To: <20190822152037.15413-1-paolo.valente@linaro.org>
On 22.08.2019 17:20, Paolo Valente wrote:
> Hi Jens,
> this patch series makes the injection mechanism better at preserving
> control on I/O.
>
> Thanks,
> Paolo
>
> Paolo Valente (4):
> block, bfq: update inject limit only after injection occurred
> block, bfq: reduce upper bound for inject limit to max_rq_in_driver+1
> block, bfq: increase update frequency of inject limit
> block, bfq: push up injection only after setting service time
>
> block/bfq-iosched.c | 35 ++++++++++++++++++++++++++---------
> 1 file changed, 26 insertions(+), 9 deletions(-)
>
> --
> 2.20.1
FWIW, Tested-by: Oleksandr Natalenko <oleksandr@natalenko.name> (I run
it for quite some time already).
--
Oleksandr Natalenko (post-factum)
next prev parent reply other threads:[~2019-09-09 6:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 15:20 [PATCH 0/4] block, bfq: series of improvements and small fixes of the injection mechanism Paolo Valente
2019-08-22 15:20 ` [PATCH 1/4] block, bfq: update inject limit only after injection occurred Paolo Valente
2019-08-22 15:20 ` [PATCH 2/4] block, bfq: reduce upper bound for inject limit to max_rq_in_driver+1 Paolo Valente
2019-08-22 15:20 ` [PATCH 3/4] block, bfq: increase update frequency of inject limit Paolo Valente
2019-08-22 15:20 ` [PATCH 4/4] block, bfq: push up injection only after setting service time Paolo Valente
2019-09-09 5:57 ` [PATCH 0/4] block, bfq: series of improvements and small fixes of the injection mechanism Paolo Valente
2019-09-09 6:03 ` Oleksandr Natalenko [this message]
2019-09-16 15:32 ` Paolo Valente
2019-09-16 16:17 ` Jens Axboe
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=9088f78edc97279e34f6a96277d088f9@natalenko.name \
--to=oleksandr@natalenko.name \
--cc=axboe@kernel.dk \
--cc=bfq-iosched@googlegroups.com \
--cc=linus.walleij@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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