regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Paolo Valente <paolo.valente@linaro.org>, Jens Axboe <axboe@kernel.dk>
Cc: Josef Bacik <josef@toxicpanda.com>,
	David Sterba <dsterba@suse.com>, Chris Mason <clm@fb.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Wyatt Childers <kernel.dbwta@haxing.ninja>,
	pmacedo@gmail.com,
	Linux regressions mailing list <regressions@lists.linux.dev>,
	dsterba@suse.cz
Subject: Re: [Regression] Bug 216961 - Severe IO scheduling starvation issues with btrfs
Date: Wed, 1 Mar 2023 08:34:23 +0100	[thread overview]
Message-ID: <d7fe697d-09eb-3a59-6cb3-8eec480d1407@leemhuis.info> (raw)
In-Reply-To: <20230228194039.GP10580@suse.cz>

On 28.02.23 20:40, David Sterba wrote:
> On Fri, Feb 17, 2023 at 06:17:58AM +0100, Linux regression tracking (Thorsten Leemhuis) wrote:
>> On 16.02.23 23:39, Josef Bacik wrote:
>>> On Thu, Feb 16, 2023 at 12:43 PM Thorsten Leemhuis
>>> <regressions@leemhuis.info> wrote:
>>>>
>>>> I might be missing something, but it looks like the report was ignored.
>>>> Is there a reason for that?
>>> Mostly just being blind.
>> Happens.
>>
>>>  I've responded to the BZ, I'll investigate
>>> through the BZ.
> According to the bug it's a problem in BFQ.

Yeah, I noticed yesterday, after I looked into the issue again, as it
looked stalled. But as I already wrote in a comment in the ticket
yesterday:

Did anyone tell the bfq developers about this?

Doesn't look like it. Adding them to the list of recipients them now,
even if they might know about it. If not:

Paolo, Jens, there seems to be a regression in BFQ likely introduced
between 5.19 and 6.0 that people apparently notice often with Btrfs. For
details see:
https://bugzilla.kernel.org/show_bug.cgi?id=216961

Josef apparently has seen report about this as well where switching to
another io scheduler helped:
https://bugzilla.kernel.org/show_bug.cgi?id=216961#c8

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

#regzbot title: bfq: severe IO scheduling starvation issues with btrfs

      reply	other threads:[~2023-03-01  7:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 11:17 [Regression] Bug 216961 - Severe IO scheduling starvation issues with btrfs Linux kernel regression tracking (Thorsten Leemhuis)
2023-02-16 17:43 ` Thorsten Leemhuis
2023-02-16 22:39   ` Josef Bacik
2023-02-17  5:17     ` Linux regression tracking (Thorsten Leemhuis)
2023-02-28 19:40       ` David Sterba
2023-03-01  7:34         ` Linux regression tracking (Thorsten Leemhuis) [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=d7fe697d-09eb-3a59-6cb3-8eec480d1407@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=axboe@kernel.dk \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=josef@toxicpanda.com \
    --cc=kernel.dbwta@haxing.ninja \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paolo.valente@linaro.org \
    --cc=pmacedo@gmail.com \
    --cc=regressions@lists.linux.dev \
    /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).