From: Thinh Tran <thinhtr@linux.ibm.com>
To: Thomas Monjalon <thomas@monjalon.net>, dpdk-dev <dev@dpdk.org>
Subject: Re: release candidate 24.03-rc4
Date: Wed, 27 Mar 2024 08:52:52 -0500 [thread overview]
Message-ID: <67ec1009-01d8-481b-92b3-59cbf0120df9@linux.ibm.com> (raw)
In-Reply-To: <24804928.kmuVQn2iE0@thomas>
IBM - Power Systems
DPDK v24.03-rc4-2-gded4d47651
* Build CI on Fedora 30,37,38,39,40 container images for ppc64le
* Basic PF on Mellanox: No issue found
* Performance: not tested.
* OS:- RHEL 9.3 kernel: 5.14.0-362.2.1.el9_3.ppc64le
with gcc version 11.4.1 20230605 (Red Hat 11.4.1-2)
- RHEL 9.2 kernel: 5.14.0-284.52.1.el9_2.ppc64le
with gcc version 11.3.1 20221121 (Red Hat 11.3.1-4) (GCC)
- SLES 15-SP5 ppc64le kernel: 5.14.21-150500.55.44-default
with gcc version 12.3.0 (SUSE Linux)
Systems tested:
- LPARs on IBM Power10 CHRP IBM,9105-22A
NICs:
- Mellanox Mellanox Technologies MT2894 Family [ConnectX-6 Lx]
- firmware version: 26.40.1000
- MLNX_OFED_LINUX-24.01-0.3.3.5
Regards,
Thinh Tran
On 3/24/2024 10:01 PM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v24.03-rc4
>
> There are 31 new patches in this snapshot.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_24_03.html
>
> As usual, you can report any issue 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.
>
> The final release should happen in a couple of days.
>
> Please think about sharing your roadmap now for DPDK 24.07.
>
> Thank you everyone
>
>
next prev parent reply other threads:[~2024-03-27 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 3:01 Thomas Monjalon
2024-03-27 13:52 ` Thinh Tran [this message]
2024-03-28 9:44 ` Xu, HailinX
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=67ec1009-01d8-481b-92b3-59cbf0120df9@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).