From: Jiri Pirko <jiri@resnulli.us>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, idosch@mellanox.com,
eladr@mellanox.com, yotamg@mellanox.com, nogahf@mellanox.com,
ogerlitz@mellanox.com, roopa@cumulusnetworks.com,
nikolay@cumulusnetworks.com, linville@tuxdriver.com,
tgraf@suug.ch, gospo@cumulusnetworks.com, sfeldma@gmail.com,
ast@plumgrid.com, edumazet@google.com,
hannes@stressinduktion.org, f.fainelli@gmail.com,
jhs@mojatatu.com, vivien.didelot@savoirfairelinux.com,
john.fastabend@intel.com, andrew@lunn.ch, ivecera@redhat.com
Subject: Re: [patch net-next RFC 1/2] fib: introduce fib notification infrastructure
Date: Tue, 6 Sep 2016 16:44:08 +0200 [thread overview]
Message-ID: <20160906144408.GH1692@nanopsycho> (raw)
In-Reply-To: <6a4d9ba6-7113-b487-eb52-ca1f703d13f6@cumulusnetworks.com>
Tue, Sep 06, 2016 at 04:32:12PM CEST, dsa@cumulusnetworks.com wrote:
>On 9/6/16 6:01 AM, Jiri Pirko wrote:
>> From: Jiri Pirko <jiri@mellanox.com>
>>
>> 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 <jiri@mellanox.com>
>> ---
>> 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)
next prev parent reply other threads:[~2016-09-06 14:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 12:01 [patch net-next RFC 0/2] fib4 offload: notifier to let hw to be aware of all prefixes Jiri Pirko
2016-09-06 12:01 ` [patch net-next RFC 1/2] fib: introduce fib notification infrastructure Jiri Pirko
2016-09-06 14:32 ` David Ahern
2016-09-06 14:44 ` Jiri Pirko [this message]
2016-09-06 15:11 ` David Ahern
2016-09-06 15:49 ` Jiri Pirko
2016-09-06 16:14 ` Hannes Frederic Sowa
2016-09-06 15:13 ` David Ahern
2016-09-07 8:03 ` Jiri Pirko
2016-09-15 14:41 ` [net-next,RFC,1/2] " Andy Gospodarek
2016-09-15 14:45 ` Jiri Pirko
2016-09-15 14:47 ` Andy Gospodarek
2016-09-18 23:23 ` [patch net-next RFC 1/2] " Roopa Prabhu
2016-09-19 6:06 ` Jiri Pirko
2016-09-19 14:53 ` Roopa Prabhu
2016-09-19 15:08 ` Jiri Pirko
2016-09-06 12:01 ` [patch net-next RFC 2/2] mlxsw: spectrum_router: Use FIB notifications instead of switchdev calls Jiri Pirko
2016-09-18 20:00 ` [patch net-next RFC 0/2] fib4 offload: notifier to let hw to be aware of all prefixes Florian Fainelli
2016-09-18 23:16 ` Roopa Prabhu
2016-09-19 6:14 ` Jiri Pirko
2016-09-19 14:59 ` Roopa Prabhu
2016-09-19 15:15 ` Jiri Pirko
2016-09-20 5:49 ` Roopa Prabhu
2016-09-20 6:02 ` Jiri Pirko
2016-09-20 6:18 ` Roopa Prabhu
2016-09-19 6:08 ` Jiri Pirko
2016-09-19 16:44 ` Florian Fainelli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160906144408.GH1692@nanopsycho \
--to=jiri@resnulli.us \
--cc=andrew@lunn.ch \
--cc=ast@plumgrid.com \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=edumazet@google.com \
--cc=eladr@mellanox.com \
--cc=f.fainelli@gmail.com \
--cc=gospo@cumulusnetworks.com \
--cc=hannes@stressinduktion.org \
--cc=idosch@mellanox.com \
--cc=ivecera@redhat.com \
--cc=jhs@mojatatu.com \
--cc=john.fastabend@intel.com \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=nogahf@mellanox.com \
--cc=ogerlitz@mellanox.com \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@gmail.com \
--cc=tgraf@suug.ch \
--cc=vivien.didelot@savoirfairelinux.com \
--cc=yotamg@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).