On Fri, 4 May 2001, Andi Kleen wrote:
> On Fri, May 04, 2001 at 02:01:52AM +0200, David S. Miller wrote:
> Not the current ones.
> It would be useful in some cases to trigger a TCP retransmit though.
> This is needed for good behaviour on dynamic IP addresses with the ip_dynaddr
> hack. ip_dynaddr can only rewrite the socket from the dummy dialdevice address
> to the real dynamic address when it gets a retransmit from transport layer.
> When IFF_DYNAMIC is set it makes sense to have a notifier in TCP listen
> to it and call tcp_simple_retransmit().
> [implementing this is on my todo list and I hopefully will get to it soon...]
As well as SCTP could use this for failover.
If i am not mistaken it was Alexey that removed this from the
netlink interface sometime around 2.3. The problem was that link
notification was done at interupt context and netlink is not comfortable
With 2.5 changes proposed that should be a non-issue.
Andi, I suggest you leave the current interface as is. Just register to
receive the messages and work around the interupt context issues.
This way other parties interested (such as user space proggies) can use it
to innovate their own applications.
Come to think of it: How does cardbus/pcmcia netcard insertion work? That
sends a netlink message and if i am not mistaken in interupt context.