public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Javier Guerra <javier@guerrag.com>
Cc: Avi Kivity <avi@redhat.com>, Nolan <nolan@sigbus.net>,
	kvm@vger.kernel.org
Subject: Re: Live memory allocation?
Date: Tue, 31 Mar 2009 11:30:29 +0200	[thread overview]
Message-ID: <49D1E2B5.7030901@wpkg.org> (raw)
In-Reply-To: <90eb1dc70903300818u643d0c55n8030f104bc984f6f@mail.gmail.com>

Javier Guerra schrieb:
> On Mon, Mar 30, 2009 at 10:15 AM, Tomasz Chmielewski <mangoo@wpkg.org> wrote:
>> Still, if there is free memory on host, why not use it for cache?
> 
> because it's best used on the guest;

It is correct, but not realistic from the administrative point of view.

Let's say you have several KVM hosts, each with 16 GB RAM.

Guests can come and go - so you give them only as much memory as they 
need (more or less).
In other words, normally, you don't create the first guest with 16 GB 
RAM assigned. Upon creation of the second guest 2 hours later, you don't 
stop guest 1, just to start both guests with 8 GB RAM a while later. And 
so on. And so on, stopping and starting a whole bunch of guests until 
each of them has 512 MB RAM.

No, not all guests support ballooning.
But for those which support ballooning, the easiest way to implement it 
would be to write a user-space daemon I guess.


> so, not
> cacheing already-cached data, it's free to cache other more important
> things, or to keep more of the VMs memory on RAM.

Correct - if the host knew what the guest already cached, the host could 
use RAM for other things.

Anyway, there are still more pressing issues than that ;)


-- 
Tomasz Chmielewski
http://wpkg.org

      reply	other threads:[~2009-03-31  9:30 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
2009-03-30 15:18                       ` Javier Guerra
2009-03-31  9:30                         ` Tomasz Chmielewski [this message]

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=49D1E2B5.7030901@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=avi@redhat.com \
    --cc=javier@guerrag.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