From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw140758 [PATCH] [v2] event/dsw: support explicit release
Date: Wed, 05 Jun 2024 09:46:12 -0700 (PDT) [thread overview]
Message-ID: <66609654.050a0220.6680c.52b7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240605133820.369677-1-mattias.ronnblom@ericsson.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/140758
_Performance Testing PASS_
Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Wednesday, June 05 2024 13:38:20
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:229d27a82792fab339d78b9bec26a0f395674d43
140758 --> 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.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30116/
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-05 16:46 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240605133820.369677-1-mattias.ronnblom@ericsson.com>
2024-06-05 13:21 ` |SUCCESS| pw140758 [PATCH v2] event/dsw: support explicit release only mode qemudev
2024-06-05 13:25 ` qemudev
2024-06-05 13:48 ` checkpatch
2024-06-05 14:45 ` 0-day Robot
2024-06-05 16:46 ` dpdklab [this message]
2024-06-05 16:48 ` |SUCCESS| pw140758 [PATCH] [v2] event/dsw: support explicit release dpdklab
2024-06-05 16:53 ` dpdklab
2024-06-05 16:57 ` dpdklab
2024-06-05 17:01 ` dpdklab
2024-06-05 17:02 ` dpdklab
2024-06-05 17:03 ` dpdklab
2024-06-05 17:04 ` dpdklab
2024-06-05 17:09 ` dpdklab
2024-06-05 17:30 ` dpdklab
2024-06-05 17:31 ` dpdklab
2024-06-05 17:32 ` dpdklab
2024-06-05 17:38 ` dpdklab
2024-06-05 17:46 ` dpdklab
2024-06-05 17:52 ` dpdklab
2024-06-05 17:53 ` dpdklab
2024-06-05 17:53 ` dpdklab
2024-06-05 17:53 ` dpdklab
2024-06-05 17:54 ` dpdklab
2024-06-05 17:54 ` dpdklab
2024-06-05 17:54 ` dpdklab
2024-06-05 17:54 ` dpdklab
2024-06-05 18:04 ` dpdklab
2024-06-05 18:09 ` dpdklab
2024-06-05 18:13 ` dpdklab
2024-06-05 18:15 ` dpdklab
2024-06-05 18:15 ` dpdklab
2024-06-05 18:16 ` dpdklab
2024-06-05 18:16 ` dpdklab
2024-06-05 18:17 ` dpdklab
2024-06-05 18:19 ` dpdklab
2024-06-05 18:19 ` dpdklab
2024-06-05 18:20 ` dpdklab
2024-06-05 18:20 ` dpdklab
2024-06-05 18:20 ` dpdklab
2024-06-05 18:20 ` dpdklab
2024-06-05 18:20 ` dpdklab
2024-06-05 18:21 ` dpdklab
2024-06-05 18:21 ` dpdklab
2024-06-05 18:21 ` dpdklab
2024-06-05 18:22 ` dpdklab
2024-06-05 18:22 ` dpdklab
2024-06-05 18:22 ` dpdklab
2024-06-05 18:23 ` dpdklab
2024-06-05 18:23 ` dpdklab
2024-06-05 18:23 ` dpdklab
2024-06-05 18:24 ` dpdklab
2024-06-05 18:24 ` dpdklab
2024-06-05 18:25 ` dpdklab
2024-06-05 18:25 ` dpdklab
2024-06-05 18:26 ` dpdklab
2024-06-05 18:26 ` dpdklab
2024-06-05 18:26 ` dpdklab
2024-06-05 18:27 ` dpdklab
2024-06-05 18:36 ` |WARNING| " dpdklab
2024-06-05 18:36 ` |SUCCESS| " dpdklab
2024-06-05 18:37 ` dpdklab
2024-06-05 18:37 ` dpdklab
2024-06-05 18:37 ` dpdklab
2024-06-05 18:38 ` dpdklab
2024-06-05 18:38 ` |WARNING| " dpdklab
2024-06-05 18:38 ` |SUCCESS| " dpdklab
2024-06-05 18:39 ` dpdklab
2024-06-05 18:39 ` dpdklab
2024-06-05 18:40 ` |WARNING| " dpdklab
2024-06-05 18:40 ` |SUCCESS| " dpdklab
2024-06-05 18:40 ` dpdklab
2024-06-05 18:41 ` dpdklab
2024-06-05 18:42 ` dpdklab
2024-06-05 18:42 ` |WARNING| " dpdklab
2024-06-05 18:43 ` |SUCCESS| " dpdklab
2024-06-05 18:43 ` |WARNING| " dpdklab
2024-06-05 18:43 ` dpdklab
2024-06-05 18:44 ` dpdklab
2024-06-05 18:44 ` |SUCCESS| " dpdklab
2024-06-05 18:44 ` dpdklab
2024-06-05 18:44 ` dpdklab
2024-06-05 18:44 ` |WARNING| " dpdklab
2024-06-05 18:45 ` |SUCCESS| " dpdklab
2024-06-05 18:45 ` dpdklab
2024-06-05 18:46 ` dpdklab
2024-06-05 18:54 ` |WARNING| " dpdklab
2024-06-05 18:55 ` |SUCCESS| " dpdklab
2024-06-05 18:55 ` dpdklab
2024-06-05 18:55 ` |WARNING| " dpdklab
2024-06-05 18:57 ` dpdklab
2024-06-05 18:59 ` dpdklab
2024-06-05 19:04 ` |SUCCESS| " dpdklab
2024-06-05 19:06 ` |WARNING| " dpdklab
2024-06-05 19:18 ` dpdklab
2024-06-05 19:35 ` |SUCCESS| " dpdklab
2024-06-05 20:37 ` dpdklab
2024-06-05 21:24 ` dpdklab
2024-06-06 1:02 ` dpdklab
2024-06-06 2:50 ` dpdklab
2024-06-06 2:57 ` dpdklab
2024-06-06 3:21 ` 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=66609654.050a0220.6680c.52b7SMTPIN_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).