From: Steve Modica <modica@sgi.com>
To: netdev@oss.sgi.com
Subject: High interrupt rate on tg3 driver
Date: Wed, 05 Nov 2003 14:41:46 -0600 [thread overview]
Message-ID: <3FA9608A.1020706@sgi.com> (raw)
Hi All,
It turns out that there's a hardware bug that can cause a missed interrupt with
the 570X chipset. So the tg3 driver will poke the card every 10msec to make
sure we don't miss one. Each of these pokes generates an interrupt.
However this still doesn't explain the high interrupt rate I'm seeing. I'm
seeing about 22k/sec when moving 500kBytes/sec of data.
I've got 5 cards ports on the system, so I can account for 500/sec, and I could
even see each NAPI interrupt/poll cycle generating a few hundred a sec, but
22000 seems like way too many.
Can anyone think of a real good way to capture this? Profiling just shows me
spending a lot of time in tg3_poll, do_csum and memcpy.
Steve
--
Steve Modica
work: 651-683-3224
MTS-Technical Lead
"Give a man a fish, and he will eat for a day, hit him with a fish and
he leaves you alone" - me
reply other threads:[~2003-11-05 20:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3FA9608A.1020706@sgi.com \
--to=modica@sgi.com \
--cc=netdev@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).