public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Jeff Garzik <jgarzik@mandrakesoft.mandrakesoft.com>
Cc: Donald Becker <becker@scyld.com>,
	linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [RFC] Configuring synchronous interfaces in Linux
Date: Sun, 03 Dec 2000 11:20:46 +1100	[thread overview]
Message-ID: <2776.975802846@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 02 Dec 2000 13:07:29 MDT." <Pine.LNX.3.96.1001202130202.1450B-100000@mandrakesoft.mandrakesoft.com>

On Sat, 2 Dec 2000 13:07:29 -0600 (CST), 
Jeff Garzik <jgarzik@mandrakesoft.mandrakesoft.com> wrote:
>If yes, my guess is correct, I think the proper solution is to:
>* create a generic set_config, which does nothing but convert the calls'
>semantics into ethtool semantics, and
>* add ethtool support to the specific driver

cc list trimmed.

If you go down this path, please add a standard performance monitoring
method to query the current capacity of an interface.  It is frustrating
to report "eth0 is handling 1 Megabyte/second, but we cannot tell if
that is 90% (10BaseT) or 9% (100BaseT) utilization".  We should report
capacity rather than speed because speed alone is not the controlling
factor, other things like half or full duplex affect the capacity.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-12-03  0:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-30 19:16 [RFC] Configuring synchronous interfaces in Linux Ivan Passos
2000-12-01  9:01 ` Francois romieu
2000-12-01 10:32   ` Chris Wedgwood
2000-12-01 11:00     ` Christoph Hellwig
2000-12-01 12:30       ` Xavier Bestel
2000-12-01 12:07     ` Russell King
2000-12-01 13:00       ` Francois Romieu
2000-12-02 16:09         ` Donald Becker
2000-12-02 18:59           ` Chris Wedgwood
2000-12-02 19:07             ` Jeff Garzik
2000-12-02 19:46               ` Russell King
2000-12-02 20:02               ` Philip Blundell
2000-12-03  5:47                 ` Chris Wedgwood
2000-12-03 11:10                   ` Philip Blundell
2000-12-03 11:27                     ` Russell King
2000-12-03  0:20               ` Keith Owens [this message]
2000-12-03 13:43                 ` Jeff Garzik
2000-12-03 20:29                   ` Keith Owens
2000-12-03 20:41                     ` Keith Owens
2000-12-02 19:48             ` Donald Becker
2000-12-07  8:44               ` Chris Wedgwood
2000-12-01 13:44       ` Philip Blundell
2000-12-01 12:15     ` Francois Romieu
2000-12-01 13:14     ` Bogdan Costescu
2000-12-01 16:26   ` Francois Desloges

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=2776.975802846@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=becker@scyld.com \
    --cc=jgarzik@mandrakesoft.mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --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