From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu, laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, niv@us.ibm.com, tglx@linutronix.de,
peterz@infradead.org, rostedt@goodmis.org,
Valdis.Kletnieks@vt.edu, dhowells@redhat.com,
eric.dumazet@gmail.com, darren@dvhart.com, fweisbec@gmail.com,
sbw@mit.edu, patches@linaro.org
Subject: [PATCH tip/core/rcu 0/5] Documentation and rcutorture changes
Date: Thu, 30 Aug 2012 11:44:48 -0700 [thread overview]
Message-ID: <20120830184448.GA31753@linux.vnet.ibm.com> (raw)
Hello!
This series covers changes to rcutorture and documentation updates.
The individual patches in this series are as follows:
1. Update rcutorture default values so that casual rcutorture
users will do more aggressive testing.
2. Make rcutorture track CPU-hotplug latency statistics.
3. Document SRCU's new-found ability to be used by offline and
idle CPUs, and also emphasize SRCU's limitations.
4. Use the new pr_*() interfaces in rcutorture.
5. Prevent kthread-initialization races in rcutorture.
Thanx, Paul
------------------------------------------------------------------------
b/Documentation/RCU/checklist.txt | 6 +
b/Documentation/RCU/whatisRCU.txt | 9 +-
b/kernel/rcutorture.c | 4 -
kernel/rcutorture.c | 152 +++++++++++++++++++++++---------------
4 files changed, 108 insertions(+), 63 deletions(-)
next reply other threads:[~2012-08-30 18:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 18:44 Paul E. McKenney [this message]
2012-08-30 18:45 ` [PATCH tip/core/rcu 1/5] rcu: Update rcutorture defaults Paul E. McKenney
2012-08-30 18:45 ` [PATCH tip/core/rcu 2/5] rcu: Track CPU-hotplug duration statistics Paul E. McKenney
2012-08-30 19:00 ` Josh Triplett
2012-08-30 20:38 ` Paul E. McKenney
2012-08-30 23:23 ` Josh Triplett
2012-08-30 18:45 ` [PATCH tip/core/rcu 3/5] rcu: Document SRCU dead-CPU capabilities, emphasize read-side limits Paul E. McKenney
2012-08-30 19:01 ` Josh Triplett
2012-09-18 9:12 ` Lai Jiangshan
2012-09-18 23:32 ` Paul E. McKenney
2012-08-30 18:45 ` [PATCH tip/core/rcu 4/5] rcu: Switch rcutorture to pr_alert() and friends Paul E. McKenney
2012-08-30 19:05 ` Josh Triplett
2012-08-30 18:45 ` [PATCH tip/core/rcu 5/5] rcu: Prevent initialization race in rcutorture kthreads Paul E. McKenney
2012-08-30 19:15 ` Josh Triplett
2012-08-30 18:57 ` [PATCH tip/core/rcu 1/5] rcu: Update rcutorture defaults Josh Triplett
2012-08-30 21:35 ` Paul E. McKenney
2012-08-30 23:24 ` Josh Triplett
2012-08-30 18:56 ` [PATCH tip/core/rcu 0/5] Documentation and rcutorture changes Josh Triplett
2012-08-30 21:46 ` Paul E. McKenney
2012-08-30 23:22 ` Josh Triplett
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=20120830184448.GA31753@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=darren@dvhart.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=eric.dumazet@gmail.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=patches@linaro.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sbw@mit.edu \
--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;
as well as URLs for NNTP newsgroup(s).