From: "xu,huilong" <huilongx.xu@intel.com>
To: dts@dpdk.org
Cc: "xu,huilong" <huilongx.xu@intel.com>
Subject: [dts] [PATCH V1 5/6] add a new config file for unit test
Date: Fri, 25 Aug 2017 15:42:10 +0800 [thread overview]
Message-ID: <1503646931-91671-5-git-send-email-huilongx.xu@intel.com> (raw)
In-Reply-To: <1503646931-91671-1-git-send-email-huilongx.xu@intel.com>
Signed-off-by: xu,huilong <huilongx.xu@intel.com>
---
executions/execution_unit.cfg | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
create mode 100644 executions/execution_unit.cfg
diff --git a/executions/execution_unit.cfg b/executions/execution_unit.cfg
new file mode 100644
index 0000000..151d3a9
--- /dev/null
+++ b/executions/execution_unit.cfg
@@ -0,0 +1,22 @@
+[Execution1]
+crbs=<CRB IP Address>
+drivername=<driver name igb_uio or vfio-pci or mlx5_core>
+test_suites=
+ unit_tests_cmdline,
+ unit_tests_eal,
+ unit_tests_dump,
+ unit_tests_kni,
+ unit_tests_lpm,
+ unit_tests_mbuf,
+ unit_tests_mempool,
+# only niantic nic support
+# unit_tests_pmd_perf
+ unit_tests_power,
+ unit_tests_qos,
+ unit_tests_ring,
+ unit_tests_ringpmd,
+ unit_tests_timer,
+ unit_tests_crc
+targets=
+ x86_64-native-linuxapp-gcc
+parameters=nic_type=niantic:func=true
--
1.9.3
next prev parent reply other threads:[~2017-08-25 7:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 7:42 [dts] [PATCH V1 1/6] add a new config file for fortvill PF full function test xu,huilong
2017-08-25 7:42 ` [dts] [PATCH V1 2/6] add a new config file for fortville PF scalare rx mode test xu,huilong
2017-08-25 7:42 ` [dts] [PATCH V1 3/6] add a new config file for fortville PF no vector pmd " xu,huilong
2017-08-25 7:42 ` [dts] [PATCH V1 4/6] remove old config file for fortville test xu,huilong
2017-08-25 7:42 ` xu,huilong [this message]
2017-08-25 7:42 ` [dts] [PATCH V1 6/6] add a new example for performance test xu,huilong
2017-09-06 5:07 ` [dts] [PATCH V1 1/6] add a new config file for fortvill PF full function test Xu, Qian Q
2017-09-06 14:59 ` 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=1503646931-91671-5-git-send-email-huilongx.xu@intel.com \
--to=huilongx.xu@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).