From: "Yao, BingX Y" <bingx.y.yao@intel.com>
To: "Lin, Xueqin" <xueqin.lin@intel.com>,
"Tu, Lijuan" <lijuan.tu@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Wang, FengqinX" <fengqinx.wang@intel.com>
Subject: Re: [dts] [PATCH] tests/unit_tests_eal: add more hash relative unit tests.
Date: Mon, 10 Dec 2018 01:57:47 +0000 [thread overview]
Message-ID: <95BCD24840F32441BEA74E0F8A31839E04ECD263@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <0D300480287911409D9FF92C1FA2A3355B45C827@SHSMSX104.ccr.corp.intel.com>
-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Lin, Xueqin
Sent: Tuesday, December 4, 2018 2:08 PM
To: Tu, Lijuan <lijuan.tu@intel.com>; dts@dpdk.org
Subject: Re: [dts] [PATCH] tests/unit_tests_eal: add more hash relative unit tests.
The unit tests are not new, I will try to add this part.
Best regards,
Xueqin
-----Original Message-----
From: Tu, Lijuan
Sent: Monday, December 3, 2018 11:26 AM
To: Lin, Xueqin <xueqin.lin@intel.com>; dts@dpdk.org
Cc: Lin, Xueqin <xueqin.lin@intel.com>
Subject: RE: [dts] [PATCH] tests/unit_tests_eal: add more hash relative unit tests.
Hi xueqin,
Did you forget test plan?
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Xueqin Lin
> Sent: Friday, November 30, 2018 9:13 AM
> To: dts@dpdk.org
> Cc: Lin, Xueqin <xueqin.lin@intel.com>
> Subject: [dts] [PATCH] tests/unit_tests_eal: add more hash relative
> unit tests.
>
> From: "xueqin.lin" <xueqin.lin@intel.com>
>
> test_hash_functions
> test_hash_multiwriter
> test_hash_readwrite
> test_hash_readwrite_lf
>
> Signed-off-by: Xueqin Lin <xueqin.lin@intel.com>
> tested-by: Yaobing <Yao, BingX Y@intel.com>
> ---
> tests/TestSuite_unit_tests_eal.py | 55
> +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 55 insertions(+)
>
> diff --git a/tests/TestSuite_unit_tests_eal.py
> b/tests/TestSuite_unit_tests_eal.py
> index 68a4cbe..c7de5b7 100644
> --- a/tests/TestSuite_unit_tests_eal.py
> +++ b/tests/TestSuite_unit_tests_eal.py
> @@ -115,6 +115,13 @@ class TestUnitTestsEal(TestCase):
> self.dut.send_expect(self.test_app_cmdline, "R.*T.*E.*>.*>",
> self.start_test_time)
> out = self.dut.send_expect("hash_autotest", "RTE>>",
> self.run_cmd_time)
> self.dut.send_expect("quit", "# ")
> +
> + # Extendable Bucket Table enhances and guarantees insertion
> + of
> 100% of
> + # the keys for a given hash table size. Add the check that average
> + # table utilization is 100% when extendable table is enabled.
> +
> + self.verify("Average table utilization = 100.00%" in out,
> + "Test failed for extenable bucket table")
> self.verify("Test OK" in out, "Test failed")
>
> def test_hash_perf(self):
> @@ -128,6 +135,54 @@ class TestUnitTestsEal(TestCase):
> self.dut.send_expect("quit", "# ")
> self.verify("Test OK" in out, "Test failed")
>
> + def test_hash_functions(self):
> + """
> + Run hash functions autotest.
> + """
> +
> + self.dut.send_expect(self.test_app_cmdline,
> + "R.*T.*E.*>.*>", self.start_test_time)
> + out = self.dut.send_expect("hash_functions_autotest",
> + "RTE>>", self.run_cmd_time)
> + self.dut.send_expect("quit", "# ")
> + self.verify("Test OK" in out, "Test failed")
> +
> + def test_hash_multiwriter(self):
> + """
> + Run hash multiwriter autotest.
> + """
> +
> + self.dut.send_expect(self.test_app_cmdline,
> + "R.*T.*E.*>.*>", self.start_test_time)
> + out = self.dut.send_expect("hash_multiwriter_autotest",
> + "RTE>>", self.run_cmd_time)
> + self.dut.send_expect("quit", "# ")
> + self.verify("Test OK" in out, "Test failed")
> +
> + def test_hash_readwrite(self):
> + """
> + Run hash readwrite autotest.
> + """
> +
> + self.dut.send_expect(self.test_app_cmdline,
> + "R.*T.*E.*>.*>", self.start_test_time)
> + out = self.dut.send_expect("hash_readwrite_autotest",
> + "RTE>>", self.run_cmd_time)
> + self.dut.send_expect("quit", "# ")
> + self.verify("Test OK" in out, "Test failed")
> +
> + def test_hash_readwrite_lf(self):
> + """
> + Run hash readwrite_lf autotest.
> + """
> +
> + self.dut.send_expect("./%s/app/test" % self.target,
> + "R.*T.*E.*>.*>", self.start_test_time)
> + out = self.dut.send_expect("hash_readwrite_lf_autotest",
> + "RTE>>", self.run_cmd_time)
> + self.dut.send_expect("quit", "# ")
> + self.verify("Test OK" in out, "Test failed")
> +
> def test_func_reentrancy(self):
> """
> Run function reentrancy autotest.
> --
> 2.7.5
next prev parent reply other threads:[~2018-12-10 1:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 1:12 Xueqin Lin
2018-12-03 3:26 ` Tu, Lijuan
2018-12-04 6:07 ` Lin, Xueqin
2018-12-10 1:57 ` Yao, BingX Y [this message]
2018-12-10 2:08 ` Yao, BingX Y
2019-01-07 8:18 ` 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=95BCD24840F32441BEA74E0F8A31839E04ECD263@shsmsx102.ccr.corp.intel.com \
--to=bingx.y.yao@intel.com \
--cc=dts@dpdk.org \
--cc=fengqinx.wang@intel.com \
--cc=lijuan.tu@intel.com \
--cc=xueqin.lin@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).