From: Luiz Capitulino <lcapitulino@redhat.com>
To: Anton Vorontsov <anton.vorontsov@linaro.org>
Cc: Michal Hocko <mhocko@suse.cz>,
aquini@redhat.com, mst@redhat.com, linux-kernel@vger.kernel.org,
David Rientjes <rientjes@google.com>,
qemu-devel@nongnu.org, Glauber Costa <glommer@parallels.com>,
Pekka Enberg <penberg@kernel.org>,
linux-mm@kvack.org, John Stultz <john.stultz@linaro.org>,
Mel Gorman <mgorman@suse.de>,
agl@us.ibm.com, amit.shah@redhat.com, kirill@shutemov.name,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Qemu-devel] [RFC 3/3] virtio-balloon: add auto-ballooning support
Date: Wed, 19 Dec 2012 09:30:39 -0200 [thread overview]
Message-ID: <20121219093039.51831f6f@doriath.home> (raw)
In-Reply-To: <20121218225330.GA28297@lizard.mcd00620.sjc.wayport.net>
On Tue, 18 Dec 2012 14:53:30 -0800
Anton Vorontsov <anton.vorontsov@linaro.org> wrote:
> Hello Luiz,
>
> On Tue, Dec 18, 2012 at 06:16:55PM -0200, Luiz Capitulino wrote:
> > The auto-ballooning feature automatically performs balloon inflate
> > or deflate based on host and guest memory pressure. This can help to
> > avoid swapping or worse in both, host and guest.
> >
> > Auto-ballooning has a host and a guest part. The host performs
> > automatic inflate by requesting the guest to inflate its balloon
> > when the host is facing memory pressure. The guest performs
> > automatic deflate when it's facing memory pressure itself. It's
> > expected that auto-inflate and auto-deflate will balance each
> > other over time.
> >
> > This commit implements the host side of auto-ballooning.
> >
> > To be notified of host memory pressure, this commit makes use of this
> > kernel API proposal being discussed upstream:
> >
> > http://marc.info/?l=linux-mm&m=135513372205134&w=2
>
> Wow, you're fast! And I'm glad that it works for you, so we have two
> full-featured mempressure cgroup users already.
Thanks, although I think we need more testing to be sure this does what
we want. I mean, the basic mechanics does work, but my testing has been
very light so far.
> Even though it is a qemu patch, I think we should Cc linux-mm folks on it,
> just to let them know the great news.
I'll do it next time.
next prev parent reply other threads:[~2012-12-19 11:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 20:16 [Qemu-devel] [RFC 0/3] auto-ballooning prototype (host part) Luiz Capitulino
2012-12-18 20:16 ` [Qemu-devel] [RFC 1/3] virtio-balloon: add guest_get_actual_ram() Luiz Capitulino
2012-12-18 20:16 ` [Qemu-devel] [RFC 2/3] virtio-balloon: add virtio_balloon_conf skeleton Luiz Capitulino
2012-12-18 20:16 ` [Qemu-devel] [RFC 3/3] virtio-balloon: add auto-ballooning support Luiz Capitulino
2012-12-18 22:53 ` Anton Vorontsov
2012-12-19 11:30 ` Luiz Capitulino [this message]
2012-12-20 5:24 ` Dietmar Maurer
2012-12-22 21:45 ` Luiz Capitulino
2013-01-11 20:32 ` Amit Shah
2013-01-14 11:58 ` Luiz Capitulino
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=20121219093039.51831f6f@doriath.home \
--to=lcapitulino@redhat.com \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=amit.shah@redhat.com \
--cc=anton.vorontsov@linaro.org \
--cc=aquini@redhat.com \
--cc=glommer@parallels.com \
--cc=john.stultz@linaro.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=mst@redhat.com \
--cc=penberg@kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=rientjes@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).