From: Jiale Song <songx.jiale@intel.com>
To: dts@dpdk.org
Cc: Jiale Song <songx.jiale@intel.com>
Subject: [dts] [PATCH V2 2/9] execution: add parameters and parameter comments
Date: Fri, 25 Aug 2023 15:28:18 +0000 [thread overview]
Message-ID: <20230825152825.2831565-3-songx.jiale@intel.com> (raw)
In-Reply-To: <20230825152825.2831565-1-songx.jiale@intel.com>
add execution related parameters and comments for MEV testing.
Signed-off-by: Jiale Song <songx.jiale@intel.com>
---
execution.cfg | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/execution.cfg b/execution.cfg
index 1507527c..f2526e70 100644
--- a/execution.cfg
+++ b/execution.cfg
@@ -1,3 +1,24 @@
+# ************Readme************
+# [Execution1]; Section Name,multiple segments can be configured, Required
+# crbs=xxx:xxx:xxx:xxx; DUT ip address, Required
+# drivername=vfio-pci or igb_uio; DPDK use driver, Required
+# build_type=meson; DPDK compilation type, Required
+# test_suites:
+# hello_world, Test suite list, Required
+# targets=
+# x86_64-native-linuxapp-gcc or 86_64-native-linuxapp-clang or arm64-intel-linux-gcc; DPDK compilation targets, Required
+# parameters=nic_type=cfg:func/perf=true; Test type, function or performance, Required
+# rx_mode=novector or sse or avx2, avx512, avx512, nolimit, Setting the testpmd force-max-simd-bitwidth parameter, Optional or not filled in
+# novector:force-max-simd-bitwidth=64; sse: force-max-simd-bitwidth=128; avx2:force-max-simd-bitwidth=256; avx512: force-max-simd-bitwidth=512; nolimit: force-max-simd-bitwidth=0;
+# dcf_mode=enable; Testing vf cases using dcf mode, Optional or not filled in
+
+# **********MEV nic test config parameters**********
+# test_mev=False or True; Is it testing the MEV network card, Required in MEV test
+# test_acc=False or True; Is it testing the MEV network card on ACC, Required in MEV test
+# queue_model=splitq or singleq; Set the queue of the MEV port; Required in MEV test
+# vport=0-3; Set the vport of the mev port; Required in MEV test
+# rx_vport=0; Set the vport packet receiving port; Required in MEV test
+
[Execution1]
crbs=<CRB IP Address>
#using igb_uio please refer to doc/dts_gsg/support_igb_uio.rst
--
2.25.1
next prev parent reply other threads:[~2023-08-25 7:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 15:28 [dts] [PATCH V2 0/9] add functions to test MEV Jiale Song
2023-08-25 8:01 ` David Marchand
2023-08-25 15:28 ` [dts] [PATCH V2 1/9] conf/crbs: add parameters Jiale Song
2023-08-25 15:28 ` Jiale Song [this message]
2023-08-25 15:28 ` [dts] [PATCH V2 3/9] framework/config: obtain and save the acc and imc configurations of MEV Jiale Song
2023-08-25 15:28 ` [dts] [PATCH V2 4/9] framework/dts: add global variables Jiale Song
2023-08-25 15:28 ` [dts] [PATCH V2 5/9] framework/dut: add and modify methods to adapt to MEV testing Jiale Song
2023-08-25 15:28 ` [dts] [PATCH V2 6/9] framework/pmd_output: optimize " Jiale Song
2023-08-25 15:28 ` [dts] [PATCH V2 7/9] framework/project_dpdk: " Jiale Song
2023-08-25 15:28 ` [dts] [PATCH V2 8/9] framework/settings: add drivers and NICs for mev Jiale Song
2023-08-25 15:28 ` [dts] [PATCH V2 9/9] framework/tester: optimize scripts Jiale Song
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=20230825152825.2831565-3-songx.jiale@intel.com \
--to=songx.jiale@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).