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>
Subject: Re: [Xen-devel] pre-reservation of memory for domain creation
From: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Date: Tue, 9 Feb 2010 13:47:40 +0000
Cc: Dongxiao Xu <dongxiao.xu@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx>
Delivery-date: Tue, 09 Feb 2010 05:47:56 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B7165F1020000780002E726@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: <6CADD16F56BC954D8E28F3836FA7ED7112A79326F2@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4B4D8A9402000078000299C3@xxxxxxxxxxxxxxxxxx> <6CADD16F56BC954D8E28F3836FA7ED7112A7932EBF@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4B4EEB300200007800029E45@xxxxxxxxxxxxxxxxxx> <20100114124619.GE30054@xxxxxxxxxxxxxxxxxxxxxxx> <4B70490D020000780002E4AD@xxxxxxxxxxxxxxxxxx> <20100209103958.GC368@xxxxxxxxxxxxxxxxxxxxxxx> <4B715347020000780002E6DD@xxxxxxxxxxxxxxxxxx> <20100209113454.GF368@xxxxxxxxxxxxxxxxxxxxxxx> <4B7165F1020000780002E726@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
At 12:41 +0000 on 09 Feb (1265719265), Jan Beulich wrote:
> >OK; the early allocation, for a domain with no vcpus and no RAM, is a
> >constant 4 MiB, and just needs to be added to whatever overheads are
> >already being taken into account (domain and vcpu structs, VMCBs, &c).
> 
> The issue is that this used to be 1Mb. Hence the question whether
> in fact it needs to be 4Mb now (which it got increased to when max
> HVM vCPU-s got grown to 128).
> 
> The point here is that on one hand there's no clear picture how
> much memory is really needed before the full shadow allocation
> gets set up, and on the other hand Keir is recalling issues
> resulting from not growing the amount to 4Mb.

Righto.  The change from 1MB to 4MB is not the right fix for those
issues -- instead, Xend ought to set the shadow memory allocation before
it allocates vcpus.

Tim

-- 
Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, XenServer Engineering
Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

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