[dpdk-stable] 18.11.11 (LTS) patches review and test

[Ali Alnubani]

Hi Kevin,

> -----Original Message-----
> From: Kevin Traynor <ktraynor at redhat.com>
> Sent: Thursday, January 14, 2021 6:55 PM
> To: Ali Alnubani <alialnu at nvidia.com>; stable at dpdk.org
> Cc: dev at dpdk.org; Abhishek Marathe <Abhishek.Marathe at microsoft.com>;
> Akhil Goyal <akhil.goyal at nxp.com>; benjamin.walker at intel.com; David
> Christensen <drc at linux.vnet.ibm.com>; Hemant Agrawal
> <hemant.agrawal at nxp.com>; Ian Stokes <ian.stokes at intel.com>; Jerin
> Jacob <jerinj at marvell.com>; John McNamara <john.mcnamara at intel.com>;
> Ju-Hyoung Lee <juhlee at microsoft.com>; Luca Boccassi <bluca at debian.org>;
> Pei Zhang <pezhang at redhat.com>; pingx.yu at intel.com;
> qian.q.xu at intel.com; Raslan Darawsheh <rasland at mellanox.com>; NBU-
> Contact-Thomas Monjalon <thomas at monjalon.net>; yuan.peng at intel.com;
> zhaoyan.chen at intel.com; hariprasad.govindharajan at intel.com; Slava
> Ovsiienko <viacheslavo at nvidia.com>; Asaf Penso <asafp at nvidia.com>
> Subject: Re: [dpdk-stable] 18.11.11 (LTS) patches review and test
> 
> On 14/01/2021 15:11, Ali Alnubani wrote:
> > Hi,
> >
> 
> Hi Ali,
> 
> >> -----Original Message-----
> >> From: stable <stable-bounces at dpdk.org> On Behalf Of Kevin Traynor
> >> Sent: Thursday, December 17, 2020 2:03 PM
> >> To: stable at dpdk.org
> >> Cc: dev at dpdk.org; Abhishek Marathe
> <Abhishek.Marathe at microsoft.com>;
> >> Akhil Goyal <akhil.goyal at nxp.com>; Ali Alnubani
> >> <alialnu at mellanox.com>; benjamin.walker at intel.com; David Christensen
> >> <drc at linux.vnet.ibm.com>; Hemant Agrawal
> <hemant.agrawal at nxp.com>;
> >> Ian Stokes <ian.stokes at intel.com>; Jerin Jacob <jerinj at marvell.com>;
> >> John McNamara <john.mcnamara at intel.com>; Ju-Hyoung Lee
> >> <juhlee at microsoft.com>; Kevin Traynor <ktraynor at redhat.com>; Luca
> >> Boccassi <bluca at debian.org>; Pei Zhang <pezhang at redhat.com>;
> >> pingx.yu at intel.com; qian.q.xu at intel.com; Raslan Darawsheh
> >> <rasland at mellanox.com>; NBU- Contact-Thomas Monjalon
> >> <thomas at monjalon.net>; yuan.peng at intel.com;
> zhaoyan.chen at intel.com;
> >> hariprasad.govindharajan at intel.com
> >> Subject: [dpdk-stable] 18.11.11 (LTS) patches review and test
> >>
> >> Hi all,
> >>
> >> Here is a list of patches targeted for LTS release 18.11.11.
> >>
> >> The planned date for the final release is 19th January.
> >>
> >> Note, this is the last planned release of 18.11 LTS, and it will be
> >> unmaintained after this release, so I encourage anyone who is using
> >> 18.11 LTS to test.
> >>
> >> Please help with testing and validation of your use cases and report
> >> any issues/results with reply-all to this mail. For the final release
> >> the fixes and reported validations will be added to the release notes.
> >>
> >
> > The following covers the functional tests that we ran on Mellanox
> hardware for this release:
> > - Basic functionality:
> >   Send and receive multiple types of traffic.
> > - testpmd xstats counter tests.
> > - testpmd timestamp tests.
> > - Changing/checking link status through testpmd.
> > - RTE flow and flow_director tests.
> > - Some RSS tests.
> > - VLAN stripping and insertion tests.
> > - Checksum and TSO tests.
> > - ptype tests.
> > - l3fwd-power example application tests.
> > - Multi-process example applications tests.
> >
> > Functional tests ran on:
> > - NIC: ConnectX-4 Lx / OS: RHEL7.4 / Driver:
> > MLNX_OFED_LINUX-5.2-1.0.4.0 / Firmware: 14.29.1016
> > - NIC: ConnectX-5 / OS: RHEL7.4 / Driver: MLNX_OFED_LINUX-5.2-1.0.4.0
> > / Firmware: 16.29.1016
> >
> 
> Thanks for your testing.
> 
> > We don't see any issues introduced by the new changes in this release,
> however, we found the following issues while testing due to environment
> changes:
> > - Bug 615 - testpmd gets stuck when deleting an FDIR flow -
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs
> .dpdk.org%2Fshow_bug.cgi%3Fid%3D615&data=04%7C01%7Calialnu%4
> 0nvidia.com%7C0697f1840c024f99d82908d8b8ad45a0%7C43083d15727340c1b
> 7db39efd9ccc17a%7C0%7C0%7C637462401681676672%7CUnknown%7CTWFp
> bGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVC
> I6Mn0%3D%7C1000&sdata=4DWeo1yuZd7Y1%2BgfkX4vkTQGkrqtYLPFR
> 4KBTb2J5Us%3D&reserved=0 - Won't fix.
> > - Bug 616 - [mlx5] packet does not match a corresponding rte_flow rule due
> to inner ether_type spec validation -
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs
> .dpdk.org%2Fshow_bug.cgi%3Fid%3D616&data=04%7C01%7Calialnu%4
> 0nvidia.com%7C0697f1840c024f99d82908d8b8ad45a0%7C43083d15727340c1b
> 7db39efd9ccc17a%7C0%7C0%7C637462401681686667%7CUnknown%7CTWFp
> bGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVC
> I6Mn0%3D%7C1000&sdata=EzIwmXI5Fd9o2AA33sU26MNrYOBbgTugfh
> Cm0gHFzEA%3D&reserved=0 - Won't fix.
> > - Bug 617 - [mlx5] packet does not match a corresponding rte_flow rule due
> to vxlan vni spec validation -
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs
> .dpdk.org%2Fshow_bug.cgi%3Fid%3D617&data=04%7C01%7Calialnu%4
> 0nvidia.com%7C0697f1840c024f99d82908d8b8ad45a0%7C43083d15727340c1b
> 7db39efd9ccc17a%7C0%7C0%7C637462401681686667%7CUnknown%7CTWFp
> bGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVC
> I6Mn0%3D%7C1000&sdata=dCdR2epT0kOoTXs%2B2hrOZeTBtMI8jVHP6
> uKYKtTzbkA%3D&reserved=0 - Won't fix.
> 
> We can put these in the known issues section of the release notes.
> 
> > - Bug 618 - [mlx5] secondary process fails to start -
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs
> .dpdk.org%2Fshow_bug.cgi%3Fid%3D618&data=04%7C01%7Calialnu%4
> 0nvidia.com%7C0697f1840c024f99d82908d8b8ad45a0%7C43083d15727340c1b
> 7db39efd9ccc17a%7C0%7C0%7C637462401681686667%7CUnknown%7CTWFp
> bGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVC
> I6Mn0%3D%7C1000&sdata=Akc9dviCGiCfqbuFJZLbsC8%2BU394q9jYOKr
> fbOZlBXk%3D&reserved=0 - We are still looking into this.
> >
> 
> Ok, I'll keep an eye on the Bz and please add me on Cc: if there are patches
> to fix it and I can run them through the 18.11 build checks etc.
> 

Ran all my tests again on latest (660b995) and didn't see any new issues.

Thanks,
Ali