This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] RE: Ballooning up

To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx>
Subject: Re: [Xen-devel] RE: Ballooning up
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Tue, 14 Sep 2010 09:41:11 +0100
Cc: Konrad Wilk <konrad.wilk@xxxxxxxxxx>, Xen-devel@xxxxxxxxxxxxxxxxxxx, Daniel Kiper <dkiper@xxxxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Delivery-date: Tue, 14 Sep 2010 01:41:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C8EAB0E.7040407@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4C85F973.2030007@xxxxxxxx> <54eebb3a-f539-43be-8134-a969a4f671c4@default> <4C8EAB0E.7040407@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
 >>> On 14.09.10 at 00:51, Jeremy Fitzhardinge <jeremy@xxxxxxxx> 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.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>