From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141175-141181 [PATCH] [7/7] test/security: use single se
Date: Mon, 17 Jun 2024 00:34:27 -0700 (PDT) [thread overview]
Message-ID: <666fe703.170a0220.5f414.6dc8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240617055841.2359729-8-asasidharan@marvell.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/141181
_Performance Testing PASS_
Submitter: Aakash Sasidharan <asasidharan@marvell.com>
Date: Monday, June 17 2024 05:58:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6909b48776badc05542a410ebd34bcfec4c248bf
141175-141181 --> performance testing pass
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
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.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -1.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
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/30203/
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-17 7:34 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240617055841.2359729-8-asasidharan@marvell.com>
2024-06-17 5:34 ` |SUCCESS| pw141175-141181 [PATCH 7/7] test/security: use single session in data walkthrough test qemudev
2024-06-17 5:38 ` qemudev
2024-06-17 6:00 ` |SUCCESS| pw141181 " checkpatch
2024-06-17 6:45 ` |SUCCESS| pw141175-141181 [PATCH] [7/7] test/security: use single se dpdklab
2024-06-17 6:47 ` dpdklab
2024-06-17 6:47 ` dpdklab
2024-06-17 6:47 ` dpdklab
2024-06-17 6:48 ` dpdklab
2024-06-17 7:04 ` |SUCCESS| pw141181 [PATCH 7/7] test/security: use single session in data walkthrough test 0-day Robot
2024-06-17 7:06 ` |SUCCESS| pw141175-141181 [PATCH] [7/7] test/security: use single se dpdklab
2024-06-17 7:23 ` dpdklab
2024-06-17 7:24 ` dpdklab
2024-06-17 7:25 ` dpdklab
2024-06-17 7:27 ` dpdklab
2024-06-17 7:28 ` dpdklab
2024-06-17 7:30 ` dpdklab
2024-06-17 7:30 ` dpdklab
2024-06-17 7:31 ` dpdklab
2024-06-17 7:31 ` dpdklab
2024-06-17 7:32 ` dpdklab
2024-06-17 7:32 ` dpdklab
2024-06-17 7:33 ` dpdklab
2024-06-17 7:33 ` dpdklab
2024-06-17 7:33 ` dpdklab
2024-06-17 7:34 ` dpdklab
2024-06-17 7:34 ` dpdklab [this message]
2024-06-17 7:34 ` dpdklab
2024-06-17 7:34 ` dpdklab
2024-06-17 7:35 ` dpdklab
2024-06-17 7:35 ` dpdklab
2024-06-17 7:35 ` dpdklab
2024-06-17 7:36 ` dpdklab
2024-06-17 7:37 ` dpdklab
2024-06-17 7:38 ` dpdklab
2024-06-17 7:38 ` dpdklab
2024-06-17 7:38 ` dpdklab
2024-06-17 7:39 ` dpdklab
2024-06-17 7:39 ` dpdklab
2024-06-17 7:39 ` dpdklab
2024-06-17 7:40 ` dpdklab
2024-06-17 7:40 ` dpdklab
2024-06-17 7:41 ` dpdklab
2024-06-17 7:41 ` dpdklab
2024-06-17 7:42 ` dpdklab
2024-06-17 7:42 ` dpdklab
2024-06-17 7:42 ` dpdklab
2024-06-17 7:43 ` dpdklab
2024-06-17 7:43 ` dpdklab
2024-06-17 7:43 ` dpdklab
2024-06-17 7:43 ` dpdklab
2024-06-17 7:44 ` dpdklab
2024-06-17 7:44 ` dpdklab
2024-06-17 7:44 ` dpdklab
2024-06-17 7:45 ` dpdklab
2024-06-17 7:46 ` dpdklab
2024-06-17 7:46 ` dpdklab
2024-06-17 7:46 ` dpdklab
2024-06-17 7:47 ` dpdklab
2024-06-17 7:47 ` dpdklab
2024-06-17 7:48 ` dpdklab
2024-06-17 7:48 ` dpdklab
2024-06-17 7:50 ` dpdklab
2024-06-17 7:51 ` dpdklab
2024-06-17 7:52 ` dpdklab
2024-06-17 7:53 ` dpdklab
2024-06-17 7:53 ` dpdklab
2024-06-17 7:53 ` dpdklab
2024-06-17 7:54 ` dpdklab
2024-06-17 7:54 ` dpdklab
2024-06-17 7:54 ` dpdklab
2024-06-17 7:54 ` dpdklab
2024-06-17 7:54 ` dpdklab
2024-06-17 7:55 ` dpdklab
2024-06-17 7:55 ` dpdklab
2024-06-17 7:56 ` dpdklab
2024-06-17 7:56 ` dpdklab
2024-06-17 7:56 ` dpdklab
2024-06-17 7:57 ` dpdklab
2024-06-17 7:57 ` dpdklab
2024-06-17 7:57 ` dpdklab
2024-06-17 7:58 ` dpdklab
2024-06-17 7:58 ` dpdklab
2024-06-17 7:58 ` dpdklab
2024-06-17 7:59 ` dpdklab
2024-06-17 7:59 ` dpdklab
2024-06-17 8:00 ` dpdklab
2024-06-17 8:01 ` dpdklab
2024-06-17 8:01 ` dpdklab
2024-06-17 8:01 ` dpdklab
2024-06-17 8:02 ` dpdklab
2024-06-17 8:02 ` dpdklab
2024-06-17 8:03 ` dpdklab
2024-06-17 8:04 ` dpdklab
2024-06-17 8:05 ` dpdklab
2024-06-17 8:05 ` dpdklab
2024-06-17 8:06 ` dpdklab
2024-06-17 8:06 ` dpdklab
2024-06-17 8:08 ` dpdklab
2024-06-17 8:08 ` dpdklab
2024-06-17 8:09 ` dpdklab
2024-06-17 8:11 ` dpdklab
2024-06-17 8:12 ` dpdklab
2024-06-17 8:13 ` dpdklab
2024-06-17 8:15 ` dpdklab
2024-06-17 8:15 ` dpdklab
2024-06-17 8:16 ` dpdklab
2024-06-17 8:16 ` dpdklab
2024-06-17 8:18 ` dpdklab
2024-06-17 8:19 ` dpdklab
2024-06-17 8:23 ` dpdklab
2024-06-17 8:30 ` dpdklab
2024-06-17 8:35 ` dpdklab
2024-06-17 10:00 ` 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=666fe703.170a0220.5f414.6dc8SMTPIN_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).