From: "Jan Beulich" <JBeulich@novell.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>,
Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Konrad Wilk <konrad.wilk@oracle.com>,
Xen-devel@lists.xensource.com, Daniel Kiper <dkiper@net-space.pl>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: RE: Ballooning up
Date: Tue, 14 Sep 2010 09:41:11 +0100 [thread overview]
Message-ID: <4C8F51470200007800015EEA@vpn.id2.novell.com> (raw)
In-Reply-To: <4C8EAB0E.7040407@goop.org>
>>> On 14.09.10 at 00:51, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> I guess there are three options:
>
> 1. add a "xen_maxmem" (or something) kernel parameter to override
> space specified in the E820 table
Isn't that what the (native) "mem=" option is intended for?
> 2. ignore E820 if its a privileged domain
I think this upper limit specified by the machine E820 should be
ignored here, and an option (as per 1.) should be available.
> 3. only allow extra memory up to a certain ratio of the base memory
> (8x? 16x? 32x?)
Enforcing a sane upper limit of the ratio (we use 32x currently)
seems like a reasonable thing to do in any case.
Jan
next prev parent reply other threads:[~2010-09-14 8:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 8:36 Ballooning up Jeremy Fitzhardinge
[not found] ` <54eebb3a-f539-43be-8134-a969a4f671c4@default4C8EAB0E.7040407@goop.org>
2010-09-07 10:14 ` Ian Campbell
2010-09-07 13:26 ` Jeremy Fitzhardinge
2010-09-07 14:10 ` Ian Campbell
2010-09-15 21:47 ` Dan Magenheimer
2010-09-15 22:41 ` Jeremy Fitzhardinge
2010-09-13 21:17 ` Dan Magenheimer
2010-09-13 21:39 ` Dan Magenheimer
2010-09-13 23:06 ` Jeremy Fitzhardinge
2010-09-13 22:51 ` Jeremy Fitzhardinge
2010-09-14 0:22 ` Dan Magenheimer
2010-09-14 0:46 ` Jeremy Fitzhardinge
2010-09-14 15:06 ` Dan Magenheimer
2010-09-14 22:05 ` Jeremy Fitzhardinge
2010-09-15 7:13 ` Ian Campbell
2010-09-14 8:41 ` Jan Beulich [this message]
2010-09-14 16:35 ` Jeremy Fitzhardinge
2010-09-14 9:07 ` Ian Campbell
2010-09-14 16:42 ` Jeremy Fitzhardinge
2010-09-15 7:10 ` Ian Campbell
2010-09-15 17:29 ` Jeremy Fitzhardinge
2010-09-15 18:06 ` Dan Magenheimer
2010-09-15 20:29 ` Jeremy Fitzhardinge
2010-09-14 8:34 ` Ian Campbell
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=4C8F51470200007800015EEA@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=Xen-devel@lists.xensource.com \
--cc=dan.magenheimer@oracle.com \
--cc=dkiper@net-space.pl \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=stefano.stabellini@eu.citrix.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.