automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129436 [PATCH] [v2] ipsec: fix NAT-T header length calcu
Date: Tue, 11 Jul 2023 08:06:21 -0700 (PDT)	[thread overview]
Message-ID: <64ad6fed.c80a0220.7db4c.3cc9SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/129436

_Performance Testing PASS_

Submitter: Xiao Liang <shaw.leon@gmail.com>
Date: Tuesday, July 11 2023 02:18:47 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:623dc9364dc6a818799941cc26dc8f70feb2bb24

129436 --> performance testing pass

Test environment and result as below:

Ubuntu 18.04
Kernel: 4.15.0-166-generic
Compiler: gcc 7.5.0
NIC: Mellanox ConnectX-5 100000 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.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 128        | 256     | 1        | 1           | -0.3%                        |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 256     | 1        | 1           | 0.3%                         |
+------------+---------+----------+-------------+------------------------------+
| 256        | 256     | 1        | 1           | -0.3%                        |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 256     | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 512        | 256     | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-07-11 15:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-11 15:06 dpdklab [this message]
2023-07-11 15:06 dpdklab
2023-07-11 15:07 dpdklab
2023-07-11 15:10 dpdklab
2023-07-11 15:14 dpdklab
2023-07-11 15:15 dpdklab
2023-07-11 15:46 dpdklab
2023-07-11 15:47 dpdklab
2023-07-11 15:49 dpdklab
2023-07-11 15:50 dpdklab
2023-07-11 15:52 dpdklab
2023-07-11 16:03 dpdklab
2023-07-11 16:10 dpdklab
2023-07-11 16:45 dpdklab
2023-07-11 18:21 dpdklab
2023-07-12  4:36 dpdklab
2023-07-12  4:38 dpdklab
2023-07-12  5:37 dpdklab
2023-07-12  7:49 dpdklab
2023-07-13 15:40 dpdklab
2023-07-13 15:41 dpdklab
2023-07-13 17:19 dpdklab
2023-07-13 17:22 dpdklab
2023-07-14 13:43 dpdklab
2023-07-14 13:49 dpdklab
2023-07-14 13:54 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=64ad6fed.c80a0220.7db4c.3cc9SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=alialnu@nvidia.com \
    --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).