mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Robin Holt" <holt@sgi.com>
Cc: "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 15:26:46 +0300	[thread overview]
Message-ID: <84144f020807170526x6f013357i29280595f65a67f4@mail.gmail.com> (raw)
In-Reply-To: <20080717113826.GG8534@sgi.com>

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.

However, while double-checking this, I noticed that for UP,
on_each_cpu() enables interrupts unconditionally with
local_irq_enable() whereas the call while the old code in SLUB did a
local_irq_restore() that preserves the irq mask. Looking at the
callers of flush_all() in mm/slub.c, the change looks okay, but it's
still bit strange on_each_cpu() works that way on UP.

                          Pekka

  reply	other threads:[~2008-07-17 12:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16 17:29 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 [this message]
2008-07-17 12:39     ` Robin Holt
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=84144f020807170526x6f013357i29280595f65a67f4@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=adobriyan@gmail.com \
    --cc=cl@linux-foundation.org \
    --cc=holt@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®