linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mike Travis <travis@sgi.com>,
	steiner@sgi.com, ak@suse.de, 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: Tue, 4 Sep 2007 20:48:20 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0709042047380.7231@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070904141055.e00a60d7.akpm@linux-foundation.org>

On Tue, 4 Sep 2007, Andrew Morton wrote:

> > 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... ;-)
> 
> It'd be better to convert the unconverted architectures?

That is certainly the cleanest solution. Maybe we can only convert the 
variables used in the scheduler that way?

--
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>

      parent reply	other threads:[~2007-09-05  3:48 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
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 [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=Pine.LNX.4.64.0709042047380.7231@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --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