From: Riley Fletcher <rileyf@linux.ibm.com>
To: Thomas Monjalon <thomas@monjalon.net>, dev@dpdk.org
Subject: Re: DPDK release candidate 26.07-rc4
Date: Tue, 21 Jul 2026 00:01:23 -0500 [thread overview]
Message-ID: <057d70e5fafe99c9e8b70f6aa55f088a14b2eb25.camel@linux.ibm.com> (raw)
In-Reply-To: <kvNGsDZ2SLOK2WFaq05qOA@monjalon.net>
IBM - Power Systems Testing
DPDK v26.07-rc4
* 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.2 kernel: 6.12.0-211.7.3.el10_2.ppc64le
with gcc version 14.3.1 20251022 (Red Hat 14.3.1-4)
Systems tested:
- LPARs on IBM Power11 CHRP IBM, 9105-22A
NICs:
- Mellanox Technologies MT4129 Family [ConnectX-7 100 GbE 2-Port]
- Firmware Version: 28.48.1000 (MT_0000000834)
- OFED 26.04-0.8.6
Regards,
Riley Fletcher
On Sun, 2026-07-19 at 11:53 +0200, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v26.07-rc4
>
> There are 48 new patches in this snapshot.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_26_07.html
>
> Please test and report issues on 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.
>
> Only release notes changes are expected at this stage.
> There are some deprecation notices pending for review.
>
> This release cycle should be closed in few days.
>
> Thank you everyone
>
next parent reply other threads:[~2026-07-21 5:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <kvNGsDZ2SLOK2WFaq05qOA@monjalon.net>
2026-07-21 5:01 ` Riley Fletcher [this message]
2026-07-23 8:13 ` DPDK release candidate 26.07-rc4 testing report Wael Abualrub
2026-07-23 17:51 ` DPDK release candidate 26.07-rc4 Kishore Padmanabha
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=057d70e5fafe99c9e8b70f6aa55f088a14b2eb25.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