Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-03 Thread Keith Owens
On Mon, 04 Dec 2000 07:29:10 +1100, Keith Owens <[EMAIL PROTECTED]> wrote: >On Sun, 3 Dec 2000 07:43:01 -0600 (CST), >Jeff Garzik <[EMAIL PROTECTED]> wrote: >>On Sun, 3 Dec 2000, Keith Owens wrote: >>> If you go down this path, please add a standard performance monitoring >>> method to query the

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-03 Thread Keith Owens
On Sun, 3 Dec 2000 07:43:01 -0600 (CST), Jeff Garzik <[EMAIL PROTECTED]> wrote: >On Sun, 3 Dec 2000, Keith Owens wrote: >> If you go down this path, please add a standard performance monitoring >> method to query the current capacity of an interface. >Well, ethtool interface supports reporting me

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-03 Thread Jeff Garzik
On Sun, 3 Dec 2000, Keith Owens wrote: > If you go down this path, please add a standard performance monitoring > method to query the current capacity of an interface. > to report "eth0 is handling 1 Megabyte/second, but we cannot tell if > that is 90% (10BaseT) or 9% (100BaseT) utilization". We

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-03 Thread Russell King
(CC list trimmed) Philip Blundell writes: > >Does it? At which point? To me it looks like it calls dev->do_ioctl > >or am I missing something? > > It uses SIOCSIFMAP, which (I think) winds up in dev.c here: > > case SIOCSIFMAP: > if (dev->set_config) { >

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-03 Thread Philip Blundell
>Does it? At which point? To me it looks like it calls dev->do_ioctl >or am I missing something? It uses SIOCSIFMAP, which (I think) winds up in dev.c here: case SIOCSIFMAP: if (dev->set_config) { if (!netif_device_present(dev))

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-02 Thread Keith Owens
On Sat, 2 Dec 2000 13:07:29 -0600 (CST), Jeff Garzik <[EMAIL PROTECTED]> 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

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-02 Thread Philip Blundell
>Does 'ifconfig eth0 media xxx' wind up calling dev->set_config? Yes. p. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-02 Thread Russell King
Jeff Garzik writes: > Does 'ifconfig eth0 media xxx' wind up calling dev->set_config? Yes. See drivers/acorn/net/etherh.c for an(other) example driver supporting 10baseT and 10base2. > If yes, my guess is correct, I think the proper solution is to: > * create a generic set_config, which does no

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-02 Thread Donald Becker
On Sun, 3 Dec 2000, Chris Wedgwood wrote: > On Sat, Dec 02, 2000 at 11:09:35AM -0500, Donald Becker wrote: > > Hey, I'll make it easy. Find an approach that fully handles only the Tulip > and 3c59x drivers, and that is consistent. > > Actually, I starteed work on adding this to the 3c5

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-02 Thread Jeff Garzik
On Sun, 3 Dec 2000, Chris Wedgwood wrote: > > Russell King <[EMAIL PROTECTED]> écrit : > > [...] > > > We already have a standard interface for this, but many drivers do not > > > support it. Its called "ifconfig eth0 media xxx": > Actually, I starteed work on adding this to the

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-02 Thread Donald Becker
On Fri, 1 Dec 2000, Francois Romieu wrote: > Russell King <[EMAIL PROTECTED]> écrit : > [...] > > We already have a standard interface for this, but many drivers do not > > support it. Its called "ifconfig eth0 media xxx": Uhmmm, it's not a standard if "many drivers do not support it". It is v

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-01 Thread Francois Desloges
On Fri, 01 Dec 2000, Francois romieu wrote: > [netdev Cced] > > The Thu, Nov 30, 2000 at 11:16:52AM -0800, Ivan Passos wrote : > [...] > > For synchronous network interfaces, besides configuring network parameters > > such as IP address, netmask, MTU, etc., the system should also configure > > pa

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-01 Thread Philip Blundell
In message <[EMAIL PROTECTED]>, Russell King wri tes: >We already have a standard interface for this, but many drivers do not >support it. Its called "ifconfig eth0 media xxx": The Ethtool interface is rather better. p. - To unsubscribe from this list: send the line "unsubscribe linux-kernel"

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-01 Thread Bogdan Costescu
On Fri, 1 Dec 2000, Chris Wedgwood wrote: > Actually; Ethernet badly needs something like this too. I would kill > to be able to do something like: > > ifconfig eth0 speed 100 duplex full Even if you are thinking about Ethernet only, it's not easy to do it. Most modern NICs have MII transc

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-01 Thread Francois Romieu
Russell King <[EMAIL PROTECTED]> écrit : [...] > We already have a standard interface for this, but many drivers do not > support it. Its called "ifconfig eth0 media xxx": > > bash-2.04# ifconfig --help > Usage: > ifconfig [-a] [-i] [-v] [-s] [[] ] > ... > [mem_start ] [io_addr ] [irq ]

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-01 Thread Xavier Bestel
> In article <[EMAIL PROTECTED]> you wrote: > > Actually; Ethernet badly needs something like this too. I would kill > > to be able to do something like: > > > ifconfig eth0 speed 100 duplex full > > > o across different networks cards -- I've been thinking about it of > > late as I had to b

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-01 Thread Francois Romieu
Chris Wedgwood <[EMAIL PROTECTED]> écrit : [...] > o across different networks cards -- I've been thinking about it of > late as I had to battle with this earlier this week; depending on > what network card you use, you need different magic incarnations to > do the above. > > A standard interface

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-01 Thread Russell King
Chris Wedgwood writes: > Actually; Ethernet badly needs something like this too. I would kill > to be able to do something like: > > ifconfig eth0 speed 100 duplex full > > o across different networks cards -- I've been thinking about it of > late as I had to battle with this earlier this

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-01 Thread Christoph Hellwig
In article <[EMAIL PROTECTED]> you wrote: > Actually; Ethernet badly needs something like this too. I would kill > to be able to do something like: > ifconfig eth0 speed 100 duplex full > o across different networks cards -- I've been thinking about it of > late as I had to battle with thi

Re: [RFC] Configuring synchronous interfaces in Linux

2000-12-01 Thread Francois romieu
[netdev Cced] The Thu, Nov 30, 2000 at 11:16:52AM -0800, Ivan Passos wrote : [...] > For synchronous network interfaces, besides configuring network parameters > such as IP address, netmask, MTU, etc., the system should also configure > parameters specific to these sync i/f's, such as media (e.g

[RFC] Configuring synchronous interfaces in Linux

2000-11-30 Thread Ivan Passos
Hello, For synchronous network interfaces, besides configuring network parameters such as IP address, netmask, MTU, etc., the system should also configure parameters specific to these sync i/f's, such as media (e.g V.35, X.21, T1, E1), clock (internal or external, and value if int.), protocol (e