From: Thinh Tran <thinhtr@linux.ibm.com>
To: Thomas Monjalon <thomas@monjalon.net>, dpdk-dev <dev@dpdk.org>
Subject: Re: release candidate 24.11-rc1
Date: Tue, 29 Oct 2024 14:31:58 -0500 [thread overview]
Message-ID: <6fb759e9-f65c-4f34-9cf7-0ecb42a0602d@linux.ibm.com> (raw)
In-Reply-To: <11832939.RiKt1P0BV1@thomas>
IBM - Power Systems
DPDK v24.11-rc1-6-g90cb8ff819
* Build CI on Fedora 38,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.40.1.el9_4.ppc64le
with gcc version 11.4.1 20231218 (Red Hat 11.4.1-3) (GCC)
SLES15 SP5 kernel: 5.14.21-150500.55.49-default
with gcc version 13.2.1 20230912 (SUSE Linux)
Systems tested:
- LPARs on IBM Power10 CHRP IBM,9105-22A
NICs:
- Mellanox Mellanox Technologies MT2894 Family [ConnectX-6 Lx]
- firmware version: 26.42.1000
- MLNX_OFED_LINUX-24.07-0.6.1.5
Thinh Tran
On 10/18/2024 4:47 PM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v24.11-rc1
>
> There are 630 new patches in this snapshot,
> including many API/ABI compatibility breakages.
> This release won't be ABI-compatible with previous ones.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_24_11.html
>
> Highlights of 24.11-rc1:
> - bit set and atomic bit manipulation
> - IPv6 address API
> - Ethernet link lanes
> - flow table index action
> - Cisco enic VF
> - Marvell CN20K
> - symmetric crypto SM4
> - asymmetric crypto EdDSA
> - event device pre-scheduling
> - event device independent enqueue
>
> Please test and report issues on bugs.dpdk.org.
>
> Few more new APIs may be added in -rc2.
> DPDK 24.11-rc2 is expected in more than two weeks (early November).
>
> Thank you everyone
>
>
prev parent reply other threads:[~2024-10-29 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 21:47 release candidate 24.11-rc1 Thomas Monjalon
2024-10-29 10:19 ` Xu, HailinX
2024-10-29 19:31 ` Thinh Tran [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=6fb759e9-f65c-4f34-9cf7-0ecb42a0602d@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.