From: TangHaifeng <haifengx.tang@intel.com>
To: dts@dpdk.org
Cc: jingguox.fu@intel.com
Subject: [dts] [dts 23/28] add unit_test_pmd testcase into dts
Date: Tue, 26 May 2015 15:35:50 +0800 [thread overview]
Message-ID: <1432625755-19403-17-git-send-email-haifengx.tang@intel.com> (raw)
In-Reply-To: <1432625755-19403-1-git-send-email-haifengx.tang@intel.com>
---
tests/TestSuite_unit_tests_pmd_perf.py | 146 ++++++++++++++++++++++++++++++++
1 files changed, 146 insertions(+), 0 deletions(-)
create mode 100644 tests/TestSuite_unit_tests_pmd_perf.py
diff --git a/tests/TestSuite_unit_tests_pmd_perf.py b/tests/TestSuite_unit_tests_pmd_perf.py
new file mode 100644
index 0000000..8745227
--- /dev/null
+++ b/tests/TestSuite_unit_tests_pmd_perf.py
@@ -0,0 +1,146 @@
+# BSD LICENSE
+#
+# Copyright(c) 2010-2014 Intel Corporation. All rights reserved.
+# All rights reserved.
+#
+# Redistribution and use in source and binary forms, with or without
+# modification, are permitted provided that the following conditions
+# are met:
+#
+# * Redistributions of source code must retain the above copyright
+# notice, this list of conditions and the following disclaimer.
+# * Redistributions in binary form must reproduce the above copyright
+# notice, this list of conditions and the following disclaimer in
+# the documentation and/or other materials provided with the
+# distribution.
+# * Neither the name of Intel Corporation nor the names of its
+# contributors may be used to endorse or promote products derived
+# from this software without specific prior written permission.
+#
+# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
+# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
+# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
+# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+"""
+DPDK Test suite.
+
+This TestSuite runs the unit tests included in DPDK for pmd performance.
+"""
+
+import dts
+import re
+from test_case import TestCase
+
+#
+#
+# Test class.
+#
+
+
+class TestUnitTestsPmdPerf(TestCase):
+
+ #
+ #
+ #
+ # Test cases.
+ #
+
+ def set_up_all(self):
+ """
+ Run at the start of each test suite.
+
+ Power Prerequisites
+ """
+ self.dut_ports = self.dut.get_ports(self.nic)
+ self.verify(len(self.dut_ports) >= 1, "Insufficient ports for testing")
+ [self.arch, machine, env, toolchain] = self.target.split('-')
+ self.verify(self.arch == "x86_64", "pmd perf request running in x86_64")
+ self.burst_ctlmodes = ['poll_before_xmit', 'poll_after_xmit']
+ self.rxtx_modes = ['vector', 'scalar', 'full', 'hybrid']
+ self.anchors = ['rxtx', 'rxonly', 'txonly']
+
+ # for better scalar performance data, need disble CONFIG_RTE_IXGBE_INC_VECTOR
+ [arch, machine, env, toolchain] = self.target.split('-')
+ self.dut.send_expect("sed -i -e 's/CONFIG_RTE_IXGBE_INC_VECTOR=y/CONFIG_RTE_IXGBE_INC_VECTOR=n/' config/common_%s" % env, "# ", 30)
+ self.dut.build_install_dpdk(self.target)
+ out = self.dut.build_dpdk_apps('./app/test/')
+ self.verify('make: Leaving directory' in out, "Compilation failed")
+ self.dut.send_expect("mv -f ./app/test/test ./app/test/test_scalar", "# ")
+ self.dut.send_expect("sed -i -e 's/CONFIG_RTE_IXGBE_INC_VECTOR=n/CONFIG_RTE_IXGBE_INC_VECTOR=y/' config/common_%s" % env, "# ", 30)
+ self.dut.build_install_dpdk(self.target)
+ out = self.dut.build_dpdk_apps('./app/test/')
+ self.verify('make: Leaving directory' in out, "Compilation failed")
+
+ def set_up(self):
+ """
+ Run before each test case.
+ """
+ pass
+
+ def test_pmd_burst(self):
+ """
+ Run pmd stream control mode burst test case.
+ """
+
+ self.dut.send_expect("./app/test/test -n 1 -c ffff", "R.*T.*E.*>.*>", 30)
+ for mode in self.burst_ctlmodes:
+ self.dut.send_expect("set_rxtx_sc %s" % mode, "RTE>>", 5)
+ out = self.dut.send_expect("pmd_perf_autotest", "RTE>>", 60)
+ match_regex = "Result: (\d+) cycles per packet"
+ m = re.compile(r"%s" % match_regex, re.S)
+ result = m.search(out)
+ self.logger.info("Mode %s latency is %s" % (mode, result.group(1)))
+
+ self.dut.send_expect("quit", "# ")
+
+ def test_pmd_continues(self):
+ """
+ Run pmd stream control mode continues test case.
+ """
+
+ self.table_header = ['Mode']
+ self.table_header += self.anchors
+ dts.results_table_add_header(self.table_header)
+ print self.table_header
+
+ for mode in self.rxtx_modes:
+ if mode is "scalar":
+ self.dut.send_expect("./app/test/test_scalar -n 1 -c ffff", "R.*T.*E.*>.*>", 30)
+ else:
+ self.dut.send_expect("./app/test/test -n 1 -c ffff", "R.*T.*E.*>.*>", 30)
+
+ table_row = [mode]
+ self.dut.send_expect("set_rxtx_sc continuous", "RTE>>", 5)
+ self.dut.send_expect("set_rxtx_mode %s" % mode, "RTE>>", 5)
+ for anchor in self.anchors:
+ self.dut.send_expect("set_rxtx_anchor %s" % anchor, "RTE>>", 5)
+ out = self.dut.send_expect("pmd_perf_autotest", "RTE>>", 60)
+ match_regex = "Result: (\d+) cycles per packet"
+ m = re.compile(r"%s" % match_regex, re.S)
+ result = m.search(out)
+ table_row.append(result.group(1))
+
+ self.dut.send_expect("quit", "# ")
+ dts.results_table_add_row(table_row)
+
+ dts.results_table_print()
+
+ def tear_down(self):
+ """
+ Run after each test case.
+ """
+ pass
+
+ def tear_down_all(self):
+ """
+ Run after each test suite.
+ """
+ pass
--
1.7.4.4
next prev parent reply other threads:[~2015-05-26 7:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 7:35 [dts] [dts 07/28] add unit_test_mbuf rst file " TangHaifeng
2015-05-26 7:35 ` [dts] [dts 08/28] add unit_test_mempool " TangHaifeng
2015-05-26 7:35 ` [dts] [dts 09/28] add unit_tests_pmd_perf " TangHaifeng
2015-05-26 7:35 ` [dts] [dts 10/28] add unit_test_power " TangHaifeng
2015-05-26 9:01 ` Liu, Yong
2015-05-26 7:35 ` [dts] [dts 11/28] add unit_test_qos " TangHaifeng
2015-05-26 7:35 ` [dts] [dts 12/28] add unit_test_ring " TangHaifeng
2015-05-26 7:35 ` [dts] [dts 13/28] add unit_test_ringpmd " TangHaifeng
2015-05-26 7:35 ` [dts] [dts 14/28] add unit_test_timer " TangHaifeng
2015-05-26 7:35 ` [dts] [dts 15/28] add unit_test_cmdline testcase " TangHaifeng
2015-05-26 7:35 ` [dts] [dts 16/28] add unit_test_dump " TangHaifeng
2015-05-26 7:35 ` [dts] [dts 17/28] add unit_test_eal " TangHaifeng
2015-05-26 7:35 ` [dts] [dts 18/28] add unit_test_ivshmem " TangHaifeng
2015-05-26 7:35 ` [dts] [dts 19/28] add unit_test_kni " TangHaifeng
2015-05-26 7:35 ` [dts] [dts 20/28] add unit_test_lpm " TangHaifeng
2015-05-26 7:35 ` [dts] [dts 21/28] add unit_test_mbuf " TangHaifeng
2015-05-26 7:35 ` [dts] [dts 22/28] add unit_test_mempool " TangHaifeng
2015-05-26 7:35 ` TangHaifeng [this message]
2015-05-26 7:35 ` [dts] [dts 24/28] add unit_test_power " TangHaifeng
2015-05-26 7:35 ` [dts] [dts 25/28] add unit_test_qos " TangHaifeng
2015-05-26 7:35 ` [dts] [dts 26/28] add unit_test_ring " TangHaifeng
2015-05-26 7:35 ` [dts] [dts 27/28] add unit_test_ringpmd " TangHaifeng
2015-05-26 7:35 ` [dts] [dts 28/28] add unit_tests_timer " TangHaifeng
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=1432625755-19403-17-git-send-email-haifengx.tang@intel.com \
--to=haifengx.tang@intel.com \
--cc=dts@dpdk.org \
--cc=jingguox.fu@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).