From: Riley Fletcher <rileyf@linux.ibm.com>
To: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org
Subject: Re: DPDK release candidate 26.03-rc3
Date: Tue, 31 Mar 2026 09:39:21 -0500 [thread overview]
Message-ID: <6ef072f2871cb5d99e38ae635318a4924f8bb9c5.camel@linux.ibm.com> (raw)
In-Reply-To: <4340093.KlZ2vcFHjT@thomas>
IBM - Power Systems Testing
DPDK v26.03-rc3
* Build CI on Fedora 40, 41, 42 and 43 container images for ppc64le
* Basic PF on Mellanox: No issues found
* Performance: TestPMD throughput single core tests
* OS:- RHEL 10.1 kernel: 6.12.0-124.39.1.el10_1.ppc64le
with gcc version 14.2.1 20250110 (Red Hat 14.2.1-7)
Systems tested:
- LPARs on IBM Power11 CHRP IBM, 9105-22A
NICs:
- Mellanox Technologies MT2910 Family [ConnectX-7 25 GbE 4-Port]
- Mellanox Technologies MT4129 Family [ConnectX-7 100 GbE 2-Port]
- Firmware Version: 28.47.1088
- OFED 26.01-1.0.0
Regards,
Riley Fletcher
On Thu, 2026-03-26 at 01:14 +0100, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v26.03-rc3
>
> There are 65 new patches in this snapshot.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_26_03.html
>
> Please test and report issues on https://bugs.dpdk.org
>
> You may share some release validation results
> by replying to this message at dev@dpdk.org
> and by adding tested hardware in the release notes.
>
> More tooling and documentation could be added before closing 26.03.
> The final release will happen in a few days, at the end of the month.
>
> Thank you everyone
>
prev parent reply other threads:[~2026-03-31 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4340093.KlZ2vcFHjT@thomas>
[not found] ` <MW4PR11MB5799CA8B1E076690F4BA4E109D56A@MW4PR11MB5799.namprd11.prod.outlook.com>
2026-03-31 9:50 ` DPDK release candidate 26.03-rc3 Xu, HailinX
2026-03-31 14:39 ` Riley Fletcher [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=6ef072f2871cb5d99e38ae635318a4924f8bb9c5.camel@linux.ibm.com \
--to=rileyf@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