From: David Ahern <dsahern@kernel.org>
To: davem@davemloft.net, netdev@vger.kernel.org
Cc: idosch@mellanox.com, David Ahern <dsahern@gmail.com>
Subject: [PATCH net-next 0/7] net: Export functions for nexthop code
Date: Sun, 5 May 2019 09:40:49 -0700 [thread overview]
Message-ID: <20190505164056.1742-1-dsahern@kernel.org> (raw)
From: David Ahern <dsahern@gmail.com>
This set exports ipv4 and ipv6 fib functions for use by the nexthop
code. It also adds new ones to send route notifications if a nexthop
configuration changes.
David Ahern (7):
ipv6: Add delete route hook to stubs
ipv6: Add hook to bump sernum for a route to stubs
ipv6: export function to send route updates
ipv4: Add function to send route updates
ipv4: export fib_check_nh
ipv4: export fib_flush
ipv4: export fib_info_update_nh_saddr
include/net/ip6_fib.h | 7 +++++
include/net/ip_fib.h | 8 +++++-
include/net/ipv6_stubs.h | 5 ++++
net/ipv4/fib_frontend.c | 2 +-
net/ipv4/fib_semantics.c | 23 ++++++++--------
net/ipv4/fib_trie.c | 72 ++++++++++++++++++++++++++++++++++++++++++++++++
net/ipv6/addrconf_core.c | 6 ++++
net/ipv6/af_inet6.c | 3 ++
net/ipv6/ip6_fib.c | 16 ++++++++---
net/ipv6/route.c | 32 +++++++++++++++++++++
10 files changed, 156 insertions(+), 18 deletions(-)
--
2.11.0
next reply other threads:[~2019-05-05 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 16:40 David Ahern [this message]
2019-05-05 16:40 ` [PATCH net-next 1/7] ipv6: Add delete route hook to stubs David Ahern
2019-05-05 16:40 ` [PATCH net-next 2/7] ipv6: Add hook to bump sernum for a route " David Ahern
2019-05-05 16:40 ` [PATCH net-next 3/7] ipv6: export function to send route updates David Ahern
2019-05-05 16:40 ` [PATCH net-next 4/7] ipv4: Add " David Ahern
2019-05-05 16:40 ` [PATCH net-next 5/7] ipv4: export fib_check_nh David Ahern
2019-05-05 16:40 ` [PATCH net-next 6/7] ipv4: export fib_flush David Ahern
2019-05-05 16:40 ` [PATCH net-next 7/7] ipv4: export fib_info_update_nh_saddr David Ahern
2019-05-06 5:00 ` [PATCH net-next 0/7] net: Export functions for nexthop code David Miller
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=20190505164056.1742-1-dsahern@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=idosch@mellanox.com \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.