[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166910821529.27872.4243816404919308717.git-patchwork-notify@kernel.org>
Date: Tue, 22 Nov 2022 09:10:15 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Suman Ghosh <sumang@...vell.com>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, sgoutham@...vell.com, sbhatta@...vell.com,
jerinj@...vell.com, gakula@...vell.com, hkelam@...vell.com,
lcherian@...vell.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [net-next PATCH] octeontx2-pf: Add additional checks while
configuring ucast/bcast/mcast rules
Hello:
This patch was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@...hat.com>:
On Fri, 18 Nov 2022 11:03:29 +0530 you wrote:
> 1. If a profile does not support DMAC extraction then avoid installing NPC
> flow rules for unicast. Similarly, if LXMB(L2 and L3) extraction is not
> supported by the profile then avoid installing broadcast and multicast
> rules.
> 2. Allow MCAM entry insertion for promiscuous mode.
> 3. For the profiles where DMAC is not extracted in MKEX key default
> unicast entry installed by AF is not valid. Hence do not use action
> from the AF installed default unicast entry for such cases.
> 4. Adjacent packet header fields in a packet like IP header source
> and destination addresses or UDP/TCP header source port and destination
> can be extracted together in MKEX profile. Therefore MKEX profile can be
> configured to in two ways:
> a. Total of 4 bytes from start of UDP header(src port
> + destination port)
> or
> b. Two bytes from start and two bytes from offset 2
>
> [...]
Here is the summary with links:
- [net-next] octeontx2-pf: Add additional checks while configuring ucast/bcast/mcast rules
https://git.kernel.org/netdev/net-next/c/674b3e164238
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