netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Snook <csnook@redhat.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: Linux Network Development list <netdev@vger.kernel.org>
Subject: Re: a maze of twisty stats, most different
Date: Thu, 28 Jun 2007 08:47:56 -0400	[thread overview]
Message-ID: <4683ADFC.4020000@redhat.com> (raw)
In-Reply-To: <46829C48.6080005@hp.com>

Rick Jones wrote:
> It seems that every driver, when providing support for ethtool -S 
> functionality, has considerable lattitude when it comes to the stats 
> provided.  Clearly this is very nice for the driver writer(s) as it 
> allows them to provide whatever stats they feel are most "natural" for 
> their NIC(s) and name them as they see fit.

This is deliberate.  Ethtool operates at a very primitive level, and generally 
does little or no translation between the hardware registers and userspace.

> However :)
> 
>  From the standpoint of someone looking from the outside, say someone 
> wanting to consume ethtool -S statistics, it seems to be a big jumble.
> 
> Might there be a way to bring those two camps together?  Is there 
> already, with the same wide availabilty of ethtool, and I've just not 
> seen it?

ifconfig comes to mind, for one.  What statistics are you looking for exactly?

	-- Chris

  reply	other threads:[~2007-06-28 12:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27 17:20 a maze of twisty stats, most different Rick Jones
2007-06-28 12:47 ` Chris Snook [this message]
2007-06-28 17:34   ` Rick Jones
2007-06-28 18:17     ` David Stevens
2007-06-28 20:36       ` David Miller
2007-06-28 21:21         ` Rick Jones
2007-06-29 17:30       ` Andi Kleen
2007-06-29 18:21         ` David Stevens
2007-06-29 19:37           ` Andi Kleen

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=4683ADFC.4020000@redhat.com \
    --to=csnook@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=rick.jones2@hp.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).