From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw147759 [PATCH] Revert "eal/unix: fix thread creation"
Date: Thu, 31 Oct 2024 17:55:15 -0700 (PDT) [thread overview]
Message-ID: <672426f3.050a0220.27d1ce.6136SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241030190945.409721-1-luca.boccassi@gmail.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/147759
_Performance Testing PASS_
Submitter: Luca Boccassi <luca.boccassi@gmail.com>
Date: Wednesday, October 30 2024 19:08:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2a682d65f8dbe1e8be9cc2425095827e18c700e3
147759 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#193032
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
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 | 2.2% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31785/
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-11-01 0:55 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241030190945.409721-1-luca.boccassi@gmail.com>
2024-10-30 18:39 ` qemudev
2024-10-30 18:43 ` qemudev
2024-10-30 19:11 ` |WARNING| " checkpatch
2024-10-30 20:04 ` |SUCCESS| " 0-day Robot
2024-10-31 0:45 ` dpdklab
2024-10-31 0:59 ` dpdklab
2024-10-31 2:57 ` dpdklab
2024-10-31 3:07 ` dpdklab
2024-10-31 3:26 ` dpdklab
2024-10-31 3:34 ` dpdklab
2024-10-31 3:58 ` dpdklab
2024-10-31 4:34 ` dpdklab
2024-10-31 4:35 ` |PENDING| " dpdklab
2024-10-31 5:13 ` |SUCCESS| " dpdklab
2024-10-31 8:55 ` |PENDING| " dpdklab
2024-10-31 9:09 ` |SUCCESS| " dpdklab
2024-10-31 9:30 ` |PENDING| " dpdklab
2024-10-31 9:30 ` dpdklab
2024-10-31 9:39 ` |SUCCESS| " dpdklab
2024-10-31 10:04 ` |PENDING| " dpdklab
2024-10-31 10:11 ` |SUCCESS| " dpdklab
2024-10-31 10:26 ` dpdklab
2024-10-31 10:38 ` dpdklab
2024-10-31 10:51 ` |PENDING| " dpdklab
2024-10-31 11:57 ` |SUCCESS| " dpdklab
2024-10-31 14:54 ` |PENDING| " dpdklab
2024-10-31 15:00 ` |SUCCESS| " dpdklab
2024-10-31 16:00 ` dpdklab
2024-10-31 16:58 ` dpdklab
2024-10-31 20:12 ` dpdklab
2024-10-31 22:28 ` dpdklab
2024-10-31 22:42 ` dpdklab
2024-10-31 22:47 ` dpdklab
2024-10-31 22:47 ` dpdklab
2024-10-31 23:00 ` dpdklab
2024-10-31 23:00 ` dpdklab
2024-10-31 23:03 ` dpdklab
2024-10-31 23:03 ` dpdklab
2024-11-01 0:55 ` dpdklab [this message]
2024-11-01 1:31 ` dpdklab
2024-11-01 1:50 ` dpdklab
2024-11-01 2:25 ` 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=672426f3.050a0220.27d1ce.6136SMTPIN_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).