From: hanyingya <yingyax.han@intel.com>
To: dts@dpdk.org
Cc: hanyingya <yingyax.han@intel.com>
Subject: [dts] [PATCH V1 2/3]conf: add vf single core configuration file
Date: Wed, 11 Nov 2020 14:27:00 +0800 [thread overview]
Message-ID: <20201111062701.36217-3-yingyax.han@intel.com> (raw)
In-Reply-To: <20201111062701.36217-1-yingyax.han@intel.com>
Signed-off-by: hanyingya <yingyax.han@intel.com>
---
conf/vf_single_core_perf.cfg | 64 ++++++++++++++++++++++++++++++++++++
1 file changed, 64 insertions(+)
create mode 100644 conf/vf_single_core_perf.cfg
diff --git a/conf/vf_single_core_perf.cfg b/conf/vf_single_core_perf.cfg
new file mode 100644
index 00000000..041faa87
--- /dev/null
+++ b/conf/vf_single_core_perf.cfg
@@ -0,0 +1,64 @@
+# Throughput numbers vary in different environment.
+# Users could 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'}}}
+# Every user should fill it out with your actual numbers. To keep the
+# expected throughput private, dts takes 0.00 as default.
+#
+# - if update_expected == Ture, and add argument "--update-expected" in
+# bash command, all objects in this file will changed after the run
+# for example: ./dts --update-expected
+#
+# Highlights:
+# At the begining, please change test_parameters according to your
+# requirements, then run ./dts --update-expected to get the absolute
+# results which will replace the default numbers 0.00 in this configuration.
+# So you will have your own private configuration, and could start your
+# tests as ususal.
+
+[suite]
+update_expected = True
+test_parameters = {'1C/1T': {64: [512, 2048]},
+ '1C/2T': {64: [512, 2048]}}
+test_duration = 60
+accepted_tolerance = 1
+expected_throughput = {
+ 'fortville_spirit': {
+ '1C/1T': {64: {512: 0.00, 2048: 0.00}},
+ '1C/2T': {64: {512: 0.00, 2048: 0.00}}},
+ 'fortville_eagle': {
+ '1C/1T':{64: {512: 0.00, 2048: 0.00}},
+ '1C/2T':{64: {512: 0.00, 2048: 0.00}}},
+ 'niantic': {
+ '1C/1T': {64: {128: 0.00, 512: 0.00, 2048: 0.00}},
+ '1C/2T': {64: {128: 0.00, 512: 0.00, 2048: 0.00}}},
+ 'fortville_25g': {
+ '1C/1T': {64: {512: 0.00, 2048: 0.00}},
+ '1C/2T': {64: {512: 0.00, 2048: 0.00}}},
+ 'columbiaville_100g': {
+ '1C/1T': {64: {512: 0.00, 2048: 0.00}},
+ '1C/2T': {64: {512: 0.00, 2048: 0.00}}},
+ 'columbiaville_25g': {
+ '1C/1T': {64: {512: 0.00, 2048: 0.00}},
+ '1C/2T': {64: {512: 0.00, 2048: 0.00}}},
+ 'ConnectX4_LX_MT4117': {'40G': {
+ '1C/1T': {64: {128: 0.00, 256: 0.00, 512: 0.00, 2048: 0.00}},
+ '1C/2T': {64: {128: 0.00, 256: 0.00, 512: 0.00, 2048: 0.00}}},
+ '25G': {
+ '1C/1T': {64: {128: 0.00, 256: 0.00, 512: 0.00, 2048: 0.00}},
+ '1C/2T': {64: {128: 0.00, 256: 0.00, 512: 0.00, 2048: 0.00}}}},
+ 'ConnectX5_MT4121': {
+ '1C/1T': {64: {128: 0.00, 256: 0.00, 512: 0.00, 2048: 0.00}},
+ '1C/2T': {64: {128: 0.00, 256: 0.00, 512: 0.00, 2048: 0.00}}}}
--
2.17.1
next prev parent reply other threads:[~2020-11-11 6:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 6:26 [dts] [PATCH V1 0/3] add vf single core perf test suite hanyingya
2020-11-11 6:26 ` [dts] [PATCH V1 1/3]test_plans: add vf single core test plan hanyingya
2020-11-11 6:27 ` hanyingya [this message]
2020-11-11 6:27 ` [dts] [PATCH V1 3/3]tests: add vf single core test script hanyingya
2020-11-11 6:42 ` [dts] [PATCH V1 0/3] add vf single core perf test suite 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=20201111062701.36217-3-yingyax.han@intel.com \
--to=yingyax.han@intel.com \
--cc=dts@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).