From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: Nanzhe Zhao <nzzhao.sigma@gmail.com>,
linux-f2fs-devel@lists.sourceforge.net,
Barry Song <baohua@kernel.org>, Juan Yescas <jyescas@google.com>,
Daeho Jeong <daehojeong@google.com>,
Pengfei Li <lipengfei28@xiaomi.com>, Dev Jain <Dev.Jain@arm.com>,
David Hildenbrand <David.Hildenbrand@arm.com>,
linux-kernel@vger.kernel.org, Bo Zhang <zhangbo56@xiaomi.com>,
Kalesh Singh <kaleshsingh@google.com>,
Nanzhe Zhao <nzzhao@126.com>, Nanzhe Zhao <zhaonanzhe@xiaomi.com>,
Ryan Roberts <Ryan.Roberts@arm.com>
Subject: Re: [f2fs-dev] [PATCH v4 00/18] f2fs: support & optimize large folios for writable files
Date: Wed, 14 Oct 2026 01:43:00 +0000 [thread overview]
Message-ID: <as7eJJRyJk61kuf1@google.com> (raw)
In-Reply-To: <0392781c-0ef7-4cd8-b48c-cde83e09abb4@kernel.org>
On 10/14, Chao Yu wrote:
> Hi Jaegeuk,
>
> On 10/14/26 02:46, Jaegeuk Kim wrote:
> > Hi Nanzhe,
> >
> > Could you please rebase your patches on top of dev-test?
>
> Nanzhe rebased the patchset to linux-next, so sashiko can apply & review
> the patchset as expected.
>
> The gap here is two missing cleanup patches from Zi Yan, please apply them
> into dev-test before applying Nanzhe's one, since it's dev-test, it won't
> cause any conflict w/ linux-next.
>
> "f2fs: stop using PG_private"
> "f2fs: reject device aliasing without a multi-device configuration"
>
> See https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/log/?h=feature/large_folio
Per offline sync, they're going to go through MM tree. Please rebase on f2fs tree.
>
> Thanks,
>
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/log/?h=dev-test
> >
> > Note, I applied [0] and [1] already.
> >
> > On 10/13, Nanzhe Zhao wrote:
> >> From: Nanzhe Zhao <zhaonanzhe@xiaomi.com>
> >>
> >> This series supports large folios for most readable/writable files
> >> in buffered I/O paths, including normal files, block-layer encrypted
> >> files, and atomic files except for inline-data files, compressed files,
> >> and quota files.
> >>
> >> It also extends f2fs_folio_state to coexist with f2fs page-private
> >> flags and to handle large folio write path and partial truncate of
> >> large folios correctly.
> >>
> >> Benchmark details can be found in the RFC v2 cover letter [1].
> >>
> >> Changes in v4:
> >> - Rebased onto linux-next next-20261012 (4eb2586bd40d); its f2fs part
> >> is the f2fs dev branch.
> >> - Added "f2fs: read i_size once in f2fs_vm_page_mkwrite" as a
> >> prerequisite (also sent separately).
> >> - "f2fs: remove mappedtodisk flag usage in mmap write path" is kept as
> >> a prerequisite.
> >> - Link to v3: [2]
> >>
> >> Patches 1 and 2 are prerequisites for the large folio work. They are
> >> also posted independently as bug fixes, and are kept in this series to
> >> make it self-contained for the sashiko review.
> >>
> >> Many thanks to Chao and Daeho for your extensive reviews and valuable
> >> suggestions!
> >>
> >> [1] https://lore.kernel.org/r/20260622160830.324455-1-zhaonanzhe@xiaomi.com
> >> [2] https://lore.kernel.org/linux-f2fs-devel/20261009161224.4163796-1-zhaonanzhe@xiaomi.com/
> >>
> >> Nanzhe Zhao (18):
> >> f2fs: read i_size once in f2fs_vm_page_mkwrite
> >> f2fs: remove mappedtodisk flag usage in mmap write path
> >> f2fs: extend folio state for large folio write path
> >> f2fs: carry subpage offset and count in write IO
> >> f2fs: support regular file buffered writes on large folios
> >> f2fs: support atomic file large folios buffered write
> >> f2fs: support large folio writeback
> >> f2fs: account large folio dirty data at block granularity
> >> f2fs: prepare mmap write faults for large folios
> >> f2fs: make GC migration large-folio aware
> >> f2fs: optimize small block size large folio read
> >> f2fs: support partial uptodate large folio read
> >> f2fs: handle partial truncate of large folio dirty subpages
> >> f2fs: wait for folio writeback before ffs_detach_free
> >> f2fs: fix zeroing paths for large folios
> >> f2fs: handle block cloning within the same large folio
> >> f2fs: allow large folio support to writeable files
> >> f2fs: make compressed files compatible with large folio
> >>
> >> Documentation/filesystems/f2fs.rst | 10 +
> >> fs/f2fs/checkpoint.c | 40 +-
> >> fs/f2fs/compress.c | 7 +-
> >> fs/f2fs/data.c | 1425 +++++++++++++++++++++++++---
> >> fs/f2fs/dir.c | 2 +-
> >> fs/f2fs/f2fs.h | 173 +++-
> >> fs/f2fs/file.c | 252 +++--
> >> fs/f2fs/gc.c | 38 +-
> >> fs/f2fs/inline.c | 9 +-
> >> fs/f2fs/inode.c | 4 +-
> >> fs/f2fs/namei.c | 1 +
> >> fs/f2fs/node.c | 2 +-
> >> fs/f2fs/segment.c | 3 +-
> >> 13 files changed, 1706 insertions(+), 260 deletions(-)
> >>
> >> --
> >> 2.43.0
> >>
> >>
> >>
> >> _______________________________________________
> >> 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-10-14 1:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 11:56 Nanzhe Zhao
2026-10-13 11:56 ` [PATCH v4 01/18] f2fs: read i_size once in f2fs_vm_page_mkwrite Nanzhe Zhao
2026-10-13 11:56 ` [PATCH v4 02/18] f2fs: remove mappedtodisk flag usage in mmap write path Nanzhe Zhao
2026-10-13 11:56 ` [PATCH v4 03/18] f2fs: extend folio state for large folio " Nanzhe Zhao
2026-10-13 11:56 ` [PATCH v4 04/18] f2fs: carry subpage offset and count in write IO Nanzhe Zhao
2026-10-13 11:56 ` [PATCH v4 05/18] f2fs: support regular file buffered writes on large folios Nanzhe Zhao
2026-10-13 11:56 ` [PATCH v4 06/18] f2fs: support atomic file large folios buffered write Nanzhe Zhao
2026-10-13 11:56 ` [PATCH v4 07/18] f2fs: support large folio writeback Nanzhe Zhao
2026-10-13 11:56 ` [PATCH v4 08/18] f2fs: account large folio dirty data at block granularity Nanzhe Zhao
2026-10-13 11:56 ` [PATCH v4 09/18] f2fs: prepare mmap write faults for large folios Nanzhe Zhao
2026-10-13 11:56 ` [PATCH v4 10/18] f2fs: make GC migration large-folio aware Nanzhe Zhao
2026-10-13 11:56 ` [PATCH v4 11/18] f2fs: optimize small block size large folio read Nanzhe Zhao
2026-10-13 11:56 ` [PATCH v4 12/18] f2fs: support partial uptodate " Nanzhe Zhao
2026-10-13 11:56 ` [PATCH v4 13/18] f2fs: handle partial truncate of large folio dirty subpages Nanzhe Zhao
2026-10-13 11:56 ` [PATCH v4 14/18] f2fs: wait for folio writeback before ffs_detach_free Nanzhe Zhao
2026-10-13 11:56 ` [PATCH v4 15/18] f2fs: fix zeroing paths for large folios Nanzhe Zhao
2026-10-13 11:56 ` [PATCH v4 16/18] f2fs: handle block cloning within the same large folio Nanzhe Zhao
2026-10-13 11:56 ` [PATCH v4 17/18] f2fs: allow large folio support to writeable files Nanzhe Zhao
2026-10-13 11:56 ` [PATCH v4 18/18] f2fs: make compressed files compatible with large folio Nanzhe Zhao
2026-10-13 18:46 ` [f2fs-dev] [PATCH v4 00/18] f2fs: support & optimize large folios for writable files Jaegeuk Kim
2026-10-14 1:08 ` Chao Yu
2026-10-14 1:43 ` Jaegeuk Kim [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=as7eJJRyJk61kuf1@google.com \
--to=jaegeuk@kernel.org \
--cc=David.Hildenbrand@arm.com \
--cc=Dev.Jain@arm.com \
--cc=Ryan.Roberts@arm.com \
--cc=baohua@kernel.org \
--cc=chao@kernel.org \
--cc=daehojeong@google.com \
--cc=jyescas@google.com \
--cc=kaleshsingh@google.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lipengfei28@xiaomi.com \
--cc=nzzhao.sigma@gmail.com \
--cc=nzzhao@126.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®