From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Yohan Joung <jyh429@gmail.com>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: optimize f2fs DIO overwrites
Date: Tue, 18 Mar 2025 01:30:32 +0000 [thread overview]
Message-ID: <174226143279.3976340.11320826422025580869.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250317133611.457-1-yohan.joung@sk.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 17 Mar 2025 22:36:11 +0900 you wrote:
> this is unnecessary when we know we are overwriting already allocated
> blocks and the overhead of starting a transaction can be significant
> especially for multithreaded workloads doing small writes.
>
> Signed-off-by: Yohan Joung <yohan.joung@sk.com>
> ---
> fs/f2fs/data.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
Here is the summary with links:
- [f2fs-dev,v2] f2fs: optimize f2fs DIO overwrites
https://git.kernel.org/jaegeuk/f2fs/c/351bc761338d
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: Yohan Joung <jyh429@gmail.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, daeho43@gmail.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: optimize f2fs DIO overwrites
Date: Tue, 18 Mar 2025 01:30:32 +0000 [thread overview]
Message-ID: <174226143279.3976340.11320826422025580869.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250317133611.457-1-yohan.joung@sk.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 17 Mar 2025 22:36:11 +0900 you wrote:
> this is unnecessary when we know we are overwriting already allocated
> blocks and the overhead of starting a transaction can be significant
> especially for multithreaded workloads doing small writes.
>
> Signed-off-by: Yohan Joung <yohan.joung@sk.com>
> ---
> fs/f2fs/data.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
Here is the summary with links:
- [f2fs-dev,v2] f2fs: optimize f2fs DIO overwrites
https://git.kernel.org/jaegeuk/f2fs/c/351bc761338d
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-03-18 1:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 13:36 [f2fs-dev] [PATCH v2] f2fs: optimize f2fs DIO overwrites Yohan Joung
2025-03-17 13:36 ` Yohan Joung
2025-03-18 1:18 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-03-18 1:18 ` Chao Yu
2025-03-18 1:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-03-18 1: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=174226143279.3976340.11320826422025580869.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--cc=jyh429@gmail.com \
--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.