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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126357-126362 [PATCH] [v2, 7/7] net/idpf: register timestamp mbuf when starting dev
Date: Fri, 21 Apr 2023 18:28:21 -0700 (PDT)	[thread overview]
Message-ID: <64433835.020a0220.a142.ebc4SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Performance Testing PASS_

Submitter: Wenjing Qiao <wenjing.qiao@intel.com>
Date: Friday, April 21 2023 07:16:03 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5f34cc454df420b9b2da8deb949fb76cba058b87

126357-126362 --> 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           | 4.2%                         |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -0.7%                        |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-04-22  1:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-22  1:28 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-22  6:18 dpdklab
2023-04-22  6:17 dpdklab
2023-04-22  4:53 dpdklab
2023-04-22  4:13 dpdklab
2023-04-22  3:25 dpdklab
2023-04-22  3:25 dpdklab
2023-04-22  3:19 dpdklab
2023-04-22  3:08 dpdklab
2023-04-22  3:08 dpdklab
2023-04-22  3:07 dpdklab
2023-04-22  2:58 dpdklab
2023-04-22  2:57 dpdklab
2023-04-22  2:41 dpdklab
2023-04-22  2:40 dpdklab
2023-04-22  2:38 dpdklab
2023-04-22  2:22 dpdklab
2023-04-22  1:57 dpdklab
2023-04-22  1:51 dpdklab
2023-04-22  1:46 dpdklab
2023-04-22  1:44 dpdklab
2023-04-22  1:42 dpdklab
2023-04-22  1:41 dpdklab
2023-04-22  1:38 dpdklab
2023-04-22  1:37 dpdklab
2023-04-22  1:37 dpdklab
2023-04-22  1:35 dpdklab
2023-04-22  1:30 dpdklab
2023-04-22  1:29 dpdklab
     [not found] <20230421071603.55680-8-wenjing.qiao@intel.com>
2023-04-21  7:12 ` |SUCCESS| pw126357-126362 [PATCH v2 " qemudev
2023-04-21  7:16 ` qemudev

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=64433835.020a0220.a142.ebc4SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).