diff mbox series

[V1,2/2] test_plans/rteflow_priority: modify the priority of switch and fdir

Message ID 20211022144440.10099-2-pingx.zou@intel.com (mailing list archive)
State Superseded
Headers show
Series [V1,1/2] tests/rteflow_priority: modify the priority of switch and fdir | expand

Commit Message

Zou Ping Oct. 22, 2021, 2:44 p.m. UTC
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 mbox series

Patch

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