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| pw137356 [PATCH] doc: replace code blocks with includes in
Date: Thu, 29 Feb 2024 04:05:58 -0800 (PST)	[thread overview]
Message-ID: <65e07326.050a0220.661d.4630SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240227142138.1942161-1-david.marchand@redhat.com>

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

_Performance Testing PASS_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Tuesday, February 27 2024 14:21:38 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137356 --> performance testing pass

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.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           | -2.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -1.4%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-02-29 12:05 UTC|newest]

Thread overview: 139+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240227142138.1942161-1-david.marchand@redhat.com>
2024-02-27 13:59 ` |SUCCESS| pw137356 [PATCH] doc: replace code blocks with includes in logging guide qemudev
2024-02-27 14:03 ` qemudev
2024-02-27 14:23 ` checkpatch
2024-02-27 15:25 ` 0-day Robot
2024-02-27 21:20 ` |SUCCESS| pw137356 [PATCH] doc: replace code blocks with includes in dpdklab
2024-02-27 21:21 ` dpdklab
2024-02-27 21:21 ` dpdklab
2024-02-27 21:21 ` dpdklab
2024-02-27 21:22 ` dpdklab
2024-02-27 21:22 ` dpdklab
2024-02-27 21:22 ` dpdklab
2024-02-27 21:22 ` dpdklab
2024-02-27 21:23 ` dpdklab
2024-02-27 21:23 ` dpdklab
2024-02-27 21:23 ` dpdklab
2024-02-27 21:31 ` dpdklab
2024-02-27 21:32 ` dpdklab
2024-02-27 21:32 ` dpdklab
2024-02-27 21:32 ` dpdklab
2024-02-27 21:33 ` dpdklab
2024-02-27 21:34 ` dpdklab
2024-02-27 21:34 ` dpdklab
2024-02-27 21:39 ` dpdklab
2024-02-27 21:39 ` dpdklab
2024-02-27 21:40 ` dpdklab
2024-02-27 21:41 ` dpdklab
2024-02-27 21:41 ` dpdklab
2024-02-27 21:41 ` dpdklab
2024-02-27 21:41 ` dpdklab
2024-02-27 21:42 ` dpdklab
2024-02-27 21:42 ` dpdklab
2024-02-27 21:42 ` dpdklab
2024-02-27 21:42 ` dpdklab
2024-02-27 21:43 ` dpdklab
2024-02-27 21:43 ` dpdklab
2024-02-27 21:44 ` dpdklab
2024-02-27 21:45 ` dpdklab
2024-02-27 21:45 ` dpdklab
2024-02-27 21:45 ` dpdklab
2024-02-27 21:45 ` dpdklab
2024-02-27 21:45 ` dpdklab
2024-02-27 21:46 ` dpdklab
2024-02-27 21:46 ` dpdklab
2024-02-27 21:46 ` dpdklab
2024-02-27 21:46 ` dpdklab
2024-02-27 21:46 ` dpdklab
2024-02-27 21:46 ` dpdklab
2024-02-27 21:47 ` dpdklab
2024-02-27 21:49 ` dpdklab
2024-02-27 21:49 ` dpdklab
2024-02-27 21:49 ` dpdklab
2024-02-27 21:50 ` dpdklab
2024-02-27 21:50 ` dpdklab
2024-02-27 21:50 ` dpdklab
2024-02-27 21:50 ` dpdklab
2024-02-27 21:51 ` dpdklab
2024-02-27 21:51 ` dpdklab
2024-02-27 21:51 ` dpdklab
2024-02-27 21:52 ` dpdklab
2024-02-27 21:52 ` dpdklab
2024-02-27 21:52 ` dpdklab
2024-02-27 21:52 ` dpdklab
2024-02-27 21:52 ` dpdklab
2024-02-27 21:52 ` dpdklab
2024-02-27 21:53 ` dpdklab
2024-02-27 21:53 ` dpdklab
2024-02-27 21:53 ` dpdklab
2024-02-27 21:53 ` dpdklab
2024-02-27 21:53 ` dpdklab
2024-02-27 21:54 ` dpdklab
2024-02-27 22:01 ` dpdklab
2024-02-27 22:04 ` dpdklab
2024-02-27 22:04 ` dpdklab
2024-02-27 22:07 ` dpdklab
2024-02-27 22:07 ` dpdklab
2024-02-27 22:07 ` dpdklab
2024-02-27 22:07 ` dpdklab
2024-02-27 22:08 ` dpdklab
2024-02-27 22:08 ` dpdklab
2024-02-27 22:09 ` dpdklab
2024-02-27 22:09 ` dpdklab
2024-02-27 22:10 ` dpdklab
2024-02-27 22:19 ` dpdklab
2024-02-27 22:19 ` dpdklab
2024-02-27 22:20 ` dpdklab
2024-02-27 22:29 ` dpdklab
2024-02-27 22:40 ` dpdklab
2024-02-27 22:49 ` dpdklab
2024-02-27 22:57 ` dpdklab
2024-02-27 23:43 ` dpdklab
2024-02-28  4:27 ` dpdklab
2024-02-28  4:49 ` dpdklab
2024-02-28  8:26 ` dpdklab
2024-02-28  8:43 ` dpdklab
2024-02-28  8:51 ` dpdklab
2024-02-28  9:25 ` dpdklab
2024-02-28 12:52 ` dpdklab
2024-02-28 14:29 ` dpdklab
2024-02-28 22:21 ` dpdklab
2024-02-28 23:58 ` dpdklab
2024-02-29 12:05 ` dpdklab [this message]
2024-02-29 12:11 ` dpdklab
2024-02-29 12:13 ` dpdklab
2024-02-29 12:31 ` dpdklab
2024-02-29 12:35 ` dpdklab
2024-02-29 12:37 ` dpdklab
2024-02-29 12:39 ` dpdklab
2024-02-29 12:42 ` dpdklab
2024-02-27 19:09 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2024-02-27 18:47 dpdklab
2024-02-27 18:47 dpdklab
2024-02-27 18:41 dpdklab
2024-02-27 18:39 dpdklab
2024-02-27 18:30 dpdklab
2024-02-27 18:29 dpdklab
2024-02-27 18:27 dpdklab
2024-02-27 18:26 dpdklab
2024-02-27 18:25 dpdklab
2024-02-27 18:24 dpdklab
2024-02-27 18:21 dpdklab
2024-02-27 18:21 dpdklab
2024-02-27 18:20 dpdklab
2024-02-27 18:20 dpdklab
2024-02-27 18:19 dpdklab
2024-02-27 18:19 dpdklab
2024-02-27 18:18 dpdklab
2024-02-27 18:18 dpdklab
2024-02-27 18:18 dpdklab
2024-02-27 18:17 dpdklab
2024-02-27 18:17 dpdklab
2024-02-27 18:12 dpdklab
2024-02-27 18:11 dpdklab
2024-02-27 17:58 dpdklab
2024-02-27 17:57 dpdklab
2024-02-27 17:55 dpdklab
2024-02-27 17:42 dpdklab
2024-02-27 17:40 dpdklab
2024-02-27 17:37 dpdklab
2024-02-27 17:35 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=65e07326.050a0220.661d.4630SMTPIN_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).