From: Ben Greear <greearb@candelatech.com>
To: Mark Seger <Mark.Seger@hp.com>
Cc: netdev@vger.kernel.org
Subject: Re: occasionally corrupted network stats in /proc/net/dev
Date: Mon, 14 Jan 2008 11:01:42 -0800 [thread overview]
Message-ID: <478BB196.7050300@candelatech.com> (raw)
In-Reply-To: <478BAF47.10607@hp.com>
Mark Seger wrote:
> 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
Ok, we do a similar stats polling, though through a private ioctl I
hacked into the kernel to
get the netdev->stats struct with a memcpy. I haven't noticed any
problems with counters
in the e1000 driver. I haven't done enough testing on bcm drivers to
ascertain whether it's
reliable or not w/regard to stats.
If you can reproduce the problem with e1000, it would be worth looking
at the logic that prints
out the proc interface text for problems..and if you cannot, then maybe
it's the bcm driver that
is at issue.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2008-01-14 19:01 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 [this message]
2008-01-14 19:12 ` Eric Dumazet
2008-01-14 20:41 ` Michael Chan
2008-01-14 20:05 ` Mark Seger
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=478BB196.7050300@candelatech.com \
--to=greearb@candelatech.com \
--cc=Mark.Seger@hp.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).