From: Mike Travis <travis@sgi.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Jack Steiner <steiner@sgi.com>, Andi Kleen <ak@suse.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Subject: Re: [PATCH 3/6] x86: Convert cpu_sibling_map to be a per cpu variable (v2) (fwd)
Date: Tue, 04 Sep 2007 13:29:11 -0700 [thread overview]
Message-ID: <46DDC017.4040301@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708312028400.24049@schroedinger.engr.sgi.com>
[Sorry, I did not see this message until Christoph forwarded it to me. I'm
guessing we (SGI) still have a problem with our external spam filter?]
>
> ---------- Forwarded message ----------
> Date: Fri, 31 Aug 2007 19:49:03 -0700
> From: Andrew Morton <akpm@linux-foundation.org>
> To: travis@sgi.com
> Cc: Andi Kleen <ak@suse.de>, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
> Christoph Lameter <clameter@sgi.com>
> Subject: Re: [PATCH 3/6] x86: Convert cpu_sibling_map to be a per cpu variable
> (v2)
>
> On Fri, 24 Aug 2007 15:26:57 -0700 travis@sgi.com wrote:
>
>> Convert cpu_sibling_map from a static array sized by NR_CPUS to a
>> per_cpu variable. This saves sizeof(cpumask_t) * NR unused cpus.
>> Access is mostly from startup and CPU HOTPLUG functions.
>
> ia64 allmodconfig:
>
> kernel/sched.c: In function `cpu_to_phys_group': kernel/sched.c:5937: error: `per_cpu__cpu_sibling_map' undeclared (first use in this function) kernel/sched.c:5937: error: (Each undeclared identifier is reported only once
> kernel/sched.c:5937: error: for each function it appears in.) kernel/sched.c:5937: warning: type defaults to `int' in declaration of `type name'
> kernel/sched.c:5937: error: invalid type argument of `unary *' kernel/sched.c: In function `build_sched_domains': kernel/sched.c:6172: error: `per_cpu__cpu_sibling_map' undeclared (first use in this function) kernel/sched.c:6172: warning: type defaults to `int' in declaration of `type name' kernel/sched.c:6172: error: invalid type argument of `unary *' kernel/sched.c:6183: warning: type defaults to `int' in declaration of `type name' kernel/sched.c:6183: error: invalid type argument of `unary *'
I'm thinking that the best approach would be to define a cpu_sibling_map() macro
to handle the cases where cpu_sibling_map is not a per_cpu variable? Perhaps
something like:
#ifdef CONFIG_SCHED_SMT
#ifndef cpu_sibling_map
#define cpu_sibling_map(cpu) cpu_sibling_map[cpu]
#endif
#endif
My question though, would include/linux/smp.h be the appropriate place for
the above define? (That is, if the above approach is the correct one... ;-)
Thanks,
Mike
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2007-09-04 20:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0708312028400.24049@schroedinger.engr.sgi.com>
2007-09-04 20:29 ` Mike Travis [this message]
2007-09-04 21:10 ` Andrew Morton
2007-09-04 23:11 ` Mike Travis
2007-09-05 0:00 ` Andrew Morton
2007-09-05 8:10 ` Andi Kleen
2007-09-05 8:40 ` Andrew Morton
2007-09-05 14:46 ` Mike Travis
2007-09-05 15:15 ` Andrew Morton
2007-09-05 3:48 ` Christoph Lameter
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=46DDC017.4040301@sgi.com \
--to=travis@sgi.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=steiner@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox