From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andres Lagar-Cavilla Subject: Re: [PATCH 3/7] libxenlight resend: 8mb physmap slack for pv domains Date: Thu, 03 Dec 2009 11:49:44 -0500 Message-ID: <4B17EC28.8030100@lagarcavilla.com> References: <4B16AB3F.4000809@lagarcavilla.com> <20091203161013.GB16684@gwig.uk.xensource.com> <4B17E16E.3000302@lagarcavilla.com> <20091203165010.GA16701@gwig.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20091203165010.GA16701@gwig.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Vincent Hanquez Cc: "xen-devel@lists.xensource.com" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org 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. > >