All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Frank Swiderski <fes@google.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	riel@redhat.com, Andrea Arcangeli <aarcange@redhat.com>,
	virtualization@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	mikew@google.com
Subject: Re: [PATCH] Add a page cache-backed balloon device driver.
Date: Mon, 03 Sep 2012 18:09:32 +0300	[thread overview]
Message-ID: <5044C82C.10507@redhat.com> (raw)
In-Reply-To: <1340742778-11282-1-git-send-email-fes@google.com>

On 06/26/2012 11:32 PM, Frank Swiderski wrote:
> This implementation of a virtio balloon driver uses the page cache to
> "store" pages that have been released to the host.  The communication
> (outside of target counts) is one way--the guest notifies the host when
> it adds a page to the page cache, allowing the host to madvise(2) with
> MADV_DONTNEED.  Reclaim in the guest is therefore automatic and implicit
> (via the regular page reclaim).  This means that inflating the balloon
> is similar to the existing balloon mechanism, but the deflate is
> different--it re-uses existing Linux kernel functionality to
> automatically reclaim.

Interesting idea.

How is the host able to manage overcommit this way?  If deflate is not
host controlled, the host may start swapping guests out to disk if they
all self-deflate.


-- 
error compiling committee.c: too many arguments to function

WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Frank Swiderski <fes@google.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
	riel@redhat.com, kvm@vger.kernel.org,
	"Michael S. Tsirkin" <mst@redhat.com>,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org, mikew@google.com
Subject: Re: [PATCH] Add a page cache-backed balloon device driver.
Date: Mon, 03 Sep 2012 18:09:32 +0300	[thread overview]
Message-ID: <5044C82C.10507@redhat.com> (raw)
In-Reply-To: <1340742778-11282-1-git-send-email-fes@google.com>

On 06/26/2012 11:32 PM, Frank Swiderski wrote:
> This implementation of a virtio balloon driver uses the page cache to
> "store" pages that have been released to the host.  The communication
> (outside of target counts) is one way--the guest notifies the host when
> it adds a page to the page cache, allowing the host to madvise(2) with
> MADV_DONTNEED.  Reclaim in the guest is therefore automatic and implicit
> (via the regular page reclaim).  This means that inflating the balloon
> is similar to the existing balloon mechanism, but the deflate is
> different--it re-uses existing Linux kernel functionality to
> automatically reclaim.

Interesting idea.

How is the host able to manage overcommit this way?  If deflate is not
host controlled, the host may start swapping guests out to disk if they
all self-deflate.


-- 
error compiling committee.c: too many arguments to function

  parent reply	other threads:[~2012-09-03 15:09 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26 20:32 [PATCH] Add a page cache-backed balloon device driver Frank Swiderski
2012-06-26 20:40 ` Rik van Riel
2012-06-26 20:40   ` Rik van Riel
2012-06-26 21:31   ` Frank Swiderski
2012-06-26 21:31     ` Frank Swiderski
2012-06-26 21:45     ` Rik van Riel
2012-06-26 21:45       ` Rik van Riel
2012-06-26 23:45       ` Frank Swiderski
2012-06-27  9:04         ` Michael S. Tsirkin
2012-06-27  9:04           ` Michael S. Tsirkin
2012-06-26 21:47     ` Michael S. Tsirkin
2012-06-26 21:47       ` Michael S. Tsirkin
2012-06-26 23:21       ` Frank Swiderski
2012-06-26 23:21         ` Frank Swiderski
2012-06-27  9:02         ` Michael S. Tsirkin
2012-06-27  9:02           ` Michael S. Tsirkin
2012-07-02  0:29         ` Rusty Russell
2012-07-02  0:29           ` Rusty Russell
2012-09-03  6:35           ` Paolo Bonzini
2012-09-03  6:35             ` Paolo Bonzini
2012-09-06  1:35             ` Rusty Russell
2012-09-06  1:35               ` Rusty Russell
2012-06-26 21:41 ` Michael S. Tsirkin
2012-06-26 21:41   ` Michael S. Tsirkin
2012-06-27  2:56   ` Rusty Russell
2012-06-27  2:56     ` Rusty Russell
2012-06-27 15:48     ` Frank Swiderski
2012-06-27 15:48       ` Frank Swiderski
2012-06-27 16:06       ` Michael S. Tsirkin
2012-06-27 16:06         ` Michael S. Tsirkin
2012-06-27 16:08         ` Frank Swiderski
2012-06-27 16:08           ` Frank Swiderski
2012-06-27  9:40 ` Amit Shah
2012-06-27  9:40   ` Amit Shah
2012-08-30  8:57 ` Michael S. Tsirkin
2012-08-30  8:57   ` Michael S. Tsirkin
2012-09-03 15:09 ` Avi Kivity [this message]
2012-09-03 15:09   ` Avi Kivity
2012-09-10  9:05 ` Michael S. Tsirkin
2012-09-10  9:05   ` Michael S. Tsirkin
2012-09-10 17:37   ` Mike Waychison
2012-09-10 17:37     ` Mike Waychison
2012-09-10 18:04     ` Rik van Riel
2012-09-10 18:04       ` Rik van Riel
2012-09-10 18:29       ` Mike Waychison
2012-09-10 18:29         ` Mike Waychison
2012-09-10 19:59     ` Michael S. Tsirkin
2012-09-10 19:59       ` Michael S. Tsirkin
2012-09-10 19:59       ` Michael S. Tsirkin
2012-09-10 20:49       ` Mike Waychison
2012-09-10 20:49         ` Mike Waychison
2012-09-10 21:10         ` Michael S. Tsirkin
2012-09-10 21:10           ` Michael S. Tsirkin
2012-10-30 15:29           ` Michael S. Tsirkin
2012-10-30 15:29             ` Michael S. Tsirkin
2012-10-30 16:25             ` Mike Waychison
2012-10-30 16:25               ` Mike Waychison
2012-09-12  5:25         ` Rusty Russell
2012-09-12  5:25           ` Rusty Russell
2012-06-26 20:32 Frank Swiderski

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=5044C82C.10507@redhat.com \
    --to=avi@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=fes@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikew@google.com \
    --cc=mst@redhat.com \
    --cc=riel@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=virtualization@lists.linux-foundation.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 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.