From: Christoph Hellwig <hch@infradead.org>
To: Chao Yu <chao@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH v3] f2fs: introduce flush_policy sysfs entry
Date: Tue, 12 Aug 2025 00:59:10 -0700 [thread overview]
Message-ID: <aJr0Tk36ZNiCg8mQ@infradead.org> (raw)
In-Reply-To: <dec5b832-53f1-4274-902c-418f01df9458@kernel.org>
On Tue, Aug 12, 2025 at 03:53:54PM +0800, Chao Yu wrote:
> > What did you use before? At least for older qemu the default was
> > buffered I/O, which can lead to very expensive fua or flush calls.
>
> Previously, I didn't use any cache= option, as manual described, it
> should equal to cache=wrteback.
Modern qemu actually split the cache option. You absolute want
cache.direct=on. If you don't do simulated power fail testing by
killing qemu (or run real workloads for the matter, but who does that
:)) it might make sense to just ignore the flushes with cache.no-flush=on
as well, which is what I do for my test VMs on the laptop.
next prev parent reply other threads:[~2025-08-12 7:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 3:48 [PATCH v3] f2fs: introduce flush_policy sysfs entry Chao Yu
2025-08-07 5:31 ` [f2fs-dev] " Zhiguo Niu
2025-08-11 10:52 ` Christoph Hellwig
2025-08-11 13:44 ` Bart Van Assche
2025-08-12 6:39 ` Chao Yu
2025-08-12 6:28 ` Chao Yu
2025-08-12 7:32 ` Christoph Hellwig
2025-08-12 7:53 ` Chao Yu
2025-08-12 7:59 ` Christoph Hellwig [this message]
2025-08-12 8:22 ` Chao Yu
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=aJr0Tk36ZNiCg8mQ@infradead.org \
--to=hch@infradead.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-block@vger.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;
as well as URLs for NNTP newsgroup(s).