From: Kevin Traynor <ktraynor@redhat.com>
To: dwilder <dwilder@us.ibm.com>
Cc: dpdk stable <stable@dpdk.org>,
dev@dpdk.org, Sitong Liu <siliu@redhat.com>,
Pei Zhang <pezhang@redhat.com>,
Raslan Darawsheh <rasland@mellanox.com>,
qian.q.xu@intel.com, Ju-Hyoung Lee <juhlee@microsoft.com>,
Ian Stokes <ian.stokes@intel.com>,
Ali Alnubani <alialnu@mellanox.com>,
David Christensen <drc@linux.vnet.ibm.com>,
benjamin.walker@intel.com, Thomas Monjalon <thomas@monjalon.net>,
John McNamara <john.mcnamara@intel.com>,
Luca Boccassi <bluca@debian.org>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Akhil Goyal <akhil.goyal@nxp.com>
Subject: Re: [dpdk-dev] [dpdk-stable] 18.11.2 (LTS) patches review and test
Date: Fri, 24 May 2019 17:51:06 +0100 [thread overview]
Message-ID: <22bc3895-134f-9ee9-f211-5861bfeb795b@redhat.com> (raw)
In-Reply-To: <f3d5f1fc4fbee19e9b2acd3e346d10dd@linux.vnet.ibm.com>
On 24/05/2019 17:46, dwilder wrote:
> Hi Kevin-
>
> I tested 8.11.2 RC1 on IBM Power9 hardware. No issues or performance
> degradation were observed.
>
Thanks David. Good news on a Friday is always welcome :-)
> Tests run:
> * 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.
>
> System tested:
> - IBM Power9 Model 8335-101 CPU: 2.3 (pvr 004e 1203)
>
> Tested NICs:
> - ConnectX-5 (fw 16.23.1020).
>
> OS Tested
> - Ubuntu 18.04.2 LTS (kernel 4.15.0-47-generic)
>
I will add it to the release notes,
thanks,
Kevin.
> Regards,
> Dave
next prev parent reply other threads:[~2019-05-24 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 14:01 [dpdk-dev] " Kevin Traynor
2019-05-24 16:46 ` [dpdk-dev] [dpdk-stable] " dwilder
2019-05-24 16:51 ` Kevin Traynor [this message]
2019-05-30 22:32 ` Ju-Hyoung Lee
2019-05-30 8:15 ` [dpdk-dev] " Ian Stokes
2019-05-30 11:59 ` Ali Alnubani
2019-06-04 8:11 ` Pei Zhang
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=22bc3895-134f-9ee9-f211-5861bfeb795b@redhat.com \
--to=ktraynor@redhat.com \
--cc=akhil.goyal@nxp.com \
--cc=alialnu@mellanox.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=dwilder@us.ibm.com \
--cc=hemant.agrawal@nxp.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=juhlee@microsoft.com \
--cc=pezhang@redhat.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@mellanox.com \
--cc=siliu@redhat.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).