All of lore.kernel.org
 help / color / mirror / Atom feed
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 08/14] f2fs: optimize small block size large folio read
Date: Thu, 17 Sep 2026 16:09:45 +0800	[thread overview]
Message-ID: <6045b4b3-26ef-4d12-b832-7affc9574df0@kernel.org> (raw)
In-Reply-To: <20260915041909.2903887-9-zhaonanzhe@xiaomi.com>

On 9/15/26 12:19, 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 | 65 ++++++++++++++++++++++++++++++++++----------------
>  1 file changed, 45 insertions(+), 20 deletions(-)
> 
> diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
> index 287d83debf95..09ad5cf0d9aa 100644
> --- a/fs/f2fs/data.c
> +++ b/fs/f2fs/data.c
> @@ -173,8 +173,9 @@ 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;

I just notice that in somewhere, we missed to cast the private field to
f2fs_folio_state pointer as below, please take a look.

ffs = folio->private;

>  
>  			spin_lock_irqsave(&ffs->state_lock, flags);
>  			ffs->read_pages_pending -= nr_pages;
> @@ -2844,8 +2845,7 @@ static int f2fs_read_data_large_folio(struct inode *inode,
>  	pgoff_t index, offset, next_pgofs = 0;
>  	unsigned max_nr_pages = rac ? readahead_count(rac) :
>  				folio_nr_pages(folio);
> -	unsigned int nrpages;
> -	struct f2fs_folio_state *ffs;
> +	unsigned int nrpages, len_blks;
>  	int ret = 0;
>  	bool folio_in_bio = false;
>  
> @@ -2868,11 +2868,17 @@ static int f2fs_read_data_large_folio(struct inode *inode,
>  	folio_in_bio = false;
>  	index = folio->index;
>  	offset = 0;
> -	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.
>  		 */
> @@ -2901,13 +2907,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;
> @@ -2917,15 +2941,13 @@ 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)) {
> -			ffs = f2fs_ffs_find_or_alloc(folio);
> +		if (folio_test_large(folio) && !whole_folio_in_bio) {
> +			f2fs_ffs_find_or_alloc(folio);

Need to check return value?

Thanks,

>  
>  			/* set the bitmap to wait */
> -			spin_lock_irq(&ffs->state_lock);
> -			ffs->read_pages_pending++;
> -			spin_unlock_irq(&ffs->state_lock);
> +			f2fs_update_read_folio_pending(folio, len_blks);
>  		}
>  
>  		/*
> @@ -2949,17 +2971,20 @@ 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(F2FS_I_SB(inode)),
> +		if (!bio_add_folio(bio, folio,
> +				len_blks * F2FS_BLKSIZE(F2FS_I_SB(inode)),
>  				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(F2FS_I_SB(inode)));
> -		last_block_in_bio = block_nr;
> +				len_blks * F2FS_BLKSIZE(F2FS_I_SB(inode)));
> +		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

  parent reply	other threads:[~2026-09-17  8:10 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
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 [this message]
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=6045b4b3-26ef-4d12-b832-7affc9574df0@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.