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| pw140289 [PATCH] [v4] net/af_xdp: fix umem map size for ze
Date: Thu, 23 May 2024 02:30:58 -0700 (PDT)	[thread overview]
Message-ID: <664f0cd2.050a0220.cbf57.1563SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240523080751.2347970-1-frank.du@intel.com>

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

_Performance Testing PASS_

Submitter: Frank Du <frank.du@intel.com>
Date: Thursday, May 23 2024 08:07:51 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a012926d36f3feb9d17a51c8f1559f466570ec0a

140289 --> performance testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 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.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 128        | 256     | 1        | 1           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 256        | 256     | 1        | 1           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 512        | 256     | 1        | 1           | 0.3%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-23  9:31 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240523080751.2347970-1-frank.du@intel.com>
2024-05-23  8:01 ` |SUCCESS| pw140289 [PATCH v4] net/af_xdp: fix umem map size for zero copy qemudev
2024-05-23  8:06 ` qemudev
2024-05-23  8:26 ` checkpatch
2024-05-23  9:20 ` |SUCCESS| pw140289 [PATCH] [v4] net/af_xdp: fix umem map size for ze dpdklab
2024-05-23  9:21 ` dpdklab
2024-05-23  9:22 ` |FAILURE| " dpdklab
2024-05-23  9:24 ` |SUCCESS| pw140289 [PATCH v4] net/af_xdp: fix umem map size for zero copy 0-day Robot
2024-05-23  9:30 ` |SUCCESS| pw140289 [PATCH] [v4] net/af_xdp: fix umem map size for ze dpdklab
2024-05-23  9:30 ` dpdklab [this message]
2024-05-23  9:31 ` dpdklab
2024-05-23  9:32 ` |FAILURE| " dpdklab
2024-05-23  9:32 ` dpdklab
2024-05-23  9:32 ` |SUCCESS| " dpdklab
2024-05-23  9:33 ` dpdklab
2024-05-23  9:33 ` dpdklab
2024-05-23  9:33 ` dpdklab
2024-05-23  9:34 ` |FAILURE| " dpdklab
2024-05-23  9:35 ` |SUCCESS| " dpdklab
2024-05-23  9:35 ` |FAILURE| " dpdklab
2024-05-23  9:36 ` |SUCCESS| " dpdklab
2024-05-23  9:36 ` |FAILURE| " dpdklab
2024-05-23  9:36 ` |SUCCESS| " dpdklab
2024-05-23  9:37 ` |FAILURE| " dpdklab
2024-05-23  9:37 ` |SUCCESS| " dpdklab
2024-05-23  9:37 ` dpdklab
2024-05-23  9:38 ` dpdklab
2024-05-23  9:38 ` dpdklab
2024-05-23  9:38 ` dpdklab
2024-05-23  9:39 ` dpdklab
2024-05-23  9:39 ` dpdklab
2024-05-23  9:39 ` |FAILURE| " dpdklab
2024-05-23  9:40 ` |SUCCESS| " dpdklab
2024-05-23  9:40 ` |FAILURE| " dpdklab
2024-05-23  9:40 ` |SUCCESS| " dpdklab
2024-05-23  9:40 ` dpdklab
2024-05-23  9:41 ` dpdklab
2024-05-23  9:41 ` dpdklab
2024-05-23  9:41 ` dpdklab
2024-05-23  9:42 ` dpdklab
2024-05-23  9:42 ` dpdklab
2024-05-23  9:42 ` dpdklab
2024-05-23  9:46 ` dpdklab
2024-05-23  9:47 ` |FAILURE| " dpdklab
2024-05-23  9:47 ` |SUCCESS| " dpdklab
2024-05-23  9:48 ` |FAILURE| " dpdklab
2024-05-23  9:48 ` |SUCCESS| " dpdklab
2024-05-23  9:48 ` dpdklab
2024-05-23  9:48 ` dpdklab
2024-05-23  9:49 ` dpdklab
2024-05-23  9:56 ` dpdklab
2024-05-23  9:56 ` dpdklab
2024-05-23  9:57 ` dpdklab
2024-05-23  9:57 ` dpdklab
2024-05-23  9:58 ` |FAILURE| " dpdklab
2024-05-23  9:58 ` |SUCCESS| " dpdklab
2024-05-23  9:59 ` dpdklab
2024-05-23  9:59 ` |FAILURE| " dpdklab
2024-05-23  9:59 ` dpdklab
2024-05-23 10:00 ` dpdklab
2024-05-23 10:00 ` dpdklab
2024-05-23 10:01 ` dpdklab
2024-05-23 10:02 ` |SUCCESS| " dpdklab
2024-05-23 10:05 ` |FAILURE| " dpdklab
2024-05-23 10:05 ` |SUCCESS| " dpdklab
2024-05-23 10:06 ` dpdklab
2024-05-23 10:06 ` dpdklab
2024-05-23 10:06 ` dpdklab
2024-05-23 10:07 ` dpdklab
2024-05-23 10:08 ` |FAILURE| " dpdklab
2024-05-23 10:11 ` |SUCCESS| " dpdklab
2024-05-23 10:12 ` dpdklab
2024-05-23 10:12 ` |FAILURE| " dpdklab
2024-05-23 10:12 ` |SUCCESS| " dpdklab
2024-05-23 10:12 ` dpdklab
2024-05-23 10:13 ` dpdklab
2024-05-23 10:13 ` dpdklab
2024-05-23 10:15 ` dpdklab
2024-05-23 10:15 ` dpdklab
2024-05-23 10:15 ` dpdklab
2024-05-23 10:15 ` dpdklab
2024-05-23 10:25 ` dpdklab
2024-05-23 10:27 ` dpdklab
2024-05-23 10:40 ` dpdklab
2024-05-23 10:41 ` dpdklab
2024-05-23 10:44 ` dpdklab
2024-05-23 10:44 ` dpdklab
2024-05-23 10:45 ` dpdklab
2024-05-23 10:45 ` dpdklab
2024-05-23 10:49 ` dpdklab
2024-05-23 10:50 ` dpdklab
2024-05-23 11:06 ` 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=664f0cd2.050a0220.cbf57.1563SMTPIN_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).