From: andres@lagarcavilla.com
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Vincent Hanquez <vincent.hanquez@eu.citrix.com>
Subject: Re: [PATCH 3/7] libxenlight resend: 8mb physmap slack for pv domains
Date: Thu, 3 Dec 2009 07:55:38 -0800 [thread overview]
Message-ID: <6e2eaf13d39969c10a1e4ac628e052d1.squirrel@webmail.lagarcavilla.com> (raw)
I can cut the patch that way, however ... a fixed 8mb slack for pv domains
has been in place at least since Dec 08 2006, changeset 12803. No one
seems to have needed an optionally larger or smaller slack ;)
Andres
> On Wed, 2 Dec 2009, 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.
>>
>> Note that this does not allocate any extra memory
>> to the domain, it simply extends the physmap with
>> some extra room for "bounce bufffering back" pfn's
>> that are yielded to dom0.
>>
>
> Vincent is probably traveling and for this reason he didn't reply to
> your last email about this patch.
>
> I don't think he would be happy until you move the 8mb slack into a
> configurable parameter in libxl_domain_build_info, defaulted to 8mb in
> init_build_info.
>
>
next reply other threads:[~2009-12-03 15:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 15:55 andres [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=6e2eaf13d39969c10a1e4ac628e052d1.squirrel@webmail.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.