From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141594 [PATCH] [v2] app/graph: fix destination buffer to
Date: Mon, 24 Jun 2024 15:37:33 -0700 (PDT) [thread overview]
Message-ID: <6679f52d.050a0220.1fc6d.8166SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240624200114.1792214-1-mahmoudmatook.mm@gmail.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/141594
_Performance Testing PASS_
Submitter: Mahmoud Maatuq <mahmoudmatook.mm@gmail.com>
Date: Monday, June 24 2024 20:01:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4a44d97f0a52a76258c6a6cb6a713f4380a8ab1f
141594 --> 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.0% |
+------------+---------+----------+-------------+------------------------------+
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 | 1.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | 1.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.7% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30302/
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-24 22:37 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240624200114.1792214-1-mahmoudmatook.mm@gmail.com>
2024-06-24 19:35 ` |SUCCESS| pw141594 [PATCH v2] app/graph: fix destination buffer too small qemudev
2024-06-24 19:39 ` qemudev
2024-06-24 20:03 ` checkpatch
2024-06-24 21:04 ` |FAILURE| " 0-day Robot
2024-06-24 22:28 ` |SUCCESS| pw141594 [PATCH] [v2] app/graph: fix destination buffer to dpdklab
2024-06-24 22:35 ` dpdklab
2024-06-24 22:36 ` dpdklab
2024-06-24 22:37 ` dpdklab
2024-06-24 22:37 ` dpdklab
2024-06-24 22:37 ` dpdklab [this message]
2024-06-24 22:37 ` dpdklab
2024-06-24 22:39 ` dpdklab
2024-06-24 22:40 ` dpdklab
2024-06-24 22:40 ` dpdklab
2024-06-24 22:41 ` dpdklab
2024-06-24 22:41 ` dpdklab
2024-06-24 22:41 ` dpdklab
2024-06-24 22:41 ` dpdklab
2024-06-24 22:42 ` dpdklab
2024-06-24 23:00 ` dpdklab
2024-06-24 23:00 ` dpdklab
2024-06-24 23:01 ` dpdklab
2024-06-24 23:08 ` dpdklab
2024-06-24 23:09 ` dpdklab
2024-06-24 23:09 ` dpdklab
2024-06-24 23:14 ` dpdklab
2024-06-24 23:15 ` dpdklab
2024-06-24 23:15 ` dpdklab
2024-06-24 23:16 ` dpdklab
2024-06-24 23:16 ` dpdklab
2024-06-24 23:16 ` dpdklab
2024-06-24 23:18 ` dpdklab
2024-06-24 23:21 ` dpdklab
2024-06-24 23:22 ` dpdklab
2024-06-25 0:08 ` dpdklab
2024-06-25 0:28 ` |FAILURE| " dpdklab
2024-06-25 0:29 ` dpdklab
2024-06-25 0:30 ` dpdklab
2024-06-25 0:30 ` dpdklab
2024-06-25 0:31 ` dpdklab
2024-06-25 0:31 ` dpdklab
2024-06-25 0:32 ` dpdklab
2024-06-25 0:32 ` dpdklab
2024-06-25 0:33 ` dpdklab
2024-06-25 0:34 ` dpdklab
2024-06-25 0:34 ` dpdklab
2024-06-25 0:40 ` dpdklab
2024-06-25 0:41 ` dpdklab
2024-06-25 0:41 ` dpdklab
2024-06-25 0:41 ` dpdklab
2024-06-25 0:44 ` dpdklab
2024-06-25 0:45 ` dpdklab
2024-06-25 0:46 ` dpdklab
2024-06-25 0:47 ` dpdklab
2024-06-25 0:47 ` dpdklab
2024-06-25 0:58 ` dpdklab
2024-06-25 0:59 ` dpdklab
2024-06-25 1:00 ` dpdklab
2024-06-25 1:01 ` dpdklab
2024-06-25 1:01 ` dpdklab
2024-06-25 1:01 ` dpdklab
2024-06-25 1:02 ` dpdklab
2024-06-25 1:02 ` dpdklab
2024-06-25 1:02 ` dpdklab
2024-06-25 1:04 ` dpdklab
2024-06-25 1:05 ` dpdklab
2024-06-25 1:07 ` dpdklab
2024-06-25 1:08 ` dpdklab
2024-06-25 1:17 ` dpdklab
2024-06-25 1:20 ` dpdklab
2024-06-25 1:20 ` dpdklab
2024-06-25 1:21 ` dpdklab
2024-06-25 1:21 ` dpdklab
2024-06-25 1:22 ` dpdklab
2024-06-25 1:22 ` dpdklab
2024-06-25 1:23 ` dpdklab
2024-06-25 1:23 ` dpdklab
2024-06-25 1:24 ` dpdklab
2024-06-25 1:24 ` dpdklab
2024-06-25 1:25 ` dpdklab
2024-06-25 1:25 ` dpdklab
2024-06-25 1:26 ` dpdklab
2024-06-25 1:26 ` dpdklab
2024-06-25 1:26 ` dpdklab
2024-06-25 1:27 ` dpdklab
2024-06-25 1:29 ` dpdklab
2024-06-25 1:31 ` dpdklab
2024-06-25 1:31 ` dpdklab
2024-06-25 1:32 ` dpdklab
2024-06-25 1:33 ` dpdklab
2024-06-25 1:33 ` dpdklab
2024-06-25 1:34 ` dpdklab
2024-06-25 1:34 ` dpdklab
2024-06-25 1:39 ` dpdklab
2024-06-25 1:39 ` dpdklab
2024-06-25 1:40 ` dpdklab
2024-06-25 1:54 ` dpdklab
2024-06-25 2:00 ` dpdklab
2024-06-25 2:01 ` dpdklab
2024-06-25 2:03 ` dpdklab
2024-06-25 2:06 ` dpdklab
2024-06-25 2:15 ` dpdklab
2024-06-25 2:15 ` dpdklab
2024-06-25 2:16 ` dpdklab
2024-06-25 2:16 ` dpdklab
2024-06-25 2:17 ` dpdklab
2024-06-25 2:19 ` dpdklab
2024-06-25 2:20 ` dpdklab
2024-06-25 2:48 ` dpdklab
2024-06-25 3:32 ` dpdklab
2024-06-25 3:41 ` dpdklab
2024-06-25 3:48 ` dpdklab
2024-06-25 11:53 ` |WARNING| " 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=6679f52d.050a0220.1fc6d.8166SMTPIN_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).