From: Thinh Tran <thinhtr@linux.ibm.com>
To: David Marchand <david.marchand@redhat.com>, dpdk-dev <dev@dpdk.org>
Subject: Re: release candidate 24.07-rc2
Date: Wed, 17 Jul 2024 17:31:59 -0500 [thread overview]
Message-ID: <2d35aa45-47b9-4cc7-8b7f-2c3a1272a50c@linux.ibm.com> (raw)
In-Reply-To: <CAJFAV8yPESOEVHydQWUnhcY+dYQN8y2V5sPwdLE6WGQVJKjytw@mail.gmail.com>
IBM - Power Systems Testing
DPDK 24.07-rc2
* Build CI on Fedora 30,37,39,40 container images for ppc64le
* Basic PF on Mellanox: No issue found
* Performance: not tested.
* OS:- RHEL 9.4 kernel: 5.14.0-427.13.1.el9_4.ppc64le
with gcc version 11.4.1 20231218 (Red Hat 11.4.1-3)
- 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.41.1000
- MLNX_OFED_LINUX-24.04-0.6.6.5
Regards,
Thinh
On 7/12/2024 1:25 PM, David Marchand wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v24.07-rc2
>
> There are 461 new patches in this snapshot.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_24_07.html
>
> Highlights of 24.07-rc2:
> - SVE support in the hash library
> - FEC support in net/i40e and net/ice
> - log cleanups in drivers
> - various driver fixes and updates
>
> Please test and report issues on bugs.dpdk.org.
>
> DPDK 24.07-rc3 is expected in approximately one week.
>
> Thank you everyone
>
next prev parent reply other threads:[~2024-07-17 22:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 18:25 David Marchand
2024-07-17 22:31 ` Thinh Tran [this message]
2024-07-23 2:14 ` 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=2d35aa45-47b9-4cc7-8b7f-2c3a1272a50c@linux.ibm.com \
--to=thinhtr@linux.ibm.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
/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).