WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] [PATCH][Take 2] Sysfs Interface for balloon driver

To: "Satoshi Uchida" <s-uchida@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH][Take 2] Sysfs Interface for balloon driver
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Mon, 25 Sep 2006 13:10:54 +0100
Delivery-date: Mon, 25 Sep 2006 05:11:32 -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>
References: <002601c6e098$f632c110$4c87380a@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbgmPYKO+6dSF7KTWykOVHhL8ByPQAAfPLA
Thread-topic: [Xen-devel] [PATCH][Take 2] Sysfs Interface for balloon driver
> This patch provides a sysfs interface for the balloon driver (Take 2).
> Example outputs of the sysfs interface of the balloon driver are as
> follows:
> 
>  Example 1.  Show each information
> 
>   [root@Dom0 ~]# ls /sys/devices/system/memory/memory0/
>   balloon_high  current_pages  hard_limit
>   balloon_low   driver_pages   target_pages

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.

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).

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

Thanks,
Ian

>   [root@Dom0 ~]# cat /sys/devices/system/memory/memory0/current_pages
>     262144
>   [root@Dom0 ~]# cat /sys/devices/system/memory/memory0/target_pages
>     262144
>   [root@Dom0 ~]# cat /sys/devices/system/memory/memory0/balloon_high
>          0
>   [root@Dom0 ~]# cat /sys/devices/system/memory/memory0/balloon_low
>     509952
>   [root@Dom0 ~]# cat /sys/devices/system/memory/memory0/hard_limit
>   ???
>   [root@Dom0 ~]# cat /sys/devices/system/memory/memory0/driver_pages
>       1024
> 
>  Example 2. Set memory size of a domain
> 
>   [root@Dom0 ~]# echo 1024M >
> /sys/devices/system/memory/memory0/target_pages
>   [root@Dom0 ~]# cat /sys/devices/system/memory/memory0/target_pages
>    1048576
>   [root@Dom0 ~]# cat /sys/devices/system/memory/memory0/current_pages
>     758192
>   [root@Dom0 ~]# cat /sys/devices/system/memory/memory0/hard_limit
>     758192
>   [root@Dom0 ~]# cat /sys/devices/system/memory/memory0/driver_pages
>       1024
> 
> 
> Regards
> Satoshi UCHIDA
>    NEC Corporation, Japan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel