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
Cc: dev@dpdk.org, Luca Boccassi <bluca@debian.org>,
	Raslan Darawsheh <rasland@nvidia.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: 24.11.2 patches review and test
Date: Fri, 11 Apr 2025 14:45:00 +0100	[thread overview]
Message-ID: <51cac182-1eca-4a78-80ac-ce686d88ea47@redhat.com> (raw)
In-Reply-To: <bcf9bb55-af24-4191-afb6-6ac01a2c89b3@nvidia.com>

On 10/04/2025 15:40, Ali Alnubani wrote:
> Hello,
> 

> We ran the following functional tests with Nvidia hardware on v24.11.2-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 22.04 / Driver: 
> MLNX_OFED_LINUX-24.10-2.1.8.0 / Firmware: 22.43.2566
> - NIC: ConnectX-7 / OS: Ubuntu 22.04 / Driver: 
> MLNX_OFED_LINUX-24.10-2.1.8.0 / Firmware: 28.43.2566
> - DPU: BlueField-2 / DOCA SW version: 2.10.0 / Firmware: 24.44.1036
> 
> Additionally, we ran build tests with multiple configurations on the 
> following OS/driver combinations (all passed):
> - Ubuntu 22.04 with MLNX_OFED_LINUX-24.10-2.1.8.0.
> - Ubuntu 24.04 with MLNX_OFED_LINUX-24.10-2.1.8.0.
> - Ubuntu 22.04 with rdma-core master (9e9a957).
> - Ubuntu 24.04 with rdma-core v50.0.
> - Fedora 41 with rdma-core v51.0.
> - Fedora 43 (Rawhide) with rdma-core v56.0.
> - OpenSUSE Leap 15.6 with rdma-core v49.1.
> - Windows Server 2022 with Clang 16.0.6.
> 
> We don't see new issues caused by the changes in this release.
> 
> Thanks,
> Ali
> 

Thanks Ali. I will add these to the release notes.

Kevin.


  reply	other threads:[~2025-04-11 13:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 10:14 Kevin Traynor
2025-04-01  8:05 ` Yanghang Liu
2025-04-11 13:43   ` Kevin Traynor
2025-04-10 14:40 ` Ali Alnubani
2025-04-11 13:45   ` Kevin Traynor [this message]
2025-04-11 13:50 ` 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=51cac182-1eca-4a78-80ac-ce686d88ea47@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=alialnu@nvidia.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --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).