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 08/14] f2fs: optimize small block size large folio read
Date: Mon, 31 Aug 2026 12:21:11 +0800 [thread overview]
Message-ID: <fe3ef362-3d4e-41cc-8237-05261c873bab@kernel.org> (raw)
In-Reply-To: <20260826082641.2007658-9-zhaonanzhe@xiaomi.com>
On 8/26/26 16:26, Nanzhe Zhao wrote:
> The original f2fs_read_data_large_folio() implementation has limited
> benefit with a 4KB block size, mainly because updating
> read_pages_pending greatly increases the number of spinlock
> operations.
>
> Use len_blks to batch read_pages_pending and iostat updates for
> contiguous mapped blocks. If the contiguous mapping covers the whole
> folio, skip f2fs_folio_state allocation for that folio.
>
> Signed-off-by: Nanzhe Zhao <zhaonanzhe@xiaomi.com>
> ---
> fs/f2fs/data.c | 62 ++++++++++++++++++++++++++++++++++++++------------
> 1 file changed, 47 insertions(+), 15 deletions(-)
>
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index 0e54b1e25893..48c1bb6c02e3 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -153,6 +153,7 @@ static void f2fs_finish_read_bio(struct bio *bio, bool in_task)
> struct folio *folio = fi.folio;
> unsigned int 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,10 +164,14 @@ static void f2fs_finish_read_bio(struct bio *bio, bool in_task)
> continue;
> }
>
> - if (folio_test_large(folio)) {
> - struct f2fs_folio_state *ffs = folio->private;
> + if (f2fs_folio_has_ffs(folio)) {
> + struct f2fs_folio_state *ffs =
> + (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);
> @@ -182,7 +187,7 @@ static void f2fs_finish_read_bio(struct bio *bio, bool in_task)
> bio->bi_status = BLK_STS_IOERR;
>
> if (finished)
> - folio_end_read(folio, bio->bi_status == BLK_STS_OK);
folio_end_read(folio, bio->bi_status == BLK_STS_OK && uptodate);
in case f2fs_sanity_check_node_footer() failed.
Thanks,
> + folio_end_read(folio, uptodate);
> }
>
> if (ctx)
> @@ -2887,8 +2892,15 @@ static int f2fs_read_data_large_folio(struct inode *inode,
> ffs = NULL;
> nrpages = folio_nr_pages(folio);
>
> - for (; nrpages; nrpages--, max_nr_pages--, index++, offset++) {
> + for (; nrpages;
> + nrpages -= len_blks, max_nr_pages -= len_blks,
> + index += len_blks, offset += len_blks) {
> sector_t block_nr;
> + bool whole_folio_in_bio;
> + unsigned int i;
> +
> + len_blks = 1;
> +
> /*
> * Map blocks using the previous result first.
> */
> @@ -2917,13 +2929,31 @@ static int f2fs_read_data_large_folio(struct inode *inode,
> got_it:
> if ((map.m_flags & F2FS_MAP_MAPPED)) {
> block_nr = map.m_pblk + index - map.m_lblk;
> - if (!f2fs_is_valid_blkaddr(F2FS_I_SB(inode), block_nr,
> +
> + 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));
> +
> + for (i = 0; i < len_blks; i++) {
> + if (!f2fs_is_valid_blkaddr(F2FS_I_SB(inode),
> + block_nr + i,
> DATA_GENERIC_ENHANCE_READ)) {
> - ret = -EFSCORRUPTED;
> - goto err_out;
> + ret = -EFSCORRUPTED;
> + goto err_out;
> + }
> }
> +
> + /*
> + * If an entire folio is added to one bio,
> + * folio_end_read() can complete the folio read status
> + * without relying on f2fs_folio_state.
> + */
> + whole_folio_in_bio = offset == 0 &&
> + len_blks == folio_nr_pages(folio);
> +
> } else {
> size_t page_offset = offset << PAGE_SHIFT;
> +
> folio_zero_range(folio, page_offset, PAGE_SIZE);
> if (vi && !fsverity_verify_blocks(vi, folio, PAGE_SIZE, page_offset)) {
> ret = -EIO;
> @@ -2933,14 +2963,14 @@ static int f2fs_read_data_large_folio(struct inode *inode,
> }
>
> /* We must increment read_pages_pending before possible BIOs submitting
> - * to prevent from premature folio_end_read() call on folio
> + * to prevent from premature folio_end_read() call on folio.
> */
> - if (folio_test_large(folio)) {
> + if (folio_test_large(folio) && !whole_folio_in_bio) {
> ffs = f2fs_ffs_find_or_alloc(folio);
>
> /* set the bitmap to wait */
> spin_lock_irq(&ffs->state_lock);
> - ffs->read_pages_pending++;
> + ffs->read_pages_pending += len_blks;
> spin_unlock_irq(&ffs->state_lock);
> }
>
> @@ -2965,17 +2995,19 @@ static int f2fs_read_data_large_folio(struct inode *inode,
> * If the page is under writeback, we need to wait for
> * its completion to see the correct decrypted data.
> */
> - f2fs_wait_on_block_writeback(inode, block_nr);
> + for (i = 0; i < len_blks; i++)
> + f2fs_wait_on_block_writeback(inode, block_nr + i);
>
> - if (!bio_add_folio(bio, folio, F2FS_BLKSIZE,
> + if (!bio_add_folio(bio, folio, len_blks * F2FS_BLKSIZE,
> offset << PAGE_SHIFT))
> goto submit_and_realloc;
>
> folio_in_bio = true;
> - inc_page_count(F2FS_I_SB(inode), F2FS_RD_DATA);
> + for (i = 0; i < len_blks; i++)
> + inc_page_count(F2FS_I_SB(inode), F2FS_RD_DATA);
> f2fs_update_iostat(F2FS_I_SB(inode), NULL, FS_DATA_READ_IO,
> - F2FS_BLKSIZE);
> - last_block_in_bio = block_nr;
> + len_blks * F2FS_BLKSIZE);
> + last_block_in_bio = block_nr + len_blks - 1;
> }
> trace_f2fs_read_folio(folio, DATA);
> err_out:
_______________________________________________
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-08-31 4:21 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 8:26 [f2fs-dev] [PATCH 00/14] f2fs: support & optimize large folios for writable files Nanzhe Zhao via Linux-f2fs-devel
2026-08-26 8:26 ` [f2fs-dev] [PATCH 01/14] f2fs: extend folio state for large folio write path Nanzhe Zhao via Linux-f2fs-devel
2026-08-27 6:57 ` Chao Yu via Linux-f2fs-devel
2026-08-27 20:51 ` Daeho Jeong
2026-09-04 3:44 ` Daeho Jeong
2026-08-26 8:26 ` [f2fs-dev] [PATCH 02/14] f2fs: carry subpage offset and count in write IO Nanzhe Zhao via Linux-f2fs-devel
2026-08-27 7:16 ` Chao Yu via Linux-f2fs-devel
2026-08-27 21:06 ` Daeho Jeong
2026-08-26 8:26 ` [f2fs-dev] [PATCH 03/14] f2fs: support regular file buffered writes on large folios Nanzhe Zhao via Linux-f2fs-devel
2026-08-27 8:56 ` Chao Yu via Linux-f2fs-devel
2026-08-27 21:13 ` Daeho Jeong
2026-08-31 3:04 ` Chao Yu via Linux-f2fs-devel
2026-08-26 8:26 ` [f2fs-dev] [PATCH 04/14] f2fs: support atomic file large folios buffered write Nanzhe Zhao via Linux-f2fs-devel
2026-08-27 9:24 ` Chao Yu via Linux-f2fs-devel
2026-08-26 8:26 ` [f2fs-dev] [PATCH 05/14] f2fs: support large folio writeback Nanzhe Zhao via Linux-f2fs-devel
2026-08-27 11:17 ` Chao Yu via Linux-f2fs-devel
2026-08-27 22:39 ` Daeho Jeong
2026-09-04 4:04 ` Daeho Jeong
2026-09-04 4:07 ` Daeho Jeong
2026-08-26 8:26 ` [f2fs-dev] [PATCH 06/14] f2fs: prepare mmap write faults for large folios Nanzhe Zhao via Linux-f2fs-devel
2026-08-27 12:36 ` Chao Yu via Linux-f2fs-devel
2026-08-28 17:18 ` Daeho Jeong
2026-08-26 8:26 ` [f2fs-dev] [PATCH 07/14] f2fs: make GC migration large-folio aware Nanzhe Zhao via Linux-f2fs-devel
2026-08-28 17:20 ` Daeho Jeong
2026-08-31 3:14 ` Chao Yu via Linux-f2fs-devel
2026-08-26 8:26 ` [f2fs-dev] [PATCH 08/14] f2fs: optimize small block size large folio read Nanzhe Zhao via Linux-f2fs-devel
2026-08-31 4:21 ` Chao Yu via Linux-f2fs-devel [this message]
2026-08-26 8:26 ` [f2fs-dev] [PATCH 09/14] f2fs: support partial uptodate " Nanzhe Zhao via Linux-f2fs-devel
2026-08-26 8:26 ` [f2fs-dev] [PATCH 10/14] f2fs: handle partial truncate of large folio dirty subpages Nanzhe Zhao via Linux-f2fs-devel
2026-08-31 7:46 ` Chao Yu via Linux-f2fs-devel
2026-08-26 13:09 ` [f2fs-dev] [PATCH 11/14] f2fs: fix zeroing paths for large folios Nanzhe Zhao via Linux-f2fs-devel
2026-08-31 7:56 ` Chao Yu via Linux-f2fs-devel
2026-08-26 13:09 ` [f2fs-dev] [PATCH 12/14] f2fs: handle block cloning within the same large folio Nanzhe Zhao via Linux-f2fs-devel
2026-08-31 8:19 ` Chao Yu via Linux-f2fs-devel
2026-08-26 13:09 ` [f2fs-dev] [PATCH 13/14] f2fs: allow large folio support to writeable files Nanzhe Zhao via Linux-f2fs-devel
2026-08-28 17:44 ` Daeho Jeong
2026-08-31 8:31 ` Chao Yu via Linux-f2fs-devel
2026-08-26 13:09 ` [f2fs-dev] [PATCH 14/14] f2fs: make compressed files compatible with large folio Nanzhe Zhao via Linux-f2fs-devel
2026-08-28 17:52 ` Daeho Jeong
2026-08-31 8:46 ` Chao Yu 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=fe3ef362-3d4e-41cc-8237-05261c873bab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox