From: Andi Kleen <ak@suse.de>
To: Mike Travis <travis@sgi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
clameter@sgi.com, steiner@sgi.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, kamalesh@linux.vnet.ibm.com
Subject: Re: [PATCH 3/6] x86: Convert cpu_sibling_map to be a per cpu variable (v2) (fwd)
Date: Wed, 5 Sep 2007 09:10:10 +0100 [thread overview]
Message-ID: <200709050910.10954.ak@suse.de> (raw)
In-Reply-To: <46DDE623.1090402@sgi.com>
> > It'd be better to convert the unconverted architectures?
Agreed.
> I can easily do the changes for ia64 and test them. I don't have the
> capability of testing on the powerpc.
You can get cross compilers and make it compile and I'm sure some
powerpc person will be happy to test it then when you post the patches
> And are you asking for just the changes to fix the build problem, or the
> whole set of the changes that were made for x86_64 and i386 in regards to
> converting NR_CPU arrays to per cpu data?
At least the variables that are used by non architecture specific code
(like cpu_sibling_map) should be probably all converted. For architecture
specific variables it's ok to leave it to the architecture people.
-Andi
next prev parent reply other threads:[~2007-09-05 8:13 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 ` [PATCH 3/6] x86: Convert cpu_sibling_map to be a per cpu variable (v2) (fwd) Mike Travis
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 [this message]
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=200709050910.10954.ak@suse.de \
--to=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 \
--cc=travis@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