All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thinh Tran <thinhtr@linux.vnet.ibm.com>
To: dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 21.02-rc1
Date: Fri, 29 Jan 2021 14:36:38 -0600	[thread overview]
Message-ID: <92ce632a-dc21-f50c-d4d6-85e7961b6e3b@linux.vnet.ibm.com> (raw)
In-Reply-To: <4846307.Pfn0FrbqUJ@thomas>

Hi
DPDK on IBM Power result

* DPDK: v21.02-rc1-58-g45eb6a1df
* Build with gcc 9.3.0-1: no issue found
* Basic PF on Mallanox: No new issues or regressions were seen.
* Performance: not tested yet.

System tested:
  - IBM Power9 Model 8335-101 CPU: 2.3 (pvr 004e 1203)
Tested NICs:
  - Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
  - MLNX_OFED_LINUX-4.9-0.0.4.1
  - Firmware level: 16.27.2008

Regards,
Thinh Tran
d
On 1/19/2021 8:06 PM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> 	https://git.dpdk.org/dpdk/tag/?id=v21.02-rc1
> 
> There are 544 new patches in this snapshot,
> which is reasonnable for starting a new year.
> 
> Release notes:
> 	https://doc.dpdk.org/guides/rel_notes/release_21_02.html
> 
> Highlights of 21.02-rc1, grouped by category:
> * Networking
> 	- power management API
> 	- generic modify action in flow API
> 	- GENEVE TLV option in flow API
> 	- Windows support of i40e and mlx5
> * Cryptography
> 	- callback API for enqueue/dequeue
> 
> Please test and report issues on bugs.dpdk.org.
> 
> DPDK 21.02-rc2 is expected at the end of this month
> and may include:
> 	- Arm build rework
> 	- pmdinfogen rework
> 	- power management updates
> 	- drivers updates
> 
> Let's be reactive and focus to allow a quiet Chinese New Year.
> Thank you everyone
> 
> 

      parent reply	other threads:[~2021-01-29 20:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20  2:06 [dpdk-dev] [dpdk-announce] release candidate 21.02-rc1 Thomas Monjalon
2021-01-22 10:36 ` Yu, PingX
2021-01-27  6:27   ` Jiang, YuX
2021-01-29 20:36 ` 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=92ce632a-dc21-f50c-d4d6-85e7961b6e3b@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.