From: Xie wei <weix.xie@intel.com>
To: dts@dpdk.org
Cc: Xie wei <weix.xie@intel.com>
Subject: [dts] [PATCH V1 1/2] tests/TestSuite_cvl_fdir:remove flow-mark-support param
Date: Tue, 29 Sep 2020 14:17:46 +0800 [thread overview]
Message-ID: <20200929061747.27735-1-weix.xie@intel.com> (raw)
According to dpdk commit 62451c94a, remove flow-mark-support param when
it starts testpmd.
Signed-off-by: Xie wei <weix.xie@intel.com>
---
tests/TestSuite_cvl_fdir.py | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/tests/TestSuite_cvl_fdir.py b/tests/TestSuite_cvl_fdir.py
index 474ec2c9..e5a9c71e 100644
--- a/tests/TestSuite_cvl_fdir.py
+++ b/tests/TestSuite_cvl_fdir.py
@@ -2290,7 +2290,7 @@ class TestCVLFdir(TestCase):
self.pmd_output.start_testpmd(cores="1S/4C/1T",
param="--portmask=%s --rxq=%d --txq=%d --port-topology=loop" % (
self.portMask, rxq, txq),
- eal_param="-w %s,flow-mark-support=1 -w %s,flow-mark-support=1 --log-level=ice,7" % (
+ eal_param="-w %s -w %s --log-level=ice,7" % (
self.pci0, self.pci1), socket=self.ports_socket)
self.config_testpmd()
@@ -3031,9 +3031,7 @@ class TestCVLFdir(TestCase):
f.writelines(cmds_li)
self.dut.session.copy_file_to(cmd_path, cmd_path)
try:
- eal_param = self.dut.create_eal_parameters(cores="1S/4C/1T", ports=[self.pci0 + ",flow-mark-support=1",
- self.pci1 + ",flow-mark-support=1"],
- socket=self.ports_socket)
+ eal_param = self.dut.create_eal_parameters(cores="1S/4C/1T", ports=[self.pci0, self.pci1], socket=self.ports_socket)
param = " --log-level='ice,7' -- -i --portmask=%s --rxq=%d --txq=%d --port-topology=loop --cmdline-file=%s" % (
self.portMask, 64, 64, cmd_path)
command_line = self.dut.apps_name['test-pmd'] + eal_param + param
@@ -3140,7 +3138,7 @@ class TestCVLFdir(TestCase):
out = self.pmd_output.start_testpmd(cores="1S/4C/1T",
param="--portmask=%s --rxq=%d --txq=%d --port-topology=loop --cmdline-file=%s" % (
self.portMask, 64, 64, cmd_path),
- eal_param="-w %s,flow-mark-support=1 -w %s,flow-mark-support=1 --log-level='ice,7'" % (
+ eal_param="-w %s -w %s --log-level='ice,7'" % (
self.pci0, self.pci1), socket=self.ports_socket)
self.verify('Failed to create flow' not in out, "create some rule failed")
self.config_testpmd()
--
2.17.1
next reply other threads:[~2020-09-29 6:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 6:17 Xie wei [this message]
2020-09-29 6:17 ` [dts] [PATCH V1 2/2] test_plans/cvl_fdir_test_plan:remove " Xie wei
2020-09-29 6:54 ` Peng, Yuan
2020-09-29 6:53 ` [dts] [PATCH V1 1/2] tests/TestSuite_cvl_fdir:remove " Peng, Yuan
2020-10-12 8:10 ` 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=20200929061747.27735-1-weix.xie@intel.com \
--to=weix.xie@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).