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| pw135335-135336 [PATCH] [2/2] ip_frag: updated name for IP
Date: Tue, 19 Dec 2023 08:11:52 -0800 (PST)	[thread overview]
Message-ID: <6581c0c8.170a0220.5aeec.d91dSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-intel-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/135336

_Performance Testing PASS_

Submitter: Euan Bourke <euan.bourke@intel.com>
Date: Tuesday, December 19 2023 15:17:54 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e

135335-135336 --> performance testing pass

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 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.3%                         |
+------------+---------+----------+-------------+------------------------------+

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

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 16:11 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 16:11 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-19 18:50 dpdklab
2023-12-19 17:47 dpdklab
2023-12-19 17:41 dpdklab
2023-12-19 17:11 dpdklab
2023-12-19 16:55 dpdklab
2023-12-19 16:52 dpdklab
2023-12-19 16:51 dpdklab
2023-12-19 16:51 dpdklab
2023-12-19 16:51 dpdklab
2023-12-19 16:51 dpdklab
2023-12-19 16:48 dpdklab
2023-12-19 16:46 dpdklab
2023-12-19 16:44 dpdklab
2023-12-19 16:43 dpdklab
2023-12-19 16:43 dpdklab
2023-12-19 16:41 dpdklab
2023-12-19 16:40 dpdklab
2023-12-19 16:39 dpdklab
2023-12-19 16:38 dpdklab
2023-12-19 16:38 dpdklab
2023-12-19 16:37 dpdklab
2023-12-19 16:37 dpdklab
2023-12-19 16:36 dpdklab
2023-12-19 16:35 dpdklab
2023-12-19 16:35 dpdklab
2023-12-19 16:34 dpdklab
2023-12-19 16:34 dpdklab
2023-12-19 16:33 dpdklab
2023-12-19 16:33 dpdklab
2023-12-19 16:32 dpdklab
2023-12-19 16:32 dpdklab
2023-12-19 16:31 dpdklab
2023-12-19 16:31 dpdklab
2023-12-19 16:30 dpdklab
2023-12-19 16:30 dpdklab
2023-12-19 16:30 dpdklab
2023-12-19 16:30 dpdklab
2023-12-19 16:28 dpdklab
2023-12-19 16:25 dpdklab
2023-12-19 16:18 dpdklab
2023-12-19 16:17 dpdklab
2023-12-19 16:17 dpdklab
2023-12-19 16:17 dpdklab
2023-12-19 16:17 dpdklab
2023-12-19 16:12 dpdklab
2023-12-19 16:11 dpdklab
2023-12-19 16:11 dpdklab
2023-12-19 16:08 dpdklab
2023-12-19 16:08 dpdklab
2023-12-19 16:06 dpdklab
2023-12-19 16:04 dpdklab
2023-12-19 16:04 dpdklab
2023-12-19 16:04 dpdklab
2023-12-19 16:03 dpdklab
2023-12-19 16:03 dpdklab
2023-12-19 16:03 dpdklab
2023-12-19 16:01 dpdklab
2023-12-19 16:01 dpdklab
2023-12-19 16:00 dpdklab
2023-12-19 15:58 dpdklab
2023-12-19 15:58 dpdklab
2023-12-19 15:57 dpdklab
2023-12-19 15:57 dpdklab
2023-12-19 15:56 dpdklab
2023-12-19 15:55 dpdklab
2023-12-19 15:55 dpdklab
2023-12-19 15:55 dpdklab
2023-12-19 15:54 dpdklab
2023-12-19 15: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=6581c0c8.170a0220.5aeec.d91dSMTPIN_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).