diff mbox series

[V2,1/2] test_plans/cvl_dcf_flow_priority: modify rule priority

Message ID 1631684394-95135-1-git-send-email-songx.jiale@intel.com (mailing list archive)
State Accepted
Headers
Series [V2,1/2] test_plans/cvl_dcf_flow_priority: modify rule priority |

Commit Message

Jiale, SongX Sept. 15, 2021, 5:39 a.m. UTC 
  because the priority of the dpdk rule is changed from 0<1<2... to 0>1>2..., 
modify the testplan

Signed-off-by: Jiale Song <songx.jiale@intel.com>
---
 .../cvl_dcf_flow_priority_test_plan.rst       | 26 +++++++++----------
 1 file changed, 13 insertions(+), 13 deletions(-)
 mode change 100644 => 100755 test_plans/cvl_dcf_flow_priority_test_plan.rst

Comments

Tu, Lijuan Sept. 27, 2021, 6:31 a.m. UTC | #1 
> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Jiale Song
> Sent: 2021年9月15日 13:40
> To: dts@dpdk.org
> Cc: Jiale, SongX <songx.jiale@intel.com>
> Subject: [dts] [PATCH V2 1/2] test_plans/cvl_dcf_flow_priority: modify rule
> priority
> 
> because the priority of the dpdk rule is changed from 0<1<2... to 0>1>2...,
> modify the testplan
> 
> Signed-off-by: Jiale Song <songx.jiale@intel.com>

Could you please provide me dpdk commit ?
Huang, ZhiminX Oct. 20, 2021, 9:47 a.m. UTC | #2 
> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Tu, Lijuan
> Sent: Monday, September 27, 2021 2:32 PM
> To: Jiale, SongX <songx.jiale@intel.com>; dts@dpdk.org
> Cc: Jiale, SongX <songx.jiale@intel.com>
> Subject: Re: [dts] [PATCH V2 1/2] test_plans/cvl_dcf_flow_priority: modify rule
> priority
> 
> > -----Original Message-----
> > From: dts <dts-bounces@dpdk.org> On Behalf Of Jiale Song
> > Sent: 2021年9月15日 13:40
> > To: dts@dpdk.org
> > Cc: Jiale, SongX <songx.jiale@intel.com>
> > Subject: [dts] [PATCH V2 1/2] test_plans/cvl_dcf_flow_priority: modify
> > rule priority
> >
> > because the priority of the dpdk rule is changed from 0<1<2... to
> > 0>1>2..., modify the testplan
> >
> > Signed-off-by: Jiale Song <songx.jiale@intel.com>
> 
> Could you please provide me dpdk commit ?

According to dpdk commit 72908beba944b57e3e1cbe0edf7728a192230d2b, modified testplan.
diff mbox series

Patch

diff --git a/test_plans/cvl_dcf_flow_priority_test_plan.rst b/test_plans/cvl_dcf_flow_priority_test_plan.rst
old mode 100644
new mode 100755
index 8ae6052..38e86a7
--- a/test_plans/cvl_dcf_flow_priority_test_plan.rst
+++ b/test_plans/cvl_dcf_flow_priority_test_plan.rst
@@ -118,16 +118,16 @@  test steps for supported pattern
 ================================
 1. validate rules: two rules have same pattern, input set but different priority and action(priority 0 -> to vf 1, priority 1 -> to vf 2).
 2. create rules and list rules.
-3. send matched packets, check vf 2 receive the packets for hiting the priority 1.
+3. send matched packets, check vf 1 receive the packets for hiting the priority 0.
 4. send mismatched packets, check the packets are not received by vf 1 or 2.
-5. destroy rule with priority 1, list rules.
-6. send matched packets, check vf 1 receive the packets for hiting the priority 0.
+5. destroy rule with priority 0, list rules.
+6. send matched packets, check vf 2 receive the packets for hiting the priority 1.
 7. send mismatched packets, check the packets are not received by vf 1 or 2.
-8. recreate rules which priority is 1, list rule.
-9. destroy rule with priority 0, list rules.
-10. send matched packets, check vf 2 receive the packets for hiting the priority 1.
+8. recreate rules which priority is 0, list rule.
+9. destroy rule with priority 1, list rules.
+10. send matched packets, check vf 1 receive the packets for hiting the priority 0.
 11. send mismatched packets, check the packets are not received by vf 1 or 2.
-12. destroy rule with priority 1, list rules.
+12. destroy rule with priority 0, list rules.
 13. send matched packets, check the packets are not received by vf 1 or 2.
 
 
@@ -1745,12 +1745,12 @@  subcase 3: some rules overlap
 -----------------------------
 1. create rules::
 
-    flow create 0 priority 0 ingress pattern eth / vlan / vlan / pppoes / pppoe_proto_id is 0x21 / end actions vf id 1 / end
-    flow create 0 priority 0 ingress pattern eth / vlan / vlan tci is 2 / end actions vf id 1 / end
-    flow create 0 priority 1 ingress pattern eth / vlan / vlan / pppoes seid is 1 / ipv4 / end actions vf id 2 / end
-    flow create 0 priority 1 ingress pattern eth dst is 00:00:00:01:03:03 / vlan / vlan / end actions vf id 2 / end
-    flow create 0 priority 1 ingress pattern eth dst is 00:00:00:01:03:03 / end actions vf id 3 / end
-    flow create 0 priority 1 ingress pattern eth / vlan tci is 1 / vlan tci is 2 / end actions vf id 3 / end
+    flow create 0 priority 1 ingress pattern eth / vlan / vlan / pppoes / pppoe_proto_id is 0x21 / end actions vf id 1 / end
+    flow create 0 priority 1 ingress pattern eth / vlan / vlan tci is 2 / end actions vf id 1 / end
+    flow create 0 priority 0 ingress pattern eth / vlan / vlan / pppoes seid is 1 / ipv4 / end actions vf id 2 / end
+    flow create 0 priority 0 ingress pattern eth dst is 00:00:00:01:03:03 / vlan / vlan / end actions vf id 2 / end
+    flow create 0 priority 0 ingress pattern eth dst is 00:00:00:01:03:03 / end actions vf id 3 / end
+    flow create 0 priority 0 ingress pattern eth / vlan tci is 1 / vlan tci is 2 / end actions vf id 3 / end
 
 2. check all the rules exist in the list::