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:tho...@monjalon.net] Sent: Wednesday, August 05, 2020 4:29 PM To: Kishore Padmanabha <kishore.padmana...@broadcom.com> Cc: dev@dpdk.org; ferruh.yi...@intel.com; Shahaji Bhosle <sbho...@broadcom.com>; Mike Baucom <michael.bau...@broadcom.com>; Ajit Khaparde <ajit.khapa...@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.padmana...@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.padmana...@broadcom.com> > Reviewed-by: Shahaji Bhosle <sbho...@broadcom.com> > Reviewed-by: Mike Baucom <michael.bau...@broadcom.com> > Reviewed-by: Ajit Khaparde <ajit.khapa...@broadcom.com>
