From: Chao Yu <chao@kernel.org>
To: Nanzhe Zhao <zhaonanzhe@xiaomi.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>, 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: [PATCH v2 04/14] f2fs: support atomic file large folios buffered write
Date: Wed, 16 Sep 2026 20:07:17 +0800 [thread overview]
Message-ID: <51c3f1f9-7e91-4f9a-9f22-d1ba8df357c6@kernel.org> (raw)
In-Reply-To: <20260915041909.2903887-5-zhaonanzhe@xiaomi.com>
On 9/15/26 12:18, Nanzhe Zhao wrote:
> ioctl can convert an inode with large folio support into an atomic
> file. Support large folio buffered writes for atomic files as well.
>
> Add a large folio atomic write_begin helper that reserves COW mappings
> for the write range. For partial head and tail subpages, read the
> existing data from either the COW inode or the original inode before
> marking the subpage uptodate.
>
> Signed-off-by: Nanzhe Zhao <zhaonanzhe@xiaomi.com>
> ---
> fs/f2fs/data.c | 88 ++++++++++++++++++++++++++++++++++++++++++++++----
> 1 file changed, 81 insertions(+), 7 deletions(-)
>
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index a490df4f50b3..eb5fb8e52851 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -4016,18 +4016,16 @@ static int __reserve_data_block(struct inode *inode, pgoff_t index,
> }
>
> static int prepare_atomic_write_begin(struct f2fs_sb_info *sbi,
> - struct folio *folio, loff_t pos, unsigned int len,
> + struct inode *inode, pgoff_t index,
> block_t *blk_addr, bool *node_changed)
> {
> - struct inode *inode = folio->mapping->host;
> struct inode *cow_inode = F2FS_I(inode)->cow_inode;
> - pgoff_t index = folio->index;
> int err = 0;
> block_t ori_blk_addr = NULL_ADDR;
> bool cow_has_reserved_block = false;
>
> /* If pos is beyond the end of file, reserve a new block in COW inode */
^^^
Need to update comments here? there is no @pos in the function.
> - if ((pos & PAGE_MASK) >= i_size_read(inode))
> + if ((index << PAGE_SHIFT) >= i_size_read(inode))
> goto reserve_block;
>
> /* Look for the block in COW inode first */
> @@ -4168,6 +4166,74 @@ static int prepare_large_folio_write_begin(struct inode *inode,
> return 0;
> }
>
> +static int prepare_large_folio_atomic_write_begin(struct inode *inode,
> + struct address_space *mapping, struct folio *folio, loff_t pos,
> + unsigned int len)
> +{
> + struct f2fs_sb_info *sbi = F2FS_I_SB(inode);
> + size_t ori_off = offset_in_folio(folio, pos);
> + pgoff_t start, end, index;
> + unsigned int orig_order;
> + int err = 0;
> +
> + len = min_t(unsigned int, len, folio_size(folio) - ori_off);
> +
> + if (!f2fs_ffs_find_or_alloc(folio))
> + return -ENOMEM;
> +
> + /* Inline data must have been converted before reaching here. */
> + f2fs_bug_on(sbi, f2fs_has_inline_data(inode));
> +
> + start = folio->index + (ori_off >> PAGE_SHIFT);
> + end = folio->index + ((ori_off + len - 1) >> PAGE_SHIFT);
> +
> + for (index = start; index <= end; index++) {
> + block_t blkaddr = NULL_ADDR;
> + bool node_changed = false;
> + size_t off = (index - folio->index) << PAGE_SHIFT;
> +
> + err = prepare_atomic_write_begin(sbi, inode, index,
> + &blkaddr, &node_changed);
> + if (err)
> + return err;
> +
> + if (f2fs_ffs_test_blk_uptodate(folio, index))
> + goto balance;
> +
> + if (blkaddr == NEW_ADDR) {
> + folio_zero_segment(folio, off, off + PAGE_SIZE);
> + f2fs_ffs_mark_subrange_uptodate(folio, off, PAGE_SIZE);
> + goto balance;
> + }
> +
> + if (!f2fs_is_valid_blkaddr(sbi, blkaddr,
> + DATA_GENERIC_ENHANCE_READ))
> + return -EFSCORRUPTED;
> +
> + err = f2fs_submit_page_read_sync(inode, folio, index,
> + blkaddr);
> + if (err)
> + return err;
> +balance:
> + /*
> + * Expand the 4K-page balance decision per subpage: check
> + * right after each preallocated block.
> + */
> + if (node_changed && !IS_NOQUOTA(inode) &&
!IS_NOQUOTA(inode) is not needed.
> + has_not_enough_free_secs(sbi, 0, 0)) {
> + orig_order = folio_order(folio);
> + folio_unlock(folio);
> + f2fs_balance_fs(sbi, true);
> + folio_lock(folio);
> + if (unlikely(folio->mapping != mapping ||
> + folio_order(folio) != orig_order))
> + return -EAGAIN;
> + }
Why can't we merge this logic w/ others? it seems duplicated.
Thanks,
> + }
> +
> + return 0;
> +}
> +
> static int f2fs_write_begin(const struct kiocb *iocb,
> struct address_space *mapping,
> loff_t pos, unsigned len, struct folio **foliop,
> @@ -4245,8 +4311,8 @@ static int f2fs_write_begin(const struct kiocb *iocb,
>
> *foliop = folio;
>
> - if (f2fs_is_atomic_file(inode))
> - err = prepare_atomic_write_begin(sbi, folio, pos, len,
> + if (f2fs_is_atomic_file(inode) && !folio_test_large(folio))
> + err = prepare_atomic_write_begin(sbi, inode, folio->index,
> &blkaddr, &need_balance);
> else if (!folio_test_large(folio))
> err = prepare_write_begin(sbi, folio, pos, len,
> @@ -4270,10 +4336,18 @@ static int f2fs_write_begin(const struct kiocb *iocb,
> f2fs_folio_wait_writeback(folio, DATA, false, true);
>
> if (folio_test_large(folio)) {
> - err = prepare_large_folio_write_begin(inode,
> + if (f2fs_is_atomic_file(inode))
> + err = prepare_large_folio_atomic_write_begin(inode,
> + mapping, folio, pos, len);
> + else
> + err = prepare_large_folio_write_begin(inode,
> folio, pos, len);
> if (!err)
> return 0;
> + if (err == -EAGAIN) {
> + f2fs_folio_put(folio, true);
> + goto repeat;
> + }
> goto put_folio;
> }
>
next prev parent reply other threads:[~2026-09-16 12:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 4:18 [PATCH v2 00/14] f2fs: support & optimize large folios for writable files Nanzhe Zhao
2026-09-15 4:18 ` [PATCH v2 01/14] f2fs: extend folio state for large folio write path Nanzhe Zhao
2026-09-16 9:53 ` Chao Yu
2026-09-15 4:18 ` [PATCH v2 02/14] f2fs: carry subpage offset and count in write IO Nanzhe Zhao
2026-09-15 4:18 ` [PATCH v2 03/14] f2fs: support regular file buffered writes on large folios Nanzhe Zhao
2026-09-16 11:47 ` Chao Yu
2026-09-15 4:18 ` [PATCH v2 04/14] f2fs: support atomic file large folios buffered write Nanzhe Zhao
2026-09-16 12:07 ` Chao Yu [this message]
2026-09-15 4:19 ` [PATCH v2 05/14] f2fs: support large folio writeback Nanzhe Zhao
2026-09-17 3:48 ` Chao Yu
2026-09-15 4:19 ` [PATCH v2 06/14] f2fs: prepare mmap write faults for large folios Nanzhe Zhao
2026-09-17 6:32 ` Chao Yu
2026-09-15 4:19 ` [PATCH v2 07/14] f2fs: make GC migration large-folio aware Nanzhe Zhao
2026-09-15 4:19 ` [PATCH v2 08/14] f2fs: optimize small block size large folio read Nanzhe Zhao
2026-09-16 4:33 ` [f2fs-dev] " Daeho Jeong
2026-09-15 4:19 ` [PATCH v2 09/14] f2fs: support partial uptodate " Nanzhe Zhao
2026-09-15 4:19 ` [PATCH v2 10/14] f2fs: handle partial truncate of large folio dirty subpages Nanzhe Zhao
2026-09-15 4:25 ` [PATCH v2 11/14] f2fs: fix zeroing paths for large folios Nanzhe Zhao
2026-09-15 4:25 ` [PATCH v2 12/14] f2fs: handle block cloning within the same large folio Nanzhe Zhao
2026-09-15 4:25 ` [PATCH v2 13/14] f2fs: allow large folio support to writeable files Nanzhe Zhao
2026-09-15 4:25 ` [PATCH v2 14/14] f2fs: make compressed files compatible with large folio Nanzhe Zhao
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=51c3f1f9-7e91-4f9a-9f22-d1ba8df357c6@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=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@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®