From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142183 [PATCH] [v2] vhost: fix crash caused by accessing
Date: Sun, 07 Jul 2024 19:48:56 -0700 (PDT) [thread overview]
Message-ID: <668b5398.050a0220.784b8.002eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <TYAP286MB0649F57394FD92719A1F99D8D8DA2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/142183
_Performance Testing PASS_
Submitter: Gongming Chen <chengongming1900@outlook.com>
Date: Monday, July 08 2024 02:17:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:9cbdb606e5d04de04be3d9f70f0e76551e8c9a36
142183 --> performance testing pass
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
Target: Unknown
Fail/Total: 0/3
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -1.7% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: Unknown
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.7% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30445/
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-08 2:48 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <TYAP286MB0649F57394FD92719A1F99D8D8DA2@TYAP286MB0649.JPNP286.PROD.OUTLOOK.COM>
2024-07-08 1:51 ` |SUCCESS| pw142183 [PATCH v2] vhost: fix crash caused by accessing a freed vsocket qemudev
2024-07-08 1:56 ` qemudev
2024-07-08 2:18 ` |WARNING| " checkpatch
2024-07-08 2:45 ` |SUCCESS| pw142183 [PATCH] [v2] vhost: fix crash caused by accessing dpdklab
2024-07-08 2:47 ` dpdklab
2024-07-08 2:48 ` dpdklab [this message]
2024-07-08 2:49 ` dpdklab
2024-07-08 2:52 ` dpdklab
2024-07-08 2:54 ` dpdklab
2024-07-08 2:55 ` dpdklab
2024-07-08 2:55 ` |PENDING| " dpdklab
2024-07-08 2:55 ` dpdklab
2024-07-08 2:56 ` dpdklab
2024-07-08 2:56 ` |SUCCESS| " dpdklab
2024-07-08 2:58 ` |PENDING| " dpdklab
2024-07-08 2:59 ` dpdklab
2024-07-08 3:00 ` dpdklab
2024-07-08 3:03 ` |FAILURE| pw142183 [PATCH v2] vhost: fix crash caused by accessing a freed vsocket 0-day Robot
2024-07-08 3:03 ` |PENDING| pw142183 [PATCH] [v2] vhost: fix crash caused by accessing dpdklab
2024-07-08 3:05 ` |SUCCESS| " dpdklab
2024-07-08 3:07 ` |PENDING| " dpdklab
2024-07-08 3:08 ` dpdklab
2024-07-08 3:09 ` dpdklab
2024-07-08 3:09 ` dpdklab
2024-07-08 3:10 ` dpdklab
2024-07-08 3:10 ` dpdklab
2024-07-08 3:13 ` dpdklab
2024-07-08 3:13 ` |SUCCESS| " dpdklab
2024-07-08 3:13 ` |PENDING| " dpdklab
2024-07-08 3:14 ` dpdklab
2024-07-08 3:14 ` dpdklab
2024-07-08 3:15 ` dpdklab
2024-07-08 3:16 ` dpdklab
2024-07-08 3:18 ` |FAILURE| " dpdklab
2024-07-08 3:19 ` dpdklab
2024-07-08 3:19 ` |PENDING| " dpdklab
2024-07-08 3:19 ` dpdklab
2024-07-08 3:19 ` |FAILURE| " dpdklab
2024-07-08 3:19 ` |PENDING| " dpdklab
2024-07-08 3:20 ` dpdklab
2024-07-08 3:21 ` dpdklab
2024-07-08 3:21 ` dpdklab
2024-07-08 3:24 ` |SUCCESS| " dpdklab
2024-07-08 3:26 ` |FAILURE| " dpdklab
2024-07-08 3:26 ` |PENDING| " dpdklab
2024-07-08 3:27 ` |FAILURE| " dpdklab
2024-07-08 3:29 ` dpdklab
2024-07-08 3:30 ` |SUCCESS| " dpdklab
2024-07-08 3:30 ` |FAILURE| " dpdklab
2024-07-08 3:31 ` |PENDING| " dpdklab
2024-07-08 3:34 ` dpdklab
2024-07-08 3:36 ` dpdklab
2024-07-08 3:38 ` dpdklab
2024-07-08 3:39 ` |FAILURE| " dpdklab
2024-07-08 3:41 ` |PENDING| " dpdklab
2024-07-08 3:41 ` |FAILURE| " dpdklab
2024-07-08 3:41 ` |PENDING| " dpdklab
2024-07-08 3:42 ` |FAILURE| " dpdklab
2024-07-08 3:43 ` dpdklab
2024-07-08 3:43 ` dpdklab
2024-07-08 3:44 ` dpdklab
2024-07-08 3:44 ` dpdklab
2024-07-08 3:44 ` |SUCCESS| " dpdklab
2024-07-08 3:45 ` |FAILURE| " dpdklab
2024-07-08 3:46 ` dpdklab
2024-07-08 3:47 ` dpdklab
2024-07-08 3:47 ` dpdklab
2024-07-08 3:48 ` dpdklab
2024-07-08 3:48 ` dpdklab
2024-07-08 3:50 ` dpdklab
2024-07-08 3:51 ` dpdklab
2024-07-08 3:51 ` dpdklab
2024-07-08 3:52 ` dpdklab
2024-07-08 3:53 ` dpdklab
2024-07-08 3:53 ` dpdklab
2024-07-08 3:55 ` dpdklab
2024-07-08 3:57 ` dpdklab
2024-07-08 3:57 ` dpdklab
2024-07-08 3:57 ` dpdklab
2024-07-08 3:57 ` dpdklab
2024-07-08 3:58 ` dpdklab
2024-07-08 4:01 ` |SUCCESS| " dpdklab
2024-07-08 4:27 ` |FAILURE| " dpdklab
2024-07-09 11:02 ` |SUCCESS| " dpdklab
2024-07-09 11:15 ` dpdklab
2024-07-14 0:04 ` dpdklab
2024-07-14 11:03 ` dpdklab
2024-07-14 17:34 ` dpdklab
2024-07-15 10:27 ` dpdklab
2024-07-15 10:31 ` 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=668b5398.050a0220.784b8.002eSMTPIN_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).