virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Frank Swiderski <fes@google.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
	Rik van Riel <riel@redhat.com>, Rafael Aquini <aquini@redhat.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	Ying Han <yinghan@google.com>,
	mikew@google.com
Subject: Re: [PATCH] Add a page cache-backed balloon device driver.
Date: Wed, 27 Jun 2012 00:47:10 +0300	[thread overview]
Message-ID: <20120626214709.GA15406@redhat.com> (raw)
In-Reply-To: <CAK+C7kWKtoYC=1fBQ45RTFfNc3p2PwZbLMOefMTtzOfsqe_k8w@mail.gmail.com>

On Tue, Jun 26, 2012 at 02:31:26PM -0700, Frank Swiderski wrote:
> On Tue, Jun 26, 2012 at 1:40 PM, Rik van Riel <riel@redhat.com> wrote:
> > On 06/26/2012 04: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.
> >>
> >> Signed-off-by: Frank Swiderski<fes@google.com>
> >
> >
> > It is a great idea, but how can this memory balancing
> > possibly work if someone uses memory cgroups inside a
> > guest?
> 
> Thanks and good point--this isn't something that I considered in the
> implementation.
> 
> > Having said that, we currently do not have proper
> > memory reclaim balancing between cgroups at all, so
> > requiring that of this balloon driver would be
> > unreasonable.
> >
> > The code looks good to me, my only worry is the
> > code duplication. We now have 5 balloon drivers,
> > for 4 hypervisors, all implementing everything
> > from scratch...
> 
> Do you have any recommendations on this?  I could (I think reasonably
> so) modify the existing virtio_balloon.c and have it change behavior
> based on a feature bit or other configuration.  I'm not sure that
> really addresses the root of what you're pointing out--it's still
> adding a different implementation, but doing so as an extension of an
> existing one.
> 
> fes

Let's assume it's a feature bit: how would you
formulate what the feature does *from host point of view*?

-- 
MST

  parent reply	other threads:[~2012-06-26 21:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1340742778-11282-1-git-send-email-fes@google.com>
2012-06-26 20:40 ` [PATCH] Add a page cache-backed balloon device driver Rik van Riel
2012-06-26 21:31   ` Frank Swiderski
2012-06-26 21:45     ` Rik van Riel
     [not found]       ` <CAK+C7kVHeUz7nUV1vtSHrK6vXorLsZoos82NFm0P0Ux0rEOZGQ@mail.gmail.com>
2012-06-27  9:04         ` Michael S. Tsirkin
2012-06-26 21:47     ` Michael S. Tsirkin [this message]
2012-06-26 23:21       ` Frank Swiderski
2012-06-27  9:02         ` Michael S. Tsirkin
2012-07-02  0:29         ` Rusty Russell
2012-09-03  6:35           ` Paolo Bonzini
2012-09-06  1:35             ` Rusty Russell
2012-06-26 21:41 ` Michael S. Tsirkin
2012-06-27  2:56   ` Rusty Russell
2012-06-27 15:48     ` Frank Swiderski
2012-06-27 16:06       ` Michael S. Tsirkin
2012-06-27 16:08         ` Frank Swiderski
2012-06-27  9:40 ` Amit Shah
2012-08-30  8:57 ` Michael S. Tsirkin
2012-09-03 15:09 ` Avi Kivity
2012-09-10  9:05 ` Michael S. Tsirkin
2012-09-10 17:37   ` Mike Waychison
2012-09-10 18:04     ` Rik van Riel
2012-09-10 18:29       ` Mike Waychison
2012-09-10 19:59     ` Michael S. Tsirkin
2012-09-10 20:49       ` Mike Waychison
2012-09-10 21:10         ` Michael S. Tsirkin
2012-10-30 15:29           ` Michael S. Tsirkin
2012-10-30 16:25             ` Mike Waychison
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=20120626214709.GA15406@redhat.com \
    --to=mst@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=aquini@redhat.com \
    --cc=fes@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikew@google.com \
    --cc=riel@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=yinghan@google.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).