From: Christoph Hellwig <hch@lst.de>
To: Carlos Maiolino <cem@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: fix cache flushes for the RT device
Date: Mon, 7 Sep 2026 10:33:06 +0300 [thread overview]
Message-ID: <20260907073427.719935-1-hch@lst.de> (raw)
Hi all,
when tracing workloads, I realized that currently the volatile write
cache on RT devices is only flushed by fsync, but never at all for
workloads that do not use fsync.
Changes since v1:
- drop the patches that are pure optimizations for a minimal fix
series
- improve a commit log
Diffstat:
xfs_file.c | 47 ++++++++++++++---------------------------------
xfs_log.c | 45 +++++++++++++++++++++++++++++++--------------
xfs_log_cil.c | 7 ++++---
3 files changed, 49 insertions(+), 50 deletions(-)
next reply other threads:[~2026-09-07 7:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 7:33 Christoph Hellwig [this message]
2026-09-07 7:33 ` [PATCH 1/3] xfs: also flush the RT device cache in xlog_write_iclog Christoph Hellwig
2026-09-10 10:40 ` Carlos Maiolino
2026-09-07 7:33 ` [PATCH 2/3] xfs: don't continue on error in xfs_fsync Christoph Hellwig
2026-09-10 10:40 ` Carlos Maiolino
2026-09-07 7:33 ` [PATCH 3/3] xfs: avoid extra cache flushes for multi-device file systems " Christoph Hellwig
2026-09-10 10:43 ` Carlos Maiolino
2026-09-11 7:29 ` fix cache flushes for the RT device Carlos Maiolino
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=20260907073427.719935-1-hch@lst.de \
--to=hch@lst.de \
--cc=cem@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox