netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@kernel.org>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, assogba.emery@gmail.com,
	dsahern@gmail.com, David Ahern <dsahern@kernel.org>
Subject: [PATCH RFC net-next 0/8] nexthop: Add support for active-backup nexthop type
Date: Tue,  9 Jun 2020 21:49:45 -0600	[thread overview]
Message-ID: <20200610034953.28861-1-dsahern@kernel.org> (raw)

This set adds support for a new nexthop group - active-backup.
The intent is that the group describes a primary nexthop with a backup
option if the primary is not available. Since nexthop code removes
entries on carrier or admin down this really means the backup applies
when the neighbor entry for the active becomes invalid. In that case,
the lookup atomically switches to use the backup. I mentioned this use
case at LPC2019[0] as a follow on use case for the nexthop code.

The first 6 patches refactor existing code to get ready for a new
group type. The a-b group is added in patch 7 with selftests in
patch 8.

[0] https://linuxplumbersconf.org/event/4/contributions/434/attachments/251/436/nexthop-objects-talk.pdf

David Ahern (8):
  nexthop: Rename nexthop_free_mpath
  nexthop: Refactor nexthop_select_path
  nexthop: Refactor nexthop_for_each_fib6_nh
  nexthop: Move nexthop_get_nhc_lookup to nexthop.c
  nexthop: Move nexthop_uses_dev to nexthop.c
  nexthop: Add primary_only argument to nexthop_for_each_fib6_nh
  nexthop: Add support for active-backup nexthop type
  selftests: Add active-backup nexthop tests

 include/net/nexthop.h                       | 106 +++---
 include/uapi/linux/nexthop.h                |   1 +
 net/ipv4/fib_semantics.c                    |   6 +-
 net/ipv4/nexthop.c                          | 356 +++++++++++++++++---
 net/ipv6/ip6_fib.c                          |   4 +-
 net/ipv6/route.c                            |  37 +-
 tools/testing/selftests/net/fib_nexthops.sh | 334 +++++++++++++++++-
 7 files changed, 713 insertions(+), 131 deletions(-)

-- 
2.21.1 (Apple Git-122.3)


             reply	other threads:[~2020-06-10  3:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10  3:49 David Ahern [this message]
2020-06-10  3:49 ` [PATCH RFC net-next 1/8] nexthop: Rename nexthop_free_mpath David Ahern
2020-06-10  3:49 ` [PATCH RFC net-next 2/8] nexthop: Refactor nexthop_select_path David Ahern
2020-06-10  3:49 ` [PATCH RFC net-next 3/8] nexthop: Refactor nexthop_for_each_fib6_nh David Ahern
2020-06-10  3:49 ` [PATCH RFC net-next 4/8] nexthop: Move nexthop_get_nhc_lookup to nexthop.c David Ahern
2020-06-10  3:49 ` [PATCH RFC net-next 5/8] nexthop: Move nexthop_uses_dev " David Ahern
2020-06-10  3:49 ` [PATCH RFC net-next 6/8] nexthop: Add primary_only argument to nexthop_for_each_fib6_nh David Ahern
2020-06-10  3:49 ` [PATCH RFC net-next 7/8] nexthop: Add support for active-backup nexthop type David Ahern
2020-06-10  3:49 ` [PATCH RFC net-next 8/8] selftests: Add active-backup nexthop tests 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=20200610034953.28861-1-dsahern@kernel.org \
    --to=dsahern@kernel.org \
    --cc=assogba.emery@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=kuba@kernel.org \
    --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).