From: Rusty Russell <rusty@rustcorp.com.au>
To: Mike Waychison <mikew@google.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: Frank Swiderski <fes@google.com>, Rik van Riel <riel@redhat.com>,
Andrea Arcangeli <aarcange@redhat.com>,
virtualization@lists.linux-foundation.org,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org
Subject: Re: [PATCH] Add a page cache-backed balloon device driver.
Date: Wed, 12 Sep 2012 14:55:08 +0930 [thread overview]
Message-ID: <87ligfdd8r.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CAGTjWtCiqjkR_Ze=0-ebO08+eziz6c8TXLb+O1iiArRQeSE6zw@mail.gmail.com>
Mike Waychison <mikew@google.com> writes:
> On Mon, Sep 10, 2012 at 3:59 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
>> On Mon, Sep 10, 2012 at 01:37:06PM -0400, Mike Waychison wrote:
>>> On Mon, Sep 10, 2012 at 5:05 AM, Michael S. Tsirkin <mst@redhat.com> wrote:
>>> > On Tue, Jun 26, 2012 at 01:32:58PM -0700, 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>
>>>
>>> Hi Michael,
>>>
>>> I'm very sorry that Frank and I have been silent on these threads.
>>> I've been out of the office and Frank has been been swamped :)
>>>
>>> I'll take a stab at answering some of your questions below, and
>>> hopefully we can end up on the same page.
Hi Mike, Frank, Michael,
Thanks for the explanation and discussion. I like that this
implementation is more dynamic: the guest can use more pages for a while
(and the balloon kthread will furiously start trying to grab more pages
to give back). This part is a completely reasonable implementation, and
more sophisticated that what we have.
It doesn't *quite* meet the spec, because we don't notify the host when
we pull a page from the balloon, but I think that is quite possible. If
this is a performance waster, we should add a "SILENT_DEFLATE" feature
to tell the driver that it doesn't need to, though we should stll
support the !SILENT_DEFLATE case.
And Michael: thanks again for doing the heavy lifting on this!
Cheers,
Rusty.
prev parent reply other threads:[~2012-09-12 6:34 UTC|newest]
Thread overview: 30+ 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 21:31 ` Frank Swiderski
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-26 21:47 ` Michael S. Tsirkin
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 [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=87ligfdd8r.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox