From: Andi Kleen <ak@suse.de>
To: Ravikiran G Thirumalai <kiran@scalex86.org>
Cc: Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org, discuss@x86-64.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: [discuss] [patch 1/3] x86_64: Node local pda take 2 -- early cpu_to_node
Date: Thu, 15 Dec 2005 10:44:37 +0100 [thread overview]
Message-ID: <20051215094437.GY23384@wotan.suse.de> (raw)
In-Reply-To: <20051215023345.GB3787@localhost.localdomain>
On Wed, Dec 14, 2005 at 06:33:45PM -0800, Ravikiran G Thirumalai wrote:
> Here is take 2 on x86_64 node local pda allocation.
>
> This patchset does away with the extra memory reference for non CONFIG_NUMA
> case. The early cpu_to_node helps AMD and EM64T systems which work well
> with CONFIG_ACPI_NUMA. cpu_to_node is not inited early for AMD systems
> which work only with old style K8_NUMA. (Tested on EM64 NUMA and Tyan K8
> dual core 4 cpu boxes)
Thanks for now testing on AMD too - that makes me more confident in your
patches.
> Andi, I could not eliminate the need for a initial static pda array, since
> sched_init needs the static per-cpu offset array for NR_CPUS early. Hope
> this is OK.
See my comment.
> + * Setup cpu_to_node using the SRAT lapcis & ACPI MADT table
> + * info.
> + */
> +void __init init_cpu_to_node(void)
> +{
> + int i;
> + for (i = 0; i < NR_CPUS; i++)
> + cpu_to_node[i] = apicid_to_node[x86_cpu_to_apicid[i]];
> +}
I would prefer it if you moved that to numa.c and run always
(even for the k8topology case). Otherwise k8topology will behave
differently whether CONFIG_ACPI_NUMA is set or not, and I don't like
that.
-Andi
next prev parent reply other threads:[~2005-12-15 9:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 2:33 Ravikiran G Thirumalai
2005-12-15 2:35 ` [patch 2/3] x86_64: Node local pda take 2 -- cpu_pda_prep Ravikiran G Thirumalai
2005-12-15 2:37 ` [patch 3/3] x86_64: Node local pda take 2 -- node local pda allocation Ravikiran G Thirumalai
2005-12-15 8:22 ` Eric Dumazet
2005-12-15 9:36 ` Andi Kleen
2005-12-15 9:42 ` [discuss] " Andi Kleen
2005-12-15 18:47 ` Ravikiran G Thirumalai
2005-12-16 0:19 ` Andi Kleen
2005-12-16 3:55 ` Ravikiran G Thirumalai
2005-12-15 9:44 ` Andi Kleen [this message]
2005-12-15 19:01 ` [discuss] [patch 1/3] x86_64: Node local pda take 2 -- early cpu_to_node Ravikiran G Thirumalai
2005-12-16 0:20 ` Andi Kleen
2005-12-16 8:11 ` Ravikiran G Thirumalai
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=20051215094437.GY23384@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=discuss@x86-64.org \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome