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| pw135977 [PATCH] test/security: add inline IPsec Rx inject
Date: Fri, 19 Jan 2024 09:18:47 -0800 (PST)	[thread overview]
Message-ID: <65aaaef7.050a0220.82ddd.8522SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Performance Testing PASS_

Submitter: Rahul Bhansali <rbhansali@marvell.com>
Date: Friday, January 19 2024 06:12:20 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:30a988126ecee65a890a4b6a52690442024f2554

135977 --> 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.3%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.0%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-19 17:18 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 17:18 dpdklab [this message]
2024-01-19 17:20 dpdklab
2024-01-19 17:23 dpdklab
2024-01-19 17:26 dpdklab
2024-01-19 17:31 dpdklab
2024-01-19 17:32 dpdklab
2024-01-19 17:55 dpdklab
2024-01-19 18:17 dpdklab
2024-01-19 18:26 dpdklab
2024-01-19 18:31 dpdklab
2024-01-19 18:32 dpdklab
2024-01-19 18:33 dpdklab
2024-01-19 18:34 dpdklab
2024-01-19 18:35 dpdklab
2024-01-19 18:35 dpdklab
2024-01-19 18:36 dpdklab
2024-01-19 18:38 dpdklab
2024-01-19 18:44 dpdklab
2024-01-19 18:47 dpdklab
2024-01-19 18:49 dpdklab
2024-01-19 18:57 dpdklab
2024-01-19 18:59 dpdklab
2024-01-19 18:59 dpdklab
2024-01-19 19:07 dpdklab
2024-01-19 19:09 dpdklab
2024-01-19 19:13 dpdklab
2024-01-19 19:16 dpdklab
2024-01-19 19:16 dpdklab
2024-01-19 19:16 dpdklab
2024-01-19 19:17 dpdklab
2024-01-19 19:18 dpdklab
2024-01-19 19:20 dpdklab
2024-01-19 19:20 dpdklab
2024-01-19 19:20 dpdklab
2024-01-19 19:25 dpdklab
2024-01-19 19:26 dpdklab
2024-01-19 19:27 dpdklab
2024-01-19 19:28 dpdklab
2024-01-19 19:28 dpdklab
2024-01-19 19:28 dpdklab
2024-01-19 19:30 dpdklab
2024-01-19 19:30 dpdklab
2024-01-19 19:30 dpdklab
2024-01-19 19:31 dpdklab
2024-01-19 19:31 dpdklab
2024-01-19 19:31 dpdklab
2024-01-19 19:32 dpdklab
2024-01-19 19:32 dpdklab
2024-01-19 19:32 dpdklab
2024-01-19 19:32 dpdklab
2024-01-19 19:33 dpdklab
2024-01-19 19:34 dpdklab
2024-01-19 19:38 dpdklab
2024-01-19 19:39 dpdklab
2024-01-19 19:39 dpdklab
2024-01-19 19:40 dpdklab
2024-01-19 19:41 dpdklab
2024-01-19 19:41 dpdklab
2024-01-19 19:41 dpdklab
2024-01-19 20:03 dpdklab
2024-01-19 20:04 dpdklab
2024-01-19 20:05 dpdklab
2024-01-19 20:06 dpdklab
2024-01-19 20:16 dpdklab
2024-01-19 20:29 dpdklab
2024-01-19 20:30 dpdklab
2024-01-19 20:35 dpdklab
2024-01-19 20:49 dpdklab
2024-01-20  9:28 dpdklab
2024-01-22 15:46 dpdklab
2024-01-22 15:53 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=65aaaef7.050a0220.82ddd.8522SMTPIN_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).