From: Lijuan Tu <lijuan.tu@intel.com>
To: dliu@iol.unh.edu, ohilyard@iol.unh.edu, alialnu@nvidia.com
Cc: dts@dpdk.org, Lijuan Tu <lijuan.tu@intel.com>
Subject: [dts] [v2 0/6] revise tests/nic_signle_core_perf
Date: Wed, 31 Mar 2021 09:34:04 +0000 [thread overview]
Message-ID: <20210331093410.505773-1-lijuan.tu@intel.com> (raw)
* changed pass / fail determination to be percentage based
* made multiple traffic measurements during the test run to
collect better statistics
Group agreed in CI Meeting:
https://mails.dpdk.org/archives/ci/2021-February/001049.html
* v2:
* changed percentage to a float
* separate to serval patches
* fix rx desc size
Lijuan Tu (6):
tests/nic_single_core_perf: beauty JSON string
tests/nic_single_core_perf: get better throughput stats
tests/nic_single_core_perf: revise rst table
tests/nic_single_core_perf: revise delta to ratio
tests/nic_single_core_perf: add expected mpps into JSON
tests/nic_single_core_perf: revise rx desc size
conf/nic_single_core_perf.cfg | 18 +++-
tests/TestSuite_nic_single_core_perf.py | 112 +++++++++++++++---------
2 files changed, 83 insertions(+), 47 deletions(-)
--
2.25.1
next reply other threads:[~2021-03-31 1:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 9:34 Lijuan Tu [this message]
2021-03-31 9:34 ` [dts] [v2 1/6] tests/nic_single_core_perf: beauty JSON string Lijuan Tu
2021-03-31 9:34 ` [dts] [v2 2/6] tests/nic_single_core_perf: get better throughput stats Lijuan Tu
2021-03-31 9:34 ` [dts] [v2 3/6] tests/nic_single_core_perf: revise rst table Lijuan Tu
2021-03-31 9:34 ` [dts] [v2 4/6] tests/nic_single_core_perf: revise delta to ratio Lijuan Tu
2021-03-31 9:34 ` [dts] [v2 5/6] tests/nic_single_core_perf: add expected mpps into JSON Lijuan Tu
2021-03-31 9:34 ` [dts] [v2 6/6] tests/nic_single_core_perf: revise rx desc size Lijuan Tu
2021-06-25 5:21 ` [dts] [v2 0/6] revise tests/nic_signle_core_perf Tu, Lijuan
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=20210331093410.505773-1-lijuan.tu@intel.com \
--to=lijuan.tu@intel.com \
--cc=alialnu@nvidia.com \
--cc=dliu@iol.unh.edu \
--cc=dts@dpdk.org \
--cc=ohilyard@iol.unh.edu \
/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).