From: Ali Alnubani <alialnu@nvidia.com>
To: Kevin Traynor <ktraynor@redhat.com>, "stable@dpdk.org" <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
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>,
Ju-Hyoung Lee <juhlee@microsoft.com>,
"Luca Boccassi" <bluca@debian.org>,
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>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
"yuan.peng@intel.com" <yuan.peng@intel.com>,
"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>,
"hariprasad.govindharajan@intel.com"
<hariprasad.govindharajan@intel.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Asaf Penso <asafp@nvidia.com>
Subject: Re: [dpdk-stable] 18.11.11 (LTS) patches review and test
Date: Thu, 14 Jan 2021 15:11:07 +0000 [thread overview]
Message-ID: <MWHPR12MB1472366727AAE1E75A3305A3DAA80@MWHPR12MB1472.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20201217120304.351927-1-ktraynor@redhat.com>
Hi,
> -----Original Message-----
> From: stable <stable-bounces@dpdk.org> On Behalf Of Kevin Traynor
> Sent: Thursday, December 17, 2020 2:03 PM
> To: stable@dpdk.org
> Cc: dev@dpdk.org; Abhishek Marathe <Abhishek.Marathe@microsoft.com>;
> 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>; Ju-Hyoung Lee <juhlee@microsoft.com>;
> Kevin Traynor <ktraynor@redhat.com>; Luca Boccassi <bluca@debian.org>;
> Pei Zhang <pezhang@redhat.com>; pingx.yu@intel.com;
> qian.q.xu@intel.com; Raslan Darawsheh <rasland@mellanox.com>; NBU-
> Contact-Thomas Monjalon <thomas@monjalon.net>; yuan.peng@intel.com;
> zhaoyan.chen@intel.com; hariprasad.govindharajan@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
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://bugs.dpdk.org/show_bug.cgi?id=615 - Won't fix.
- Bug 616 - [mlx5] packet does not match a corresponding rte_flow rule due to inner ether_type spec validation - https://bugs.dpdk.org/show_bug.cgi?id=616 - Won't fix.
- Bug 617 - [mlx5] packet does not match a corresponding rte_flow rule due to vxlan vni spec validation - https://bugs.dpdk.org/show_bug.cgi?id=617 - Won't fix.
- Bug 618 - [mlx5] secondary process fails to start - https://bugs.dpdk.org/show_bug.cgi?id=618 - We are still looking into this.
Regards,
Ali
next prev parent reply other threads:[~2021-01-14 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 12:03 Kevin Traynor
2020-12-23 9:41 ` Pei Zhang
2021-01-05 16:24 ` Kevin Traynor
2020-12-29 9:01 ` [dpdk-stable] [dpdk-dev] " Chen, BoX C
2021-01-05 16:23 ` Kevin Traynor
2021-01-06 2:08 ` Chen, BoX C
2021-01-12 9:45 ` [dpdk-stable] " Kevin Traynor
2021-01-14 14:32 ` Govindharajan, Hariprasad
2021-01-14 16:50 ` Kevin Traynor
2021-01-14 15:11 ` Ali Alnubani [this message]
2021-01-14 16:55 ` Kevin Traynor
2021-01-20 10:55 ` Ali Alnubani
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=MWHPR12MB1472366727AAE1E75A3305A3DAA80@MWHPR12MB1472.namprd12.prod.outlook.com \
--to=alialnu@nvidia.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=akhil.goyal@nxp.com \
--cc=asafp@nvidia.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=hariprasad.govindharajan@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=juhlee@microsoft.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=viacheslavo@nvidia.com \
--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).