From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| [GIT MASTER] 80fc98a06e7cab92d6d1ec4228cde9303be90997
Date: Mon, 22 Apr 2019 22:44:47 -0400 (EDT) [thread overview]
Message-ID: <20190423024447.984F8EDD9C@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
_Performance Testing PASS_
Branch: dpdk
80fc98a06e7cab92d6d1ec4228cde9303be90997 --> performance testing pass
Test environment and result as below:
Ubuntu 18.10
Kernel: 4.18.0-16-generic
GCC: gcc (Ubuntu 8.2.0-7ubuntu1) 8.2.0
NIC: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Detail performance results:
+------------+-----------------------------------+
| frame_size | ovs-perf difference from expected |
+============+===================================+
| 100 | 0 |
+------------+-----------------------------------+
https://lab.dpdk.org/results/dashboard/tarballs/4399/
UNH-IOL DPDK Performance Test Lab
next reply other threads:[~2019-04-23 2:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 2:44 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-23 2:44 dpdklab
2019-04-23 2:44 dpdklab
2019-04-22 22:19 dpdklab
2019-04-22 22:19 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=20190423024447.984F8EDD9C@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@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).