From: <edward.cree@amd.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 net-next 0/5] sfc: add basic flower matches to offload
Date: Mon, 24 Oct 2022 10:29:20 +0100 [thread overview]
Message-ID: <cover.1666603600.git.ecree.xilinx@gmail.com> (raw)
From: Edward Cree <ecree.xilinx@gmail.com>
Support offloading TC flower rules with matches on L2-L4 fields.
Edward Cree (5):
sfc: check recirc_id match caps before MAE offload
sfc: add Layer 2 matches to ef100 TC offload
sfc: add Layer 3 matches to ef100 TC offload
sfc: add Layer 3 flag matches to ef100 TC offload
sfc: add Layer 4 matches to ef100 TC offload
drivers/net/ethernet/sfc/mae.c | 132 ++++++++++++++++++++++++++++++
drivers/net/ethernet/sfc/mcdi.h | 12 +++
drivers/net/ethernet/sfc/tc.c | 137 +++++++++++++++++++++++++++++---
drivers/net/ethernet/sfc/tc.h | 16 ++++
4 files changed, 286 insertions(+), 11 deletions(-)
next reply other threads:[~2022-10-24 9:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 9:29 edward.cree [this message]
2022-10-24 9:29 ` [PATCH net-next 1/5] sfc: check recirc_id match caps before MAE offload edward.cree
2022-10-26 2:40 ` Jakub Kicinski
2022-11-01 13:30 ` Edward Cree
2022-11-01 15:21 ` Jakub Kicinski
2022-11-01 15:41 ` Edward Cree
2022-11-01 15:50 ` Jakub Kicinski
2022-10-24 9:29 ` [PATCH net-next 2/5] sfc: add Layer 2 matches to ef100 TC offload edward.cree
2022-10-24 9:29 ` [PATCH net-next 3/5] sfc: add Layer 3 " edward.cree
2022-10-24 9:29 ` [PATCH net-next 4/5] sfc: add Layer 3 flag " edward.cree
2022-10-24 9:29 ` [PATCH net-next 5/5] sfc: add Layer 4 " edward.cree
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.1666603600.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).