From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137293-137294 [PATCH] [2/2] app/pdump: handle SIGTERM an
Date: Mon, 26 Feb 2024 23:39:36 -0800 (PST) [thread overview]
Message-ID: <65dd91b8.170a0220.558c8.2239SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-mellanox-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/137294
_Performance Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Monday, February 26 2024 20:49:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137293-137294 --> performance testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-78-generic
Compiler: gcc 11.4.0
NIC: Mellanox ConnectX-6 Lx 25000 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.0% |
+------------+---------+----------+-------------+------------------------------+
| 1024 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 256 | 256 | 1 | 1 | -0.0% |
+------------+---------+----------+-------------+------------------------------+
| 1518 | 256 | 1 | 1 | -0.2% |
+------------+---------+----------+-------------+------------------------------+
| 512 | 256 | 1 | 1 | 0.3% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29273/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-27 7:40 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 7:39 dpdklab [this message]
[not found] <20240226205143.66702-3-stephen@networkplumber.org>
2024-02-28 2:30 ` dpdklab
2024-02-28 2:33 ` dpdklab
2024-02-29 6:17 ` dpdklab
2024-02-29 6:19 ` dpdklab
2024-02-29 6:25 ` dpdklab
2024-02-29 6:28 ` dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-27 11:43 dpdklab
2024-02-27 11:28 dpdklab
2024-02-27 10:45 dpdklab
2024-02-27 10:27 dpdklab
2024-02-27 10:18 dpdklab
2024-02-27 10:18 dpdklab
2024-02-27 10:18 dpdklab
2024-02-27 10:17 dpdklab
2024-02-27 10:17 dpdklab
2024-02-27 10:17 dpdklab
2024-02-27 10:16 dpdklab
2024-02-27 10:13 dpdklab
2024-02-27 10:10 dpdklab
2024-02-27 10:10 dpdklab
2024-02-27 10:09 dpdklab
2024-02-27 10:08 dpdklab
2024-02-27 10:08 dpdklab
2024-02-27 10:07 dpdklab
2024-02-27 10:06 dpdklab
2024-02-27 10:05 dpdklab
2024-02-27 10:05 dpdklab
2024-02-27 10:03 dpdklab
2024-02-27 10:03 dpdklab
2024-02-27 10:03 dpdklab
2024-02-27 10:02 dpdklab
2024-02-27 10:00 dpdklab
2024-02-27 10:00 dpdklab
2024-02-27 9:52 dpdklab
2024-02-27 9:51 dpdklab
2024-02-27 9:49 dpdklab
2024-02-27 9:49 dpdklab
2024-02-27 9:48 dpdklab
2024-02-27 9:47 dpdklab
2024-02-27 9:44 dpdklab
2024-02-27 9:43 dpdklab
2024-02-27 9:34 dpdklab
2024-02-27 9:34 dpdklab
2024-02-27 9:32 dpdklab
2024-02-27 8:59 dpdklab
2024-02-27 8:54 dpdklab
2024-02-27 8:38 dpdklab
2024-02-27 8:34 dpdklab
2024-02-27 8:32 dpdklab
2024-02-27 8:26 dpdklab
2024-02-27 8:04 dpdklab
2024-02-27 8:03 dpdklab
2024-02-27 8:03 dpdklab
2024-02-27 8:03 dpdklab
2024-02-27 8:02 dpdklab
2024-02-27 7:58 dpdklab
2024-02-27 7:56 dpdklab
2024-02-27 7:49 dpdklab
2024-02-27 7:48 dpdklab
2024-02-27 7:48 dpdklab
2024-02-27 7:46 dpdklab
2024-02-27 7:46 dpdklab
2024-02-27 7:45 dpdklab
2024-02-27 7:44 dpdklab
2024-02-27 7:44 dpdklab
2024-02-27 7:44 dpdklab
2024-02-27 7:43 dpdklab
2024-02-27 7:38 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=65dd91b8.170a0220.558c8.2239SMTPIN_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).