From: Jakub Kicinski <kuba@kernel.org>
To: Subbaraya Sundeep <sbhatta@marvell.com>
Cc: <davem@davemloft.net>, <pabeni@redhat.com>, <edumazet@google.com>,
<sgoutham@marvell.com>, <netdev@vger.kernel.org>,
Suman Ghosh <sumang@marvell.com>
Subject: Re: [net v2 PATCH 3/5] octeontx2-af: Allow mkex profiles without dmac.
Date: Wed, 27 Jul 2022 19:51:06 -0700 [thread overview]
Message-ID: <20220727195106.44100254@kernel.org> (raw)
In-Reply-To: <1658844682-12913-4-git-send-email-sbhatta@marvell.com>
On Tue, 26 Jul 2022 19:41:20 +0530 Subbaraya Sundeep wrote:
> From: Suman Ghosh <sumang@marvell.com>
>
> It is possible to have custom mkex profiles which do not extract
> DMAC into the key to free up space in the key and use it for L3
> or L4 packet fields. Current code bails out if DMAC extraction is
> not present in the key. This patch fixes it by allowing profiles
> without DMAC and also supports installing rules based on L2MB bit
> set by hardware for multicast and broadcast packets.
This sounds half way between a feature and a fix. Can you make it
clearer why it's a fix and not an optimization?
> This patch also adds debugging prints needed to identify profiles
> with wrong configuration.
All those prints make the patch even less acceptable as a fix.
We merge fixes into net-next every week, you can send a minimal
fix and extend the code in net-next soon after that.
> Fixes: 9b179a960a96 ("octeontx2-af: Generate key field bit mask from KEX profile")
> + /* If DMAC is not extracted in MKEX, rules installed by AF
> + * can rely on L2MB bit set by hardware protocol checker for
> + * broadcast and multicast addresses.
> + */
> + if (npc_check_field(rvu, blkaddr, NPC_DMAC, req->intf))
> + goto process_flow;
Merge this condition with the condition below, goto should be avoided
but for error paths.
> + if (is_pffunc_af(req->hdr.pcifunc) &&
> + req->features & BIT_ULL(NPC_DMAC)) {
> + if (is_unicast_ether_addr(req->packet.dmac)) {
> + dev_err(rvu->dev,
> + "%s: mkex profile does not support ucast flow\n",
> + __func__);
> + return NPC_FLOW_NOT_SUPPORTED;
> + }
> +
> + if (!npc_is_field_present(rvu, NPC_LXMB, req->intf)) {
> + dev_err(rvu->dev,
> + "%s: mkex profile does not support bcast/mcast flow",
> + __func__);
> + return NPC_FLOW_NOT_SUPPORTED;
> + }
> +
> + /* Modify feature to use LXMB instead of DMAC */
> + req->features &= ~BIT_ULL(NPC_DMAC);
> + req->features |= BIT_ULL(NPC_LXMB);
> + }
> +
> +process_flow:
> if (from_vf && req->default_rule)
> return NPC_FLOW_VF_PERM_DENIED;
>
next prev parent reply other threads:[~2022-07-28 2:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 14:11 [net v2 PATCH 0/5] Octeontx2 AF driver fixes for NPC Subbaraya Sundeep
2022-07-26 14:11 ` [net v2 PATCH 1/5] octeontx2-af: Apply tx nibble fixup always Subbaraya Sundeep
2022-07-26 14:11 ` [net v2 PATCH 2/5] octeontx2-af: suppress external profile loading warning Subbaraya Sundeep
2022-07-28 2:41 ` Jakub Kicinski
2022-07-28 2:51 ` Jakub Kicinski
2022-07-26 14:11 ` [net v2 PATCH 3/5] octeontx2-af: Allow mkex profiles without dmac Subbaraya Sundeep
2022-07-28 2:51 ` Jakub Kicinski [this message]
2022-07-26 14:11 ` [net v2 PATCH 4/5] octeontx2-af: Fix mcam entry resource leak Subbaraya Sundeep
2022-07-26 14:11 ` [net v2 PATCH 5/5] octeontx2-af: Fix key checking for source mac Subbaraya Sundeep
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=20220727195106.44100254@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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;
as well as URLs for NNTP newsgroup(s).