From: Zou Ping <pingx.zou@intel.com>
To: dts@dpdk.org
Cc: Zou Ping <pingx.zou@intel.com>
Subject: [dts] [PATCH V1 1/2] tests/rteflow_priority: modify the priority of switch and fdir
Date: Fri, 22 Oct 2021 22:44:39 +0800 [thread overview]
Message-ID: <20211022144440.10099-1-pingx.zou@intel.com> (raw)
the priority of switch and fdir changed,modified influenced rules.
Signed-off-by: Zou Ping <pingx.zou@intel.com>
---
tests/TestSuite_rteflow_priority.py | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/tests/TestSuite_rteflow_priority.py b/tests/TestSuite_rteflow_priority.py
index 23aea82f..3fb8720a 100755
--- a/tests/TestSuite_rteflow_priority.py
+++ b/tests/TestSuite_rteflow_priority.py
@@ -204,9 +204,9 @@ class TestRteflowPriority(TestCase):
out = self.dut.send_expect(command, "testpmd> ", 120)
self.logger.debug(out)
- out=self.dut.send_expect("flow create 0 priority 0 ingress pattern eth / ipv4 src is 192.168.0.2 dst is 192.168.0.3 tos is 4 / end actions queue index 2 / end", "testpmd>", 15)
+ out=self.dut.send_expect("flow create 0 priority 0 ingress pattern eth / ipv4 src is 192.168.0.2 dst is 192.168.0.3 tos is 4 / end actions queue index 2 / mark / end", "testpmd>", 15)
self.verify( "Successed" and "(1)" in out, "failed: rule can't be created to fdir")
- out=self.dut.send_expect("flow create 0 priority 1 ingress pattern eth / ipv4 src is 192.168.0.2 dst is 192.168.0.3 tos is 4 / end actions queue index 2 / end", "testpmd>", 15)
+ out=self.dut.send_expect("flow create 0 priority 1 ingress pattern eth / ipv4 src is 192.168.0.2 dst is 192.168.0.3 tos is 4 / end actions queue index 2 / mark / end", "testpmd>", 15)
self.verify( "Failed" in out, "failed: default value of priority is 0 in non-pipeline mode")
self.dut.send_expect("flow flush 0", "testpmd>", 20)
self.dut.send_expect("quit", "#", 50)
@@ -216,9 +216,9 @@ class TestRteflowPriority(TestCase):
out = self.dut.send_expect(command, "testpmd> ", 120)
self.logger.debug(out)
- out=self.dut.send_expect("flow create 0 priority 0 ingress pattern eth / ipv4 src is 192.168.0.2 dst is 192.168.0.3 tos is 4 / end actions queue index 2 / end", "testpmd>", 15)
+ out=self.dut.send_expect("flow create 0 priority 0 ingress pattern eth / ipv4 src is 192.168.0.2 dst is 192.168.0.3 tos is 4 / end actions queue index 2 / mark / end", "testpmd>", 15)
self.verify( "Successed" and "(1)" in out, "failed: rule can't be created to fdir")
- out=self.dut.send_expect("flow create 0 priority 1 ingress pattern eth / ipv4 src is 192.168.0.2 dst is 192.168.0.3 tos is 4 / end actions queue index 2 / end", "testpmd>", 15)
+ out=self.dut.send_expect("flow create 0 priority 1 ingress pattern eth / ipv4 src is 192.168.0.2 dst is 192.168.0.3 tos is 4 / end actions queue index 2 / mark / end", "testpmd>", 15)
self.verify( "Failed" in out, "failed: default value of priority is 0 in non-pipeline mode")
self.dut.send_expect("flow flush 0", "testpmd>", 20)
self.dut.send_expect("quit", "#", 50)
--
2.17.1
next reply other threads:[~2021-10-22 6:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 14:44 Zou Ping [this message]
2021-10-22 14:44 ` [dts] [PATCH V1 2/2] test_plans/rteflow_priority: " Zou Ping
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=20211022144440.10099-1-pingx.zou@intel.com \
--to=pingx.zou@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).