From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: RE: Re: Xenheap disappearance: (was: xen_phys_startfor32b) Date: Mon, 19 Jan 2009 08:22:33 +0000 Message-ID: <49744659.76E4.0078.0@novell.com> References: <49704F4D.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: 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: Keir Fraser , Dan Magenheimer Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >>> Dan Magenheimer 17.01.09 00:16 >>> >I'm not sure what you are getting at. Are you saying that >creating a domain takes (big)MB from domheap, then later >(little)KB from xenheap, and if we combine domheap and xenheap, >the tools might launch a domain when available memory is >greater than (big)MB but smaller than (big)MB+(small)KB, >and that will result in the tools thinking the domain >can launch but it won't? I suppose that's possible, Yes, that's what I'm trying to say. And I think it's rather likely to = happen, as I frequently see systems with completely empty domain heaps. >but exceedingly unlikely. And I think Keir's plan will >have the same problem. Sounds like a tools bug, not a >reason to avoid modernizing Xen memory management. No, I wasn't making the point to ask for not doing improvements in Xen - in fact, it's been for a long time that I've been raising the scalability = issue of the limited Xen heap. I was just trying to point out that the Xen = change *must* be accompanied by a tools change in order to be usable in other than development/test environments. Jan