From: Rik van Riel <riel@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, aquini@redhat.com, amit.shah@redhat.com,
anton@enomsg.org
Subject: Re: [RFC 2/2] virtio_balloon: auto-ballooning support
Date: Mon, 13 May 2013 15:10:19 -0400 [thread overview]
Message-ID: <51913A9B.2030807@redhat.com> (raw)
In-Reply-To: <20130513153513.GA4981@redhat.com>
On 05/13/2013 11:35 AM, Michael S. Tsirkin wrote:
> On Mon, May 13, 2013 at 11:22:58AM -0400, Rik van Riel wrote:
>> I believe the Google patches still included some way for the
>> host to initiate balloon inflation on the guest side, because
>> the guest internal state alone is not enough to see when the
>> host is under memory pressure.
>>
>> I discussed the project with the Google developers in question
>> a little over a year ago, but I do not remember whether their
>> pressure notification went through qemu, or directly from the
>> host kernel to the guest kernel...
>
> So increasing the max number of pages in balloon
> indicates host memory pressure to the guest?
> Fair enough but I wonder whether there's a way to
> make it more explicit in the interface, somehow.
There may be a better way to do this, but I am really not sure
what that would be. What properties would you like to see in
the interface? What kind of behaviour are you looking for?
--
All rights reversed
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-05-13 19:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 14:53 [RFC v2 0/2] virtio_balloon: auto-ballooning support Luiz Capitulino
2013-05-09 14:53 ` [RFC 1/2] virtio_balloon: move balloon_lock mutex to callers Luiz Capitulino
2013-05-09 21:03 ` Rafael Aquini
2013-05-10 12:52 ` Luiz Capitulino
2013-05-09 14:53 ` [RFC 2/2] virtio_balloon: auto-ballooning support Luiz Capitulino
2013-05-09 21:15 ` Rafael Aquini
2013-05-10 13:20 ` Luiz Capitulino
2013-05-10 13:28 ` Luiz Capitulino
2013-05-13 14:34 ` Rafael Aquini
2013-05-13 18:25 ` Luiz Capitulino
2013-05-13 19:02 ` Michael S. Tsirkin
2013-05-13 20:01 ` Luiz Capitulino
2013-05-12 14:30 ` Michael S. Tsirkin
2013-05-12 16:36 ` Rik van Riel
2013-05-12 18:49 ` Michael S. Tsirkin
2013-05-13 15:03 ` Luiz Capitulino
2013-05-13 15:16 ` Michael S. Tsirkin
2013-05-13 15:22 ` Rik van Riel
2013-05-13 15:35 ` Michael S. Tsirkin
2013-05-13 19:10 ` Rik van Riel [this message]
2013-05-13 19:21 ` Michael S. Tsirkin
2013-05-16 20:56 ` [RFC v2 0/2] " Sasha Levin
2013-05-16 21:04 ` 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=51913A9B.2030807@redhat.com \
--to=riel@redhat.com \
--cc=amit.shah@redhat.com \
--cc=anton@enomsg.org \
--cc=aquini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mst@redhat.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).