This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] A tale of three memory allocators

To: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Subject: Re: [Xen-devel] A tale of three memory allocators
From: Andrew Theurer <habanero@xxxxxxxxxx>
Date: Fri, 18 Mar 2005 14:18:28 -0600
Cc: <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 18 Mar 2005 20:22:44 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <516F50407E01324991DD6D07B0531AD52A2DC0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <516F50407E01324991DD6D07B0531AD52A2DC0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.5
On Friday 18 March 2005 14:07, Magenheimer, Dan (HP Labs Fort Collins) wrote:
> >Of course I mean that the hypervisor probably has to support this stuff
> to
> >work correctly on multi-node ia64 machines.  The guests can probably
> get away
> >with being special cased since they can be presented with a contiguous
> memory
> >model (Dan is this what you're doing now?)...
> On Xen/ia64, domain0 is given the real EFI memory map and has capability
> to map any part of memory not owned by the Xen hypervisor.  All other
> domains are presented with contiguous memory starting at zero.

Even though the memory presented to the domU's are contiguous and start at 
zero, do you think it would be advantageous to still provide some sort of 
cpu<->memory topology infomation to the domU, so that domU's which span more 
than one node can take advantage of the NUMA code in the Linux kernel?  I 
would think eventually this is something many of the platforms would want, 

-Andrew Theurer

SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
Xen-devel mailing list