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| pw70961 [PATCH] devtools: allow ENOSYS in checkpatch
Date: Mon, 8 Jun 2020 10:44:26 -0400 (EDT) [thread overview]
Message-ID: <20200608144426.7FE0D6D4B0@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
Test-Label: iol-nxp-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/70961
_Performance Testing PASS_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Monday, June 08 2020 13:28:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:60814f955cfdebeb1d7bb3c8c5ae6c566b15f572
70961 --> performance testing pass
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.14.122
Compiler: 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.291 |
+------------+---------+-------------------------------------+
| 64 | 2048 | 0.054 |
+------------+---------+-------------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/11394/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2020-06-08 14:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 14:44 dpdklab [this message]
[not found] <20200608132850.2096345-1-thomas@monjalon.net>
2020-06-10 7:57 ` checkpatch
-- strict thread matches above, loose matches on Subject: below --
2020-06-08 15:55 dpdklab
2020-06-08 15:40 dpdklab
2020-06-08 15:26 dpdklab
2020-06-08 14:35 dpdklab
2020-06-08 14:09 dpdklab
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=20200608144426.7FE0D6D4B0@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).