From: Benjamin LaHaise <bcrl@redhat.com>
To: Chris Newton <newton@unb.ca>
Cc: Andrew Morton <akpm@zip.com.au>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: excessive interrupts on network cards
Date: Tue, 25 Sep 2001 17:42:04 -0400 [thread overview]
Message-ID: <20010925174203.C19494@redhat.com> (raw)
In-Reply-To: <3BB11992@webmail1>
In-Reply-To: <3BB11992@webmail1>; from newton@unb.ca on Tue, Sep 25, 2001 at 06:38:31PM -0300
On Tue, Sep 25, 2001 at 06:38:31PM -0300, Chris Newton wrote:
> Yea, it is a single port card... I had meant to mention that in the email I
> sent out... ie: that it wasn't reporting correctly... but, I didnt really
> think it was related, since the eepro was doing the same thing.
>
> As for comparing with ifconfig, I ran 'watch 1 ifconfig -a', and sure
> enough, I have about ~7000-7500 packets coming in right now. And, the
> 'procinfo -D', reports ~21000-22000 interrupts per second.
This is heavily dependant on the interrupt mitigation features that a card
has. At least for the ns83820 driver, I'm testing a technique where the
driver essentially switches to polled mode once the interrupt load goes
above a certain threshold, thereby limiting the load to ~2500 irq/sec.
Combined with carefully placed data prefetching, I'm seeing a huge increase
in performance. Of course, this comes at the expense of latency.
-ben
next prev parent reply other threads:[~2001-09-25 21:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-25 21:38 excessive interrupts on network cards Chris Newton
2001-09-25 21:42 ` Benjamin LaHaise [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-25 22:32 Chris Newton
2001-09-25 19:20 Chris Newton
2001-09-25 20:01 ` Andrew Morton
2001-09-25 20:36 ` Tim Moore
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=20010925174203.C19494@redhat.com \
--to=bcrl@redhat.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox