From: Kevin Wolf <kwolf@redhat.com>
To: Qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Christoph Hellwig <hch@lst.de>,
Anthony Liguori <anthony@codemonkey.ws>,
Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] Default cache mode
Date: Wed, 29 Jun 2011 13:59:21 +0200 [thread overview]
Message-ID: <4E0B1399.4050807@redhat.com> (raw)
Hi,
I think we have touched this topic before during some IRC discussions or
somewhere deep in a mailing list thread, but I think it hasn't been
discussed on the list.
Our default cache mode of cache=writethrough is extremely conservative
and provides absolute safety at the cost of performance, and most people
don't use it if they know that it can be changed because it just
performs too bad. There are use cases where you need it (broken guest
OS), but none and writeback are just as correct with respect to the
specs and they are safe to use with current OSes. And even with broken
OSes, in many use cases it doesn't really matter if you lose a VM and
have to reinstall it (which is probably true even more for users
invoking qemu directly instead of using libvirt).
I think the motivation to switch from writeback to writethrough as
default was that writeback was entirely unsafe back then. This isn't
true any more, so is there still enough reason to have the slow
writethrough mode as default?
I'm not entirely sure if I should suggest writeback or none as the new
default, but I think it could make sense to change it.
Kevin
next reply other threads:[~2011-06-29 11:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 11:59 Kevin Wolf [this message]
2011-06-29 12:06 ` [Qemu-devel] Default cache mode Anthony Liguori
2011-06-29 12:16 ` Kevin Wolf
2011-06-29 12:23 ` Anthony Liguori
2011-06-29 12:32 ` Kevin Wolf
2011-06-29 13:51 ` Christoph Hellwig
2011-06-29 14:17 ` Michael Tokarev
2011-06-29 14:50 ` Christoph Hellwig
2011-06-29 15:07 ` Michael Tokarev
2011-06-29 13:50 ` Christoph Hellwig
2011-06-29 14:13 ` Anthony Liguori
2011-06-29 14:47 ` Christoph Hellwig
2011-06-29 16:03 ` Stefan Hajnoczi
2011-06-29 13:53 ` Frediano Ziglio
2011-06-29 14:11 ` Kevin Wolf
2011-06-29 14:12 ` Christoph Hellwig
2011-06-29 14:21 ` Kevin Wolf
2011-06-29 13:49 ` Christoph Hellwig
2011-06-29 12:08 ` Anthony Liguori
2011-06-29 13:55 ` Christoph Hellwig
2011-06-29 14:20 ` Anthony Liguori
2011-06-29 14:52 ` Christoph Hellwig
2011-06-29 15:26 ` Anthony Liguori
2011-06-29 12:21 ` Alexander Graf
2011-06-29 13:57 ` Stefan Hajnoczi
2011-06-29 14:05 ` Alexander Graf
2011-06-29 12:52 ` Stefan Hajnoczi
2011-06-29 13:56 ` Christoph Hellwig
2011-06-29 13:00 ` Avi Kivity
2011-06-29 13:05 ` Anthony Liguori
2011-06-29 13:30 ` Avi Kivity
2011-06-29 13:11 ` Kevin Wolf
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=4E0B1399.4050807@redhat.com \
--to=kwolf@redhat.com \
--cc=Qemu-devel@nongnu.org \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=hch@lst.de \
--cc=stefanha@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).