From: wang fei <feix.y.wang@intel.com>
To: dts@dpdk.org
Cc: yong.liu@intel.com, wang fei <feix.y.wang@intel.com>
Subject: [dts] [DTS][PATCH V4 3/3] conf/nic_single_core_perf.cfg: add suite configuration file
Date: Mon, 5 Feb 2018 15:58:54 +0800 [thread overview]
Message-ID: <1517817535-23964-2-git-send-email-feix.y.wang@intel.com> (raw)
In-Reply-To: <1517817535-23964-1-git-send-email-feix.y.wang@intel.com>
For next branch: add the expected throughput values for NICs:
"niantic"(4 ports), "fortville_25g"(2 ports), and the values
will be parsed by the test suite.
Signed-off-by: wang fei <feix.y.wang@intel.com>
---
conf/nic_single_core_perf.cfg | 10 ++++++++++
1 file changed, 10 insertions(+)
create mode 100644 conf/nic_single_core_perf.cfg
diff --git a/conf/nic_single_core_perf.cfg b/conf/nic_single_core_perf.cfg
new file mode 100644
index 0000000..8746326
--- /dev/null
+++ b/conf/nic_single_core_perf.cfg
@@ -0,0 +1,10 @@
+[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"}}
+throughput_nnt = {64: {128: 53.435, 512: 53.699, 2048: 42.798}}
+throughput_fvl25g = {64: {512: 43.777, 2048: 43.651}}
--
2.7.4
next prev parent reply other threads:[~2018-02-05 5:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 7:58 [dts] [DTS][PATCH V4 2/3] test_plans/nic_single_core_perf_test_plan.rst: add new test plan wang fei
2018-02-05 7:58 ` wang fei [this message]
2018-02-05 7:58 ` [dts] [DTS][PATCH v4 1/3] tests/TestSuite_nic_single_core_perf.py: add a new test suite for performance wang fei
2018-02-05 14:42 ` Liu, Yong
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=1517817535-23964-2-git-send-email-feix.y.wang@intel.com \
--to=feix.y.wang@intel.com \
--cc=dts@dpdk.org \
--cc=yong.liu@intel.com \
/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).