From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133932 [PATCH] raw/cnxk_gpio: fix resource leak
Date: Tue, 07 Nov 2023 02:58:48 -0800 (PST) [thread overview]
Message-ID: <654a1868.050a0220.c0efb.bbb9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/133932
_Performance Testing PASS_
Submitter: Tomasz Duszynski <tduszynski@marvell.com>
Date: Tuesday, November 07 2023 09:59:46
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2bbad8f974e00552d106c27e1d157a31179ab5ec
133932 --> performance testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
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/28265/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-07 10:58 UTC|newest]
Thread overview: 112+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 10:58 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-08 13:28 dpdklab
2023-11-08 3:40 dpdklab
2023-11-08 0:02 dpdklab
2023-11-07 22:31 dpdklab
2023-11-07 22:02 dpdklab
2023-11-07 21:24 dpdklab
2023-11-07 20:33 dpdklab
2023-11-07 20:32 dpdklab
2023-11-07 20:31 dpdklab
2023-11-07 20:31 dpdklab
2023-11-07 20:29 dpdklab
2023-11-07 20:29 dpdklab
2023-11-07 20:20 dpdklab
2023-11-07 20:20 dpdklab
2023-11-07 20:15 dpdklab
2023-11-07 20:14 dpdklab
2023-11-07 20:14 dpdklab
2023-11-07 20:14 dpdklab
2023-11-07 20:13 dpdklab
2023-11-07 20:12 dpdklab
2023-11-07 20:12 dpdklab
2023-11-07 20:11 dpdklab
2023-11-07 20:10 dpdklab
2023-11-07 20:09 dpdklab
2023-11-07 20:07 dpdklab
2023-11-07 20:03 dpdklab
2023-11-07 20:00 dpdklab
2023-11-07 20:00 dpdklab
2023-11-07 20:00 dpdklab
2023-11-07 19:59 dpdklab
2023-11-07 19:59 dpdklab
2023-11-07 19:59 dpdklab
2023-11-07 19:59 dpdklab
2023-11-07 19:59 dpdklab
2023-11-07 19:58 dpdklab
2023-11-07 19:58 dpdklab
2023-11-07 19:58 dpdklab
2023-11-07 19:58 dpdklab
2023-11-07 19:58 dpdklab
2023-11-07 19:58 dpdklab
2023-11-07 19:58 dpdklab
2023-11-07 19:56 dpdklab
2023-11-07 19:54 dpdklab
2023-11-07 19:54 dpdklab
2023-11-07 19:54 dpdklab
2023-11-07 19:52 dpdklab
2023-11-07 19:44 dpdklab
2023-11-07 19:40 dpdklab
2023-11-07 18:38 dpdklab
2023-11-07 18:15 dpdklab
2023-11-07 18:15 dpdklab
2023-11-07 18:14 dpdklab
2023-11-07 18:14 dpdklab
2023-11-07 18:13 dpdklab
2023-11-07 18:12 dpdklab
2023-11-07 18:11 dpdklab
2023-11-07 18:10 dpdklab
2023-11-07 18:06 dpdklab
2023-11-07 18:06 dpdklab
2023-11-07 18:03 dpdklab
2023-11-07 18:03 dpdklab
2023-11-07 18:00 dpdklab
2023-11-07 17:59 dpdklab
2023-11-07 17:50 dpdklab
2023-11-07 17:42 dpdklab
2023-11-07 16:42 dpdklab
2023-11-07 15:54 dpdklab
2023-11-07 15:53 dpdklab
2023-11-07 15:53 dpdklab
2023-11-07 15:53 dpdklab
2023-11-07 15:52 dpdklab
2023-11-07 15:52 dpdklab
2023-11-07 15:52 dpdklab
2023-11-07 11:06 dpdklab
2023-11-07 11:06 dpdklab
2023-11-07 11:06 dpdklab
2023-11-07 11:06 dpdklab
2023-11-07 11:03 dpdklab
2023-11-07 11:03 dpdklab
2023-11-07 11:03 dpdklab
2023-11-07 11:03 dpdklab
2023-11-07 11:03 dpdklab
2023-11-07 11:03 dpdklab
2023-11-07 11:03 dpdklab
2023-11-07 11:03 dpdklab
2023-11-07 11:03 dpdklab
2023-11-07 11:03 dpdklab
2023-11-07 11:03 dpdklab
2023-11-07 11:03 dpdklab
2023-11-07 11:03 dpdklab
2023-11-07 11:01 dpdklab
2023-11-07 10:58 dpdklab
2023-11-07 10:58 dpdklab
2023-11-07 10:58 dpdklab
2023-11-07 10:58 dpdklab
2023-11-07 10:58 dpdklab
2023-11-07 10:58 dpdklab
2023-11-07 10:58 dpdklab
2023-11-07 10:58 dpdklab
2023-11-07 10:56 dpdklab
2023-11-07 10:55 dpdklab
2023-11-07 10:54 dpdklab
2023-11-07 10:49 dpdklab
2023-11-07 10:49 dpdklab
2023-11-07 10:49 dpdklab
2023-11-07 10:49 dpdklab
2023-11-07 10:49 dpdklab
[not found] <20231107095946.3227242-1-tduszynski@marvell.com>
2023-11-07 9:40 ` qemudev
2023-11-07 9:45 ` qemudev
2023-11-07 10:00 ` checkpatch
2023-11-07 11:19 ` 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=654a1868.050a0220.c0efb.bbb9SMTPIN_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).