From: <ecree@xilinx.com>
To: <netdev@vger.kernel.org>, <linux-net-drivers@amd.com>
Cc: <davem@davemloft.net>, <kuba@kernel.org>, <pabeni@redhat.com>,
<edumazet@google.com>, <habetsm.xilinx@gmail.com>,
Edward Cree <ecree.xilinx@gmail.com>
Subject: [PATCH v2 net-next 0/6] sfc: bare bones TC offload
Date: Mon, 26 Sep 2022 19:57:30 +0100 [thread overview]
Message-ID: <cover.1664218348.git.ecree.xilinx@gmail.com> (raw)
From: Edward Cree <ecree.xilinx@gmail.com>
This series begins the work of supporting TC flower offload on EF100 NICs.
This is the absolute minimum viable TC implementation to get traffic to
VFs and allow them to be tested; it supports no match fields besides
ingress port, no actions besides mirred and drop, and no stats.
More matches, actions, and counters will be added in subsequent patches.
Changed in v2:
- Add missing 'static' on declarations (kernel test robot, sparse)
Edward Cree (6):
sfc: bind blocks for TC offload on EF100
sfc: bind indirect blocks for TC offload on EF100
sfc: optional logging of TC offload errors
sfc: add a hashtable for offloaded TC rules
sfc: interrogate MAE capabilities at probe time
sfc: bare bones TC offload on EF100
drivers/net/ethernet/sfc/Makefile | 2 +-
drivers/net/ethernet/sfc/ef100_ethtool.c | 2 +
drivers/net/ethernet/sfc/ef100_netdev.c | 4 +
drivers/net/ethernet/sfc/ef100_nic.c | 3 +
drivers/net/ethernet/sfc/ef100_rep.c | 18 +-
drivers/net/ethernet/sfc/ef100_rep.h | 1 +
drivers/net/ethernet/sfc/ethtool_common.c | 37 ++
drivers/net/ethernet/sfc/ethtool_common.h | 2 +
drivers/net/ethernet/sfc/mae.c | 165 +++++++++
drivers/net/ethernet/sfc/mae.h | 14 +
drivers/net/ethernet/sfc/mcdi.h | 10 +
drivers/net/ethernet/sfc/net_driver.h | 2 +
drivers/net/ethernet/sfc/tc.c | 430 +++++++++++++++++++++-
drivers/net/ethernet/sfc/tc.h | 36 ++
drivers/net/ethernet/sfc/tc_bindings.c | 228 ++++++++++++
drivers/net/ethernet/sfc/tc_bindings.h | 29 ++
16 files changed, 980 insertions(+), 3 deletions(-)
create mode 100644 drivers/net/ethernet/sfc/tc_bindings.c
create mode 100644 drivers/net/ethernet/sfc/tc_bindings.h
next reply other threads:[~2022-09-26 18:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 18:57 ecree [this message]
2022-09-26 18:57 ` [PATCH v2 net-next 1/6] sfc: bind blocks for TC offload on EF100 ecree
2022-09-28 8:43 ` Martin Habets
2022-09-26 18:57 ` [PATCH v2 net-next 2/6] sfc: bind indirect " ecree
2022-09-26 18:57 ` [PATCH v2 net-next 3/6] sfc: optional logging of TC offload errors ecree
2022-09-28 17:44 ` Jakub Kicinski
2022-09-28 18:17 ` Edward Cree
2022-09-28 18:32 ` Jakub Kicinski
2022-09-28 18:58 ` Edward Cree
2022-09-28 19:07 ` Jakub Kicinski
2022-09-28 21:14 ` Edward Cree
2022-09-29 1:15 ` Jakub Kicinski
2022-09-30 9:03 ` Edward Cree
2022-09-30 14:19 ` Jakub Kicinski
2022-10-03 19:30 ` Edward Cree
2022-09-26 18:57 ` [PATCH v2 net-next 4/6] sfc: add a hashtable for offloaded TC rules ecree
2022-09-26 18:57 ` [PATCH v2 net-next 5/6] sfc: interrogate MAE capabilities at probe time ecree
2022-09-26 18:57 ` [PATCH v2 net-next 6/6] sfc: bare bones TC offload on EF100 ecree
2022-09-28 8:50 ` [PATCH v2 net-next 0/6] sfc: bare bones TC 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.1664218348.git.ecree.xilinx@gmail.com \
--to=ecree@xilinx.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).