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] [PATCH][Take 2] Sysfs Interface for balloon driver

To: "'Ian Pratt'" <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH][Take 2] Sysfs Interface for balloon driver
From: "Satoshi Uchida" <s-uchida@xxxxxxxxxxxxx>
Date: Tue, 26 Sep 2006 17:29:52 +0900
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 26 Sep 2006 01:35:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <3AAA99889D105740BE010EB6D5A5A3B202A36F@xxxxxxxxxxxxxxxxxxxxxxxxxx>
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: AcbgmPYKO+6dSF7KTWykOVHhL8ByPQAAfPLAACfBAXA=
 Ti, Ian

> These names are a bit misleading, confusing pages and KB.
> Perhaps go for everything in KB, and have a '_KB' post fix to 
> all the names e.g. 'current_KB'.


> Does anyone actually use balloon_low and _high? At the very 
> least they should be renamed, possibly put under an info sub 
> directory.

Works the renaming.

However, Does it needs to put under an info sub directory?
Because both of current pages and high/low memory are information and show 
states of memory.
Perhaps, The parameter is only target pages.

> Since linux currently doesn't know the hard limit, perhaps 
> best to remove this node.

The hard limit show limitation after ballooning process.
The hard limit currently is initialized before ballooning process, so 
no have its significance.
But, at least, anyone know the limitaion by it when ballooning process.
Maybe may it be left?

> Something that would be good to export via sysfs is the 
> maximum amount of memory the guest could have (for guests 
> that can't expand their page array i.e. all current guests).

What is this means?
Should information export the limitaion handled within linux? (i.e by mem 
or the limitation controlled at hypervisor (mem-max)?

Satoshi UCHIDA

Xen-devel mailing list