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| pw130651 [PATCH] mempool/cnxk: support CNF10KA SoC
Date: Tue, 22 Aug 2023 16:19:03 -0700 (PDT)	[thread overview]
Message-ID: <64e54267.250a0220.6b0a3.2c20SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Performance Testing PASS_

Submitter: Ashwin Sekhar T K <asekhar@marvell.com>
Date: Tuesday, August 22 2023 17:07:10 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:971d2b57972919527e27ed683032a71864a2eb56

130651 --> 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.1%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-22 23:19 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22 23:19 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-23 18:36 dpdklab
2023-08-23 18:19 dpdklab
2023-08-23 18:14 dpdklab
2023-08-23 18:09 dpdklab
2023-08-23 18:05 dpdklab
2023-08-23 10:05 dpdklab
2023-08-23  4:57 dpdklab
2023-08-23  3:54 dpdklab
2023-08-23  3:36 dpdklab
2023-08-23  3:35 dpdklab
2023-08-23  3:32 dpdklab
2023-08-23  3:32 dpdklab
2023-08-23  3:31 dpdklab
2023-08-23  3:28 dpdklab
2023-08-23  3:27 dpdklab
2023-08-23  3:24 dpdklab
2023-08-23  3:22 dpdklab
2023-08-23  3:22 dpdklab
2023-08-23  3:18 dpdklab
2023-08-23  3:14 dpdklab
2023-08-23  3:10 dpdklab
2023-08-23  3:10 dpdklab
2023-08-23  3:03 dpdklab
2023-08-23  2:54 dpdklab
2023-08-23  2:36 dpdklab
2023-08-23  2:32 dpdklab
2023-08-23  2:29 dpdklab
2023-08-23  2:27 dpdklab
2023-08-23  2:25 dpdklab
2023-08-23  2:20 dpdklab
2023-08-23  2:18 dpdklab
2023-08-23  2:14 dpdklab
2023-08-23  2:04 dpdklab
2023-08-23  2:04 dpdklab
2023-08-23  2:03 dpdklab
2023-08-23  2:02 dpdklab
2023-08-23  1:54 dpdklab
2023-08-23  1:53 dpdklab
2023-08-23  1:53 dpdklab
2023-08-23  1:53 dpdklab
2023-08-23  1:52 dpdklab
2023-08-23  1:52 dpdklab
2023-08-23  1:52 dpdklab
2023-08-23  1:51 dpdklab
2023-08-23  1:51 dpdklab
2023-08-23  1:51 dpdklab
2023-08-23  1:51 dpdklab
2023-08-23  1:51 dpdklab
2023-08-23  1:50 dpdklab
2023-08-23  1:50 dpdklab
2023-08-23  1:50 dpdklab
2023-08-23  1:49 dpdklab
2023-08-23  1:49 dpdklab
2023-08-23  1:49 dpdklab
2023-08-23  0:53 dpdklab
2023-08-22 23:52 dpdklab
2023-08-22 23:51 dpdklab
2023-08-22 23:17 dpdklab
2023-08-22 23:17 dpdklab
     [not found] <20230822170710.2637687-1-asekhar@marvell.com>
2023-08-22 16:56 ` qemudev
2023-08-22 17:00 ` qemudev
2023-08-22 17:09 ` checkpatch
2023-08-22 18:00 ` 0-day Robot

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=64e54267.250a0220.6b0a3.2c20SMTPIN_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).