From: patchwork-bot+netdevbpf@kernel.org
To: Suman Ghosh <sumang@marvell.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, sgoutham@marvell.com, sbhatta@marvell.com,
jerinj@marvell.com, gakula@marvell.com, hkelam@marvell.com,
lcherian@marvell.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [net-next PATCH] octeontx2-pf: Add additional checks while configuring ucast/bcast/mcast rules
Date: Tue, 22 Nov 2022 09:10:15 +0000 [thread overview]
Message-ID: <166910821529.27872.4243816404919308717.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221118053329.2288486-1-sumang@marvell.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.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
prev parent reply other threads:[~2022-11-22 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 5:33 [net-next PATCH] octeontx2-pf: Add additional checks while configuring ucast/bcast/mcast rules Suman Ghosh
2022-11-22 9: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=166910821529.27872.4243816404919308717.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=sumang@marvell.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