From: Keir Fraser Subject: Re: [PATCH] linux/balloon: don't allow ballooningdowna domain below a reasonable limit Date: Thu, 01 May 2008 08:01:59 +0100 Message-ID: References: <20080430174950187.00000002360@djm-pc> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20080430174950187.00000002360@djm-pc> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "dan.magenheimer@oracle.com" , Jan Beulich Cc: Ky Srinivasan , "xen-devel@lists.xensource.com" , KurtGarloff List-Id: xen-devel@lists.xenproject.org On 1/5/08 00:49, "Dan Magenheimer" wrote: > I'm experimenting now with an algorithm which starts > with vm_committed_space* and adds back in a (for > now) fixed fraction of 1/32 of total physical > memory. > > Dan > > * Alas this is not exported so won't work in a module, > but it seems to be a pretty good estimator of active > virtual memory usage. Can't vm_committed_space grow *bigger* than available memory when using swap? It may indicate the 'static' demand for memory (in terms of requested allocations so far) but we're interested in dynamic demand (how much of that allocated memory is actually used), which afaics vm_committed_space doesn't appear very useful for. Some indication of paging churn, or average age of pages in memory, or something like that, would seem more useful (albeit arbitrarily harder to work out from within the balloon driver!). Maybe I'm missing something. I've only had a quick look at usage of vm_committed_space. -- Keir