On Mon, 2016-10-31 at 23:13 +0200, [email protected] wrote: > From: Ido Schimmel <[email protected]> > > When registering a FIB notifier block we should notify the caller of > already existing FIB entries and rules, as it would otherwise have an > incomplete view of the FIB tables. This is especially important for > switchdev drivers that support FIB offloads. Failing to notify them of > existing entries may lead to packet loss. > > Upon registration, walk the leafs of all the routing tables and for each > leaf send notification of existing FIB aliases. Similarly, when > unregistering the notifier synthesize a deletion event, thereby > relieving potential callers from the need to perform cleanup. > > The above is consistent with the netdevice notification chain, where > "registration and up events are replayed to the new notifier" upon > registration. > > Signed-off-by: Ido Schimmel <[email protected]> > Reviewed-by: Jiri Pirko <[email protected]>
How well will this work for large FIB tables ? Holding rtnl while sending thousands of skb will prevent consumers to make progress ?
