From: Ratheesh Kannoth <rkannoth@marvell.com>
To: <davem@davemloft.net>, <linux-kernel@vger.kernel.org>,
<naveenm@marvell.com>, <netdev@vger.kernel.org>
Cc: <andrew+netdev@lunn.ch>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <sgoutham@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>
Subject: Re: [PATCH v2 net] octeontx2-af: npc: Fix CPT channel mask in npc_install_flow
Date: Wed, 3 Jun 2026 10:37:48 +0530 [thread overview]
Message-ID: <ah-2pHqi1dpsdmB7@rkannoth-OptiPlex-7090> (raw)
In-Reply-To: <20260602045853.1558530-1-rkannoth@marvell.com>
On 2026-06-02 at 10:28:53, Ratheesh Kannoth (rkannoth@marvell.com) wrote:
> From: Nithin Dabilpuram <ndabilpuram@marvell.com>
>
> Use the CPT-aware NIX channel mask in the npc_install_flow path so that
> when the host PF installs steering rules in kernel for a VF used from
> userspace (e.g. DPDK), MCAM entries see the same channel mask semantics as
> other RX paths.
>
> Fixes: 56bcef528bd8 ("octeontx2-af: Use npc_install_flow API for promisc and broadcast entries")
> Cc: Naveen Mamindlapalli <naveenm@marvell.com>
> Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
> Signed-off-by: Ratheesh Kannoth <rkannoth@marvell.com>
> ---
https://sashiko.dev/#/patchset/20260602045853.1558530-1-rkannoth%40marvell.com
sashiko says:
> - /* For cn10k the upper two bits of the channel number are
>> - * cpt channel number. with masking out these bits in the
>> - * mcam entry, same entry used for NIX will allow packets
>> - * received from cpt for parsing.
>> - */
>> - if (!is_rvu_otx2(rvu))
>> - req.chan_mask = NIX_CHAN_CPT_X2P_MASK;
>> - else
>> - req.chan_mask = 0xFFFU;
>> -
>> + req.chan_mask = rvu_get_cpt_chan_mask(rvu);
>> req.channel = chan;
>> req.intf = pfvf->nix_rx_intf;
>> req.entry = index;
>This isn't a bug introduced by this patch, but should the channel mask
>also be updated in rvu_npc_install_bcast_match_entry() and
>rvu_switch_disable()?
No. we dont need this in bcast and switch_disable().
next prev parent reply other threads:[~2026-06-03 5:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 4:58 [PATCH v2 net] octeontx2-af: npc: Fix CPT channel mask in npc_install_flow Ratheesh Kannoth
2026-06-03 5:07 ` Ratheesh Kannoth [this message]
2026-06-04 15:40 ` 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=ah-2pHqi1dpsdmB7@rkannoth-OptiPlex-7090 \
--to=rkannoth@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naveenm@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgoutham@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