From: Thinh Tran <thinhtr@linux.vnet.ibm.com>
To: dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 21.11-rc2
Date: Wed, 17 Nov 2021 13:56:47 -0600 [thread overview]
Message-ID: <207a9885-17f5-a48d-42ee-24f427ddf8ec@linux.vnet.ibm.com> (raw)
In-Reply-To: <2415599.WskMzomRmS@thomas>
Hi
IBM - Power Systems
DPDK v21.11-rc2-101-g329f73eb35
* Basic PF on Mellanox: No new issues or regressions were seen.
* Performance: not tested.
Systems tested:
- IBM Power9 PowerNV 9006-22P
OS: RHEL 8.4
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)
Regards,
Thinh Tran
On 11/8/2021 6:45 PM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v21.11-rc2
>
> There are 448 new patches in this snapshot.
>
> Release notes:
> https://doc.dpdk.org/guides/rel_notes/release_21_11.html
>
> Highlights of 21.11-rc2:
> - Toeplitz hash using Galois Fields New Instructions (GFNI)
> - virtio RSS
> - vhost power monitor wakeup
> - Xilinx vDPA driver
> - DMA drivers for HiSilicon and Marvell CNXK
> - GPU device class library
> - AddressSanitizer (ASan) integration for debug
> - more API internals hidden (ip_frag, vDPA)
>
> Please test and report issues on bugs.dpdk.org.
> Some bugs found with ASan are tagged and can be found with this query:
> https://bugs.dpdk.org/buglist.cgi?quicksearch=[asan]
>
> DPDK 21.11-rc3 is expected in one week or less.
>
> Thank you everyone
>
>
prev parent reply other threads:[~2021-11-17 19:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 0:45 Thomas Monjalon
2021-11-11 8:25 ` Jiang, YuX
2021-11-11 8:57 ` David Marchand
2021-11-16 7:13 ` Jiang, YuX
2021-11-15 4:34 ` Pei Zhang
2021-11-15 5:00 ` [dpdk-dev] " Kalesh Anakkur Purayil
2021-11-17 19:56 ` 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=207a9885-17f5-a48d-42ee-24f427ddf8ec@linux.vnet.ibm.com \
--to=thinhtr@linux.vnet.ibm.com \
--cc=dev@dpdk.org \
/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).