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: |PENDING| pw142395 [PATCH] doc: update AMD Linux guide for power
Date: Fri, 12 Jul 2024 20:18:50 -0700 (PDT)	[thread overview]
Message-ID: <6691f21a.050a0220.d27dc.10c5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240713023051.763-1-vipin.varghese@amd.com>

Test-Label: iol-broadcom-Performance
Test-Status: PENDING
http://dpdk.org/patch/142395

_Performance Testing pending_

Submitter: Vipin Varghese <vipin.varghese@amd.com>
Date: Saturday, July 13 2024 02:30:51 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084

142395 --> performance testing pending

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Fail/Total: 0/3

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 128     | 1        | 1           | 0.4%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | 0.3%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -1.3%                        |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Fail/Total: 0/1

Detail performance results: 
The measurement deltas are not ready yet! Please check back later.

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-13  3:18 UTC|newest]

Thread overview: 115+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240713023051.763-1-vipin.varghese@amd.com>
2024-07-13  2:23 ` |SUCCESS| " qemudev
2024-07-13  2:27 ` qemudev
2024-07-13  2:33 ` checkpatch
2024-07-13  3:07 ` dpdklab
2024-07-13  3:11 ` dpdklab
2024-07-13  3:12 ` |PENDING| " dpdklab
2024-07-13  3:14 ` dpdklab
2024-07-13  3:14 ` dpdklab
2024-07-13  3:17 ` dpdklab
2024-07-13  3:18 ` dpdklab [this message]
2024-07-13  3:19 ` dpdklab
2024-07-13  3:20 ` dpdklab
2024-07-13  3:20 ` dpdklab
2024-07-13  3:23 ` dpdklab
2024-07-13  3:24 ` |FAILURE| " 0-day Robot
2024-07-13  3:25 ` |PENDING| " dpdklab
2024-07-13  3:26 ` |SUCCESS| " dpdklab
2024-07-13  3:26 ` |PENDING| " dpdklab
2024-07-13  3:27 ` |SUCCESS| " dpdklab
2024-07-13  3:27 ` |PENDING| " dpdklab
2024-07-13  3:29 ` dpdklab
2024-07-13  3:29 ` |SUCCESS| " dpdklab
2024-07-13  3:30 ` |PENDING| " dpdklab
2024-07-13  3:30 ` dpdklab
2024-07-13  3:31 ` dpdklab
2024-07-13  3:31 ` dpdklab
2024-07-13  3:32 ` dpdklab
2024-07-13  3:33 ` dpdklab
2024-07-13  3:33 ` |SUCCESS| " dpdklab
2024-07-13  3:34 ` |PENDING| " dpdklab
2024-07-13  3:34 ` dpdklab
2024-07-13  3:35 ` dpdklab
2024-07-13  3:36 ` dpdklab
2024-07-13  3:36 ` dpdklab
2024-07-13  3:36 ` dpdklab
2024-07-13  3:36 ` dpdklab
2024-07-13  3:37 ` dpdklab
2024-07-13  3:37 ` dpdklab
2024-07-13  3:38 ` dpdklab
2024-07-13  3:39 ` dpdklab
2024-07-13  3:39 ` dpdklab
2024-07-13  3:39 ` dpdklab
2024-07-13  3:40 ` dpdklab
2024-07-13  3:40 ` dpdklab
2024-07-13  3:41 ` dpdklab
2024-07-13  3:41 ` dpdklab
2024-07-13  3:43 ` dpdklab
2024-07-13  3:43 ` dpdklab
2024-07-13  3:43 ` dpdklab
2024-07-13  3:44 ` dpdklab
2024-07-13  3:45 ` dpdklab
2024-07-13  3:45 ` dpdklab
2024-07-13  3:45 ` dpdklab
2024-07-13  3:49 ` dpdklab
2024-07-13  3:49 ` dpdklab
2024-07-13  3:50 ` dpdklab
2024-07-13  3:53 ` dpdklab
2024-07-13  3:53 ` |SUCCESS| " dpdklab
2024-07-13  3:54 ` |PENDING| " dpdklab
2024-07-13  3:54 ` dpdklab
2024-07-13  3:54 ` dpdklab
2024-07-13  3:55 ` dpdklab
2024-07-13  3:57 ` dpdklab
2024-07-13  4:01 ` dpdklab
2024-07-13  4:02 ` dpdklab
2024-07-13  4:04 ` dpdklab
2024-07-13  4:05 ` dpdklab
2024-07-13  4:05 ` dpdklab
2024-07-13  4:06 ` dpdklab
2024-07-13  4:08 ` dpdklab
2024-07-13  4:10 ` dpdklab
2024-07-13  4:10 ` dpdklab
2024-07-13  4:12 ` dpdklab
2024-07-13  4:12 ` dpdklab
2024-07-13  4:13 ` dpdklab
2024-07-13  4:13 ` dpdklab
2024-07-13  4:13 ` dpdklab
2024-07-13  4:14 ` dpdklab
2024-07-13  4:15 ` dpdklab
2024-07-13  4:16 ` dpdklab
2024-07-13  4:16 ` dpdklab
2024-07-13  4:17 ` dpdklab
2024-07-13  4:17 ` dpdklab
2024-07-13  4:17 ` dpdklab
2024-07-13  4:22 ` dpdklab
2024-07-13  4:22 ` dpdklab
2024-07-13  4:22 ` dpdklab
2024-07-13  4:23 ` dpdklab
2024-07-13  4:23 ` dpdklab
2024-07-13  4:24 ` dpdklab
2024-07-13  4:25 ` dpdklab
2024-07-13  4:26 ` |SUCCESS| " dpdklab
2024-07-13  4:28 ` |PENDING| " dpdklab
2024-07-13  4:31 ` |SUCCESS| " dpdklab
2024-07-13  4:31 ` |PENDING| " dpdklab
2024-07-13  4:32 ` dpdklab
2024-07-13  4:37 ` dpdklab
2024-07-13  4:39 ` dpdklab
2024-07-13  4:40 ` dpdklab
2024-07-13  4:40 ` |SUCCESS| " dpdklab
2024-07-13  4:43 ` |PENDING| " dpdklab
2024-07-13  4:45 ` dpdklab
2024-07-13  4:46 ` dpdklab
2024-07-13  4:47 ` dpdklab
2024-07-13  4:47 ` dpdklab
2024-07-13  4:52 ` dpdklab
2024-07-13  4:53 ` dpdklab
2024-07-13  4:56 ` dpdklab
2024-07-13  5:02 ` |SUCCESS| " dpdklab
2024-07-13  5:04 ` dpdklab
2024-07-15 14:07 ` dpdklab
2024-07-15 14:11 ` dpdklab
2024-07-15 14:31 ` dpdklab
2024-07-15 14:36 ` dpdklab
2024-07-15 14:42 ` 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=6691f21a.050a0220.d27dc.10c5SMTPIN_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).