From: Thinh Tran <thinhtr@linux.ibm.com>
To: Thomas Monjalon <thomas@monjalon.net>, dpdk-dev <dev@dpdk.org>
Subject: Re: release candidate 24.03-rc1
Date: Tue, 5 Mar 2024 15:46:08 -0600 [thread overview]
Message-ID: <31d33bd5-42b2-403e-b7c9-c9fcfeeab396@linux.ibm.com> (raw)
In-Reply-To: <9238933.CDJkKcVGEf@thomas>
IBM - Power Systems
DPDK v24.03-rc1-106-g2a0244d611
* Build CI on Fedora 30,37,38,39 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.0 kernel: 4.18.0-348.el8.ppc64le
with gcc version 11.2.1 20230214 (Red Hat 11.2.1-9) (GCC)
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 2/22/2024 1:35 AM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v24.03-rc1
>
> There are 521 new patches in this snapshot.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_24_03.html
>
> Highlights of 24.03-rc1:
> - argument parsing library
> - dynamic logging standardized
> - HiSilicon UACCE bus
> - Tx queue query
> - flow matching with random and field comparison
> - flow action NAT64
> - more cleanups to prepare MSVC build
>
> Please test and report issues on bugs.dpdk.org.
>
> DPDK 24.03-rc2 will be out as soon as possible.
> Priority is on features announced in the roadmap:
> https://core.dpdk.org/roadmap/
>
> Thank you everyone
>
>
next prev parent reply other threads:[~2024-03-06 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 7:35 Thomas Monjalon
2024-02-29 9:18 ` Xu, HailinX
2024-03-05 21:46 ` Thinh Tran [this message]
2024-03-20 11:47 ` Ferruh Yigit
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=31d33bd5-42b2-403e-b7c9-c9fcfeeab396@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).