> Also, I don't really see why the QNX scheduler would cause OOPSen in
> <select_dcache>, and also why most people on this list have an aversion to
> the QNX Scheduler patch, which I have used on this machine since version
> 1.06 on 2.0.31, and which has been rock-solid ever since, as has 2.1.65
> apart from the OOPSen I sent in earlier.
> What I like most about the QNX scheduler, is that I can leave a password
> cracker going in the background, at a low priority, and it will only use
> CPU time when nothing else wants the CPU, so it doesn't affect performance
> at all.
>
> Also, with the QNX sheduler in place I have been able to push my
> load average to 1000 and over (with a forkbomb and ulimit -u 1024) and
> the system was still very responsive from my root login. (which I had
> niced negatively.)
>
> It's worth looking at, and should IMHO be considered for inclusion in
> 2.1.X, if only as a config/Makefile option.
I'd like to give it a spin, but I seem to have lost any other references
to it. From the description I read a while ago, it seems like a very
solid scheduling technique. I really like the sound of continued
responsiveness despite CPU-intensive background processes. Where can the
patch be found? (I've checked the various kernel sites.)
+----------------------------------------->
| Aron Griffis (agriffis@coat.com)
| Burlington Coat Factory - Network Group
+----------------------------------------->