public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Avi Kivity <avi@redhat.com>
Cc: Nolan <nolan@sigbus.net>, kvm@vger.kernel.org
Subject: Re: Live memory allocation?
Date: Mon, 30 Mar 2009 17:15:25 +0200	[thread overview]
Message-ID: <49D0E20D.2010505@wpkg.org> (raw)
In-Reply-To: <49D0DE26.8040009@redhat.com>

Avi Kivity schrieb:
> Tomasz Chmielewski wrote:
>>>
>>> Double caching is indeed a bad idea.  That's why you have cache=off 
>>> (though it isn't recommended with qcow2).
>>
>> cache= option is about write cache, right?
>>
>> Here, I'm talking about read cache.
>>
>> Or, does "cache=none" disable read cache as well?
> 
> cache=writethrough disables the write cache
> cache=none disables host caching completely

Still, if there is free memory on host, why not use it for cache?


-- 
Tomasz Chmielewski
http://wpkg.org


  reply	other threads:[~2009-03-30 15:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26 13:44 Live memory allocation? Evert
2009-03-26 14:01 ` Tomasz Chmielewski
2009-03-26 14:04   ` Izik Eidus
2009-03-26 14:11     ` Tomasz Chmielewski
2009-03-26 17:47       ` Evert
2009-03-28 13:38       ` Alberto Treviño
2009-03-28 17:17         ` Brian Jackson
2009-03-30 13:23           ` Alberto Treviño
2009-03-30 15:48             ` Brian Jackson
2009-03-28 18:25         ` Nolan
2009-03-29 12:33           ` Avi Kivity
2009-03-30 13:40             ` Tomasz Chmielewski
2009-03-30 13:48               ` Avi Kivity
2009-03-30 13:55                 ` Tomasz Chmielewski
2009-03-30 14:58                   ` Avi Kivity
2009-03-30 15:15                     ` Tomasz Chmielewski [this message]
2009-03-30 15:18                       ` Javier Guerra
2009-03-31  9:30                         ` Tomasz Chmielewski

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=49D0E20D.2010505@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=nolan@sigbus.net \
    /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