From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
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: Mon, 19 Jan 2026 13:50:53 +0000 [thread overview]
Message-ID: <176883065328.1419958.4608417190161935533.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260112013320.8028-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 12 Jan 2026 09:33:20 +0800 you wrote:
> For consecutive large hole mapping across {d,id,did}nodes , we don't
> need to call f2fs_map_blocks() to check one hole block per one time,
> instead, we can use map.m_next_pgofs as a hint of next potential valid
> block, so that we can skip calling f2fs_map_blocks the range of
> [cur_pgofs + 1, .m_next_pgofs).
>
> 1) regular case
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: avoid f2fs_map_blocks() for consecutive holes in readpages
https://git.kernel.org/jaegeuk/f2fs/c/fe2961fb77e4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
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: patchwork-bot+f2fs@kernel.org
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: Mon, 19 Jan 2026 13:50:53 +0000 [thread overview]
Message-ID: <176883065328.1419958.4608417190161935533.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260112013320.8028-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 12 Jan 2026 09:33:20 +0800 you wrote:
> For consecutive large hole mapping across {d,id,did}nodes , we don't
> need to call f2fs_map_blocks() to check one hole block per one time,
> instead, we can use map.m_next_pgofs as a hint of next potential valid
> block, so that we can skip calling f2fs_map_blocks the range of
> [cur_pgofs + 1, .m_next_pgofs).
>
> 1) regular case
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: avoid f2fs_map_blocks() for consecutive holes in readpages
https://git.kernel.org/jaegeuk/f2fs/c/fe2961fb77e4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-01-19 13:54 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
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 [this message]
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=176883065328.1419958.4608417190161935533.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@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.