From: Zhimin Huang <zhiminx.huang@intel.com>
To: dts@dpdk.org
Cc: Zhimin Huang <zhiminx.huang@intel.com>
Subject: [dts] [PATCH V1] test_plans/cvl_iavf_ip_fragment_rte_flow:simply ipfargment rule
Date: Wed, 28 Jul 2021 23:03:59 +0800 [thread overview]
Message-ID: <20210728150400.31037-1-zhiminx.huang@intel.com> (raw)
*.according to the change of dpdk, simply ipfragment rule
Signed-off-by: Zhimin Huang <zhiminx.huang@intel.com>
---
...vl_iavf_ip_fragment_rte_flow_test_plan.rst | 38 +++++++++----------
1 file changed, 19 insertions(+), 19 deletions(-)
diff --git a/test_plans/cvl_iavf_ip_fragment_rte_flow_test_plan.rst b/test_plans/cvl_iavf_ip_fragment_rte_flow_test_plan.rst
index 6b2f82c9..9813b53c 100644
--- a/test_plans/cvl_iavf_ip_fragment_rte_flow_test_plan.rst
+++ b/test_plans/cvl_iavf_ip_fragment_rte_flow_test_plan.rst
@@ -111,9 +111,9 @@ take 'MAC_IPV4_FRAG fdir queue index' for fdir example
------------------------------------------------------
1. validate and create rule::
- flow validate 0 ingress pattern eth / ipv4 packet_id spec 0 packet_id last 0xffff packet_id mask 0xffff fragment_offset spec 0x2000 fragment_offset last 0x1fff fragment_offset mask 0xffff / end actions queue index 1 / mark / end
+ flow validate 0 ingress pattern eth / ipv4 fragment_offset spec 0x2000 fragment_offset mask 0x2000 / end actions queue index 1 / mark / end
Flow rule validated
- flow create 0 ingress pattern eth / ipv4 packet_id spec 0 packet_id last 0xffff packet_id mask 0xffff fragment_offset spec 0x2000 fragment_offset last 0x1fff fragment_offset mask 0xffff / end actions queue index 1 / mark / end
+ flow create 0 ingress pattern eth / ipv4 fragment_offset spec 0x2000 fragment_offset mask 0x2000 / end actions queue index 1 / mark / end
Flow rule #0 created
2. send matched pkts and check two pkts distributed to queue 1, `RSS hash=0x261a7deb - RSS queue=0x1` in output::
@@ -245,7 +245,7 @@ Subcase 1: MAC_IPV4_FRAG fdir queue index
1. rules::
- flow create 0 ingress pattern eth / ipv4 packet_id spec 0 packet_id last 0xffff packet_id mask 0xffff fragment_offset spec 0x2000 fragment_offset last 0x1fff fragment_offset mask 0xffff / end actions queue index 1 / mark / end
+ flow create 0 ingress pattern eth / ipv4 fragment_offset spec 0x2000 fragment_offset mask 0x2000 / end actions queue index 1 / mark / end
2. matched packets::
@@ -260,7 +260,7 @@ Subcase 2: MAC_IPV4_FRAG fdir rss queues
1. rules::
- flow create 0 ingress pattern eth / ipv4 packet_id spec 0 packet_id last 0xffff packet_id mask 0xffff fragment_offset spec 0x2000 fragment_offset last 0x1fff fragment_offset mask 0xffff / end actions rss queues 2 3 end / mark / end
+ flow create 0 ingress pattern eth / ipv4 fragment_offset spec 0x2000 fragment_offset mask 0x2000 / end actions rss queues 2 3 end / mark / end
2. matched packets::
@@ -275,7 +275,7 @@ Subcase 3: MAC_IPV4_FRAG fdir passthru
1. rules::
- flow create 0 ingress pattern eth / ipv4 packet_id spec 0 packet_id last 0xffff packet_id mask 0xffff fragment_offset spec 0x2000 fragment_offset last 0x1fff fragment_offset mask 0xffff / end actions passthru / mark / end
+ flow create 0 ingress pattern eth / ipv4 fragment_offset spec 0x2000 fragment_offset mask 0x2000 / end actions passthru / mark / end
2. matched packets::
@@ -290,7 +290,7 @@ Subcase 4: MAC_IPV4_FRAG fdir drop
1. rules::
- flow create 0 ingress pattern eth / ipv4 packet_id spec 0 packet_id last 0xffff packet_id mask 0xffff fragment_offset spec 0x2000 fragment_offset last 0x1fff fragment_offset mask 0xffff / end actions drop / end
+ flow create 0 ingress pattern eth / ipv4 fragment_offset spec 0x2000 fragment_offset mask 0x2000 / end actions drop / end
2. matched packets::
@@ -305,7 +305,7 @@ Subcase 5: MAC_IPV4_FRAG fdir mark+rss
1. rules::
- flow create 0 ingress pattern eth / ipv4 packet_id spec 0 packet_id last 0xffff packet_id mask 0xffff fragment_offset spec 0x2000 fragment_offset last 0x1fff fragment_offset mask 0xffff / end actions mark / rss / end
+ flow create 0 ingress pattern eth / ipv4 fragment_offset spec 0x2000 fragment_offset mask 0x2000 / end actions mark / rss / end
2. matched packets::
@@ -320,7 +320,7 @@ Subcase 6: MAC_IPV4_FRAG fdir mark
1. rules::
- flow create 0 ingress pattern eth / ipv4 packet_id spec 0 packet_id last 0xffff packet_id mask 0xffff fragment_offset spec 0x2000 fragment_offset last 0x1fff fragment_offset mask 0xffff / end actions mark id 1 / end
+ flow create 0 ingress pattern eth / ipv4 fragment_offset spec 0x2000 fragment_offset mask 0x2000 / end actions mark id 1 / end
2. matched packets::
@@ -338,7 +338,7 @@ Subcase 1: MAC_IPV6_FRAG fdir queue index
1. rules::
- flow create 0 ingress pattern eth / ipv6 / ipv6_frag_ext packet_id spec 0 packet_id last 0xffffffff packet_id mask 0xffffffff frag_data spec 0x0001 frag_data last 0xffff frag_data mask 0xffff / end actions queue index 1 / mark / end
+ flow create 0 ingress pattern eth / ipv6 / ipv6_frag_ext frag_data spec 0x0001 frag_data mask 0x0001 / end actions queue index 1 / mark / end
2. matched packets::
@@ -353,7 +353,7 @@ Subcase 2: MAC_IPV6_FRAG fdir rss queues
1. rules::
- flow create 0 ingress pattern eth / ipv6 / ipv6_frag_ext packet_id spec 0 packet_id last 0xffffffff packet_id mask 0xffffffff frag_data spec 0x0001 frag_data last 0xffff frag_data mask 0xffff / end actions rss queues 2 3 / mark / end
+ flow create 0 ingress pattern eth / ipv6 / ipv6_frag_ext frag_data spec 0x0001 frag_data mask 0x0001 / end actions rss queues 2 3 end / mark / end
2. matched packets::
@@ -368,7 +368,7 @@ Subcase 3: MAC_IPV6_FRAG fdir passthru
1. rules::
- flow create 0 ingress pattern eth / ipv6 / ipv6_frag_ext packet_id spec 0 packet_id last 0xffffffff packet_id mask 0xffffffff frag_data spec 0x0001 frag_data last 0xffff frag_data mask 0xffff / end actions passthru / mark / end
+ flow create 0 ingress pattern eth / ipv6 / ipv6_frag_ext frag_data spec 0x0001 frag_data mask 0x0001 / end actions passthru / mark / end
2. matched packets::
@@ -383,7 +383,7 @@ Subcase 4: MAC_IPV6_FRAG fdir drop
1. rules::
- flow create 0 ingress pattern eth / ipv6 / ipv6_frag_ext packet_id spec 0 packet_id last 0xffffffff packet_id mask 0xffffffff frag_data spec 0x0001 frag_data last 0xffff frag_data mask 0xffff / end actions drop / end
+ flow create 0 ingress pattern eth / ipv6 / ipv6_frag_ext frag_data spec 0x0001 frag_data mask 0x0001 / end actions drop / end
2. matched packets::
@@ -398,7 +398,7 @@ Subcase 5: MAC_IPV6_FRAG fdir mark+rss
1. rules::
- flow create 0 ingress pattern eth / ipv6 / ipv6_frag_ext packet_id spec 0 packet_id last 0xffffffff packet_id mask 0xffffffff frag_data spec 0x0001 frag_data last 0xffff frag_data mask 0xffff / end actions mark / rss / end
+ flow create 0 ingress pattern eth / ipv6 / ipv6_frag_ext frag_data spec 0x0001 frag_data mask 0x0001 / end actions mark / rss / end
2. matched packets::
@@ -413,7 +413,7 @@ Subcase 6: MAC_IPV6_FRAG fdir mark
1. rules::
- flow create 0 ingress pattern eth / ipv6 / ipv6_frag_ext packet_id spec 0 packet_id last 0xffffffff packet_id mask 0xffffffff frag_data spec 0x0001 frag_data last 0xffff frag_data mask 0xffff / end actions mark id 1 / end
+ flow create 0 ingress pattern eth / ipv6 / ipv6_frag_ext frag_data spec 0x0001 frag_data mask 0x0001 / end actions mark id 1 / end
2. matched packets::
@@ -446,7 +446,7 @@ take 'mac_ipv4_frag_l3src_fdir_queue_index' example::
1.rules:
- flow create 0 ingress pattern eth / ipv4 src is 192.168.1.1 packet_id spec 0 packet_id last 0xffff packet_id mask 0xffff fragment_offset spec 0x2000 fragment_offset last 0x1fff fragment_offset mask 0xffff / end actions queue index 1 / mark / end
+ flow create 0 ingress pattern eth / ipv4 src is 192.168.1.1 fragment_offset spec 0x2000 fragment_offset mask 0x2000 / end actions queue index 1 / mark / end
2.matched packets:
@@ -473,7 +473,7 @@ take 'mac_ipv6_frag_l3src_fdir_queue_index' example::
1.rules:
- flow create 0 ingress pattern eth / ipv6 src is 2001::1 / ipv6_frag_ext packet_id spec 0 packet_id last 0xffffffff packet_id mask 0xffffffff frag_data spec 0x0001 frag_data last 0xffff frag_data mask 0xffff / end actions queue index 1 / mark / end
+ flow create 0 ingress pattern eth / ipv6 src is 2001::1 / ipv6_frag_ext frag_data spec 0x0001 frag_data mask 0x0001 / end actions queue index 1 / mark / end
2.matched packets:
@@ -544,7 +544,7 @@ Subcase 1: exclusive validation fdir rule
1. create fdir filter rules::
flow create 0 ingress pattern eth / ipv4 src is 192.168.0.20 / end actions queue index 1 / end
- flow create 0 ingress pattern eth / ipv4 packet_id spec 0 packet_id last 0xffff packet_id mask 0xffff fragment_offset spec 0x2000 fragment_offset last 0x1fff fragment_offset mask 0xffff / end actions queue index 2 / end
+ flow create 0 ingress pattern eth / ipv4 fragment_offset spec 0x2000 fragment_offset mask 0x2000 / end actions queue index 1 / end actions queue index 2 / end
2. hit pattern/defined input set id, the pkt received for queue 2::
@@ -554,7 +554,7 @@ Subcase 2: exclusive validation fdir rule
-----------------------------------------
1. create fdir filter rules::
- flow create 0 ingress pattern eth / ipv4 packet_id spec 0 packet_id last 0xffff packet_id mask 0xffff fragment_offset spec 0x2000 fragment_offset last 0x1fff fragment_offset mask 0xffff / end actions queue index 2 / end
+ flow create 0 ingress pattern eth / ipv4 fragment_offset spec 0x2000 fragment_offset mask 0x2000 / end actions queue index 1 / end actions queue index 2 / end
flow create 0 ingress pattern eth / ipv4 src is 192.168.0.20 / end actions queue index 1 / end
2. hit pattern/defined input set id, the pkt received for queue 2::
@@ -568,7 +568,7 @@ Subcase 3: exclusive validation rss rule
flow create 0 ingress pattern eth / ipv4 / end actions rss types ipv4 end key_len 0 queues end / end
flow create 0 ingress pattern eth / ipv4 / end actions rss types ipv4-frag end key_len 0 queues end / end
-2. hit pattern/defined input set id, the pkt received for rss diffent queue::
+2. hit pattern/defined input set id, the pkt received for rss same queue::
p=Ether()/IP(id=47750)/Raw('X'*666); pkts=fragment6(p, 500)
p=Ether()/IP(id=47751)/Raw('X'*666); pkts=fragment6(p, 500)
--
2.17.1
next reply other threads:[~2021-07-28 6:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 15:03 Zhimin Huang [this message]
2021-07-28 15:04 ` [dts] [PATCH V1] tests/cvl_iavf_ip_fragment_rte_flow:simply ipfragment rule Zhimin Huang
2021-07-28 6:33 ` Huang, ZhiminX
2021-08-04 2:21 ` Fu, Qi
2021-09-14 8:14 ` Tu, Lijuan
2021-08-04 2:23 ` [dts] [PATCH V1] test_plans/cvl_iavf_ip_fragment_rte_flow:simply ipfargment rule Fu, Qi
2021-09-13 4:39 ` Tu, Lijuan
2021-09-13 5:12 ` Huang, ZhiminX
2021-09-14 8:13 ` 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=20210728150400.31037-1-zhiminx.huang@intel.com \
--to=zhiminx.huang@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).