patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@mellanox.com>
To: Luca Boccassi <bluca@debian.org>, dpdk stable <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Raslan Darawsheh <rasland@mellanox.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Slava Ovsiienko <viacheslavo@mellanox.com>,
	Matan Azrad <matan@mellanox.com>, Phil Yang <phil.yang@arm.com>,
	David Marchand <david.marchand@redhat.com>,
	"Xueming(Steven) Li" <xuemingl@mellanox.com>
Subject: Re: [dpdk-stable] 17.11.10 (LTS) patches review and test
Date: Sun, 26 Jan 2020 14:58:52 +0000	[thread overview]
Message-ID: <AM0PR05MB440128AB2925462DDB14C611D7080@AM0PR05MB4401.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <6ca12b1f06f3f8b0b05f53717abc17743076896e.camel@debian.org>

Hi Luca,
Sorry for the late response 😊

> -----Original Message-----
> From: Luca Boccassi <bluca@debian.org>
> Sent: Thursday, January 23, 2020 1:06 PM
> To: Ali Alnubani <alialnu@mellanox.com>; dpdk stable <stable@dpdk.org>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@mellanox.com>; Thomas
> Monjalon <thomas@monjalon.net>; Slava Ovsiienko
> <viacheslavo@mellanox.com>; Matan Azrad <matan@mellanox.com>; Phil
> Yang <phil.yang@arm.com>; David Marchand
> <david.marchand@redhat.com>
> Subject: Re: 17.11.10 (LTS) patches review and test
> 
> 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@debian.org
> > > >
> > > >
> > > > Sent: Monday, January 13, 2020 2:47 PM
> > > > To: dpdk stable <
> > > > stable@dpdk.org
> > > >
> > > >
> > > > Cc:
> > > > dev@dpdk.org
> > > >
> > > > ; Akhil Goyal <
> > > > akhil.goyal@nxp.com
> > > >
> > > > > ; Ali Alnubani
> > > >
> > > > <
> > > > alialnu@mellanox.com
> > > >
> > > > > ;
> > > >
> > > > benjamin.walker@intel.com
> > > >
> > > > ; David Christensen
> > > > <
> > > > drc@linux.vnet.ibm.com
> > > >
> > > > > ; Hemant Agrawal <
> > > >
> > > > hemant.agrawal@nxp.com
> > > >
> > > > > ;
> > > >
> > > > Ian Stokes <
> > > > ian.stokes@intel.com
> > > >
> > > > > ; Jerin Jacob <
> > > >
> > > > jerinj@marvell.com
> > > >
> > > > > ; John
> > > >
> > > > McNamara <
> > > > john.mcnamara@intel.com
> > > >
> > > > > ; Kevin Traynor
> > > >
> > > > <
> > > > ktraynor@redhat.com
> > > >
> > > > > ; Pei Zhang <
> > > >
> > > > pezhang@redhat.com
> > > >
> > > > > ;
> > > >
> > > > pingx.yu@intel.com
> > > >
> > > > ;
> > > > qian.q.xu@intel.com
> > > >
> > > > ; Raslan Darawsheh
> > > > <
> > > > rasland@mellanox.com
> > > >
> > > > > ; Thomas Monjalon <
> > > >
> > > > thomas@monjalon.net
> > > >
> > > > > ;
> > > >
> > > > yuan.peng@intel.com
> > > >
> > > > ; Chen, Zhaoyan <
> > > > zhaoyan.chen@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?

Only the segfault is caused by new changes. It is caused by commit:
https://git.dpdk.org/dpdk-stable/commit/?h=17.11&id=a10a7083d164fb48cc3978067820c3d256899f3e (Added Xueming Li to CC list.)
I should've reported the rest of the issues earlier, my bad.

> 
> 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*:
> 
<removed>
> 
> They seem quite innocous to me, but I might be wrong. Authors and
> reviewers CC'ed.
> 
> - there's no "off_t" reference in MLX4

This started reproducing since driver (MLNX_OFED_LINUX) version 4.6-1.0.1.1. Full error:
"""
In file included from /path/to/drivers/net/mlx4/mlx4_rxq.c:49:0:
/usr/include/infiniband/mlx4dv.h:176:2: error: unknown type name ‘off_t’
  off_t   uar_mmap_offset;
  ^
make[6]: *** [mlx4_rxq.o] Error 1
make[6]: *** Waiting for unfinished jobs....
"""

> - the only flow change was this commit and it seems unrelated:
> 
<removed>
> 
> 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?

Regarding issues:
- Count action isn’t supported in rte_flow.
- Error creating rte_flow rules with vlan items.
These are related to support in the OFED driver, and we still need to do more investigation.

> 
> Thanks!
> 
> --
> Kind regards,
> Luca Boccassi

Regards,
Ali

  reply	other threads:[~2020-01-26 14:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 12:47 Luca Boccassi
2020-01-17  2:52 ` Pei Zhang
2020-01-17 10:44   ` [dpdk-stable] [dpdk-dev] " Luca Boccassi
2020-01-22  5:27 ` [dpdk-stable] " Yu, PingX
2020-01-22 11:37   ` [dpdk-stable] [dpdk-dev] " Luca Boccassi
2020-01-22 14:17     ` Kevin Traynor
2020-01-22 16:07       ` Luca Boccassi
2020-01-22 16:06 ` [dpdk-stable] " Ali Alnubani
2020-01-22 16:34   ` Luca Boccassi
2020-01-23 11:05     ` Luca Boccassi
2020-01-26 14:58       ` Ali Alnubani [this message]
2020-01-27 10:41         ` [dpdk-stable] [dpdk-dev] " Luca Boccassi
2020-01-30 10:08 ` [dpdk-stable] " Luca Boccassi
2020-01-30 15:01   ` [dpdk-stable] [dpdk-dev] " Stokes, Ian
2020-01-30 15:25     ` Luca Boccassi
2020-02-15 11:21   ` [dpdk-stable] " Luca Boccassi
2020-02-20 10:00     ` Luca Boccassi
2020-02-20 11:37       ` [dpdk-stable] [dpdk-dev] " Trahe, Fiona

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AM0PR05MB440128AB2925462DDB14C611D7080@AM0PR05MB4401.eurprd05.prod.outlook.com \
    --to=alialnu@mellanox.com \
    --cc=bluca@debian.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=phil.yang@arm.com \
    --cc=rasland@mellanox.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@mellanox.com \
    --cc=xuemingl@mellanox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).