From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142675 [PATCH] net/gve: Fix TX/RX queue setup and stop f
Date: Wed, 24 Jul 2024 01:40:18 -0700 (PDT) [thread overview]
Message-ID: <66a0bdf2.170a0220.26dcac.5b52SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1721800736-2392953-1-git-send-email-tathagat.dpdk@gmail.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/142675
_Performance Testing PASS_
Submitter: Tathagat Priyadarshi <tathagat.dpdk@gmail.com>
Date: Wednesday, July 24 2024 05:58:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:9cad88310860ad99f9133af39f9cf98e524de9ac
142675 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#170290
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Fail/Total: 0/3
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -0.8% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30601/
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-24 9:54 UTC|newest]
Thread overview: 105+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1721800736-2392953-1-git-send-email-tathagat.dpdk@gmail.com>
2024-07-24 5:48 ` |SUCCESS| pw142675 [PATCH] net/gve: Fix TX/RX queue setup and stop for DQO qemudev
2024-07-24 5:53 ` qemudev
2024-07-24 6:10 ` checkpatch
2024-07-24 6:43 ` |FAILURE| " 0-day Robot
2024-07-24 8:02 ` |PENDING| pw142675 [PATCH] net/gve: Fix TX/RX queue setup and stop f dpdklab
2024-07-24 8:05 ` dpdklab
2024-07-24 8:06 ` |SUCCESS| " dpdklab
2024-07-24 8:08 ` dpdklab
2024-07-24 8:10 ` dpdklab
2024-07-24 8:10 ` dpdklab
2024-07-24 8:21 ` dpdklab
2024-07-24 8:24 ` dpdklab
2024-07-24 8:25 ` |PENDING| " dpdklab
2024-07-24 8:27 ` dpdklab
2024-07-24 8:28 ` |SUCCESS| " dpdklab
2024-07-24 8:32 ` |PENDING| " dpdklab
2024-07-24 8:32 ` dpdklab
2024-07-24 8:33 ` dpdklab
2024-07-24 8:37 ` dpdklab
2024-07-24 8:38 ` dpdklab
2024-07-24 8:39 ` dpdklab
2024-07-24 8:40 ` dpdklab [this message]
2024-07-24 8:41 ` dpdklab
2024-07-24 8:45 ` dpdklab
2024-07-24 8:45 ` |SUCCESS| " dpdklab
2024-07-24 8:46 ` dpdklab
2024-07-24 8:53 ` dpdklab
2024-07-24 8:54 ` |PENDING| " dpdklab
2024-07-24 8:55 ` dpdklab
2024-07-24 8:57 ` |SUCCESS| " dpdklab
2024-07-24 8:57 ` |PENDING| " dpdklab
2024-07-24 9:07 ` dpdklab
2024-07-24 9:08 ` dpdklab
2024-07-24 9:10 ` |SUCCESS| " dpdklab
2024-07-24 9:16 ` dpdklab
2024-07-24 10:05 ` |FAILURE| " dpdklab
2024-07-24 10:06 ` dpdklab
2024-07-24 10:07 ` dpdklab
2024-07-24 10:08 ` dpdklab
2024-07-24 10:08 ` dpdklab
2024-07-24 10:09 ` dpdklab
2024-07-24 10:12 ` dpdklab
2024-07-24 10:15 ` dpdklab
2024-07-24 10:15 ` dpdklab
2024-07-24 10:16 ` dpdklab
2024-07-24 10:16 ` dpdklab
2024-07-24 10:18 ` dpdklab
2024-07-24 10:19 ` dpdklab
2024-07-24 10:21 ` dpdklab
2024-07-24 10:21 ` dpdklab
2024-07-24 10:21 ` dpdklab
2024-07-24 10:22 ` dpdklab
2024-07-24 10:23 ` dpdklab
2024-07-24 10:23 ` dpdklab
2024-07-24 10:23 ` dpdklab
2024-07-24 10:23 ` dpdklab
2024-07-24 10:24 ` dpdklab
2024-07-24 10:24 ` dpdklab
2024-07-24 10:25 ` dpdklab
2024-07-24 10:25 ` dpdklab
2024-07-24 10:26 ` dpdklab
2024-07-24 10:27 ` dpdklab
2024-07-24 10:27 ` dpdklab
2024-07-24 10:31 ` dpdklab
2024-07-24 10:32 ` dpdklab
2024-07-24 10:35 ` dpdklab
2024-07-24 10:35 ` dpdklab
2024-07-24 10:36 ` dpdklab
2024-07-24 10:36 ` dpdklab
2024-07-24 10:36 ` dpdklab
2024-07-24 10:40 ` dpdklab
2024-07-24 10:43 ` dpdklab
2024-07-24 10:44 ` dpdklab
2024-07-24 10:45 ` dpdklab
2024-07-24 10:45 ` dpdklab
2024-07-24 10:45 ` dpdklab
2024-07-24 10:47 ` dpdklab
2024-07-24 10:47 ` dpdklab
2024-07-24 10:49 ` dpdklab
2024-07-24 10:50 ` dpdklab
2024-07-24 10:50 ` dpdklab
2024-07-24 10:50 ` dpdklab
2024-07-24 10:50 ` dpdklab
2024-07-24 10:51 ` dpdklab
2024-07-24 10:52 ` dpdklab
2024-07-24 10:54 ` dpdklab
2024-07-24 10:54 ` dpdklab
2024-07-24 10:56 ` dpdklab
2024-07-24 10:56 ` dpdklab
2024-07-24 10:57 ` dpdklab
2024-07-24 11:00 ` dpdklab
2024-07-24 11:00 ` dpdklab
2024-07-24 11:00 ` dpdklab
2024-07-24 11:00 ` dpdklab
2024-07-24 11:02 ` dpdklab
2024-07-24 11:02 ` dpdklab
2024-07-24 11:03 ` dpdklab
2024-07-24 11:03 ` dpdklab
2024-07-24 11:03 ` dpdklab
2024-07-24 11:04 ` dpdklab
2024-07-24 11:04 ` dpdklab
2024-07-24 11:06 ` dpdklab
2024-07-24 11:08 ` dpdklab
2024-07-24 11:24 ` |WARNING| " dpdklab
2024-07-25 16:33 ` 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=66a0bdf2.170a0220.26dcac.5b52SMTPIN_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).