--Jeff Garzik <[EMAIL PROTECTED]> wrote (on Saturday, February 19, 2005 11:30:53 -0500):
Pallipadi, Venkatesh wrote:
You are right. Kernel balancer doesn't move around the irqs, unless it has too many interrupts. The logic is moving around interrupts all the time will not be good on caches. So, there is a threshold above which the balancer start moving things around.
You should see them moving around if you do 'ping -f' or a big 'dd' from the disk.
If kirqd is moving NIC interrupts, it's broken.
(and another reason why irqbalanced is preferable)
Why is it broken to move NIC interrupts? Obviously you don't want to
rotate them around a lot, but in the interests of fairness to other processes, it seems reasonable to migrate them occasionally (IIRC, kirqd
rate limits to once a second or something).
This has been explained to you before, search your email archives...
The main problem that has been seen in the field SMP packet ordering, but a secondary problem observed is cache misses. Just NAPI mitigates this somewhat (no pun intended).
Overall, kirqd should be avoided except in special situations. It doesn't know about such policy things as network-specific or storage-specific irq balancing (and shouldn't).
Jeff
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
