automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw97563-97564 [PATCH] [v3, 2/2] test/eal: add a test for rte_ctrl_thread_create
Date: Mon, 30 Aug 2021 15:08:52 -0400 (EDT)	[thread overview]
Message-ID: <20210830190852.D00B91D4@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 1815 bytes --]

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

_Performance Testing PASS_

Submitter: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Date: Monday, August 30 2021 16:34:13 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:bfd3c352eb9729f97da6e1b5e958e121542d8a8d

97563-97564 --> performance testing pass

Test environment and result as below:

Ubuntu 20.04
Kernel: 4.15.0-65-generic
Compiler: gcc gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
NIC: Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 512     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 512     | 1        | 2           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 2           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-08-30 19:08 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30 19:08 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-31 18:11 dpdklab
2021-08-31  6:41 dpdklab
2021-08-31  6:21 dpdklab
2021-08-31  6:02 dpdklab
2021-08-31  5:46 dpdklab
2021-08-31  5:28 dpdklab
2021-08-31  5:06 dpdklab
2021-08-31  4:52 dpdklab
2021-08-31  4:26 dpdklab
2021-08-31  4:08 dpdklab
2021-08-30 22:28 dpdklab
2021-08-30 20:48 dpdklab
2021-08-30 20:31 dpdklab
2021-08-30 20:28 dpdklab
2021-08-30 20:10 dpdklab
2021-08-30 20:08 dpdklab
2021-08-30 20:04 dpdklab
2021-08-30 19:45 dpdklab
2021-08-30 19:45 dpdklab
2021-08-30 19:39 dpdklab
2021-08-30 19:37 dpdklab
2021-08-30 19:36 dpdklab
2021-08-30 19:23 dpdklab
2021-08-30 19:13 dpdklab
2021-08-30 19:13 dpdklab
2021-08-30 18:52 dpdklab
2021-08-30 18:51 dpdklab
2021-08-30 18:39 dpdklab
2021-08-30 18:36 dpdklab
2021-08-30 18:31 dpdklab
2021-08-30 18:13 dpdklab
2021-08-30 17:55 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=20210830190852.D00B91D4@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=ajit.khaparde@broadcom.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).