From: Jaegeuk Kim via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Nanzhe Zhao <zhaonanzhe@xiaomi.com>
Cc: baohua@kernel.org, lipengfei28@xiaomi.com, zhangbo56@xiaomi.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [DISCUSSION] f2fs: compatibility between compressed files and large folios
Date: Mon, 3 Aug 2026 23:38:55 +0000 [thread overview]
Message-ID: <anEmjytbni9He124@google.com> (raw)
In-Reply-To: <20260731090714.876795-1-zhaonanzhe@xiaomi.com>
On 07/31, Nanzhe Zhao via Linux-f2fs-devel wrote:
> The quote part of last email to reply is:
>
> > Can we call truncate_inode_pages() after mapping_set_folio_order_range()? something
> > like this:
> >
> > filemap_invalidate_lock
> >
> > mapping_set_folio_order_range(, 0, 0)
>
> Thanks,
>
> Nanzhe
From the previous experience, this won't work, as you mentioned it's not allowed
to change the order on the fly. Should set the order in f2fs_iget() only, but
it'd be better to keep supporting compression. :)
>
>
>
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2026-08-03 23:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 0:28 [f2fs-dev] [DISCUSSION] f2fs: compatibility between compressed files and large folios Nanzhe Zhao via Linux-f2fs-devel
2026-07-30 13:45 ` Chao Yu via Linux-f2fs-devel
2026-07-31 8:52 ` Nanzhe Zhao via Linux-f2fs-devel
2026-07-31 9:07 ` Nanzhe Zhao via Linux-f2fs-devel
2026-08-03 23:38 ` Jaegeuk Kim via Linux-f2fs-devel [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=anEmjytbni9He124@google.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=baohua@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=lipengfei28@xiaomi.com \
--cc=zhangbo56@xiaomi.com \
--cc=zhaonanzhe@xiaomi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.