From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141511 [PATCH] net/mlx5: fix HWS GRE OPTION item validat
Date: Mon, 24 Jun 2024 00:55:40 -0700 (PDT) [thread overview]
Message-ID: <6679267c.050a0220.7007a.baf1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240624051100.42212-1-getelson@nvidia.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/141511
_Performance Testing PASS_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Monday, June 24 2024 05:11:00
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c1cdfbcc339c2c951bff95854983a8773d9e5b8e
141511 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Target: Unknown
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30283/
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-24 8:10 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240624051100.42212-1-getelson@nvidia.com>
2024-06-24 4:45 ` |SUCCESS| pw141511 [PATCH] net/mlx5: fix HWS GRE OPTION item validation qemudev
2024-06-24 4:49 ` qemudev
2024-06-24 5:13 ` checkpatch
2024-06-24 6:04 ` 0-day Robot
2024-06-24 7:45 ` |SUCCESS| pw141511 [PATCH] net/mlx5: fix HWS GRE OPTION item validat dpdklab
2024-06-24 7:55 ` dpdklab [this message]
2024-06-24 7:57 ` dpdklab
2024-06-24 7:57 ` dpdklab
2024-06-24 7:58 ` dpdklab
2024-06-24 8:01 ` dpdklab
2024-06-24 8:02 ` dpdklab
2024-06-24 8:02 ` dpdklab
2024-06-24 8:04 ` dpdklab
2024-06-24 8:05 ` dpdklab
2024-06-24 8:30 ` dpdklab
2024-06-24 8:33 ` dpdklab
2024-06-24 8:35 ` dpdklab
2024-06-24 8:38 ` dpdklab
2024-06-24 8:40 ` dpdklab
2024-06-24 8:42 ` dpdklab
2024-06-24 8:43 ` dpdklab
2024-06-24 8:43 ` dpdklab
2024-06-24 8:46 ` dpdklab
2024-06-24 8:47 ` dpdklab
2024-06-24 8:49 ` dpdklab
2024-06-24 8:50 ` dpdklab
2024-06-24 8:51 ` dpdklab
2024-06-24 8:53 ` dpdklab
2024-06-24 8:55 ` dpdklab
2024-06-24 8:58 ` dpdklab
2024-06-24 9:00 ` dpdklab
2024-06-24 9:01 ` dpdklab
2024-06-24 9:01 ` dpdklab
2024-06-24 9:02 ` dpdklab
2024-06-24 9:03 ` dpdklab
2024-06-24 9:04 ` dpdklab
2024-06-24 9:05 ` dpdklab
2024-06-24 9:08 ` dpdklab
2024-06-24 9:09 ` dpdklab
2024-06-24 9:09 ` dpdklab
2024-06-24 9:10 ` dpdklab
2024-06-24 9:11 ` dpdklab
2024-06-24 9:13 ` dpdklab
2024-06-24 9:14 ` dpdklab
2024-06-24 9:15 ` dpdklab
2024-06-24 9:15 ` dpdklab
2024-06-24 9:16 ` dpdklab
2024-06-24 9:17 ` dpdklab
2024-06-24 9:18 ` dpdklab
2024-06-24 9:18 ` dpdklab
2024-06-24 9:18 ` dpdklab
2024-06-24 9:19 ` dpdklab
2024-06-24 9:20 ` dpdklab
2024-06-24 9:21 ` dpdklab
2024-06-24 9:21 ` dpdklab
2024-06-24 9:22 ` dpdklab
2024-06-24 9:22 ` dpdklab
2024-06-24 9:23 ` dpdklab
2024-06-24 9:24 ` dpdklab
2024-06-24 9:26 ` dpdklab
2024-06-24 9:26 ` dpdklab
2024-06-24 9:28 ` dpdklab
2024-06-24 9:31 ` dpdklab
2024-06-24 9:35 ` dpdklab
2024-06-24 9:35 ` dpdklab
2024-06-24 9:36 ` dpdklab
2024-06-24 9:36 ` dpdklab
2024-06-24 9:36 ` dpdklab
2024-06-24 9:36 ` dpdklab
2024-06-24 9:36 ` dpdklab
2024-06-24 9:37 ` dpdklab
2024-06-24 9:37 ` dpdklab
2024-06-24 9:37 ` dpdklab
2024-06-24 9:37 ` dpdklab
2024-06-24 9:38 ` dpdklab
2024-06-24 9:38 ` dpdklab
2024-06-24 9:38 ` dpdklab
2024-06-24 9:38 ` dpdklab
2024-06-24 9:39 ` dpdklab
2024-06-24 9:39 ` dpdklab
2024-06-24 9:39 ` dpdklab
2024-06-24 9:39 ` dpdklab
2024-06-24 9:39 ` dpdklab
2024-06-24 9:40 ` dpdklab
2024-06-24 9:41 ` dpdklab
2024-06-24 9:42 ` dpdklab
2024-06-24 9:49 ` dpdklab
2024-06-24 9:51 ` dpdklab
2024-06-24 9:51 ` dpdklab
2024-06-24 9:51 ` dpdklab
2024-06-24 9:52 ` dpdklab
2024-06-24 9:52 ` dpdklab
2024-06-24 9:52 ` dpdklab
2024-06-24 9:56 ` dpdklab
2024-06-24 9:57 ` dpdklab
2024-06-24 10:01 ` dpdklab
2024-06-24 10:02 ` dpdklab
2024-06-24 10:02 ` dpdklab
2024-06-24 10:02 ` dpdklab
2024-06-24 10:02 ` dpdklab
2024-06-24 10:02 ` dpdklab
2024-06-24 10:03 ` dpdklab
2024-06-24 10:03 ` dpdklab
2024-06-24 10:04 ` dpdklab
2024-06-24 10:05 ` dpdklab
2024-06-24 10:08 ` dpdklab
2024-06-24 10:15 ` dpdklab
2024-06-24 10:15 ` dpdklab
2024-06-24 10:18 ` dpdklab
2024-06-24 10:20 ` dpdklab
2024-06-24 10:31 ` dpdklab
2024-06-24 10:32 ` dpdklab
2024-06-24 10:34 ` dpdklab
2024-06-24 10:37 ` dpdklab
2024-06-24 10:48 ` 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=6679267c.050a0220.7007a.baf1SMTPIN_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).