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


[Xen-devel] Re: [PATCH][BALLOON] Fix minimum target

On 27 May 2006, at 06:18, Puthiyaparambil, Aravindh wrote:

We tried a few experiments with your 2% patch. We found that 2% is not
good enough. The magic numbers seem to be 3% for DomUs and 5% for Dom0.
Any idea why the difference in percentages?

The minimum should probably include a fixed-size base value, plus some percentage of maximum possible memory size. The patch I applied does not include the fixed-size base value as it isn't obvious what to set it to.

The percentage you need (5%) for domain0 may appear bigger for a few reasons: * There's a bigger static allocation of memory in domain0, independent of maximum memory size * You allocate less initial memory to domain0, so the fixed-size reserved memory is a bigger proprtion of total reserved memory.

What happens if you set the min to 16MB + 2% of max-mem?

 -- Keir

If this patch is fine by you, could you please apply to both
xen-unstable and xen-3.0-testing?

Xen-devel mailing list

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