From: Ben Greear <greearb@candelatech.com>
To: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: How to count tx and rx bytes?
Date: Mon, 15 Dec 2003 12:03:58 -0800 [thread overview]
Message-ID: <3FDE13AE.3050402@candelatech.com> (raw)
Is there an agreed upon standard for exactly what ethernet drivers
should be counting for rx-bytes and tx-bytes? For example, should the
counters include the 4-byte FCS? Should they include the ethernet header?
From what I can tell, various drivers count the rx and tx bytes differently,
which cannot be correct....
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2003-12-15 20:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 20:03 Ben Greear [this message]
2003-12-15 22:17 ` How to count tx and rx bytes? David S. Miller
2003-12-15 22:40 ` Randy.Dunlap
2003-12-15 23:19 ` Donald Becker
2003-12-15 23:22 ` Randy.Dunlap
2003-12-15 22:46 ` Ben Greear
2003-12-15 22:54 ` David S. Miller
2003-12-15 23:17 ` Ben Greear
2003-12-16 0:08 ` David S. Miller
2003-12-16 13:38 ` Rask Ingemann Lambertsen
2003-12-16 15:45 ` Randy.Dunlap
2003-12-16 19:38 ` 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=3FDE13AE.3050402@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).