| To: | Jeff Garzik <jgarzik@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [RFC] Configuring synchronous interfaces in Linux |
| From: | Keith Owens <kaos@xxxxxxxxxx> |
| Date: | Sun, 03 Dec 2000 11:20:46 +1100 |
| Cc: | Donald Becker <becker@xxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | Your message of "Sat, 02 Dec 2000 13:07:29 MDT." <Pine.LNX.3.96.1001202130202.1450B-100000@mandrakesoft.mandrakesoft.com> |
| Sender: | owner-netdev@xxxxxxxxxxx |
On Sat, 2 Dec 2000 13:07:29 -0600 (CST), Jeff Garzik <jgarzik@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> 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. |
| Previous by Date: | Re: [RFC] Configuring synchronous interfaces in Linux, Philip Blundell |
|---|---|
| Next by Date: | Re: [RFC] Configuring synchronous interfaces in Linux, Chris Wedgwood |
| Previous by Thread: | Re: [RFC] Configuring synchronous interfaces in Linux, Russell King |
| Next by Thread: | Re: [RFC] Configuring synchronous interfaces in Linux, Jeff Garzik |
| Indexes: | [Date] [Thread] [Top] [All Lists] |