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>,
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 v2 06/14] f2fs: prepare mmap write faults for large folios
Date: Thu, 17 Sep 2026 14:32:59 +0800 [thread overview]
Message-ID: <fe99e57f-20e4-4975-b7ed-f6e16ed331ed@kernel.org> (raw)
In-Reply-To: <20260915041909.2903887-7-zhaonanzhe@xiaomi.com>
On 9/15/26 12:19, Nanzhe Zhao wrote:
> Now write protect `mmap` also need to support large folio,
> Change `f2fs_vm_page_mkwrite` to acheive that.
>
> Note it currently marks the whole large folio dirty
> to avoid data loss which causes write amplification.
> Further optimization is welcome.
>
> PG_mappedtodisk is useless in f2fs, so drop the
> folio_test_mappedtodisk() check and its goto out_sem
> shortcut in f2fs_vm_page_mkwrite(). We extend the
> folio_zero_segment() in mkwrite to zero the post-EOF part
> of the faulted folio for both order-0 and large folios, so
> the f2fs_zero_post_eof_page() call added to cover that
> shortcut is no longer needed.
>
> Signed-off-by: Nanzhe Zhao <zhaonanzhe@xiaomi.com>
> ---
> fs/f2fs/f2fs.h | 4 ++
> fs/f2fs/file.c | 107 ++++++++++++++++++++++++++++++-------------------
> 2 files changed, 70 insertions(+), 41 deletions(-)
>
> diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
> index 8eccca6e5d27..f48e2627d90a 100644
> --- a/fs/f2fs/f2fs.h
> +++ b/fs/f2fs/f2fs.h
> @@ -4393,6 +4393,10 @@ int f2fs_write_single_data_page(struct folio *folio, int *submitted,
> enum iostat_type io_type,
> int compr_blocks, bool allow_balance);
> bool f2fs_ffs_test_blk_uptodate(const struct folio *folio, pgoff_t index);
> +struct f2fs_folio_state *f2fs_ffs_find_or_alloc(struct folio *folio);
> +void f2fs_ffs_mark_subrange_dirty(struct folio *folio, size_t offset, size_t len);
> +bool f2fs_ffs_clear_subrange_dirty_and_test(struct folio *folio, size_t offset,
> + size_t len);
> void f2fs_write_failed(struct inode *inode, loff_t to);
> void f2fs_invalidate_folio(struct folio *folio, size_t offset, size_t length);
> bool f2fs_release_folio(struct folio *folio, gfp_t wait);
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index 9071bd23e57b..738a751c3903 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -118,13 +118,47 @@ static vm_fault_t f2fs_filemap_fault(struct vm_fault *vmf)
> return ret;
> }
>
> +static int f2fs_get_block_mkwrite(struct inode *inode, struct folio *folio,
> + pgoff_t index, bool need_alloc)
> +{
> + struct dnode_of_data dn;
> + int err;
> +
> + set_new_dnode(&dn, inode, NULL, NULL, 0);
> + if (need_alloc) {
> + err = f2fs_get_block_locked(&dn, index);
> + } else {
> + err = f2fs_get_dnode_of_data(&dn, index, LOOKUP_NODE);
> + f2fs_put_dnode(&dn);
> + if (f2fs_is_pinned_file(inode) &&
> + !__is_valid_data_blkaddr(dn.data_blkaddr))
> + err = -EIO;
> + }
> +
> + if (err)
> + return err;
> +
> + f2fs_folio_wait_writeback(folio, DATA, false, true);
> +
> + /* wait for GCed page writeback via META_MAPPING */
> + f2fs_wait_on_block_writeback(inode, dn.data_blkaddr);
> +
> + return 0;
> +}
> +
> static vm_fault_t f2fs_vm_page_mkwrite(struct vm_fault *vmf)
> {
> struct folio *folio = page_folio(vmf->page);
> struct inode *inode = file_inode(vmf->vma->vm_file);
> struct f2fs_sb_info *sbi = F2FS_I_SB(inode);
> - struct dnode_of_data dn;
> bool need_alloc = !f2fs_is_pinned_file(inode);
> + pgoff_t pidx = folio->index + folio_page_idx(folio, vmf->page);
> + loff_t pos = (loff_t)pidx << PAGE_SHIFT;
> + loff_t isize;
> + loff_t folio_start;
> + loff_t valid_end;
> + size_t dirty_len;
> + size_t subpage_off;
pgoff_t i, nr;
> int err = 0;
> vm_fault_t ret;
>
> @@ -161,7 +195,7 @@ static vm_fault_t f2fs_vm_page_mkwrite(struct vm_fault *vmf)
>
> #ifdef CONFIG_F2FS_FS_COMPRESSION
> if (f2fs_compressed_file(inode)) {
> - int ret = f2fs_is_compressed_cluster(inode, folio->index);
> + int ret = f2fs_is_compressed_cluster(inode, pidx);
>
> if (ret < 0) {
> err = ret;
> @@ -179,72 +213,63 @@ static vm_fault_t f2fs_vm_page_mkwrite(struct vm_fault *vmf)
>
> f2fs_bug_on(sbi, f2fs_has_inline_data(inode));
>
> - err = f2fs_zero_post_eof_page(inode,
> - (folio->index + 1) << PAGE_SHIFT, true, false);
> - if (err)
> - goto out_pagefault;
> -
> file_update_time(vmf->vma->vm_file);
> filemap_invalidate_lock_shared(inode->i_mapping);
>
> folio_lock(folio);
> + isize = i_size_read(inode);
> + folio_start = folio_pos(folio);
> + subpage_off = offset_in_folio(folio, pos);
> + valid_end = min_t(loff_t, folio_start + folio_size(folio), isize);
> + dirty_len = valid_end > folio_start ? valid_end - folio_start : 0;
valid_end <= folio_start, is this a possible case? if the folio is post EOF,
can it be dirtied via mmap?
> +
> if (unlikely(folio->mapping != inode->i_mapping ||
> - folio_pos(folio) > i_size_read(inode) ||
> - !folio_test_uptodate(folio))) {
> + pos >= isize ||
> + !f2fs_ffs_test_blk_uptodate(folio,
> + folio->index + (subpage_off >> PAGE_SHIFT)))) {
> folio_unlock(folio);
> err = -EFAULT;
> goto out_sem;
> }
>
> - set_new_dnode(&dn, inode, NULL, NULL, 0);
> - if (need_alloc) {
> - /* block allocation */
> - err = f2fs_get_block_locked(&dn, folio->index);
> - } else {
> - err = f2fs_get_dnode_of_data(&dn, folio->index, LOOKUP_NODE);
> - f2fs_put_dnode(&dn);
> - if (f2fs_is_pinned_file(inode) &&
> - !__is_valid_data_blkaddr(dn.data_blkaddr))
> - err = -EIO;
> - }
> + pgoff_t i, nr = DIV_ROUND_UP(dirty_len, PAGE_SIZE);
>
> - if (err) {
> - folio_unlock(folio);
> - goto out_sem;
> + for (i = 0; i < nr; i++) {
> + err = f2fs_get_block_mkwrite(inode, folio, folio->index + i,
> + need_alloc);
> + if (err) {
> + folio_unlock(folio);
> + goto out_sem;
> + }
> }
>
> - f2fs_folio_wait_writeback(folio, DATA, false, true);
> -
> - /* wait for GCed page writeback via META_MAPPING */
> - f2fs_wait_on_block_writeback(inode, dn.data_blkaddr);
> -
> - /*
> - * check to see if the page is mapped already (no holes)
> - */
> - if (folio_test_mappedtodisk(folio))
> - goto out_sem;
I think we'd better to drop this logic in a separated patch, it doesn't
belong to current patch?
Thanks,
> -
> /* page is wholly or partially inside EOF */
> - if (((loff_t)(folio->index + 1) << PAGE_SHIFT) >
> - i_size_read(inode)) {
> - loff_t offset;
> + if (folio_start + folio_size(folio) > isize) {
> + size_t offset = offset_in_folio(folio, isize);
>
> - offset = i_size_read(inode) & ~PAGE_MASK;
> folio_zero_segment(folio, offset, folio_size(folio));
> }
> +
> + if (folio_test_large(folio)) {
> + if (!f2fs_ffs_find_or_alloc(folio)) {
> + folio_unlock(folio);
> + err = -ENOMEM;
> + goto out_sem;
> + }
> + f2fs_ffs_mark_subrange_dirty(folio, 0, dirty_len);
> + }
> folio_mark_dirty(folio);
>
> - f2fs_update_iostat(sbi, inode, APP_MAPPED_IO, F2FS_BLKSIZE(sbi));
> + f2fs_update_iostat(sbi, inode, APP_MAPPED_IO, dirty_len);
> f2fs_update_time(sbi, REQ_TIME);
>
> out_sem:
> filemap_invalidate_unlock_shared(inode->i_mapping);
> -out_pagefault:
> sb_end_pagefault(inode->i_sb);
> out:
> ret = vmf_fs_error(err);
>
> - trace_f2fs_vm_page_mkwrite(inode, folio->index, vmf->vma->vm_flags, ret);
> + trace_f2fs_vm_page_mkwrite(inode, pidx, vmf->vma->vm_flags, ret);
> return ret;
> }
>
_______________________________________________
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-09-17 6:33 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 4:18 [f2fs-dev] [PATCH v2 00/14] f2fs: support & optimize large folios for writable files Nanzhe Zhao via Linux-f2fs-devel
2026-09-15 4:18 ` [f2fs-dev] [PATCH v2 01/14] f2fs: extend folio state for large folio write path Nanzhe Zhao via Linux-f2fs-devel
2026-09-16 9:53 ` Chao Yu via Linux-f2fs-devel
2026-09-15 4:18 ` [f2fs-dev] [PATCH v2 02/14] f2fs: carry subpage offset and count in write IO Nanzhe Zhao via Linux-f2fs-devel
2026-09-15 4:18 ` [f2fs-dev] [PATCH v2 03/14] f2fs: support regular file buffered writes on large folios Nanzhe Zhao via Linux-f2fs-devel
2026-09-16 11:47 ` Chao Yu via Linux-f2fs-devel
2026-09-29 17:41 ` Daeho Jeong
2026-10-08 5:33 ` Nanzhe Zhao via Linux-f2fs-devel
2026-10-02 17:02 ` Daeho Jeong
2026-10-08 5:46 ` Nanzhe Zhao via Linux-f2fs-devel
2026-09-15 4:18 ` [f2fs-dev] [PATCH v2 04/14] f2fs: support atomic file large folios buffered write Nanzhe Zhao via Linux-f2fs-devel
2026-09-16 12:07 ` Chao Yu via Linux-f2fs-devel
2026-09-23 3:21 ` Nanzhe Zhao via Linux-f2fs-devel
2026-09-23 7:22 ` Chao Yu via Linux-f2fs-devel
2026-09-15 4:19 ` [f2fs-dev] [PATCH v2 05/14] f2fs: support large folio writeback Nanzhe Zhao via Linux-f2fs-devel
2026-09-17 3:48 ` Chao Yu via Linux-f2fs-devel
2026-09-21 2:52 ` Chao Yu via Linux-f2fs-devel
2026-10-02 20:51 ` Daeho Jeong
2026-09-15 4:19 ` [f2fs-dev] [PATCH v2 06/14] f2fs: prepare mmap write faults for large folios Nanzhe Zhao via Linux-f2fs-devel
2026-09-17 6:32 ` Chao Yu via Linux-f2fs-devel [this message]
2026-09-15 4:19 ` [f2fs-dev] [PATCH v2 07/14] f2fs: make GC migration large-folio aware Nanzhe Zhao via Linux-f2fs-devel
2026-09-15 4:19 ` [f2fs-dev] [PATCH v2 08/14] f2fs: optimize small block size large folio read Nanzhe Zhao via Linux-f2fs-devel
2026-09-16 4:33 ` Daeho Jeong
2026-09-23 2:36 ` Nanzhe Zhao via Linux-f2fs-devel
2026-09-24 1:34 ` Nanzhe Zhao via Linux-f2fs-devel
2026-09-17 8:09 ` Chao Yu via Linux-f2fs-devel
2026-09-15 4:19 ` [f2fs-dev] [PATCH v2 09/14] f2fs: support partial uptodate " Nanzhe Zhao via Linux-f2fs-devel
2026-09-15 4:19 ` [f2fs-dev] [PATCH v2 10/14] f2fs: handle partial truncate of large folio dirty subpages Nanzhe Zhao via Linux-f2fs-devel
2026-09-17 8:30 ` Chao Yu via Linux-f2fs-devel
2026-09-23 2:50 ` Nanzhe Zhao via Linux-f2fs-devel
2026-09-23 7:18 ` Chao Yu via Linux-f2fs-devel
2026-09-17 8:32 ` Chao Yu via Linux-f2fs-devel
2026-09-15 4:25 ` [f2fs-dev] [PATCH v2 11/14] f2fs: fix zeroing paths for large folios Nanzhe Zhao via Linux-f2fs-devel
2026-09-15 4:25 ` [f2fs-dev] [PATCH v2 12/14] f2fs: handle block cloning within the same large folio Nanzhe Zhao via Linux-f2fs-devel
2026-09-15 4:25 ` [f2fs-dev] [PATCH v2 13/14] f2fs: allow large folio support to writeable files Nanzhe Zhao via Linux-f2fs-devel
2026-09-17 14:07 ` Chao Yu via Linux-f2fs-devel
2026-09-15 4:25 ` [f2fs-dev] [PATCH v2 14/14] f2fs: make compressed files compatible with large folio Nanzhe Zhao via Linux-f2fs-devel
2026-09-22 3:09 ` Chao Yu via Linux-f2fs-devel
2026-09-30 17:08 ` [f2fs-dev] [PATCH v2 00/14] f2fs: support & optimize large folios for writable files Jaegeuk Kim via Linux-f2fs-devel
2026-10-03 13:40 ` [f2fs-dev] 答复: [External Mail]Re: " 赵南哲 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=fe99e57f-20e4-4975-b7ed-f6e16ed331ed@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=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.