From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124886-124888 [PATCH] [v2, 2/2] vhost: refactor to follow new naming convention
Date: Sat, 11 Mar 2023 02:58:02 +0000 (UTC) [thread overview]
Message-ID: <20230311025802.AD6FE6011D@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/124888
_Performance Testing PASS_
Submitter: Nobuhiro MIKI <nmiki@yahoo-corp.jp>
Date: Thursday, March 09 2023 05:16:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b15d75b2872efce397d827dac78692a919358302
124886-124888 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-39-generic
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Target: x86_64-native-linuxapp-gcc
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.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25655/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-11 2:58 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 2:58 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-13 0:25 dpdklab
2023-03-12 23:03 dpdklab
2023-03-12 12:28 dpdklab
2023-03-12 12:27 dpdklab
2023-03-12 12:25 dpdklab
2023-03-12 12:23 dpdklab
2023-03-12 12:19 dpdklab
2023-03-12 12:15 dpdklab
2023-03-12 12:10 dpdklab
2023-03-12 12:07 dpdklab
2023-03-12 12:03 dpdklab
2023-03-12 12:00 dpdklab
2023-03-12 11:51 dpdklab
2023-03-12 11:47 dpdklab
2023-03-12 11:41 dpdklab
2023-03-12 11:40 dpdklab
2023-03-12 11:26 dpdklab
2023-03-12 11:22 dpdklab
2023-03-12 11:05 dpdklab
2023-03-12 10:53 dpdklab
2023-03-12 10:51 dpdklab
2023-03-12 10:50 dpdklab
2023-03-12 10:48 dpdklab
2023-03-12 10:47 dpdklab
2023-03-12 10:44 dpdklab
2023-03-12 10:44 dpdklab
2023-03-12 10:42 dpdklab
2023-03-12 10:41 dpdklab
2023-03-12 10:29 dpdklab
2023-03-12 10:26 dpdklab
2023-03-11 23:35 dpdklab
2023-03-11 23:22 dpdklab
2023-03-11 23:20 dpdklab
2023-03-11 22:24 dpdklab
2023-03-11 4:17 dpdklab
2023-03-11 4:07 dpdklab
2023-03-11 4:05 dpdklab
2023-03-11 4:04 dpdklab
2023-03-11 3:51 dpdklab
2023-03-11 3:50 dpdklab
2023-03-11 3:44 dpdklab
2023-03-11 3:41 dpdklab
2023-03-11 3:37 dpdklab
2023-03-11 3:36 dpdklab
2023-03-11 3:34 dpdklab
2023-03-11 3:31 dpdklab
2023-03-11 3:28 dpdklab
2023-03-11 3:23 dpdklab
2023-03-11 3:22 dpdklab
2023-03-11 3:18 dpdklab
2023-03-11 3:17 dpdklab
2023-03-11 3:17 dpdklab
2023-03-11 3:15 dpdklab
2023-03-11 3:12 dpdklab
2023-03-11 3:07 dpdklab
2023-03-11 3:06 dpdklab
2023-03-11 3:03 dpdklab
2023-03-11 3:00 dpdklab
2023-03-11 2:58 dpdklab
2023-03-11 2:56 dpdklab
2023-03-11 2:46 dpdklab
[not found] <20230309051643.70171-3-nmiki@yahoo-corp.jp>
2023-03-09 5:05 ` |SUCCESS| pw124886-124888 [PATCH v2 " qemudev
2023-03-09 5:09 ` qemudev
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=20230311025802.AD6FE6011D@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).