From: Chao Yu <chao@kernel.org>
To: Daeho Jeong <daeho43@gmail.com>
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, jaegeuk@kernel.org,
Seongjae Jeong <jsjlee1020@gmail.com>
Subject: Re: [PATCH] f2fs: avoid unnecessary reads in f2fs_update_meta_block()
Date: Sun, 11 Oct 2026 16:41:53 +0800 [thread overview]
Message-ID: <00c340f7-723c-4b17-a5db-17906ff2951a@kernel.org> (raw)
In-Reply-To: <20261002064853.37782-1-jsjlee1020@gmail.com>
On 10/2/26 14:48, Seongjae Jeong wrote:
> When the packed SSA feature is enabled, f2fs_update_meta_block()
> uses f2fs_get_meta_cache_retry(), which reads the target block from
> disk if the cache entry is not uptodate.
>
> However, f2fs_update_meta_block() overwrites the entire filesystem
> block with memcpy(), so the existing contents are not needed.
> Partial updates to packed SSA blocks are handled separately in
> write_sum_block().
>
> Use f2fs_grab_meta_cache() unconditionally to avoid reading blocks
> that will be fully overwritten. Also remove the error check, since
> f2fs_grab_meta_cache() retries allocation failures internally and
> does not return an error pointer.
>
> Signed-off-by: Seongjae Jeong <jsjlee1020@gmail.com>
> ---
> fs/f2fs/segment.c | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index 794e0d99fc7c..51858f64e43e 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -2844,13 +2844,7 @@ void f2fs_update_meta_block(struct f2fs_sb_info *sbi,
> {
> struct f2fs_cached_block *entry;
>
> - if (!f2fs_sb_has_packed_ssa(sbi))
> - entry = f2fs_grab_meta_cache(sbi, blk_addr);
> - else
> - entry = f2fs_get_meta_cache_retry(sbi, blk_addr);
> -
> - if (IS_ERR(entry))
> - return;
> + entry = f2fs_grab_meta_cache(sbi, blk_addr);
Daeho,
From code side, I feel this is clean.
But, could you double check this cleanup? in case if we handle this
intentionally in original patch for something.
Thanks,
>
> memcpy(cache_address(entry), src, F2FS_BLKSIZE(sbi));
> f2fs_mark_cache_dirty(entry);
prev parent reply other threads:[~2026-10-11 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 6:48 Seongjae Jeong
2026-10-11 8:41 ` Chao Yu [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=00c340f7-723c-4b17-a5db-17906ff2951a@kernel.org \
--to=chao@kernel.org \
--cc=daeho43@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=jsjlee1020@gmail.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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®