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 RFC tip/core/rcu 0/3] RT latency optimizations
Date: Mon, 18 Nov 2013 14:02:20 -0800 [thread overview]
Message-ID: <20131118220220.GA23353@linux.vnet.ibm.com> (raw)
Hello!
This series provides some minor latency optimizations for kernels that
build with CONFIG_RCU_NOCB_CPU_ALL=y:
1. Create a static inline implementation of rcu_is_nocb_cpu() that
unconditionally returns true when CONFIG_RCU_NOCB_CPU_ALL=y.
2. Create a static inline implementation of rcu_needs_cpu() that
unconditionally returns false when CONFIG_RCU_NOCB_CPU_ALL=y.
3. Create static inline implementations of rcu_prepare_for_idle()
and rcu_cleanup_after_idle() that are no-ops when
CONFIG_RCU_NOCB_CPU_ALL=y.
Thanx, Paul
------------------------------------------------------------------------
b/include/linux/rcupdate.h | 13 +++++++++++++
b/include/linux/rcutiny.h | 6 ------
b/include/linux/rcutree.h | 2 ++
b/kernel/rcu/tree.c | 2 +-
b/kernel/rcu/tree_plugin.h | 13 +++++++++++--
5 files changed, 27 insertions(+), 9 deletions(-)
next reply other threads:[~2013-11-18 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 22:02 Paul E. McKenney [this message]
2013-11-18 22:02 ` [PATCH tip/core/rcu 1/3] rcu: Optimize rcu_is_nocb_cpu() for RCU_NOCB_CPU_ALL Paul E. McKenney
2013-11-18 22:02 ` [PATCH tip/core/rcu 2/3] rcu: Optimize rcu_needs_cpu() " Paul E. McKenney
2013-11-18 22:02 ` [PATCH tip/core/rcu 3/3] Optimize RCU_FAST_NO_HZ " 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=20131118220220.GA23353@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;
as well as URLs for NNTP newsgroup(s).