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| pw141477-141479 [PATCH] [3/3] dts: mac filter test suite r
Date: Fri, 21 Jun 2024 11:34:36 -0700 (PDT)	[thread overview]
Message-ID: <6675c7bc.170a0220.31706.06c9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240621172059.8194-8-npratte@iol.unh.edu>

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

_Performance Testing PASS_

Submitter: Nicholas Pratte <npratte@iol.unh.edu>
Date: Friday, June 21 2024 17:21:03 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:4a44d97f0a52a76258c6a6cb6a713f4380a8ab1f

141477-141479 --> 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.3%                         |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 256     | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 256        | 256     | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 256     | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 512        | 256     | 1        | 1           | -0.4%                        |
+------------+---------+----------+-------------+------------------------------+

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

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-21 18:34 UTC|newest]

Thread overview: 115+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240621172059.8194-8-npratte@iol.unh.edu>
2024-06-21 16:57 ` |SUCCESS| pw141477-141479 [PATCH 3/3] dts: mac filter test suite refactored for new dts qemudev
2024-06-21 17:01 ` qemudev
2024-06-21 17:25 ` |SUCCESS| pw141479 " checkpatch
2024-06-21 18:25 ` 0-day Robot
2024-06-21 18:32 ` |SUCCESS| pw141477-141479 [PATCH] [3/3] dts: mac filter test suite r dpdklab
2024-06-21 18:32 ` dpdklab
2024-06-21 18:33 ` dpdklab
2024-06-21 18:33 ` dpdklab
2024-06-21 18:33 ` dpdklab
2024-06-21 18:34 ` dpdklab
2024-06-21 18:34 ` dpdklab
2024-06-21 18:34 ` dpdklab [this message]
2024-06-21 18:35 ` dpdklab
2024-06-21 18:35 ` dpdklab
2024-06-21 18:35 ` dpdklab
2024-06-21 18:35 ` dpdklab
2024-06-21 18:37 ` dpdklab
2024-06-21 18:37 ` dpdklab
2024-06-21 18:38 ` dpdklab
2024-06-21 18:38 ` dpdklab
2024-06-21 18:39 ` dpdklab
2024-06-21 18:40 ` dpdklab
2024-06-21 18:40 ` dpdklab
2024-06-21 18:41 ` dpdklab
2024-06-21 18:42 ` dpdklab
2024-06-21 18:42 ` dpdklab
2024-06-21 18:43 ` dpdklab
2024-06-21 18:44 ` dpdklab
2024-06-21 18:44 ` dpdklab
2024-06-21 18:45 ` dpdklab
2024-06-21 18:45 ` dpdklab
2024-06-21 18:46 ` dpdklab
2024-06-21 18:46 ` dpdklab
2024-06-21 18:47 ` dpdklab
2024-06-21 18:47 ` dpdklab
2024-06-21 18:48 ` dpdklab
2024-06-21 18:48 ` dpdklab
2024-06-21 18:49 ` dpdklab
2024-06-21 18:49 ` dpdklab
2024-06-21 18:49 ` dpdklab
2024-06-21 18:50 ` dpdklab
2024-06-21 18:50 ` dpdklab
2024-06-21 18:51 ` dpdklab
2024-06-21 18:51 ` dpdklab
2024-06-21 18:52 ` dpdklab
2024-06-21 18:52 ` dpdklab
2024-06-21 18:52 ` dpdklab
2024-06-21 18:53 ` dpdklab
2024-06-21 18:53 ` dpdklab
2024-06-21 18:53 ` dpdklab
2024-06-21 18:54 ` dpdklab
2024-06-21 18:54 ` dpdklab
2024-06-21 18:55 ` dpdklab
2024-06-21 18:55 ` dpdklab
2024-06-21 18:55 ` dpdklab
2024-06-21 18:55 ` dpdklab
2024-06-21 18:56 ` dpdklab
2024-06-21 18:56 ` dpdklab
2024-06-21 18:56 ` dpdklab
2024-06-21 18:56 ` dpdklab
2024-06-21 18:57 ` dpdklab
2024-06-21 18:57 ` dpdklab
2024-06-21 18:57 ` dpdklab
2024-06-21 18:58 ` dpdklab
2024-06-21 18:58 ` dpdklab
2024-06-21 18:58 ` dpdklab
2024-06-21 18:58 ` dpdklab
2024-06-21 18:59 ` dpdklab
2024-06-21 18:59 ` dpdklab
2024-06-21 19:00 ` dpdklab
2024-06-21 19:00 ` dpdklab
2024-06-21 19:00 ` dpdklab
2024-06-21 19:00 ` dpdklab
2024-06-21 19:01 ` dpdklab
2024-06-21 19:01 ` dpdklab
2024-06-21 19:01 ` dpdklab
2024-06-21 19:01 ` dpdklab
2024-06-21 19:02 ` dpdklab
2024-06-21 19:02 ` dpdklab
2024-06-21 19:02 ` dpdklab
2024-06-21 19:02 ` dpdklab
2024-06-21 19:03 ` dpdklab
2024-06-21 19:04 ` dpdklab
2024-06-21 19:04 ` dpdklab
2024-06-21 19:05 ` dpdklab
2024-06-21 19:05 ` dpdklab
2024-06-21 19:06 ` dpdklab
2024-06-21 19:06 ` dpdklab
2024-06-21 19:06 ` dpdklab
2024-06-21 19:06 ` dpdklab
2024-06-21 19:06 ` dpdklab
2024-06-21 19:07 ` dpdklab
2024-06-21 19:07 ` dpdklab
2024-06-21 19:07 ` dpdklab
2024-06-21 19:08 ` dpdklab
2024-06-21 19:09 ` dpdklab
2024-06-21 19:09 ` dpdklab
2024-06-21 19:10 ` dpdklab
2024-06-21 19:11 ` dpdklab
2024-06-21 19:12 ` dpdklab
2024-06-21 19:13 ` dpdklab
2024-06-21 19:13 ` dpdklab
2024-06-21 19:14 ` dpdklab
2024-06-21 19:15 ` dpdklab
2024-06-21 19:17 ` dpdklab
2024-06-21 19:18 ` dpdklab
2024-06-21 19:21 ` dpdklab
2024-06-21 19:23 ` dpdklab
2024-06-21 19:24 ` dpdklab
2024-06-21 19:37 ` dpdklab
2024-06-21 19:48 ` dpdklab
2024-06-21 19:51 ` dpdklab
2024-06-21 21:25 ` dpdklab
2024-06-21 21:38 ` dpdklab
2024-06-22 12:56 ` 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=6675c7bc.170a0220.31706.06c9SMTPIN_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).