From: David Sterba <dsterba@suse.cz>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Bruno Damasceno Freire <bdamasceno@hotmail.com.br>,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
fdmanana@suse.com
Subject: Re: [regression] 5.15 kernel triggering 100x more inode evictions
Date: Fri, 8 Apr 2022 16:52:22 +0200 [thread overview]
Message-ID: <20220408145222.GR15609@twin.jikos.cz> (raw)
In-Reply-To: <9163b8a9-e852-5786-24fa-d324e3118890@leemhuis.info>
On Fri, Apr 08, 2022 at 12:32:20PM +0200, Thorsten Leemhuis wrote:
> Hi, this is your Linux kernel regression tracker. Top-posting for once,
> to make this easily accessible to everyone.
>
> Btrfs maintainers, what's up here? Yes, this regression report was a bit
> confusing in the beginning, but Bruno worked on it. And apparently it's
> already fixed in 5.16, but still in 5.15. Is this caused by a change
> that is to big to backport or something?
I haven't identified possible fixes in 5.16 so I can't tell how much
backport efforts it could be. As the report is related to performance on
package updates, my best guess is that the patches fixing it are those
from Filipe related to fsync/logging, and there are several of such
improvements in 5.16. Or something else that fixes it indirectly.
next prev parent reply other threads:[~2022-04-08 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MN2PR20MB2512314446801B92562E26B5D2169@MN2PR20MB2512.namprd20.prod.outlook.com>
[not found] ` <07bb78be-1d58-7d88-288b-6516790f3b5d@leemhuis.info>
[not found] ` <MN2PR20MB251203B4B5445B4B0C4148C9D21D9@MN2PR20MB2512.namprd20.prod.outlook.com>
2022-03-28 11:28 ` [regression] 5.15 kernel triggering 100x more inode evictions Thorsten Leemhuis
2022-04-04 5:29 ` Bruno Damasceno Freire
2022-04-08 10:32 ` Thorsten Leemhuis
2022-04-08 14:52 ` David Sterba [this message]
2022-04-08 15:55 ` Filipe Manana
2022-04-08 16:50 ` Thorsten Leemhuis
2022-04-09 17:12 ` Bruno Damasceno Freire
2022-04-10 7:27 ` Thorsten Leemhuis
2022-04-13 0:15 ` Nicholas D Steeves
2022-04-09 17:07 ` Bruno Damasceno Freire
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=20220408145222.GR15609@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=bdamasceno@hotmail.com.br \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--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