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: Jan Beulich <JBeulich@xxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>
Subject: RE: [Xen-devel] pre-reservation of memory for domain creation
From: "Xu, Dongxiao" <dongxiao.xu@xxxxxxxxx>
Date: Thu, 14 Jan 2010 17:09:20 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 14 Jan 2010 01:09:48 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B4EEB300200007800029E45@xxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqU+ALKTloQ/udjQy2+8G+R/LtDwwAADx2A
Thread-topic: [Xen-devel] pre-reservation of memory for domain creation
Jan Beulich wrote:
>>>> "Xu, Dongxiao" <dongxiao.xu@xxxxxxxxx> 14.01.10 08:19 >>>
>>    Currently guest initialization process in xend
>> (XendDomainInfo.py) is: 
>> 
>>    _constructDomain() --> domain_create() --> domain_max_vcpus() ...
>>    --> _initDomain() --> shadow_mem_control() ...
> 
> While the patch certainly matches what I had in mind, with this
> sequence 
> it is clear that the tools still will need adjustment: The full
> ballooning only happens from _initDomain(), and hence the
> pre-reservation (from _constructDomain) of 4Mb would still be too
> small for large vCPU counts. 

The pre-reservation of memory size should be no relationship with vcpu number. 
As vcpu hasn't been initialized at that point. On vcpu initialization, the 
patch has ballooned the shadow size to 128 pages per vcpu. Did you find some 
piece of code that use the pre-reserved memory to allocate vcpu-related memory? 

Thanks!
Dongxiao

> 
> I wonder though what all this memory is needed for before the domain
> (not to speak of secondary CPUs) actually gets started. If that could
> be 
> got under control, tools side adjustment would not be necessary. Tim?
> 
> Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>