From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] fix generic non-SMP builds
Date: Mon, 14 Mar 2005 04:49:39 +0000 [thread overview]
Message-ID: <200503132049.39708.jbarnes@sgi.com> (raw)
In-Reply-To: <1110765467.10208.9.camel@localhost>
On Sunday, March 13, 2005 5:57 pm, dann frazier wrote:
> +u8 cpu_to_node_map[NR_CPUS] __cacheline_aligned;
> +EXPORT_SYMBOL(cpu_to_node_map);
> +
> +cpumask_t node_to_cpu_mask[MAX_NUMNODES] __cacheline_aligned;
I'm trying to figure out why these are caheline aligned... they're ready-only
for after boot (hotplug aside), right? Do we see that a lot of cpu/node
local references to them occur? OTOH, the wastage isn't that big either
way...
> + for(cpu = 0; cpu < NR_CPUS; ++cpu) {
> + node = -1;
> + for (i = 0; i < NR_CPUS; ++i)
> + if (cpu_physical_id(cpu) = node_cpuid[i].phys_id) {
> + node = node_cpuid[i].nid;
Is there a for_each_node(n) now?
> + for (cpu = 0; cpu < NR_CPUS; cpu++)
> + per_cpu(local_per_cpu_offset, cpu) = __per_cpu_offset[cpu];
for_each_cpu here I think.
Not sure when Tony had this queued up, so we may have to rediff in a week or
two, otherwise it looks good.
Jess
next prev parent reply other threads:[~2005-03-14 4:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 1:57 [PATCH] fix generic non-SMP builds dann frazier
2005-03-14 4:49 ` Jesse Barnes [this message]
2005-06-08 21:03 ` Greg Edwards
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=200503132049.39708.jbarnes@sgi.com \
--to=jbarnes@sgi.com \
--cc=linux-ia64@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