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: [dpdk-dev] [dpdk-announce] release candidate 20.05-rc4
Date: Tue, 26 May 2020 09:41:55 -0500	[thread overview]
Message-ID: <1ceefa1b-4a7b-419e-e7cc-57e6a6bfc0bc@linux.vnet.ibm.com> (raw)
In-Reply-To: <31184835.9hX2MqESlx@thomas>

Hi-

IBM - DPDK on Power result

*Basic PF on Mallanox: No new errors or regressions were seen.
*Performance: no degradation compared to 20.02

System tested:
  - IBM Power9 Model 8335-101 CPU: 2.3 (pvr 004e 1203)
Tested NICs:
  - Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
  - firmware version: 16.26.4012
  - MLNX_OFED_LINUX-4.7-3.2.9.1


Regards,
Thinh Tran

On 5/24/2020 7:09 PM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> 	https://git.dpdk.org/dpdk/tag/?id=v20.05-rc4
> 
> There are 44 new patches in this snapshot.
> 
> Release notes:
> 	http://doc.dpdk.org/guides/rel_notes/release_20_05.html
> Some deprecation notices might be added if reviewed on time.
> 
> This is the last release candidate for DPDK 20.05.
> After -rc4 there should be only doc updates.
> Please share some release validation results
> by replying to this message (at dev@dpdk.org).
> If no critical issue is reported, 20.05 will be closed on Tuesday 26 May.
> 
> If you are preparing the next release cycle, please send your v1 patches
> before the 20.08 proposal deadline, the Friday 12 June.
> It is also time to build an estimated roadmap for the next cycles.
> 
> Thank you everyone
> 
> 

      reply	other threads:[~2020-05-26 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25  0:09 Thomas Monjalon
2020-05-26 14:41 ` 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=1ceefa1b-4a7b-419e-e7cc-57e6a6bfc0bc@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).