public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Dor Laor <dor.laor@gmail.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: kvm-devel@lists.sourceforge.net,
	Marcelo Tosatti <marcelo@kvack.org>,
	Avi Kivity <avi@qumranet.com>
Subject: Re: [PATCH] QEMU support for virtio balloon driver
Date: Tue, 26 Feb 2008 01:45:38 +0200	[thread overview]
Message-ID: <1203983138.3053.42.camel@localhost.localdomain> (raw)
In-Reply-To: <1203968825-19161-1-git-send-email-aliguori@us.ibm.com>


On Mon, 2008-02-25 at 13:47 -0600, Anthony Liguori wrote:
> This patch adds support to QEMU for Rusty's recently introduce virtio balloon
> driver.  The user-facing portions of this are the introduction of a "balloon"
> and "info balloon" command in the monitor.
> 

The patch looks good. Might be a good idea to split it into 2 (balloon
vs s->vdev.get_config patch.

> Right now madvise() is commented out since it causes host panics.  Ballooning
> is still functional though--the host just doesn't reclaim the memory
> immediately.
> 

Since the mmu notifiers are not merged into 2.6.25 even, we need a
temporary solution for it.
There are two+ options:
1. Use the ksm (shared pages) scan and zero ballooned pages.
   This way the memory will be quickly picked up by the kernel.
2. Add in-kernel atomic ioctl for zapping the mmu + madvise
2+. Some sort of mmu notifiers backport (hard and hacky).

IMHO 2 is the best option.
btw: Izik's ksm module enable running 50 1G xp guests over a 16G host
even without the ballooning running!



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  reply	other threads:[~2008-02-25 23:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25 19:47 [PATCH] QEMU support for virtio balloon driver Anthony Liguori
2008-02-25 23:45 ` Dor Laor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-24 21:23 Anthony Liguori
     [not found] ` <1201209786831-git-send-email-aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-01-24 22:29   ` Anthony Liguori
     [not found]     ` <4799115F.8010506-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-01-25 16:08       ` Marcelo Tosatti
2008-01-25 17:02         ` Anthony Liguori
     [not found]           ` <479A162C.1060209-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-01-26 18:47             ` Avi Kivity
2008-03-08 19:27               ` Marcelo Tosatti
2008-03-08 20:51                 ` Marcelo Tosatti
2008-03-09  2:46                   ` Anthony Liguori
2008-01-26  3:35         ` Rusty Russell
2008-01-25 23:08       ` Dor Laor
     [not found]         ` <1201302492.2944.8.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-01-26  0:10           ` Anthony Liguori
     [not found]             ` <479A7A5C.6030005-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-01-26 18:35               ` Avi Kivity

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=1203983138.3053.42.camel@localhost.localdomain \
    --to=dor.laor@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@qumranet.com \
    --cc=dor.laor@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=marcelo@kvack.org \
    /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