From: "Michael Chan" <mchan@broadcom.com>
To: "David Miller" <davem@davemloft.net>
Cc: harald@iki.fi, linux-kernel@vger.kernel.org,
netdev <netdev@vger.kernel.org>
Subject: Re: tg3 bad performance, lots of hardware interrupts
Date: Thu, 27 Mar 2008 17:01:38 -0800 [thread overview]
Message-ID: <1206666100.5368.6.camel@dell> (raw)
In-Reply-To: <20080327.144925.196529669.davem@davemloft.net>
On Thu, 2008-03-27 at 14:49 -0700, David Miller wrote:
> From: Harald Hannelius <harald@iki.fi>
> Date: Thu, 27 Mar 2008 15:53:56 +0200 (EET)
>
> > I experience a lot of hardware interrupts with a BCM5751 PCI-express NIC
> > (tg3). modprobe tg3, ifconfig ethX up and friends makes the system
> > unresponsive. Just having the interface up makes the system sluggish.
> >
I just tested a similar NIC using the same kernel and driver, but I did
not notice anything unusual. netperf gave me 941Mbps.
> > Onboard forcedeth works fine (with the same cable).
> >
> > iperf gives me just 2Mbps on a 1Gbps ethernet. Load average near 1.0. top
> > reports 40-50%hi (hardware interrupts) when generating traffic over that
> > interface.
Can you look at /proc/interrupts to see roughly how many are reported
per second when link is down, link is up with no traffic, and with
traffic?
Finally, you can also try ethtool -t eth0 to see if it passes a simple
self test.
next prev parent reply other threads:[~2008-03-28 0:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 13:53 tg3 bad performance, lots of hardware interrupts Harald Hannelius
2008-03-27 21:49 ` David Miller
2008-03-28 1:01 ` Michael Chan [this message]
2008-03-28 13:04 ` Harald Hannelius
2008-03-28 17:49 ` Michael Chan
2008-03-28 17:12 ` Jiri Kosina
2008-03-28 17:37 ` Harald Hannelius
2008-03-28 19:06 ` Michael Chan
2008-03-28 18:09 ` Harald Hannelius
2008-04-02 8:55 ` Harald Hannelius
2008-03-28 17:31 ` Harald Hannelius
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=1206666100.5368.6.camel@dell \
--to=mchan@broadcom.com \
--cc=davem@davemloft.net \
--cc=harald@iki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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.