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 00/13] ipv6: Use fib6_result for fib_lookups
Date: Mon, 15 Apr 2019 17:56:39 -0700 [thread overview]
Message-ID: <20190416005652.29286-1-dsahern@kernel.org> (raw)
From: David Ahern <dsahern@gmail.com>
Add fib6_result as a single data structure to hold results from a fib
lookup. IPv6 currently has everything in 1 data structure - a fib6_info,
but with nexthop objects the fib6_nh can be in a nexthop or a nexthop
can be a blackhole which affects the fib6_type and flags (REJECT).
David Ahern (13):
ipv6: Rename fib6_multipath_select and pass fib6_result
ipv6: Pass fib6_result to rt6_find_cached_rt
ipv6: Pass fib6_result to ip6_rt_cache_alloc
ipv6: Pass fib6_result to ip6_create_rt_rcu
ipv6: Pass fib6_result to pcpu route functions
ipv6: Pass fib6_result to ip6_rt_get_dev_rcu and ip6_rt_copy_init
ipv6: Pass fib6_result to rt6_insert_exception
ipv6: Pass fib6_result to ip6_mtu_from_fib6 and fib6_mtu
ipv6: Pass fib6_result to rt6_device_match
ipv6: Pass fib6_result to rt6_select and find_rr_leaf
ipv6: Pass fib6_result to fib6_table_lookup tracepoint
ipv6: Pass fib6_result to fib lookups
ipv6: Add fib6_type and fib6_flags to fib6_result
include/net/ip6_fib.h | 24 ++-
include/net/ip6_route.h | 5 +-
include/net/ipv6_stubs.h | 25 ++-
include/trace/events/fib6.h | 16 +-
net/core/filter.c | 56 +++---
net/ipv6/addrconf_core.c | 29 +--
net/ipv6/af_inet6.c | 2 +-
net/ipv6/fib6_rules.c | 34 ++--
net/ipv6/ip6_fib.c | 7 +-
net/ipv6/route.c | 443 +++++++++++++++++++++++++-------------------
10 files changed, 348 insertions(+), 293 deletions(-)
--
2.11.0
next reply other threads:[~2019-04-16 0:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 0:56 David Ahern [this message]
2019-04-16 0:56 ` [PATCH net-next 01/13] ipv6: Rename fib6_multipath_select and pass fib6_result David Ahern
2019-04-16 0:56 ` [PATCH net-next 02/13] ipv6: Pass fib6_result to rt6_find_cached_rt David Ahern
2019-04-16 0:56 ` [PATCH net-next 03/13] ipv6: Pass fib6_result to ip6_rt_cache_alloc David Ahern
2019-04-16 0:56 ` [PATCH net-next 04/13] ipv6: Pass fib6_result to ip6_create_rt_rcu David Ahern
2019-04-16 0:56 ` [PATCH net-next 05/13] ipv6: Pass fib6_result to pcpu route functions David Ahern
2019-04-16 0:56 ` [PATCH net-next 06/13] ipv6: Pass fib6_result to ip6_rt_get_dev_rcu and ip6_rt_copy_init David Ahern
2019-04-16 0:56 ` [PATCH net-next 07/13] ipv6: Pass fib6_result to rt6_insert_exception David Ahern
2019-04-16 0:56 ` [PATCH net-next 08/13] ipv6: Pass fib6_result to ip6_mtu_from_fib6 and fib6_mtu David Ahern
2019-04-16 0:56 ` [PATCH net-next 09/13] ipv6: Pass fib6_result to rt6_device_match David Ahern
2019-04-16 0:56 ` [PATCH net-next 10/13] ipv6: Pass fib6_result to rt6_select and find_rr_leaf David Ahern
2019-04-16 0:56 ` [PATCH net-next 11/13] ipv6: Pass fib6_result to fib6_table_lookup tracepoint David Ahern
2019-04-16 0:56 ` [PATCH net-next 12/13] ipv6: Pass fib6_result to fib lookups David Ahern
2019-04-16 15:00 ` David Ahern
2019-04-16 0:56 ` [PATCH net-next 13/13] ipv6: Add fib6_type and fib6_flags to fib6_result David Ahern
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=20190416005652.29286-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 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).