From: Paolo Valente <paolo.valente@linaro.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block <linux-block@vger.kernel.org>,
linux-kernel@vger.kernel.org, ulf.hansson@linaro.org,
linus.walleij@linaro.org, bfq-iosched@googlegroups.com,
oleksandr@natalenko.name
Subject: Re: [PATCH BUGFIX IMPROVEMENT V2 0/1] block, bfq: eliminate latency regression with fast drives
Date: Thu, 18 Jul 2019 09:06:41 +0200 [thread overview]
Message-ID: <12B115BF-AF31-44F8-9A3A-EC64D3284FBB@linaro.org> (raw)
In-Reply-To: <6867cf11-d7f8-cadf-b9ec-85549bb86af3@kernel.dk>
> Il giorno 16 lug 2019, alle ore 16:11, Jens Axboe <axboe@kernel.dk> ha scritto:
>
> On 7/15/19 4:57 AM, Paolo Valente wrote:
>> [V2 that should apply cleanly on current HEAD]
>>
>> Hi Jens,
>> I've spotted a regression on a fast SSD: a loss of I/O-latency control
>> with interactive tasks (such as the application start up I usually
>> test). Details in the commit.
>>
>> I do hope that, after proper review, this commit makes it for 5.3.
>
> If it's a regression, it should have a Fixes: line telling us which
> commit originally introduced the regression. This is important for
> folks doing backports.
Right, sorry.
> Can you add that?
>
Added, together with an explanation of why the fixed commit fails.
Sending a V3.
Thanks,
Paolo
> --
> Jens Axboe
>
prev parent reply other threads:[~2019-07-18 7:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 10:57 [PATCH BUGFIX IMPROVEMENT V2 0/1] block, bfq: eliminate latency regression with fast drives Paolo Valente
2019-07-15 10:57 ` [PATCH BUGFIX IMPROVEMENT V2 1/1] block, bfq: check also in-flight I/O in dispatch plugging Paolo Valente
2019-07-16 14:11 ` [PATCH BUGFIX IMPROVEMENT V2 0/1] block, bfq: eliminate latency regression with fast drives Jens Axboe
2019-07-18 7:06 ` Paolo Valente [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=12B115BF-AF31-44F8-9A3A-EC64D3284FBB@linaro.org \
--to=paolo.valente@linaro.org \
--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=oleksandr@natalenko.name \
--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;
as well as URLs for NNTP newsgroup(s).