netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mirko Lindner <demon@pro-linux.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: krishnakumar@naturesoft.net, mlindner@syskonnect.de,
	netdev@oss.sgi.com, felix@allot.com
Subject: Re: [PATCH]sk98lin ethtool support
Date: Wed, 31 Dec 2003 01:37:22 +0000	[thread overview]
Message-ID: <3FF22852.3060101@pro-linux.de> (raw)
In-Reply-To: <3FF2170D.5070302@pobox.com>

Jeff,

> Well, understood, but we don't need vendor-specific, non-standard 
> statistics when there is a standard method to export these statistics 
> (ETHTOOl_GSTATS).

I agree with you.


> Make sure you don't duplicate any ethtool functions.  We don't need a 
> NIC-specific diag tool either ;-)  ethtool is the preferred method 
> moving forward, as it's already shipping in most Linux distros.

Yes, we need it ;) No kidding! This is not a tool for SW checks like 
media, link or driver version checks, but a tool for HW checks like 
register, PROM, MAC, PHY and some other chip and card checks. The 
ethtool is a great tool, but the intention of this tool is not the same.

Mirko

  reply	other threads:[~2003-12-31  1:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-30 10:24 [PATCH]sk98lin ethtool support Krishnakumar. R
2003-12-30 12:27 ` Mirko Lindner
2003-12-30 12:29   ` Felix Radensky
2003-12-30 15:14   ` Jeff Garzik
2003-12-31  1:15     ` Mirko Lindner
2003-12-31  0:23       ` Jeff Garzik
2003-12-31  1:37         ` Mirko Lindner [this message]
     [not found] <C6F5CF431189FA4CBAEC9E7DD5441E0103424AA4@orsmsx402.jf.intel.com>
2004-01-02  8:00 ` Feldman, Scott
2004-01-02 14:23   ` Mirko Lindner

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=3FF22852.3060101@pro-linux.de \
    --to=demon@pro-linux.de \
    --cc=felix@allot.com \
    --cc=jgarzik@pobox.com \
    --cc=krishnakumar@naturesoft.net \
    --cc=mlindner@syskonnect.de \
    --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).