From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw123730-123734 [PATCH] [5/5] ipsec: fix usage of RTE_LOGTYPE_USER1
Date: Sun, 12 Feb 2023 16:56:36 +0000 (UTC) [thread overview]
Message-ID: <20230212165636.634C1600A6@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2549 bytes --]
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/123734
_Performance Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Sunday, February 12 2023 16:14:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:39d469a7eb4f157923be73aea0b0cc1015860ca7
123730-123734 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-39-generic
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.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.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -2.8% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
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 | 0.4% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25361/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-12 16:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 16:56 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-15 4:41 dpdklab
2023-02-14 8:52 dpdklab
2023-02-13 10:55 dpdklab
2023-02-13 10:55 dpdklab
2023-02-13 10:52 dpdklab
2023-02-13 10:50 dpdklab
2023-02-13 10:43 dpdklab
2023-02-13 10:27 dpdklab
2023-02-13 10:26 dpdklab
2023-02-13 10:25 dpdklab
2023-02-13 10:21 dpdklab
2023-02-13 10:17 dpdklab
2023-02-13 10:06 dpdklab
2023-02-13 10:04 dpdklab
2023-02-13 9:52 dpdklab
2023-02-12 23:18 dpdklab
2023-02-12 17:58 dpdklab
2023-02-12 17:02 dpdklab
2023-02-12 16:58 dpdklab
2023-02-12 16:55 dpdklab
2023-02-12 16:54 dpdklab
2023-02-12 16:52 dpdklab
2023-02-12 16:49 dpdklab
2023-02-12 16:47 dpdklab
2023-02-12 16:43 dpdklab
2023-02-12 16:42 dpdklab
2023-02-12 16:39 dpdklab
2023-02-12 16:37 dpdklab
[not found] <20230212161454.836493-6-stephen@networkplumber.org>
2023-02-12 16:04 ` |SUCCESS| pw123730-123734 [PATCH 5/5] " qemudev
2023-02-12 16:08 ` qemudev
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=20230212165636.634C1600A6@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).