commit a94844b22a2e2b9155bbc0878c507850477221c2
author Paul E. McKenney <paulmck@linux.vnet.ibm.com> Fri Dec 12 07:37:48 2014 -0800
committer Paul E. McKenney <paulmck@linux.vnet.ibm.com> Thu Jan 15 23:25:04 2015 -0800
tree a7a9504a509d05b7b793d629bb3116a811f0c4a9
parent e3663b1024d1f94688e5233440ad67a9bc10b94e

rcu: Optionally run grace-period kthreads at real-time priority

Recent testing has shown that under heavy load, running RCU's grace-period
kthreads at real-time priority can improve performance (according to 0day
test robot) and reduce the incidence of RCU CPU stall warnings.  However,
most systems do just fine with the default non-realtime priorities for
these kthreads, and it does not make sense to expose the entire user
base to any risk stemming from this change, given that this change is
of use only to a few users running extremely heavy workloads.

Therefore, this commit allows users to specify realtime priorities
for the grace-period kthreads, but leaves them running SCHED_OTHER
by default.  The realtime priority may be specified at build time
via the RCU_KTHREAD_PRIO Kconfig parameter, or at boot time via the
rcutree.kthread_prio parameter.  Either way, 0 says to continue the
default SCHED_OTHER behavior and values from 1-99 specify that priority
of SCHED_FIFO behavior.  Note that a value of 0 is not permitted when
the RCU_BOOST Kconfig parameter is specified.

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