From: Thinh Tran <thinhtr@linux.vnet.ibm.com>
To: dev@dpdk.org
Cc: drc@ibm.com, pradeep@us.ibm.com, dwilder@us.ibm.com
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 19.08-rc4
Date: Fri, 9 Aug 2019 16:03:29 -0500 [thread overview]
Message-ID: <cab6e536-627f-13ce-ac12-dacde5187a2c@linux.vnet.ibm.com> (raw)
In-Reply-To: <1789600.lZGjF2gddP@xps>
IBM Power9 testing for v19.08-rc4
Hi-
The following describes the test completed for v19.08-rc4 run on IBM
Power9 hardware.
* Single port stability test using l3fwd (16 cpus) and TRex, tested 64
and 1500 byte packets at a 0.0% drop rate for 4 hours each.
No errors or regressions were seen.
System tested:
- IBM Power9 Model 8335-101 CPU: 2.3 (pvr 004e 1203)
Tested NICs:
- Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
FW Version: 16.23.1020
OS Tested
- Ubuntu 18.04.2 LTS kernel: 4.15.0-50-generic
Latest dpdk tested version:
- version(tag): v19.08-rc4-12-g07f08a96f
Regards,
Thinh Tran
On 8/6/2019 5:05 PM, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v19.08-rc4
> 82 patches were integrated.
> This is the last release candidate for DPDK 19.08.
>
> The release notes are complete:
> http://doc.dpdk.org/guides/rel_notes/release_19_08.html
> Only the deprecation notices are missing (waiting for comments).
>
> This is the right time to do the last checks.
> Please share some release validation results
> by replying to this message (at dev@dpdk.org).
> If no objection, the version 19.08.0 will be out on August 11.
>
> If you are preparing the next release cycle, please send your v1 patches
> before the 19.11 proposal deadline, which will happen on September 6.
> It is also time to build an estimated roadmap for the next cycles.
>
> Thank you everyone
>
>
parent reply other threads:[~2019-08-09 21:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1789600.lZGjF2gddP@xps>]
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=cab6e536-627f-13ce-ac12-dacde5187a2c@linux.vnet.ibm.com \
--to=thinhtr@linux.vnet.ibm.com \
--cc=dev@dpdk.org \
--cc=drc@ibm.com \
--cc=dwilder@us.ibm.com \
--cc=pradeep@us.ibm.com \
/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).