[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "Satoshi Uchida" <s-uchida@xxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Tue, 26 Sep 2006 19:26:18 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 26 Sep 2006 11:28:50 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcbgmPYKO+6dSF7KTWykOVHhL8ByPQAAfPLAACfBAXAAF8OesA==
  • Thread-topic: [Xen-devel] [PATCH][Take 2] Sysfs Interface for balloon driver

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

target_pages (or rather target_KB) is the only thing you can adjust.
 
> > 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 option)
> or the limitation controlled at hypervisor (mem-max)?

I guess this is the total of the current memory and the memory in the
high and low balloons.

Ian

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.