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] [PATCH][BALLOON] Fix minimum target

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH][BALLOON] Fix minimum target
From: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Date: Sat, 27 May 2006 01:18:33 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Carb, Brian A" <Brian.Carb@xxxxxxxxxx>
Delivery-date: Fri, 26 May 2006 22:19:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcaBTP/GxgbO8k30QtO+t2cnxbetYg==
Thread-topic: [PATCH][BALLOON] Fix minimum target

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?

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

Aravindh Puthiyaparambil 
Xen Development Team
Unisys, Tredyffrin PA


Do not allow target to be set below 3% of maximum memory for DomUs and
5% for Dom0.
Signed-off-by: Aravindh Puthiyaparambil

Attachment: balloon_percent-unstable.patch
Description: balloon_percent-unstable.patch

Attachment: balloon_percent-testing.patch
Description: balloon_percent-testing.patch

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>