I think this will confuse atd too, which is an obvious candidate
for the batch scheduler; it may end up starting all jobs which
sit in it's "batch" queue.
I think a load-average calculation scheme like this would be better:
oldload: is the load average calculated the old way
batchload: is the load average calculated only from the batch scheduler
numcpus: number of cpus...
newload(){
if (oldload > numcpus) return oldload;
if ((oldload+batchload) > numcpus) return numcpus;
return (oldload+batchload)
}
So the batch processes would show the CPUs maxed out, but would not show
up as overload in the load average. (and you could run
"atd -l <numcpus - 0.3>")
regards:
Gabor Vitez
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/