Home
last modified time | relevance | path

Searched hist:"8 d6dd656" (Results 1 – 2 of 2) sorted by relevance

/openbmc/linux/tools/testing/selftests/rcutorture/configs/rcu/
H A DSRCU-N8d6dd656 Mon Apr 10 12:27:19 CDT 2017 Paul E. McKenney <paulmck@linux.vnet.ibm.com> rcutorture: Add three-level tree test for Tree SRCU

This commit adds a test for a three-level srcu_node tree for Tree SRCU
in the existing SRCU-P scenario. This requires enabling CONFIG_RCU_EXPERT,
so the CONFIG_RCU_EXPERT=n scenario is now SRCU-N. The reason for using
SRCU-P for the tall tree is that preemption raises the possibility of
locating more bugs than does the non-preemptive SRCU-N.

Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
8d6dd656 Mon Apr 10 12:27:19 CDT 2017 Paul E. McKenney <paulmck@linux.vnet.ibm.com> rcutorture: Add three-level tree test for Tree SRCU

This commit adds a test for a three-level srcu_node tree for Tree SRCU
in the existing SRCU-P scenario. This requires enabling CONFIG_RCU_EXPERT,
so the CONFIG_RCU_EXPERT=n scenario is now SRCU-N. The reason for using
SRCU-P for the tall tree is that preemption raises the possibility of
locating more bugs than does the non-preemptive SRCU-N.

Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
H A DSRCU-P8d6dd656 Mon Apr 10 12:27:19 CDT 2017 Paul E. McKenney <paulmck@linux.vnet.ibm.com> rcutorture: Add three-level tree test for Tree SRCU

This commit adds a test for a three-level srcu_node tree for Tree SRCU
in the existing SRCU-P scenario. This requires enabling CONFIG_RCU_EXPERT,
so the CONFIG_RCU_EXPERT=n scenario is now SRCU-N. The reason for using
SRCU-P for the tall tree is that preemption raises the possibility of
locating more bugs than does the non-preemptive SRCU-N.

Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
8d6dd656 Mon Apr 10 12:27:19 CDT 2017 Paul E. McKenney <paulmck@linux.vnet.ibm.com> rcutorture: Add three-level tree test for Tree SRCU

This commit adds a test for a three-level srcu_node tree for Tree SRCU
in the existing SRCU-P scenario. This requires enabling CONFIG_RCU_EXPERT,
so the CONFIG_RCU_EXPERT=n scenario is now SRCU-N. The reason for using
SRCU-P for the tall tree is that preemption raises the possibility of
locating more bugs than does the non-preemptive SRCU-N.

Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>