From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw80723 [PATCH] eal: fix build with conflicting libc variable memory_order
Date: Wed, 14 Oct 2020 11:34:25 -0400 (EDT) [thread overview]
Message-ID: <20201014153425.396F460524@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1912 bytes --]
Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/80723
_Performance Testing PASS_
Submitter: Eli Britstein <elibr@nvidia.com>
Date: Wednesday, October 14 2020 06:19:09
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:9d3ad80abd34f2420998d94606e208518d330bcc
80723 --> performance testing pass
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
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 | 2.747 |
+------------+---------+-------------------------------------+
| 64 | 2048 | 1.694 |
+------------+---------+-------------------------------------+
Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 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 | 1.856 |
+------------+---------+-------------------------------------+
| 64 | 2048 | 0.871 |
+------------+---------+-------------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/13701/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2020-10-14 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 15:34 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-14 22:14 dpdklab
2020-10-14 15:10 dpdklab
2020-10-14 14:49 dpdklab
2020-10-14 13:16 dpdklab
2020-10-14 13:08 dpdklab
[not found] <20201014061909.9957-1-elibr@nvidia.com>
2020-10-14 12:03 ` 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=20201014153425.396F460524@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).