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| pw133844 [PATCH] [v4,1/1] build: add libarchive to externa
Date: Fri, 03 Nov 2023 15:47:49 -0700 (PDT)	[thread overview]
Message-ID: <65457895.920a0220.160cc.6c70SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Performance Testing PASS_

Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Friday, November 03 2023 16:38:53 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e9555aad006a739de9ae2a14a94128931634eea0

133844 --> performance testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.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           | -0.2%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-03 22:47 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 22:47 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-04  3:42 dpdklab
2023-11-04  2:19 dpdklab
2023-11-04  0:31 dpdklab
2023-11-04  0:30 dpdklab
2023-11-03 23:57 dpdklab
2023-11-03 23:57 dpdklab
2023-11-03 23:57 dpdklab
2023-11-03 23:53 dpdklab
2023-11-03 23:33 dpdklab
2023-11-03 23:32 dpdklab
2023-11-03 23:31 dpdklab
2023-11-03 23:30 dpdklab
2023-11-03 23:24 dpdklab
2023-11-03 23:09 dpdklab
2023-11-03 23:09 dpdklab
2023-11-03 23:09 dpdklab
2023-11-03 23:08 dpdklab
2023-11-03 23:07 dpdklab
2023-11-03 23:07 dpdklab
2023-11-03 23:07 dpdklab
2023-11-03 23:07 dpdklab
2023-11-03 23:06 dpdklab
2023-11-03 23:06 dpdklab
2023-11-03 23:05 dpdklab
2023-11-03 23:04 dpdklab
2023-11-03 23:04 dpdklab
2023-11-03 23:03 dpdklab
2023-11-03 23:02 dpdklab
2023-11-03 23:02 dpdklab
2023-11-03 23:02 dpdklab
2023-11-03 23:01 dpdklab
2023-11-03 23:00 dpdklab
2023-11-03 22:58 dpdklab
2023-11-03 22:56 dpdklab
2023-11-03 22:56 dpdklab
2023-11-03 22:55 dpdklab
2023-11-03 22:54 dpdklab
2023-11-03 22:52 dpdklab
2023-11-03 22:51 dpdklab
2023-11-03 22:51 dpdklab
2023-11-03 22:49 dpdklab
2023-11-03 22:49 dpdklab
2023-11-03 22:49 dpdklab
2023-11-03 22:49 dpdklab
2023-11-03 22:49 dpdklab
2023-11-03 22:48 dpdklab
2023-11-03 22:48 dpdklab
2023-11-03 22:48 dpdklab
2023-11-03 22:48 dpdklab
2023-11-03 22:47 dpdklab
2023-11-03 22:40 dpdklab
2023-11-03 22:40 dpdklab
2023-11-03 22:38 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=65457895.920a0220.160cc.6c70SMTPIN_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).