>> I am (or rather, will be once 2.2 stabilizes) working
>> on the exact opposite: SCHED_IDLE processes which only
>> run when the system's got nothing else to do.
>
> I already have something like that. It's a modification of how niceness
> values are interpreted. It uses a range of 11 niceness values to get
> the processor, e.g. when there's a process running at nice=0 then no
> proces with nice=11 or higher will get the cpu. On the other hand, if
> there's a process running at nice=-11 (eg. timidity or mikmod) then no
> 'normal' process will get the cpu. Processes started just with nice
> will still get a little bit of the cpu as usual (that's why the
> range is 11 and not 10).
I like this very much.
Wasn't there a problem with kernel locks though? Maybe it involved
a low-priority process renaming directories, then a high-priority
process waking up and trying to do the same thing. That might not
be it exactly, but there was some kind of problem with idle eaters.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/