[dpdk-dev] 17.11.10 (LTS) patches review and test

[Luca Boccassi]

On Wed, 2020-01-22 at 16:34 +0000, Luca Boccassi wrote:
> On Wed, 2020-01-22 at 16:06 +0000, Ali Alnubani wrote:
> > Hi,
> > 
> > > -----Original Message-----
> > > From: Luca Boccassi <
> > > bluca at debian.org
> > > 
> > > 
> > > Sent: Monday, January 13, 2020 2:47 PM
> > > To: dpdk stable <
> > > stable at dpdk.org
> > > 
> > > 
> > > Cc: 
> > > dev at dpdk.org
> > > 
> > > ; 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
> > > 
> > > > ; Kevin Traynor
> > > 
> > > <
> > > ktraynor at redhat.com
> > > 
> > > > ; Pei Zhang <
> > > 
> > > pezhang at redhat.com
> > > 
> > > > ;
> > > 
> > > pingx.yu at intel.com
> > > 
> > > ; 
> > > qian.q.xu at intel.com
> > > 
> > > ; Raslan Darawsheh
> > > <
> > > rasland at mellanox.com
> > > 
> > > > ; Thomas Monjalon <
> > > 
> > > thomas at monjalon.net
> > > 
> > > > ;
> > > 
> > > yuan.peng at intel.com
> > > 
> > > ; Chen, Zhaoyan <
> > > zhaoyan.chen at intel.com
> > > 
> > > 
> > > Subject: 17.11.10 (LTS) patches review and test
> > > 
> > > Hi all,
> > > 
> > > Here is a list of patches targeted for LTS release 17.11.10.
> > > This will be the last 17.11 release.
> > > 
> > > The planned date for the final release is the 30th of January.
> > > 
> > > 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 cases were tested on Mellanox devices:
> > - Verify sending and receiving 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.
> > - Multi-process tests.
> > 
> > Testing matrix:
> > - NIC: ConnectX-4 Lx / OS: RHEL7.4 / Driver: MLNX_OFED_LINUX-4.7-
> > 3.2.9.0 / Firmware: 14.26.4012
> > - NIC: ConnectX-5 / OS: RHEL7.4 / Driver: MLNX_OFED_LINUX-4.7-
> > 3.2.9.0 
> > / Firmware: 16.26.4012
> > 
> > Current issues:
> > - The message “PMD: Failed to send netlink message: Bad file
> > descriptor (9)” is shown at testpmd startup. Still didn’t debug its
> > effect on functionality.
> > - ibv_icmd_create_cq () from /lib64/libibverbs.so.1 segfaults after
> > setting the number of queues and restarting the ports.
> > - Enabling MLX4_PMD causes a build failure with OFED-4.7-3.2.9.0
> > (“error: unknown type name ‘off_t’”).
> > - Count action isn’t supported in rte_flow.
> > - Error creating rte_flow rules with vlan items.
> > 
> > 
> > Regards,
> > Ali
> 
> Thanks - are these new regressions since 17.11.9?

It was mentioned in the release meeting call that they are new
regressions since 17.11.10-rc1 - these are the commits that were
backported that changed drivers/mlx*:

https://git.dpdk.org/dpdk-stable/commit/?h=17.11&id=60d0f2e079
https://git.dpdk.org/dpdk-stable/commit/?h=17.11&id=005b17cbab
https://git.dpdk.org/dpdk-stable/commit/?h=17.11&id=4cd784b02d
https://git.dpdk.org/dpdk-stable/commit/?h=17.11&id=569c98371e

They seem quite innocous to me, but I might be wrong. Authors and
reviewers CC'ed.

- there's no "off_t" reference in MLX4
- the only flow change was this commit and it seems unrelated:

https://git.dpdk.org/dpdk-stable/commit/?h=17.11&id=940d6c60d5748

So I'd imagine it could be some unrelated change, in the core
libraries, that causes these issues. Would you be able to bisect the
tree to see exactly which commits cause issues?

Thanks!

-- 
Kind regards,
Luca Boccassi