[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <161059440891.32332.11503603600649559584.git-patchwork-notify@kernel.org>
Date: Thu, 14 Jan 2021 03:20:08 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Naveen Mamindlapalli <naveenm@...vell.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
kuba@...nel.org, davem@...emloft.net, sgoutham@...vell.com,
lcherian@...vell.com, gakula@...vell.com, jerinj@...vell.com,
sbhatta@...vell.com, hkelam@...vell.com
Subject: Re: [PATCH] octeontx2-pf: Add flow classification using IP next level
protocol
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Mon, 11 Jan 2021 16:55:37 +0530 you wrote:
> This patch adds support to install flow rules using ipv4 proto or
> ipv6 next header field to distinguish between tcp/udp/sctp/esp/ah
> flows when user doesn't specify the other match creteria related to
> the flow such as tcp/udp/sctp source port and destination port, ah/esp
> spi value. This is achieved by matching the layer type extracted by
> NPC HW into the search key. Modified the driver to use Ethertype as
> match criteria when user doesn't specify source IP address and dest
> IP address. The esp/ah flow rule matching using security parameter
> index (spi) is not supported as of now since the field is not extracted
> into MCAM search key. Modified npc_check_field function to return bool.
>
> [...]
Here is the summary with links:
- octeontx2-pf: Add flow classification using IP next level protocol
https://git.kernel.org/netdev/net-next/c/b7cf966126eb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists