All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nick Piggin <npiggin@suse.de>
Cc: riel@redhat.com, linuxppc-dev@ozlabs.org,
	akpm@linux-foundation.org, paulmck@linux.vnet.ibm.com,
	a.p.zijlstra@chello.nl
Subject: Re: [patch 1/1] powerpc: add rcu_read_lock() to gup_fast() implementation
Date: Wed, 28 Apr 2010 14:10:58 +1000	[thread overview]
Message-ID: <1272427858.24542.60.camel@pasglop> (raw)
In-Reply-To: <20100428032931.GE5683@laptop>

On Wed, 2010-04-28 at 13:29 +1000, Nick Piggin wrote:
> I think I nacked this because the rest of the powerpc code also
> assumes irq disables provide an rcu critical section. The plan was
> to convert powerpc pagetable code to use call_rcu_sched.

Right, on my todo list.

Cheers,
Ben.

  reply	other threads:[~2010-04-28  4:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27 21:10 [patch 1/1] powerpc: add rcu_read_lock() to gup_fast() implementation akpm
2010-04-28  3:29 ` Nick Piggin
2010-04-28  4:10   ` Benjamin Herrenschmidt [this message]
2010-04-28  4:26 ` Benjamin Herrenschmidt

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=1272427858.24542.60.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=npiggin@suse.de \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=riel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.