From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: [PATCH] RFC: initial libxl support for xenpaging Date: Mon, 20 Feb 2012 16:38:41 +0100 Message-ID: <20120220153841.GB14062@aepfle.de> References: <1329490712.3131.97.camel@zakaz.uk.xensource.com> <20120217152443.GA16995@aepfle.de> <1329492796.3131.104.camel@zakaz.uk.xensource.com> <20120217154346.GA19731@aepfle.de> <1329494069.3131.109.camel@zakaz.uk.xensource.com> <20120217160341.GA22266@aepfle.de> <1329496998.3131.131.camel@zakaz.uk.xensource.com> <20120220111230.GA5856@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: George Dunlap Cc: "xen-devel@lists.xensource.com" , Ian Campbell List-Id: xen-devel@lists.xenproject.org On Mon, Feb 20, George Dunlap wrote: > xl mem-set domain M > xenpaging off: Set balloon target to M > xenpaging on: Set paging target to M > xenpaging delay: Set balloon target to M, and wait for actual memory > to reach M. If it hasn't reached it by $paging_delay seconds, set > balloon target to M. The tristate instead of a boolean is not really needed as well. Right now a reduction of the balloon target depends on how fast the guests balloon driver can claim memory from the guest OS. This means it could take an infinite amount of time to reach the requested target. With paging the request to reduce the "footprint" can be reached as fast as xenpaging can page-out gfns (and page-in busy gfns). So having a delay or not seems to depend on how mem-set is supposed to react, either now or at an (kind of) undefined time in the future. If "now" is not the desired mode then xenpaging can slowly work toward a new lower target by calling its evict_pages() with low numbers and and an adjustable delay between calls. Olaf