From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: Ali Alnubani <alialnu@nvidia.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>
Subject: Re: [dpdk-dev] 20.11.2 patches review and test
Date: Tue, 6 Jul 2021 02:37:32 +0000 [thread overview]
Message-ID: <DM4PR12MB5373D91482B4C9564AA98CD4A11B9@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <DM4PR12MB5167020B0F13154660AE7999DA009@DM4PR12MB5167.namprd12.prod.outlook.com>
> -----Original Message-----
> From: Ali Alnubani <alialnu@nvidia.com>
> Sent: Thursday, July 1, 2021 11:54 PM
> To: Xueming(Steven) Li <xuemingl@nvidia.com>; stable@dpdk.org
> Cc: dev@dpdk.org; Abhishek Marathe <Abhishek.Marathe@microsoft.com>; Akhil Goyal <akhil.goyal@nxp.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: RE: 20.11.2 patches review and test
>
> Hi,
>
> > -----Original Message-----
> > From: Xueming(Steven) Li <xuemingl@nvidia.com>
> > Sent: Sunday, June 27, 2021 2:28 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;
> > Xueming(Steven) Li <xuemingl@nvidia.com>
> > Subject: 20.11.2 patches review and test
> >
> > Hi all,
> >
> > Here is a list of patches targeted for stable release 20.11.2.
> >
> > The planned date for the final release is 6th July.
> >
> > 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.2-rc2
> >
> > These patches are located at branch 20.11 of dpdk-stable repo:
> > https://dpdk.org/browse/dpdk-stable/
> >
> > Thanks.
> >
> > Xueming Li <xuemingl@nvidia.com>
> >
>
> 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.3-1.0.0.1 / Firmware: 14.30.1004
> - NIC: ConnectX-5 / OS: Ubuntu 20.04 LTS / Driver: MLNX_OFED_LINUX-5.3-1.0.0.1 / Firmware: 16.30.1004
>
> Compilation tests with multiple configurations in the following OS/driver combinations are also passing:
> - Ubuntu 20.04.2 with MLNX_OFED_LINUX-5.3-1.0.0.1.
> - Ubuntu 20.04.2 with rdma-core master (a66e2a5).
> - 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 (a66e2a5) (i386).
> - Ubuntu 16.04.7 with rdma-core v22.7.
> - Fedora 34 with rdma-core v35.0.
> - Fedora 35 (Rawhide) with rdma-core v35.0 (only with gcc).
> - CentOS 7 7.9.2009 with rdma-core master (a66e2a5).
> - CentOS 7 7.9.2009 with MLNX_OFED_LINUX-5.3-1.0.0.1.
> - CentOS 8 8.3.2011 with rdma-core master (7f2d460).
> - OpenSUSE Leap 15.3 with rdma-core v31.0.
>
> Note that the clang build is failing in Fedora 35 due to the following issue:
> - https://bugs.dpdk.org/show_bug.cgi?id=745
>
> We don't see any other critical issues blocking this release.
>
> Thanks,
> Ali
Thank you very much!
next prev parent reply other threads:[~2021-07-06 2:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 23:28 Xueming Li
2021-06-30 10:33 ` Jiang, YuX
2021-07-06 2:37 ` Xueming(Steven) Li
2021-07-01 15:54 ` Ali Alnubani
2021-07-06 2:37 ` Xueming(Steven) Li [this message]
2021-07-06 3:26 ` [dpdk-dev] [dpdk-stable] " Kalesh Anakkur Purayil
2021-07-06 6:47 ` Xueming(Steven) Li
-- strict thread matches above, loose matches on Subject: below --
2021-06-26 23:08 [dpdk-dev] " Xueming Li
2021-06-26 15:41 Xueming(Steven) Li
2021-06-01 7:54 Xueming(Steven) Li
2021-06-08 8:52 ` Jiang, YuX
2021-06-08 10:28 ` Pei Zhang
2021-06-08 11:31 ` Kevin Traynor
2021-06-08 13:10 ` Xueming(Steven) Li
2021-06-14 12:39 ` Xueming(Steven) Li
2021-06-09 11:56 ` Xueming(Steven) Li
2021-06-10 8:53 ` Christian Ehrhardt
2021-06-14 12:35 ` Xueming(Steven) Li
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=DM4PR12MB5373D91482B4C9564AA98CD4A11B9@DM4PR12MB5373.namprd12.prod.outlook.com \
--to=xuemingl@nvidia.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=akhil.goyal@nxp.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=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).