From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Nanzhe Zhao <zhaonanzhe@xiaomi.com>,
linux-f2fs-devel@lists.sourceforge.net,
Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Barry Song <baohua@kernel.org>, Juan Yescas <jyescas@google.com>,
Daeho Jeong <daehojeong@google.com>, Dev Jain <Dev.Jain@arm.com>,
linux-kernel@vger.kernel.org,
David Hildenbrand <David.Hildenbrand@arm.com>,
Bo Zhang <zhangbo56@xiaomi.com>,
Kalesh Singh <kaleshsingh@google.com>,
Nanzhe Zhao <nzzhao@126.com>, Pengfei Li <lipengfei28@xiaomi.com>,
Ryan Roberts <Ryan.Roberts@arm.com>
Subject: Re: [f2fs-dev] [PATCH v3 03/17] f2fs: support regular file buffered writes on large folios
Date: Mon, 12 Oct 2026 11:01:06 +0800 [thread overview]
Message-ID: <efb9eda2-371b-437c-8652-ed25c842f11a@kernel.org> (raw)
In-Reply-To: <20261009161224.4163796-4-zhaonanzhe@xiaomi.com>
On 10/10/26 00:12, Nanzhe Zhao wrote:
> +/*
> + * Drop the folio lock when a node was changed, then balance the
> + * filesystem and reacquire the lock.
> + *
> + * Return: true if the folio became unusable while unlocked (being
> + * truncated), false if the folio is still usable.
> + */
> +static bool f2fs_folio_may_unlock_balance_fs(struct folio *folio,
f2fs_balance_fs_folio_locked() ?
> @@ -4198,11 +4501,15 @@ static int f2fs_write_begin(const struct kiocb *iocb,
>
> *foliop = folio;
>
> + /* Clamp the write length to the folio size. */
> + blen = min_t(unsigned int, len,
> + folio_size(folio) - offset_in_folio(folio, pos));
> +
> if (f2fs_is_atomic_file(inode))
> err = prepare_atomic_write_begin(sbi, folio, pos, len,
> &blkaddr, &need_balance);
> - else
> - err = prepare_write_begin(sbi, folio, pos, len,
> + else if (!folio_test_large(folio))
> + err = prepare_write_begin(sbi, folio, pos, blen,
> &blkaddr, &need_balance);
> if (err)
> goto put_folio;
> @@ -4222,7 +4529,19 @@ static int f2fs_write_begin(const struct kiocb *iocb,
>
> f2fs_folio_wait_writeback(folio, false, true);
>
> - if (len == folio_size(folio) || folio_test_uptodate(folio))
> + if (folio_test_large(folio)) {
> + err = prepare_large_folio_write_begin(inode,
> + folio, pos, blen);
Is it possible that we can relocate prepare_large_folio_write_begin() after
else if (!folio_test_large(folio))
err = prepare_write_begin(sbi, folio, pos, blen,
&blkaddr, &need_balance);
else
err = prepare_large_folio_write_begin(...);
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2026-10-12 3:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 16:12 [f2fs-dev] [PATCH v3 00/17] f2fs: support & optimize large folios for writable files Nanzhe Zhao via Linux-f2fs-devel
2026-10-09 16:12 ` [f2fs-dev] [PATCH v3 01/17] f2fs: extend folio state for large folio write path Nanzhe Zhao via Linux-f2fs-devel
2026-10-09 16:12 ` [f2fs-dev] [PATCH v3 02/17] f2fs: carry subpage offset and count in write IO Nanzhe Zhao via Linux-f2fs-devel
2026-10-09 16:12 ` [f2fs-dev] [PATCH v3 03/17] f2fs: support regular file buffered writes on large folios Nanzhe Zhao via Linux-f2fs-devel
2026-10-09 18:34 ` Daeho Jeong
2026-10-10 10:02 ` Nanzhe Zhao via Linux-f2fs-devel
2026-10-12 3:01 ` Chao Yu via Linux-f2fs-devel [this message]
2026-10-12 13:06 ` Nanzhe Zhao via Linux-f2fs-devel
2026-10-09 16:12 ` [f2fs-dev] [PATCH v3 04/17] f2fs: support atomic file large folios buffered write Nanzhe Zhao via Linux-f2fs-devel
2026-10-12 3:06 ` Chao Yu via Linux-f2fs-devel
2026-10-09 16:12 ` [f2fs-dev] [PATCH v3 05/17] f2fs: support large folio writeback Nanzhe Zhao via Linux-f2fs-devel
2026-10-12 4:36 ` Chao Yu via Linux-f2fs-devel
2026-10-09 16:12 ` [f2fs-dev] [PATCH v3 06/17] f2fs: account large folio dirty data at block granularity Nanzhe Zhao via Linux-f2fs-devel
2026-10-12 6:54 ` Chao Yu via Linux-f2fs-devel
2026-10-09 16:12 ` [f2fs-dev] [PATCH v3 07/17] f2fs: remove mappedtodisk flag usage in mmap write path Nanzhe Zhao via Linux-f2fs-devel
2026-10-09 16:12 ` [f2fs-dev] [PATCH v3 08/17] f2fs: prepare mmap write faults for large folios Nanzhe Zhao via Linux-f2fs-devel
2026-10-12 7:04 ` Chao Yu via Linux-f2fs-devel
2026-10-09 16:12 ` [f2fs-dev] [PATCH v3 09/17] f2fs: make GC migration large-folio aware Nanzhe Zhao via Linux-f2fs-devel
2026-10-09 16:12 ` [f2fs-dev] [PATCH v3 10/17] f2fs: optimize small block size large folio read Nanzhe Zhao via Linux-f2fs-devel
2026-10-12 7:09 ` Chao Yu via Linux-f2fs-devel
2026-10-09 16:28 ` [f2fs-dev] [PATCH v3 11/17] f2fs: support partial uptodate " Nanzhe Zhao via Linux-f2fs-devel
2026-10-12 7:18 ` Chao Yu via Linux-f2fs-devel
2026-10-09 16:28 ` [f2fs-dev] [PATCH v3 12/17] f2fs: handle partial truncate of large folio dirty subpages Nanzhe Zhao via Linux-f2fs-devel
2026-10-09 18:14 ` Daeho Jeong
2026-10-12 7:27 ` Chao Yu via Linux-f2fs-devel
2026-10-13 12:01 ` Nanzhe Zhao via Linux-f2fs-devel
2026-10-09 16:28 ` [f2fs-dev] [PATCH v3 13/17] f2fs: wait for folio writeback before ffs_detach_free Nanzhe Zhao via Linux-f2fs-devel
2026-10-09 16:28 ` [f2fs-dev] [PATCH v3 14/17] f2fs: fix zeroing paths for large folios Nanzhe Zhao via Linux-f2fs-devel
2026-10-09 16:28 ` [f2fs-dev] [PATCH v3 15/17] f2fs: handle block cloning within the same large folio Nanzhe Zhao via Linux-f2fs-devel
2026-10-09 16:28 ` [f2fs-dev] [PATCH v3 16/17] f2fs: allow large folio support to writeable files Nanzhe Zhao via Linux-f2fs-devel
2026-10-09 16:28 ` [f2fs-dev] [PATCH v3 17/17] f2fs: make compressed files compatible with large folio Nanzhe Zhao via Linux-f2fs-devel
2026-10-13 22:30 ` [f2fs-dev] [PATCH v3 00/17] f2fs: support & optimize large folios for writable files patchwork-bot+f2fs--- via Linux-f2fs-devel
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=efb9eda2-371b-437c-8652-ed25c842f11a@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--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=jaegeuk@kernel.org \
--cc=jyescas@google.com \
--cc=kaleshsingh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lipengfei28@xiaomi.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 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.