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| pw142858 [PATCH] [v5] net/gve : Update EOP & csum bit in t
Date: Fri, 02 Aug 2024 03:02:57 -0700 (PDT)	[thread overview]
Message-ID: <66acaed1.0d0a0220.23b17.5398SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1722575288-2408630-1-git-send-email-tathagat.dpdk@gmail.com>

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

_Performance Testing pending_

Submitter: Tathagat Priyadarshi <tathagat.dpdk@gmail.com>
Date: Friday, August 02 2024 05:08:08 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:37ce4c84c0f23c3989bc7ae19e03a4593cec94e5

142858 --> performance testing pending

Upstream job id: Template-DTS-Pipeline#172726

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.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | -1.3%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.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/30706/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-02 10:02 UTC|newest]

Thread overview: 110+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1722575288-2408630-1-git-send-email-tathagat.dpdk@gmail.com>
2024-08-02  4:39 ` |SUCCESS| pw142858 [PATCH v5] net/gve : Update EOP & csum bit in txd rte_mbuf chain qemudev
2024-08-02  4:43 ` qemudev
2024-08-02  5:07 ` checkpatch
2024-08-02  6:02 ` 0-day Robot
2024-08-02  6:55 ` |SUCCESS| pw142858 [PATCH] [v5] net/gve : Update EOP & csum bit in t dpdklab
2024-08-02  7:07 ` |PENDING| " dpdklab
2024-08-02  7:20 ` |SUCCESS| " dpdklab
2024-08-02  7:23 ` |PENDING| " dpdklab
2024-08-02  7:34 ` dpdklab
2024-08-02  7:36 ` |SUCCESS| " dpdklab
2024-08-02  7:45 ` |PENDING| " dpdklab
2024-08-02  7:46 ` dpdklab
2024-08-02  7:50 ` dpdklab
2024-08-02  7:58 ` dpdklab
2024-08-02  8:03 ` dpdklab
2024-08-02  8:04 ` dpdklab
2024-08-02  8:05 ` dpdklab
2024-08-02  8:07 ` dpdklab
2024-08-02  8:08 ` dpdklab
2024-08-02  8:12 ` dpdklab
2024-08-02  8:14 ` dpdklab
2024-08-02  8:17 ` dpdklab
2024-08-02  8:18 ` |SUCCESS| " dpdklab
2024-08-02  8:24 ` dpdklab
2024-08-02 10:02 ` dpdklab [this message]
2024-08-02 10:11 ` dpdklab
2024-08-02 10:46 ` dpdklab
2024-08-02 12:14 ` |PENDING| " dpdklab
2024-08-02 12:16 ` dpdklab
2024-08-02 12:18 ` dpdklab
2024-08-02 12:22 ` dpdklab
2024-08-02 12:35 ` |SUCCESS| " dpdklab
2024-08-02 12:36 ` |PENDING| " dpdklab
2024-08-02 12:36 ` dpdklab
2024-08-02 12:40 ` dpdklab
2024-08-02 12:40 ` |SUCCESS| " dpdklab
2024-08-02 12:41 ` |PENDING| " dpdklab
2024-08-02 12:41 ` dpdklab
2024-08-02 12:43 ` dpdklab
2024-08-02 12:45 ` dpdklab
2024-08-02 12:45 ` |SUCCESS| " dpdklab
2024-08-02 12:46 ` |PENDING| " dpdklab
2024-08-02 12:47 ` dpdklab
2024-08-02 12:50 ` |SUCCESS| " dpdklab
2024-08-02 12:53 ` |PENDING| " dpdklab
2024-08-02 12:54 ` dpdklab
2024-08-02 12:57 ` dpdklab
2024-08-02 12:59 ` dpdklab
2024-08-02 12:59 ` dpdklab
2024-08-02 13:01 ` dpdklab
2024-08-02 13:01 ` dpdklab
2024-08-02 13:02 ` dpdklab
2024-08-02 13:03 ` dpdklab
2024-08-02 13:03 ` dpdklab
2024-08-02 13:05 ` dpdklab
2024-08-02 13:06 ` dpdklab
2024-08-02 13:07 ` dpdklab
2024-08-02 13:08 ` dpdklab
2024-08-02 13:08 ` dpdklab
2024-08-02 13:09 ` |SUCCESS| " dpdklab
2024-08-02 13:10 ` |PENDING| " dpdklab
2024-08-02 13:10 ` dpdklab
2024-08-02 13:11 ` dpdklab
2024-08-02 13:12 ` dpdklab
2024-08-02 13:12 ` dpdklab
2024-08-02 13:14 ` dpdklab
2024-08-02 13:15 ` dpdklab
2024-08-02 13:16 ` dpdklab
2024-08-02 13:16 ` dpdklab
2024-08-02 13:16 ` dpdklab
2024-08-02 13:19 ` dpdklab
2024-08-02 13:22 ` dpdklab
2024-08-02 13:22 ` dpdklab
2024-08-02 13:24 ` dpdklab
2024-08-02 13:25 ` dpdklab
2024-08-02 13:29 ` dpdklab
2024-08-02 13:29 ` dpdklab
2024-08-02 13:30 ` dpdklab
2024-08-02 13:31 ` dpdklab
2024-08-02 13:34 ` dpdklab
2024-08-02 13:35 ` dpdklab
2024-08-02 13:35 ` dpdklab
2024-08-02 13:36 ` dpdklab
2024-08-02 13:37 ` dpdklab
2024-08-02 13:38 ` dpdklab
2024-08-02 13:39 ` dpdklab
2024-08-02 13:39 ` dpdklab
2024-08-02 13:40 ` dpdklab
2024-08-02 13:43 ` dpdklab
2024-08-02 13:43 ` |SUCCESS| " dpdklab
2024-08-02 13:44 ` |PENDING| " dpdklab
2024-08-02 13:50 ` dpdklab
2024-08-02 13:54 ` dpdklab
2024-08-02 13:56 ` dpdklab
2024-08-02 13:58 ` dpdklab
2024-08-02 13:59 ` dpdklab
2024-08-02 14:00 ` dpdklab
2024-08-02 14:03 ` dpdklab
2024-08-02 14:04 ` dpdklab
2024-08-02 14:04 ` dpdklab
2024-08-02 14:06 ` dpdklab
2024-08-02 14:08 ` |SUCCESS| " dpdklab
2024-08-02 14:08 ` dpdklab
2024-08-02 14:09 ` dpdklab
2024-08-02 14:09 ` dpdklab
2024-08-02 14:17 ` dpdklab
2024-08-03  8:46 ` dpdklab
2024-08-06 11:21 ` dpdklab
2024-08-06 11:30 ` dpdklab
2024-08-06 11:43 ` 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=66acaed1.0d0a0220.23b17.5398SMTPIN_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).