From: "Dan Magenheimer" Subject: RE: [PATCH] linux/balloon: don't allow ballooningdowna domain below a reasonable limit Date: Thu, 1 May 2008 10:59:58 -0600 Message-ID: <20080501105958328.00000002360@djm-pc> References: <20080501173644.50786041@core> Reply-To: "dan.magenheimer@oracle.com" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20080501173644.50786041@core> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Alan Cox , Keir Fraser Cc: Ky Srinivasan , "xen-devel@lists.xensource.com" , KurtGarloff , Jan Beulich List-Id: xen-devel@lists.xenproject.org > It doesn't measure memory or total virtual commitment. Hmm... in my experiments, it seems to do exactly that. I wrote a simple "eatmem" program that uses a random amount of memory (writing to the first byte in each page) for a random amount of time (printing out the random values), and watched Committed_AS in /proc/meminfo and it seems to track well. > -----Original Message----- > From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk] > Sent: Thursday, May 01, 2008 10:37 AM > To: Keir Fraser > Cc: dan.magenheimer@oracle.com; Jan Beulich; Ky Srinivasan; > xen-devel@lists.xensource.com; KurtGarloff > Subject: Re: [Xen-devel] [PATCH] linux/balloon: don't allow > ballooningdowna domain below a reasonable limit > = > = > > Can't vm_committed_space grow *bigger* than available = > memory when using > > swap? It may indicate the 'static' demand for memory > = > vm_committed_space measures address space commitment for anonymous > objects. It doesn't measure memory or total virtual commitment. > = > Alan >