[Top] [All Lists]

Re: NETDEV_CHANGE events when __LINK_STATE_NOCARRIER is modified

To: "David S. Miller" <davem@xxxxxxxxxx>
Subject: Re: NETDEV_CHANGE events when __LINK_STATE_NOCARRIER is modified
From: Roger Venning <c729953@xxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Fri, 4 May 2001 16:07:24 +1000 (EST)
Cc: Janice Girouard <girouard@xxxxxxxxxx>, netdev@xxxxxxxxxxx
In-reply-to: <15089.61808.45075.22401@xxxxxxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx
On Thu, 3 May 2001, David S. Miller wrote:

> It is not a physical state change.  This state bit is meant only as a
> hack for the isdn layers dial on demand like functionality.
> This is not the kind of state change the notifier chain listeners are
> interested in.  It would be meaningless for the notifiers to run
> every time I yank my ethernet cable out of the card on my machine :-)

(presuming first that these events can be propagated up to user space
through some kind of listen on a socket style API, something that I don't
think is possible _yet_)

I beg to differ a little. Considering the case with the machine has
multiple network interfaces, and a mobile IP (RFC2002 and 
friends) capability, this kind of notification is crucial to smoothly
transferring traffic onto other available interfaces (think mobile pda
with ethernet & wide area cellular data). This is just one instance of
'middleware' style applications that would prefer not to poll this kind of


> Later,
> David S. Miller
> davem@xxxxxxxxxx

Roger Venning - Technologist - Telstra Research Laboratories

          For a successful technology, reality must take
          precedence over public relations, for Nature
          cannot be fooled.                 Richard Feynman

<Prev in Thread] Current Thread [Next in Thread>