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>
Subject: Re: 21.11.4 patches review and test
Date: Wed, 19 Apr 2023 15:21:39 +0100 [thread overview]
Message-ID: <a62570e9-47bf-4906-5c82-f8755de3351f@redhat.com> (raw)
In-Reply-To: <DM4PR12MB5167AC728322A4C8EB9543D6DA629@DM4PR12MB5167.namprd12.prod.outlook.com>
On 19/04/2023 14:24, Ali Alnubani wrote:
>> -----Original Message-----
>> From: Kevin Traynor <ktraynor@redhat.com>
>> Sent: Thursday, April 6, 2023 2:38 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.4 patches review and test
>>
>> Hi all,
>>
>> Here is a list of patches targeted for stable release 21.11.4.
>>
>> The planned date for the final release is 25th April.
>>
>> 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.4-rc1
>>
>> These patches are located at branch 21.11 of dpdk-stable repo:
>> https://dpdk.org/browse/dpdk-stable/
>>
>> Thanks.
>>
>> Kevin
>>
>> ---
>
> We ran the following functional tests with Nvidia hardware on 21.11.4-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.
> - 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-6 Dx / OS: Ubuntu 20.04 / Driver: MLNX_OFED_LINUX-5.9-0.5.6.0 / Firmware: 22.36.1010
> - NIC: ConnectX-7 / OS: Ubuntu 20.04 / Driver: MLNX_OFED_LINUX-5.9-0.5.6.0 / Firmware: 22.36.1010
> - DPU: BlueField-2 / DOCA SW version: 1.5.1 / Firmware: 24.35.2000
>
> Additionally, we ran compilation tests with multiple configurations in the following OS/driver combinations:
> - Ubuntu 20.04.5 with MLNX_OFED_LINUX-5.9-0.5.6.0.
> - Ubuntu 20.04.5 with rdma-core master (f0a079f).
> - 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 (f0a079f) (i386).
> - Fedora 37 with rdma-core v41.0.
> - Fedora 39 (Rawhide) with rdma-core v44.0.
> - CentOS 7 7.9.2009 with rdma-core master (f0a079f).
> - CentOS 7 7.9.2009 with MLNX_OFED_LINUX-5.9-0.5.6.0.
> - CentOS 8 8.4.2105 with rdma-core master (f0a079f).
> - 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.
>
Great, thanks for testing and reporting Ali.
Kevin.
> Please note that not all the functional tests mentioned above fall under "Basic functionality with testpmd" like reported in the release notes for previous releases:
> https://git.dpdk.org/dpdk-stable/commit/?h=v21.11.3&id=31608e4db56893c896375288671b5ee38723a211
> Some of them test other applications.
>
> Thanks,
> Ali
prev parent reply other threads:[~2023-04-19 14:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 11:37 Kevin Traynor
2023-04-13 6:12 ` Xu, HailinX
2023-04-19 11:00 ` YangHang Liu
2023-04-19 14:21 ` Kevin Traynor
2023-04-20 2:40 ` Xu, HailinX
2023-04-20 10:32 ` Kevin Traynor
2023-05-02 9:35 ` Kevin Traynor
2023-05-04 2:13 ` Xu, HailinX
2023-05-04 10:10 ` Kevin Traynor
2023-05-05 1:42 ` Xu, HailinX
2023-05-08 15:23 ` Kevin Traynor
2023-05-11 7:33 ` Jiang, YuX
2023-05-16 8:41 ` Kevin Traynor
2023-04-19 13:24 ` Ali Alnubani
2023-04-19 14:21 ` Kevin Traynor [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=a62570e9-47bf-4906-5c82-f8755de3351f@redhat.com \
--to=ktraynor@redhat.com \
--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).