Skip to contentSkip to conversation

excessive interrupts on network cards

DISCUSSION Chris Newton 3 participants 3 messages Sep 25, 2001

lore
Share & tools
lore
#0 lore raw

Hi,

I 'think' the number of interrupts being generated for the network traffic I
monitor, is excessive. Having talked quikly with Donald Becker, he indicated that I should be seeing a little less than the number of RX/TX packets/s on a wire, in terms of interrupts/s. That, however, is not what I am seeing. I am seeing 3 times as many interrupts/s as I am seeing packets/s.

I have used three network devices to look at the stream I am monitoring, and
it is usually aorund 5K packet/s IN, and 5K out, fed full duplex into a single 3Com 3c982 (2.4.10 kernel reports that anyways). However, watching:

'procinfo -D', reports on the order of 30,000 interrupts per second.

This page:

http://www.scyld.com/network/3c509.html

has a snipet:

"some other device or device driver hogging the bus or disabling interrupts.
Check /proc/interrupts for excessive interrupt counts. The timer tick interrupt should always be incrementing faster than the others. "

Well, looking at this machine, since it booted 57 minutes ago:

[root@phantom /proc]# more interrupts
CPU0 CPU1

  0:     172754     171041    IO-APIC-edge  timer
  1:          0          3    IO-APIC-edge  keyboard
  2:          0          0          XT-PIC  cascade
 14:          2          2    IO-APIC-edge  ide0
 16:      87361      87539   IO-APIC-level  eth2
 20:    6798697    6799977   IO-APIC-level  eth0
 21:          0          0   IO-APIC-level  eth1
 30:      11837      11806   IO-APIC-level  aic7xxx
 31:     199418     199209   IO-APIC-level  aic7xxx
NMI:          0          0
LOC:     343669     343708
ERR:          0
MIS:          0

In 57 minutes, that ethernet card has generated: 14,000,459 interrupts.

Isn't this excessive?

I also have a different brand card on board... an intel ether express pro.
So... I swapped the cables so that the intel card would see that network
stream. Well, it caused even more interrupts per second. (more like 40K).

I have tried kernel 2.4.9, 2.4.2 (redhat 7.1 version), and just now, 2.4.10,
all SMP builds, on a dual 1 GHz PIII, with 1 GB of SDRAM, Adaptec 7899 Ultra160 controller, two 3c982 netcards and one onboard intel etherexpress pro 100 cards.

Guess my question is, first of.. is this normal?

#1 lore raw
Quoted 9 lines · Chris Newton

Hi,

I 'think' the number of interrupts being generated for the network traffic I
monitor, is excessive. Having talked quikly with Donald Becker, he indicated that I should be seeing a little less than the number of RX/TX packets/s on a wire, in terms of interrupts/s. That, however, is not what I am seeing. I am seeing 3 times as many interrupts/s as I am seeing packets/s.

Quoted 3 lines

I have used three network devices to look at the stream I am monitoring, and
it is usually aorund 5K packet/s IN, and 5K out, fed full duplex into a single 3Com 3c982 (2.4.10 kernel reports that anyways). However, watching:

3c982 is a dual-port server NIC. Is your card dual-port? If not, it's probably a 3c980, and I goofed :)

Quoted 1 line

'procinfo -D', reports on the order of 30,000 interrupts per second.

That does sound rather high. You should compare the interrupt rate with the packet rate from `ifconfig' or /proc/net/dev.

Normally, 3c59x will show approx three Tx packets per interrupt and one Rx packet per interrupt. It varies with workload, but it tends to vary in the "good" direction - at higher packet rates, we do more work in a single interrupt and the interrupt-per-packet rate falls.

#2 lore raw
In reply to Chris Newton
Quoted 5 lines

I 'think' the number of interrupts being generated for the network traffic I
monitor, is excessive. Having talked quikly with Donald Becker, he indicated that I should be seeing a little less than the number of RX/TX packets/s on a wire, in terms of interrupts/s. That, however, is not what I am seeing. I am seeing 3 times as many interrupts/s as I am seeing packets/s.

Also check context switches and TX/RX errors. Reference point as follows.

rgds,
tim.

*****
10MB file copy, scp v1.68, switched private LAN:

Clocktime: 9 sec
Receiver IRQ/sec: 599
Receiver context switch/sec: 1271
Receiver bytes/IRQ: 1935

NIC driver (both):
tulip.c:v0.91g-ppc 7/16/99 [email protected]

Sender: 2.2.20pre6, i586@166MHz
eth1: Lite-On 82c168 PNIC rev 32 at 0x6200, 00:A0:CC:58:F8:CE, IRQ 10.
eth1: MII transceiver #1 config 3000 status 782d advertising 01e1.
eth1: Setting full-duplex based on MII#1 link partner capability of 41e1.
eth1 Link encap:Ethernet HWaddr 00:A0:CC:58:F8:CE

          inet addr:192.168.1.11  Bcast:192.168.1.255 
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2230475 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3785425 errors:3 dropped:0 overruns:3 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:10 Base address:0x6200 

Receiver: 2.2.20pre10, Athlon@850MHz
eth0: Lite-On 82c168 PNIC rev 32 at 0xec00, 00:A0:CC:57:89:93, IRQ 11.
eth0: MII transceiver #1 config 3000 status 7829 advertising 01e1.
eth0: Setting full-duplex based on MII#1 link partner capability of 41e1.
eth0 Link encap:Ethernet HWaddr 00:A0:CC:57:89:93

          inet addr:192.168.1.10  Bcast:192.168.1.255 
Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2741953 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1606566 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:11 Base address:0xec00 
Signature · 1 line
  |  650.390.9613 - 650.224.7437c