From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw103204 [PATCH] app/flow-perf: added option to support flow priority
Date: Fri, 29 Oct 2021 04:52:50 +0000 (UTC) [thread overview]
Message-ID: <20211029045250.3A9C6602B0@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2978 bytes --]
Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/103204
_Performance Testing PASS_
Submitter: Satheesh Paul <psatheesh@marvell.com>
Date: Friday, October 29 2021 04:08:47
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:efb57dd5bbf0ffac645d09ed4d0dbad088b602f1
103204 --> performance testing pass
Test environment and result as below:
Ubuntu 20.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/4
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | -0.4% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.6% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 2 | -3.4% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 2 | -1.9% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 20.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/4
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 2 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 2 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/19831/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-10-29 4:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 4:52 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-30 20:56 dpdklab
2021-10-30 20:44 dpdklab
2021-10-30 12:59 dpdklab
2021-10-30 2:54 dpdklab
2021-10-29 13:41 dpdklab
2021-10-29 4:59 dpdklab
2021-10-29 4:51 dpdklab
2021-10-29 4:50 dpdklab
2021-10-29 4:45 dpdklab
2021-10-29 4:39 dpdklab
2021-10-29 4:36 dpdklab
[not found] <20211029040847.2176787-1-psatheesh@marvell.com>
2021-10-29 4:09 ` 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=20211029045250.3A9C6602B0@dpdk-ubuntu.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).