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] [PATCH 0/6] xen,xend,tools: Add NUMA support to Xen

To: Tristan Gingold <Tristan.Gingold@xxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0/6] xen,xend,tools: Add NUMA support to Xen
From: Ryan Harper <ryanh@xxxxxxxxxx>
Date: Tue, 1 Aug 2006 10:40:53 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 01 Aug 2006 08:41:25 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200608010946.43556.Tristan.Gingold@xxxxxxxx>
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>
References: <20060731190958.GI1694@xxxxxxxxxx> <200608010946.43556.Tristan.Gingold@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6+20040907i
* Tristan Gingold <Tristan.Gingold@xxxxxxxx> [2006-08-01 02:43]:
> Le Lundi 31 Juillet 2006 21:09, Ryan Harper a écrit :
> > I've respun the NUMA patches against 10874 and I'm re-submitting them
> > with the optimizations mentioned [1]previously on the list.  There was a
> > request to see the overhead on non-numa/single-node machines.  I've
> > re-run those benchmarks (ballooning up from small mem to multi-gig) as
> > well as timing the initially domain increase_reservation time to gauge
> > the overhead when allocating from the heap.
> Hi,
> 
> I am trying to use your patch on ia64.

Thanks for testing these out on ia64.

> 
> In asm-x86/topology.h, you wrote:
> 
> extern unsigned int cpu_to_node[];
> extern cpumask_t     node_to_cpumask[];
> 
> #define cpu_to_node(cpu)              (cpu_to_node[cpu])
> #define parent_node(node)             (node)
> #define node_to_first_cpu(node)  (__ffs(node_to_cpumask[node]))
> #define node_to_cpumask(node)    (node_to_cpumask[node])
> 
> I think cpu_to_node and node_to_cpumask must be either a variable or a macro, 
> but not both! (ia64 defines cpu_to_node as a macro).

I'm not sure about this, but the definition of both the variable and
macro come from Linux, for example in

linux/include/asm-x86_64/topology.h

extern unsigned char cpu_to_node[];
extern cpumask_t     node_to_cpumask[];

#ifdef CONFIG_ACPI_NUMA
extern int __node_distance(int, int);
#define node_distance(a,b) __node_distance(a,b)
/* #else fallback version */
#endif

#define cpu_to_node(cpu)      (cpu_to_node[cpu])
#define parent_node(node)     (node)
#define node_to_first_cpu(node)  (first_cpu(node_to_cpumask[node]))
#define node_to_cpumask(node)    (node_to_cpumask[node])

AFAIK, this isn't an issue.

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@xxxxxxxxxx

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