From: Ryan Harper <ryanh@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Xen Devel <xen-devel@lists.xensource.com>,
Andi Kleen <ak@suse.de>, Ryan Grimm <grimm@us.ibm.com>
Subject: Re: Re: [PATCH 1/6][RESEND] xen: Add NUMA support to Xen
Date: Mon, 15 May 2006 12:11:05 -0500 [thread overview]
Message-ID: <20060515171105.GK16876@us.ibm.com> (raw)
In-Reply-To: <70145f7d61d476ea095803ce06d3cb93@cl.cam.ac.uk>
* Keir Fraser <Keir.Fraser@cl.cam.ac.uk> [2006-05-15 11:55]:
>
> On 15 May 2006, at 17:27, Andi Kleen wrote:
>
> >> 1. You re-indented. Normally a good thing but not for copies of
> >>Linux source files. Please edit them and maintain them in Linux style
> >>(inc. hard tabs) as it makes it easier to sync with Linux updates.
> >
> >What Linux updates? The i386 NUMA support is basically dead and
> >bitrots slowly (except perhaps on NUMAQ) Every half a year someone
> >uses it and finds it doesn't work, maybe even fixes it and then it
> >breaks shortly after again. That's because it isn't used and tested in
> >any significant way. No distribution I'm aware of uses it either.
> >
> >If you want maintained NUMA it would be much better to base on the
> >x86-64
> >NUMA code.
>
> Sounds like an excellent plan to me: the x86/64 code looks cleaner too.
> Let's go with the x86/64 code then, unless there are any objections
> from the IBM folks?
When I looked at the x86_64 NUMA code, I noticed that SRAT parsing was
done by ACPI_NUMA (drivers/acpi/numa.c). That code requires more ACPI
support than Xen currently has available. Rather than pulling in all of
that ACPI, I chose to start with the i386 SRAT table parser which was
sufficient for both i386 and x86_64. I would think that using the
modified i386 srat.c for parser gets the job done without bringing in
all of the support needed to compile drivers/acpi/numa.c in Xen.
How about putting the two together: use the i386 SRAT parser and the
x86_64 srat.c for structures and initialization?
--
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-05-15 17:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 21:56 [PATCH 1/6] xen: Add NUMA support to Xen Ryan Harper
2006-05-02 14:15 ` Keir Fraser
2006-05-02 14:39 ` Ryan Harper
2006-05-12 15:12 ` [PATCH 1/6][RESEND] " Ryan Harper
2006-05-13 9:07 ` Keir Fraser
2006-05-15 16:27 ` Andi Kleen
2006-05-15 16:54 ` Keir Fraser
2006-05-15 17:11 ` Ryan Harper [this message]
2006-05-15 17:17 ` Keir Fraser
2006-05-15 17:23 ` Keir Fraser
2006-05-15 17:25 ` Andi Kleen
2006-05-15 17:27 ` Ryan Harper
2006-05-15 17:34 ` Keir Fraser
2006-05-15 20:32 ` Ryan Harper
2006-05-15 20:46 ` Andi Kleen
2006-05-16 7:49 ` Keir Fraser
2006-05-16 12:57 ` Andi Kleen
2006-05-16 13:03 ` Keir Fraser
2006-05-19 21:08 ` Ryan Harper
2006-05-20 8:50 ` Keir Fraser
2006-05-22 11:01 ` Andi Kleen
2006-05-24 19:02 ` Ryan Harper
2006-05-31 18:06 ` Ryan Harper
2006-06-02 15:55 ` Ryan Harper
2006-05-17 17:21 ` Ryan Harper
2006-05-17 18:07 ` Andi Kleen
2006-05-18 15:30 ` Ryan Harper
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=20060515171105.GK16876@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=ak@suse.de \
--cc=grimm@us.ibm.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.