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| pw129157 [PATCH] [v2] net/idpf: fix error path processing
Date: Fri, 30 Jun 2023 15:44:57 -0700 (PDT)	[thread overview]
Message-ID: <649f5ae9.170a0220.e80d.dc8bSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/129157

_Performance Testing PASS_

Submitter: Liu, Mingxia <mingxia.liu@intel.com>
Date: Friday, June 30 2023 18:54:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:93a4b3beba4ee611685148917981f846427cafb2

129157 --> performance testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-39-generic
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Target: x86_64-native-linuxapp-gcc
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           | -0.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.2%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-06-30 22:45 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 22:44 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-02 13:44 dpdklab
2023-07-01  8:44 dpdklab
2023-07-01  8:43 dpdklab
2023-07-01  8:42 dpdklab
2023-07-01  7:56 dpdklab
2023-07-01  7:24 dpdklab
2023-07-01  3:31 dpdklab
2023-07-01  3:20 dpdklab
2023-07-01  3:19 dpdklab
2023-07-01  0:14 dpdklab
2023-07-01  0:13 dpdklab
2023-07-01  0:10 dpdklab
2023-07-01  0:06 dpdklab
2023-07-01  0:06 dpdklab
2023-07-01  0:05 dpdklab
2023-06-30 23:56 dpdklab
2023-06-30 23:56 dpdklab
2023-06-30 23:56 dpdklab
2023-06-30 23:56 dpdklab
2023-06-30 23:51 dpdklab
2023-06-30 23:45 dpdklab
2023-06-30 23:39 dpdklab
2023-06-30 23:38 dpdklab
2023-06-30 22:54 dpdklab
2023-06-30 22:44 dpdklab
2023-06-30 22:44 dpdklab
2023-06-30 22:44 dpdklab
2023-06-30 22:43 dpdklab
2023-06-30 22:35 dpdklab
2023-06-30 22:35 dpdklab
     [not found] <20230630185402.13307-1-mingxia.liu@intel.com>
2023-06-30 10:31 ` |SUCCESS| pw129157 [PATCH v2] " qemudev
2023-06-30 10:35 ` qemudev
2023-06-30 10:36 ` checkpatch
2023-06-30 11:39 ` 0-day Robot

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=649f5ae9.170a0220.e80d.dc8bSMTPIN_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).