patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.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>,
	"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>,
	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>,
	"yanghliu@redhat.com" <yanghliu@redhat.com>,
	"yuan.peng@intel.com" <yuan.peng@intel.com>,
	"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>
Subject: Re: 21.11.3 patches review and test
Date: Mon, 19 Dec 2022 10:40:48 +0000	[thread overview]
Message-ID: <4b918f79-8f8b-3380-2aa5-79e69eb63c67@redhat.com> (raw)
In-Reply-To: <DM4PR12MB5167A3234974A391E216255FDAE19@DM4PR12MB5167.namprd12.prod.outlook.com>

On 15/12/2022 17:51, Ali Alnubani wrote:
>> -----Original Message-----
>> From: Kevin Traynor <ktraynor@redhat.com>
>> Sent: Tuesday, December 6, 2022 1:30 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>; 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>; yanghliu@redhat.com; yuan.peng@intel.com;
>> zhaoyan.chen@intel.com
>> Subject: 21.11.3 patches review and test
>>
>> Hi all,
>>
>> Here is a list of patches targeted for stable release 21.11.3.
>>
>> The planned date for the final release is 19th 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://dpdk.org/browse/dpdk-stable/tag/?id=v21.11.3-rc1
>>
>> These patches are located at branch 21.11 of dpdk-stable repo:
>>      https://dpdk.org/browse/dpdk-stable/
>>
>> Thanks.
>>
>> Kevin
>>
>> ---
> 
> Hello,
> 
> We ran the following functional tests with Nvidia hardware on 21.11.3-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:
>    - ecpri
>    - eth
>    - flex
>    - geneve
>    - geneve_opt
>    - gre
>    - gre_key
>    - gre_option
>    - gtp
>    - gtp_psc
>    - icmp
>    - icmp6
>    - integrity
>    - 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
>    - meter
>    - modify_field
>    - nvgre_decap
>    - nvgre_encap
>    - of_pop_vlan
>    - of_push_vlan
>    - of_set_vlan_pcp
>    - of_set_vlan_vid
>    - queue
>    - raw_decap
>    - raw_encap
>    - rss
>    - sample
>    - 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.
> - Regex application tests.
> - Buffer Split tests.
> - Tx scheduling tests.
> 
> Functional tests ran on:
> - NIC: ConnectX-4 Lx / OS: Ubuntu 20.04 LTS / Driver: MLNX_OFED_LINUX-5.8-1.0.1.1 / Firmware: 14.32.1010
> - NIC: ConnectX-5 / OS: Ubuntu 20.04 LTS / Driver: MLNX_OFED_LINUX-5.8-1.0.1.1 / Firmware: 16.35.1012
> - NIC: ConnectX-6 Dx / OS: Ubuntu 20.04 LTS / Driver: MLNX_OFED_LINUX-5.7-1.0.2.0 / Firmware: 22.35.1012
> - DPU: BlueField-2 / DOCA SW version: 1.5.0 / Firmware: 24.35.1012
> 
> We don't see any new issues in functional testing caused by changes in this release.
> 
> Additionally, we ran compilation tests with multiple configurations on the following OS/driver combinations:
> - Ubuntu 22.04.1 with MLNX_OFED_LINUX-5.8-1.1.2.1.
> - Ubuntu 20.04.5 with MLNX_OFED_LINUX-5.8-1.1.2.1.
> - Ubuntu 20.04.5 with rdma-core master (76cfaa1).
> - Ubuntu 20.04.5 with rdma-core v28.0.
> - Ubuntu 18.04.6 with rdma-core v17.1.
> - Ubuntu 18.04.6 with rdma-core master (76cfaa1) (i386).
> - Ubuntu 16.04.7 with rdma-core v22.7.
> - Fedora 37 with rdma-core v41.0.
> - Fedora 38 (Rawhide) with rdma-core v41.0.
> - CentOS 7 7.9.2009 with rdma-core master (76cfaa1).
> - CentOS 7 7.9.2009 with MLNX_OFED_LINUX-5.8-1.0.1.1.
> - CentOS 8 8.4.2105 with rdma-core master (76cfaa1).
> - OpenSUSE Leap 15.4 with rdma-core v38.1.
> - Windows Server 2019 with Clang 11.0.0.
> 
> The builds are passing on most OS except for Fedora 37 and 38, where I have the following issues:
> - Bug 1149 - [21.11] lib/ring build failure with gcc 12 and debug enabled (https://bugs.dpdk.org/show_bug.cgi?id=1149)
> - Bug 1150 - [21.11] failure to build API's html docs on Fedora 37 (https://bugs.dpdk.org/show_bug.cgi?id=1150)
> 

Thanks for testing Ali. I will take a look at these.
Kevin.

> Thanks,
> Ali


  reply	other threads:[~2022-12-19 10:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 11:29 Kevin Traynor
2022-12-13 11:48 ` Christian Ehrhardt
2022-12-15 10:19   ` Kevin Traynor
2022-12-15  3:44 ` Jiang, YuX
2022-12-15 10:35   ` Kevin Traynor
2022-12-15 17:51 ` Ali Alnubani
2022-12-19 10:40   ` Kevin Traynor [this message]
2022-12-16  7:55 ` YangHang Liu
2022-12-19 10:39   ` Kevin Traynor

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=4b918f79-8f8b-3380-2aa5-79e69eb63c67@redhat.com \
    --to=ktraynor@redhat.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=hemant.agrawal@nxp.com \
    --cc=ian.stokes@intel.com \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=juhlee@microsoft.com \
    --cc=pezhang@redhat.com \
    --cc=qian.q.xu@intel.com \
    --cc=rasland@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --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).