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>, Luca Boccassi <bluca@debian.org>,
Raslan Darawsheh <rasland@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Maayan Kashani <mkashani@nvidia.com>
Subject: Re: 21.11.7 patches review and test
Date: Mon, 29 Apr 2024 14:55:27 +0100 [thread overview]
Message-ID: <4eb898e6-7e49-45bf-bdf4-8ec84402207c@redhat.com> (raw)
In-Reply-To: <DM4PR12MB5167E978BD5A6EAB24399855DA1B2@DM4PR12MB5167.namprd12.prod.outlook.com>
On 29/04/2024 12:21, Ali Alnubani wrote:
>> -----Original Message-----
>> From: Kevin Traynor <ktraynor@redhat.com>
>> Sent: Thursday, April 18, 2024 3:34 PM
>> To: stable@dpdk.org
>> Cc: dev@dpdk.org; Abhishek Marathe <Abhishek.Marathe@microsoft.com>;
>> Ali Alnubani <alialnu@nvidia.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>; Raslan
>> Darawsheh <rasland@nvidia.com>; NBU-Contact-Thomas Monjalon
>> (EXTERNAL) <thomas@monjalon.net>; yanghliu@redhat.com
>> Subject: 21.11.7 patches review and test
>>
>> Hi all,
>>
>> Here is a list of patches targeted for stable release 21.11.7.
>>
>> The planned date for the final release is 30th 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.7-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.7-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 (https://doc.dpdk.org/guides/nics/mlx5.html#supported-hardware-offloads)
> - 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.
> - Buffer Split tests.
> - Tx scheduling tests.
>
> Functional tests ran on:
> - NIC: ConnectX-6 Dx / OS: Ubuntu 20.04 / Driver: MLNX_OFED_LINUX-24.01-0.3.3.1 / Firmware: 22.40.1000
> - NIC: ConnectX-7 / OS: Ubuntu 20.04 / Driver: MLNX_OFED_LINUX-24.01-0.3.3.1 / Firmware: 28.40.1000
> - DPU: BlueField-2 / DOCA SW version: 2.6.0 / Firmware: 24.40.1000
>
> Additionally, we ran build tests with multiple configurations on the following OS/driver combinations (all passed):
> - Debian 12 with MLNX_OFED_LINUX-24.01-0.3.3.1.
> - Ubuntu 20.04.6 with MLNX_OFED_LINUX-24.01-0.3.3.1.
> - Ubuntu 20.04.6 with rdma-core master (3be5661).
> - Ubuntu 20.04.6 with rdma-core v28.0.
> - Fedora 38 with rdma-core v44.0.
> - Fedora 40 (Rawhide) with rdma-core v48.0.
> - OpenSUSE Leap 15.5 with rdma-core v42.0.
> - Windows Server 2019 with Clang 16.0.6.
>
> We don't see new issues caused by the changes in this release.
>
Thanks for testing Ali. I will add into the release notes.
Kevin.
> Thanks,
> Ali
prev parent reply other threads:[~2024-04-29 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 12:34 Kevin Traynor
2024-04-22 8:38 ` YangHang Liu
2024-04-26 9:08 ` Kevin Traynor
2024-04-26 9:04 ` Xu, HailinX
2024-04-26 9:07 ` Kevin Traynor
2024-04-29 11:21 ` Ali Alnubani
2024-04-29 13:55 ` 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=4eb898e6-7e49-45bf-bdf4-8ec84402207c@redhat.com \
--to=ktraynor@redhat.com \
--cc=alialnu@nvidia.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=mkashani@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).