From: Chris Dunlop <chris@onthe.net.au>
To: Leah Rumancik <lrumancik@google.com>, Theodore Ts'o <tytso@mit.edu>
Cc: Dave Chinner <david@fromorbit.com>, linux-xfs@vger.kernel.org
Subject: Subject: v5.15 backport - 5e672cd69f0a xfs: non-blocking inodegc pushes
Date: Wed, 12 Jul 2023 12:17:13 +1000 [thread overview]
Message-ID: <20230712021713.GA902741@onthe.net.au> (raw)
In-Reply-To: <ZK4E/gGuaBu+qvKL@dread.disaster.area>
Request for backport to v5.15:
5e672cd69f0a xfs: non-blocking inodegc pushes
Reference:
https://lore.kernel.org/all/ZK4E%2FgGuaBu+qvKL@dread.disaster.area/
---------------------------------------------------------------------
From: Dave Chinner <david@fromorbit.com>
To: Chris Dunlop <chris@onthe.net.au>
Cc: linux-xfs@vger.kernel.org
Subject: Re: rm hanging, v6.1.35
On Wed, Jul 12, 2023 at 11:13:56AM +1000, Chris Dunlop wrote:
>> On Tue, Jul 11, 2023 at 05:05:30PM +1000, Chris Dunlop wrote:
>>> In particular, could "5e672cd69f0a xfs: non-blocking inodegc pushes"
>>> cause a significantly greater write load on the cache?
...
> Or could / should it be considered for an official backport? Looks like it
> applies cleanly to current v5.15.120.
I thought that had already been done - there's supposed to be
someone taking care of 5.15 LTS backports for XFS....
---------------------------------------------------------------------
Thanks,
Chris
next prev parent reply other threads:[~2023-07-12 2:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 21:53 rm hanging, v6.1.35 Chris Dunlop
2023-07-11 0:13 ` Chris Dunlop
2023-07-11 1:57 ` Chris Dunlop
2023-07-11 3:10 ` Dave Chinner
2023-07-11 7:05 ` Chris Dunlop
2023-07-11 22:21 ` Dave Chinner
2023-07-12 1:13 ` Chris Dunlop
2023-07-12 1:42 ` Dave Chinner
2023-07-12 2:17 ` Chris Dunlop [this message]
2023-07-12 9:26 ` Subject: v5.15 backport - 5e672cd69f0a xfs: non-blocking inodegc pushes Amir Goldstein
2023-07-13 0:31 ` Chris Dunlop
2023-07-13 0:57 ` Chris Dunlop
2023-07-11 0:53 ` rm hanging, v6.1.35 Bagas Sanjaya
2023-07-11 1:13 ` Chris Dunlop
2023-07-11 2:29 ` Dave Chinner
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=20230712021713.GA902741@onthe.net.au \
--to=chris@onthe.net.au \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=lrumancik@google.com \
--cc=tytso@mit.edu \
/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