From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142686 [PATCH] [v1] net/ntnic: add missing SPDX tag
Date: Wed, 24 Jul 2024 14:54:34 -0700 (PDT) [thread overview]
Message-ID: <66a1781a.050a0220.188912.1670SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240724131445.510743-1-mko-plv@napatech.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/142686
_Performance Testing PASS_
Submitter: Mykola Kostenok <mko-plv@napatech.com>
Date: Wednesday, July 24 2024 13:14:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:82c47f005b9a0a1e3a649664b7713443d18abe43
142686 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#170505
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
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.9% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.2% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.8% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30606/
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-24 21:54 UTC|newest]
Thread overview: 127+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240724131445.510743-1-mko-plv@napatech.com>
2024-07-24 12:46 ` |SUCCESS| pw142686 [PATCH v1] " qemudev
2024-07-24 12:51 ` qemudev
2024-07-24 13:15 ` checkpatch
2024-07-24 14:03 ` 0-day Robot
2024-07-24 19:49 ` |SUCCESS| pw142686 [PATCH] [v1] " dpdklab
2024-07-24 19:56 ` dpdklab
2024-07-24 19:58 ` dpdklab
2024-07-24 20:00 ` dpdklab
2024-07-24 21:19 ` dpdklab
2024-07-24 21:23 ` dpdklab
2024-07-24 21:28 ` dpdklab
2024-07-24 21:28 ` |PENDING| " dpdklab
2024-07-24 21:30 ` dpdklab
2024-07-24 21:33 ` dpdklab
2024-07-24 21:38 ` |SUCCESS| " dpdklab
2024-07-24 21:41 ` |PENDING| " dpdklab
2024-07-24 21:47 ` |SUCCESS| " dpdklab
2024-07-24 21:49 ` dpdklab
2024-07-24 21:51 ` |PENDING| " dpdklab
2024-07-24 21:53 ` dpdklab
2024-07-24 21:53 ` |SUCCESS| " dpdklab
2024-07-24 21:54 ` dpdklab [this message]
2024-07-24 21:55 ` |PENDING| " dpdklab
2024-07-24 21:57 ` dpdklab
2024-07-24 22:00 ` dpdklab
2024-07-24 22:01 ` dpdklab
2024-07-24 22:03 ` dpdklab
2024-07-24 22:04 ` dpdklab
2024-07-24 22:06 ` dpdklab
2024-07-24 22:06 ` dpdklab
2024-07-24 22:09 ` dpdklab
2024-07-24 22:12 ` |SUCCESS| " dpdklab
2024-07-24 22:22 ` dpdklab
2024-07-24 22:52 ` dpdklab
2024-07-24 23:42 ` |PENDING| " dpdklab
2024-07-24 23:47 ` dpdklab
2024-07-25 0:33 ` dpdklab
2024-07-25 0:33 ` dpdklab
2024-07-25 0:35 ` |SUCCESS| " dpdklab
2024-07-25 0:36 ` |PENDING| " dpdklab
2024-07-25 0:36 ` dpdklab
2024-07-25 0:36 ` dpdklab
2024-07-25 0:41 ` dpdklab
2024-07-25 0:42 ` dpdklab
2024-07-25 0:47 ` dpdklab
2024-07-25 0:52 ` dpdklab
2024-07-25 0:55 ` dpdklab
2024-07-25 0:57 ` dpdklab
2024-07-25 1:02 ` dpdklab
2024-07-25 1:02 ` dpdklab
2024-07-25 1:04 ` dpdklab
2024-07-25 1:06 ` dpdklab
2024-07-25 1:06 ` dpdklab
2024-07-25 1:07 ` dpdklab
2024-07-25 1:08 ` dpdklab
2024-07-25 1:08 ` dpdklab
2024-07-25 1:10 ` dpdklab
2024-07-25 1:10 ` dpdklab
2024-07-25 1:11 ` dpdklab
2024-07-25 1:13 ` dpdklab
2024-07-25 1:15 ` dpdklab
2024-07-25 1:16 ` dpdklab
2024-07-25 1:16 ` dpdklab
2024-07-25 1:19 ` dpdklab
2024-07-25 1:20 ` dpdklab
2024-07-25 1:21 ` |SUCCESS| " dpdklab
2024-07-25 1:25 ` |PENDING| " dpdklab
2024-07-25 1:26 ` dpdklab
2024-07-25 1:26 ` dpdklab
2024-07-25 1:27 ` dpdklab
2024-07-25 1:28 ` dpdklab
2024-07-25 1:29 ` dpdklab
2024-07-25 1:29 ` dpdklab
2024-07-25 1:31 ` dpdklab
2024-07-25 1:32 ` dpdklab
2024-07-25 1:35 ` dpdklab
2024-07-25 1:36 ` dpdklab
2024-07-25 1:36 ` |SUCCESS| " dpdklab
2024-07-25 1:41 ` |PENDING| " dpdklab
2024-07-25 1:41 ` dpdklab
2024-07-25 1:42 ` dpdklab
2024-07-25 1:43 ` dpdklab
2024-07-25 1:43 ` dpdklab
2024-07-25 1:43 ` dpdklab
2024-07-25 1:44 ` dpdklab
2024-07-25 1:47 ` dpdklab
2024-07-25 1:50 ` dpdklab
2024-07-25 1:50 ` dpdklab
2024-07-25 1:51 ` dpdklab
2024-07-25 1:52 ` dpdklab
2024-07-25 1:52 ` dpdklab
2024-07-25 1:54 ` dpdklab
2024-07-25 1:55 ` dpdklab
2024-07-25 1:57 ` dpdklab
2024-07-25 1:57 ` dpdklab
2024-07-25 1:59 ` dpdklab
2024-07-25 2:00 ` dpdklab
2024-07-25 2:03 ` dpdklab
2024-07-25 2:07 ` dpdklab
2024-07-25 2:07 ` dpdklab
2024-07-25 2:07 ` dpdklab
2024-07-25 2:08 ` dpdklab
2024-07-25 2:09 ` dpdklab
2024-07-25 2:13 ` dpdklab
2024-07-25 2:16 ` dpdklab
2024-07-25 2:18 ` dpdklab
2024-07-25 2:22 ` |SUCCESS| " dpdklab
2024-07-25 2:23 ` dpdklab
2024-07-25 2:36 ` dpdklab
2024-07-25 2:46 ` |PENDING| " dpdklab
2024-07-25 2:47 ` dpdklab
2024-07-25 2:55 ` dpdklab
2024-07-25 3:09 ` dpdklab
2024-07-25 3:10 ` dpdklab
2024-07-25 3:18 ` |SUCCESS| " dpdklab
2024-07-25 4:02 ` dpdklab
2024-07-25 10:21 ` |SUCCESS| pw142686 [PATCH v1] " qemudev
2024-07-25 10:22 ` qemudev
2024-07-25 10:36 ` qemudev
2024-07-25 10:36 ` qemudev
2024-07-25 10:40 ` qemudev
2024-07-25 10:40 ` qemudev
2024-07-25 10:53 ` qemudev
2024-07-25 10:53 ` qemudev
2024-07-25 10:57 ` qemudev
2024-07-25 10:57 ` qemudev
2024-07-25 22:50 ` |SUCCESS| pw142686 [PATCH] [v1] " 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=66a1781a.050a0220.188912.1670SMTPIN_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).