From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw145594 [PATCH] [v3] crypto/ipsec_mb: bump minimum IPsec
Date: Thu, 10 Oct 2024 14:23:54 -0700 (PDT) [thread overview]
Message-ID: <670845ea.170a0220.26ad9c.10caSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241010101313.3933073-1-brian.dooley@intel.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/145594
_Performance Testing PASS_
Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Thursday, October 10 2024 10:13:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2a440e9a06652e77aa2d6f51358ac3b879779676
145594 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#187053
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
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | 0.5% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.7% |
+------------+---------+----------+-------------+------------------------------+
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 | -0.6% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -1.8% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31397/
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-10 21:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241010101313.3933073-1-brian.dooley@intel.com>
2024-10-10 9:57 ` |SUCCESS| pw145594 [PATCH v3] crypto/ipsec_mb: bump minimum IPsec MB version qemudev
2024-10-10 10:01 ` qemudev
2024-10-10 10:14 ` checkpatch
2024-10-10 20:29 ` |SUCCESS| pw145594 [PATCH] [v3] crypto/ipsec_mb: bump minimum IPsec dpdklab
2024-10-10 20:29 ` dpdklab
2024-10-10 20:40 ` dpdklab
2024-10-10 20:43 ` dpdklab
2024-10-10 20:47 ` dpdklab
2024-10-10 20:52 ` dpdklab
2024-10-10 20:53 ` dpdklab
2024-10-10 20:53 ` dpdklab
2024-10-10 21:03 ` |PENDING| " dpdklab
2024-10-10 21:14 ` |SUCCESS| " dpdklab
2024-10-10 21:23 ` |PENDING| " dpdklab
2024-10-10 21:23 ` dpdklab [this message]
2024-10-10 21:58 ` |SUCCESS| " dpdklab
2024-10-10 22:10 ` |PENDING| " 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=670845ea.170a0220.26ad9c.10caSMTPIN_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).