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 v2 net-next 0/5] net: More movement to fib_nh_common
Date: Mon, 1 Apr 2019 09:25:58 -0700 [thread overview]
Message-ID: <20190401162603.26914-1-dsahern@kernel.org> (raw)
From: David Ahern <dsahern@gmail.com>
Second set of three with the end goal of enabling IPv6 gateways with IPv4
routes.
This set moves:
- the ipv4 tracepoint to take a fib_nh_common and updates it to handle
a v6 gateway.
- consolidates route notifications to use the same fill functions
for both ipv4 and ipv6
v2
- dropped patches moving cached routes and exception buckets to
fib_nh_common. The goal is allowing a fib6_nh to be used with an
IPv4 route. The hold up is the need for separate exception buckets -
one for v6 routes and one for v4 routes. When all of the nexthop patches
are in, adding a secondi exception bucket pushes IPv6 fib6_info
allocations over 256 which means fib6_info allocations roll up to 512.
Hence, deferring the patches until some data mining can be done to keep
the allocations at 256.
David Ahern (5):
ipv4: Update fib_table_lookup tracepoint to take common nexthop
ipv4: Add fib_nh_common to fib_result
ipv4: Refactor nexthop attributes in fib_dump_info
ipv4: Change fib_nexthop_info and fib_add_nexthop to take
fib_nh_common
ipv6: Flip to fib_nexthop_info
include/net/ip_fib.h | 52 +++++------
include/trace/events/fib.h | 45 ++++++----
net/core/filter.c | 12 +--
net/ipv4/fib_frontend.c | 6 +-
net/ipv4/fib_lookup.h | 1 +
net/ipv4/fib_semantics.c | 220 ++++++++++++++++++++++++++++++++-------------
net/ipv4/fib_trie.c | 13 +--
net/ipv4/route.c | 60 ++++++++-----
net/ipv6/route.c | 78 ++--------------
9 files changed, 273 insertions(+), 214 deletions(-)
--
2.11.0
next reply other threads:[~2019-04-01 16:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 16:25 David Ahern [this message]
2019-04-01 16:25 ` [PATCH v2 net-next 1/5] ipv4: Update fib_table_lookup tracepoint to take common nexthop David Ahern
2019-04-01 16:26 ` [PATCH v2 net-next 2/5] ipv4: Add fib_nh_common to fib_result David Ahern
2019-04-01 18:20 ` Martin Lau
2019-04-01 18:47 ` David Ahern
2019-04-01 16:26 ` [PATCH v2 net-next 3/5] ipv4: Refactor nexthop attributes in fib_dump_info David Ahern
2019-04-01 16:26 ` [PATCH v2 net-next 4/5] ipv4: Change fib_nexthop_info and fib_add_nexthop to take fib_nh_common David Ahern
2019-04-01 16:26 ` [PATCH v2 net-next 5/5] ipv6: Flip to fib_nexthop_info David Ahern
2019-04-01 20:15 ` Martin Lau
2019-04-01 20:20 ` 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=20190401162603.26914-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.