From: Andi Kleen <ak@suse.de>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: discuss@x86-64.org, Ravikiran G Thirumalai <kiran@scalex86.org>,
linux-kernel@vger.kernel.org,
"Shai Fultheim (Shai@scalex86.org)" <shai@scalex86.org>
Subject: Re: [discuss] [rfc] x86_64: Kconfig changes for NUMA
Date: Thu, 27 Oct 2005 10:31:15 +0200 [thread overview]
Message-ID: <200510271031.15403.ak@suse.de> (raw)
In-Reply-To: <aec7e5c30510270125q1e175daeoeaea99584f305261@mail.gmail.com>
On Thursday 27 October 2005 10:25, Magnus Damm wrote:
>
> But if the same logic is applied to the NUMA code, why then is there
> both k8topology.c and srat.c? Does non-ACPI systems exist in x86_64
> land?
Historical reasons. The first AMD NUMA systems indeed didn't have SRAT
and before ACPI 3.0 was released there were some concerns about the
Microsoft license of SRAT. So k8topology was implemented as a stopgap.
The long term plan is to get rid of it though once the ACPI code has been
proven completely stable.
-Andi
prev parent reply other threads:[~2005-10-27 8:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 7:09 [rfc] x86_64: Kconfig changes for NUMA Ravikiran G Thirumalai
2005-10-26 14:46 ` [discuss] " Andi Kleen
2005-10-26 20:20 ` Ravikiran G Thirumalai
2005-10-26 21:39 ` Andi Kleen
2005-10-27 1:40 ` Magnus Damm
2005-10-27 6:25 ` Magnus Damm
2005-10-27 7:50 ` Andi Kleen
2005-10-27 8:25 ` Magnus Damm
2005-10-27 8:31 ` Andi Kleen [this message]
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=200510271031.15403.ak@suse.de \
--to=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=shai@scalex86.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox