On Sun, Mar 06, 2011 at 09:45:41AM -0800, Stephen Hemminger wrote: > Since this a generic problem, it needs a better solution. > Sending NETDEV_CHANGE impacts lots of other pieces, and even > user space has similar problems. It does seem a little broad notification type. I've checked over all the currently defined NETDEV notifiers, and it seems that NETDEV_NOTIFY_PEERS may be a better option to use when bridge has a potential topology change. Currently it is only used in ipv4/devinet.c: where it is used to issue a gratuitous ARP. -- Adam Majer adamm@xxxxxxxxxxx _______________________________________________ Bridge mailing list Bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/bridge
