From: Lijuan Tu <lijuan.tu@intel.com>
To: dts@dpdk.org, pmacarth@iol.unh.edu, alialnu@mellanox.com
Cc: Lijuan Tu <lijuan.tu@intel.com>
Subject: [dts] [next] [PATCH 3/3] conf/nic_single_core_perf: redefine elements
Date: Fri, 20 Jul 2018 23:22:04 +0800 [thread overview]
Message-ID: <1532100124-64769-4-git-send-email-lijuan.tu@intel.com> (raw)
In-Reply-To: <1532100124-64769-1-git-send-email-lijuan.tu@intel.com>
script changed , and align with it.
Signed-off-by: Lijuan Tu <lijuan.tu@intel.com>
---
conf/nic_single_core_perf.cfg | 33 +++++++++++++++++++++++++++------
1 file changed, 27 insertions(+), 6 deletions(-)
diff --git a/conf/nic_single_core_perf.cfg b/conf/nic_single_core_perf.cfg
index 444307e..e855bb5 100644
--- a/conf/nic_single_core_perf.cfg
+++ b/conf/nic_single_core_perf.cfg
@@ -1,11 +1,32 @@
+# Throughput numbers vary in different environment.
+# Change these configuration on demand.
+# test_parameters defines the combination of frame size and descriptor
+# numbers, and the pattern is
+# {'frame size': ['descriptor number #1', 'descriptor number #2']}
+# test_duration is how many seconds each combination performance will be
+# recorded.
+# accepted_tolerance defines the accepted tolerance between test results and
+# expected numbers.
+# expected_throughput is a dictionary defining expected throughput
+# numbers based on NIC, and the pattern is
+# {'NIC': {'frame size': {'descriptor number': 'excepted throughput'}}}
+# Default numbers of fortville_spirit and niantic is generated on this
+# environment
+# * Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
+# * Trex v3.23
+
[suite]
-# list expected throughput values for 64byte packet size and different
-# txd/rxd, these values may vary dut to different test enviroment,
-# please adjust accordingly, the below nnt and fvl25g expected
-# throughputs were tested under Purly,Ubuntu 16.04, IXIA
-# the formate for the expected throughput is a dictinary which means
-# {"packet size": {"descriptor ring size": "throughput"}}
+test_parameters = {64: [512, 2048]}
+test_duration = 60
+accepted_tolerance = 1
+expected_throughput = {'fortville_spirit': {64: {512: 62.35, 2048: 47.89}},
+ 'niantic': {64: {128: 53.435, 512: 53.699, 2048: 42.798}},
+ 'fortville_25g': {64: {512: 62.35, 2048: 47.651}},
+ 'ConnectX4_LX_MT4117': {'40G': {64: {128: 31.635, 256: 32.473, 512: 30.72, 2048: 26.94}},
+ '25G': {64: {128: 28.178, 256: 34.581, 512: 30.528, 2048: 26.004}}},
+ 'ConnectX5_MT4121': {64: {128: 42.161, 256: 56.651, 512: 47.091, 2048: 40.104}}}
+# legacy formate for reference
throughput_nnt = {64: {128: 53.435, 512: 53.699, 2048: 42.798}}
throughput_fvl25g = {64: {512: 43.777, 2048: 43.651}}
throughput_fvl40g = {64: {512: 62.35, 2048: 47.89}}
--
1.8.3.1
prev parent reply other threads:[~2018-07-20 6:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 15:22 [dts] [next] [PATCH 0/3] support update-expected to meet Open Lab requirement Lijuan Tu
2018-07-20 15:22 ` [dts] [next] [PATCH 1/3] framework: support argument: --update-expected Lijuan Tu
2018-07-20 7:23 ` Liu, Yong
2018-07-20 15:22 ` [dts] [next] [PATCH 2/3] tests/nic_single_core_perf: remove hardcode Lijuan Tu
2018-07-20 15:22 ` Lijuan Tu [this message]
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=1532100124-64769-4-git-send-email-lijuan.tu@intel.com \
--to=lijuan.tu@intel.com \
--cc=alialnu@mellanox.com \
--cc=dts@dpdk.org \
--cc=pmacarth@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).