netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <edward.cree@amd.com>
To: <linux-net-drivers@amd.com>, <davem@davemloft.net>,
	<kuba@kernel.org>, <pabeni@redhat.com>, <edumazet@google.com>
Cc: Edward Cree <ecree.xilinx@gmail.com>, <netdev@vger.kernel.org>,
	<habetsm.xilinx@gmail.com>
Subject: [PATCH v2 net-next 0/6] sfc: TC encap actions offload
Date: Thu, 8 Jun 2023 17:42:29 +0100	[thread overview]
Message-ID: <cover.1686240142.git.ecree.xilinx@gmail.com> (raw)

From: Edward Cree <ecree.xilinx@gmail.com>

This series adds support for offloading TC tunnel_key set actions to the
 EF100 driver, supporting VxLAN and GENEVE tunnels over IPv4 or IPv6.

Edward Cree (6):
  sfc: add fallback action-set-lists for TC offload
  sfc: some plumbing towards TC encap action offload
  sfc: add function to atomically update a rule in the MAE
  sfc: MAE functions to create/update/delete encap headers
  sfc: neighbour lookup for TC encap action offload
  sfc: generate encap headers for TC offload

 drivers/net/ethernet/sfc/Makefile           |   3 +-
 drivers/net/ethernet/sfc/ef100_netdev.c     |  34 +
 drivers/net/ethernet/sfc/mae.c              | 113 ++-
 drivers/net/ethernet/sfc/mae.h              |   8 +
 drivers/net/ethernet/sfc/net_driver.h       |   3 +
 drivers/net/ethernet/sfc/tc.c               | 182 ++++-
 drivers/net/ethernet/sfc/tc.h               |  23 +
 drivers/net/ethernet/sfc/tc_bindings.c      |  13 +
 drivers/net/ethernet/sfc/tc_bindings.h      |   2 +
 drivers/net/ethernet/sfc/tc_encap_actions.c | 746 ++++++++++++++++++++
 drivers/net/ethernet/sfc/tc_encap_actions.h | 103 +++
 11 files changed, 1222 insertions(+), 8 deletions(-)
 create mode 100644 drivers/net/ethernet/sfc/tc_encap_actions.c
 create mode 100644 drivers/net/ethernet/sfc/tc_encap_actions.h


             reply	other threads:[~2023-06-08 16:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-08 16:42 edward.cree [this message]
2023-06-08 16:42 ` [PATCH v2 net-next 1/6] sfc: add fallback action-set-lists for TC offload edward.cree
2023-06-09  9:37   ` Simon Horman
2023-06-08 16:42 ` [PATCH v2 net-next 2/6] sfc: some plumbing towards TC encap action offload edward.cree
2023-06-09  9:35   ` Simon Horman
2023-06-08 16:42 ` [PATCH v2 net-next 3/6] sfc: add function to atomically update a rule in the MAE edward.cree
2023-06-09  9:35   ` Simon Horman
2023-06-08 16:42 ` [PATCH v2 net-next 4/6] sfc: MAE functions to create/update/delete encap headers edward.cree
2023-06-09  9:36   ` Simon Horman
2023-06-08 16:42 ` [PATCH v2 net-next 5/6] sfc: neighbour lookup for TC encap action offload edward.cree
2023-06-09  9:37   ` Simon Horman
2023-06-09 10:25   ` Pieter Jansen van Vuuren
2023-06-08 16:42 ` [PATCH v2 net-next 6/6] sfc: generate encap headers for TC offload edward.cree
2023-06-09  9:36   ` Simon Horman
2023-06-09 10:29   ` Pieter Jansen van Vuuren
2023-06-10  7:21 ` [PATCH v2 net-next 0/6] sfc: TC encap actions offload patchwork-bot+netdevbpf

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=cover.1686240142.git.ecree.xilinx@gmail.com \
    --to=edward.cree@amd.com \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=habetsm.xilinx@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-net-drivers@amd.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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).