mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Seongjae Jeong <jsjlee1020@gmail.com>
To: jaegeuk@kernel.org, chao@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, jsjlee1020@gmail.com
Subject: [PATCH] f2fs: avoid unnecessary reads in f2fs_update_meta_block()
Date: Fri,  2 Oct 2026 06:48:53 +0000	[thread overview]
Message-ID: <20261002064853.37782-1-jsjlee1020@gmail.com> (raw)

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);
 
 	memcpy(cache_address(entry), src, F2FS_BLKSIZE(sbi));
 	f2fs_mark_cache_dirty(entry);
-- 
2.53.0


                 reply	other threads:[~2026-10-02  6:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261002064853.37782-1-jsjlee1020@gmail.com \
    --to=jsjlee1020@gmail.com \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --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®