From: Steven Rostedt <rostedt@goodmis.org>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@polymtl.ca,
josht@linux.vnet.ibm.com, dvhltc@us.ibm.com, niv@us.ibm.com,
tglx@linutronix.de, peterz@infradead.org
Subject: Re: [PATCH tip/core/rcu 0/3] increase rcutorture intensity and fix a couple resulting bugs
Date: Tue, 08 Sep 2009 19:37:30 -0400 [thread overview]
Message-ID: <1252453051.20985.9.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20090908225349.GA19524@linux.vnet.ibm.com>
On Tue, 2009-09-08 at 15:53 -0700, Paul E. McKenney wrote:
> This patch series increases the intensity of rcutorture testing for
> TREE_PREEMPT_RCU and provides fixes for a couple resulting bugs.
>
> o Make rcutorture's RCU read-side critical sections occasionally
> spin for a few tens of milliseconds, which greatly increases
> the probability that they will be preempted and that quiescent
> states will be forced. Yes, this does uncover some bugs in
> TREE_PREEMPT_RCU (though TREE_RCU passes with flying colors).
>
> o Fix a bug where rnp->gpnum was not being updated. This
> increases TREE_PREEMPT_RCU's reliability considerably, though
> bugs still remain.
>
> o Make the initialization of multi-node trees of rcu_node
> structures unconditionally acquire rnp->lock. This simplifies
> the code a bit and will make it easier to allow grace-period
> initialization become preemptable, should this be needed.
>
> Next steps include applying review comments, adding expedited grace
> periods, and chasing down remaining bugs. Longer term, RCU priority
> boosting.
Hi Paul,
These patches look decent to me.
If it makes you feel comfy:
Acked-by: Steven Rostedt <rostedt@goodmis.org>
-- Steve
next prev parent reply other threads:[~2009-09-08 23:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 22:53 Paul E. McKenney
2009-09-08 22:54 ` [PATCH tip/core/rcu 1/3] rcutorture: Occasionally delay readers enough to make RCU force_quiescent_state Paul E. McKenney
2009-09-12 7:45 ` Ingo Molnar
2009-09-12 14:36 ` Paul E. McKenney
2009-09-12 7:55 ` [tip:core/urgent] " tip-bot for Josh Triplett
2009-09-17 22:10 ` tip-bot for Josh Triplett
2009-09-08 22:54 ` [PATCH tip/core/rcu 2/3] Need to update rnp->gpnum if preemptable RCU is to be reliable Paul E. McKenney
2009-09-12 7:55 ` [tip:core/urgent] rcu: " tip-bot for Paul E. McKenney
2009-09-17 22:10 ` tip-bot for Paul E. McKenney
2009-09-08 22:54 ` [PATCH tip/core/rcu 3/3] Initialize multi-level RCU grace periods holding locks Paul E. McKenney
2009-09-12 7:55 ` [tip:core/urgent] rcu: " tip-bot for Paul E. McKenney
2009-09-17 22:10 ` tip-bot for Paul E. McKenney
2009-09-08 23:37 ` Steven Rostedt [this message]
2009-09-09 17:43 ` [PATCH tip/core/rcu 0/3] increase rcutorture intensity and fix a couple resulting bugs Valdis.Kletnieks
2009-09-09 18:23 ` Paul E. McKenney
2009-09-12 7:46 ` Ingo Molnar
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=1252453051.20985.9.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=dipankar@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=josht@linux.vnet.ibm.com \
--cc=laijs@cn.fujitsu.com \
--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=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 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®