From: Luca Boccassi <bluca@debian.org>
To: Ali Alnubani <alialnu@nvidia.com>, "stable@dpdk.org" <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] 20.11.3 patches review and test
Date: Thu, 19 Aug 2021 15:31:56 +0100 [thread overview]
Message-ID: <c9a5b8948c295f7cd9ebf170ef647459d17d600c.camel@debian.org> (raw)
In-Reply-To: <DM4PR12MB5167348CDDDE7C83DD1D6F85DAC09@DM4PR12MB5167.namprd12.prod.outlook.com>
On Thu, 2021-08-19 at 12:10 +0000, Ali Alnubani wrote:
> Hi,
>
> > -----Original Message-----
> > From: luca.boccassi@gmail.com <luca.boccassi@gmail.com>
> > Sent: Monday, August 9, 2021 11:44 AM
> > 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: 20.11.3 patches review and test
> >
> > Hi all,
> >
> > Here is a list of patches targeted for stable release 20.11.3.
> >
> > The planned date for the final release is August 23rd.
> >
> > 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=v20.11.3-rc1
> >
> > These patches are located at branch 20.11 of dpdk-stable repo:
> > https://dpdk.org/browse/dpdk-stable/
> >
> > Thanks.
> >
> > Luca Boccassi
> >
> > ---
>
> 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
> - gre
> - gre_key
> gtp
> - icmp
> - icmp6
> - ipv4
> - ipv6
> - ipv6_ext
> - ipv6_frag_ext
> - meta
> - mpls
> - nvgre
> - tcp
> - udp
> - vlan
> - vxlan
> - vxlan-gpe
> Actions:
> - age (shared and non-shared)
> - count
> - dec_tcp_ack
> - dec_tcp_seq
> - dec_ttl
> - drop
> - flag
> - inc_tcp_ack
> - inc_tcp_seq
> - jump
> - mark
> - meter
> - of_pop_vlan
> - of_push_vlan
> - of_set_vlan_pcp
> - of_set_vlan_vid
> - queue
> - raw_decap
> - raw_encap
> - rss (shared and non-shared)
> - set_ipv4_dscp
> - set_ipv4_dst
> - set_ipv4_src
> - set_ipv6_dscp
> - set_ipv6_dst
> - set_ipv6_src
> - set_mac_dst
> - set_mac_src
> - set_meta
> - set_tag
> - set_tp_dst
> - set_tp_src
> - set_ttl
> - vxlan_decap
> - vxlan_encap
>
> - 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.
> - Hardware LRO tests.
>
> Functional tests ran on:
> - NIC: ConnectX-4 Lx / OS: Ubuntu 20.04 LTS / Driver: MLNX_OFED_LINUX-5.4-1.0.3.0 / Firmware: 14.31.1014
> - NIC: ConnectX-4 Lx / OS: Ubuntu 20.04 LTS / kernel: 5.14.0-rc6 / Driver: rdma-core v36.0 / Firmware: 14.31.1014
> - NIC: ConnectX-5 / OS: Ubuntu 20.04 LTS / Driver: MLNX_OFED_LINUX-5.4-1.0.3.0 / Firmware: 16.31.1014
> - NIC: ConnectX-5 / OS: Ubuntu 20.04 LTS / kernel: 5.14.0-rc6 / Driver: v36.0 / Firmware: 16.31.1014
>
> Compilation tests with multiple configurations in the following OS/driver combinations are also passing:
> - Ubuntu 20.04.2 with MLNX_OFED_LINUX-5.4-1.0.3.0.
> - Ubuntu 20.04.2 with rdma-core master (64d1ae5).
> - 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 (5b0f5b2) (i386).
> - Ubuntu 16.04.7 with rdma-core v22.7.
> - Fedora 34 with rdma-core v36.0.
> - Fedora 36 (Rawhide) with rdma-core v36.0 (only with gcc).
> - CentOS 7 7.9.2009 with rdma-core master (64d1ae5).
> - CentOS 7 7.9.2009 with MLNX_OFED_LINUX-5.4-1.0.3.0.
> - CentOS 8 8.3.2011 with rdma-core master (64d1ae5).
> - OpenSUSE Leap 15.3 with rdma-core v31.0.
>
> We don't see any critical issues blocking this release.
>
> Regards,
> Ali
Thank you!
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2021-08-19 14:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 8:43 luca.boccassi
2021-08-13 11:42 ` Jiang, YuX
2021-08-13 13:31 ` Luca Boccassi
2021-08-13 14:25 ` David Hunt
2021-08-23 15:30 ` Luca Boccassi
2021-08-26 10:09 ` Christian Ehrhardt
2021-08-26 12:20 ` Luca Boccassi
2021-08-19 12:10 ` Ali Alnubani
2021-08-19 14:31 ` Luca Boccassi [this message]
2021-08-23 2:37 ` Pei Zhang
2021-08-23 10:08 ` Luca Boccassi
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=c9a5b8948c295f7cd9ebf170ef647459d17d600c.camel@debian.org \
--to=bluca@debian.org \
--cc=alialnu@nvidia.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).