On Tue, Sep 28, 2021 at 5:43 AM Ferruh Yigit <ferruh.yi...@intel.com> wrote: > > On 9/20/2021 8:42 AM, Venkat Duvvuru wrote: > > From: Kishore Padmanabha <kishore.padmana...@broadcom.com> > > > > Add support for tunnel offload APIs. Specifically the following > > are supported. > > tunnel_decap_set, tunnel_match, tunnel_action_decap_release, > > tunnel_item_release. > > > > This provides support for VXLAN decap action where two flows > > can indicate tunnel offload rule. The first flow indicates the > > tunnel properties and second flow indicates the inner packet > > structure. The templates are updated to support this > > feature. > > > > Signed-off-by: Kishore Padmanabha <kishore.padmana...@broadcom.com> > > Signed-off-by: Venkat Duvvuru <venkatkumar.duvv...@broadcom.com> > > Reviewed-by: Shahaji Bhosle <sbho...@broadcom.com> > > Acked-by: Ajit Khaparde <ajit.khapa...@broadcom.com> > > > Hi Ajit, > > Following warning is reported by Jerin & Thomas: > > $ ./devtools/check-doc-vs-code.sh > rte_flow doc out of sync for bnxt > action shared > > > This is mainly saying 'RTE_FLOW_ACTION_TYPE_SHARED' flow action is supported > but > not documented. But from code I am not sure if shared action is used, there is > only one range check using this enum in the code, can you please clarify?
Correct. RTE_FLOW_ACTION_TYPE_SHARED is being used only for a range check. It is not really a supported action right now as far as the code is concerned. As of now, no document update is necessary. Thanks > If it is supported I can update the documentation. > > Thanks, > ferruh
