From: Jens Axboe <axboe@kernel.dk>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: linux-block <linux-block@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Mark Brown <broonie@kernel.org>,
'Paolo Valente' via bfq-iosched <bfq-iosched@googlegroups.com>,
oleksandr@natalenko.name, hurikhan77+bko@gmail.com
Subject: Re: [PATCH BUGFIX RFC 0/2] reverting two commits causing freezes
Date: Fri, 18 Jan 2019 10:36:07 -0700 [thread overview]
Message-ID: <c71255da-c142-8ea1-2dc4-840a6581689b@kernel.dk> (raw)
In-Reply-To: <D212BCED-49BD-47F0-AF7F-0CCDBC82D131@linaro.org>
On 1/18/19 10:24 AM, Paolo Valente wrote:
>
>
>> Il giorno 18 gen 2019, alle ore 14:35, Jens Axboe <axboe@kernel.dk> ha scritto:
>>
>> On 1/18/19 4:52 AM, Paolo Valente wrote:
>>> Hi Jens,
>>> a user reported a warning, followed by freezes, in case he increases
>>> nr_requests to more than 64 [1]. After reproducing the issues, I
>>> reverted the commit f0635b8a416e ("bfq: calculate shallow depths at
>>> init time"), plus the related commit bd7d4ef6a4c9 ("bfq-iosched:
>>> remove unused variable"). The problem went away.
>>
>> For reverts, please put the justification into the actual revert
>> commit. With this series, if applied as-is, we'd have two patches
>> in the tree that just says "revert X" without any hint as to why
>> that was done.
>>
>
> I forget to say explicitly that these patches were meant only to give
> you and anybody else something concrete to test and check.
>
> With me you're as safe as houses, in terms of amount of comments in
> final patches :)
It's almost an example of the classic case of "if you want a real
solution to a problem, post a knowingly bad and half assed solution".
That always gets people out of the woodwork :-)
>>> Maybe the assumption in commit f0635b8a416e ("bfq: calculate shallow
>>> depths at init time") does not hold true?
>>
>> It apparently doesn't! But let's try and figure this out instead of
>> blindly reverting it.
>
> Totally agree.
>
>> OK, I think I see it. For the sched_tags
>> case, when we grow the requests, we allocate a new set. Hence any
>> old cache would be stale at that point.
>>
>
> ok
>
>> How about something like this? It still keeps the code of having
>> to update this out of the hot IO path, and only calls it when we
>> actually change the depths.
>>
>
> Looks rather clean and efficient.
>
>> Totally untested...
>>
>
> It seems to work here too.
OK good, I've posted it "officially" now.
--
Jens Axboe
prev parent reply other threads:[~2019-01-18 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 11:52 [PATCH BUGFIX RFC 0/2] reverting two commits causing freezes Paolo Valente
2019-01-18 11:52 ` [PATCH BUGFIX RFC 1/2] Revert "bfq-iosched: remove unused variable" Paolo Valente
2019-01-18 11:52 ` [PATCH BUGFIX RFC 2/2] Revert "bfq: calculate shallow depths at init time" Paolo Valente
2019-01-18 13:35 ` [PATCH BUGFIX RFC 0/2] reverting two commits causing freezes Jens Axboe
2019-01-18 16:29 ` Jens Axboe
2019-01-18 17:24 ` Paolo Valente
2019-01-18 17:36 ` 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=c71255da-c142-8ea1-2dc4-840a6581689b@kernel.dk \
--to=axboe@kernel.dk \
--cc=bfq-iosched@googlegroups.com \
--cc=broonie@kernel.org \
--cc=hurikhan77+bko@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).