From: Yu Jiang <yux.jiang@intel.com>
To: lijuan.tu@intel.com, dts@dpdk.org
Cc: Yu Jiang <yux.jiang@intel.com>
Subject: [dts][PATCH V1] tests/unit_tests_eal: fix acl script call error and support different rx_mode
Date: Wed, 15 Jun 2022 16:49:25 +0000 [thread overview]
Message-ID: <20220615164925.1583168-1-yux.jiang@intel.com> (raw)
Since DTS commit "7eaf4b60 tests/l3fwdacl: modify pmd param for acl" has incorrect usage,
fix script to support different rx_mode.
Signed-off-by: Yu Jiang <yux.jiang@intel.com>
---
tests/TestSuite_unit_tests_eal.py | 15 +++++++++------
1 file changed, 9 insertions(+), 6 deletions(-)
diff --git a/tests/TestSuite_unit_tests_eal.py b/tests/TestSuite_unit_tests_eal.py
index c1de4884..9cac6197 100644
--- a/tests/TestSuite_unit_tests_eal.py
+++ b/tests/TestSuite_unit_tests_eal.py
@@ -465,15 +465,18 @@ class TestUnitTestsEal(TestCase):
"""
Run acl autotest.
"""
- eal_params = self.dut.create_eal_parameters(
- other_eal_param="force-max-simd-bitwidth"
- )
+ eal_params = self.dut.create_eal_parameters()
app_name = self.dut.apps_name["test"]
test_app_cmdline = app_name + eal_params
test_app_cmdline += "--no-pci"
-
- if self.dut.dpdk_version >= "20.11.0":
- test_app_cmdline += " --force-max-simd-bitwidth=0"
+ # When execution.cfg set rx_mode=xxx, it should have priority.
+ print("eal_para = {}".format(eal_params))
+ if "force-max-simd-bitwidth" in eal_params:
+ pass
+ else:
+ # DTS commit 68bb1b92("tests/l3fwdacl: try to use highest available method") when dpdk > 20.11.0 by konstantin.ananyev@intel.com
+ if self.dut.dpdk_version >= "20.11.0":
+ test_app_cmdline += " --force-max-simd-bitwidth=0"
self.dut.send_expect(test_app_cmdline, "R.*T.*E.*>.*>", self.start_test_time)
out = self.dut.send_expect("acl_autotest", "RTE>>", self.run_cmd_time)
self.dut.send_expect("quit", "# ")
--
2.25.1
next reply other threads:[~2022-06-15 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 16:49 Yu Jiang [this message]
2022-06-15 9:15 ` lijuan.tu
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=20220615164925.1583168-1-yux.jiang@intel.com \
--to=yux.jiang@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).