DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@nvidia.com>
To: "Xueming(Steven) Li" <xuemingl@nvidia.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Cc: "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>,
	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>,
	Yanghang Liu <yanghliu@redhat.com>,
	"yuan.peng@intel.com" <yuan.peng@intel.com>,
	"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>
Subject: RE: 20.11.6 patches review and test
Date: Tue, 23 Aug 2022 14:54:51 +0000	[thread overview]
Message-ID: <DM4PR12MB5167D9B2A56A060EF3776C51DA709@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220815091655.1202165-1-xuemingl@nvidia.com>

> -----Original Message-----
> From: Xueming(Steven) Li <xuemingl@nvidia.com>
> Sent: Monday, August 15, 2022 12:17 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>; 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>; Yanghang
> Liu <yanghliu@redhat.com>; yuan.peng@intel.com;
> zhaoyan.chen@intel.com
> Subject: 20.11.6 patches review and test
> 
> Hi all,
> 
> Here is a list of patches targeted for stable release 20.11.6.
> 
> The planned date for the final release is August 29th.
> 
> 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.6-rc1
> 
> These patches are located at branch 20.11 of dpdk-stable repo:
>     https://dpdk.org/browse/dpdk-stable/
> 
> Thanks.
> 
> Xueming Li <xuemingl@nvidia.com>
> 
> ---

Hello,

We ran the following functional tests with Nvidia hardware on 20.11.6-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
  - 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
  - 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
  - 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.7-1.0.2.0 / Firmware: 14.32.1010
- NIC: ConnectX-5 / OS: Ubuntu 20.04 LTS / Driver: MLNX_OFED_LINUX-5.7-1.0.2.0 / Firmware: 16.34.1002
- NIC: ConnectX-6 Dx / OS: Ubuntu 20.04 LTS / Driver: MLNX_OFED_LINUX-5.7-1.0.2.0 / Firmware: 22.34.1002
- DPU: BlueField-2 / DOCA SW version: 1.4.0

Additionally, we ran compilation tests with multiple configurations in the following OS/driver combinations:
- Ubuntu 20.04.4 with MLNX_OFED_LINUX-5.7-1.0.2.0.
- Ubuntu 20.04.4 with rdma-core master (23a0021).
- 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 (23a0021) (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 (with clang only).
- CentOS 7 7.9.2009 with rdma-core master (23a0021).
- CentOS 7 7.9.2009 with MLNX_OFED_LINUX-5.7-1.0.2.0.
- CentOS 8 8.4.2105 with rdma-core master (23a0021).
- OpenSUSE Leap 15.4 with rdma-core v38.1.
- Windows Server 2019 with Clang 11.0.0.

We don't see new issues caused by the changes in this release.

Thanks,
Ali

  parent reply	other threads:[~2022-08-23 14:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15  9:16 Xueming Li
2022-08-17  3:22 ` Jiang, YuX
2022-08-17  6:09   ` Xueming(Steven) Li
2022-08-23  9:38     ` Jiang, YuX
2022-08-23 11:51       ` Xueming(Steven) Li
2022-08-25  2:45         ` Jiang, YuX
2022-08-25  5:44           ` Xueming(Steven) Li
2022-08-23 14:54 ` Ali Alnubani [this message]
2022-08-25  5:45   ` Xueming(Steven) Li
2022-08-24 14:44 ` YangHang Liu
2022-08-25  5:45   ` Xueming(Steven) Li
2022-08-29 13:02 ` Stokes, Ian
2022-08-29 13:04   ` 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=DM4PR12MB5167D9B2A56A060EF3776C51DA709@DM4PR12MB5167.namprd12.prod.outlook.com \
    --to=alialnu@nvidia.com \
    --cc=Abhishek.Marathe@microsoft.com \
    --cc=benjamin.walker@intel.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.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=xuemingl@nvidia.com \
    --cc=yanghliu@redhat.com \
    --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).