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] 22b0194263b83fa09a25511b26a38597fff44a2c
Date: Wed, 13 Mar 2024 23:48:43 -0700 (PDT)	[thread overview]
Message-ID: <65f29dcb.050a0220.f7f00.2acaSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing PASS_

Branch: dpdk-next-net

22b0194263b83fa09a25511b26a38597fff44a2c --> performance testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-78-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/6

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 256     | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 128        | 256     | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 256     | 1        | 1           | -0.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 256        | 256     | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 256     | 1        | 1           | -0.2%                        |
+------------+---------+----------+-------------+------------------------------+
| 512        | 256     | 1        | 1           | 0.3%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-03-14  6:48 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14  6:48 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-17 22:05 dpdklab
2024-03-17 21:29 dpdklab
2024-03-14  9:33 dpdklab
2024-03-14  8:01 dpdklab
2024-03-14  7:12 dpdklab
2024-03-14  7:05 dpdklab
2024-03-14  6:59 dpdklab
2024-03-14  6:58 dpdklab
2024-03-14  6:57 dpdklab
2024-03-14  6:56 dpdklab
2024-03-14  6:56 dpdklab
2024-03-14  6:55 dpdklab
2024-03-14  6:55 dpdklab
2024-03-14  6:55 dpdklab
2024-03-14  6:52 dpdklab
2024-03-14  6:52 dpdklab
2024-03-14  6:52 dpdklab
2024-03-14  6:52 dpdklab
2024-03-14  6:51 dpdklab
2024-03-14  6:51 dpdklab
2024-03-14  6:51 dpdklab
2024-03-14  6:51 dpdklab
2024-03-14  6:50 dpdklab
2024-03-14  6:50 dpdklab
2024-03-14  6:50 dpdklab
2024-03-14  6:50 dpdklab
2024-03-14  6:50 dpdklab
2024-03-14  6:49 dpdklab
2024-03-14  6:49 dpdklab
2024-03-14  6:49 dpdklab
2024-03-14  6:49 dpdklab
2024-03-14  6:49 dpdklab
2024-03-14  6:49 dpdklab
2024-03-14  6:48 dpdklab
2024-03-14  6:48 dpdklab
2024-03-14  6:48 dpdklab
2024-03-14  6:48 dpdklab
2024-03-14  6:47 dpdklab
2024-03-14  6:47 dpdklab
2024-03-14  6:46 dpdklab
2024-03-14  6:46 dpdklab
2024-03-14  6:45 dpdklab
2024-03-14  6:45 dpdklab
2024-03-14  6:45 dpdklab
2024-03-14  6:44 dpdklab
2024-03-14  6:44 dpdklab
2024-03-14  6:44 dpdklab
2024-03-14  6:44 dpdklab
2024-03-14  6:44 dpdklab
2024-03-14  6:43 dpdklab
2024-03-14  6:43 dpdklab
2024-03-14  6:43 dpdklab
2024-03-14  6:43 dpdklab
2024-03-14  6:42 dpdklab
2024-03-14  6:42 dpdklab
2024-03-14  6:42 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=65f29dcb.050a0220.f7f00.2acaSMTPIN_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).