From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: mingo@kernel.org
Cc: linux-kernel@vger.kernel.org, sasha.levin@oracle.com,
tglx@linutronix.de, cl@linux.com, dave.hansen@intel.com,
ak@linux.intel.com, umgwanakikbuti@gmail.com,
eric.dumazet@gmail.com, josh@joshtriplett.org, oleg@redhat.com
Subject: [GIT PULL rcu/urgent] Fixes for 3.16
Date: Tue, 24 Jun 2014 06:58:58 -0700 [thread overview]
Message-ID: <20140624135857.GA3203@linux.vnet.ibm.com> (raw)
Hello, Ingo,
This series includes the following:
1. Export a pair of debug-object interfaces for RCU that will
allow the slab allocators to avoid a recursion bug located
by Sasha Levin. Strictly speaking, this is not a regression,
but it would be good to enable the fix.
2. Address a serious performance regression on an open/close
micro-benchmark located by Dave Hansen. The offending commit
is ac1bea85781e (Make cond_resched() report RCU quiescent states).
Both have been exposed to -next testing, and are available in the git
repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git urgent.2014.06.23a
for you to fetch changes up to 4a81e8328d3791a4f99bf5b436d050f6dc5ffea3:
rcu: Reduce overhead of cond_resched() checks for RCU (2014-06-23 11:19:32 -0700)
----------------------------------------------------------------
Paul E. McKenney (2):
rcu: Export debug_init_rcu_head() and and debug_init_rcu_head()
rcu: Reduce overhead of cond_resched() checks for RCU
Documentation/kernel-parameters.txt | 6 ++
include/linux/rcupdate.h | 46 +++---------
kernel/rcu/tree.c | 140 ++++++++++++++++++++++++++++--------
kernel/rcu/tree.h | 6 +-
kernel/rcu/tree_plugin.h | 2 +-
kernel/rcu/update.c | 22 +-----
kernel/sched/core.c | 7 +-
7 files changed, 137 insertions(+), 92 deletions(-)
next reply other threads:[~2014-06-24 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 13:58 Paul E. McKenney [this message]
2014-06-25 5:39 ` [GIT PULL rcu/urgent] Fixes for 3.16 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=20140624135857.GA3203@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=ak@linux.intel.com \
--cc=cl@linux.com \
--cc=dave.hansen@intel.com \
--cc=eric.dumazet@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=sasha.levin@oracle.com \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@gmail.com \
/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.