From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133267 [PATCH] vhost: make experimental API's stable
Date: Tue, 24 Oct 2023 10:12:30 -0700 (PDT) [thread overview]
Message-ID: <6537fafe.050a0220.d475c.1be1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/133267
_Performance Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, October 24 2023 16:31:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2a0557d1ea21c3f63a212385348c97c414970e81
133267 --> 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.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28055/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-24 17:12 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 17:12 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-25 17:50 dpdklab
2023-10-24 18:35 dpdklab
2023-10-24 17:35 dpdklab
2023-10-24 17:32 dpdklab
2023-10-24 17:27 dpdklab
2023-10-24 17:26 dpdklab
2023-10-24 17:24 dpdklab
2023-10-24 17:24 dpdklab
2023-10-24 17:23 dpdklab
2023-10-24 17:23 dpdklab
2023-10-24 17:22 dpdklab
2023-10-24 17:21 dpdklab
2023-10-24 17:20 dpdklab
2023-10-24 17:20 dpdklab
2023-10-24 17:19 dpdklab
2023-10-24 17:19 dpdklab
2023-10-24 17:19 dpdklab
2023-10-24 17:19 dpdklab
2023-10-24 17:19 dpdklab
2023-10-24 17:18 dpdklab
2023-10-24 17:18 dpdklab
2023-10-24 17:18 dpdklab
2023-10-24 17:18 dpdklab
2023-10-24 17:18 dpdklab
2023-10-24 17:18 dpdklab
2023-10-24 17:17 dpdklab
2023-10-24 17:17 dpdklab
2023-10-24 17:16 dpdklab
2023-10-24 17:16 dpdklab
2023-10-24 17:15 dpdklab
2023-10-24 17:15 dpdklab
2023-10-24 17:15 dpdklab
2023-10-24 17:15 dpdklab
2023-10-24 17:14 dpdklab
2023-10-24 17:14 dpdklab
2023-10-24 17:14 dpdklab
2023-10-24 17:14 dpdklab
2023-10-24 17:13 dpdklab
2023-10-24 17:13 dpdklab
2023-10-24 17:13 dpdklab
2023-10-24 17:13 dpdklab
2023-10-24 17:13 dpdklab
2023-10-24 17:12 dpdklab
2023-10-24 17:12 dpdklab
2023-10-24 17:12 dpdklab
2023-10-24 17:12 dpdklab
2023-10-24 17:12 dpdklab
2023-10-24 17:11 dpdklab
2023-10-24 17:11 dpdklab
2023-10-24 17:11 dpdklab
2023-10-24 17:10 dpdklab
2023-10-24 17:10 dpdklab
2023-10-24 17:09 dpdklab
[not found] <20231024163123.12576-1-stephen@networkplumber.org>
2023-10-24 16:12 ` qemudev
2023-10-24 16:16 ` qemudev
2023-10-24 17:39 ` 0-day Robot
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=6537fafe.050a0220.d475c.1be1SMTPIN_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).