From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev <dev@dpdk.org>
Subject: Re: release candidate 24.03-rc1
Date: Wed, 20 Mar 2024 11:47:17 +0000 [thread overview]
Message-ID: <5babb52e-67ee-43a9-b439-5498cfa24d75@amd.com> (raw)
In-Reply-To: <9238933.CDJkKcVGEf@thomas>
On 2/22/2024 7: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
>
>
AMD v24.03-rc1 test report (on behalf of the test team).
Summary:
Build + limited unit test coverage, no defect or regression found.
Systems tested:
- AMD EPYC Milan: AMD EPYC 7543 32-Core Processor
- BIOS 7.00.30.00
- AMD EPYC Siena: AMD EPYC 8534 64-Core Processor
- BIOS 7.00.00.00
- Ubuntu 22.04.4 LTS (Linux Kernel Version: 5.15.0-100-generic)
- Compiler version GCC 12.3 & 13.2
Configuration:
- NPS=2, SMT=enabled, Turbo Boost=enabled
Test cases:
* Build tests on above platforms
* Various crypto algorithms micro benchmarks (unit tests)
* Various core libraries micro benchmarks (unit tests)
* efd, fib6, ring, graph
prev parent reply other threads:[~2024-03-20 11:47 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
2024-03-20 11:47 ` Ferruh Yigit [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=5babb52e-67ee-43a9-b439-5498cfa24d75@amd.com \
--to=ferruh.yigit@amd.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).