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,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] 70fef0ac8fa33eebc9c5c95844466544f35e35f9
Date: Sat, 27 Apr 2024 00:51:56 -0700 (PDT)	[thread overview]
Message-ID: <662cae9c.050a0220.af9d7.aba8SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: dpdk-next-net

70fef0ac8fa33eebc9c5c95844466544f35e35f9 --> performance testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 512     | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 1.4%                         |
+------------+---------+----------+-------------+------------------------------+

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28959/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-04-27  7:51 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-27  7:51 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-27  9:55 dpdklab
2024-04-27  9:33 dpdklab
2024-04-27  8:57 dpdklab
2024-04-27  8:42 dpdklab
2024-04-27  8:23 dpdklab
2024-04-27  8:19 dpdklab
2024-04-27  8:15 dpdklab
2024-04-27  8:13 dpdklab
2024-04-27  8:11 dpdklab
2024-04-27  7:44 dpdklab
2024-04-27  7:40 dpdklab
2024-04-27  7:39 dpdklab
2024-04-27  7:37 dpdklab
2024-04-27  7:37 dpdklab
2024-04-27  7:35 dpdklab
2024-04-27  7:34 dpdklab
2024-04-27  7:32 dpdklab
2024-04-27  7:31 dpdklab
2024-04-27  7:27 dpdklab
2024-04-27  7:27 dpdklab
2024-04-27  7:25 dpdklab
2024-04-27  7:23 dpdklab
2024-04-27  7:23 dpdklab
2024-04-27  7:22 dpdklab
2024-04-27  7:19 dpdklab
2024-04-27  7:14 dpdklab
2024-04-27  7:13 dpdklab
2024-04-27  7:13 dpdklab
2024-04-27  7:12 dpdklab
2024-04-27  7:05 dpdklab
2024-04-27  7:03 dpdklab
2024-04-27  7:03 dpdklab
2024-04-27  7:02 dpdklab
2024-04-27  7:02 dpdklab
2024-04-27  7:02 dpdklab
2024-04-27  7:02 dpdklab
2024-04-27  7:02 dpdklab
2024-04-27  7:01 dpdklab
2024-04-27  7:01 dpdklab
2024-04-27  7:01 dpdklab
2024-04-27  7:00 dpdklab
2024-04-27  7:00 dpdklab
2024-04-27  6:59 dpdklab
2024-04-27  6:59 dpdklab
2024-04-27  6:59 dpdklab
2024-04-27  6:59 dpdklab
2024-04-27  6:59 dpdklab
2024-04-27  6:58 dpdklab
2024-04-27  6:58 dpdklab
2024-04-27  6:58 dpdklab
2024-04-27  6:58 dpdklab
2024-04-27  6:58 dpdklab
2024-04-27  6:57 dpdklab
2024-04-27  6:57 dpdklab
2024-04-27  6:57 dpdklab
2024-04-27  6:57 dpdklab
2024-04-27  6:57 dpdklab
2024-04-27  6:56 dpdklab
2024-04-27  6:56 dpdklab
2024-04-27  6:55 dpdklab
2024-04-27  6:55 dpdklab
2024-04-27  6:55 dpdklab
2024-04-27  6:55 dpdklab
2024-04-27  6:54 dpdklab
2024-04-27  6:54 dpdklab
2024-04-27  6:54 dpdklab
2024-04-27  6:54 dpdklab
2024-04-27  6:53 dpdklab
2024-04-27  6:53 dpdklab
2024-04-27  6:53 dpdklab
2024-04-27  6:52 dpdklab
2024-04-27  6:51 dpdklab
2024-04-27  6: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=662cae9c.050a0220.af9d7.aba8SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ferruh.yigit@amd.com \
    --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).