automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141489 [PATCH] meson: use built-in 'modules' helper for
Date: Sun, 23 Jun 2024 14:34:06 -0700 (PDT)	[thread overview]
Message-ID: <667894ce.170a0220.beba4.729cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240623123032.35928-1-luca.boccassi@gmail.com>

Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/141489

_Performance Testing PASS_

Submitter: Luca Boccassi <luca.boccassi@gmail.com>
Date: Sunday, June 23 2024 12:30:23 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:4a44d97f0a52a76258c6a6cb6a713f4380a8ab1f

141489 --> 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.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 256        | 256     | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 512        | 256     | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30278/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-06-23 21:34 UTC|newest]

Thread overview: 115+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240623123032.35928-1-luca.boccassi@gmail.com>
2024-06-23 12:07 ` |SUCCESS| pw141489 [PATCH] meson: use built-in 'modules' helper for python dependencies qemudev
2024-06-23 12:11 ` qemudev
2024-06-23 12:32 ` checkpatch
2024-06-23 13:24 ` 0-day Robot
2024-06-23 21:33 ` |SUCCESS| pw141489 [PATCH] meson: use built-in 'modules' helper for dpdklab
2024-06-23 21:33 ` dpdklab
2024-06-23 21:34 ` dpdklab [this message]
2024-06-23 21:34 ` dpdklab
2024-06-23 21:56 ` dpdklab
2024-06-23 21:56 ` dpdklab
2024-06-23 21:57 ` dpdklab
2024-06-23 21:58 ` dpdklab
2024-06-23 21:59 ` dpdklab
2024-06-23 21:59 ` dpdklab
2024-06-23 21:59 ` dpdklab
2024-06-23 21:59 ` dpdklab
2024-06-23 22:12 ` dpdklab
2024-06-23 22:13 ` dpdklab
2024-06-23 22:13 ` dpdklab
2024-06-23 22:14 ` dpdklab
2024-06-23 22:14 ` dpdklab
2024-06-23 22:14 ` dpdklab
2024-06-23 22:15 ` dpdklab
2024-06-23 22:15 ` dpdklab
2024-06-23 22:17 ` dpdklab
2024-06-23 22:17 ` dpdklab
2024-06-23 22:18 ` dpdklab
2024-06-23 22:19 ` dpdklab
2024-06-23 22:19 ` dpdklab
2024-06-23 22:22 ` dpdklab
2024-06-23 22:22 ` dpdklab
2024-06-23 22:23 ` dpdklab
2024-06-23 22:25 ` dpdklab
2024-06-23 22:25 ` dpdklab
2024-06-23 22:26 ` dpdklab
2024-06-23 22:26 ` dpdklab
2024-06-23 22:27 ` dpdklab
2024-06-23 22:28 ` dpdklab
2024-06-23 22:28 ` dpdklab
2024-06-23 22:29 ` dpdklab
2024-06-23 22:29 ` dpdklab
2024-06-23 22:30 ` dpdklab
2024-06-23 22:31 ` dpdklab
2024-06-23 22:31 ` dpdklab
2024-06-23 22:33 ` dpdklab
2024-06-23 22:33 ` dpdklab
2024-06-23 22:34 ` dpdklab
2024-06-23 22:34 ` dpdklab
2024-06-23 22:35 ` dpdklab
2024-06-23 22:35 ` dpdklab
2024-06-23 22:36 ` dpdklab
2024-06-23 22:37 ` dpdklab
2024-06-23 22:37 ` dpdklab
2024-06-23 22:37 ` dpdklab
2024-06-23 22:37 ` dpdklab
2024-06-23 22:38 ` dpdklab
2024-06-23 22:39 ` dpdklab
2024-06-23 22:39 ` dpdklab
2024-06-23 22:40 ` dpdklab
2024-06-23 22:40 ` dpdklab
2024-06-23 22:40 ` dpdklab
2024-06-23 22:40 ` dpdklab
2024-06-23 22:40 ` dpdklab
2024-06-23 22:41 ` dpdklab
2024-06-23 22:41 ` dpdklab
2024-06-23 22:41 ` dpdklab
2024-06-23 22:42 ` dpdklab
2024-06-23 22:42 ` dpdklab
2024-06-23 22:42 ` dpdklab
2024-06-23 22:43 ` dpdklab
2024-06-23 22:43 ` dpdklab
2024-06-23 22:44 ` dpdklab
2024-06-23 22:44 ` dpdklab
2024-06-23 22:45 ` dpdklab
2024-06-23 22:45 ` dpdklab
2024-06-23 22:46 ` dpdklab
2024-06-23 22:49 ` dpdklab
2024-06-23 22:50 ` dpdklab
2024-06-23 22:51 ` dpdklab
2024-06-23 22:52 ` dpdklab
2024-06-23 22:56 ` dpdklab
2024-06-23 22:56 ` dpdklab
2024-06-23 22:59 ` dpdklab
2024-06-23 22:59 ` dpdklab
2024-06-23 23:00 ` dpdklab
2024-06-23 23:01 ` dpdklab
2024-06-23 23:01 ` dpdklab
2024-06-23 23:04 ` dpdklab
2024-06-23 23:05 ` dpdklab
2024-06-23 23:07 ` dpdklab
2024-06-23 23:08 ` dpdklab
2024-06-23 23:10 ` dpdklab
2024-06-23 23:10 ` dpdklab
2024-06-23 23:11 ` dpdklab
2024-06-23 23:13 ` dpdklab
2024-06-23 23:13 ` dpdklab
2024-06-23 23:15 ` dpdklab
2024-06-23 23:15 ` dpdklab
2024-06-23 23:16 ` dpdklab
2024-06-23 23:18 ` dpdklab
2024-06-23 23:19 ` dpdklab
2024-06-23 23:20 ` dpdklab
2024-06-23 23:20 ` dpdklab
2024-06-23 23:21 ` dpdklab
2024-06-23 23:22 ` dpdklab
2024-06-23 23:23 ` dpdklab
2024-06-23 23:25 ` dpdklab
2024-06-23 23:26 ` dpdklab
2024-06-23 23:27 ` dpdklab
2024-06-23 23:28 ` dpdklab
2024-06-23 23:32 ` dpdklab
2024-06-23 23:36 ` dpdklab
2024-06-23 23:41 ` dpdklab
2024-06-24  0:54 ` dpdklab
2024-06-24  1:05 ` 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=667894ce.170a0220.beba4.729cSMTPIN_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).