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 v2] f2fs: fix to mitigate overhead of f2fs_zero_post_eof_page()
Date: Mon, 29 Sep 2025 22:30:28 +0000 [thread overview]
Message-ID: <175918502899.1733438.7787562060460882934.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250916024709.4062265-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 16 Sep 2025 10:47:09 +0800 you wrote:
> f2fs_zero_post_eof_page() may cuase more overhead due to invalidate_lock
> and page lookup, change as below to mitigate its overhead:
> - check new_size before grabbing invalidate_lock
> - lookup and invalidate pages only in range of [old_size, new_size]
>
> Fixes: ba8dac350faf ("f2fs: fix to zero post-eof page")
> Signed-off-by: Chao Yu <chao@kernel.org>
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: fix to mitigate overhead of f2fs_zero_post_eof_page()
https://git.kernel.org/jaegeuk/f2fs/c/c2f7c32b2540
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 v2] f2fs: fix to mitigate overhead of f2fs_zero_post_eof_page()
Date: Mon, 29 Sep 2025 22:30:28 +0000 [thread overview]
Message-ID: <175918502899.1733438.7787562060460882934.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250916024709.4062265-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 16 Sep 2025 10:47:09 +0800 you wrote:
> f2fs_zero_post_eof_page() may cuase more overhead due to invalidate_lock
> and page lookup, change as below to mitigate its overhead:
> - check new_size before grabbing invalidate_lock
> - lookup and invalidate pages only in range of [old_size, new_size]
>
> Fixes: ba8dac350faf ("f2fs: fix to zero post-eof page")
> Signed-off-by: Chao Yu <chao@kernel.org>
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: fix to mitigate overhead of f2fs_zero_post_eof_page()
https://git.kernel.org/jaegeuk/f2fs/c/c2f7c32b2540
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:[~2025-09-29 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 2:47 [f2fs-dev] [PATCH v2] f2fs: fix to mitigate overhead of f2fs_zero_post_eof_page() Chao Yu via Linux-f2fs-devel
2025-09-16 2:47 ` Chao Yu
2025-09-29 22:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-09-29 22:30 ` [f2fs-dev] " 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=175918502899.1733438.7787562060460882934.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.