• Home
  • Raw
  • Download

Lines Matching refs:nice

6 nice-levels implementation in the new Linux scheduler.
9 pestered us to make nice +19 tasks use up much less CPU time.
12 scheduler, (otherwise we'd have done it long ago) because nice level
16 In the O(1) scheduler (in 2003) we changed negative nice levels to be
19 rule so that nice +19 level would be _exactly_ 1 jiffy. To better
34 -*----------------------------------*-----> [nice level]
49 people were running number crunching apps at nice +19.)
51 So for HZ=1000 we changed nice +19 to 5msecs, because that felt like the
53 But the fundamental HZ-sensitive property for nice+19 still remained,
54 and we never got a single complaint about nice +19 being too _weak_ in
58 To sum it up: we always wanted to make nice levels more consistent, but
63 about Linux's nice level support was its assymetry around the origo
65 accurately: the fact that nice level behavior depended on the _absolute_
66 nice level as well, while the nice API itself is fundamentally
69 int nice(int inc);
74 Note that the 'inc' is relative to the current nice level. Tools like
75 bash's "nice" command mirror this relative API.
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
83 nice levels were not 'punchy enough', so lots of people had to resort to
90 To address the first complaint (of nice levels being not "punchy"
92 (and granularity was made a separate concept from nice levels) and thus
93 it was possible to implement better and more consistent nice +19
94 support: with the new scheduler nice +19 tasks get a HZ-independent
98 To address the second complaint (of nice levels not being consistent),
99 the new scheduler makes nice(1) have the same CPU utilization effect on
100 tasks, regardless of their absolute nice levels. So on the new
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
103 task. (one will get 55% of the CPU, the other 45%.) That is why nice
105 it does not matter which nice level you start out from, the 'relative
108 The third complaint (of negative nice levels not being "punchy" enough
111 automatically: stronger negative nice levels are an automatic
112 side-effect of the recalibrated dynamic range of nice levels.