From: Paul Larson <plars@linuxtestproject.org>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: lowest limit for balloon?
Date: Mon, 18 Jul 2005 10:55:39 -0500 [thread overview]
Message-ID: <1121702139.21890.30.camel@localhost.localdomain> (raw)
In-Reply-To: <3f5bbf036ea5085e752235233f8760dd@cl.cam.ac.uk>
[-- Attachment #1.1: Type: text/plain, Size: 921 bytes --]
On Mon, 2005-07-18 at 13:38 +0100, Keir Fraser wrote:
> It's probably a job for higher-level management tools. Maybe a safety
> catch should be placed on 'xm balloon', but the intra-VM
> /proc/xen/balloon interface is definitely not intended for the casual
> user.
I still think /proc/xen/balloon makes it far too easy to shoot yourself
in the foot, even for the non-casual user. Simply forgetting to leave
the units off the end of an echo can bring your domain (even dom0) to a
screeching halt.
Such as doing:
echo 200000 > /proc/xen/balloon
instead of:
echo 200000K > /proc/xen/balloon.
I know that it's really difficult to determine how low is too low.
Could I recommend a small interface change though, that would force the
user to always specify units {B,K,M,...}? That might help a little at
least.
--
Thanks,
Paul Larson
plars@linuxtestproject.org
http://www.linuxtestproject.org
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2005-07-18 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 10:57 lowest limit for balloon? aq
2005-07-18 12:38 ` Keir Fraser
2005-07-18 15:44 ` aq
2005-07-18 15:55 ` Paul Larson [this message]
2005-07-18 16:12 ` Mark Williamson
2005-07-18 16:47 ` Keir Fraser
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=1121702139.21890.30.camel@localhost.localdomain \
--to=plars@linuxtestproject.org \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.