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 10:26:52 -0500 [thread overview]
Message-ID: <4E0B443C.3070608@codemonkey.ws> (raw)
In-Reply-To: <20110629145248.GC17085@lst.de>
On 06/29/2011 09:52 AM, Christoph Hellwig wrote:
> On Wed, Jun 29, 2011 at 09:20:03AM -0500, Anthony Liguori wrote:
>> Sorry, I meant having a new cache option (maybe diskcache). Semantics
>> would be:
>>
>> diskcache=on,wce=on 0
>> diskcache=on,wce=off O_SYNC
>> diskcache=off,wce=on O_DIRECT
>> diskcache=off,wce=off O_DIRECT | O_SYNC
>>
>> ignore_flush could be another option too.
>
> Please make it two options instead of a two-dimensional one.
Yeah, that was just for the table. diskcache/hostcache belongs in
-drive, wce belongs in -device.
> E.g. e hostcache=[on,off] option for the drive command line,
> where fake is the equivalent of the current code together with
>
>> I think developers usually want diskcache=on but I also agree that usually
>> in production, you want diskcache=off.
>
> Why would you want to not use O_DIRECT as a developer?
Relaunching the same guest:
cache=writethrough:
real 0m9.500s
user 0m4.720s
sys 0m3.780s
cache=none:
real 0m15.263s
user 0m4.870s
sys 0m6.390s
If you're doing kernel development where you're frequently launching the
same guest with a different kernel, it using the page cache makes a big
difference in guest boot time.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2011-06-29 15:26 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 [this message]
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=4E0B443C.3070608@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 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).