[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Tue, 3 Mar 2015 09:10:56 -0800
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: linux-kernel@...r.kernel.org
Cc: mingo@...nel.org, laijs@...fujitsu.com, dipankar@...ibm.com,
akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
josh@...htriplett.org, tglx@...utronix.de, peterz@...radead.org,
rostedt@...dmis.org, dhowells@...hat.com, edumazet@...gle.com,
dvhart@...ux.intel.com, fweisbec@...il.com, oleg@...hat.com,
bobby.prani@...il.com
Subject: [PATCH tip/core/rcu 0/5] In-kernel programmatic grace-period
expediting for v4.1
Hello!
This series provides an in-kernel API to expedite and unexpedite normal
RCU grace-period primitives such as synchronize_rcu(). It also provides
a Kconfig parameter that implicitly expedites at boot time, along with
a function that notes the end of in-kernel boot. This last function is
intended to be invoked just before init is spawned.
1. Provide rcu_expedite_gp() and rcu_unexpedite_gp().
2. Add rcu_expedite_gp() and rcu_unexpedite_gp() to rcutorture.
3. Change open-coded references ot the rcu_expedited variable to
instead use the new rcu_gp_is_expedited() function.
4. Add a CONFIG_RCU_EXPEDITE_BOOT Kconfig parameter that emulates
a very early boot rcu_expedite_gp(). Also provide a new
rcu_end_inkernel_boot() function that provides the corresponding
rcu_unexpedite_gp() if CONFIG_RCU_EXPEDITE_BOOT.
5. Make consistent use of variables in rcu_torture_writer().
Thanx, Paul
------------------------------------------------------------------------
b/include/linux/rcupdate.h | 21 ++++++++++++++++
b/init/Kconfig | 13 +++++++++
b/kernel/rcu/rcutorture.c | 27 +++++++++++++++++++-
b/kernel/rcu/srcu.c | 2 -
b/kernel/rcu/tree.c | 9 +++---
b/kernel/rcu/tree_plugin.h | 2 -
b/kernel/rcu/update.c | 59 ++++++++++++++++++++++++++++++++++++++++++++-
7 files changed, 125 insertions(+), 8 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists