aboutsummaryrefslogtreecommitdiffstats
path: root/init/Kconfig
diff options
context:
space:
mode:
authorPaul E. McKenney <paul.mckenney@linaro.org>2012-04-18 19:20:18 -0400
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>2012-04-24 23:54:50 -0400
commitc9336643e1440f4dfc89ad4ac6185813619abb8c (patch)
tree1a32e3f08548a4b55cd2ec93b240c11a361e74ca /init/Kconfig
parentf88022a4f650ac1778cafcc17d2e522283bdf590 (diff)
rcu: Clarify help text for RCU_BOOST_PRIO
The old text confused real-time applications with real-time threads, so that you pretty much needed to understand how this kernel configuration parameter worked to understand the help text. This commit therefore attempts to make the help text human-readable. Reported-by: Jörn Engel <joern@purestorage.com> Signed-off-by: Paul E. McKenney <paul.mckenney@linaro.org> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Diffstat (limited to 'init/Kconfig')
-rw-r--r--init/Kconfig23
1 files changed, 19 insertions, 4 deletions
diff --git a/init/Kconfig b/init/Kconfig
index 6cfd71d06463..85c6870ed476 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -515,10 +515,25 @@ config RCU_BOOST_PRIO
515 depends on RCU_BOOST 515 depends on RCU_BOOST
516 default 1 516 default 1
517 help 517 help
518 This option specifies the real-time priority to which preempted 518 This option specifies the real-time priority to which long-term
519 RCU readers are to be boosted. If you are working with CPU-bound 519 preempted RCU readers are to be boosted. If you are working
520 real-time applications, you should specify a priority higher then 520 with a real-time application that has one or more CPU-bound
521 the highest-priority CPU-bound application. 521 threads running at a real-time priority level, you should set
522 RCU_BOOST_PRIO to a priority higher then the highest-priority
523 real-time CPU-bound thread. The default RCU_BOOST_PRIO value
524 of 1 is appropriate in the common case, which is real-time
525 applications that do not have any CPU-bound threads.
526
527 Some real-time applications might not have a single real-time
528 thread that saturates a given CPU, but instead might have
529 multiple real-time threads that, taken together, fully utilize
530 that CPU. In this case, you should set RCU_BOOST_PRIO to
531 a priority higher than the lowest-priority thread that is
532 conspiring to prevent the CPU from running any non-real-time
533 tasks. For example, if one thread at priority 10 and another
534 thread at priority 5 are between themselves fully consuming
535 the CPU time on a given CPU, then RCU_BOOST_PRIO should be
536 set to priority 6 or higher.
522 537
523 Specify the real-time priority, or take the default if unsure. 538 Specify the real-time priority, or take the default if unsure.
524 539