On Sat, 2006-11-25 at 03:55 +0200, Itay Duvdevani wrote: > It seems like the timer generates most of the interrupts, which makes > sense. But can it possibly be the reason for the 30% usage? > > Anyways, since I'm a bit unfamiliar with the /proc/interrupts format: > > CPU0 > 0: 6772583 IO-APIC-edge timer > 1: 4929 IO-APIC-edge i8042 > 7: 3 IO-APIC-edge parport0 > 8: 1 IO-APIC-edge rtc > 9: 0 IO-APIC-level acpi > 14: 52691 IO-APIC-edge ide0 > 15: 242905 IO-APIC-edge ide1 > 169: 1006942 IO-APIC-level eth0 > 185: 53538 IO-APIC-level uhci_hcd:usb1, uhci_hcd:usb2, > uhci_hcd:usb3, ehci_hcd:usb4 > 193: 724 IO-APIC-level EMU10K1 > 201: 2089405 IO-APIC-level nvidia > NMI: 0 > LOC: 6772539 > ERR: 0 > MIS: 0 > > Thanks, > - Itay.
It's seems that the IRQ hitters are the eth0 and nVidia. Your eth0 card seems to be hitting a lot of traffic. (most of the packet handling is done in SI) Please post the output of $ ifconfig eth0 | egrep -e 'TX|RX' What chipset does your ethernet card use? Which driver are you using? Oh... do you have iptables enabled? Routing? As for the nvidia driver - well, the interrupt count seems a bit high - though AFAIK, nVidia doesn't do too much work in SI. Which driver are you using? - Gilboa ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
