From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141226 [PATCH] config: fix warning for cross build with
Date: Mon, 17 Jun 2024 15:03:08 -0700 (PDT) [thread overview]
Message-ID: <6670b29c.050a0220.ca75d.4e43SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240617151458.1005103-1-david.marchand@redhat.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/141226
_Performance Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Monday, June 17 2024 15:14:58
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2a3b212fafaab648cf8abf771da427c991cd5de8
141226 --> 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.3% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30215/
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-17 22:03 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240617151458.1005103-1-david.marchand@redhat.com>
2024-06-17 14:47 ` |SUCCESS| pw141226 [PATCH] config: fix warning for cross build with meson >= 1.3.0 qemudev
2024-06-17 14:52 ` qemudev
2024-06-17 15:16 ` checkpatch
2024-06-17 16:06 ` 0-day Robot
2024-06-17 22:03 ` dpdklab [this message]
2024-06-17 22:03 ` |SUCCESS| pw141226 [PATCH] config: fix warning for cross build with dpdklab
2024-06-17 22:33 ` dpdklab
2024-06-17 22:38 ` dpdklab
2024-06-17 22:54 ` dpdklab
2024-06-17 22:55 ` dpdklab
2024-06-17 22:59 ` dpdklab
2024-06-17 23:00 ` dpdklab
2024-06-17 23:13 ` dpdklab
2024-06-17 23:20 ` dpdklab
2024-06-17 23:33 ` dpdklab
2024-06-17 23:33 ` dpdklab
2024-06-17 23:37 ` dpdklab
2024-06-17 23:50 ` dpdklab
2024-06-18 0:22 ` dpdklab
2024-06-18 0:23 ` dpdklab
2024-06-18 0:28 ` dpdklab
2024-06-18 0:28 ` dpdklab
2024-06-18 0:29 ` dpdklab
2024-06-18 0:30 ` dpdklab
2024-06-18 0:32 ` dpdklab
2024-06-18 0:32 ` dpdklab
2024-06-18 0:33 ` dpdklab
2024-06-18 0:33 ` dpdklab
2024-06-18 0:34 ` dpdklab
2024-06-18 0:36 ` dpdklab
2024-06-18 0:36 ` dpdklab
2024-06-18 0:39 ` dpdklab
2024-06-18 0:41 ` dpdklab
2024-06-18 0:51 ` dpdklab
2024-06-18 0:54 ` dpdklab
2024-06-18 0:55 ` dpdklab
2024-06-18 1:06 ` dpdklab
2024-06-18 1:07 ` dpdklab
2024-06-18 1:08 ` dpdklab
2024-06-18 1:19 ` dpdklab
2024-06-18 1:35 ` dpdklab
2024-06-18 1:36 ` dpdklab
2024-06-18 1:40 ` dpdklab
2024-06-18 2:04 ` dpdklab
2024-06-18 2:05 ` dpdklab
2024-06-18 2:13 ` dpdklab
2024-06-18 2:14 ` dpdklab
2024-06-18 2:17 ` dpdklab
2024-06-18 2:17 ` dpdklab
2024-06-18 2:18 ` dpdklab
2024-06-18 2:19 ` dpdklab
2024-06-18 2:20 ` dpdklab
2024-06-18 2:21 ` dpdklab
2024-06-18 2:22 ` dpdklab
2024-06-18 2:22 ` dpdklab
2024-06-18 2:23 ` dpdklab
2024-06-18 2:23 ` dpdklab
2024-06-18 2:24 ` dpdklab
2024-06-18 2:24 ` dpdklab
2024-06-18 2:26 ` dpdklab
2024-06-18 2:29 ` dpdklab
2024-06-18 2:29 ` dpdklab
2024-06-18 2:29 ` dpdklab
2024-06-18 2:30 ` dpdklab
2024-06-18 2:31 ` dpdklab
2024-06-18 2:31 ` dpdklab
2024-06-18 2:32 ` dpdklab
2024-06-18 2:40 ` dpdklab
2024-06-18 2:42 ` dpdklab
2024-06-18 2:54 ` dpdklab
2024-06-18 2:54 ` dpdklab
2024-06-18 2:55 ` dpdklab
2024-06-18 2:55 ` dpdklab
2024-06-18 2:59 ` dpdklab
2024-06-18 3:01 ` dpdklab
2024-06-18 3:04 ` dpdklab
2024-06-18 3:05 ` dpdklab
2024-06-18 3:07 ` dpdklab
2024-06-18 3:08 ` dpdklab
2024-06-18 3:08 ` dpdklab
2024-06-18 3:10 ` dpdklab
2024-06-18 3:11 ` dpdklab
2024-06-18 3:13 ` dpdklab
2024-06-18 3:14 ` dpdklab
2024-06-18 3:15 ` dpdklab
2024-06-18 3:15 ` dpdklab
2024-06-18 3:17 ` dpdklab
2024-06-18 3:17 ` dpdklab
2024-06-18 3:18 ` dpdklab
2024-06-18 3:18 ` dpdklab
2024-06-18 3:19 ` dpdklab
2024-06-18 3:19 ` dpdklab
2024-06-18 3:19 ` dpdklab
2024-06-18 3:20 ` dpdklab
2024-06-18 3:20 ` dpdklab
2024-06-18 3:20 ` dpdklab
2024-06-18 3:22 ` dpdklab
2024-06-18 3:22 ` dpdklab
2024-06-18 3:23 ` dpdklab
2024-06-18 3:24 ` dpdklab
2024-06-18 3:24 ` dpdklab
2024-06-18 3:26 ` dpdklab
2024-06-18 3:26 ` dpdklab
2024-06-18 3:26 ` dpdklab
2024-06-18 3:27 ` dpdklab
2024-06-18 3:27 ` dpdklab
2024-06-18 3:29 ` dpdklab
2024-06-18 3:29 ` dpdklab
2024-06-18 3:31 ` dpdklab
2024-06-18 3:40 ` dpdklab
2024-06-18 3:57 ` dpdklab
2024-06-18 4:24 ` dpdklab
2024-06-18 4:36 ` dpdklab
2024-06-18 4:44 ` dpdklab
2024-06-18 7:09 ` |WARNING| " 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=6670b29c.050a0220.ca75d.4e43SMTPIN_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).