From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw140927-140931 [PATCH] [v4,5/5] vhost: manage FD with epo
Date: Wed, 12 Jun 2024 18:14:38 -0700 (PDT) [thread overview]
Message-ID: <666a47fe.170a0220.efb84.deb4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240611133957.72032-6-maxime.coquelin@redhat.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/140931
_Performance Testing PASS_
Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Tuesday, June 11 2024 13:39:57
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6f80df8cb0f889203d7cd27766abcc6ebc720e33
140927-140931 --> performance testing pass
Test environment and result as below:
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.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
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.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | 0.9% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 1.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30165/
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-06-13 1:18 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240611133957.72032-6-maxime.coquelin@redhat.com>
2024-06-11 13:14 ` |SUCCESS| pw140927-140931 [PATCH v4 5/5] vhost: manage FD with epoll qemudev
2024-06-11 13:19 ` qemudev
2024-06-11 13:42 ` |SUCCESS| pw140931 " checkpatch
2024-06-11 14:44 ` 0-day Robot
2024-06-11 18:42 ` |SUCCESS| pw140927-140931 [PATCH] [v4,5/5] vhost: manage FD with epo dpdklab
2024-06-11 18:47 ` dpdklab
2024-06-11 18:50 ` dpdklab
2024-06-11 18:51 ` dpdklab
2024-06-11 18:54 ` dpdklab
2024-06-11 19:05 ` dpdklab
2024-06-13 1:10 ` dpdklab
2024-06-13 1:12 ` dpdklab
2024-06-13 1:12 ` |FAILURE| " dpdklab
2024-06-13 1:12 ` |SUCCESS| " dpdklab
2024-06-13 1:13 ` dpdklab
2024-06-13 1:13 ` dpdklab
2024-06-13 1:14 ` dpdklab
2024-06-13 1:14 ` |FAILURE| " dpdklab
2024-06-13 1:14 ` dpdklab [this message]
2024-06-13 1:15 ` dpdklab
2024-06-13 1:16 ` |SUCCESS| " dpdklab
2024-06-13 1:16 ` |FAILURE| " dpdklab
2024-06-13 1:16 ` |SUCCESS| " dpdklab
2024-06-13 1:16 ` dpdklab
2024-06-13 1:16 ` dpdklab
2024-06-13 1:17 ` dpdklab
2024-06-13 1:17 ` dpdklab
2024-06-13 1:18 ` dpdklab
2024-06-13 1:18 ` dpdklab
2024-06-13 1:19 ` dpdklab
2024-06-13 1:19 ` dpdklab
2024-06-13 1:19 ` |FAILURE| " dpdklab
2024-06-13 1:20 ` |SUCCESS| " dpdklab
2024-06-13 1:20 ` dpdklab
2024-06-13 1:20 ` |FAILURE| " dpdklab
2024-06-13 1:20 ` dpdklab
2024-06-13 1:20 ` dpdklab
2024-06-13 1:21 ` dpdklab
2024-06-13 1:21 ` |SUCCESS| " dpdklab
2024-06-13 1:21 ` |FAILURE| " dpdklab
2024-06-13 1:21 ` dpdklab
2024-06-13 1:21 ` |SUCCESS| " dpdklab
2024-06-13 1:21 ` |FAILURE| " dpdklab
2024-06-13 1:22 ` dpdklab
2024-06-13 1:22 ` dpdklab
2024-06-13 1:22 ` |SUCCESS| " dpdklab
2024-06-13 1:22 ` |FAILURE| " dpdklab
2024-06-13 1:22 ` dpdklab
2024-06-13 1:22 ` dpdklab
2024-06-13 1:22 ` dpdklab
2024-06-13 1:22 ` dpdklab
2024-06-13 1:23 ` |SUCCESS| " dpdklab
2024-06-13 1:23 ` |FAILURE| " dpdklab
2024-06-13 1:23 ` dpdklab
2024-06-13 1:23 ` dpdklab
2024-06-13 1:23 ` dpdklab
2024-06-13 1:23 ` |SUCCESS| " dpdklab
2024-06-13 1:23 ` |FAILURE| " dpdklab
2024-06-13 1:23 ` dpdklab
2024-06-13 1:23 ` dpdklab
2024-06-13 1:23 ` dpdklab
2024-06-13 1:23 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:24 ` dpdklab
2024-06-13 1:25 ` dpdklab
2024-06-13 1:25 ` dpdklab
2024-06-13 1:25 ` dpdklab
2024-06-13 1:25 ` dpdklab
2024-06-13 1:25 ` dpdklab
2024-06-13 1:25 ` dpdklab
2024-06-13 1:25 ` dpdklab
2024-06-13 1:25 ` dpdklab
2024-06-13 1:25 ` dpdklab
2024-06-13 1:26 ` dpdklab
2024-06-13 1:26 ` dpdklab
2024-06-13 1:26 ` dpdklab
2024-06-13 1:26 ` dpdklab
2024-06-13 1:26 ` dpdklab
2024-06-13 1:26 ` dpdklab
2024-06-13 1:26 ` dpdklab
2024-06-13 1:26 ` dpdklab
2024-06-13 1:26 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:27 ` dpdklab
2024-06-13 1:28 ` dpdklab
2024-06-13 1:28 ` dpdklab
2024-06-13 1:28 ` dpdklab
2024-06-13 1:28 ` dpdklab
2024-06-13 1:28 ` dpdklab
2024-06-13 1:28 ` |SUCCESS| " 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=666a47fe.170a0220.efb84.deb4SMTPIN_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).