19 Aug, 2013
1 commit
-
This commit adds information about testing nohz_full, and also emphasizes
the fact that you need a multi-CPU system to get any benefit from nohz_full.Signed-off-by: Paul E. McKenney
Acked-by: Frederic Weisbecker
Reviewed-by: Josh Triplett
11 Jun, 2013
2 commits
-
This commit calls out the potential for slowing the tick even when there
are multiple runnable processes per CPU, It also points out that current
mainlined version keeps the tick going on at least one CPU even when all
CPUs are otherwise idle. Finally, it notes the need for a 1-HZ tick in
order to calculate CPU load, maintain sched average, compute CFS entity
vruntime, compute avenrun, and carry out load balancing.Signed-off-by: Paul E. McKenney
Reviewed-by: Josh Triplett -
Make it more clear that there are three options, and give hints as
to which of the three is most likely to be useful in different
situations.Reported-by: Sedat Dilek
Signed-off-by: Paul E. McKenney
Reviewed-by: Josh Triplett
28 Apr, 2013
1 commit
-
Signed-off-by: Paul E. McKenney
Cc: Frederic Weisbecker
Cc: Steven Rostedt
Cc: Borislav Petkov
Cc: Arjan van de Ven
Cc: Kevin Hilman
Cc: Christoph Lameter
Cc: Peter Zijlstra
Cc: Thomas Gleixner
Cc: Olivier Baetz
Reviewed-by: Randy Dunlap
Reviewed-by: Borislav Petkov
Reviewed-by: Kevin Hilman