From: Thinh Tran <thinhtr@linux.ibm.com>
To: Thomas Monjalon <thomas@monjalon.net>, dpdk-dev <dev@dpdk.org>
Subject: Re: release candidate 25.03-rc1
Date: Thu, 27 Feb 2025 15:20:02 -0600 [thread overview]
Message-ID: <c7be6e2f-f9f7-4513-99ff-b9a353cf7d28@linux.ibm.com> (raw)
In-Reply-To: <17054329.0ZKypZ73Fx@thomas>
IBM - Power Systems
DPDK v25.03-rc1
* Build CI on Fedora 38,39,40 and 41 container images for ppc64le
* Basic PF on Mellanox: No issue found
* Performance: not tested.
* OS: - RHEL 9.4 kernel: 5.14.0-427.40.1.el9_4.ppc64le
with gcc version 11.4.1 20231218 (Red Hat 11.4.1-3) (GCC)
- SLES15 SP5 kernel: 5.14.21-150500.55.49-default
with gcc version 13.2.1 20230912 (SUSE Linux)
- SLES 15-SP6 kernel: 6.4.0-150600.21-default
with gcc version 13.2.1 20240206 (SUSE Linux)
Systems tested:
- LPARs on IBM Power10 CHRP IBM,9105-22A
NICs:
- Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
- firmware version: 16.35.4030
- OFED-internal-25.01-0.6.0
Regards,
Thinh Tran
On 2/12/2025 10:49 AM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v25.03-rc1
>
> There are 478 new patches in this snapshot.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_25_03.html
>
> Highlights of 25.03-rc1:
> - Staged-Ordered ring (SORING)
> - mbuf raw bulk functions
> - some Intel drivers merged together
> - Yunsilicon xsc networking driver
> - ZTE Storage Data Accelerator (ZSDA) driver
> - Intel compiler icc support replaced by icx
> - more function annotations for analyzers
> - more MSVC compatibility
>
> Please test and report issues on bugs.dpdk.org.
>
> DPDK 25.03-rc2 is expected in more than two weeks (end of February).
>
> Thank you everyone
>
>
prev parent reply other threads:[~2025-02-27 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 16:49 release candidate 25.03-rc1 Thomas Monjalon
2025-02-27 3:03 ` Xu, HailinX
2025-02-27 21:20 ` 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=c7be6e2f-f9f7-4513-99ff-b9a353cf7d28@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.