patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"dev@dpdk.org" <dev@dpdk.org>,
	 Abhishek Marathe <Abhishek.Marathe@microsoft.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>,
	 "qian.q.xu@intel.com" <qian.q.xu@intel.com>,
	Raslan Darawsheh <rasland@nvidia.com>,
	 "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
	"yuan.peng@intel.com" <yuan.peng@intel.com>,
	 "zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>
Subject: Re: 19.11.12 patches review and test
Date: Mon, 4 Apr 2022 09:12:45 +0200	[thread overview]
Message-ID: <CAATJJ0L81h65JBFy51G0C948xpyqeAkrpoZG+dC1-xs6WHH4SQ@mail.gmail.com> (raw)
In-Reply-To: <DM4PR12MB51677CA946793CC45AD40F65DAE59@DM4PR12MB5167.namprd12.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 3871 bytes --]

On Mon, Apr 4, 2022 at 8:52 AM Ali Alnubani <alialnu@nvidia.com> wrote:

> > -----Original Message-----
> > From: christian.ehrhardt@canonical.com
> > <christian.ehrhardt@canonical.com>
> > Sent: Monday, March 21, 2022 1:55 PM
> > To: stable@dpdk.org
> > Cc: dev@dpdk.org; Abhishek Marathe <Abhishek.Marathe@microsoft.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>; qian.q.xu@intel.com; Raslan Darawsheh
> > <rasland@nvidia.com>; NBU-Contact-Thomas Monjalon (EXTERNAL)
> > <thomas@monjalon.net>; yuan.peng@intel.com; zhaoyan.chen@intel.com
> > Subject: 19.11.12 patches review and test
> >
> > Hi all,
> >
> > Here is a list of patches targeted for stable release 19.11.12.
> >
> > The planned date for the final release is 7th of April.
> >
> > 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.
> >
>
> Hello,
>

Thank you Ali, added to the list of verifications of 19.11.12


> We ran the following functional tests with Nvidia hardware on 19.11.12-rc1:
> - 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 / ipv4 / ipv6 / tcp / udp / icmp / gre / nvgre / geneve /
> vxlan / 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: Ubuntu 20.04 LTS / Driver:
> MLNX_OFED_LINUX-5.5-1.0.3.2 / Firmware: 14.32.1010
> - NIC: ConnectX-4 Lx / OS: Ubuntu 20.04 LTS / Kernel: 5.17.0 / Driver:
> rdma-core v39.0 / Firmware: 14.32.1010
> - NIC: ConnectX-5 / OS: Ubuntu 20.04 LTS / Driver:
> MLNX_OFED_LINUX-5.5-1.0.3.2 / Firmware: 16.32.1010
> - NIC: ConnectX-5 / OS: Ubuntu 20.04 LTS / Kernel: 5.17.0 / Driver: v39.0
> / Firmware: 16.32.1010
>
> We also ran compilation tests with multiple configurations in the
> following OS/driver combinations:
> - Ubuntu 20.04.4 with MLNX_OFED_LINUX-5.5-1.0.3.2.
> - Ubuntu 20.04.4 with rdma-core v39.0.
> - Ubuntu 20.04.4 with rdma-core v28.0.
> - Ubuntu 18.04.6 with rdma-core v17.1.
> - Ubuntu 18.04.6 with rdma-core master (91004ec) (i386).
> - Ubuntu 16.04.7 with rdma-core v22.7.
> - Fedora 35 with rdma-core v39.0.
> - Fedora 37 (Rawhide) with rdma-core v39.0
> - CentOS 7 7.9.2009 with rdma-core master (91004ec).
> - CentOS 7 7.9.2009 with MLNX_OFED_LINUX-5.5-1.0.3.2.
> - CentOS 8 8.4.2105 with rdma-core master (91004ec).
> - OpenSUSE Leap 15.3 with rdma-core v31.0.
>
> Build failures:
> - Bug 912 - [19.11.11-rc1] net/qede build failure with make and clang 13 (
> https://bugs.dpdk.org/show_bug.cgi?id=912)
> - Bug 985 - [19.11] librte_eal build error with gcc 12 (
> https://bugs.dpdk.org/show_bug.cgi?id=985)
> - Bug 991 - [19.11] net/ena build failure with gcc 12 (
> https://bugs.dpdk.org/show_bug.cgi?id=991)
>
> We don't see any other new issues in this release.
>
> Thanks,
> Ali
>


-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

[-- Attachment #2: Type: text/html, Size: 6390 bytes --]

  reply	other threads:[~2022-04-04  7:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 11:55 christian.ehrhardt
2022-03-30 11:04 ` Jiang, YuX
2022-03-31 10:00   ` Christian Ehrhardt
2022-04-06  6:49     ` Christian Ehrhardt
2022-04-06  7:05       ` Jiang, YuX
2022-04-06  8:40         ` Christian Ehrhardt
2022-03-31 10:50 ` Christian Ehrhardt
2022-04-01 14:34 ` Kalesh Anakkur Purayil
2022-04-04  6:35   ` Christian Ehrhardt
2022-04-04  6:39 ` Christian Ehrhardt
2022-04-04  7:02   ` Ali Alnubani
2022-04-04  6:52 ` Ali Alnubani
2022-04-04  7:12   ` Christian Ehrhardt [this message]
2022-04-06  2:11 ` Pei Zhang
2022-04-06  6:45   ` Christian Ehrhardt

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=CAATJJ0L81h65JBFy51G0C948xpyqeAkrpoZG+dC1-xs6WHH4SQ@mail.gmail.com \
    --to=christian.ehrhardt@canonical.com \
    --cc=Abhishek.Marathe@microsoft.com \
    --cc=alialnu@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=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).