netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Seger <Mark.Seger@hp.com>
To: Michael Chan <mchan@broadcom.com>
Cc: Eric Dumazet <dada1@cosmosbay.com>,
	Ben Greear <greearb@candelatech.com>,
	netdev <netdev@vger.kernel.org>
Subject: Re: occasionally corrupted network stats in /proc/net/dev
Date: Mon, 14 Jan 2008 15:05:21 -0500	[thread overview]
Message-ID: <478BC081.70101@hp.com> (raw)
In-Reply-To: <1200343269.15122.23.camel@dell>

outstanding!  I'm just happy to hear it's not a bug in my monitoring 
code...  8-)
-mark

Michael Chan wrote:
> On Mon, 2008-01-14 at 20:12 +0100, Eric Dumazet wrote:
>   
>> Mark Seger a écrit :
>>     
>>> Ignore that last one as it was pointed out to me that we have both nic 
>>> installed on many of our systems and ethtool told me the one 
>>> associated with the nic is actually the broadcom one.
>>>
>>> version:        1.4.38 E1B1EC867DEEB8027B2DA0F
>>> license:        GPL
>>> description:    Broadcom NetXtreme II BCM5706/5708 Driver
>>>
>>>       
>> I remember some tg3 chips actually have bugs when reporting stats.... 
>> once in a while
>>
>> CCed to Michael Chan to get some details.
>>     
>
> Yes, that's right.  Some BNX2 chips have this problem and we have a
> workaround:
>
> http://git.kernel.org/?p=linux/kernel/git/davem/net-2.6.git;a=commit;h=02537b0676930b1bd9aff2139e0e645c79986931
>
> The chip sometimes DMA wrong counter values if the chip is also
> internally gathering the counters at the time of the DMA.
>
> Driver 1.5.11 and later versions have this workaround.
>
>
>   


      reply	other threads:[~2008-01-14 20:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-14 17:20 occasionally corrupted network stats in /proc/net/dev Mark Seger
2008-01-14 17:38 ` Eric Dumazet
2008-01-14 18:08 ` Ben Greear
2008-01-14 18:24   ` Mark Seger
2008-01-14 18:51     ` Mark Seger
2008-01-14 19:01       ` Ben Greear
2008-01-14 19:12       ` Eric Dumazet
2008-01-14 20:41         ` Michael Chan
2008-01-14 20:05           ` Mark Seger [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=478BC081.70101@hp.com \
    --to=mark.seger@hp.com \
    --cc=dada1@cosmosbay.com \
    --cc=greearb@candelatech.com \
    --cc=mchan@broadcom.com \
    --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;
as well as URLs for NNTP newsgroup(s).