From: yufengmx <yufengx.mo@intel.com>
To: dts@dpdk.org, lijuan.tu@intel.com
Cc: yufengmx <yufengx.mo@intel.com>
Subject: [dts] [PATCH V4 2/4] conf/vf_l3fwd_kernelpf: suite testing configuration
Date: Fri, 10 Apr 2020 15:52:18 +0800 [thread overview]
Message-ID: <20200410075220.5184-3-yufengx.mo@intel.com> (raw)
In-Reply-To: <20200410075220.5184-1-yufengx.mo@intel.com>
add vf_l3fwd_kernelpf suite testing configuration.
Signed-off-by: yufengmx <yufengx.mo@intel.com>
---
conf/vf_l3fwd_kernelpf.cfg | 104 +++++++++++++++++++++++++++++++++++++
1 file changed, 104 insertions(+)
create mode 100644 conf/vf_l3fwd_kernelpf.cfg
diff --git a/conf/vf_l3fwd_kernelpf.cfg b/conf/vf_l3fwd_kernelpf.cfg
new file mode 100644
index 0000000..b0d4ad0
--- /dev/null
+++ b/conf/vf_l3fwd_kernelpf.cfg
@@ -0,0 +1,104 @@
+# 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
+# {
+# 'Numbers of Cores/Sockets/Queues #1': ['frame_size #1', 'frame_size #2',...],
+# 'Numbers of Cores/Sockets/Queues #2': ['frame_size #1', 'frame_size #2',...],
+# ......
+# }
+#
+# - test_duration is how many seconds each combination performance will
+# be recorded, default is 60s
+#
+# - accepted_tolerance defines the accepted tolerance between test
+# results and expected numbers, unit is percentage, (actual number - expected number)/expected number/100
+#
+# - expected_throughput is a dictionary defining expected throughput
+# numbers based on NIC, and the pattern is
+# {
+# 'columbiaville_100g':
+# {
+# 'Numbers of Cores/Sockets/Queues #1':
+# {
+# 'frame_size #1': 'expected number',
+# 'frame_size #2': 'expected number',
+# ...
+# },
+# 'Numbers of Cores/Sockets/Queues #2':
+# {
+# 'frame_size #1': 'expected number',
+# 'frame_size #2': 'expected number',
+# ...
+# },
+# }
+# ......
+# }
+# Every user should fill it out with your actual numbers. To keep the
+# expected throughput private, dts takes 0.00 as default.
+#
+#==========this feature supported is P4.======================
+# - if update_expected == True, 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 beginning, 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 usual.
+
+[suite]
+update_expected = True
+test_duration = 12
+accepted_tolerance = 1
+test_parameters = {
+ '1C/1T/1Q': ['64', '128', '256', '512', '1024', '1280', '1518',],
+ '1C/2T/2Q': ['64', '128', '256', '512', '1024', '1280', '1518',],
+ '2C/2T/2Q': ['64', '128', '256', '512', '1024', '1280', '1518',],
+ '2C/4T/4Q': ['64', '128', '256', '512', '1024', '1280', '1518',],
+ '4C/4T/4Q': ['64', '128', '256', '512', '1024', '1280', '1518',],}
+expected_throughput = {
+ 'test_perf_vf_throughput_ipv4_lpm': {
+ 'niantic': {
+ '1C/1T/1Q': {
+ '64': '0.00',
+ '128': '0.00',
+ '256': '0.00',
+ '512': '0.00',
+ '1024': '0.00',
+ '1280': '0.00',
+ '1518': '0.00', },
+ '1C/2T/2Q': {
+ '64': '0.00',
+ '128': '0.00',
+ '256': '0.00',
+ '512': '0.00',
+ '1024': '0.00',
+ '1280': '0.00',
+ '1518': '0.00', },
+ '2C/2T/2Q': {
+ '64': '0.00',
+ '128': '0.00',
+ '256': '0.00',
+ '512': '0.00',
+ '1024': '0.00',
+ '1280': '0.00',
+ '1518': '0.00', },
+ '2C/4T/4Q': {
+ '64': '0.00',
+ '128': '0.00',
+ '256': '0.00',
+ '512': '0.00',
+ '1024': '0.00',
+ '1280': '0.00',
+ '1518': '0.00', },
+ '4C/4T/4Q': {
+ '64': '0.00',
+ '128': '0.00',
+ '256': '0.00',
+ '512': '0.00',
+ '1024': '0.00',
+ '1280': '0.00',
+ '1518': '0.00', },},},}
\ No newline at end of file
--
2.21.0
next prev parent reply other threads:[~2020-04-10 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 7:52 [dts] [PATCH V4 0/4] l3fwd: support l3fwd pf&vf test scenario yufengmx
2020-04-10 7:52 ` [dts] [PATCH V4 1/4] conf/vf_l3fwd_base: stream flow configuration yufengmx
2020-04-10 7:52 ` yufengmx [this message]
2020-04-10 7:52 ` [dts] [PATCH V4 3/4] tests/vf_l3fwd_kernelpf: upload automation script yufengmx
2020-04-10 7:52 ` [dts] [PATCH V4 4/4] vf_l3fwd: support l3fwd pf&vf test scenario yufengmx
2020-04-20 4:43 ` [dts] [PATCH V4 0/4] l3fwd: " 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=20200410075220.5184-3-yufengx.mo@intel.com \
--to=yufengx.mo@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@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).