All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Christoph Hellwig <hch@lst.de>
Cc: Kevin Wolf <kwolf@redhat.com>, Avi Kivity <avi@redhat.com>,
	Qemu-devel@nongnu.org,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] Default cache mode
Date: Wed, 29 Jun 2011 09:13:35 -0500	[thread overview]
Message-ID: <4E0B330F.7090307@codemonkey.ws> (raw)
In-Reply-To: <20110629135059.GB15863@lst.de>

On 06/29/2011 08:50 AM, Christoph Hellwig wrote:
> On Wed, Jun 29, 2011 at 07:23:31AM -0500, Anthony Liguori wrote:
>> Which file system on the host?
>
> Any filesystem.  Although extN and btrfs are particularly bad.
>
>> At any rate, I'm a big fan of making wce tunable in the guest and then I
>> think setting wce=1 is quite reasonable to do by default.
>
> Note that this means a manual override during each boot.  Windows and
> modern Linux just use what's available.  Only Solaris with ZFS actually
> turns WCE on if it's not set AFAIK.  And to me it's a rather questionable
> behaviour at least for SCSI disks where the admin might have chosen
> those intentionally.  (unlike ATA disks SCSI allows to store the setting
> permanently)

Is WCE ever persisted by a disk?  Would it make sense to have a 
mechanism to persist the WCE setting for a guest?

Regards,

Anthony Liguori

>

  reply	other threads:[~2011-06-29 14:13 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 [this message]
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=4E0B330F.7090307@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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 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.