From: Eric Dumazet <eric.dumazet@gmail.com>
To: Michael Durket <durket@highwire.stanford.edu>
Cc: netdev@vger.kernel.org
Subject: Re: Question about tg3 and bnx2 driver suppliers
Date: Thu, 17 Feb 2011 15:17:35 +0100 [thread overview]
Message-ID: <1297952255.2604.115.camel@edumazet-laptop> (raw)
In-Reply-To: <3BA51C2C-B28F-4FED-BF5D-B9BF46EAF3F7@highwire.stanford.edu>
Le jeudi 17 février 2011 à 05:24 -0800, Michael Durket a écrit :
> I'm trying to fix a problem with packet drops and frame errors (really
> rxbds_empty and rx_discards (or rx_fw_discards depending on whether or
> not its a tg3 supported chip or a bnx2 chip)). We have this happening
> on pretty much all the RedHat 5.x systems we're running these drivers
> on. In investigating what remedies to employ to fix this, I'm trying
> to determine if new versions of this driver are supplied by Broadcom,
> or by people within the Linux community so
> I can find the right place to ask questions about it. I'm pretty sure
> this isn't the right list for these types of questions, but if someone
> could tell me whether I should be contacting Broadcom directly, or the
> name of some other Linux mailing list or forum that might help, I'd
> appreciate it.
>
It _is_ the right place, dont worry ;)
One possible cause of packet drops is when softirqs are disabled for too
long periods, even if NIC has a big RX ring (check ethtool -g eth0)
We fixed one big offender some weeks ago : iptables -L
Fix is in commit 83723d60717f8da0f53f
http://git2.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=83723d60717f8da0f53f91cf42a845ed56c09662
next prev parent reply other threads:[~2011-02-17 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 13:24 Question about tg3 and bnx2 driver suppliers Michael Durket
2011-02-17 14:16 ` Ben Hutchings
2011-02-17 14:17 ` Eric Dumazet [this message]
2011-02-20 18:19 ` Micha Nelissen
2011-02-20 19:17 ` Eric Dumazet
2011-02-20 20:41 ` Stephen Hemminger
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=1297952255.2604.115.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=durket@highwire.stanford.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox