From: patchwork-bot+netdevbpf@kernel•org
To: <edward.cree@amd•com>
Cc: linux-net-drivers@amd•com, davem@davemloft•net, kuba@kernel•org,
pabeni@redhat•com, edumazet@google•com, ecree.xilinx@gmail•com,
netdev@vger•kernel.org, habetsm.xilinx@gmail•com,
michal.swiatkowski@linux•intel.com, simon.horman@corigine•com
Subject: Re: [PATCH net-next v3 0/6] sfc: support TC decap rules
Date: Wed, 29 Mar 2023 08:10:26 +0000 [thread overview]
Message-ID: <168007742661.16006.10917682225413087784.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1679912088.git.ecree.xilinx@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft•net>:
On Mon, 27 Mar 2023 11:36:02 +0100 you wrote:
> From: Edward Cree <ecree.xilinx@gmail•com>
>
> This series adds support for offloading tunnel decapsulation TC rules to
> ef100 NICs, allowing matching encapsulated packets to be decapsulated in
> hardware and redirected to VFs.
> For now an encap match must be on precisely the following fields:
> ethertype (IPv4 or IPv6), source IP, destination IP, ipproto UDP,
> UDP destination port. This simplifies checking for overlaps in the
> driver; the hardware supports a wider range of match fields which
> future driver work may expose.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/6] sfc: document TC-to-EF100-MAE action translation concepts
https://git.kernel.org/netdev/net-next/c/edd025ca0887
- [net-next,v3,2/6] sfc: add notion of match on enc keys to MAE machinery
https://git.kernel.org/netdev/net-next/c/b9d5c9b7d8a4
- [net-next,v3,3/6] sfc: handle enc keys in efx_tc_flower_parse_match()
https://git.kernel.org/netdev/net-next/c/b7f5e17b3bb9
- [net-next,v3,4/6] sfc: add functions to insert encap matches into the MAE
https://git.kernel.org/netdev/net-next/c/2245eb0086d8
- [net-next,v3,5/6] sfc: add code to register and unregister encap matches
https://git.kernel.org/netdev/net-next/c/746224cdef01
- [net-next,v3,6/6] sfc: add offloading of 'foreign' TC (decap) rules
https://git.kernel.org/netdev/net-next/c/17654d84b47c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-03-29 8:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 10:36 [PATCH net-next v3 0/6] sfc: support TC decap rules edward.cree
2023-03-27 10:36 ` [PATCH net-next v3 1/6] sfc: document TC-to-EF100-MAE action translation concepts edward.cree
2023-03-27 10:36 ` [PATCH net-next v3 2/6] sfc: add notion of match on enc keys to MAE machinery edward.cree
2023-03-27 14:27 ` Simon Horman
2023-03-27 10:36 ` [PATCH net-next v3 3/6] sfc: handle enc keys in efx_tc_flower_parse_match() edward.cree
2023-03-27 10:36 ` [PATCH net-next v3 4/6] sfc: add functions to insert encap matches into the MAE edward.cree
2023-03-27 14:28 ` Simon Horman
2023-03-27 10:36 ` [PATCH net-next v3 5/6] sfc: add code to register and unregister encap matches edward.cree
2023-03-27 14:28 ` Simon Horman
2023-03-27 10:36 ` [PATCH net-next v3 6/6] sfc: add offloading of 'foreign' TC (decap) rules edward.cree
2023-03-29 8:10 ` patchwork-bot+netdevbpf [this message]
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=168007742661.16006.10917682225413087784.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=ecree.xilinx@gmail$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=edward.cree@amd$(echo .)com \
--cc=habetsm.xilinx@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-net-drivers@amd$(echo .)com \
--cc=michal.swiatkowski@linux$(echo .)intel.com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=simon.horman@corigine$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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