[dpdk-dev] [PATCH v2 2/4] net/bnxt: fix lookup for default parif action record

Kishore Padmanabha kishore.padmanabha at broadcom.com
Thu Aug 6 03:27:50 CEST 2020


Hi Thomas,

The commit message could be changed to "must".
In the HW offload, if the incoming packet match fails in the exact match
table, then the packet needs to use a default action. This default action
is being configured as part of this patch. The parif is a HW table and it
is being configured so that there is default action for the missed
packets.

Rgds,
Kishore

-----Original Message-----
From: Thomas Monjalon [mailto:thomas at monjalon.net]
Sent: Wednesday, August 05, 2020 4:29 PM
To: Kishore Padmanabha <kishore.padmanabha at broadcom.com>
Cc: dev at dpdk.org; ferruh.yigit at intel.com; Shahaji Bhosle
<sbhosle at broadcom.com>; Mike Baucom <michael.baucom at broadcom.com>; Ajit
Khaparde <ajit.khaparde at broadcom.com>
Subject: Re: [dpdk-dev] [PATCH v2 2/4] net/bnxt: fix lookup for default
parif action record

31/07/2020 19:23, Ajit Khaparde:
> From: Kishore Padmanabha <kishore.padmanabha at broadcom.com>
>
> The lookup default action record parif table is updated to catch the
> miss path for the entries in the exact match table.
>
> Fixes: fe82f3e02701 ("net/bnxt: support exact match templates")

It doesn't look like a fix.

What is "parif action"?

> Signed-off-by: Kishore Padmanabha <kishore.padmanabha at broadcom.com>
> Reviewed-by: Shahaji Bhosle <sbhosle at broadcom.com>
> Reviewed-by: Mike Baucom <michael.baucom at broadcom.com>
> Reviewed-by: Ajit Khaparde <ajit.khaparde at broadcom.com>


More information about the dev mailing list