From: Ben Greear <greearb@candelatech.com>
To: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: Getting physical packet counts with LRO enabled with ixgbe?
Date: Wed, 23 Sep 2009 14:37:13 -0700 [thread overview]
Message-ID: <4ABA9509.7000008@candelatech.com> (raw)
In-Reply-To: <1253730766.2538.28.camel@localhost.localdomain>
I noticed that 'ethtool -d' has some counters that may be right,
including bytes.
(I'm looking at the 82599 chipset currently)
0x04074: gprc (Good Packets Received Count) 0xF611E2C2
0x04078: bprc (Broadcast Packets Rx Count) 0x00000000
0x0407C: mprc (Multicast Packets Rx Count) 0x0000000C
0x04080: gptc (Good Packets Transmitted Count) 0xC9962C10
0x04088: gorcl (Good Octets Rx Count Low) 0x9A23F0B0
0x0408C: gorch (Good Octets Rx Count High) 0x00000000
0x04090: gotcl (Good Octets Tx Count Low) 0x5DFAACD4
0x04094: gotch (Good Octets Tx Count High) 0x00000000
Any suggestions on a more efficient way to get these than dumping 'ethtool -d' and
searching all that data? Maybe put it in 'ethtool -S' as well ?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2009-09-23 21:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 16:40 Getting physical packet counts with LRO enabled with ixgbe? Ben Greear
2009-09-23 18:32 ` Peter P Waskiewicz Jr
2009-09-23 18:46 ` Ben Greear
2009-09-23 18:50 ` Peter P Waskiewicz Jr
2009-09-23 18:56 ` Ben Greear
2009-09-23 19:03 ` Rick Jones
2009-09-25 21:45 ` Herbert Xu
2009-09-25 21:50 ` Ben Greear
2009-09-25 21:59 ` David Miller
2009-09-25 22:01 ` Herbert Xu
2009-09-25 22:12 ` Ben Greear
2009-09-25 22:40 ` Peter P Waskiewicz Jr
2009-09-25 22:09 ` Herbert Xu
2009-09-25 21:56 ` Peter P Waskiewicz Jr
2009-09-25 22:10 ` Herbert Xu
2009-09-23 21:37 ` Ben Greear [this message]
2009-09-23 21:56 ` Ben Greear
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=4ABA9509.7000008@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.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 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.