From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Song, Keesang" <Keesang.Song@amd.com>,
David Marchand <david.marchand@redhat.com>
Subject: Re: release candidate 22.07-rc2
Date: Fri, 1 Jul 2022 15:27:02 +0100 [thread overview]
Message-ID: <71ee8210-64f9-b3b4-fdf6-5f7d4c9659d6@xilinx.com> (raw)
In-Reply-To: <4109670.NACDBdzCOe@thomas>
On 6/27/2022 3:15 AM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v22.07-rc2
>
> There are 317 new patches in this snapshot.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_22_07.html
>
> There were a lot of updates in drivers.
> The driver features should be frozen now.
>
> Please test and report issues on bugs.dpdk.org.
> Do not forget to review examples and documentation updates.
>
> DPDK 22.07-rc3 is expected in one week (targetting end of June).
>
> Thank you everyone
>
The testing with dpdk 22.07-rc2 from AMD looks good.
Following functional testing is done:
* Basic NIC IO forwarding (single/multiple queues/cores)
* Basic cryptodev
* AES-CBC128 SHA1-HMAC
* AES-CBC128 SHA2-256-HMAC
* AES-GCM-128
Systems tested:
- Platform: AMD EPYC 7713 64-Core Processor (2 Socket)
OS: Ubuntu 20.04.3 LTS
NICs:
- Mellanox MLX5 CX-6
Tuning guide: AMD Milan DPDK tuning guide (BIOS and Kernel)
(https://www.amd.com/system/files/documents/data-plane-development-kit-tuning-guide-amd-epyc7003-series-processors.pdf)
Thanks to the team that did the testing, I am just a messenger ;)
next prev parent reply other threads:[~2022-07-01 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 2:15 Thomas Monjalon
2022-06-30 8:31 ` Jiang, YuX
2022-07-04 9:58 ` Jiang, YuX
2022-07-01 14:27 ` Ferruh Yigit [this message]
2022-07-02 1:33 ` Thinh Tran
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=71ee8210-64f9-b3b4-fdf6-5f7d4c9659d6@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=Keesang.Song@amd.com \
--cc=david.marchand@redhat.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).