Just wanted to let you gentlemen know that I'm still alive.. and I'm in
the process of writing te patch (and userspace) to implement my idea. in
fact, it's 90% done. then I'll be able to do some benchmarks and see if's
is a GoodThing(tm)...
The problem I'm having now is that I can pin a process to a cpu (code to
add the functionality to the prctl call was stolen from a patch Dimitris
made to the kernel list a few month ago), and shut off all other
scheduling/interrupts/and tasklets(not efficiently, but it seems to
work)... and it works like a charm if I don't change the scheduler.
But when I change the process to SCHED_FIFO, with a priority of 99, it
appearently gets scheduled on the System CPU, and softlocks the system (I
have a dual proc machine, 1 system cpu, and one app cpu.. so if it gets
scheduled on the system cpu, then nothing else can run until its
done... its supposed to go on the app cpu)..... ugh.. soo close...
SO once I figure that out, I'll be posting a preliminary patch up here to
see what people think... then I'll post some benchmarks and release it all
for real, for better or for worse...
john.c
|