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

[Xen-devel] Re: [PATCH 3/7] libxenlight resend: 8mb physmap slack for pv

To: Vincent Hanquez <vincent.hanquez@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 3/7] libxenlight resend: 8mb physmap slack for pv domains
From: Andres Lagar-Cavilla <andres@xxxxxxxxxxxxxxxx>
Date: Thu, 03 Dec 2009 11:49:44 -0500
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Thu, 03 Dec 2009 08:50:06 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20091203165010.GA16701@xxxxxxxxxxxxxxxxxxxxx>
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: <4B16AB3F.4000809@xxxxxxxxxxxxxxxx> <20091203161013.GB16684@xxxxxxxxxxxxxxxxxxxxx> <4B17E16E.3000302@xxxxxxxxxxxxxxxx> <20091203165010.GA16701@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.23 (X11/20090817)
The p2m is *inside* the pv guest. So the only "impact" is infinitesimally increasing the chances of an oom_killer going postal. This is not for hvm's with external p2m's
Andres
Vincent Hanquez wrote:
On Thu, Dec 03, 2009 at 04:03:58PM +0000, Andres Lagar-Cavilla wrote:
No extra memory is being allocated at all in any way. The only impact is a wee bit larger p2m table.

yes, and that consumes memory. not sure that's one we care about in XCP,
but as a rule to not make any exceptions, i want the amount to be explicetly
tracked.

note that also, whilst xend didn't have much done regarding memory stuff,
xapi (the ocaml daemon running instead of xend in XCP) have load of changes
regarding how we allocate and track things.



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