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| [GIT MASTER] 62774b78a84e9fa5df56d04cffed69bef8c901f1
Date: Thu, 31 Aug 2023 18:03:23 -0700 (PDT)	[thread overview]
Message-ID: <64f1385b.810a0220.bf22d.caafSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: dpdk

62774b78a84e9fa5df56d04cffed69bef8c901f1 --> performance testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 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.7%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.2%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-09-01  1:03 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01  1:03 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-01 14:11 dpdklab
2023-09-01 13:37 dpdklab
2023-09-01  2:32 dpdklab
2023-09-01  2:28 dpdklab
2023-09-01  2:19 dpdklab
2023-09-01  2:18 dpdklab
2023-09-01  2:01 dpdklab
2023-09-01  1:55 dpdklab
2023-09-01  1:24 dpdklab
2023-09-01  1:24 dpdklab
2023-09-01  1:22 dpdklab
2023-09-01  1:20 dpdklab
2023-09-01  1:20 dpdklab
2023-09-01  1:18 dpdklab
2023-09-01  1:18 dpdklab
2023-09-01  1:15 dpdklab
2023-09-01  1:14 dpdklab
2023-09-01  1:14 dpdklab
2023-09-01  1:14 dpdklab
2023-09-01  1:11 dpdklab
2023-09-01  1:10 dpdklab
2023-09-01  1:09 dpdklab
2023-09-01  1:08 dpdklab
2023-09-01  1:08 dpdklab
2023-09-01  1:07 dpdklab
2023-09-01  1:06 dpdklab
2023-09-01  1:05 dpdklab
2023-09-01  1:04 dpdklab
2023-09-01  1:04 dpdklab
2023-09-01  1:03 dpdklab
2023-09-01  1:03 dpdklab
2023-09-01  1:03 dpdklab
2023-09-01  1:02 dpdklab
2023-09-01  1:02 dpdklab
2023-09-01  1:02 dpdklab
2023-09-01  1:00 dpdklab
2023-09-01  1:00 dpdklab
2023-09-01  0:59 dpdklab
2023-09-01  0:59 dpdklab
2023-09-01  0:58 dpdklab
2023-09-01  0:58 dpdklab
2023-09-01  0:58 dpdklab
2023-09-01  0:58 dpdklab
2023-09-01  0:58 dpdklab
2023-09-01  0:58 dpdklab
2023-09-01  0:58 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=64f1385b.810a0220.bf22d.caafSMTPIN_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).