public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, 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, dhowells@redhat.com,
	edumazet@google.com, darren@dvhart.com, fweisbec@gmail.com,
	sbw@mit.edu
Subject: [PATCH tip/core/rcu 0/6] Idle entry/exit changes for 3.13
Date: Tue, 24 Sep 2013 18:49:55 -0700	[thread overview]
Message-ID: <20130925014954.GA32109@linux.vnet.ibm.com> (raw)

Hello!

This series updates RCU's idle entry/exit processing:

1.	Remove redundant code from rcu_cleanup_after_idle().

2.	Throttle rcu_try_advance_all_cbs() execution to avoid kbuild
	slowdowns.

3.	Throttle non-lazy-callback-induced invoke_rcu_core() invocations.

4.	Add primitive to determine whether it is safe to enter an RCU
	read-side critical section.

5.	Upgrade EXPORT_SYMBOL() to EXPORT_SYMBOL_GPL().

6.	Change rcu_is_cpu_idle() function to __rcu_is_watching() for
	naming consistency.

							Thanx, Paul


 b/include/linux/rcupdate.h |   26 +++++++++++-----------
 b/include/linux/rcutiny.h  |   25 ++++++++++++++++++----
 b/include/linux/rcutree.h  |    4 ++-
 b/kernel/lockdep.c         |    4 +--
 b/kernel/rcupdate.c        |    2 -
 b/kernel/rcutiny.c         |   10 ++++----
 b/kernel/rcutree.c         |   51 ++++++++++++++++++++++++++++-----------------
 b/kernel/rcutree.h         |    2 +
 b/kernel/rcutree_plugin.h  |   24 +++++++++++----------
 9 files changed, 92 insertions(+), 56 deletions(-)


             reply	other threads:[~2013-09-25  1:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-25  1:49 Paul E. McKenney [this message]
2013-09-25  1:50 ` [PATCH tip/core/rcu 1/6] rcu: Remove redundant code from rcu_cleanup_after_idle() Paul E. McKenney
2013-09-25  1:50   ` [PATCH tip/core/rcu 2/6] rcu: Throttle rcu_try_advance_all_cbs() execution Paul E. McKenney
2013-09-25  1:50   ` [PATCH tip/core/rcu 3/6] rcu: Throttle invoke_rcu_core() invocations due to non-lazy callbacks Paul E. McKenney
2013-09-25  1:50   ` [PATCH tip/core/rcu 4/6] rcu: Is it safe to enter an RCU read-side critical section? Paul E. McKenney
2013-09-25  1:50   ` [PATCH tip/core/rcu 5/6] rcu: Change EXPORT_SYMBOL() to EXPORT_SYMBOL_GPL() Paul E. McKenney
2013-09-25  1:50   ` [PATCH tip/core/rcu 6/6] rcu: Consistent rcu_is_watching() naming Paul E. McKenney
2013-09-25  4:08 ` [PATCH tip/core/rcu 0/6] Idle entry/exit changes for 3.13 Josh Triplett
2013-09-25 13:45   ` Paul E. McKenney

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=20130925014954.GA32109@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=darren@dvhart.com \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=edumazet@google.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@kernel.org \
    --cc=niv@us.ibm.com \
    --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