From: Yonggil Song <yonggil.song@samsung.com>
To: "jaegeuk@kernel.org" <jaegeuk@kernel.org>,
"chao@kernel.org" <chao@kernel.org>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Dongjin Kim <dongjin_.kim@samsung.com>,
Daejun Park <daejun7.park@samsung.com>
Subject: [PATCH v3] f2fs: issue multi-device flushes in parallel
Date: Thu, 06 Aug 2026 12:39:18 +0900 [thread overview]
Message-ID: <20260806033918epcms2p7fa34d6df7c1045b19ac026d44b877f2f@epcms2p7> (raw)
In-Reply-To: <CGME20260806030841epcms2p72fcdb3db8c3b6de434ceaff5635c8f41@epcms2p7>
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.
Flush every dirty device best-effort and in parallel instead: build
one PREFLUSH bio per dirty device, submit them all, then wait for
every completion, returning the first error seen (0 if all succeed).
This bounds the flush window by the slowest device rather than the sum
of all of them. No caller depends on the previous early-abort
behaviour -- fsync only checks whether the return value is zero
(fs/f2fs/file.c). The checkpoint path (f2fs_flush_device_cache) is
unaffected; this only touches the fsync flush path.
The per-device bio/completion array is small and bounded (at most
MAX_DEVICES entries), so allocate it with __GFP_NOFAIL rather than
keeping a separate serial fallback path for allocation failure.
Signed-off-by: Yonggil Song <yonggil.song@samsung.com>
---
fs/f2fs/segment.c | 44 +++++++++++++++++++++++++++++++++++++++++---
1 file changed, 41 insertions(+), 3 deletions(-)
diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
index d71ddb3ee918..5c7a3992cf60 100644
--- a/fs/f2fs/segment.c
+++ b/fs/f2fs/segment.c
@@ -566,21 +566,59 @@ static int __submit_flush_wait(struct f2fs_sb_info *sbi,
return ret;
}
+static void f2fs_flush_end_io(struct bio *bio)
+{
+ complete(bio->bi_private);
+}
+
+struct f2fs_flush_bio {
+ struct bio bio;
+ struct completion wait;
+};
+
static int submit_flush_wait(struct f2fs_sb_info *sbi, nid_t ino)
{
+ struct f2fs_flush_bio *flush_bio;
+ unsigned long devices = 0;
int ret = 0;
int i;
if (!f2fs_is_multi_device(sbi))
return __submit_flush_wait(sbi, sbi->sb->s_bdev);
+ flush_bio = kmalloc(array_size(sbi->s_ndevs, sizeof(*flush_bio)),
+ GFP_NOFS | __GFP_NOFAIL);
+
for (i = 0; i < sbi->s_ndevs; i++) {
if (!f2fs_is_dirty_device(sbi, ino, i, FLUSH_INO))
continue;
- ret = __submit_flush_wait(sbi, FDEV(i).bdev);
- if (ret)
- break;
+
+ bio_init(&flush_bio[i].bio, FDEV(i).bdev, NULL, 0,
+ REQ_OP_WRITE | REQ_SYNC | REQ_PREFLUSH);
+ init_completion(&flush_bio[i].wait);
+ flush_bio[i].bio.bi_private = &flush_bio[i].wait;
+ flush_bio[i].bio.bi_end_io = f2fs_flush_end_io;
+ devices |= BIT(i);
+ submit_bio(&flush_bio[i].bio);
+ }
+
+ for (i = 0; i < sbi->s_ndevs; i++) {
+ int err;
+
+ if (!(devices & BIT(i)))
+ continue;
+
+ wait_for_completion(&flush_bio[i].wait);
+ err = blk_status_to_errno(flush_bio[i].bio.bi_status);
+ trace_f2fs_issue_flush(FDEV(i).bdev, test_opt(sbi, NOBARRIER),
+ test_opt(sbi, FLUSH_MERGE), err);
+ if (!err)
+ f2fs_update_iostat(sbi, NULL, FS_FLUSH_IO, 0);
+ else if (!ret)
+ ret = err;
+ bio_uninit(&flush_bio[i].bio);
}
+ kfree(flush_bio);
return ret;
}
--
2.43.0
next prev parent reply other threads:[~2026-08-06 3:39 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] " Yonggil Song
2026-08-06 3:13 ` Chao Yu
2026-08-06 3:39 ` Yonggil Song [this message]
2026-08-06 3:46 ` [PATCH v3] " Chao Yu
2026-08-11 4: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=20260806033918epcms2p7fa34d6df7c1045b19ac026d44b877f2f@epcms2p7 \
--to=yonggil.song@samsung.com \
--cc=chao@kernel.org \
--cc=daejun7.park@samsung.com \
--cc=dongjin_.kim@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®