All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nanzhe Zhao" <nzzhao@126.com>
To: "Chao Yu" <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: avoid f2fs_map_blocks() for consecutive holes in readpages
Date: Tue, 20 Jan 2026 08:24:59 +0800 (CST)	[thread overview]
Message-ID: <7489ce81.333.19bd8ca5df6.Coremail.nzzhao@126.com> (raw)
In-Reply-To: <bf56a771-129b-4bf1-b5c7-05ecba6cda00@kernel.org>

Hi Chao:
At 2026-01-19 21:44:48, "Chao Yu" <chao@kernel.org> wrote:
>
>I guess f2fs_map_no_dnode() will update map->m_next_pgofs to pgofs of next
>potential valid dnode.
>
>Thanks,
>

I guess we were discussing the cases that f2fs_get_dnode_of_data won't return
-ENOENT in f2fs_map_blocks but dn.blkaddr is still NULL_ADDR or NEW_ADDR ?

I think I might understand the intention behind your repeated emphasis on the 
f2fs_map_no_dnode case?  Are you saying that, on F2FS, the vast majority of sparse 
files fall into holes where the dnode hasn't been allocated at all, and that within the 
dnode the blkaddr values NULL_ADDR and NEW_ADDR—especially the latter on the read path
—are relatively uncommon?

Thanks,
Nanzhe Zhao
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

WARNING: multiple messages have this Message-ID (diff)
From: "Nanzhe Zhao" <nzzhao@126.com>
To: "Chao Yu" <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re:Re: [f2fs-dev] [PATCH] f2fs: avoid f2fs_map_blocks() for consecutive holes in readpages
Date: Tue, 20 Jan 2026 08:24:59 +0800 (CST)	[thread overview]
Message-ID: <7489ce81.333.19bd8ca5df6.Coremail.nzzhao@126.com> (raw)
In-Reply-To: <bf56a771-129b-4bf1-b5c7-05ecba6cda00@kernel.org>

Hi Chao:
At 2026-01-19 21:44:48, "Chao Yu" <chao@kernel.org> wrote:
>
>I guess f2fs_map_no_dnode() will update map->m_next_pgofs to pgofs of next
>potential valid dnode.
>
>Thanks,
>

I guess we were discussing the cases that f2fs_get_dnode_of_data won't return
-ENOENT in f2fs_map_blocks but dn.blkaddr is still NULL_ADDR or NEW_ADDR ?

I think I might understand the intention behind your repeated emphasis on the 
f2fs_map_no_dnode case?  Are you saying that, on F2FS, the vast majority of sparse 
files fall into holes where the dnode hasn't been allocated at all, and that within the 
dnode the blkaddr values NULL_ADDR and NEW_ADDR—especially the latter on the read path
—are relatively uncommon?

Thanks,
Nanzhe Zhao

  reply	other threads:[~2026-01-20  0:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12  1:33 [f2fs-dev] [PATCH] f2fs: avoid f2fs_map_blocks() for consecutive holes in readpages Chao Yu via Linux-f2fs-devel
2026-01-12  1:33 ` Chao Yu
2026-01-15 12:48 ` [f2fs-dev] " Nanzhe Zhao
2026-01-15 12:48   ` Nanzhe Zhao
2026-01-16  8:52   ` Chao Yu via Linux-f2fs-devel
2026-01-16  8:52     ` Chao Yu
2026-01-19  7:43     ` Nanzhe Zhao
2026-01-19  7:43       ` Nanzhe Zhao
2026-01-19 13:44       ` Chao Yu via Linux-f2fs-devel
2026-01-19 13:44         ` Chao Yu
2026-01-20  0:24         ` Nanzhe Zhao [this message]
2026-01-20  0:24           ` Nanzhe Zhao
2026-01-20 12:49           ` Chao Yu via Linux-f2fs-devel
2026-01-20 12:49             ` Chao Yu
2026-01-19 13:50 ` patchwork-bot+f2fs--- via Linux-f2fs-devel
2026-01-19 13:50   ` patchwork-bot+f2fs

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=7489ce81.333.19bd8ca5df6.Coremail.nzzhao@126.com \
    --to=nzzhao@126.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 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.