From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142774 [PATCH] [v2] net/gve: Fix TX/RX queue setup and s
Date: Wed, 31 Jul 2024 06:37:56 -0700 (PDT) [thread overview]
Message-ID: <66aa3e34.050a0220.f54ef.d38aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1722403603-2399714-1-git-send-email-tathagat.dpdk@gmail.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/142774
_Performance Testing PASS_
Submitter: Tathagat Priyadarshi <tathagat.dpdk@gmail.com>
Date: Wednesday, July 31 2024 05:26:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4b5abe7ec1ed2d43a285599bbba23f62ac049d8f
142774 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#172073
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
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.4% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30663/
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-31 13:48 UTC|newest]
Thread overview: 114+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1722403603-2399714-1-git-send-email-tathagat.dpdk@gmail.com>
2024-07-31 5:02 ` |SUCCESS| pw142774 [PATCH v2] net/gve: Fix TX/RX queue setup and stop qemudev
2024-07-31 5:07 ` qemudev
2024-07-31 5:30 ` checkpatch
2024-07-31 6:22 ` 0-day Robot
2024-07-31 13:37 ` dpdklab [this message]
2024-07-31 14:10 ` |PENDING| pw142774 [PATCH] [v2] net/gve: Fix TX/RX queue setup and s dpdklab
2024-07-31 14:22 ` |SUCCESS| " dpdklab
2024-07-31 14:39 ` |PENDING| " dpdklab
2024-07-31 14:46 ` |SUCCESS| " dpdklab
2024-07-31 14:52 ` dpdklab
2024-07-31 14:54 ` dpdklab
2024-07-31 15:08 ` dpdklab
2024-07-31 15:46 ` dpdklab
2024-07-31 16:50 ` |PENDING| " dpdklab
2024-07-31 17:02 ` dpdklab
2024-07-31 17:02 ` dpdklab
2024-07-31 17:06 ` dpdklab
2024-07-31 17:07 ` dpdklab
2024-07-31 17:09 ` dpdklab
2024-07-31 17:09 ` dpdklab
2024-07-31 17:15 ` dpdklab
2024-07-31 17:16 ` dpdklab
2024-07-31 17:20 ` dpdklab
2024-07-31 17:21 ` dpdklab
2024-07-31 17:27 ` dpdklab
2024-07-31 17:36 ` dpdklab
2024-07-31 17:38 ` dpdklab
2024-07-31 17:40 ` |SUCCESS| " dpdklab
2024-07-31 17:41 ` dpdklab
2024-07-31 18:14 ` |PENDING| " dpdklab
2024-07-31 18:22 ` |SUCCESS| " dpdklab
2024-07-31 18:56 ` |PENDING| " dpdklab
2024-07-31 18:57 ` |SUCCESS| " dpdklab
2024-07-31 18:58 ` |PENDING| " dpdklab
2024-07-31 18:59 ` dpdklab
2024-07-31 19:01 ` dpdklab
2024-07-31 19:02 ` dpdklab
2024-07-31 19:13 ` dpdklab
2024-07-31 19:18 ` dpdklab
2024-07-31 19:19 ` dpdklab
2024-07-31 19:25 ` dpdklab
2024-07-31 19:26 ` dpdklab
2024-07-31 19:27 ` dpdklab
2024-07-31 19:33 ` dpdklab
2024-07-31 19:39 ` dpdklab
2024-07-31 19:48 ` dpdklab
2024-07-31 19:50 ` dpdklab
2024-07-31 19:57 ` dpdklab
2024-07-31 19:59 ` dpdklab
2024-07-31 20:02 ` dpdklab
2024-07-31 20:06 ` dpdklab
2024-07-31 20:07 ` dpdklab
2024-07-31 20:07 ` dpdklab
2024-07-31 20:08 ` dpdklab
2024-07-31 20:09 ` dpdklab
2024-07-31 20:14 ` dpdklab
2024-07-31 20:19 ` dpdklab
2024-07-31 20:21 ` dpdklab
2024-07-31 20:22 ` dpdklab
2024-07-31 20:27 ` dpdklab
2024-07-31 20:30 ` dpdklab
2024-07-31 20:32 ` dpdklab
2024-07-31 20:35 ` dpdklab
2024-07-31 20:35 ` dpdklab
2024-07-31 20:36 ` dpdklab
2024-07-31 20:38 ` dpdklab
2024-07-31 20:38 ` dpdklab
2024-07-31 20:48 ` dpdklab
2024-07-31 20:50 ` dpdklab
2024-07-31 20:53 ` dpdklab
2024-07-31 21:35 ` dpdklab
2024-07-31 22:12 ` dpdklab
2024-07-31 22:13 ` dpdklab
2024-07-31 22:15 ` dpdklab
2024-07-31 22:17 ` dpdklab
2024-07-31 22:17 ` dpdklab
2024-07-31 22:20 ` dpdklab
2024-07-31 22:21 ` dpdklab
2024-07-31 22:26 ` dpdklab
2024-07-31 22:27 ` dpdklab
2024-07-31 22:28 ` dpdklab
2024-07-31 22:37 ` dpdklab
2024-07-31 22:38 ` dpdklab
2024-07-31 22:40 ` dpdklab
2024-07-31 22:41 ` dpdklab
2024-07-31 22:41 ` dpdklab
2024-07-31 22:42 ` dpdklab
2024-07-31 22:44 ` dpdklab
2024-07-31 22:44 ` dpdklab
2024-07-31 22:45 ` dpdklab
2024-07-31 22:45 ` dpdklab
2024-07-31 22:45 ` dpdklab
2024-07-31 22:46 ` dpdklab
2024-07-31 22:47 ` |SUCCESS| " dpdklab
2024-07-31 22:50 ` |PENDING| " dpdklab
2024-07-31 22:50 ` dpdklab
2024-07-31 22:51 ` dpdklab
2024-07-31 22:52 ` |SUCCESS| " dpdklab
2024-07-31 22:53 ` |PENDING| " dpdklab
2024-07-31 22:53 ` dpdklab
2024-07-31 22:55 ` dpdklab
2024-07-31 22:56 ` |SUCCESS| " dpdklab
2024-07-31 22:56 ` |PENDING| " dpdklab
2024-07-31 22:57 ` |SUCCESS| " dpdklab
2024-07-31 22:59 ` |PENDING| " dpdklab
2024-07-31 23:00 ` |SUCCESS| " dpdklab
2024-07-31 23:03 ` |PENDING| " dpdklab
2024-07-31 23:04 ` dpdklab
2024-07-31 23:06 ` dpdklab
2024-07-31 23:08 ` |SUCCESS| " dpdklab
2024-07-31 23:11 ` dpdklab
2024-07-31 23:18 ` dpdklab
2024-07-31 23:20 ` dpdklab
2024-08-02 0:10 ` 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=66aa3e34.050a0220.f54ef.d38aSMTPIN_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).