DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: Ali Alnubani <alialnu@nvidia.com>, "stable@dpdk.org" <stable@dpdk.org>
Cc: "ian.stokes@intel.com" <ian.stokes@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"ktraynor@redhat.com" <ktraynor@redhat.com>,
	"Abhishek.Marathe@microsoft.com" <Abhishek.Marathe@microsoft.com>,
	"drc@linux.vnet.ibm.com" <drc@linux.vnet.ibm.com>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
	"yuan.peng@intel.com" <yuan.peng@intel.com>,
	"jerinj@marvell.com" <jerinj@marvell.com>,
	"benjamin.walker@intel.com" <benjamin.walker@intel.com>,
	"bluca@debian.org" <bluca@debian.org>,
	Raslan Darawsheh <rasland@nvidia.com>,
	"john.mcnamara@intel.com" <john.mcnamara@intel.com>,
	"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>,
	"hariprasad.govindharajan@intel.com"
	<hariprasad.govindharajan@intel.com>,
	"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
	"pezhang@redhat.com" <pezhang@redhat.com>,
	"juhlee@microsoft.com" <juhlee@microsoft.com>,
	"qian.q.xu@intel.com" <qian.q.xu@intel.com>
Subject: Re: 20.11.4 patches review and test
Date: Thu, 23 Dec 2021 15:08:07 +0000	[thread overview]
Message-ID: <8e343ce951507c8ff57dd178c5c0ae7a3841a432.camel@nvidia.com> (raw)
In-Reply-To: <DM4PR12MB5167B511FC7AB3E8BB5DE230DA7E9@DM4PR12MB5167.namprd12.prod.outlook.com>

Hi Ali,

Thanks very much for your support!

On Thu, 2021-12-23 at 14:52 +0000, Ali Alnubani wrote:
> Hi,
> 
> > -----Original Message-----
> > From: Xueming(Steven) Li <xuemingl@nvidia.com>
> > Sent: Monday, December 6, 2021 6:15 PM
> > To: stable@dpdk.org
> > Cc: Xueming(Steven) Li <xuemingl@nvidia.com>; 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: 20.11.4 patches review and test
> > 
> > Hi all,
> > 
> > Here is a list of patches targeted for stable release 20.11.4.
> > 
> > The planned date for the final release is 31th December.
> > 
> > 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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdpdk.org%2Fbrowse%2Fdpdk-stable%2Ftag%2F%3Fid%3Dv20.11.4-rc1&amp;data=04%7C01%7Cxuemingl%40nvidia.com%7C4df7aa57e1ed4e9e263308d9c623e4d0%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637758679724411133%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=jX1ppD4x%2FH3x%2FWZLI6bMP7LiUZxKPZCmks6AH7wm88c%3D&amp;reserved=0
> > 
> > These patches are located at branch 20.11 of dpdk-stable repo:
> >     https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdpdk.org%2Fbrowse%2Fdpdk-stable%2F&amp;data=04%7C01%7Cxuemingl%40nvidia.com%7C4df7aa57e1ed4e9e263308d9c623e4d0%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C637758679724411133%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=59XOMTcOVxkUmeWeg0SM8GHgGapaOLdm2oONMq7fvqQ%3D&amp;reserved=0
> > 
> > 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
>   - geneve
>   - gre
>   - gre_key
>   - gtp
>   - icmp
>   - icmp6
>   - ipv4
>   - ipv6
>   - ipv6_frag_ext
>   - mark
>   - meta
>   - mpls
>   - nvgre
>   - tag
>   - 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
>   - 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.5-1.0.3.2 / Firmware: 14.32.1010
> - NIC: ConnectX-4 Lx / OS: Ubuntu 20.04 LTS / Kernel: 5.16.0-rc5 / Driver: rdma-core v38.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.16.0-rc5 / Driver: v38.0 / Firmware: 16.32.1010
> - NIC: ConnectX-6 Dx / OS: Ubuntu 20.04 LTS / Driver: MLNX_OFED_LINUX-5.5-1.0.3.2 / Firmware: 22.32.1010
> 
> Compilation tests with multiple configurations in the following OS/driver combinations are also passing:
> - Ubuntu 20.04.3 with MLNX_OFED_LINUX-5.5-1.0.3.2.
> - Ubuntu 20.04.3 with rdma-core master (c52b43e).
> - Ubuntu 20.04.3 with rdma-core v28.0.
> - Ubuntu 18.04.6 with rdma-core v17.1.
> - Ubuntu 18.04.6 with rdma-core master (c52b43e) (i386).
> - Ubuntu 16.04.7 with rdma-core v22.7.
> - Fedora 35 with rdma-core v38.0.
> - Fedora 36 (Rawhide) with rdma-core v38.0
> - CentOS 7 7.9.2009 with rdma-core master (940f53f).
> - CentOS 7 7.9.2009 with MLNX_OFED_LINUX-5.5-1.0.3.2.
> - CentOS 8 8.4.2105 with rdma-core master (940f53f).
> - OpenSUSE Leap 15.3 with rdma-core v31.0.
> - Windows Server 2019 with Clang 11.0.0.
> 
> The only issue we found that was introduced by 20.11.4-rc1 is the following:
> - Bug 916 - [20.11.4-rc1][mlx5] 2% single core packet forwarding performance degradation (https://bugs.dpdk.org/show_bug.cgi?id=916)
> We are still discussing whether we want to backport a fix to this release or not.
> 
> Thanks,
> Ali


      reply	other threads:[~2021-12-23 15:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06 16:15 Xueming Li
2021-12-09 10:01 ` Jiang, YuX
2021-12-10 11:35   ` Jiang, YuX
2021-12-15 14:44     ` Xueming(Steven) Li
2021-12-16  6:40       ` Jiang, YuX
2021-12-23 15:07         ` Xueming(Steven) Li
2022-01-12  9:53           ` Zhang, Roy Fan
2022-01-12 11:01             ` Xueming(Steven) Li
2022-01-12 11:29               ` Jiang, YuX
2022-01-12 12:53                 ` Xueming(Steven) Li
2021-12-13 14:27 ` Pei Zhang
2021-12-15 14:46   ` Xueming(Steven) Li
2021-12-23 14:52 ` Ali Alnubani
2021-12-23 15:08   ` Xueming(Steven) Li [this message]

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=8e343ce951507c8ff57dd178c5c0ae7a3841a432.camel@nvidia.com \
    --to=xuemingl@nvidia.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).