* Different scheduler behavior between 2.4 and 2.6
@ 2007-05-10 5:46 Quan Sun
0 siblings, 0 replies; only message in thread
From: Quan Sun @ 2007-05-10 5:46 UTC (permalink / raw)
To: linux-kernel
Hi,
Recently I met a problem on different scheduler behavior between
2.4.22 and 2.6.18.8.
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 2.6.18.8, if I turn on 'noirqbalance' kernel parameter, and no
irqbalance process, 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.
/proc/interrupt shows all eths's interrupts are working at CPU0.
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2007-05-10 5:47 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-05-10 5:46 Different scheduler behavior between 2.4 and 2.6 Quan Sun
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®