From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129319 [PATCH] MAINTAINERS: remove one maintainer from p
Date: Sat, 08 Jul 2023 04:10:26 -0700 (PDT) [thread overview]
Message-ID: <64a94422.c80a0220.3df65.65ffSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/129319
_Performance Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, July 05 2023 23:00:25
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a64a4564705d18d20d20cfa16c79e795b7bf0f1e
129319 --> 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.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.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 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26986/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-07-08 11:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 11:10 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-14 17:22 dpdklab
2023-07-14 17:22 dpdklab
2023-07-13 7:46 dpdklab
2023-07-13 7:41 dpdklab
2023-07-13 7:37 dpdklab
2023-07-12 18:44 dpdklab
2023-07-12 18:44 dpdklab
2023-07-12 17:42 dpdklab
2023-07-12 17:37 dpdklab
2023-07-12 17:29 dpdklab
2023-07-11 15:07 dpdklab
2023-07-08 10:50 dpdklab
2023-07-06 23:34 dpdklab
2023-07-06 15:07 dpdklab
2023-07-06 13:10 dpdklab
2023-07-06 12:31 dpdklab
2023-07-06 7:18 dpdklab
2023-07-06 7:11 dpdklab
2023-07-06 7:09 dpdklab
2023-07-06 7:06 dpdklab
2023-07-06 7:05 dpdklab
2023-07-06 7:03 dpdklab
2023-07-06 7:02 dpdklab
2023-07-06 6:58 dpdklab
2023-07-06 6:58 dpdklab
2023-07-06 6:52 dpdklab
2023-07-06 5:46 dpdklab
2023-07-06 5:34 dpdklab
2023-07-06 5:33 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=64a94422.c80a0220.3df65.65ffSMTPIN_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).