From: John Garry <john.g.garry@oracle.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Carlos Maiolino <cem@kernel.org>, xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: compute the maximum repair reaping defer intent chain length
Date: Fri, 4 Apr 2025 17:36:54 +0100 [thread overview]
Message-ID: <011efc18-0024-402f-b79b-a8ea366fdadf@oracle.com> (raw)
In-Reply-To: <20250404160930.GC6283@frogsfrogsfrogs>
On 04/04/2025 17:09, Darrick J. Wong wrote:
>> and xfs_cui_item_overhead() - are not referenced in this patch, but only in
> The refcount intent items aren't needed for online fsck because xreap_*
> doesn't mess with file data. They're provided entirely for the sake of
> cow fallback of multi-fsblock untorn writes. IOWs, it's to reduce churn
> between our patchsets (really, this patch and your patchset) assuming
> that part of untorn writes actually goes into 6.16.
Can you please advise on how you would like to proceed this patch and my
dependent work?
Thanks,
John
next prev parent reply other threads:[~2025-04-04 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 19:12 [PATCH] xfs: compute the maximum repair reaping defer intent chain length Darrick J. Wong
2025-04-04 9:16 ` John Garry
2025-04-04 16:09 ` Darrick J. Wong
2025-04-04 16:36 ` John Garry [this message]
2025-04-06 17:22 ` Darrick J. Wong
2025-04-08 22:14 ` Dave Chinner
2025-04-08 23:13 ` Darrick J. Wong
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=011efc18-0024-402f-b79b-a8ea366fdadf@oracle.com \
--to=john.g.garry@oracle.com \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.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