qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, Christoph Hellwig <hch@lst.de>,
	Qemu-devel@nongnu.org,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] Default cache mode
Date: Wed, 29 Jun 2011 13:52:19 +0100	[thread overview]
Message-ID: <BANLkTi=ONYRPp1_RHRUkseDWcYAJXevZTg@mail.gmail.com> (raw)
In-Reply-To: <4E0B1399.4050807@redhat.com>

On Wed, Jun 29, 2011 at 12:59 PM, Kevin Wolf <kwolf@redhat.com> wrote:
> 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.

I agree that cache=none is safe and fast with correct guests and local
disks.  It is beaten by cache=writeback in cases where the host has a
lot of buffer cache to play with and the guest has very little - for
example when running qemu without a -m argument.  If I was running
qemu-system-arm I might like cache=writeback.  If I was virtualizing
x86 servers I might like cache=none.

cache=none as a default - which some management tools inherit - would
be reasonable.  Folks using command-line qemu can always tweak to use
cache=writeback or even cache=unsafe if performance matters but data
integrity does not.

Whether it is safe to transition to cache=none or not depends on what
broken guests are still widely deployed.  Does CentOS 5 flush the disk
cache?

Stefan

  parent reply	other threads:[~2011-06-29 12:52 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29 11:59 [Qemu-devel] Default cache mode Kevin Wolf
2011-06-29 12:06 ` 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 [this message]
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='BANLkTi=ONYRPp1_RHRUkseDWcYAJXevZTg@mail.gmail.com' \
    --to=stefanha@gmail.com \
    --cc=Qemu-devel@nongnu.org \
    --cc=avi@redhat.com \
    --cc=hch@lst.de \
    --cc=kwolf@redhat.com \
    --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).