Re: [patch] 2.4.1, 2.4.2-pre3: APIC lockups
Manfred Spraul (firstname.lastname@example.org)
Tue, 13 Feb 2001 23:18:09 +0100
"Maciej W. Rozycki" wrote:
> After performing various tests I came to the following workaround for
> APIC lockups which people observe under IRQ load, mostly for networking
> stuff. I believe the test should work in all cases as it basically
> implements a manual replacement for EOI messages. In my simulated
> environment I was unable to get a lockup with the code in place, even
> though I was getting about every other level-triggered IRQ misdelivered.
> Please test it extensively, as much as you can, before I submit it for
> inclusion. If you ever get "Aieee!!! Remote IRR still set after unlock!"
> message, please report it to me immediately -- it means the code failed.
> There is also an additional debugging/statistics counter provided in
> /proc/cpuinfo that counts interrupts which got delivered with its trigger
> mode mismatched. Check it out to find if you get any misdelivered
> interrupts at all.
I'm running my default webserver load test, and I get ~40 /second, 92735
bw_tcp says 1.13 MB/sec, that's wire speed.
tcpdump | grep 'sack ' doesn't show unusually many lost packets.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/