All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Daniel Magenheimer <dan.magenheimer@oracle.com>,
	xen-devel mailing list <xen-devel@lists.xensource.com>
Subject: Re: [PATCH][RFC] sub-page anonymous domain memory allocator
Date: Fri, 29 Aug 2008 19:18:43 +0100	[thread overview]
Message-ID: <C4DDFC13.1CA2C%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <2dac25a9-af17-445b-8a45-e055d8ebf71c@default>

You can more simply just have the existing xmalloc interface go at
alloc_domheap_pages(NULL) on x86/64. That would just need some #ifdef
abstraction within xmalloc.c.

 -- Keir

On 29/8/08 18:12, "Daniel Magenheimer" <dan.magenheimer@oracle.com> wrote:

> This patch uses some #define-and-Makefile trickery to completely
> leverage common/xmalloc.c to provide a sub-page memory
> allocator that takes memory from anonymous domain heap instead
> of xen heap.  Note that it is useful only on a 64-bit hypervisor.
> (Some other #define trickery can be used so that 32-bit
> hypervisor uses xenheap and 64-bit hypervisor uses adheap.)
> 
> Keir says that a goal for 3.4 is to combine xen heap and
> domain heap on 64-bit hypervisors.  This is a step in that
> direction that I am using today in some work that requires
> more memory than xenheap can provide (which I'll hopefully
> post sometime in the next few weeks).
> 
> Comments?
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2008-08-29 18:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-29 17:12 [PATCH][RFC] sub-page anonymous domain memory allocator Daniel Magenheimer
2008-08-29 18:18 ` Keir Fraser [this message]
2008-08-29 19:46   ` Daniel 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=C4DDFC13.1CA2C%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=dan.magenheimer@oracle.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.