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| pw124306-124310 [PATCH] [v7, 5/5] ipsec: fix usage of RTE_LOGTYPE_USER1
Date: Tue, 21 Feb 2023 20:12:21 +0000 (UTC) [thread overview]
Message-ID: <20230221201221.3275D600AB@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/124310
_Performance Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, February 21 2023 18:55:53
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:9bd5ebca59c865aead7096358fb733e53a72007b
124306-124310 --> 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.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -2.5% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25501/
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-21 20:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 20:12 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-23 18:10 dpdklab
2023-02-22 4:29 dpdklab
2023-02-22 3:30 dpdklab
2023-02-22 3:30 dpdklab
2023-02-22 3:27 dpdklab
2023-02-22 3:24 dpdklab
2023-02-22 3:22 dpdklab
2023-02-22 3:17 dpdklab
2023-02-22 3:12 dpdklab
2023-02-22 3:09 dpdklab
2023-02-22 3:08 dpdklab
2023-02-22 3:00 dpdklab
2023-02-22 2:59 dpdklab
2023-02-22 2:57 dpdklab
2023-02-22 2:53 dpdklab
2023-02-22 2:44 dpdklab
2023-02-21 21:11 dpdklab
2023-02-21 21:04 dpdklab
2023-02-21 20:33 dpdklab
2023-02-21 20:26 dpdklab
2023-02-21 20:09 dpdklab
2023-02-21 20:00 dpdklab
2023-02-21 20:00 dpdklab
2023-02-21 19:58 dpdklab
2023-02-21 19:54 dpdklab
[not found] <20230221185553.513432-6-stephen@networkplumber.org>
2023-02-21 18:45 ` |SUCCESS| pw124306-124310 [PATCH v7 " qemudev
2023-02-21 18:49 ` 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=20230221201221.3275D600AB@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).