From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142402 [PATCH] ethdev: fix GENEVE option item conversion
Date: Tue, 16 Jul 2024 07:05:21 -0700 (PDT) [thread overview]
Message-ID: <66967e21.050a0220.42217.0f5aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240715121316.3429593-1-michaelba@nvidia.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/142402
_Performance Testing PASS_
Submitter: Michael Baum <michaelba@nvidia.com>
Date: Monday, July 15 2024 12:13:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084
142402 --> 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
Fail/Total: 0/3
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | 1.0% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 1.1% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30515/
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-07-16 14:05 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240715121316.3429593-1-michaelba@nvidia.com>
2024-07-15 11:46 ` qemudev
2024-07-15 11:50 ` qemudev
2024-07-15 12:14 ` checkpatch
2024-07-15 13:03 ` 0-day Robot
2024-07-15 17:13 ` |PENDING| " dpdklab
2024-07-15 17:14 ` dpdklab
2024-07-15 17:15 ` dpdklab
2024-07-15 17:22 ` dpdklab
2024-07-15 17:30 ` dpdklab
2024-07-15 17:31 ` dpdklab
2024-07-15 17:35 ` dpdklab
2024-07-15 17:39 ` dpdklab
2024-07-15 17:43 ` dpdklab
2024-07-15 17:45 ` dpdklab
2024-07-15 17:45 ` dpdklab
2024-07-15 17:49 ` dpdklab
2024-07-15 17:50 ` dpdklab
2024-07-15 17:55 ` |SUCCESS| " dpdklab
2024-07-15 17:58 ` dpdklab
2024-07-15 18:00 ` |PENDING| " dpdklab
2024-07-15 18:03 ` |SUCCESS| " dpdklab
2024-07-15 18:07 ` |PENDING| " dpdklab
2024-07-15 18:14 ` |SUCCESS| " dpdklab
2024-07-15 18:16 ` dpdklab
2024-07-15 18:16 ` dpdklab
2024-07-15 18:22 ` |PENDING| " dpdklab
2024-07-15 18:28 ` |SUCCESS| " dpdklab
2024-07-15 18:29 ` |PENDING| " dpdklab
2024-07-15 18:55 ` |SUCCESS| " dpdklab
2024-07-15 18:58 ` |PENDING| " dpdklab
2024-07-15 19:07 ` dpdklab
2024-07-15 19:14 ` |SUCCESS| " dpdklab
2024-07-15 19:22 ` |PENDING| " dpdklab
2024-07-15 19:52 ` dpdklab
2024-07-15 20:42 ` dpdklab
2024-07-15 20:44 ` dpdklab
2024-07-15 20:52 ` |SUCCESS| " dpdklab
2024-07-15 21:27 ` dpdklab
2024-07-15 21:38 ` |PENDING| " dpdklab
2024-07-15 21:40 ` dpdklab
2024-07-15 21:41 ` dpdklab
2024-07-15 21:46 ` dpdklab
2024-07-15 21:48 ` dpdklab
2024-07-15 21:53 ` dpdklab
2024-07-15 21:55 ` dpdklab
2024-07-15 22:02 ` dpdklab
2024-07-15 22:04 ` dpdklab
2024-07-15 22:05 ` dpdklab
2024-07-15 22:09 ` dpdklab
2024-07-15 22:12 ` dpdklab
2024-07-15 22:13 ` dpdklab
2024-07-15 22:17 ` dpdklab
2024-07-15 22:18 ` dpdklab
2024-07-15 22:20 ` dpdklab
2024-07-15 22:21 ` dpdklab
2024-07-15 22:24 ` dpdklab
2024-07-15 22:25 ` dpdklab
2024-07-15 22:28 ` dpdklab
2024-07-15 22:29 ` dpdklab
2024-07-15 22:29 ` dpdklab
2024-07-15 22:30 ` dpdklab
2024-07-15 22:32 ` dpdklab
2024-07-15 22:34 ` dpdklab
2024-07-15 22:35 ` dpdklab
2024-07-15 22:35 ` dpdklab
2024-07-15 22:36 ` dpdklab
2024-07-15 22:37 ` dpdklab
2024-07-15 22:39 ` dpdklab
2024-07-15 23:22 ` dpdklab
2024-07-15 23:24 ` dpdklab
2024-07-15 23:28 ` dpdklab
2024-07-15 23:30 ` dpdklab
2024-07-15 23:34 ` dpdklab
2024-07-15 23:34 ` dpdklab
2024-07-15 23:35 ` dpdklab
2024-07-15 23:39 ` dpdklab
2024-07-15 23:40 ` dpdklab
2024-07-15 23:48 ` dpdklab
2024-07-15 23:50 ` dpdklab
2024-07-15 23:51 ` dpdklab
2024-07-15 23:52 ` dpdklab
2024-07-15 23:54 ` dpdklab
2024-07-15 23:59 ` dpdklab
2024-07-16 0:04 ` dpdklab
2024-07-16 0:08 ` dpdklab
2024-07-16 0:10 ` dpdklab
2024-07-16 0:14 ` dpdklab
2024-07-16 0:18 ` dpdklab
2024-07-16 0:21 ` dpdklab
2024-07-16 0:26 ` |SUCCESS| " dpdklab
2024-07-16 0:32 ` |PENDING| " dpdklab
2024-07-16 0:34 ` |SUCCESS| " dpdklab
2024-07-16 0:43 ` |PENDING| " dpdklab
2024-07-16 0:48 ` dpdklab
2024-07-16 0:55 ` |SUCCESS| " dpdklab
2024-07-16 0:56 ` |PENDING| " dpdklab
2024-07-16 0:57 ` dpdklab
2024-07-16 1:06 ` dpdklab
2024-07-16 1:13 ` dpdklab
2024-07-16 1:15 ` dpdklab
2024-07-16 1:16 ` dpdklab
2024-07-16 1:18 ` dpdklab
2024-07-16 1:30 ` dpdklab
2024-07-16 1:31 ` dpdklab
2024-07-16 1:38 ` dpdklab
2024-07-16 1:41 ` dpdklab
2024-07-16 1:43 ` dpdklab
2024-07-16 1:47 ` dpdklab
2024-07-16 1:58 ` |SUCCESS| " dpdklab
2024-07-16 10:59 ` dpdklab
2024-07-16 14:05 ` dpdklab [this message]
2024-07-16 14:10 ` dpdklab
2024-07-16 14:17 ` dpdklab
2024-07-16 14:24 ` dpdklab
2024-07-16 14:43 ` 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=66967e21.050a0220.42217.0f5aSMTPIN_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).