* High interrupt rate even when using NAPI
@ 2003-11-05 18:03 Steve Modica
2003-11-05 18:07 ` David S. Miller
0 siblings, 1 reply; 2+ messages in thread
From: Steve Modica @ 2003-11-05 18:03 UTC (permalink / raw)
To: netdev
Hi All,
I just noticed some strange behavior with the tg3 driver.
Even with NAPI enabled, during high loads of 1500 byte MTUS, I'm seeing a very
high interrupt rate. To move 500kBytes/sec I'm seeing 22k interrupts/sec. It
tracks very closely with the actualy throughput.
That amounts to about 1 interrupt per 23 bytes. I figured with NAPI, we should
do a lot better than that.
Is there a tuneable or some driver stat that I can track to figure out what's
happening here? I'd like to see that interrupt number be a lot lower.
Steve
--
Steve Modica
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: High interrupt rate even when using NAPI
2003-11-05 18:03 High interrupt rate even when using NAPI Steve Modica
@ 2003-11-05 18:07 ` David S. Miller
0 siblings, 0 replies; 2+ messages in thread
From: David S. Miller @ 2003-11-05 18:07 UTC (permalink / raw)
To: Steve Modica; +Cc: netdev
On Wed, 05 Nov 2003 12:03:46 -0600
Steve Modica <modica@sgi.com> wrote:
> I just noticed some strange behavior with the tg3 driver.
The tg3 driver needs to poke the chip a hundred times per
second in order to work around a hardware bug, eack poke
causes an interrupt. This is needed regardless of whether
the chip is processing packets or not.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-11-05 18:07 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-11-05 18:03 High interrupt rate even when using NAPI Steve Modica
2003-11-05 18:07 ` David S. Miller
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).