From: "Eilon Greenstein" <eilong@broadcom.com>
To: "Tore Anderson" <tore.anderson@redpill-linpro.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Benjamin Li" <benli@broadcom.com>
Subject: Re: "NIG timer max" messages from bnx2x
Date: Thu, 3 Dec 2009 09:47:22 +0200 [thread overview]
Message-ID: <1259826442.15524.2.camel@lb-tlvb-eilong> (raw)
In-Reply-To: <4B176A86.30009@redpill-linpro.com>
On Wed, 2009-12-02 at 23:36 -0800, Tore Anderson wrote:
> However I'm still a bit confused on why this is triggering the "NIG
> timer max" message on the Linux blade. It would have made perfect sense
> to me for the bnx2x driver/NIC to stop transmitting outbound frames if
> it was the recipient of an inbound pause frame flood, but tcpdump does
> not show any such frames being received. Yet it stalls all outbound
> traffic. Any idea why?
>
The pause frames are processed in the HW and therefore not visible to
tcpdump. You should be able to see the pause counter increases in
"ethtool -S".
Regards,
Eilon
prev parent reply other threads:[~2009-12-03 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 16:00 "NIG timer max" messages from bnx2x Tore Anderson
2009-12-02 18:41 ` Eilon Greenstein
2009-12-03 7:36 ` Tore Anderson
2009-12-03 7:47 ` Eilon Greenstein [this message]
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=1259826442.15524.2.camel@lb-tlvb-eilong \
--to=eilong@broadcom.com \
--cc=benli@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=tore.anderson@redpill-linpro.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