From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw96326 [PATCH] [v1] net/ice: fix wrong bandwidth config size in memory copy
Date: Tue, 10 Aug 2021 13:42:09 -0400 (EDT) [thread overview]
Message-ID: <20210810174209.2F523A605@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2964 bytes --]
Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/96326
_Performance Testing PASS_
Submitter: Ting Xu <ting.xu@intel.com>
Date: Tuesday, July 27 2021 10:55:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:02e077f35dbc9821dfcb32714ad1096a3ee58d08
96326 --> 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 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.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.6% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 2 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 2 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
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 | 8.6% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 4.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 2 | 7.8% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 2 | 3.6% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/17998/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-08-10 17:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 17:42 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-10 17:48 dpdklab
2021-07-29 16:52 dpdklab
2021-07-29 16:31 dpdklab
2021-07-29 16:15 dpdklab
2021-07-27 17:26 dpdklab
2021-07-27 17:05 dpdklab
2021-07-27 13:06 dpdklab
2021-07-27 12:45 dpdklab
[not found] <20210727105508.33586-1-ting.xu@intel.com>
2021-07-27 10:52 ` [dpdk-test-report] |SUCCESS| pw96326 [PATCH v1] " 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=20210810174209.2F523A605@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).