WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [RFC][PATCH 1/2] export NUMA topology from xen

To: Ryan Harper <ryanh@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [RFC][PATCH 1/2] export NUMA topology from xen
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Tue, 10 Apr 2007 10:12:22 +0100
Delivery-date: Tue, 10 Apr 2007 02:11:23 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070410010929.GF28281@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acd7UFjBlw16qOdDEduFrAAX8io7RQ==
Thread-topic: [Xen-devel] [RFC][PATCH 1/2] export NUMA topology from xen
User-agent: Microsoft-Entourage/11.2.5.060620
On 10/4/07 02:09, "Ryan Harper" <ryanh@xxxxxxxxxx> wrote:

> nr_nodes               : 4
> mem_chunks             : node0:0x0000000000000000-0x0000000190000000
>                          node1:0x0000000190000000-0x0000000300000000
>                          node2:0x0000000300000000-0x0000000470000000
>                          node3:0x0000000470000000-0x0000000640000000
> node_to_cpu            : node0:0-7
>                          node1:8-15
>                          node2:16-23
>                          node3:24-31
> 
> I've also reworked the the physinfo call to contain an array of
> cpu_to_node elements rather than node_to_cpu to support machines larger
> than 64-way.  I convert the array back to node_to_cpu for brevity in
> xm info display.

The same would make sense for memory regions (i.e., have a list of
memory-regions and include a node identifier for each one, rather than
mapping node-id to memory-region) as this would allow to have multiple
memory regions per node quite easily. But actually I'm not convinced that
allowing dom0 to read out the physical addresses of memory regions is at all
useful -- why would anyone care which particular physical address ranges
belong to a particular node? The hypercall to find amount of free memory per
node seems more useful, and probably sufficient by itself.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>