From: Ben Greear <greearb@candelatech.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Rask Ingemann Lambertsen <rask@sygehus.dk>, netdev@oss.sgi.com
Subject: Re: How to count tx and rx bytes?
Date: Tue, 16 Dec 2003 11:38:40 -0800 [thread overview]
Message-ID: <3FDF5F40.9060609@candelatech.com> (raw)
In-Reply-To: <20031216074520.40f59afd.rddunlap@osdl.org>
Randy.Dunlap wrote:
> On Tue, 16 Dec 2003 14:38:16 +0100 Rask Ingemann Lambertsen <rask@sygehus.dk> wrote:
>
> | On Mon, Dec 15, 2003 at 12:03:58PM -0800, Ben Greear 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?
> |
> | Should they include the frame padding in tx-bytes? Some do, some don't.
> | IMHO they should, because you do actually transmit those bytes on the wire.
>
> If you are referring to padding that is put there by software,
> then Yes.
The padding is often done in the NIC itself, and since the bytes are put
on the wire, they should be counted...
>
> --
> ~Randy
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2003-12-16 19:38 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
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 [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=3FDF5F40.9060609@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@oss.sgi.com \
--cc=rask@sygehus.dk \
--cc=rddunlap@osdl.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 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.