From: Ryan Harper <ryanh@us.ibm.com>
To: Tristan Gingold <Tristan.Gingold@bull.net>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 0/6] xen,xend,tools: Add NUMA support to Xen
Date: Tue, 1 Aug 2006 10:40:53 -0500 [thread overview]
Message-ID: <20060801154053.GQ1694@us.ibm.com> (raw)
In-Reply-To: <200608010946.43556.Tristan.Gingold@bull.net>
* Tristan Gingold <Tristan.Gingold@bull.net> [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@us.ibm.com
next prev parent reply other threads:[~2006-08-01 15:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 19:09 [PATCH 0/6] xen,xend,tools: Add NUMA support to Xen Ryan Harper
2006-08-01 7:46 ` Tristan Gingold
2006-08-01 15:40 ` Ryan Harper [this message]
2006-08-02 5:59 ` Tristan Gingold
2006-08-02 22:29 ` Ryan Harper
2006-08-03 6:05 ` Tristan Gingold
2006-08-05 0:33 ` [PATCH 0/6] xen, xend, tools: Add NUMA support to Xen Issues on the ES7000 Subrahmanian, Raj
2006-08-07 13:23 ` Ryan Harper
2006-08-07 19:29 ` Subrahmanian, Raj
2006-08-01 9:29 ` [PATCH 0/6] xen,xend,tools: Add NUMA support to Xen Tristan Gingold
2006-08-02 6:14 ` Tristan Gingold
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=20060801154053.GQ1694@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=Tristan.Gingold@bull.net \
--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.