Lines Matching +full:three +full:- +full:level
6 nice-levels implementation in the new Linux scheduler.
12 scheduler, (otherwise we'd have done it long ago) because nice level
19 rule so that nice +19 level would be _exactly_ 1 jiffy. To better
34 -*----------------------------------*-----> [nice level]
35 -20 | +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_ :-)
59 within the constraints of HZ and jiffies and their nasty design level
63 about Linux's nice level support was its asymmetry around the origin
65 accurately: the fact that nice level behavior depended on the _absolute_
66 nice level as well, while the nice API itself is fundamentally
74 Note that the 'inc' is relative to the current nice level. Tools like
79 depend on the nice level of the parent shell - if it was at nice -10 the
82 A third complaint against Linux's nice level support was that negative
88 The new scheduler in v2.6.23 addresses all three types of complaints:
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
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
105 it does not matter which nice level you start out from, the 'relative
112 side-effect of the recalibrated dynamic range of nice levels.