virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Adam Litke <alitke@redhat.com>
Cc: msivak@redhat.com, Daniel Kiper <daniel.kiper@oracle.com>,
	virtualization@lists.linuxfoundation.org, dfediuck@redhat.com,
	Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: Users of ballooning, please come forth!
Date: Fri, 21 Feb 2014 11:58:09 +1030	[thread overview]
Message-ID: <87txbt8dau.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20140220131706.GB18487@redhat.com>

Adam Litke <alitke@redhat.com> writes:
> On 20/02/14 14:53 +1030, Rusty Russell wrote:
>>I think we're headed to the same destination here; the variant which I
>>came up with (and suggested to Daniel and Luiz, CC'd) is similar: the
>>guest self-balloons, giving up pages when it can, but the host sets a
>>ceiling.
>>
>>This way, if the host really needs to set a limit, it can: a disobedient
>>guest will start paging.  But generally, a guest should use its
>>judgement to balloon its own pages as it can (below the ceiling).
>
> It sounds similar but it sounds like you are suggesting one limit
> value and I am suggesting two.  Your ceiling value sounds like a soft
> limit on total guest memory (aka minimum balloon size).  This is the
> more important limit of the two I have suggested.  Do you think it's
> also worthwhile to have a maximum balloon size (floor value) to keep
> the allowable balloon size between two points?

It's a little simpler to have a ceiling only.

And if everyone (guests and host) are feeling like they have plenty of
memory, it's probably best sitting in the host.

1) It can quickly go to a guest if necessary.
2) The host could coalesce/shuffle memory.
3) The host could turn off RAM to save power.

Cheers,
Rusty.

      parent reply	other threads:[~2014-02-21  2:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11  6:01 Users of ballooning, please come forth! Rusty Russell
2014-02-19 14:49 ` Adam Litke
2014-02-20  4:23   ` Rusty Russell
2014-02-20 13:17     ` Adam Litke
2014-02-20 13:42       ` Luiz Capitulino
2014-02-21  1:28       ` 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=87txbt8dau.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=alitke@redhat.com \
    --cc=daniel.kiper@oracle.com \
    --cc=dfediuck@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=msivak@redhat.com \
    --cc=virtualization@lists.linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).