From: Ali Alnubani <alialnu@mellanox.com>
To: Luca Boccassi <bluca@debian.org>, dpdk stable <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Akhil Goyal <akhil.goyal@nxp.com>,
"benjamin.walker@intel.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" <pingx.yu@intel.com>,
"qian.q.xu@intel.com" <qian.q.xu@intel.com>,
Raslan Darawsheh <rasland@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>,
"yuan.peng@intel.com" <yuan.peng@intel.com>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: Re: [dpdk-dev] 17.11.10 (LTS) patches review and test
Date: Wed, 22 Jan 2020 16:06:30 +0000 [thread overview]
Message-ID: <AM0PR05MB4401D252848D7A0DAB35684AD70C0@AM0PR05MB4401.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <630ab48b958f4bea1c31e83b8a200f236cd6fcff.camel@debian.org>
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
next prev parent reply other threads:[~2020-01-22 16:06 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 ` Luca Boccassi
2020-01-22 5:27 ` Yu, PingX
2020-01-22 11:37 ` Luca Boccassi
2020-01-22 14:17 ` [dpdk-dev] [dpdk-stable] " Kevin Traynor
2020-01-22 16:07 ` Luca Boccassi
2020-01-22 16:06 ` Ali Alnubani [this message]
2020-01-22 16:34 ` [dpdk-dev] " Luca Boccassi
2020-01-23 11:05 ` Luca Boccassi
2020-01-26 14:58 ` Ali Alnubani
2020-01-27 10:41 ` Luca Boccassi
2020-01-30 10:08 ` Luca Boccassi
2020-01-30 15:01 ` Stokes, Ian
2020-01-30 15:25 ` Luca Boccassi
2020-02-15 11:21 ` Luca Boccassi
2020-02-20 10:00 ` Luca Boccassi
2020-02-20 11:37 ` 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=AM0PR05MB4401D252848D7A0DAB35684AD70C0@AM0PR05MB4401.eurprd05.prod.outlook.com \
--to=alialnu@mellanox.com \
--cc=akhil.goyal@nxp.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=hemant.agrawal@nxp.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=ktraynor@redhat.com \
--cc=pezhang@redhat.com \
--cc=pingx.yu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@mellanox.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yuan.peng@intel.com \
--cc=zhaoyan.chen@intel.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).