From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137521 [PATCH] net/netvsc: fix number Tx queues > Rx que
Date: Mon, 04 Mar 2024 00:25:56 -0800 (PST) [thread overview]
Message-ID: <65e58594.050a0220.97c1.b6faSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <PA4PR83MB0526128CDADC4DCC27FAF491975F2@PA4PR83MB0526.EURPRD83.prod.outlook.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/137521
_Performance Testing PASS_
Submitter: Alan Elder <alan.elder@microsoft.com>
Date: Thursday, February 29 2024 19:29:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f60df26faa3c90fc66d356e16347acd046971441
137521 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | 2.6% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29349/
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-04 8:25 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PA4PR83MB0526128CDADC4DCC27FAF491975F2@PA4PR83MB0526.EURPRD83.prod.outlook.com>
2024-02-29 19:07 ` |SUCCESS| pw137521 [PATCH] net/netvsc: fix number Tx queues > Rx queues qemudev
2024-02-29 19:11 ` qemudev
2024-02-29 19:29 ` checkpatch
2024-02-29 21:24 ` |FAILURE| " 0-day Robot
2024-02-29 23:22 ` |SUCCESS| pw137521 [PATCH] net/netvsc: fix number Tx queues > Rx que dpdklab
2024-02-29 23:31 ` dpdklab
2024-02-29 23:40 ` dpdklab
2024-02-29 23:40 ` dpdklab
2024-02-29 23:42 ` dpdklab
2024-02-29 23:44 ` dpdklab
2024-02-29 23:48 ` dpdklab
2024-02-29 23:48 ` dpdklab
2024-02-29 23:49 ` dpdklab
2024-02-29 23:49 ` dpdklab
2024-02-29 23:50 ` dpdklab
2024-02-29 23:58 ` dpdklab
2024-02-29 23:58 ` dpdklab
2024-03-01 0:00 ` dpdklab
2024-03-01 0:00 ` dpdklab
2024-03-01 0:05 ` dpdklab
2024-03-01 0:05 ` dpdklab
2024-03-01 0:14 ` dpdklab
2024-03-01 3:45 ` |FAILURE| " dpdklab
2024-03-01 3:45 ` dpdklab
2024-03-01 3:46 ` dpdklab
2024-03-01 3:46 ` dpdklab
2024-03-01 3:46 ` dpdklab
2024-03-01 3:46 ` dpdklab
2024-03-01 3:46 ` dpdklab
2024-03-01 3:47 ` dpdklab
2024-03-01 3:48 ` dpdklab
2024-03-01 3:49 ` dpdklab
2024-03-01 3:50 ` dpdklab
2024-03-01 3:51 ` dpdklab
2024-03-01 3:53 ` dpdklab
2024-03-01 3:53 ` dpdklab
2024-03-01 3:53 ` dpdklab
2024-03-01 3:54 ` dpdklab
2024-03-01 3:54 ` dpdklab
2024-03-01 3:54 ` dpdklab
2024-03-01 3:55 ` dpdklab
2024-03-01 3:55 ` dpdklab
2024-03-01 3:55 ` dpdklab
2024-03-01 3:55 ` dpdklab
2024-03-01 3:55 ` dpdklab
2024-03-01 3:58 ` dpdklab
2024-03-01 3:58 ` dpdklab
2024-03-01 3:58 ` dpdklab
2024-03-01 3:58 ` dpdklab
2024-03-01 3:59 ` dpdklab
2024-03-01 4:00 ` dpdklab
2024-03-01 4:06 ` dpdklab
2024-03-01 4:07 ` dpdklab
2024-03-01 4:08 ` dpdklab
2024-03-01 4:18 ` dpdklab
2024-03-01 4:19 ` dpdklab
2024-03-01 4:21 ` dpdklab
2024-03-01 4:21 ` dpdklab
2024-03-01 4:22 ` dpdklab
2024-03-01 4:32 ` dpdklab
2024-03-01 4:33 ` dpdklab
2024-03-01 4:35 ` dpdklab
2024-03-01 4:38 ` dpdklab
2024-03-01 4:38 ` dpdklab
2024-03-01 5:41 ` dpdklab
2024-03-01 9:02 ` dpdklab
2024-03-01 14:14 ` |SUCCESS| " dpdklab
2024-03-01 14:23 ` dpdklab
2024-03-01 14:25 ` dpdklab
2024-03-01 14:28 ` dpdklab
2024-03-02 14:09 ` |WARNING| " dpdklab
2024-03-04 8:25 ` dpdklab [this message]
2024-03-04 8:58 ` |SUCCESS| " dpdklab
2024-03-04 9:39 ` |WARNING| " 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=65e58594.050a0220.97c1.b6faSMTPIN_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).