From: dpdklab@iol.unh.edu
To: Ruoshan Shi <ruoshan.shi@nxp.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw64678 [PATCH] net/ixgbe: fix build for gcc 4.8.5
Date: Tue, 14 Jan 2020 19:08:52 -0500 (EST) [thread overview]
Message-ID: <20200115000852.B39B7A7A2@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
Test-Label: iol-nxp-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/64678
_Performance Testing PASS_
Submitter: Ferruh Yigit <ferruh.yigit@intel.com>
Date: Tuesday, January 14 2020 17:52:47
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a02b9406a8769247737b55dbfa50b6b5f896d946
64678 --> performance testing pass
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.14.122
GCC: 7.3.0
NIC: NXP LS2088A 10000 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.136 |
+------------+---------+-------------------------------------+
| 64 | 2048 | -0.565 |
+------------+---------+-------------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/9195/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2020-01-15 0:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 0:08 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-15 0:08 dpdklab
2020-01-14 22:47 dpdklab
2020-01-14 22:40 dpdklab
[not found] <20200114175247.2930261-1-ferruh.yigit@intel.com>
2020-01-14 17:53 ` 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=20200115000852.B39B7A7A2@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ruoshan.shi@nxp.com \
--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).