From: patchwork-bot+f2fs@kernel.org
To: Yonggil Song <yonggil.song@samsung.com>
Cc: jaegeuk@kernel.org, chao@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, dongjin_.kim@samsung.com
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: issue multi-device flushes in parallel
Date: Tue, 11 Aug 2026 04:30:11 +0000 [thread overview]
Message-ID: <178642261113.332426.14184401363226407725.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260806033918epcms2p7fa34d6df7c1045b19ac026d44b877f2f@epcms2p7>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 06 Aug 2026 12:39:18 +0900 you wrote:
> On a multi-device setup, submit_flush_wait() walked the dirty devices
> in order and aborted the whole loop on the first device whose flush
> failed, leaving the remaining dirty devices un-flushed. Each device
> still needs its own data made durable, so a failure on one device must
> not skip the others. It also waited for one device's flush to complete
> before issuing the next, even though the devices have independent
> flush queues and could be flushed concurrently.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3] f2fs: issue multi-device flushes in parallel
https://git.kernel.org/jaegeuk/f2fs/c/e1116f8e98ea
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-11 4:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260806030841epcms2p72fcdb3db8c3b6de434ceaff5635c8f41@epcms2p7>
2026-08-06 3:08 ` [PATCH v2] f2fs: issue multi-device flushes in parallel Yonggil Song
2026-08-06 3:13 ` Chao Yu
2026-08-06 3:39 ` [PATCH v3] " Yonggil Song
2026-08-06 3:46 ` Chao Yu
2026-08-11 4:30 ` patchwork-bot+f2fs [this message]
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=178642261113.332426.14184401363226407725.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=dongjin_.kim@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yonggil.song@samsung.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox