From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Carlos Maiolino <cem@kernel.org>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 6/6] xfs: flush multiple device caches in parallel in xlog_write_iclog
Date: Thu, 3 Sep 2026 07:44:06 +0200 [thread overview]
Message-ID: <20260903054406.GA16748@lst.de> (raw)
In-Reply-To: <20260902161858.GT1933798@frogsfrogsfrogs>
On Wed, Sep 02, 2026 at 09:18:58AM -0700, Darrick J. Wong wrote:
> On Wed, Sep 02, 2026 at 08:49:20AM +0300, Christoph Hellwig wrote:
> > When xlog_write_iclog needs to flush the cache for more than one devices,
> > the current implementations does this sequentially, which adds up the
> > flush latency for all devices. Switch to kicking off all cache flushes
> > in parallel so that only the longest latency bounds the time of the log
> > I/O. This removes the REQ_PREFLUSH optimization for the log device,
> > but as that flag is never passed on to the device and just very slightly
> > reduce the latency by queueing the following write from a lower-level
> > context it is trivially shadowed by the latency improvements of the
> > parallel flush commands.
> >
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> That looks like a neat trick. Do you see any performance speedups from
> flushing in parallel?
I haven't really done a benchmark, as all the devices I test multi-device
setups don't expose volatile write caches, so I actually had to create
a synthetic setup to fully test this in qemu. But I can kick off a run
using say consumer SSDs. I expect it to significantly speed up fsync
bound workloads.
prev parent reply other threads:[~2026-09-03 5:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 5:49 fix and then optimize cache flushes for the RT device Christoph Hellwig
2026-09-02 5:49 ` [PATCH 1/6] xfs: also flush the RT device cache in xlog_write_iclog Christoph Hellwig
2026-09-02 16:01 ` Darrick J. Wong
2026-09-02 5:49 ` [PATCH 2/6] xfs: don't continue on error in xfs_fsync Christoph Hellwig
2026-09-02 16:07 ` Darrick J. Wong
2026-09-02 5:49 ` [PATCH 3/6] xfs: clean up xfs_fsync_flush_log a bit Christoph Hellwig
2026-09-02 16:07 ` Darrick J. Wong
2026-09-02 5:49 ` [PATCH 4/6] xfs: avoid extra cache flushes for multi-device file systems in xfs_fsync Christoph Hellwig
2026-09-02 16:12 ` Darrick J. Wong
2026-09-02 5:49 ` [PATCH 5/6] xfs: optimize cache flushing for CIL commits on multi-device file systems Christoph Hellwig
2026-09-02 16:15 ` Darrick J. Wong
2026-09-02 5:49 ` [PATCH 6/6] xfs: flush multiple device caches in parallel in xlog_write_iclog Christoph Hellwig
2026-09-02 16:18 ` Darrick J. Wong
2026-09-03 5:44 ` Christoph Hellwig [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=20260903054406.GA16748@lst.de \
--to=hch@lst.de \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-xfs@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 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.