DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thinh Tran <thinhtr@linux.vnet.ibm.com>
To: dpdk-dev <dev@dpdk.org>
Subject: Re: release candidate 21.11-rc3
Date: Tue, 23 Nov 2021 20:09:00 -0600	[thread overview]
Message-ID: <f5980c76-d456-03fc-e1b7-cb5f24c658c9@linux.vnet.ibm.com> (raw)
In-Reply-To: <2505332.shY60l8dLD@thomas>

Hi
IBM - Power Systems
DPDK 21.11-rc3

* 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: gcc version 8.4.1 20200928 (Red Hat 8.4.1-1)
     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-22A
     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.24.8000
     - MLNX_OFED_LINUX-5.4-2.4.1.5

Regards,
Thinh Tran


On 11/17/2021 1:30 PM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> 	https://git.dpdk.org/dpdk/tag/?id=v21.11-rc3
> 
> There are 178 new patches in this snapshot.
> 
> Release notes:
> 	https://doc.dpdk.org/guides/rel_notes/release_21_11.html
> 
> Highlights of 21.11-rc3:
> 	- NXP DPAA DMA driver
> 	- NXP ENETFEC networking driver
> 	- NVIDIA CUDA driver
> 
> Please test and report issues on bugs.dpdk.org.
> It would be nice to fix bugs found with ASan:
> 	https://bugs.dpdk.org/buglist.cgi?quicksearch=[asan]
> 
> You may share some release validation results
> by replying to this message at dev@dpdk.org.
> 
> DPDK 21.11-rc4 should be the last chance for bug fixes and doc updates
> before the major release.
> 
> Thank you everyone
> 
> 

      reply	other threads:[~2021-11-24  2:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17 19:30 Thomas Monjalon
2021-11-24  2:09 ` 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=f5980c76-d456-03fc-e1b7-cb5f24c658c9@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).