From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: allocate HOT_DATA for IPU writes
Date: Tue, 02 Sep 2025 20:20:13 +0000 [thread overview]
Message-ID: <175684441374.425353.1717450032024097846.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250827215222.1615844-1-jaegeuk@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 27 Aug 2025 21:52:22 +0000 you wrote:
> Let's split IPU writes in hot data area to improve the GC efficiency.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
> fs/f2fs/segment.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Here is the summary with links:
- [f2fs-dev] f2fs: allocate HOT_DATA for IPU writes
https://git.kernel.org/jaegeuk/f2fs/c/c872b6279cd2
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: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: allocate HOT_DATA for IPU writes
Date: Tue, 02 Sep 2025 20:20:13 +0000 [thread overview]
Message-ID: <175684441374.425353.1717450032024097846.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250827215222.1615844-1-jaegeuk@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 27 Aug 2025 21:52:22 +0000 you wrote:
> Let's split IPU writes in hot data area to improve the GC efficiency.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
> fs/f2fs/segment.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Here is the summary with links:
- [f2fs-dev] f2fs: allocate HOT_DATA for IPU writes
https://git.kernel.org/jaegeuk/f2fs/c/c872b6279cd2
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-02 20:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 21:52 [f2fs-dev] [PATCH] f2fs: allocate HOT_DATA for IPU writes Jaegeuk Kim via Linux-f2fs-devel
2025-08-27 21:52 ` Jaegeuk Kim
2025-08-28 3:31 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-08-28 3:31 ` Chao Yu
2025-08-28 15:23 ` Jaegeuk Kim via Linux-f2fs-devel
2025-08-28 15:23 ` Jaegeuk Kim
2025-08-28 23:17 ` Chao Yu via Linux-f2fs-devel
2025-08-28 23:17 ` Chao Yu
2025-08-29 20:47 ` Jaegeuk Kim via Linux-f2fs-devel
2025-08-29 20:47 ` Jaegeuk Kim
2025-08-30 1:11 ` Chao Yu via Linux-f2fs-devel
2025-08-30 1:11 ` Chao Yu
2025-08-30 23:54 ` Jaegeuk Kim via Linux-f2fs-devel
2025-08-30 23:54 ` Jaegeuk Kim
2025-09-01 2:15 ` Chao Yu via Linux-f2fs-devel
2025-09-01 2:15 ` Chao Yu
2025-09-02 20:20 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-09-02 20:20 ` 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=175684441374.425353.1717450032024097846.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--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.