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| pw135133 [PATCH] [v3] examples/packet_ordering: fix segfau
Date: Wed, 13 Dec 2023 09:58:46 -0800 (PST)	[thread overview]
Message-ID: <6579f0d6.050a0220.41a1.46ceSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Performance Testing PASS_

Submitter: Qian Hao <qi_an_hao@126.com>
Date: Wednesday, December 13 2023 11:07:18 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:f2d5afbb2c05d7647da7ea914887c52115652651

135133 --> performance testing pass

Test environment and result as below:

Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-13 17:58 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13 17:58 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-13 22:22 dpdklab
2023-12-13 21:12 dpdklab
2023-12-13 20:53 dpdklab
2023-12-13 20:16 dpdklab
2023-12-13 20:15 dpdklab
2023-12-13 20:15 dpdklab
2023-12-13 20:13 dpdklab
2023-12-13 20:12 dpdklab
2023-12-13 20:11 dpdklab
2023-12-13 20:10 dpdklab
2023-12-13 20:07 dpdklab
2023-12-13 20:07 dpdklab
2023-12-13 20:05 dpdklab
2023-12-13 20:04 dpdklab
2023-12-13 20:04 dpdklab
2023-12-13 20:01 dpdklab
2023-12-13 20:01 dpdklab
2023-12-13 19:57 dpdklab
2023-12-13 19:40 dpdklab
2023-12-13 19:39 dpdklab
2023-12-13 19:37 dpdklab
2023-12-13 19:37 dpdklab
2023-12-13 19:37 dpdklab
2023-12-13 19:36 dpdklab
2023-12-13 19:36 dpdklab
2023-12-13 19:36 dpdklab
2023-12-13 19:35 dpdklab
2023-12-13 19:35 dpdklab
2023-12-13 19:34 dpdklab
2023-12-13 19:26 dpdklab
2023-12-13 19:25 dpdklab
2023-12-13 19:21 dpdklab
2023-12-13 19:20 dpdklab
2023-12-13 19:14 dpdklab
2023-12-13 18:56 dpdklab
2023-12-13 18:51 dpdklab
2023-12-13 18:50 dpdklab
2023-12-13 18:49 dpdklab
2023-12-13 18:48 dpdklab
2023-12-13 18:47 dpdklab
2023-12-13 18:41 dpdklab
2023-12-13 18:39 dpdklab
2023-12-13 18:33 dpdklab
2023-12-13 18:32 dpdklab
2023-12-13 18:32 dpdklab
2023-12-13 18:32 dpdklab
2023-12-13 18:31 dpdklab
2023-12-13 18:31 dpdklab
2023-12-13 18:28 dpdklab
2023-12-13 18:27 dpdklab
2023-12-13 18:26 dpdklab
2023-12-13 18:26 dpdklab
2023-12-13 18:25 dpdklab
2023-12-13 18:22 dpdklab
2023-12-13 18:21 dpdklab
2023-12-13 18:19 dpdklab
2023-12-13 18:19 dpdklab
2023-12-13 18:17 dpdklab
2023-12-13 18:16 dpdklab
2023-12-13 18:08 dpdklab
2023-12-13 18:01 dpdklab
2023-12-13 17:58 dpdklab
2023-12-13 17:57 dpdklab
2023-12-13 17:52 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=6579f0d6.050a0220.41a1.46ceSMTPIN_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).