Tue, Sep 06, 2016 at 04:32:12PM CEST, dsa@cumulusnetworks.com wrote:
On 9/6/16 6:01 AM, Jiri Pirko wrote:
quoted
From: Jiri Pirko <redacted>
This allows to pass information about added/deleted fib entries to
whoever is interested. This is done in a very similar way as devinet
notifies address additions/removals.
Signed-off-by: Jiri Pirko <redacted>
---
include/net/ip_fib.h | 19 +++++++++++++++++++
net/ipv4/fib_trie.c | 43 +++++++++++++++++++++++++++++++++++++++++++
2 files changed, 62 insertions(+)
The notifier infrastructure should be generalized for use with IPv4 and IPv6. While the data will be family based, the infra can be generic.
Yeah, that I thought about as well. Thing is, ipv6 notifier has to be
atomic. That is the reason we have:
inetaddr_chain and register_inetaddr_notifier (blocking notifier)
inet6addr_chain and register_inet6addr_notifier (atomic notifier)