From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "David S. Miller" <davem@redhat.com>
Cc: greearb@candelatech.com, netdev@oss.sgi.com
Subject: Re: How to count tx and rx bytes?
Date: Mon, 15 Dec 2003 14:40:49 -0800 [thread overview]
Message-ID: <20031215144049.7acea87e.rddunlap@osdl.org> (raw)
In-Reply-To: <20031215141729.15387fc1.davem@redhat.com>
On Mon, 15 Dec 2003 14:17:29 -0800 "David S. Miller" <davem@redhat.com> wrote:
| On Mon, 15 Dec 2003 12:03:58 -0800
| Ben Greear <greearb@candelatech.com> wrote:
|
| > 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?
|
| Good question.
|
| It should be that all drivers use what skb->len ends up with at
| rx/tx time.
|
| However, it is often faster to just let the hardware keep track
| of these statistics (tg3 is one example of a chip that can do
| this). And sometimes these mechanisms take the FCS or whatever
| into account and this as you note makes the numbers different.
RFC 1573:
RFC 2233:
RFC 1213:
all agree that on an "interface" the number of octets received (InOctets)
is:
The total number of octets received on the interface, including
framing characters.
so I read that as including MAC headers and FCS. Without reading
these, I would have said include MAC headers but not FCS.
Similar for OutOctets.
--
~Randy
MOTD: Always include version info.
next prev parent reply other threads:[~2003-12-15 22:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 20:03 How to count tx and rx bytes? Ben Greear
2003-12-15 22:17 ` David S. Miller
2003-12-15 22:40 ` Randy.Dunlap [this message]
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=20031215144049.7acea87e.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=davem@redhat.com \
--cc=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).