All of lore.kernel.org
 help / color / mirror / Atom feed
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 03/14]: libxenlight, 8MB slack for PV domains
Date: Tue, 01 Dec 2009 09:15:19 -0500	[thread overview]
Message-ID: <4B1524F7.30905@lagarcavilla.com> (raw)
In-Reply-To: <20091201063440.GA15810@gwig.uk.xensource.com>

The 8mb slack is not real memory allocated. It's extra room in the pfn 
space. The memory's domain allocation remains capped at the amount 
intended. I haven't seen anyone in xen-devel for five years needing more 
slack than that ') Particularly since the network rx flipping path 
stopped being the default
Andres
Vincent Hanquez wrote:
> On Mon, Nov 30, 2009 at 07:10:58PM +0000, Andres Lagar-Cavilla wrote:
>   
>> Contemplate 8MB of slack for PV domains, since they
>> do ballooning (or flipping network rx) and need
>> some extra room in their pfn space.
>>
>> Signed-off-by: Andres Lagar-Cavilla <andres@lagarcavilla.com>
>>     
>
> this probably should be in the build structure. not magically adding 8 mb without the
> toolstack knowing, otherwise no toolstack can provide more or less slacks on a
> per domain basis. And it make precise memory handling a nightmare, and thus
> dynamic memory handling too. in some way this parameter is just like the
> shadow_memory one in the hvm build structure.
>
>   

      reply	other threads:[~2009-12-01 14:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 19:10 [PATCH 03/14]: libxenlight, 8MB slack for PV domains Andres Lagar-Cavilla
2009-12-01  6:34 ` Vincent Hanquez
2009-12-01 14:15   ` Andres Lagar-Cavilla [this message]

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=4B1524F7.30905@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.