From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138797-138810 [PATCH] [v7,14/14] examples/ipsec-secgw: f
Date: Mon, 01 Apr 2024 16:15:34 -0700 (PDT) [thread overview]
Message-ID: <660b4016.050a0220.982ad.af55SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240326125554.138840-15-sivaprasad.tummala@amd.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/138810
_Performance Testing PASS_
Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Tuesday, March 26 2024 12:55:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ded4d4765171b88470e59307f10625e942f22fca
138797-138810 --> 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: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | -0.9% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -1.8% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.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 | 2.8% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.5% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29656/
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-04-01 23:15 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240326125554.138840-15-sivaprasad.tummala@amd.com>
2024-03-26 12:35 ` |SUCCESS| pw138797-138810 [PATCH v7 14/14] examples/ipsec-secgw: fix port ID restriction qemudev
2024-03-26 12:40 ` qemudev
2024-03-26 12:58 ` |SUCCESS| pw138810 " checkpatch
2024-03-26 13:32 ` |SUCCESS| pw138797-138810 [PATCH] [v7,14/14] examples/ipsec-secgw: f dpdklab
2024-03-26 13:32 ` dpdklab
2024-03-26 13:32 ` dpdklab
2024-03-26 13:33 ` dpdklab
2024-03-26 13:33 ` dpdklab
2024-03-26 13:33 ` dpdklab
2024-03-26 13:33 ` dpdklab
2024-03-26 13:33 ` dpdklab
2024-03-26 13:34 ` dpdklab
2024-03-26 13:34 ` dpdklab
2024-03-26 13:34 ` dpdklab
2024-03-26 13:35 ` dpdklab
2024-03-26 13:35 ` dpdklab
2024-03-26 13:35 ` dpdklab
2024-03-26 13:35 ` dpdklab
2024-03-26 13:35 ` dpdklab
2024-03-26 13:36 ` dpdklab
2024-03-26 13:36 ` dpdklab
2024-03-26 13:36 ` dpdklab
2024-03-26 13:36 ` dpdklab
2024-03-26 13:37 ` dpdklab
2024-03-26 13:37 ` dpdklab
2024-03-26 13:37 ` dpdklab
2024-03-26 13:37 ` dpdklab
2024-03-26 13:37 ` dpdklab
2024-03-26 13:37 ` dpdklab
2024-03-26 13:37 ` dpdklab
2024-03-26 13:38 ` dpdklab
2024-03-26 13:38 ` dpdklab
2024-03-26 13:38 ` dpdklab
2024-03-26 13:38 ` dpdklab
2024-03-26 13:38 ` dpdklab
2024-03-26 13:38 ` dpdklab
2024-03-26 13:39 ` dpdklab
2024-03-26 13:39 ` dpdklab
2024-03-26 13:39 ` dpdklab
2024-03-26 13:39 ` dpdklab
2024-03-26 13:40 ` dpdklab
2024-03-26 13:41 ` dpdklab
2024-03-26 13:42 ` dpdklab
2024-03-26 13:42 ` dpdklab
2024-03-26 13:42 ` dpdklab
2024-03-26 13:42 ` dpdklab
2024-03-26 13:42 ` dpdklab
2024-03-26 13:44 ` dpdklab
2024-03-26 13:44 ` dpdklab
2024-03-26 13:45 ` dpdklab
2024-03-26 13:45 ` dpdklab
2024-03-26 13:45 ` dpdklab
2024-03-26 13:46 ` dpdklab
2024-03-26 13:47 ` dpdklab
2024-03-26 13:47 ` |FAILURE| " dpdklab
2024-03-26 13:47 ` |SUCCESS| " dpdklab
2024-03-26 13:49 ` dpdklab
2024-03-26 13:49 ` dpdklab
2024-03-26 13:51 ` |FAILURE| " dpdklab
2024-03-26 13:51 ` |SUCCESS| " dpdklab
2024-03-26 13:53 ` dpdklab
2024-03-26 13:55 ` |FAILURE| " dpdklab
2024-03-26 13:56 ` |SUCCESS| pw138810 [PATCH v7 14/14] examples/ipsec-secgw: fix port ID restriction 0-day Robot
2024-03-26 13:57 ` |FAILURE| pw138797-138810 [PATCH] [v7,14/14] examples/ipsec-secgw: f dpdklab
2024-03-26 13:58 ` |SUCCESS| " dpdklab
2024-03-26 13:58 ` |FAILURE| " dpdklab
2024-03-26 13:59 ` dpdklab
2024-03-26 14:00 ` dpdklab
2024-03-26 14:04 ` |SUCCESS| " dpdklab
2024-03-26 14:05 ` dpdklab
2024-03-26 14:07 ` dpdklab
2024-03-26 14:34 ` dpdklab
2024-03-26 14:54 ` dpdklab
2024-04-01 23:15 ` dpdklab [this message]
2024-04-01 23:19 ` dpdklab
2024-04-01 23:23 ` dpdklab
2024-04-01 23:42 ` dpdklab
2024-04-01 23:46 ` dpdklab
2024-04-25 13:01 ` |FAILURE| " dpdklab
2024-04-25 13:01 ` |SUCCESS| " dpdklab
2024-04-25 13:02 ` dpdklab
2024-04-25 13:04 ` dpdklab
2024-04-25 13:05 ` dpdklab
2024-04-25 13:08 ` dpdklab
2024-04-25 13:08 ` dpdklab
2024-04-25 13:10 ` dpdklab
2024-04-25 13:13 ` dpdklab
2024-04-25 13:13 ` dpdklab
2024-04-25 13:16 ` dpdklab
2024-04-25 13:18 ` dpdklab
2024-04-25 13:19 ` dpdklab
2024-04-25 13:23 ` dpdklab
2024-04-25 13:25 ` dpdklab
2024-04-25 13:27 ` dpdklab
2024-04-25 13:29 ` dpdklab
2024-04-25 13:32 ` |WARNING| " dpdklab
2024-04-25 14:03 ` |SUCCESS| " dpdklab
2024-04-25 14:05 ` dpdklab
2024-04-25 14:08 ` dpdklab
2024-04-25 14:10 ` dpdklab
2024-04-25 14:15 ` dpdklab
2024-04-25 14:17 ` dpdklab
2024-04-25 14:18 ` dpdklab
2024-04-25 14:22 ` dpdklab
2024-04-25 14:30 ` dpdklab
2024-04-25 14:44 ` dpdklab
2024-04-25 15:06 ` 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=660b4016.050a0220.982ad.af55SMTPIN_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).