From: Thinh Tran <thinhtr@linux.vnet.ibm.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 20.08-rc4
Date: Sat, 8 Aug 2020 00:11:50 -0500 [thread overview]
Message-ID: <87338a9b-c24c-a443-3ccb-5d42c0222f1c@linux.vnet.ibm.com> (raw)
In-Reply-To: <4161866.7AHn6HmuGJ@thomas>
Hi-
IBM - DPDK on Power result
*Basic PF on Mallanox: No new errors or regressions were seen.
*Performance: no degradation compared to 20.05
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
Regards,
Thinh Tran
On 8/5/2020 8:02 PM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v20.08-rc4
>
> There are 27 new patches in this snapshot.
>
> Release notes:
> http://doc.dpdk.org/guides/rel_notes/release_20_08.html
> More deprecation notices are pending for acceptance.
>
> This is the last release candidate for DPDK 20.08.
> After -rc4 there should be only doc updates.
> Please review pending patches related to the documentation
> and the deprecation notices:
> https://patches.dpdk.org/project/dpdk/list/?q=doc
>
> Please share some release validation results
> by replying to this message (at dev@dpdk.org).
> If no critical issue is reported, 20.08 will be closed end of this week.
>
> If you are preparing the next release cycle, please send your v1 patches
> before the end of August.
> We should also build and discuss the features roadmap for 20.11 soon,
> so we can prioritize tasks and avoid flooding maintainers.
>
> Thank you everyone
>
>
next prev parent reply other threads:[~2020-08-08 5:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 1:02 Thomas Monjalon
2020-08-08 5:11 ` Thinh Tran [this message]
2020-08-08 13:04 ` [dpdk-dev] [EXT] " Apeksha Gupta
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=87338a9b-c24c-a443-3ccb-5d42c0222f1c@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).