From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Yangyang Zang <zangyangyang66@gmail.com>, jaegeuk@kernel.org
Cc: Yangyang Zang <zangyangyang1@xiaomi.com>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] fsck.f2fs: fix meta readahead after non-contiguous blocks
Date: Mon, 3 Aug 2026 12:34:56 +0800 [thread overview]
Message-ID: <90e314e4-00f2-4f4e-a054-91936538f5de@kernel.org> (raw)
In-Reply-To: <20260701092850.1247010-1-zangyangyang1@xiaomi.com>
On 7/1/26 17:28, Yangyang Zang wrote:
> When the current block is not contiguous with the in-progress readahead
> range, f2fs_ra_meta_pages() issues the pending range but keeps the old
> start block and length.
>
> As a result, the current block is not included in any readahead range,
> and subsequent non-contiguous blocks keep reissuing the stale range
> instead of starting a new one.
>
> Reset start_blk and len after issuing the pending range so readahead can
> continue from the current block.
>
> Signed-off-by: Yangyang Zang <zangyangyang1@xiaomi.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2026-08-03 4:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 9:28 [f2fs-dev] [PATCH 1/2] fsck.f2fs: fix meta readahead after non-contiguous blocks Yangyang Zang
2026-07-01 9:28 ` [f2fs-dev] [PATCH 2/2] fsck.f2fs: read each sit block only once in build_sit_entries Yangyang Zang
2026-08-03 4:41 ` Chao Yu via Linux-f2fs-devel
2026-08-03 4:34 ` Chao Yu via Linux-f2fs-devel [this message]
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=90e314e4-00f2-4f4e-a054-91936538f5de@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=zangyangyang1@xiaomi.com \
--cc=zangyangyang66@gmail.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.