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, Daeho Jeong <daehojeong@google.com>,
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 v3 11/17] f2fs: support partial uptodate large folio read
Date: Mon, 12 Oct 2026 15:18:52 +0800 [thread overview]
Message-ID: <fdaf1bef-3d10-4d54-a8c3-087804ca57cf@kernel.org> (raw)
In-Reply-To: <20261009162828.4188050-1-zhaonanzhe@xiaomi.com>
On 10/10/26 00:28, Nanzhe Zhao wrote:
> Buffered write can have write bytes smaller than folio
> size for cases when folio minimum order is not zero.
> This can left partially uptodate folio in page cache.
> So we skip uptodate subpage read in read_data_large_folio.
> Also mark hole subpage uptodate in uptodate bitmap.
>
> Signed-off-by: Nanzhe Zhao <zhaonanzhe@xiaomi.com>
> ---
> fs/f2fs/data.c | 70 +++++++++++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 69 insertions(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index 6f6f5223951d..21c43019167a 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -148,6 +148,7 @@ static void f2fs_finish_read_bio(struct bio *bio, bool in_task)
> struct folio *folio = fi.folio;
> unsigned nr_pages = fi.length >> PAGE_SHIFT;
> bool finished = true;
> + bool uptodate = bio->bi_status == BLK_STS_OK;
>
> if (!folio_test_large(folio) &&
> f2fs_is_compressed_page(folio)) {
> @@ -163,6 +164,9 @@ static void f2fs_finish_read_bio(struct bio *bio, bool in_task)
> (struct f2fs_folio_state *)folio->private;
>
> spin_lock_irqsave(&ffs->state_lock, flags);
> + if (bio->bi_status == BLK_STS_OK)
> + uptodate = __ffs_mark_subrange_uptodate(folio, ffs,
> + fi.offset, fi.length);
> ffs->read_pages_pending -= nr_pages;
> finished = !ffs->read_pages_pending;
> spin_unlock_irqrestore(&ffs->state_lock, flags);
> @@ -172,7 +176,8 @@ static void f2fs_finish_read_bio(struct bio *bio, bool in_task)
> dec_cache_count(F2FS_F_SB(folio), F2FS_RD_DATA);
>
> if (finished)
> - folio_end_read(folio, bio->bi_status == BLK_STS_OK);
> + folio_end_read(folio,
> + bio->bi_status == BLK_STS_OK && uptodate);
Looks weird, can we initial uptodate to true directly? and only update it according
to __ffs_mark_subrange_uptodate(), rather than (bio->bi_status == BLK_STS_OK)?
> }
>
> if (ctx)
> @@ -3071,6 +3076,56 @@ static bool find_next_valid_block(const struct folio *folio,
> return false;
> }
>
> +static unsigned int ffs_next_uptodate_subpage(struct f2fs_folio_state *ffs,
> + unsigned int start, unsigned int end)
> +{
> + return find_next_bit(ffs->state, end + 1, start);
> +}
> +
> +static unsigned int ffs_next_nonuptodate_subpage(struct f2fs_folio_state *ffs,
> + unsigned int start, unsigned int end)
> +{
> + return find_next_zero_bit(ffs->state, end + 1, start);
> +}
> +
> +static void f2fs_skip_fully_uptodate_front(struct folio *folio,
> + pgoff_t *index, pgoff_t *offset, unsigned int *nrpages,
> + unsigned int *max_nr_pages)
> +{
> + struct f2fs_folio_state *ffs;
> + unsigned int next, skipped;
> +
> + if (!f2fs_folio_has_ffs(folio) || !*nrpages)
> + return;
> +
> + ffs = (struct f2fs_folio_state *)folio->private;
> + next = ffs_next_nonuptodate_subpage(ffs, *offset,
> + *offset + *nrpages - 1);
> + skipped = next - *offset;
> + if (!skipped)
> + return;
> +
> + *index += skipped;
> + *offset += skipped;
> + *nrpages -= skipped;
> + *max_nr_pages -= skipped;
> +}
> +
> +static void f2fs_truncate_read_extent(struct folio *folio, pgoff_t offset,
> + unsigned int *len_blks)
> +{
> + struct f2fs_folio_state *ffs;
> + unsigned int next, end;
> +
> + if (!f2fs_folio_has_ffs(folio) || *len_blks <= 1)
> + return;
> +
> + ffs = (struct f2fs_folio_state *)folio->private;
> + end = offset + *len_blks - 1;
> + next = ffs_next_uptodate_subpage(ffs, offset + 1, end);
> + if (next <= end)
> + *len_blks = next - offset;
> +}
Blank line.
Thanks,
> static int f2fs_read_data_large_folio(struct inode *inode,
> struct fsverity_info *vi,
> struct readahead_control *rac, struct folio *folio)
> @@ -3115,6 +3170,11 @@ static int f2fs_read_data_large_folio(struct inode *inode,
>
> len_blks = 1;
>
> + f2fs_skip_fully_uptodate_front(folio, &index, &offset,
> + &nrpages, &max_nr_pages);
> + if (!nrpages)
> + break;
> +
> /*
> * Map blocks using the previous result first.
> */
> @@ -3147,6 +3207,7 @@ static int f2fs_read_data_large_folio(struct inode *inode,
> len_blks = min_t(unsigned int, nrpages, max_nr_pages);
> len_blks = min_t(unsigned int, len_blks,
> (unsigned int)(map.m_lblk + map.m_len - index));
> + f2fs_truncate_read_extent(folio, offset, &len_blks);
>
> for (i = 0; i < len_blks; i++) {
> if (!f2fs_is_valid_blkaddr(F2FS_I_SB(inode),
> @@ -3165,6 +3226,13 @@ static int f2fs_read_data_large_folio(struct inode *inode,
> ret = -EIO;
> goto err_out;
> }
> + if (folio_test_large(folio)) {
> + ffs = f2fs_ffs_find_or_alloc(folio);
> + spin_lock_irq(&ffs->state_lock);
> + __ffs_mark_subrange_uptodate(folio, ffs,
> + page_offset, PAGE_SIZE);
> + spin_unlock_irq(&ffs->state_lock);
> + }
> continue;
> }
>
next prev parent reply other threads:[~2026-10-12 7:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 16:12 [PATCH v3 00/17] f2fs: support & optimize large folios for writable files Nanzhe Zhao
2026-10-09 16:12 ` [PATCH v3 01/17] f2fs: extend folio state for large folio write path Nanzhe Zhao
2026-10-09 16:12 ` [PATCH v3 02/17] f2fs: carry subpage offset and count in write IO Nanzhe Zhao
2026-10-09 16:12 ` [PATCH v3 03/17] f2fs: support regular file buffered writes on large folios Nanzhe Zhao
2026-10-09 18:34 ` [f2fs-dev] " Daeho Jeong
2026-10-10 10:02 ` Nanzhe Zhao
2026-10-12 3:01 ` Chao Yu
2026-10-12 13:06 ` [f2fs-dev] " Nanzhe Zhao
2026-10-09 16:12 ` [PATCH v3 04/17] f2fs: support atomic file large folios buffered write Nanzhe Zhao
2026-10-12 3:06 ` Chao Yu
2026-10-09 16:12 ` [PATCH v3 05/17] f2fs: support large folio writeback Nanzhe Zhao
2026-10-12 4:36 ` Chao Yu
2026-10-09 16:12 ` [PATCH v3 06/17] f2fs: account large folio dirty data at block granularity Nanzhe Zhao
2026-10-12 6:54 ` Chao Yu
2026-10-09 16:12 ` [PATCH v3 07/17] f2fs: remove mappedtodisk flag usage in mmap write path Nanzhe Zhao
2026-10-09 16:12 ` [PATCH v3 08/17] f2fs: prepare mmap write faults for large folios Nanzhe Zhao
2026-10-12 7:04 ` Chao Yu
2026-10-09 16:12 ` [PATCH v3 09/17] f2fs: make GC migration large-folio aware Nanzhe Zhao
2026-10-09 16:12 ` [PATCH v3 10/17] f2fs: optimize small block size large folio read Nanzhe Zhao
2026-10-12 7:09 ` Chao Yu
2026-10-09 16:28 ` [PATCH v3 11/17] f2fs: support partial uptodate " Nanzhe Zhao
2026-10-12 7:18 ` Chao Yu [this message]
2026-10-09 16:28 ` [PATCH v3 12/17] f2fs: handle partial truncate of large folio dirty subpages Nanzhe Zhao
2026-10-09 18:14 ` [f2fs-dev] " Daeho Jeong
2026-10-12 7:27 ` Chao Yu
2026-10-09 16:28 ` [PATCH v3 13/17] f2fs: wait for folio writeback before ffs_detach_free Nanzhe Zhao
2026-10-09 16:28 ` [PATCH v3 14/17] f2fs: fix zeroing paths for large folios Nanzhe Zhao
2026-10-09 16:28 ` [PATCH v3 15/17] f2fs: handle block cloning within the same large folio Nanzhe Zhao
2026-10-09 16:28 ` [PATCH v3 16/17] f2fs: allow large folio support to writeable files Nanzhe Zhao
2026-10-09 16:28 ` [PATCH v3 17/17] f2fs: make compressed files compatible with large folio Nanzhe Zhao
2026-10-13 22:30 ` [f2fs-dev] [PATCH v3 00/17] f2fs: support & optimize large folios for writable files patchwork-bot+f2fs
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=fdaf1bef-3d10-4d54-a8c3-087804ca57cf@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@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®