From: Robin Holt <holt@sgi.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Robin Holt <holt@sgi.com>, Alexey Dobriyan <adobriyan@gmail.com>,
cl@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: SLUB: simplify re on_each_cpu()
Date: Thu, 17 Jul 2008 07:39:06 -0500 [thread overview]
Message-ID: <20080717123906.GH8534@sgi.com> (raw)
In-Reply-To: <84144f020807170526x6f013357i29280595f65a67f4@mail.gmail.com>
On Thu, Jul 17, 2008 at 03:26:46PM +0300, Pekka Enberg wrote:
> Hi Robin,
>
> On Wed, Jul 16, 2008 at 09:29:02PM +0400, Alexey Dobriyan wrote:
> >> on_each_cpu() expands to function call on UP, too.
>
> On Thu, Jul 17, 2008 at 2:38 PM, Robin Holt <holt@sgi.com> wrote:
> > It looks to me like on_each_cpu is a #define for !SMP. Are you certain
> > of the need for this change? Are you looking at a different tree than
> > Linus'?
>
> I think it's actually you who is looking at an older tree.
I did a git-checkout of
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
which got me commit id 33af79d12e0fa25545d49e86afc67ea8ad5f2f40
and looked at include/linux/smp.h line 123. It has:
#define on_each_cpu(func,info,wait) \
({ \
local_irq_disable(); \
func(info); \
local_irq_enable(); \
0; \
})
This is the !CONFIG_SMP case (line 111). When I look at
kernel/softirq.c, I notice immediately prior to the comment the #ifdef
CONFIG_SMP.
They appear equivalent. What am I missing?
Thanks,
Robin
next prev parent reply other threads:[~2008-07-17 12:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 17:29 SLUB: simplify re on_each_cpu() Alexey Dobriyan
2008-07-16 17:36 ` Christoph Lameter
2008-07-16 20:58 ` Pekka Enberg
2008-07-17 11:38 ` Robin Holt
2008-07-17 12:26 ` Pekka Enberg
2008-07-17 12:39 ` Robin Holt [this message]
2008-07-17 12:55 ` Vegard Nossum
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=20080717123906.GH8534@sgi.com \
--to=holt@sgi.com \
--cc=adobriyan@gmail.com \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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