From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137480-137486 [PATCH] [7/7] vhost: improve FD manager lo
Date: Thu, 29 Feb 2024 05:54:41 -0800 (PST) [thread overview]
Message-ID: <65e08ca1.020a0220.f4e31.28f4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240229122502.2572343-8-maxime.coquelin@redhat.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/137486
_Performance Testing PASS_
Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Thursday, February 29 2024 12:25:02
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137480-137486 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-78-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04
Kernel: 5.15.0-78-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.5% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29333/
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-02-29 13:54 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229122502.2572343-8-maxime.coquelin@redhat.com>
2024-02-29 12:03 ` |SUCCESS| pw137480-137486 [PATCH 7/7] vhost: improve FD manager logging qemudev
2024-02-29 12:08 ` qemudev
2024-02-29 12:27 ` |SUCCESS| pw137486 " checkpatch
2024-02-29 13:25 ` 0-day Robot
2024-02-29 13:53 ` |SUCCESS| pw137480-137486 [PATCH] [7/7] vhost: improve FD manager lo dpdklab
2024-02-29 13:54 ` dpdklab [this message]
2024-02-29 13:55 ` dpdklab
2024-02-29 13:55 ` |FAILURE| " dpdklab
2024-02-29 13:56 ` |SUCCESS| " dpdklab
2024-02-29 13:59 ` |FAILURE| " dpdklab
2024-02-29 14:01 ` |SUCCESS| " dpdklab
2024-02-29 14:01 ` |FAILURE| " dpdklab
2024-02-29 14:11 ` |SUCCESS| " dpdklab
2024-02-29 14:20 ` dpdklab
2024-02-29 14:21 ` dpdklab
2024-02-29 14:21 ` dpdklab
2024-02-29 14:44 ` dpdklab
2024-02-29 14:44 ` dpdklab
2024-02-29 14:44 ` dpdklab
2024-02-29 14:45 ` dpdklab
2024-02-29 14:52 ` dpdklab
2024-02-29 14:53 ` dpdklab
2024-02-29 15:00 ` dpdklab
2024-02-29 15:00 ` dpdklab
2024-02-29 15:01 ` dpdklab
2024-02-29 15:01 ` dpdklab
2024-02-29 15:01 ` dpdklab
2024-02-29 15:02 ` dpdklab
2024-02-29 15:02 ` dpdklab
2024-02-29 15:02 ` dpdklab
2024-02-29 15:03 ` dpdklab
2024-02-29 15:06 ` dpdklab
2024-02-29 15:07 ` dpdklab
2024-02-29 15:07 ` dpdklab
2024-02-29 15:07 ` dpdklab
2024-02-29 15:07 ` dpdklab
2024-02-29 15:07 ` dpdklab
2024-02-29 15:08 ` dpdklab
2024-02-29 15:08 ` dpdklab
2024-02-29 15:08 ` dpdklab
2024-02-29 15:08 ` dpdklab
2024-02-29 15:09 ` dpdklab
2024-02-29 15:09 ` dpdklab
2024-02-29 15:16 ` dpdklab
2024-02-29 15:21 ` dpdklab
2024-02-29 15:26 ` dpdklab
2024-02-29 15:27 ` dpdklab
2024-02-29 15:27 ` dpdklab
2024-02-29 15:27 ` dpdklab
2024-02-29 15:29 ` dpdklab
2024-02-29 15:33 ` dpdklab
2024-02-29 15:33 ` dpdklab
2024-02-29 15:34 ` dpdklab
2024-02-29 15:34 ` dpdklab
2024-02-29 15:35 ` dpdklab
2024-02-29 15:35 ` dpdklab
2024-02-29 15:35 ` dpdklab
2024-02-29 15:36 ` dpdklab
2024-02-29 15:37 ` dpdklab
2024-02-29 15:37 ` dpdklab
2024-02-29 15:41 ` dpdklab
2024-02-29 15:41 ` dpdklab
2024-02-29 15:42 ` dpdklab
2024-02-29 15:42 ` dpdklab
2024-02-29 16:04 ` dpdklab
2024-02-29 16:41 ` dpdklab
2024-02-29 17:19 ` dpdklab
2024-03-01 6:16 ` dpdklab
2024-03-01 6:31 ` |FAILURE| " dpdklab
2024-03-01 6:35 ` |SUCCESS| " dpdklab
2024-03-01 6:38 ` dpdklab
2024-03-02 5:49 ` dpdklab
2024-03-02 23:49 ` dpdklab
2024-03-03 0:22 ` dpdklab
2024-03-03 0:55 ` 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=65e08ca1.020a0220.f4e31.28f4SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--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).