From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw146906-146908 [PATCH] [v7,3/3] app/test: add test sm2 C1
Date: Thu, 24 Oct 2024 06:34:28 -0700 (PDT) [thread overview]
Message-ID: <671a4ce4.d40a0220.a31d8.ef94SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241023081934.84997-4-arkadiuszx.kusztal@intel.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/146908
_Performance Testing PASS_
Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Wednesday, October 23 2024 08:19:34
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3ee7a3e0e0e0f5a81a4b102a834697bc488fb32f
146906-146908 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#190679
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 | 1.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -0.9% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.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/31621/
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-10-24 13:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241023081934.84997-4-arkadiuszx.kusztal@intel.com>
2024-10-23 9:03 ` |SUCCESS| pw146906-146908 [PATCH v7 3/3] app/test: add test sm2 C1/Kp test cases qemudev
2024-10-23 9:07 ` qemudev
2024-10-23 9:36 ` |SUCCESS| pw146908 " checkpatch
2024-10-23 10:27 ` 0-day Robot
2024-10-23 19:49 ` |SUCCESS| pw146906-146908 [PATCH] [v7,3/3] app/test: add test sm2 C1 dpdklab
2024-10-23 20:04 ` dpdklab
2024-10-23 20:41 ` dpdklab
2024-10-23 21:08 ` dpdklab
2024-10-23 21:27 ` dpdklab
2024-10-23 21:55 ` dpdklab
2024-10-23 22:24 ` dpdklab
2024-10-23 22:54 ` dpdklab
2024-10-24 0:51 ` dpdklab
2024-10-24 1:26 ` dpdklab
2024-10-24 6:36 ` |FAILURE| " dpdklab
2024-10-24 6:37 ` dpdklab
2024-10-24 6:48 ` |WARNING| " dpdklab
2024-10-24 7:32 ` |PENDING| " dpdklab
2024-10-24 7:39 ` dpdklab
2024-10-24 8:37 ` |FAILURE| " dpdklab
2024-10-24 9:44 ` |SUCCESS| " dpdklab
2024-10-24 11:06 ` dpdklab
2024-10-24 11:25 ` |FAILURE| " dpdklab
2024-10-24 11:53 ` dpdklab
2024-10-24 12:06 ` |PENDING| " dpdklab
2024-10-24 12:39 ` |SUCCESS| " dpdklab
2024-10-24 12:41 ` |FAILURE| " dpdklab
2024-10-24 12:42 ` dpdklab
2024-10-24 12:54 ` |SUCCESS| " dpdklab
2024-10-24 13:22 ` dpdklab
2024-10-24 13:34 ` dpdklab [this message]
2024-10-24 14:02 ` |FAILURE| " dpdklab
2024-10-24 14:11 ` |SUCCESS| " 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=671a4ce4.d40a0220.a31d8.ef94SMTPIN_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).