From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw142085 [PATCH] net/gve: fix RSS hash endianness in DQO f
Date: Thu, 04 Jul 2024 01:35:11 -0700 (PDT) [thread overview]
Message-ID: <66865ebf.050a0220.246a2a.96cdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240703133153.157661-1-16567adigashreesh@gmail.com>
Test-Label: iol-intel-Performance
Test-Status: PENDING
http://dpdk.org/patch/142085
_Performance Testing pending_
Submitter: Shreesh Adiga <16567adigashreesh@gmail.com>
Date: Wednesday, July 03 2024 13:31:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fbba6db3640f9f623c29c452e1a6b057073e81d2
142085 --> performance testing pending
Test environment and result as below:
22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Intel E810 100000 Mbps
Target: Unknown
Fail/Total: 0/1
Detail performance results:
The measurement deltas are not ready yet! Please check back later.
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: Unknown
Fail/Total: 0/4
Detail performance results:
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size | throughput difference from |
| | | | | expected |
+==========+=============+=========+============+==============================+
| 1 | 2 | 512 | 64 | -0.6% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 2 | 2048 | 64 | -0.9% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 512 | 64 | -0.9% |
+----------+-------------+---------+------------+------------------------------+
| 1 | 1 | 2048 | 64 | 0.6% |
+----------+-------------+---------+------------+------------------------------+
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: Unknown
Fail/Total: 0/1
Detail performance results:
The measurement deltas are not ready yet! Please check back later.
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30401/
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-07-04 8:35 UTC|newest]
Thread overview: 114+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240703133153.157661-1-16567adigashreesh@gmail.com>
2024-07-03 13:04 ` |SUCCESS| pw142085 [PATCH] net/gve: fix RSS hash endianness in DQO format qemudev
2024-07-03 13:09 ` qemudev
2024-07-03 13:32 ` checkpatch
2024-07-03 14:25 ` 0-day Robot
2024-07-04 8:35 ` dpdklab [this message]
2024-07-04 8:38 ` |SUCCESS| pw142085 [PATCH] net/gve: fix RSS hash endianness in DQO f dpdklab
2024-07-04 8:40 ` dpdklab
2024-07-04 8:48 ` dpdklab
2024-07-04 8:53 ` dpdklab
2024-07-04 8:53 ` dpdklab
2024-07-04 9:23 ` dpdklab
2024-07-04 11:35 ` |PENDING| " dpdklab
2024-07-04 11:38 ` dpdklab
2024-07-04 11:39 ` dpdklab
2024-07-04 11:41 ` dpdklab
2024-07-04 11:44 ` dpdklab
2024-07-04 11:45 ` dpdklab
2024-07-04 11:46 ` dpdklab
2024-07-04 11:51 ` dpdklab
2024-07-04 11:52 ` |FAILURE| " dpdklab
2024-07-04 11:52 ` |PENDING| " dpdklab
2024-07-04 11:54 ` dpdklab
2024-07-04 11:56 ` dpdklab
2024-07-04 11:58 ` dpdklab
2024-07-04 11:59 ` dpdklab
2024-07-04 12:01 ` |SUCCESS| " dpdklab
2024-07-04 13:54 ` dpdklab
2024-07-04 13:58 ` dpdklab
2024-07-04 14:02 ` dpdklab
2024-07-04 14:06 ` dpdklab
2024-07-04 14:25 ` dpdklab
2024-07-04 15:04 ` dpdklab
2024-07-04 15:11 ` dpdklab
2024-07-04 15:14 ` dpdklab
2024-07-04 15:46 ` dpdklab
2024-07-04 19:25 ` |PENDING| " dpdklab
2024-07-04 19:27 ` dpdklab
2024-07-04 19:27 ` dpdklab
2024-07-04 19:29 ` dpdklab
2024-07-04 19:31 ` |SUCCESS| " dpdklab
2024-07-04 19:31 ` dpdklab
2024-07-04 21:47 ` |PENDING| " dpdklab
2024-07-04 22:52 ` |SUCCESS| " dpdklab
2024-07-05 1:38 ` |PENDING| " dpdklab
2024-07-05 2:01 ` dpdklab
2024-07-05 2:07 ` dpdklab
2024-07-05 3:04 ` dpdklab
2024-07-05 3:56 ` dpdklab
2024-07-05 5:28 ` dpdklab
2024-07-05 5:29 ` dpdklab
2024-07-05 6:34 ` dpdklab
2024-07-05 6:50 ` dpdklab
2024-07-05 6:57 ` dpdklab
2024-07-05 6:57 ` dpdklab
2024-07-05 7:06 ` dpdklab
2024-07-05 7:07 ` dpdklab
2024-07-05 7:14 ` dpdklab
2024-07-05 7:37 ` dpdklab
2024-07-05 7:37 ` dpdklab
2024-07-05 7:40 ` dpdklab
2024-07-05 7:42 ` dpdklab
2024-07-05 7:44 ` dpdklab
2024-07-05 7:46 ` dpdklab
2024-07-05 7:47 ` dpdklab
2024-07-05 7:49 ` dpdklab
2024-07-05 7:55 ` dpdklab
2024-07-05 7:59 ` dpdklab
2024-07-05 7:59 ` dpdklab
2024-07-05 8:04 ` dpdklab
2024-07-05 8:05 ` dpdklab
2024-07-05 8:06 ` dpdklab
2024-07-05 8:10 ` dpdklab
2024-07-05 8:13 ` dpdklab
2024-07-05 8:14 ` dpdklab
2024-07-05 8:22 ` |SUCCESS| " dpdklab
2024-07-05 8:24 ` dpdklab
2024-07-05 8:25 ` dpdklab
2024-07-05 8:52 ` |PENDING| " dpdklab
2024-07-05 8:52 ` dpdklab
2024-07-05 8:54 ` dpdklab
2024-07-05 8:59 ` dpdklab
2024-07-05 9:04 ` dpdklab
2024-07-05 9:10 ` dpdklab
2024-07-05 9:14 ` dpdklab
2024-07-05 9:14 ` dpdklab
2024-07-05 9:17 ` dpdklab
2024-07-05 9:22 ` dpdklab
2024-07-05 9:23 ` dpdklab
2024-07-05 9:26 ` dpdklab
2024-07-05 9:28 ` dpdklab
2024-07-05 9:28 ` dpdklab
2024-07-05 9:28 ` dpdklab
2024-07-05 9:30 ` dpdklab
2024-07-05 9:30 ` dpdklab
2024-07-05 9:34 ` dpdklab
2024-07-05 9:37 ` dpdklab
2024-07-05 9:41 ` dpdklab
2024-07-05 9:46 ` dpdklab
2024-07-05 9:46 ` |SUCCESS| " dpdklab
2024-07-05 9:52 ` |PENDING| " dpdklab
2024-07-05 9:53 ` dpdklab
2024-07-05 10:08 ` dpdklab
2024-07-05 10:10 ` dpdklab
2024-07-05 10:17 ` dpdklab
2024-07-05 10:18 ` dpdklab
2024-07-05 10:19 ` dpdklab
2024-07-05 10:26 ` dpdklab
2024-07-05 11:06 ` dpdklab
2024-07-05 11:12 ` |SUCCESS| " dpdklab
2024-07-05 18:50 ` dpdklab
2024-07-05 22:22 ` dpdklab
2024-07-06 2:15 ` dpdklab
2024-07-06 5:56 ` dpdklab
2024-07-06 7:11 ` 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=66865ebf.050a0220.246a2a.96cdSMTPIN_ADDED_MISSING@mx.google.com \
--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).