Lines Matching refs:it

8 scheduler, (otherwise we'd have done it long ago) because nice level
16 understand it, the timeslice graph went like this (cheesy ASCII art
40 HZ=1000 it caused 1 jiffy to be 1 msec, which meant 0.1% CPU usage which
41 we felt to be a bit excessive. Excessive _not_ because it's too small of
42 a CPU utilization, but because it causes too frequent (once per
51 terms of CPU utilization, we only got complaints about it (still) being
54 To sum it up: we always wanted to make nice levels more consistent, but
56 coupling to timeslices and granularity it was not really viable.
75 depend on the nice level of the parent shell - if it was at nice -10 the
76 CPU split was different than if it was at +5 or +10.
89 it was possible to implement better and more consistent nice +19
101 it does not matter which nice level you start out from, the 'relative