public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: netdev@vger.kernel.org
Subject: Exact meaning of rx_bytes and tx_bytes
Date: Mon, 9 Oct 2006 17:39:02 +0200	[thread overview]
Message-ID: <200610091739.02361.jdelvare@suse.de> (raw)

Hi all,

I am wondering what exactly the rx_bytes and tx_bytes values exported 
under statistics/ in sysfs are supposed to represent.

Most popular ethernet drivers (8139too, e100, 3c59x) count the bytes in 
software, so they only take into account the bytes they actually send and 
receive. This excludes the 4-byte ethernet CRC if I understand correctly.

Other drivers, on the other hand, get the transfered bytes statistics from 
hardware registers, and these appear to include the 4-byte CRC in the 
total count. This is the case of sk98lin and e1000, for example.

So my question is, which drivers are right? Are we counting the emitted 
and received bytes at software level or at hardware level? Or do we just 
not care about the 4-byte/packet difference and both are acceptable?

Thanks,
-- 
Jean Delvare
Suse L3

             reply	other threads:[~2006-10-09 15:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-09 15:39 Jean Delvare [this message]
2006-10-09 16:22 ` Exact meaning of rx_bytes and tx_bytes Stephen Hemminger

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=200610091739.02361.jdelvare@suse.de \
    --to=jdelvare@suse.de \
    --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