xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Christoph Egger <Christoph.Egger@amd.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Cc: Tim Deegan <Tim.Deegan@eu.citrix.com>
Subject: Re: [PATCH 0/15] Nested Virtualization: Overview
Date: Fri, 4 Jun 2010 11:00:35 +0100	[thread overview]
Message-ID: <C82E8D53.16AB0%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <201006041144.54352.Christoph.Egger@amd.com>

On 04/06/2010 10:44, "Christoph Egger" <Christoph.Egger@amd.com> wrote:

> @Tim: On last review you asked about the use of MAX_NESTEDP2M.
> Actually, this is a hack. What I really need in Xen is a generic pool
> implementation like this
> http://netbsd.gw.com/cgi-bin/man-cgi?pool+9+NetBSD-current
> and this
> http://netbsd.gw.com/cgi-bin/man-cgi?pool_cache+9+NetBSD-current
> In NetBSD, pool_cache(9) is implemented on top of pool(9).
> 
> IMO, xmalloc/xfree, machine check and cpupool code should also
> use pool_cache(9) in Xen instead of having their own versions.
> Can we take the pool/pool_cache code from NetBSD ?

I'd hope we can really manage without such a mechanism. At least, we'd need
a darn good reason for it, and to have rejected simpler alternative
solutions. I know some OSes have such a concept so that paging code doesn't
deadlock. I can't immediately guess why we'd need it in Xen.

And does pool_cache have much relationship to cpupool, except both have
"pool" in their name? :-)

 -- Keir

      reply	other threads:[~2010-06-04 10:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03 16:02 [PATCH 0/15] Nested Virtualization: Overview Christoph Egger
2010-06-03 17:16 ` Keir Fraser
2010-06-03 17:52   ` Keir Fraser
2010-06-04  9:44     ` Christoph Egger
2010-06-04 10:00       ` Keir Fraser [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=C82E8D53.16AB0%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=Christoph.Egger@amd.com \
    --cc=Tim.Deegan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).