| To: | Jeff Garzik <jgarzik@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [patch] Link state reporting |
| From: | Vojtech Pavlik <vojtech@xxxxxxx> |
| Date: | Mon, 26 Nov 2001 19:03:19 +0100 |
| Cc: | Brad Hards <bhards@xxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx, becker@xxxxxxxxx |
| In-reply-to: | <3C02822D.6E103FAD@xxxxxxxxxxxxxxxx>; from jgarzik@xxxxxxxxxxxxxxxx on Mon, Nov 26, 2001 at 12:55:57PM -0500 |
| References: | <3C0234A5.767256DF@xxxxxxxxxxxxxx> <3C02822D.6E103FAD@xxxxxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Mon, Nov 26, 2001 at 12:55:57PM -0500, Jeff Garzik wrote: > There is already two ways to report link state to userspace. We do not > need a third. > > First, ETHTOOL_GLINK. Second, netif_carrier_off causes IFF_RUNNING to > disappear when the interface is up. That's from the ethernet point of view. But if I understand correctly, there is no means for the userspace to be notified of a link state *change*. And hotplug is quite the way to do that. I'd like it to report things as they appear and go, be it USB devices, be it PCI/CardBus/PCMCIA devices, be it virtual devices like input ones, it even makes sense for char and blockdevices at the interface-to-userspace layer. And it makes sense for ethernet link status as well ... -- Vojtech Pavlik SuSE Labs |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [patch] Link state reporting, Jeff Garzik |
|---|---|
| Next by Date: | Re: [patch] Link state reporting, Jeff Garzik |
| Previous by Thread: | Re: [patch] Link state reporting, Jeff Garzik |
| Next by Thread: | Re: [patch] Link state reporting, Jeff Garzik |
| Indexes: | [Date] [Thread] [Top] [All Lists] |