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| pw141761-141772 [PATCH] [v3,12/12] crypto/cnxk: enable dua
Date: Wed, 26 Jun 2024 11:33:12 -0700 (PDT)	[thread overview]
Message-ID: <667c5ee8.650a0220.7024b.f359SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240626105534.1386528-13-asasidharan@marvell.com>

Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/141772

_Performance Testing PASS_

Submitter: Aakash Sasidharan <asasidharan@marvell.com>
Date: Wednesday, June 26 2024 10:55:34 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c0fa83fe030771dea12e65ca1ba11174e1164774

141761-141772 --> performance testing pass

Test environment and result as below:

Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: Unknown
Fail/Total: 0/4

Detail performance results: 
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size |  throughput difference from  |
|          |             |         |            |           expected           |
+==========+=============+=========+============+==============================+
| 1        | 2           | 512     | 64         | -0.1%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 2048    | 64         | -1.4%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | -2.3%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | 1.0%                         |
+----------+-------------+---------+------------+------------------------------+

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

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-26 18:33 UTC|newest]

Thread overview: 115+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240626105534.1386528-13-asasidharan@marvell.com>
2024-06-26 10:34 ` |SUCCESS| pw141761-141772 [PATCH v3 12/12] crypto/cnxk: enable dual submission to CPT qemudev
2024-06-26 10:39 ` qemudev
2024-06-26 11:02 ` |SUCCESS| pw141772 " checkpatch
2024-06-26 12:05 ` 0-day Robot
2024-06-26 18:31 ` |SUCCESS| pw141761-141772 [PATCH] [v3,12/12] crypto/cnxk: enable dua dpdklab
2024-06-26 18:33 ` dpdklab [this message]
2024-06-26 18:39 ` dpdklab
2024-06-26 18:45 ` dpdklab
2024-06-26 18:45 ` |PENDING| " dpdklab
2024-06-26 18:48 ` dpdklab
2024-06-26 18:52 ` |SUCCESS| " dpdklab
2024-06-26 19:00 ` |PENDING| " dpdklab
2024-06-26 19:05 ` |SUCCESS| " dpdklab
2024-06-26 19:06 ` |PENDING| " dpdklab
2024-06-26 19:09 ` dpdklab
2024-06-26 19:09 ` dpdklab
2024-06-26 19:12 ` dpdklab
2024-06-26 19:13 ` dpdklab
2024-06-26 19:13 ` |SUCCESS| " dpdklab
2024-06-26 19:17 ` dpdklab
2024-06-26 19:18 ` |PENDING| " dpdklab
2024-06-26 19:20 ` dpdklab
2024-06-26 19:22 ` dpdklab
2024-06-26 19:25 ` |SUCCESS| " dpdklab
2024-06-26 19:27 ` |PENDING| " dpdklab
2024-06-26 19:27 ` |SUCCESS| " dpdklab
2024-06-26 19:28 ` |PENDING| " dpdklab
2024-06-26 19:29 ` |SUCCESS| " dpdklab
2024-06-26 19:38 ` |PENDING| " dpdklab
2024-06-26 19:42 ` |SUCCESS| " dpdklab
2024-06-26 19:44 ` dpdklab
2024-06-26 19:50 ` dpdklab
2024-06-26 19:51 ` dpdklab
2024-06-26 19:54 ` dpdklab
2024-06-26 20:16 ` dpdklab
2024-06-26 20:17 ` dpdklab
2024-06-26 22:04 ` dpdklab
2024-06-26 22:06 ` dpdklab
2024-06-26 22:09 ` dpdklab
2024-06-26 22:09 ` dpdklab
2024-06-26 22:10 ` dpdklab
2024-06-26 22:14 ` dpdklab
2024-06-26 22:40 ` dpdklab
2024-06-26 22:52 ` dpdklab
2024-06-26 23:16 ` dpdklab
2024-06-26 23:19 ` dpdklab
2024-06-26 23:27 ` dpdklab
2024-06-26 23:30 ` dpdklab
2024-06-26 23:37 ` dpdklab
2024-06-26 23:39 ` dpdklab
2024-06-26 23:40 ` dpdklab
2024-06-26 23:40 ` dpdklab
2024-06-26 23:40 ` dpdklab
2024-06-26 23:40 ` dpdklab
2024-06-26 23:45 ` dpdklab
2024-06-26 23:46 ` dpdklab
2024-06-26 23:50 ` dpdklab
2024-06-26 23:52 ` dpdklab
2024-06-26 23:55 ` dpdklab
2024-06-26 23:56 ` dpdklab
2024-06-26 23:57 ` dpdklab
2024-06-26 23:58 ` dpdklab
2024-06-26 23:59 ` dpdklab
2024-06-26 23:59 ` dpdklab
2024-06-27  0:01 ` dpdklab
2024-06-27  0:04 ` dpdklab
2024-06-27  0:05 ` dpdklab
2024-06-27  0:06 ` dpdklab
2024-06-27  0:06 ` dpdklab
2024-06-27  0:06 ` dpdklab
2024-06-27  0:09 ` dpdklab
2024-06-27  0:09 ` dpdklab
2024-06-27  0:16 ` dpdklab
2024-06-27  0:20 ` dpdklab
2024-06-27  0:21 ` dpdklab
2024-06-27  0:23 ` dpdklab
2024-06-27  0:24 ` dpdklab
2024-06-27  0:26 ` dpdklab
2024-06-27  0:29 ` dpdklab
2024-06-27  0:30 ` dpdklab
2024-06-27  0:30 ` dpdklab
2024-06-27  0:30 ` dpdklab
2024-06-27  0:31 ` dpdklab
2024-06-27  0:31 ` dpdklab
2024-06-27  0:34 ` dpdklab
2024-06-27  0:38 ` dpdklab
2024-06-27  0:39 ` dpdklab
2024-06-27  0:39 ` dpdklab
2024-06-27  0:41 ` dpdklab
2024-06-27  0:43 ` dpdklab
2024-06-27  0:46 ` dpdklab
2024-06-27  0:47 ` dpdklab
2024-06-27  0:50 ` dpdklab
2024-06-27  0:52 ` dpdklab
2024-06-27  0:52 ` dpdklab
2024-06-27  0:57 ` dpdklab
2024-06-27  1:02 ` dpdklab
2024-06-27  1:05 ` dpdklab
2024-06-27  1:05 ` dpdklab
2024-06-27  1:08 ` dpdklab
2024-06-27  1:11 ` dpdklab
2024-06-27  1:21 ` dpdklab
2024-06-27  1:22 ` dpdklab
2024-06-27  1:31 ` dpdklab
2024-06-27  1:32 ` dpdklab
2024-06-27  1:32 ` dpdklab
2024-06-27  1:39 ` dpdklab
2024-06-27  1:40 ` dpdklab
2024-06-27  1:48 ` dpdklab
2024-06-27  1:49 ` dpdklab
2024-06-27  1:51 ` dpdklab
2024-06-27  5:39 ` dpdklab
2024-06-27 10:35 ` dpdklab
2024-06-27 10:50 ` dpdklab
2024-06-28  4:17 ` 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=667c5ee8.650a0220.7024b.f359SMTPIN_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).