From: Thinh Tran <thinhtr@linux.vnet.ibm.com>
To: Thomas Monjalon <thomas@monjalon.net>, dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 21.08-rc2
Date: Fri, 30 Jul 2021 13:49:50 -0500 [thread overview]
Message-ID: <7c03e44f-5e11-24b7-d65c-1f3839241a12@linux.vnet.ibm.com> (raw)
In-Reply-To: <325428771.GqrL96bkll@thomas>
Hi all,
IBM - DPDK on Power Systems
* Basic PF on Mellanox: No new issues or regressions were seen.
* Performance: not tested.
Systems tested:
- IBM Power9 PowerNV 9006-22P
OS: RHEL 8.3
GCC: version 8.3.1 20191121 (Red Hat 8.3.1-5)
NICs:
- Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
- firmware version: 16.29.1017
- MLNX_OFED_LINUX-5.2-1.0.4.1 (OFED-5.2-1.0.4)
- LPARs on IBM Power10 CHRP IBM,9105-42B
OS: RHEL 8.4
GCC: gcc version 8.4.1 20200928 (Red Hat 8.4.1-1)
NICs:
- Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
- firmware version: 16.30.1004
- MLNX_OFED_LINUX-5.3-1.0.0.2
Regards,
Thinh Tran
On 7/24/2021 8:38 AM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v21.08-rc2
>
> There are 287 new patches in this snapshot,
> most of them adding or fixing features in drivers.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_21_08.html
>
> Highlights of 21.08-rc2:
> - Wangxun ngbe ethernet driver
> - Marvell CNXK event Rx/Tx adapters
> - NVIDIA mlx5 crypto driver supporting AES-XTS
> - ISAL compress support on Arm
>
> Please test and report issues on bugs.dpdk.org.
>
> DPDK 21.08-rc3 is expected in one week.
>
> Thank you everyone
>
>
prev parent reply other threads:[~2021-07-30 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 13:38 Thomas Monjalon
2021-07-28 11:06 ` Jiang, YuX
2021-07-30 9:05 ` Jiang, YuX
2021-07-30 18:49 ` 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=7c03e44f-5e11-24b7-d65c-1f3839241a12@linux.vnet.ibm.com \
--to=thinhtr@linux.vnet.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).