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/4] sfc: more flexible encap matches on TC decap rules
Date: Thu, 11 May 2023 20:47:27 +0100 [thread overview]
Message-ID: <cover.1683834261.git.ecree.xilinx@gmail.com> (raw)
From: Edward Cree <ecree.xilinx@gmail.com>
This series extends the TC offload support on EF100 to support optionally
matching on the IP ToS and UDP source port of the outer header in rules
performing tunnel decapsulation. Both of these fields allow masked
matches if the underlying hardware supports it (current EF100 hardware
supports masking on ToS, but only exact-match on source port).
Given that the source port is typically populated from a hash of inner
header entropy, it's not clear whether filtering on it is useful, but
since we can support it we may as well expose the capability.
Edward Cree (4):
sfc: release encap match in efx_tc_flow_free()
sfc: populate enc_ip_tos matches in MAE outer rules
sfc: support TC decap rules matching on enc_ip_tos
sfc: support TC decap rules matching on enc_src_port
drivers/net/ethernet/sfc/mae.c | 28 ++++-
drivers/net/ethernet/sfc/mae.h | 1 +
drivers/net/ethernet/sfc/tc.c | 205 +++++++++++++++++++++++----------
drivers/net/ethernet/sfc/tc.h | 27 +++++
4 files changed, 197 insertions(+), 64 deletions(-)
next reply other threads:[~2023-05-11 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 19:47 edward.cree [this message]
2023-05-11 19:47 ` [PATCH v2 net-next 1/4] sfc: release encap match in efx_tc_flow_free() edward.cree
2023-05-11 19:47 ` [PATCH v2 net-next 2/4] sfc: populate enc_ip_tos matches in MAE outer rules edward.cree
2023-05-11 19:47 ` [PATCH v2 net-next 3/4] sfc: support TC decap rules matching on enc_ip_tos edward.cree
2023-05-12 9:51 ` Simon Horman
2023-05-12 14:27 ` Edward Cree
2023-05-11 19:47 ` [PATCH v2 net-next 4/4] sfc: support TC decap rules matching on enc_src_port edward.cree
2023-05-12 11:50 ` [PATCH v2 net-next 0/4] sfc: more flexible encap matches on TC decap rules 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.1683834261.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).