From: Andrew Morton <akpm@zip.com.au>
To: Chris Newton <newton@unb.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: excessive interrupts on network cards
Date: Tue, 25 Sep 2001 13:01:53 -0700 [thread overview]
Message-ID: <3BB0E2B1.6DCCF9DF@zip.com.au> (raw)
In-Reply-To: <3BB0E01D@webmail1>
Chris Newton wrote:
>
> 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:
3c982 is a dual-port server NIC. Is your card dual-port? If not, it's probably
a 3c980, and I goofed :)
> '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.
next prev parent reply other threads:[~2001-09-25 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 19:20 excessive interrupts on network cards Chris Newton
2001-09-25 20:01 ` Andrew Morton [this message]
2001-09-25 20:36 ` Tim Moore
-- strict thread matches above, loose matches on Subject: below --
2001-09-25 21:38 Chris Newton
2001-09-25 21:42 ` Benjamin LaHaise
2001-09-25 22:32 Chris Newton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BB0E2B1.6DCCF9DF@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=newton@unb.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.