summaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@linux.vnet.ibm.com>2010-01-04 15:09:06 -0800
committerIngo Molnar <mingo@elte.hu>2010-01-13 09:06:03 +0100
commit0f10dc826646134dce3e5751512b87d30f3903e4 (patch)
tree6d377b3714889a0ab148166a33105b3be14be0c1 /arch
parenteb1ba45f1e7f6e626fefc063b340c7cbec9bd8c7 (diff)
downloadop-kernel-dev-0f10dc826646134dce3e5751512b87d30f3903e4.zip
op-kernel-dev-0f10dc826646134dce3e5751512b87d30f3903e4.tar.gz
rcu: Eliminate rcu_process_dyntick() return value
Because a new grace period cannot start while we are executing within the force_quiescent_state() function's switch statement, if any test within that switch statement or within any function called from that switch statement shows that the current grace period has ended, we can safely re-do that test any time before we leave the switch statement. This means that we no longer need a return value from rcu_process_dyntick(), as we can simply invoke rcu_gp_in_progress() to check whether the old grace period has finished -- there is no longer any need to worry about whether or not a new grace period has been started. Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Cc: laijs@cn.fujitsu.com Cc: dipankar@in.ibm.com Cc: mathieu.desnoyers@polymtl.ca Cc: josh@joshtriplett.org Cc: dvhltc@us.ibm.com Cc: niv@us.ibm.com Cc: peterz@infradead.org Cc: rostedt@goodmis.org Cc: Valdis.Kletnieks@vt.edu Cc: dhowells@redhat.com LKML-Reference: <12626465501857-git-send-email-> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud