public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Mikael Starvik <starvik@axis.com>,
	David Howells <dhowells@redhat.com>,
	Kyle McMartin <kyle@parisc-linux.org>,
	Anton Blanchard <anton@samba.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Paul Mundt <lethal@linux-sh.org>,
	"David S. Miller" <davem@davemloft.net>, Andi Kleen <ak@muc.de>,
	Christian Zankel <chris@zankel.net>,
	Philippe Elie <phil.el@wanadoo.fr>,
	Nathan Scott <nathans@sgi.com>, Jens Axboe <axboe@suse.de>,
	linux-arch@vger.kernel.org, Eric Dumazet <dada1@cosmosbay.com>
Subject: Re: percpu data changes
Date: Fri, 3 Feb 2006 01:36:18 -0800	[thread overview]
Message-ID: <20060203093618.GF2866@holomorphy.com> (raw)
In-Reply-To: <20060203011748.6fe3fee3.akpm@osdl.org>

On Fri, Feb 03, 2006 at 01:17:48AM -0800, Andrew Morton wrote:
> It seems that powerpc has gone and changed their implementation of percpu
> data so that there is no memory allocated for not-possible CPUs.  To save a
> bit of RAM.
> This means that any code which does
> 
> 	for (i = 0; i < NR_CPUS; i++)
> 		touch(percpudata(i))
> will explode on powerpc.
> I have a patch queued up (for 2.6.16) which fixes most users of percpu
> data.  Make them use for_each_cpu().  I'll send that in a moment.
...

Blanket Acked-by: William Irwin <wli@holomorphy.com>


-- wli

  parent reply	other threads:[~2006-02-03  9:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03  9:17 percpu data changes Andrew Morton
2006-02-03  9:18 ` Andrew Morton
2006-02-03  9:35   ` Andrew Morton
2006-02-03  9:38     ` David S. Miller
2006-02-03  9:36 ` William Lee Irwin III [this message]
2006-02-03  9:40 ` David S. Miller
2006-02-03  9:51 ` Andi Kleen
2006-02-03 11:01   ` Eric Dumazet
2006-02-03 11:07     ` Andi Kleen
2006-02-03 15:36 ` Kyle McMartin

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=20060203093618.GF2866@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=axboe@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=chris@zankel.net \
    --cc=dada1@cosmosbay.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=kyle@parisc-linux.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=nathans@sgi.com \
    --cc=paulus@samba.org \
    --cc=phil.el@wanadoo.fr \
    --cc=schwidefsky@de.ibm.com \
    --cc=starvik@axis.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