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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126125-126137 [PATCH] [v6, 15/15] eal: do not define typeof macro when building with MSVC
Date: Sat, 15 Apr 2023 02:47:15 +0000 (UTC)	[thread overview]
Message-ID: <20230415024715.EF7AD6008C@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

_Performance Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Saturday, April 15 2023 01:15:46 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:3b3fef9de22af80d173453ab65a80b01ce38cbfd

126125-126137 --> 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.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-04-15  2:47 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-15  2:47 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-15 13:54 dpdklab
2023-04-15 13:54 dpdklab
2023-04-15 13:24 dpdklab
2023-04-15 13:24 dpdklab
2023-04-15 10:59 dpdklab
2023-04-15 10:17 dpdklab
2023-04-15  9:51 dpdklab
2023-04-15  9:41 dpdklab
2023-04-15  8:42 dpdklab
2023-04-15  8:39 dpdklab
2023-04-15  8:22 dpdklab
2023-04-15  8:18 dpdklab
2023-04-15  8:02 dpdklab
2023-04-15  7:57 dpdklab
2023-04-15  6:05 dpdklab
2023-04-15  5:06 dpdklab
2023-04-15  4:59 dpdklab
2023-04-15  4:59 dpdklab
2023-04-15  4:54 dpdklab
2023-04-15  4:45 dpdklab
2023-04-15  4:44 dpdklab
2023-04-15  4:41 dpdklab
2023-04-15  4:33 dpdklab
2023-04-15  4:31 dpdklab
2023-04-15  4:20 dpdklab
2023-04-15  4:07 dpdklab
2023-04-15  4:07 dpdklab
2023-04-15  4:06 dpdklab
2023-04-15  4:05 dpdklab
2023-04-15  4:02 dpdklab
2023-04-15  3:59 dpdklab
2023-04-15  3:58 dpdklab
2023-04-15  3:57 dpdklab
2023-04-15  3:50 dpdklab
2023-04-15  3:50 dpdklab
2023-04-15  3:46 dpdklab
2023-04-15  3:45 dpdklab
2023-04-15  3:37 dpdklab
2023-04-15  3:33 dpdklab
2023-04-15  3:26 dpdklab
2023-04-15  3:21 dpdklab
2023-04-15  3:19 dpdklab
2023-04-15  3:18 dpdklab
2023-04-15  3:17 dpdklab
2023-04-15  3:17 dpdklab
2023-04-15  3:13 dpdklab
2023-04-15  3:12 dpdklab
2023-04-15  3:05 dpdklab
2023-04-15  2:56 dpdklab
2023-04-15  2:49 dpdklab
2023-04-15  2:44 dpdklab
2023-04-15  2:39 dpdklab
2023-04-15  2:39 dpdklab
2023-04-15  2:38 dpdklab
2023-04-15  2:34 dpdklab
2023-04-15  2:31 dpdklab
     [not found] <1681521346-20356-16-git-send-email-roretzla@linux.microsoft.com>
2023-04-15  1:07 ` |SUCCESS| pw126125-126137 [PATCH v6 " qemudev
2023-04-15  1:11 ` qemudev

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=20230415024715.EF7AD6008C@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).