All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@polymtl.ca,
	josh@joshtriplett.org, dvhltc@us.ibm.com, niv@us.ibm.com,
	tglx@linutronix.de, peterz@infradead.org, rostedt@goodmis.org,
	Valdis.Kletnieks@vt.edu, dhowells@redhat.com
Subject: Re: [PATCH tip/core/rcu 0/4] rcu: preemptible expedited grace periods and cleanups
Date: Thu, 03 Dec 2009 16:53:13 +0800	[thread overview]
Message-ID: <4B177C79.1040407@cn.fujitsu.com> (raw)
In-Reply-To: <20091202200955.GA12950@linux.vnet.ibm.com>

Paul E. McKenney wrote:
> This patchset includes some cleanups, improved diagnostics, and an
> implementation of expedited preemptible RCU grace periods that is
> actually expedited:
> 
> 1.	Rename the "quiet" functions.  The name rcu_quiet_cpu() was
> 	clear enough, but now that we have four flavors of quietness
> 	with more on the way, we need more meaningful names.
> 
> 2.	Enable a fourth level of the rcu_node hierarchy.  No, we really
> 	don't need the ability to run on million-CPU SMP systems at the
> 	moment, but the additional level allows more vigorous
> 	stress-testing on 16-CPU systems.
> 
> 3.	Add an implementation of synchronize_rcu_expedited() that
> 	actually expedites preemptible-RCU grace periods.
> 
> 4.	Make RCU_CPU_STALL_DETECTOR be on by default.  If this works
> 	well, the #ifdefs will eventually be removed to reduce testing
> 	load.
> 
> This patchset is intended for 2.6.34, but has passed sufficient testing
> that it could safely be included in 2.6.33, if desired.
> 

Ack for the whole patchset except [PATCH 3/4]

Acked-by: Lai Jiangshan <laijs@cn.fujitsu.com>

      parent reply	other threads:[~2009-12-03  8:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 20:09 [PATCH tip/core/rcu 0/4] rcu: preemptible expedited grace periods and cleanups Paul E. McKenney
2009-12-02 20:10 ` [PATCH tip/core/rcu 1/4] rcu: rename "quiet" functions Paul E. McKenney
2009-12-02 23:20   ` Josh Triplett
2009-12-03 13:22   ` [tip:core/rcu] rcu: Rename " tip-bot for Paul E. McKenney
2009-12-02 20:10 ` [PATCH tip/core/rcu 2/4] rcu: enable fourth level of TREE_RCU hierarchy Paul E. McKenney
2009-12-02 23:25   ` Josh Triplett
2009-12-03  0:20     ` Paul E. McKenney
2009-12-03 13:22   ` [tip:core/rcu] rcu: Enable " tip-bot for Paul E. McKenney
2009-12-02 20:10 ` [PATCH tip/core/rcu 3/4] rcu: add expedited grace-period support for preemptible RCU Paul E. McKenney
2009-12-03  9:26   ` Lai Jiangshan
2009-12-03 14:41     ` Paul E. McKenney
2009-12-03 13:22   ` [tip:core/rcu] rcu: Add " tip-bot for Paul E. McKenney
2009-12-02 20:10 ` [PATCH tip/core/rcu 4/4] rcu: make RCU's CPU-stall detector be default Paul E. McKenney
2009-12-03 13:22   ` [tip:core/rcu] rcu: Make " tip-bot for Paul E. McKenney
2009-12-03  8:53 ` Lai Jiangshan [this message]

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=4B177C79.1040407@cn.fujitsu.com \
    --to=laijs@cn.fujitsu.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=dvhltc@us.ibm.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=niv@us.ibm.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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.