From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143109-143110 [PATCH] [v2,3/3] test/bbdev: update for qu
Date: Tue, 13 Aug 2024 10:03:33 -0700 (PDT) [thread overview]
Message-ID: <66bb91e5.170a0220.215eb7.70c7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240812234201.2196633-4-nicolas.chautru@intel.com>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/143110
_Performance Testing PASS_
Submitter: Nicolas Chautru <nicolas.chautru@intel.com>
Date: Monday, August 12 2024 23:42:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143109-143110 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#174901
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | -0.4% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Fail/Total: 0/3
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 128 | 1 | 1 | 0.9% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 512 | 1 | 1 | 1.2% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.6% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30780/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-08-13 17:04 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240812234201.2196633-4-nicolas.chautru@intel.com>
2024-08-12 23:13 ` |SUCCESS| pw143109-143110 [PATCH v2 3/3] test/bbdev: update for queue stats qemudev
2024-08-12 23:17 ` qemudev
2024-08-12 23:41 ` |SUCCESS| pw143110 " checkpatch
2024-08-13 0:42 ` 0-day Robot
2024-08-13 16:16 ` |SUCCESS| pw143109-143110 [PATCH] [v2,3/3] test/bbdev: update for qu dpdklab
2024-08-13 16:16 ` dpdklab
2024-08-13 16:18 ` |PENDING| " dpdklab
2024-08-13 16:20 ` |SUCCESS| " dpdklab
2024-08-13 16:22 ` dpdklab
2024-08-13 16:24 ` dpdklab
2024-08-13 16:24 ` dpdklab
2024-08-13 16:26 ` |PENDING| " dpdklab
2024-08-13 16:27 ` |SUCCESS| " dpdklab
2024-08-13 16:28 ` |PENDING| " dpdklab
2024-08-13 16:30 ` dpdklab
2024-08-13 16:31 ` dpdklab
2024-08-13 16:32 ` dpdklab
2024-08-13 16:34 ` |SUCCESS| " dpdklab
2024-08-13 16:34 ` |PENDING| " dpdklab
2024-08-13 16:35 ` dpdklab
2024-08-13 16:36 ` dpdklab
2024-08-13 16:36 ` dpdklab
2024-08-13 16:37 ` |SUCCESS| " dpdklab
2024-08-13 16:38 ` |PENDING| " dpdklab
2024-08-13 16:38 ` dpdklab
2024-08-13 16:39 ` dpdklab
2024-08-13 16:39 ` |SUCCESS| " dpdklab
2024-08-13 16:39 ` |PENDING| " dpdklab
2024-08-13 16:40 ` dpdklab
2024-08-13 16:41 ` dpdklab
2024-08-13 16:41 ` |SUCCESS| " dpdklab
2024-08-13 16:41 ` |PENDING| " dpdklab
2024-08-13 16:42 ` dpdklab
2024-08-13 16:42 ` dpdklab
2024-08-13 16:42 ` dpdklab
2024-08-13 16:42 ` dpdklab
2024-08-13 16:42 ` dpdklab
2024-08-13 16:43 ` dpdklab
2024-08-13 16:43 ` dpdklab
2024-08-13 16:44 ` dpdklab
2024-08-13 16:44 ` dpdklab
2024-08-13 16:45 ` dpdklab
2024-08-13 16:47 ` dpdklab
2024-08-13 16:47 ` dpdklab
2024-08-13 16:49 ` dpdklab
2024-08-13 16:51 ` |SUCCESS| " dpdklab
2024-08-13 16:51 ` |PENDING| " dpdklab
2024-08-13 16:52 ` dpdklab
2024-08-13 16:52 ` dpdklab
2024-08-13 16:53 ` dpdklab
2024-08-13 16:53 ` dpdklab
2024-08-13 16:54 ` dpdklab
2024-08-13 16:54 ` dpdklab
2024-08-13 16:55 ` dpdklab
2024-08-13 16:56 ` dpdklab
2024-08-13 16:56 ` dpdklab
2024-08-13 16:57 ` dpdklab
2024-08-13 16:58 ` dpdklab
2024-08-13 16:59 ` dpdklab
2024-08-13 17:00 ` |SUCCESS| " dpdklab
2024-08-13 17:01 ` dpdklab
2024-08-13 17:01 ` |PENDING| " dpdklab
2024-08-13 17:02 ` dpdklab
2024-08-13 17:03 ` dpdklab [this message]
2024-08-13 17:03 ` dpdklab
2024-08-13 17:03 ` dpdklab
2024-08-13 17:04 ` dpdklab
2024-08-13 17:04 ` dpdklab
2024-08-13 17:04 ` dpdklab
2024-08-13 17:06 ` dpdklab
2024-08-13 17:06 ` dpdklab
2024-08-13 17:07 ` dpdklab
2024-08-13 17:07 ` dpdklab
2024-08-13 17:07 ` dpdklab
2024-08-13 17:08 ` dpdklab
2024-08-13 17:08 ` dpdklab
2024-08-13 17:10 ` dpdklab
2024-08-13 17:10 ` dpdklab
2024-08-13 17:10 ` dpdklab
2024-08-13 17:11 ` dpdklab
2024-08-13 17:11 ` |SUCCESS| " dpdklab
2024-08-13 17:12 ` |PENDING| " dpdklab
2024-08-13 17:12 ` dpdklab
2024-08-13 17:12 ` |SUCCESS| " dpdklab
2024-08-13 17:13 ` |PENDING| " dpdklab
2024-08-13 17:14 ` dpdklab
2024-08-13 17:15 ` |SUCCESS| " dpdklab
2024-08-13 17:16 ` |PENDING| " dpdklab
2024-08-13 17:18 ` dpdklab
2024-08-13 17:18 ` dpdklab
2024-08-13 17:21 ` |SUCCESS| " dpdklab
2024-08-13 17:32 ` dpdklab
2024-08-13 17:36 ` |PENDING| " dpdklab
2024-08-13 18:12 ` dpdklab
2024-08-13 18:26 ` |SUCCESS| " dpdklab
2024-08-13 19:36 ` 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=66bb91e5.170a0220.215eb7.70c7SMTPIN_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).