automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@dpdk.org,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw114521 [PATCH] [v1] buildtools: ensure the NUMA nodes are counted correct
Date: Tue,  2 Aug 2022 09:16:13 +0000 (UTC)	[thread overview]
Message-ID: <20220802091613.583E460302@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

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

_Performance Testing PASS_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Tuesday, August 02 2022 07:54:15 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:72206323a5dd3182b13f61b25a64abdddfee595c

114521 --> performance testing pass

Test environment and result as below:

Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-5 100000 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.1%                         |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 256     | 1        | 1           | -0.3%                        |
+------------+---------+----------+-------------+------------------------------+
| 256        | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 256     | 1        | 1           | -0.1%                        |
+------------+---------+----------+-------------+------------------------------+
| 512        | 256     | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-08-02  9:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02  9:16 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-02 11:03 dpdklab
2022-08-02 10:43 dpdklab
2022-08-02 10:38 dpdklab
2022-08-02 10:36 dpdklab
2022-08-02 10:31 dpdklab
2022-08-02 10:17 dpdklab
2022-08-02 10:16 dpdklab
2022-08-02 10:06 dpdklab
2022-08-02  9:59 dpdklab
2022-08-02  9:57 dpdklab
2022-08-02  9:53 dpdklab
2022-08-02  9:49 dpdklab
2022-08-02  9:48 dpdklab
2022-08-02  9:43 dpdklab
2022-08-02  9:42 dpdklab
2022-08-02  9:42 dpdklab
2022-08-02  9:39 dpdklab
2022-08-02  9:37 dpdklab
2022-08-02  9:30 dpdklab
2022-08-02  9:29 dpdklab
2022-08-02  9:24 dpdklab
2022-08-02  9:24 dpdklab
2022-08-02  9:18 dpdklab
2022-08-02  9:08 dpdklab
2022-08-02  8:58 dpdklab
     [not found] <1659426855-11014-1-git-send-email-chaoyong.he@corigine.com>
2022-08-02  7:56 ` |SUCCESS| pw114521 [PATCH v1] " checkpatch
2022-08-02  9:19 ` 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=20220802091613.583E460302@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=alialnu@nvidia.com \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).