From: "Jan Beulich" Subject: RE: [PATCH] linux/balloon: don't allow ballooningdowna domain below a reasonable limit Date: Wed, 30 Apr 2008 07:29:22 +0100 Message-ID: <48182DE2.76E4.0078.0@novell.com> References: <47F9E4FD.76E4.0078.0@novell.com> <20080429123518578.00000002360@djm-pc> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20080429123518578.00000002360@djm-pc> Content-Disposition: inline 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" Cc: Ky Srinivasan , "xen-devel@lists.xensource.com" , Keir Fraser , KurtGarloff List-Id: xen-devel@lists.xenproject.org >>> "Dan Magenheimer" 29.04.08 20:35 >>> >I made some actual measurements of the results of this algorithm >(on a RHEL5u1-32bit guest). > >memory=3D Minimum >128 75776kB >256 108544kB >512 173056kB >1024 238592kB > >This corresponds to expected values in the source comment >However, I wonder if the algorithm is probably too >conservative for large(r) memory domains. With >a light load (i.e. continuously compiling Xen), >memory utilization rarely exceeds 72MB, regardless >of the max memory (at least in the above tested values). Sure, this was (in different wording) also stated in the comment that came with the patch. A more precise estimate would certainly be welcome, but I'm afraid is going to come with a much higher (complexity) price tag. Unless you have something simple and obvious in mind that we simply didn't spot... Jan