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| pw142396 [PATCH] doc: update AMD Linux guide
Date: Sat, 13 Jul 2024 04:41:13 -0700 (PDT)	[thread overview]
Message-ID: <669267d9.050a0220.3497d.5df2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240713110829.793-1-vipin.varghese@amd.com>

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

_Performance Testing pending_

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

142396 --> 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.5%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -0.8%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+

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/30511/

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 11:41 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240713110829.793-1-vipin.varghese@amd.com>
2024-07-13 10:43 ` |SUCCESS| " qemudev
2024-07-13 10:48 ` qemudev
2024-07-13 11:09 ` checkpatch
2024-07-13 11:38 ` |PENDING| " dpdklab
2024-07-13 11:40 ` dpdklab
2024-07-13 11:41 ` dpdklab [this message]
2024-07-13 11:42 ` dpdklab
2024-07-13 11:42 ` dpdklab
2024-07-13 11:45 ` dpdklab
2024-07-13 11:46 ` |SUCCESS| " dpdklab
2024-07-13 11:47 ` |PENDING| " dpdklab
2024-07-13 11:48 ` dpdklab
2024-07-13 11:49 ` |SUCCESS| " dpdklab
2024-07-13 11:49 ` dpdklab
2024-07-13 11:49 ` |PENDING| " dpdklab
2024-07-13 11:50 ` dpdklab
2024-07-13 11:51 ` dpdklab
2024-07-13 11:52 ` dpdklab
2024-07-13 11:53 ` dpdklab
2024-07-13 11:53 ` dpdklab
2024-07-13 11:53 ` dpdklab
2024-07-13 11:53 ` dpdklab
2024-07-13 11:53 ` dpdklab
2024-07-13 11:56 ` dpdklab
2024-07-13 11:57 ` |SUCCESS| " dpdklab
2024-07-13 11:58 ` |PENDING| " dpdklab
2024-07-13 11:58 ` dpdklab
2024-07-13 11:59 ` dpdklab
2024-07-13 12:00 ` dpdklab
2024-07-13 12:00 ` dpdklab
2024-07-13 12:00 ` dpdklab
2024-07-13 12:00 ` dpdklab
2024-07-13 12:01 ` dpdklab
2024-07-13 12:01 ` dpdklab
2024-07-13 12:01 ` dpdklab
2024-07-13 12:02 ` |SUCCESS| " dpdklab
2024-07-13 12:04 ` 0-day Robot
2024-07-13 12:04 ` |PENDING| " dpdklab
2024-07-13 12:04 ` dpdklab
2024-07-13 12:04 ` dpdklab
2024-07-13 12:05 ` |SUCCESS| " dpdklab
2024-07-13 12:06 ` |PENDING| " dpdklab
2024-07-13 12:06 ` dpdklab
2024-07-13 12:06 ` dpdklab
2024-07-13 12:07 ` dpdklab
2024-07-13 12:07 ` dpdklab
2024-07-13 12:07 ` dpdklab
2024-07-13 12:08 ` dpdklab
2024-07-13 12:08 ` dpdklab
2024-07-13 12:08 ` dpdklab
2024-07-13 12:09 ` dpdklab
2024-07-13 12:10 ` dpdklab
2024-07-13 12:10 ` dpdklab
2024-07-13 12:11 ` dpdklab
2024-07-13 12:12 ` dpdklab
2024-07-13 12:12 ` dpdklab
2024-07-13 12:12 ` dpdklab
2024-07-13 12:12 ` dpdklab
2024-07-13 12:13 ` dpdklab
2024-07-13 12:13 ` dpdklab
2024-07-13 12:14 ` dpdklab
2024-07-13 12:14 ` dpdklab
2024-07-13 12:15 ` dpdklab
2024-07-13 12:15 ` dpdklab
2024-07-13 12:17 ` dpdklab
2024-07-13 12:19 ` dpdklab
2024-07-13 12:20 ` dpdklab
2024-07-13 12:20 ` dpdklab
2024-07-13 12:20 ` dpdklab
2024-07-13 12:20 ` dpdklab
2024-07-13 12:21 ` dpdklab
2024-07-13 12:22 ` |SUCCESS| " dpdklab
2024-07-13 12:22 ` |PENDING| " dpdklab
2024-07-13 12:22 ` dpdklab
2024-07-13 12:22 ` dpdklab
2024-07-13 12:22 ` |SUCCESS| " dpdklab
2024-07-13 12:22 ` |PENDING| " dpdklab
2024-07-13 12:23 ` dpdklab
2024-07-13 12:23 ` dpdklab
2024-07-13 12:24 ` dpdklab
2024-07-13 12:24 ` dpdklab
2024-07-13 12:25 ` dpdklab
2024-07-13 12:25 ` dpdklab
2024-07-13 12:26 ` dpdklab
2024-07-13 12:27 ` dpdklab
2024-07-13 12:27 ` dpdklab
2024-07-13 12:28 ` dpdklab
2024-07-13 12:29 ` dpdklab
2024-07-13 12:30 ` dpdklab
2024-07-13 12:30 ` dpdklab
2024-07-13 12:30 ` dpdklab
2024-07-13 12:32 ` dpdklab
2024-07-13 12:32 ` dpdklab
2024-07-13 12:33 ` dpdklab
2024-07-13 12:34 ` dpdklab
2024-07-13 12:34 ` dpdklab
2024-07-13 12:38 ` |SUCCESS| " dpdklab
2024-07-13 12:38 ` |PENDING| " dpdklab
2024-07-13 12:39 ` dpdklab
2024-07-13 12:39 ` dpdklab
2024-07-13 12:40 ` dpdklab
2024-07-13 12:42 ` dpdklab
2024-07-13 12:42 ` dpdklab
2024-07-13 12:43 ` |SUCCESS| " dpdklab
2024-07-13 12:43 ` dpdklab
2024-07-13 12:49 ` dpdklab
2024-07-13 13:11 ` |PENDING| " dpdklab
2024-07-13 13:26 ` dpdklab
2024-07-13 13:27 ` |SUCCESS| " dpdklab
2024-07-15 22:03 ` dpdklab
2024-07-15 22:32 ` dpdklab
2024-07-15 23:02 ` dpdklab
2024-07-15 23:31 ` dpdklab
2024-07-15 23:51 ` 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=669267d9.050a0220.3497d.5df2SMTPIN_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).