WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] pre-reservation of memory for domain creation

To: "Dongxiao Xu" <dongxiao.xu@xxxxxxxxx>
Subject: RE: [Xen-devel] pre-reservation of memory for domain creation
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Tue, 09 Feb 2010 09:18:07 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>
Delivery-date: Tue, 09 Feb 2010 01:18:25 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <6CADD16F56BC954D8E28F3836FA7ED711CA70D75F1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4B4CA40C0200007800029657@xxxxxxxxxxxxxxxxxx> <C7724B76.6265%keir.fraser@xxxxxxxxxxxxx> <4B4CAEB9020000780002969A@xxxxxxxxxxxxxxxxxx> <6CADD16F56BC954D8E28F3836FA7ED7112A79326F2@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4B4D8A9402000078000299C3@xxxxxxxxxxxxxxxxxx> <6CADD16F56BC954D8E28F3836FA7ED7112A7932EBF@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4B4EEB300200007800029E45@xxxxxxxxxxxxxxxxxx> <20100114124619.GE30054@xxxxxxxxxxxxxxxxxxxxxxx> <4B70490D020000780002E4AD@xxxxxxxxxxxxxxxxxx> <6CADD16F56BC954D8E28F3836FA7ED711CA70D75F1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> "Xu, Dongxiao" <dongxiao.xu@xxxxxxxxx> 09.02.10 09:02 >>>
>The patch I attached last time could not solve this issue. The reason is
>the same that, at the point when shadow allocates memory for each vcpu,
>xend hasn't ballooned out enough memory. 

This is why I pinged Tim again.

>I discussed this issue within our team, however we could't achieve a
>good solution currently since Chinese New Year vacation will soon start.
>Anyway I made a work-around patch for it, though you may not like it. 

Yes, this is what I don't want to do unless absolutely necessary. At
the risk of unduly repeating myself - ballooning out 4Mb to be able to
allocate 1Mb in 4-page chunks was empirically sufficient (though there
never was a guarantee). Increasing the to-be-allocated and to-be-
ballooned-out amounts by the same factor does not yield the same
confidence that allocation will actually succeed. Hence my goal to
reduce the initial allocation (to be satisfied from the pre-ballooning)
as much as possible. Unfortunately there was no reply from Tim on
that matter so far.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel