DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@nvidia.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.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>,
	"hariprasad.govindharajan@intel.com"
	<hariprasad.govindharajan@intel.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" <pingx.yu@intel.com>,
	"qian.q.xu@intel.com" <qian.q.xu@intel.com>,
	Raslan Darawsheh <rasland@nvidia.com>,
	NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
	"yuan.peng@intel.com" <yuan.peng@intel.com>,
	"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>,
	Asaf Penso <asafp@nvidia.com>
Subject: Re: [dpdk-dev] 19.11.7 patches review and test
Date: Mon, 15 Mar 2021 13:39:39 +0000	[thread overview]
Message-ID: <MWHPR12MB1472581BBE62436F91643562DA6C9@MWHPR12MB1472.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210310133709.562846-1-christian.ehrhardt@canonical.com>

Hi,

> -----Original Message-----
> From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> Sent: Wednesday, March 10, 2021 3:37 PM
> To: stable@dpdk.org
> Cc: dev@dpdk.org; Abhishek Marathe <Abhishek.Marathe@microsoft.com>;
> Akhil Goyal <akhil.goyal@nxp.com>; Ali Alnubani <alialnu@nvidia.com>;
> benjamin.walker@intel.com; David Christensen <drc@linux.vnet.ibm.com>;
> hariprasad.govindharajan@intel.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@nvidia.com>; NBU-Contact-Thomas Monjalon
> <thomas@monjalon.net>; yuan.peng@intel.com; zhaoyan.chen@intel.com
> Subject: 19.11.7 patches review and test
> 
> Hi all,
> 
> Here is a list of patches targeted for stable release 19.11.7.
> 
> The (new) planned date for the final release is 17th of March.
> 
> 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.
> 
> A release candidate tarball can be found at:
> 
>     https://dpdk.org/browse/dpdk-stable/tag/?id=v19.11.7-rc2
> 
> These patches are located at branch 19.11 of dpdk-stable repo:
>     https://dpdk.org/browse/dpdk-stable/
> 
> Thanks.
> 
> Christian Ehrhardt <christian.ehrhardt@canonical.com>
> 
> ---

Thanks Christian for creating the new release candidate.

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 test.
- testpmd timestamp test.
- Changing/checking link status through testpmd.
- RTE flow tests:
  Items: eth / vlan / ipv4 / ipv6 / tcp / udp / icmp / gre / nvgre / vxlan / ip in ip / mplsoudp / mplsogre
  Actions: drop / queue / rss / mark / flag / jump / count / raw_encap / raw_decap / vxlan_encap / vxlan_decap / NAT / dec_ttl
- Some RSS tests.
- VLAN filtering, stripping and insertion tests.
- Checksum and TSO tests.
- ptype tests.
- link_status_interrupt example application 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-2.2.0.0 / Firmware: 14.29.2002
- NIC: ConnectX-5 / OS: RHEL7.4 / Driver: MLNX_OFED_LINUX-5.2-2.2.0.0 / Firmware: 16.29.2002

Compilation tests with multiple configurations in the following OS/driver combinations are also passing:
- Ubuntu 20.04.2 with MLNX_OFED_LINUX-5.2-2.2.0.0.
- Ubuntu 20.04.2 with rdma-core master (a1a9ffb).
- Ubuntu 20.04.2 with rdma-core v28.0.
- Ubuntu 18.04.5 with rdma-core v17.1.
- Ubuntu 18.04.5 with rdma-core master (a1a9ffb) (i386).
- Ubuntu 16.04.7 with rdma-core v22.7.
- Fedora 32 with rdma-core v33.0.
- CentOS 7 7.9.2009 with rdma-core master (a1a9ffb).
- CentOS 7 7.9.2009 with MLNX_OFED_LINUX-5.2-2.2.0.0.
- CentOS 8 8.3.2011 with rdma-core master (a1a9ffb).
- OpenSUSE Leap 15.2 with rdma-core v27.1.

We don't see any new issues in this release candidate. However, due to environment changes, we started seeing the following issue, which reproduces in older 19.11 releases as well:
https://bugs.dpdk.org/show_bug.cgi?id=661
We will not fix this issue in this release.

Regards,
Ali

  reply	other threads:[~2021-03-15 13:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22 15:58 Christian Ehrhardt
2021-02-24  9:11 ` [dpdk-dev] [dpdk-stable] " Christian Ehrhardt
2021-03-01  5:48 ` [dpdk-dev] " Pei Zhang
2021-03-02  3:29 ` Chen, BoX C
2021-03-08 16:18   ` Christian Ehrhardt
2021-03-04 10:43 ` Yu, PingX
2021-03-08 15:27   ` Christian Ehrhardt
2021-03-10  5:57     ` Yu, PingX
2021-03-10 11:18       ` Christian Ehrhardt
2021-03-10 13:37 ` Christian Ehrhardt
2021-03-15 13:39   ` Ali Alnubani [this message]
2021-03-16  9:52   ` Chen, BoX C
2021-03-16 11:17   ` Govindharajan, Hariprasad

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=MWHPR12MB1472581BBE62436F91643562DA6C9@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=christian.ehrhardt@canonical.com \
    --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@nvidia.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).