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| pw135331-135332 [PATCH] [2/2] examples/ipsec-secgw: update
Date: Mon, 18 Dec 2023 22:42:08 -0800 (PST)	[thread overview]
Message-ID: <65813b40.050a0220.6538d.f48aSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Performance Testing PASS_

Submitter: Anoob Joseph <anoobj@marvell.com>
Date: Tuesday, December 19 2023 05:29:23 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e

135331-135332 --> 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.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-19  6:42 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19  6:42 dpdklab [this message]
2023-12-19  6:42 dpdklab
2023-12-19  6:42 dpdklab
2023-12-19  6:44 dpdklab
2023-12-19  6:45 dpdklab
2023-12-19  6:45 dpdklab
2023-12-19  6:46 dpdklab
2023-12-19  6:48 dpdklab
2023-12-19  6:48 dpdklab
2023-12-19  6:48 dpdklab
2023-12-19  6:50 dpdklab
2023-12-19  6:50 dpdklab
2023-12-19  6:51 dpdklab
2023-12-19  6:51 dpdklab
2023-12-19  6:56 dpdklab
2023-12-19  6:58 dpdklab
2023-12-19  6:58 dpdklab
2023-12-19  6:58 dpdklab
2023-12-19  7:00 dpdklab
2023-12-19  7:01 dpdklab
2023-12-19  7:01 dpdklab
2023-12-19  7:03 dpdklab
2023-12-19  7:15 dpdklab
2023-12-19  7:19 dpdklab
2023-12-19  7:57 dpdklab
2023-12-19  7:58 dpdklab
2023-12-19  8:00 dpdklab
2023-12-19  8:03 dpdklab
2023-12-19  8:04 dpdklab
2023-12-19  8:06 dpdklab
2023-12-19  8:06 dpdklab
2023-12-19  8:06 dpdklab
2023-12-19  8:07 dpdklab
2023-12-19  8:08 dpdklab
2023-12-19  8:11 dpdklab
2023-12-19  8:13 dpdklab
2023-12-19  8:13 dpdklab
2023-12-19  8:18 dpdklab
2023-12-19  8:20 dpdklab
2023-12-19  8:21 dpdklab
2023-12-19  8:24 dpdklab
2023-12-19  8:25 dpdklab
2023-12-19  8:26 dpdklab
2023-12-19  8:29 dpdklab
2023-12-19  8:31 dpdklab
2023-12-19  8:31 dpdklab
2023-12-19  8:33 dpdklab
2023-12-19  8:33 dpdklab
2023-12-19  8:34 dpdklab
2023-12-19  8:35 dpdklab
2023-12-19  8:35 dpdklab
2023-12-19  8:36 dpdklab
2023-12-19  8:37 dpdklab
2023-12-19  8:40 dpdklab
2023-12-19  8:41 dpdklab
2023-12-19  8:42 dpdklab
2023-12-19  8:43 dpdklab
2023-12-19  8:45 dpdklab
2023-12-19  8:48 dpdklab
2023-12-19  8:49 dpdklab
2023-12-19  8:50 dpdklab
2023-12-19  8:55 dpdklab
2023-12-19  8:55 dpdklab
2023-12-19  8:57 dpdklab
2023-12-19  8:59 dpdklab
2023-12-19  9:11 dpdklab
2023-12-19  9:24 dpdklab
2023-12-19 11:37 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=65813b40.050a0220.6538d.f48aSMTPIN_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).