DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thinh Tran <thinhtr@linux.ibm.com>
To: Thomas Monjalon <thomas@monjalon.net>, dpdk-dev <dev@dpdk.org>
Subject: Re: release candidate 25.07-rc1
Date: Fri, 20 Jun 2025 15:46:53 -0500	[thread overview]
Message-ID: <b437f3be-c2df-4f24-835b-5c5f28e44ad2@linux.ibm.com> (raw)
In-Reply-To: <5554581.qSoW2BAyJ8@thomas>

IBM - Power Systems Testing
DPDK v25.07-rc1-8-gdbeb8ae8d0


* Basic PF on Mellanox: No issue found
* Performance: not tested.
* OS:- RHEL 9.5  kernel: 5.14.0-503.11.1.el9_5.ppc64le
         with gcc version 11.5.0 20240719 (Red Hat 11.5.0-2)

Systems tested:
  - LPARs on IBM Power10 CHRP IBM,9105-22A
     NICs:
     -  Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
     - firmware version: 16.35.4030
     - OFED 25.04-0.6.1

Regards,
Thinh Tran


On 6/11/2025 8:56 PM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> 	https://git.dpdk.org/dpdk/tag/?id=v25.07-rc1
> 
> There are 542 new patches in this snapshot.
> 
> Release notes:
> 	https://doc.dpdk.org/guides/rel_notes/release_25_07.html
> 
> Highlights of 25.07-rc1:
> 	- Mucse RNP driver
> 	- ZTE Storage Data Accelerator (ZSDA) crypto driver
> 	- Performance Monitoring Unit (PMU) library
> 	- mempool optimization
> 	- zeroing of sensitive memory
> 	- RSS type for RoCE v2
> 	- graph feature arc and nodes for FIB
> 	- eventdev vector adapter
> 	- argparse enhanced
> 	- more libraries enabled with Windows MSVC
> 	- export symbols with macros instead of .map file
> 
> Please test and report issues on bugs.dpdk.org.
> 
> DPDK 25.07-rc2 is expected in two weeks.
> 
> Thank you everyone
> 
> 


      reply	other threads:[~2025-06-20 20:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12  1:56 Thomas Monjalon
2025-06-20 20:46 ` Thinh Tran [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=b437f3be-c2df-4f24-835b-5c5f28e44ad2@linux.ibm.com \
    --to=thinhtr@linux.ibm.com \
    --cc=dev@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).