From: John Hurley <john.hurley@netronome.com>
To: netdev@vger.kernel.org
Cc: simon.horman@netronome.com, jakub.kicinski@netronome.com,
oss-drivers@netronome.com,
John Hurley <john.hurley@netronome.com>
Subject: [PATCH net-next 0/9] Add ipv6 tunnel support to NFP
Date: Thu, 12 Dec 2019 18:16:47 +0000 [thread overview]
Message-ID: <1576174616-9738-1-git-send-email-john.hurley@netronome.com> (raw)
Hi,
The following patches add support for IPv6 tunnel offload to the NFP
driver.
Patches 1-2 do some code tidy up and prepare existing code for reuse in
IPv6 tunnels.
Patches 3-4 handle IPv6 tunnel decap (match) rules.
Patches 5-8 handle encap (action) rules.
Patch 9 adds IPv6 support to the merge and pre-tunnel rule functions.
John Hurley (9):
nfp: flower: pass flow rule pointer directly to match functions
nfp: flower: move udp tunnel key match compilation to helper function
nfp: flower: compile match for IPv6 tunnels
nfp: flower: offload list of IPv6 tunnel endpoint addresses
nfp: flower: modify pre-tunnel and set tunnel action for ipv6
nfp: flower: handle ipv6 tunnel no neigh request
nfp: flower: handle notifiers for ipv6 route changes
nfp: flower: support ipv6 tunnel keep-alive messages from fw
nfp: flower: update flow merge code to support IPv6 tunnels
drivers/net/ethernet/netronome/nfp/flower/action.c | 65 ++-
drivers/net/ethernet/netronome/nfp/flower/cmsg.c | 11 +-
drivers/net/ethernet/netronome/nfp/flower/cmsg.h | 106 ++++-
drivers/net/ethernet/netronome/nfp/flower/main.h | 38 +-
drivers/net/ethernet/netronome/nfp/flower/match.c | 260 +++++++----
.../net/ethernet/netronome/nfp/flower/offload.c | 144 ++++--
.../ethernet/netronome/nfp/flower/tunnel_conf.c | 497 ++++++++++++++++++---
7 files changed, 892 insertions(+), 229 deletions(-)
--
2.7.4
next reply other threads:[~2019-12-12 18:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 18:16 John Hurley [this message]
2019-12-12 18:16 ` [PATCH net-next 1/9] nfp: flower: pass flow rule pointer directly to match functions John Hurley
2019-12-12 18:16 ` [PATCH net-next 2/9] nfp: flower: move udp tunnel key match compilation to helper function John Hurley
2019-12-12 18:16 ` [PATCH net-next 3/9] nfp: flower: compile match for IPv6 tunnels John Hurley
2019-12-12 18:16 ` [PATCH net-next 4/9] nfp: flower: offload list of IPv6 tunnel endpoint addresses John Hurley
2019-12-12 18:16 ` [PATCH net-next 5/9] nfp: flower: modify pre-tunnel and set tunnel action for ipv6 John Hurley
2019-12-12 18:16 ` [PATCH net-next 6/9] nfp: flower: handle ipv6 tunnel no neigh request John Hurley
2019-12-12 18:16 ` [PATCH net-next 7/9] nfp: flower: handle notifiers for ipv6 route changes John Hurley
2019-12-12 18:16 ` [PATCH net-next 8/9] nfp: flower: support ipv6 tunnel keep-alive messages from fw John Hurley
2019-12-12 18:16 ` [PATCH net-next 9/9] nfp: flower: update flow merge code to support IPv6 tunnels John Hurley
2019-12-15 4:41 ` [PATCH net-next 0/9] Add ipv6 tunnel support to NFP Jakub Kicinski
2019-12-15 5:11 ` Jakub Kicinski
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=1576174616-9738-1-git-send-email-john.hurley@netronome.com \
--to=john.hurley@netronome.com \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=simon.horman@netronome.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).