Lines Matching +full:always +full:- +full:running
6 nice-levels implementation in the new Linux scheduler.
8 Nice levels were always pretty weak under Linux and people continuously
34 -*----------------------------------*-----> [nice level]
35 -20 | +19
49 people were running number crunching apps at nice +19.)
52 right minimal granularity - and this translates to 5% CPU utilization.
53 But the fundamental HZ-sensitive property for nice+19 still remained,
56 too _strong_ :-)
58 To sum it up: we always wanted to make nice levels more consistent, but
79 depend on the nice level of the parent shell - if it was at nice -10 the
94 support: with the new scheduler nice +19 tasks get a HZ-independent
95 1.5%, instead of the variable 3%-5%-9% range they got in the old
101 scheduler, running a nice +10 and a nice 11 task has the same CPU
102 utilization "split" between them as running a nice -5 and a nice -4
104 levels were changed to be "multiplicative" (or exponential) - that way
106 result' will always be the same.
112 side-effect of the recalibrated dynamic range of nice levels.