public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
	"Paul E. McKenney" <paulmck@us.ibm.com>
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] RCU read sched
Date: Tue, 30 Sep 2008 12:08:30 +0200	[thread overview]
Message-ID: <20080930100829.GC7557@elte.hu> (raw)
In-Reply-To: <20080929150646.GD11245@Krystal>


* Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> wrote:

> (probably already in -tip)
> 
> Add rcu_read_lock_sched() and rcu_read_unlock_sched() to rcupdate.h to match the
> recently added write-side call_rcu_sched() and rcu_barrier_sched(). They also
> match the no-so-recently-added synchronize_sched().
> 
> It will help following matching use of the update/read lock primitives. Those
> new read lock will replace preempt_disable()/enable() used in pair with
> RCU-classic synchronization.
> 
> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
> Acked-by: Peter Zijlstra <peterz@infradead.org>
> CC: Paul E McKenney <paulmck@linux.vnet.ibm.com>

Paul, does this API extension look good to you?

i'll apply it to tip/core/rcu if yes.

	Ingo

  reply	other threads:[~2008-09-30 10:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-29  8:00 [PATCH] markers: fix unregister bug and reenter bug Lai Jiangshan
2008-09-29  8:27 ` Ingo Molnar
2008-09-29 15:03   ` Mathieu Desnoyers
2008-09-29 15:05   ` [PATCH] Markers : marker_synchronize_unregister() Mathieu Desnoyers
2008-09-30  1:47     ` Lai Jiangshan
     [not found]     ` <20081002235650.43ca075c.akpm@linux-foundation.org>
2008-10-03 15:52       ` [PATCH] Markers synchronize unregister static inline Mathieu Desnoyers
2008-10-03 17:31         ` Ingo Molnar
2008-09-29 15:06   ` [PATCH] RCU read sched Mathieu Desnoyers
2008-09-30 10:08     ` Ingo Molnar [this message]
2008-09-30 13:10       ` Paul E. McKenney
2008-09-30 13:10     ` Paul E. McKenney
2008-09-29 15:08   ` [PATCH] Markers use rcu_read_lock_sched() Mathieu Desnoyers
2008-09-30 10:13     ` Ingo Molnar
2008-09-29 15:09   ` [PATCH] Markers : probe example fix teardown Mathieu Desnoyers
2008-09-29 15:10   ` [PATCH] Markers : documentation " Mathieu Desnoyers
2008-09-29 15:11   ` [PATCH] sputrace : use marker_synchronize_unregister() Mathieu Desnoyers
2008-09-29 15:13     ` Christoph Hellwig
2008-09-30  0:28     ` Jeremy Kerr
2008-09-30  9:55       ` Ingo Molnar
2008-09-30 11:22         ` [Cbe-oss-dev] " Jeremy Kerr
2008-09-30 11:30           ` Ingo Molnar
2008-09-30 11:34             ` Jeremy Kerr
2008-09-29 15:03 ` [PATCH] markers: fix unregister bug and reenter bug Mathieu Desnoyers
2008-09-30  1:40   ` Lai Jiangshan
2008-09-30  3:38     ` Mathieu Desnoyers

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=20080930100829.GC7557@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=paulmck@us.ibm.com \
    --cc=rostedt@goodmis.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