From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138952 [PATCH] [v1] doc: update release notes for 24.03
Date: Thu, 28 Mar 2024 05:56:16 -0700 (PDT) [thread overview]
Message-ID: <660568f0.020a0220.94616.1bedSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240328120550.3573051-1-john.mcnamara@intel.com>
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/138952
_Performance Testing PASS_
Submitter: John McNamara <john.mcnamara@intel.com>
Date: Thursday, March 28 2024 12:05:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c29202f2f70abd22e3d74e0671ec9f6cb9e387ee
138952 --> 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-5 100000 Mbps
Target: x86_64-native-linuxapp-gcc
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.5% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 256 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
| 128 | 256 | 1 | 1 | -0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | -0.3% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29673/
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-03-28 12:56 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240328120550.3573051-1-john.mcnamara@intel.com>
2024-03-28 11:43 ` |SUCCESS| pw138952 [PATCH v1] " qemudev
2024-03-28 11:48 ` qemudev
2024-03-28 12:06 ` checkpatch
2024-03-28 12:47 ` |SUCCESS| pw138952 [PATCH] [v1] " dpdklab
2024-03-28 12:48 ` dpdklab
2024-03-28 12:48 ` dpdklab
2024-03-28 12:48 ` dpdklab
2024-03-28 12:49 ` dpdklab
2024-03-28 12:49 ` dpdklab
2024-03-28 12:49 ` dpdklab
2024-03-28 12:49 ` dpdklab
2024-03-28 12:49 ` dpdklab
2024-03-28 12:49 ` dpdklab
2024-03-28 12:50 ` dpdklab
2024-03-28 12:50 ` dpdklab
2024-03-28 12:50 ` dpdklab
2024-03-28 12:51 ` dpdklab
2024-03-28 12:51 ` dpdklab
2024-03-28 12:51 ` dpdklab
2024-03-28 12:51 ` dpdklab
2024-03-28 12:52 ` dpdklab
2024-03-28 12:52 ` dpdklab
2024-03-28 12:52 ` dpdklab
2024-03-28 12:52 ` dpdklab
2024-03-28 12:53 ` dpdklab
2024-03-28 12:54 ` dpdklab
2024-03-28 12:55 ` dpdklab
2024-03-28 12:55 ` dpdklab
2024-03-28 12:55 ` dpdklab
2024-03-28 12:56 ` dpdklab [this message]
2024-03-28 12:56 ` dpdklab
2024-03-28 12:57 ` dpdklab
2024-03-28 12:58 ` dpdklab
2024-03-28 12:58 ` dpdklab
2024-03-28 12:59 ` dpdklab
2024-03-28 12:59 ` dpdklab
2024-03-28 13:00 ` dpdklab
2024-03-28 13:00 ` dpdklab
2024-03-28 13:05 ` |SUCCESS| pw138952 [PATCH v1] " 0-day Robot
2024-03-28 13:06 ` |SUCCESS| pw138952 [PATCH] [v1] " dpdklab
2024-03-28 13:06 ` dpdklab
2024-03-28 13:06 ` dpdklab
2024-03-28 13:06 ` dpdklab
2024-03-28 13:07 ` dpdklab
2024-03-28 13:07 ` dpdklab
2024-03-28 13:07 ` dpdklab
2024-03-28 13:07 ` dpdklab
2024-03-28 13:08 ` dpdklab
2024-03-28 13:09 ` dpdklab
2024-03-28 13:09 ` dpdklab
2024-03-28 13:09 ` |WARNING| " dpdklab
2024-03-28 13:09 ` |SUCCESS| " dpdklab
2024-03-28 13:11 ` dpdklab
2024-03-28 13:11 ` dpdklab
2024-03-28 13:18 ` dpdklab
2024-03-28 13:20 ` dpdklab
2024-03-28 13:20 ` dpdklab
2024-03-28 13:20 ` dpdklab
2024-03-28 13:21 ` dpdklab
2024-03-28 13:22 ` dpdklab
2024-03-28 13:23 ` dpdklab
2024-03-28 13:28 ` dpdklab
2024-03-28 13:29 ` dpdklab
2024-03-28 13:30 ` dpdklab
2024-03-28 13:30 ` dpdklab
2024-03-28 13:30 ` dpdklab
2024-03-28 13:31 ` dpdklab
2024-03-28 13:31 ` dpdklab
2024-03-28 13:31 ` dpdklab
2024-03-28 13:32 ` dpdklab
2024-03-28 13:33 ` dpdklab
2024-03-28 13:36 ` dpdklab
2024-03-28 13:37 ` dpdklab
2024-03-28 13:38 ` dpdklab
2024-03-28 13:39 ` dpdklab
2024-03-28 13:39 ` dpdklab
2024-03-28 13:41 ` dpdklab
2024-03-28 13:42 ` dpdklab
2024-03-28 13:46 ` dpdklab
2024-03-28 13:52 ` dpdklab
2024-03-28 13:53 ` dpdklab
2024-03-28 13:54 ` dpdklab
2024-03-28 14:11 ` dpdklab
2024-04-02 14:54 ` dpdklab
2024-04-02 14:59 ` dpdklab
2024-04-02 15:02 ` dpdklab
2024-04-02 15:22 ` dpdklab
2024-04-02 15:26 ` 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=660568f0.020a0220.94616.1bedSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--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).