From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141311 [PATCH] doc: update match with E-Switch manager d
Date: Wed, 19 Jun 2024 04:57:03 -0700 (PDT) [thread overview]
Message-ID: <6672c78f.170a0220.6c57.af30SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240619041907.2144649-1-suanmingm@nvidia.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/141311
_Performance Testing PASS_
Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Wednesday, June 19 2024 04:19:06
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c1cdfbcc339c2c951bff95854983a8773d9e5b8e
141311 --> performance testing pass
Test environment and result as below:
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
Target: Unknown
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.4% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -1.9% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: Unknown
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.4% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30239/
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-06-19 11:57 UTC|newest]
Thread overview: 112+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240619041907.2144649-1-suanmingm@nvidia.com>
2024-06-19 3:57 ` |SUCCESS| pw141311 [PATCH] doc: update match with E-Switch manager dependency qemudev
2024-06-19 4:01 ` qemudev
2024-06-19 4:20 ` checkpatch
2024-06-19 11:55 ` |SUCCESS| pw141311 [PATCH] doc: update match with E-Switch manager d dpdklab
2024-06-19 11:57 ` dpdklab [this message]
2024-06-19 11:59 ` dpdklab
2024-06-19 12:18 ` dpdklab
2024-06-19 12:19 ` dpdklab
2024-06-19 12:20 ` dpdklab
2024-06-19 12:21 ` dpdklab
2024-06-19 12:23 ` dpdklab
2024-06-19 12:24 ` dpdklab
2024-06-19 12:27 ` dpdklab
2024-06-19 12:27 ` dpdklab
2024-06-19 12:29 ` dpdklab
2024-06-19 12:35 ` dpdklab
2024-06-19 12:39 ` dpdklab
2024-06-19 12:39 ` dpdklab
2024-06-19 12:43 ` dpdklab
2024-06-19 12:47 ` dpdklab
2024-06-19 12:48 ` dpdklab
2024-06-19 12:48 ` dpdklab
2024-06-19 12:51 ` dpdklab
2024-06-19 12:52 ` dpdklab
2024-06-19 13:00 ` dpdklab
2024-06-19 13:33 ` dpdklab
2024-06-19 14:23 ` dpdklab
2024-06-19 14:25 ` dpdklab
2024-06-19 14:27 ` dpdklab
2024-06-19 14:32 ` dpdklab
2024-06-19 14:33 ` dpdklab
2024-06-19 14:34 ` dpdklab
2024-06-19 14:39 ` dpdklab
2024-06-19 14:49 ` dpdklab
2024-06-19 14:52 ` dpdklab
2024-06-19 15:02 ` dpdklab
2024-06-19 15:28 ` dpdklab
2024-06-19 15:29 ` dpdklab
2024-06-19 15:30 ` dpdklab
2024-06-19 15:31 ` dpdklab
2024-06-19 15:32 ` dpdklab
2024-06-19 16:11 ` dpdklab
2024-06-19 17:15 ` dpdklab
2024-06-19 17:17 ` dpdklab
2024-06-19 17:23 ` dpdklab
2024-06-19 17:26 ` dpdklab
2024-06-19 17:27 ` dpdklab
2024-06-19 17:28 ` dpdklab
2024-06-19 17:31 ` dpdklab
2024-06-19 17:33 ` dpdklab
2024-06-19 17:34 ` dpdklab
2024-06-19 17:36 ` dpdklab
2024-06-19 17:37 ` dpdklab
2024-06-19 17:37 ` dpdklab
2024-06-19 17:42 ` dpdklab
2024-06-19 17:43 ` dpdklab
2024-06-19 17:46 ` dpdklab
2024-06-19 17:46 ` dpdklab
2024-06-19 17:47 ` dpdklab
2024-06-19 17:48 ` dpdklab
2024-06-19 17:50 ` dpdklab
2024-06-19 18:12 ` dpdklab
2024-06-19 18:15 ` dpdklab
2024-06-19 18:22 ` dpdklab
2024-06-19 18:23 ` dpdklab
2024-06-19 18:24 ` dpdklab
2024-06-19 18:29 ` dpdklab
2024-06-19 18:31 ` dpdklab
2024-06-19 18:33 ` dpdklab
2024-06-19 18:33 ` dpdklab
2024-06-19 18:34 ` dpdklab
2024-06-19 18:34 ` dpdklab
2024-06-19 18:34 ` dpdklab
2024-06-19 18:38 ` dpdklab
2024-06-19 18:38 ` dpdklab
2024-06-19 18:39 ` dpdklab
2024-06-19 18:43 ` dpdklab
2024-06-19 18:44 ` dpdklab
2024-06-19 18:45 ` dpdklab
2024-06-19 18:46 ` dpdklab
2024-06-19 18:46 ` dpdklab
2024-06-19 18:46 ` dpdklab
2024-06-19 18:47 ` dpdklab
2024-06-19 18:50 ` dpdklab
2024-06-19 18:55 ` dpdklab
2024-06-19 19:02 ` dpdklab
2024-06-19 19:03 ` dpdklab
2024-06-19 19:04 ` dpdklab
2024-06-19 19:05 ` dpdklab
2024-06-19 19:07 ` dpdklab
2024-06-19 19:08 ` dpdklab
2024-06-19 19:08 ` dpdklab
2024-06-19 19:09 ` dpdklab
2024-06-19 19:12 ` dpdklab
2024-06-19 19:12 ` dpdklab
2024-06-19 19:13 ` dpdklab
2024-06-19 19:13 ` dpdklab
2024-06-19 19:13 ` dpdklab
2024-06-19 19:14 ` dpdklab
2024-06-19 19:14 ` dpdklab
2024-06-19 19:16 ` dpdklab
2024-06-19 19:20 ` dpdklab
2024-06-19 19:21 ` dpdklab
2024-06-19 19:21 ` dpdklab
2024-06-19 19:24 ` dpdklab
2024-06-19 19:27 ` dpdklab
2024-06-19 19:36 ` dpdklab
2024-06-19 20:42 ` dpdklab
2024-06-19 20:52 ` dpdklab
2024-06-19 23:00 ` dpdklab
2024-06-19 23:50 ` dpdklab
2024-06-21 17:28 ` 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=6672c78f.170a0220.6c57.af30SMTPIN_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).