From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130088 [PATCH] build: deprecate enable_kmods option
Date: Thu, 10 Aug 2023 09:59:00 -0700 (PDT) [thread overview]
Message-ID: <64d51754.4a0a0220.e0177.92e7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/130088
_Performance Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Thursday, August 10 2023 13:18:09
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:70b6941e4e22d67bc10495d1638234a7e974f582
130088 --> 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.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27281/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-10 16:59 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 16:59 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 2:58 dpdklab
2023-08-14 2:48 dpdklab
2023-08-14 2:35 dpdklab
2023-08-14 2:35 dpdklab
2023-08-14 2:33 dpdklab
2023-08-14 2:31 dpdklab
2023-08-14 2:31 dpdklab
2023-08-14 2:30 dpdklab
2023-08-14 2:30 dpdklab
2023-08-14 2:29 dpdklab
2023-08-14 2:29 dpdklab
2023-08-13 22:54 dpdklab
2023-08-13 19:22 dpdklab
2023-08-11 7:19 dpdklab
2023-08-11 7:14 dpdklab
2023-08-11 6:32 dpdklab
2023-08-11 5:12 dpdklab
2023-08-11 4:10 dpdklab
2023-08-11 0:47 dpdklab
2023-08-10 23:11 dpdklab
2023-08-10 20:51 dpdklab
2023-08-10 20:30 dpdklab
2023-08-10 20:29 dpdklab
2023-08-10 20:20 dpdklab
2023-08-10 20:10 dpdklab
2023-08-10 20:07 dpdklab
2023-08-10 20:01 dpdklab
2023-08-10 20:01 dpdklab
2023-08-10 20:00 dpdklab
2023-08-10 20:00 dpdklab
2023-08-10 19:56 dpdklab
2023-08-10 19:53 dpdklab
2023-08-10 19:33 dpdklab
2023-08-10 19:30 dpdklab
2023-08-10 19:20 dpdklab
2023-08-10 19:14 dpdklab
2023-08-10 19:12 dpdklab
2023-08-10 18:58 dpdklab
2023-08-10 18:57 dpdklab
2023-08-10 18:43 dpdklab
2023-08-10 18:41 dpdklab
2023-08-10 18:41 dpdklab
2023-08-10 18:40 dpdklab
2023-08-10 18:39 dpdklab
2023-08-10 18:38 dpdklab
2023-08-10 18:38 dpdklab
2023-08-10 18:38 dpdklab
2023-08-10 18:37 dpdklab
2023-08-10 18:37 dpdklab
2023-08-10 18:36 dpdklab
2023-08-10 18:35 dpdklab
2023-08-10 18:21 dpdklab
2023-08-10 18:19 dpdklab
2023-08-10 18:14 dpdklab
2023-08-10 18:13 dpdklab
2023-08-10 18:11 dpdklab
2023-08-10 18:11 dpdklab
2023-08-10 18:11 dpdklab
2023-08-10 18:10 dpdklab
2023-08-10 18:08 dpdklab
2023-08-10 18:08 dpdklab
2023-08-10 18:07 dpdklab
2023-08-10 17:58 dpdklab
2023-08-10 16:57 dpdklab
2023-08-10 16:56 dpdklab
2023-08-10 16:54 dpdklab
[not found] <20230810131809.493973-1-bruce.richardson@intel.com>
2023-08-10 13:21 ` qemudev
2023-08-10 13:25 ` qemudev
2023-08-10 13:30 ` checkpatch
2023-08-10 16:19 ` 0-day Robot
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=64d51754.4a0a0220.e0177.92e7SMTPIN_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).