From: Rusty Russell <rusty@rustcorp.com.au>
To: virtualization@lists.linux-foundation.org
Subject: Users of ballooning, please come forth!
Date: Tue, 11 Feb 2014 16:31:10 +1030 [thread overview]
Message-ID: <8761om2no9.fsf@rustcorp.com.au> (raw)
Hi all!
We're debating the design of the balloon for the OASIS spec.
Noone likes the current one, but there are fundamental usage pattern
questions which we're fumbling with.
So if you know anyone who is using it in production? If, so, how? In
particular, would you be happy with guests simply giving the host back
whatever memory they can spare (as Xen's self-balloon does)? Or do you
require the host-forcing approach? Comment or email please!
Thanks,
Rusty.
next reply other threads:[~2014-02-11 6:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 6:01 Rusty Russell [this message]
2014-02-19 14:49 ` Users of ballooning, please come forth! 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
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=8761om2no9.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--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;
as well as URLs for NNTP newsgroup(s).