From: Zou Ping <pingx.zou@intel.com>
To: dts@dpdk.org
Cc: Zou Ping <pingx.zou@intel.com>
Subject: [dts] [PATCH V1 2/2] test_plans/rteflow_priority: modify the priority of switch and fdir
Date: Fri, 22 Oct 2021 22:44:40 +0800 [thread overview]
Message-ID: <20211022144440.10099-2-pingx.zou@intel.com> (raw)
In-Reply-To: <20211022144440.10099-1-pingx.zou@intel.com>
the priority of switch and fdir changed,modified influenced rules.
Signed-off-by: Zou Ping <pingx.zou@intel.com>
---
test_plans/rteflow_priority_test_plan.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/test_plans/rteflow_priority_test_plan.rst b/test_plans/rteflow_priority_test_plan.rst
index b1815ce7..8ed5c971 100644
--- a/test_plans/rteflow_priority_test_plan.rst
+++ b/test_plans/rteflow_priority_test_plan.rst
@@ -77,14 +77,14 @@ Patterns in this case:
#. Create a rule with priority 0, Check the flow can be created but it will map to fdir filter::
- testpmd> 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> 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
ice_interrupt_handler(): OICR: MDD event
ice_flow_create(): Succeeded to create (1) flow
Flow rule #0 created
#. Create a rule with priority 1, check the flow can not be created for the vallue of priority is 0 in non-pipeline mode::
- testpmd> 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> 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
ice_flow_create(): Failed to create flow
Caught error type 4 (priority field): cause: 0x7ffe24e65738, Not support priority.: Invalid argument
@@ -96,14 +96,14 @@ Patterns in this case:
#. Create a rule with priority 0, Check the flow can be created but it will map to fdir filter::
- testpmd> 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> 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
ice_interrupt_handler(): OICR: MDD event
ice_flow_create(): Succeeded to create (1) flow
Flow rule #0 created
#. Create a rule with priority 1, check the flow can not be created for the vallue of priority is 0 in non-pipeline mode::
- testpmd> 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> 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
ice_flow_create(): Failed to create flow
Caught error type 4 (priority field): cause: 0x7ffe24e65738, Not support priority.: Invalid argument
--
2.17.1
prev parent 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 [dts] [PATCH V1 1/2] tests/rteflow_priority: " Zou Ping
2021-10-22 14:44 ` Zou Ping [this message]
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-2-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).