From: Kevin Traynor <ktraynor@redhat.com>
To: dpdklab@iol.unh.edu, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-test-report] |SUCCESS| pw53107 [PATCH] vfio: expand non-viable group error message
Date: Fri, 26 Apr 2019 19:06:16 +0100 [thread overview]
Message-ID: <dd387871-adf4-550a-a9dd-d457c6948c16@redhat.com> (raw)
In-Reply-To: <20190426175443.EC4E0EDD97@noxus.dpdklab.iol.unh.edu>
On 26/04/2019 18:54, dpdklab@iol.unh.edu wrote:
> Test-Label: intel-Performance-Testing
> Test-Status: SUCCESS
> http://dpdk.org/patch/53107
>
> _Performance Testing PASS_
>
> Submitter: Kevin Traynor <ktraynor@redhat.com>
> Date: Friday, April 26 2019 16:22:30
> DPDK git baseline: Repo:dpdk
> Branch: master
> CommitID:7f251bcf22c5729792f9243480af1b3c072876a5
>
> 53107 --> performance testing pass
>
> Test environment and result as below:
>
> Ubuntu 17.10
> Kernel: 4.13.0-43-generic
> GCC: gcc (Ubuntu 7.2.0-8ubuntu3) 7.2.0
> NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
> Target: x86_64-native-linuxapp-gcc
> Fail/Total: 0/2
>
> Detail performance results:
> +------------+---------+-------------------------------------+
> | frame_size | txd/rxd | throughput difference from expected |
> +============+=========+=====================================+
> | 64 | 512 | 0.095 |
> +------------+---------+-------------------------------------+
> | 64 | 2048 | 0.192 |
> +------------+---------+-------------------------------------+
>
> Ubuntu 17.10
> Kernel: 4.13.0-43-generic
> GCC: gcc (Ubuntu 7.2.0-8ubuntu3) 7.2.0
> NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
> Target: x86_64-native-linuxapp-gcc
> Fail/Total: 0/3
>
> Detail performance results:
> +------------+---------+-------------------------------------+
> | frame_size | txd/rxd | throughput difference from expected |
> +============+=========+=====================================+
> | 64 | 128 | -0.572 |
> +------------+---------+-------------------------------------+
> | 64 | 512 | 6.765 |
> +------------+---------+-------------------------------------+
> | 64 | 2048 | 5.058 |
> +------------+---------+-------------------------------------+
>
FYI - this seems very strange. I updated a control/error path log text.
The report saying perf is dropping 6 mpps? and also that is a pass?
> https://lab.dpdk.org/results/dashboard/patchsets/5602/
>
> UNH-IOL DPDK Performance Test Lab
>
> To manage your email subscriptions visit:
> https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
>
next prev parent reply other threads:[~2019-04-29 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 17:54 dpdklab
2019-04-26 18:06 ` Kevin Traynor [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-26 17:54 dpdklab
[not found] <20190426162230.21158-1-ktraynor@redhat.com>
2019-04-26 16:22 ` checkpatch
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=dd387871-adf4-550a-a9dd-d457c6948c16@redhat.com \
--to=ktraynor@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=dpdklab@iol.unh.edu \
--cc=ferruh.yigit@intel.com \
--cc=test-report@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).