From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@dpdk.org,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126211-126212 [PATCH] [2/2] net/iavf: add Rx AVX2 offload path
Date: Tue, 18 Apr 2023 09:33:30 +0000 (UTC) [thread overview]
Message-ID: <20230418093330.897C160095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/126212
_Performance Testing PASS_
Submitter: Wenzhuo Lu <wenzhuo.lu@intel.com>
Date: Tuesday, April 18 2023 05:11:06
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd
126211-126212 --> performance testing pass
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.15.0-166-generic
Compiler: gcc 7.5.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.0% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26024/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-18 9:33 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 9:33 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-18 23:15 dpdklab
2023-04-18 23:15 dpdklab
2023-04-18 21:31 dpdklab
2023-04-18 21:31 dpdklab
2023-04-18 15:50 dpdklab
2023-04-18 15:10 dpdklab
2023-04-18 14:54 dpdklab
2023-04-18 13:09 dpdklab
2023-04-18 11:17 dpdklab
2023-04-18 11:17 dpdklab
2023-04-18 11:12 dpdklab
2023-04-18 11:04 dpdklab
2023-04-18 10:59 dpdklab
2023-04-18 10:58 dpdklab
2023-04-18 10:57 dpdklab
2023-04-18 10:54 dpdklab
2023-04-18 10:54 dpdklab
2023-04-18 10:54 dpdklab
2023-04-18 10:53 dpdklab
2023-04-18 10:29 dpdklab
2023-04-18 10:22 dpdklab
2023-04-18 10:17 dpdklab
2023-04-18 10:15 dpdklab
2023-04-18 10:15 dpdklab
2023-04-18 10:11 dpdklab
2023-04-18 10:10 dpdklab
2023-04-18 10:06 dpdklab
2023-04-18 9:58 dpdklab
2023-04-18 9:53 dpdklab
2023-04-18 9:52 dpdklab
2023-04-18 9:50 dpdklab
2023-04-18 9:45 dpdklab
2023-04-18 9:41 dpdklab
2023-04-18 9:40 dpdklab
2023-04-18 9:40 dpdklab
2023-04-18 9:37 dpdklab
2023-04-18 9:36 dpdklab
2023-04-18 9:36 dpdklab
2023-04-18 9:34 dpdklab
2023-04-18 9:29 dpdklab
2023-04-18 9:27 dpdklab
2023-04-18 9:05 dpdklab
2023-04-18 9:01 dpdklab
2023-04-18 8:58 dpdklab
2023-04-18 8:53 dpdklab
2023-04-18 8:49 dpdklab
2023-04-18 8:47 dpdklab
2023-04-18 8:45 dpdklab
2023-04-18 8:44 dpdklab
2023-04-18 8:43 dpdklab
2023-04-18 8:41 dpdklab
2023-04-18 8:41 dpdklab
2023-04-18 8:39 dpdklab
2023-04-18 8:37 dpdklab
[not found] <1681794666-68144-3-git-send-email-wenzhuo.lu@intel.com>
2023-04-18 5:33 ` |SUCCESS| pw126211-126212 [PATCH 2/2] " qemudev
2023-04-18 5:38 ` qemudev
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=20230418093330.897C160095@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@dpdk.org \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).