From: "Huang, ZhiminX" <zhiminx.huang@intel.com>
To: "Tu, Lijuan" <lijuan.tu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1] test_plans/cvl_ip_fragment_rte_flow:simply ipfragment rule
Date: Mon, 13 Sep 2021 05:13:30 +0000 [thread overview]
Message-ID: <BN0PR11MB57120F15156FE9FAE7783BF4FDD99@BN0PR11MB5712.namprd11.prod.outlook.com> (raw)
In-Reply-To: <498cfc83206f45059a1bcc974241ea9e@intel.com>
Hi lijuan,
Add dpdk commit for simply pf ip fragment code:
5ae0906ee7d78834431af568aade1aace240e717
> -----Original Message-----
> From: Tu, Lijuan <lijuan.tu@intel.com>
> Sent: Monday, September 13, 2021 12:43 PM
> To: Huang, ZhiminX <zhiminx.huang@intel.com>; dts@dpdk.org
> Cc: Huang, ZhiminX <zhiminx.huang@intel.com>
> Subject: RE: [dts] [PATCH V1] test_plans/cvl_ip_fragment_rte_flow:simply
> ipfragment rule
>
> Could please provide dpdk commit ?
>
> > -----Original Message-----
> > From: dts <dts-bounces@dpdk.org> On Behalf Of Zhimin Huang
> > Sent: 2021年7月28日 22:12
> > To: dts@dpdk.org
> > Cc: Huang, ZhiminX <zhiminx.huang@intel.com>
> > Subject: [dts] [PATCH V1] test_plans/cvl_ip_fragment_rte_flow:simply
> > ipfragment rule
> >
> > *.sync dpdk code to simply ipfragment rule
> >
> > Signed-off-by: Zhimin Huang <zhiminx.huang@intel.com>
> > ---
> > .../cvl_ip_fragment_rte_flow_test_plan.rst | 42 +++++++++----------
> > 1 file changed, 21 insertions(+), 21 deletions(-)
> >
> > diff --git a/test_plans/cvl_ip_fragment_rte_flow_test_plan.rst
> > b/test_plans/cvl_ip_fragment_rte_flow_test_plan.rst
> > index 634550b1..704b590c 100644
> > --- a/test_plans/cvl_ip_fragment_rte_flow_test_plan.rst
> > +++ b/test_plans/cvl_ip_fragment_rte_flow_test_plan.rst
> > @@ -104,9 +104,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::
> > @@ -238,7 +238,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::
> >
> > @@ -253,7 +253,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::
> >
> > @@ -268,7 +268,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::
> >
> > @@ -283,7 +283,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::
> >
> > @@ -298,7 +298,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::
> >
> > @@ -313,7 +313,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::
> >
> > @@ -331,7 +331,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::
> >
> > @@ -346,7 +346,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::
> >
> > @@ -361,7 +361,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::
> >
> > @@ -376,7 +376,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::
> >
> > @@ -391,7 +391,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::
> >
> > @@ -406,7 +406,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::
> >
> > @@ -427,7 +427,7 @@ take 'mac_ipv4_frag_l2dst_fdir_queue_index'
> example::
> >
> > 1.rules:
> >
> > - flow create 0 ingress pattern eth dst is 00:00:00:00:00:01 / 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 dst is 00:00:00:00:00:01 /
> > + ipv4 fragment_offset spec 0x2000 fragment_offset mask 0x2000 / end
> > + actions queue index 1 / mark / end
> >
> > 2.matched packets:
> >
> > @@ -452,7 +452,7 @@ take 'mac_ipv6_frag_l2dst_fdir_queue_index'
> example::
> >
> > 1.rules:
> >
> > - flow create 0 ingress pattern eth dst is 00:00:00:00:00:01 / 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 dst is 00:00:00:00:00:01 /
> > + ipv6 / ipv6_frag_ext frag_data spec 0x0001 frag_data mask 0x0001 /
> > + end actions queue index 1 / mark / end
> >
> > 2.matched packets:
> >
> > @@ -478,7 +478,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:
> >
> > @@ -505,7 +505,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:
> >
> > @@ -576,7 +576,7 @@ Subcase 1: exclusive validation fdir rule 1.
> > create fdir filter rules::
> >
> > flow create 0 ingress pattern eth dst is 00:11:22:33:44:55 /
> > 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 2 / end
> >
> > 2. hit pattern/defined input set id, the pkt received for queue 2::
> >
> > @@ -586,7 +586,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 2 / end
> > flow create 0 ingress pattern eth dst is 00:11:22:33:44:55 /
> > 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::
> > @@ -600,7 +600,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 prev parent reply other threads:[~2021-09-13 5:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 14:11 Zhimin Huang
2021-07-28 14:11 ` [dts] [PATCH V1] tests/cvl_ip_fragment_rte_flow:simply ipfargment rule Zhimin Huang
2021-07-28 6:05 ` Huang, ZhiminX
2021-09-14 8:19 ` Tu, Lijuan
2021-09-13 4:43 ` [dts] [PATCH V1] test_plans/cvl_ip_fragment_rte_flow:simply ipfragment rule Tu, Lijuan
2021-09-13 5:13 ` Huang, ZhiminX [this message]
2021-09-14 8:20 ` 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=BN0PR11MB57120F15156FE9FAE7783BF4FDD99@BN0PR11MB5712.namprd11.prod.outlook.com \
--to=zhiminx.huang@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
/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).