automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw56474 [PATCH] [v2] examples/vm_power: fix strcpy buffer overrun
Date: Tue, 16 Jul 2019 10:25:16 -0400 (EDT)	[thread overview]
Message-ID: <20190716142516.9B65F446@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 2059 bytes --]

Test-Label: intel-Performance-Testing
Test-Status: SUCCESS
http://dpdk.org/patch/56474

_Performance Testing PASS_

Submitter: Hunt, David <david.hunt@intel.com>
Date: Tuesday, July 16 2019 08:24:05 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5eb1708ec1db1f2d644f44a42468139df0b0ad6c

56474 --> 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.651                              |
+------------+---------+-------------------------------------+
| 64         | 2048    | -0.242                              |
+------------+---------+-------------------------------------+

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.360                               |
+------------+---------+-------------------------------------+
| 64         | 512     | -0.625                              |
+------------+---------+-------------------------------------+
| 64         | 2048    | 0.289                               |
+------------+---------+-------------------------------------+

https://lab.dpdk.org/results/dashboard/patchsets/6617/

UNH-IOL DPDK Performance Test Lab

To manage your email subscriptions visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2019-07-16 14:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-16 14:25 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-07-16 14:25 dpdklab
     [not found] <20190716082405.22394-1-david.hunt@intel.com>
2019-07-16  8:25 ` [dpdk-test-report] |SUCCESS| pw56474 [PATCH v2] " 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=20190716142516.9B65F446@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@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).