From: Christoph Hellwig <hch@infradead.org>
To: Chao Yu <chao@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Zorro Lang <zlang@kernel.org>,
Jan Prusakowski <jprusakowski@google.com>,
linux-f2fs-devel@lists.sourceforge.net, fstests@vger.kernel.org,
jaegeuk@kernel.org
Subject: Re: [f2fs-dev] [PATCH] generic/064: allow 50 extents on F2FS after fcollapse
Date: Wed, 22 Jul 2026 01:59:41 -0700 [thread overview]
Message-ID: <amCGfUHu6kI4CPND@infradead.org> (raw)
In-Reply-To: <1a0bb2ad-c175-4cae-9e3f-79fbf69ce735@kernel.org>
On Wed, Jul 22, 2026 at 09:12:48AM +0800, Chao Yu wrote:
> Hi Christoph,
>
> On 7/20/26 16:04, Christoph Hellwig wrote:
> > So looking at this explanation and the code, f2fs does not actually
> > support COLLAPSE_RANGE at all, but emulates by doing a full data
>
> For non-checkpoint data, we can just update metadata w/o any data copying
> to support COLLAPSE_RANGE.
Can you clarify what "non-checkpoint data" data means? Older data?
next prev parent reply other threads:[~2026-07-22 8:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 7:04 [PATCH] generic/064: allow 50 extents on F2FS after fcollapse Jan Prusakowski
2026-06-23 8:46 ` [f2fs-dev] " Chao Yu
2026-06-24 7:46 ` Christoph Hellwig
2026-06-29 16:37 ` Zorro Lang
2026-06-30 12:09 ` [f2fs-dev] " Chao Yu
2026-07-19 9:24 ` Zorro Lang
2026-07-22 1:22 ` Chao Yu
2026-07-20 8:04 ` Christoph Hellwig
2026-07-22 1:12 ` Chao Yu
2026-07-22 8:59 ` Christoph Hellwig [this message]
2026-07-22 12:32 ` Chao Yu
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=amCGfUHu6kI4CPND@infradead.org \
--to=hch@infradead.org \
--cc=chao@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=jprusakowski@google.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=zlang@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