Different scheduler behavior between 2.4 and 2.6

From: Quan Sun
Date: Mon Apr 30 2007 - 02:23:33 EST

Recently I met a problem on different scheduler behavior between
2.4.22 and
The application works as a proxy, it listen on an interface,
connect through another interface. This application works on a box
with two Xeon cpu, each of them is hyper-threading.
On 2.4.22, CPU0 serve interrupts, the application works on other
three CPUs.
But on, if I turn on 'noirqbalance' kernel parameter, the
application will stuck to CPU0 as well as interrupts after several
seconds' working. Then there will be a 0% idle cpu, and three 100%
idle CPUs.
I have also tried irqbalance on, but the performance is
not as good as 2.4.22 too.
It seems that scheduler ignores the working load of interrupts.

My question is, is there a way to tune 2.6 kernel working as 2.4?
Just one cpu for interrupts, other three cpu for normal work.

Quan Sun
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html