From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>, Ali Alnubani <alialnu@nvidia.com>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138641 [PATCH] net: stop using mmx intrinsics
Date: Wed, 20 Mar 2024 20:05:46 -0700 (PDT) [thread overview]
Message-ID: <65fba40a.170a0220.ee85b.6c38SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1710969121-18503-2-git-send-email-roretzla@linux.microsoft.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/138641
_Performance Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, March 20 2024 21:12:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
138641 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.7% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29611/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-21 3:11 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1710969121-18503-2-git-send-email-roretzla@linux.microsoft.com>
2024-03-20 20:52 ` qemudev
2024-03-20 20:56 ` qemudev
2024-03-20 21:12 ` checkpatch
2024-03-20 22:04 ` 0-day Robot
2024-03-21 2:35 ` dpdklab
2024-03-21 2:37 ` dpdklab
2024-03-21 2:39 ` dpdklab
2024-03-21 2:39 ` dpdklab
2024-03-21 2:40 ` dpdklab
2024-03-21 2:52 ` dpdklab
2024-03-21 2:57 ` dpdklab
2024-03-21 2:58 ` dpdklab
2024-03-21 3:01 ` dpdklab
2024-03-21 3:04 ` dpdklab
2024-03-21 3:05 ` dpdklab [this message]
2024-03-21 3:08 ` dpdklab
2024-03-21 3:12 ` dpdklab
2024-03-21 3:18 ` dpdklab
2024-03-21 3:27 ` dpdklab
2024-03-21 3:32 ` dpdklab
2024-03-21 4:46 ` dpdklab
2024-03-21 4:54 ` dpdklab
2024-03-21 4:55 ` dpdklab
2024-03-21 5:01 ` dpdklab
2024-03-21 5:25 ` dpdklab
2024-03-21 5:31 ` dpdklab
2024-03-21 5:33 ` dpdklab
2024-03-21 5:58 ` dpdklab
2024-03-21 5:58 ` dpdklab
2024-03-21 5:58 ` dpdklab
2024-03-21 6:01 ` dpdklab
2024-03-21 6:01 ` dpdklab
2024-03-21 6:02 ` dpdklab
2024-03-21 6:14 ` dpdklab
2024-03-21 6:14 ` dpdklab
2024-03-21 6:15 ` dpdklab
2024-03-21 6:15 ` dpdklab
2024-03-21 6:15 ` dpdklab
2024-03-21 6:16 ` dpdklab
2024-03-21 6:16 ` dpdklab
2024-03-21 6:16 ` dpdklab
2024-03-21 6:17 ` dpdklab
2024-03-21 6:17 ` dpdklab
2024-03-21 6:19 ` dpdklab
2024-03-21 6:20 ` dpdklab
2024-03-21 6:22 ` dpdklab
2024-03-21 6:30 ` dpdklab
2024-03-21 6:30 ` dpdklab
2024-03-21 6:30 ` dpdklab
2024-03-21 6:30 ` dpdklab
2024-03-21 6:31 ` dpdklab
2024-03-21 6:31 ` dpdklab
2024-03-21 6:32 ` dpdklab
2024-03-21 6:32 ` dpdklab
2024-03-21 6:32 ` dpdklab
2024-03-21 6:32 ` dpdklab
2024-03-21 6:32 ` dpdklab
2024-03-21 6:33 ` dpdklab
2024-03-21 6:34 ` dpdklab
2024-03-21 6:34 ` dpdklab
2024-03-21 6:34 ` dpdklab
2024-03-21 6:35 ` dpdklab
2024-03-21 6:36 ` dpdklab
2024-03-21 6:43 ` dpdklab
2024-03-21 6:44 ` dpdklab
2024-03-21 6:45 ` dpdklab
2024-03-21 7:09 ` dpdklab
2024-03-21 8:22 ` dpdklab
2024-03-21 8:23 ` dpdklab
2024-03-21 8:28 ` dpdklab
2024-03-21 8:32 ` dpdklab
2024-03-21 8:39 ` dpdklab
2024-03-21 8:41 ` dpdklab
2024-03-21 8:44 ` dpdklab
2024-03-21 8:50 ` dpdklab
2024-03-21 8:51 ` dpdklab
2024-03-21 9:01 ` dpdklab
2024-03-21 13:12 ` dpdklab
2024-03-21 13:26 ` dpdklab
2024-03-21 19:13 ` dpdklab
2024-03-22 22:34 ` dpdklab
2024-03-23 0:14 ` 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=65fba40a.170a0220.ee85b.6c38SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--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).