[dpdk-dev] [PATCH v2 00/58] enhancements to host based flow table management
Ajit Khaparde
ajit.khaparde at broadcom.com
Thu Jul 8 16:37:50 CEST 2021
On Thu, Jul 8, 2021 at 5:51 AM Thomas Monjalon <thomas at monjalon.net> wrote:
> 08/07/2021 05:57, Ajit Khaparde:
> > On Wed, Jul 7, 2021 at 1:43 AM Thomas Monjalon <thomas at monjalon.net>
> wrote:
> > > 15/06/2021 21:33, Ajit Khaparde:
> > > > On Sat, Jun 12, 2021 at 5:06 PM Ajit Khaparde
> > > > <ajit.khaparde at broadcom.com> wrote:
> > > > >
> > > > > This patchset adds flow table management support for
> > > > > Thor network adapter and introduces enhancements to
> > > > > the existing flow table management functionality.
> > > > >
> > > > > v1->v2:
> > > > > - Rebased against latest dpdk-next-net-brcm for-next-net branch.
> > > > > - Fixed typo errors in some of the patches
> > > > > - Address some issues encountered while applying patches
> > > > > - Changed log levels for some log messages to debug
> > > > > - Cleaned up some unused code
> > > >
> > > > Patchset applied to the for-next-net branch of dpdk-next-net-brcm.
> > > > Thanks
> > >
> > > These 3 tools are returning errors:
> > >
> > > devtools/check-meson.py
> > > devtools/check-spdx-tag.sh
> > > devtools/check-doc-vs-code.sh
> > >
> > > 1/ The meson files have a new indent policy.
> > > 2/ The SPDX tag is missing in some hcapi_cfa files.
> > > 3/ devtools/parse-flow-support.sh must be updated with new bnxt path
> > >
> > > Please fix in dpdk-next-net-brcm.
> > >
> > Done and changes pushed to the for-next-net branch of
> dpdk-next-net-brcm.
>
> There is still an issue with the third tool mentionned above:
>
> devtools/check-doc-vs-code.sh
> rte_flow doc out of sync for bnxt
> item any
> item gre
> item icmp
> item icmp6
> action dec_ttl
> action jump
> action of_pop_vlan
> action of_push_vlan
> action of_set_vlan_pcp
> action of_set_vlan_vid
> action sample
> action set_ipv4_dst
> action set_ipv4_src
> action set_tp_dst
> action set_tp_src
>
> The file doc/guides/nics/features/bnxt.ini must be updated in each patch
> adding a new support of an item or an action.
>
> I fixed all by making sure the below command passing:
> git rebase -i --exec devtools/check-doc-vs-code.sh origin/main
>
Thanks. Let me know if you want me to fix anything else for the merge.
More information about the dev
mailing list