All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
	Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: New heap API and scrubbing
Date: Tue, 10 Feb 2009 08:22:27 +0000	[thread overview]
Message-ID: <49914753.76E4.0078.0@novell.com> (raw)
In-Reply-To: <f4d380ca-b23a-4a6b-adb9-19e9016569eb@default>

>>> Dan Magenheimer <dan.magenheimer@oracle.com> 10.02.09 01:24 >>>
>So in the new (soon-to-be 3.4) heap API, are
>
>alloc_domheap_pages(NULL,order,flags)
>
>and
>
>alloc_xenheap_pages(order,flags)
>
>synonomous on 64-bit hypervisors?  I.e. they
>are allocating from the same pool of pages?

I thought thee was a small difference, but in looking at the code it seems
there isn't at present. The difference I though would be there was that
alloc_xenheap_pages() should be allowed to access MEMZONE_XEN,
while alloc_domheap_pages() should only start allocating at MEMZONE_XEN+1.
That way, by default Xen heap allocations would eat from the domain heap,
but if that's empty would be allowed to fall back to the low memory portion.
Keir?

>And if so are the matching free routines
>synonomous?

No, because PGC_xen_heap must be cleared on pages allocated through
alloc_xenheap_pages().

Jan

  parent reply	other threads:[~2009-02-10  8:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10  0:24 New heap API and scrubbing Dan Magenheimer
2009-02-10  5:19 ` Keir Fraser
2009-02-10  8:22 ` Jan Beulich [this message]
2009-02-10  8:44   ` Keir Fraser
2009-02-10 22:53 ` Dan Magenheimer
2009-02-11  7:58   ` Keir Fraser
2009-02-11 14:20     ` Dan Magenheimer

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=49914753.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=keir.fraser@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.