From: Chao Yu <chao@kernel.org>
To: Nanzhe Zhao <nzzhao.sigma@gmail.com>,
linux-f2fs-devel@lists.sourceforge.net,
Jaegeuk Kim <jaegeuk@kernel.org>
Cc: chao@kernel.org, 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: [PATCH v8 01/15] f2fs: extend folio state for large folio write path
Date: Thu, 29 Oct 2026 09:30:54 +0800 [thread overview]
Message-ID: <50b8a3e7-a779-46b9-9238-b1e345d03841@kernel.org> (raw)
In-Reply-To: <20261028154407.1601430-2-nzzhao.sigma@gmail.com>
On 10/28/26 23:43, Nanzhe Zhao wrote:
> From: Nanzhe Zhao <zhaonanzhe@xiaomi.com>
>
> Large folio write path needs a subpage status bitmap and write
> pages pending counter, while keeping compatible with f2fs private
> flags.
>
> Move struct f2fs_folio_state to f2fs.h, add private_flags and
> subpage state bitmap, and change PAGE_PRIVATE functions to be
> compatible with f2fs_folio_state. Allocate f2fs_folio_state via kzalloc
> instead of kmem_cache, since the state size depends on the folio order.
>
> Note: Now if a path wants to use f2fs_folio_state, it must call
> `folio_has_ffs` instead of `folio_test_large`` to make check.
>
> Signed-off-by: Nanzhe Zhao <zhaonanzhe@xiaomi.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2026-10-29 1:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 15:43 [PATCH v8 00/15] f2fs: support & optimize large folios for writable files Nanzhe Zhao
2026-10-28 15:43 ` [PATCH v8 01/15] f2fs: extend folio state for large folio write path Nanzhe Zhao
2026-10-29 1:30 ` Chao Yu [this message]
2026-10-28 15:43 ` [PATCH v8 02/15] f2fs: carry subpage offset and count in write IO Nanzhe Zhao
2026-10-29 1:31 ` Chao Yu
2026-10-28 15:43 ` [PATCH v8 03/15] f2fs: support regular file buffered writes on large folios Nanzhe Zhao
2026-10-29 1:31 ` Chao Yu
2026-10-28 15:43 ` [PATCH v8 04/15] f2fs: support atomic file large folios buffered write Nanzhe Zhao
2026-10-29 1:31 ` Chao Yu
2026-10-28 15:43 ` [PATCH v8 05/15] f2fs: support large folio writeback Nanzhe Zhao
2026-10-29 1:32 ` Chao Yu
2026-10-28 15:43 ` [PATCH v8 06/15] f2fs: account large folio dirty data at block granularity Nanzhe Zhao
2026-10-29 1:32 ` Chao Yu
2026-10-28 15:43 ` [PATCH v8 07/15] f2fs: prepare mmap write faults for large folios Nanzhe Zhao
2026-10-29 1:32 ` Chao Yu
2026-10-28 15:43 ` [PATCH v8 08/15] f2fs: make GC migration large-folio aware Nanzhe Zhao
2026-10-29 1:32 ` Chao Yu
2026-10-28 15:44 ` [PATCH v8 09/15] f2fs: optimize small block size large folio read Nanzhe Zhao
2026-10-29 1:33 ` Chao Yu
2026-10-28 15:44 ` [PATCH v8 10/15] f2fs: support partial uptodate " Nanzhe Zhao
2026-10-29 1:33 ` Chao Yu
2026-10-28 15:44 ` [PATCH v8 11/15] f2fs: handle partial truncate of large folio dirty subpages Nanzhe Zhao
2026-10-29 1:34 ` Chao Yu
2026-10-28 15:44 ` [PATCH v8 12/15] f2fs: fix zeroing paths for large folios Nanzhe Zhao
2026-10-29 1:34 ` Chao Yu
2026-10-28 15:44 ` [PATCH v8 13/15] f2fs: handle block cloning within the same large folio Nanzhe Zhao
2026-10-29 1:35 ` Chao Yu
2026-10-28 15:44 ` [PATCH v8 14/15] f2fs: allow large folio support to writeable files Nanzhe Zhao
2026-10-29 1:36 ` Chao Yu
2026-10-28 15:44 ` [PATCH v8 15/15] f2fs: make compressed files compatible with large folio Nanzhe Zhao
2026-10-29 1:36 ` Chao Yu
2026-10-28 17:34 ` [f2fs-dev] [PATCH v8 00/15] f2fs: support & optimize large folios for writable files Jaegeuk Kim
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=50b8a3e7-a779-46b9-9238-b1e345d03841@kernel.org \
--to=chao@kernel.org \
--cc=David.Hildenbrand@arm.com \
--cc=Dev.Jain@arm.com \
--cc=Ryan.Roberts@arm.com \
--cc=baohua@kernel.org \
--cc=daehojeong@google.com \
--cc=jaegeuk@kernel.org \
--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®