From: Andres Lagar-Cavilla <andres@lagarcavilla.com>
To: Vincent Hanquez <vincent.hanquez@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH 3/7] libxenlight resend: 8mb physmap slack for pv domains
Date: Thu, 03 Dec 2009 11:49:44 -0500 [thread overview]
Message-ID: <4B17EC28.8030100@lagarcavilla.com> (raw)
In-Reply-To: <20091203165010.GA16701@gwig.uk.xensource.com>
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.
>
>
next prev parent reply other threads:[~2009-12-03 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 18:00 [PATCH 3/7] libxenlight resend: 8mb physmap slack for pv domains Andres Lagar-Cavilla
2009-12-03 12:34 ` Stefano Stabellini
2009-12-03 16:10 ` Vincent Hanquez
2009-12-03 16:03 ` Andres Lagar-Cavilla
2009-12-03 16:50 ` Vincent Hanquez
2009-12-03 16:49 ` Andres Lagar-Cavilla [this message]
2009-12-03 17:05 ` [PATCH 3/7] libxenlight meta-resend: " Andres Lagar-Cavilla
2009-12-04 7:12 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2009-12-03 15:55 [PATCH 3/7] libxenlight resend: 8mb " andres
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B17EC28.8030100@lagarcavilla.com \
--to=andres@lagarcavilla.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=vincent.hanquez@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.