From: "Lin, Xueqin" <xueqin.lin@intel.com>
To: "Xia, YanX" <yanx.xia@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Xia, YanX" <yanx.xia@intel.com>
Subject: Re: [dts] [PATCH V1] test_plans/generic_flow_api_test_plan: modify cmd for rule of vf
Date: Wed, 27 Jan 2021 08:45:36 +0000 [thread overview]
Message-ID: <BL0PR11MB33647966649D690E08E54BC094BB9@BL0PR11MB3364.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210127065404.19410-1-yanx.xia@intel.com>
Acked-by: Xueqin Lin<xueqin.lin@intel.com>
> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Xia Yan
> Sent: Wednesday, January 27, 2021 2:54 PM
> To: dts@dpdk.org
> Cc: Xia, YanX <yanx.xia@intel.com>
> Subject: [dts] [PATCH V1] test_plans/generic_flow_api_test_plan: modify
> cmd for rule of vf
>
> add "transfer" in cmd for rule of vf
>
> Signed-off-by: Xia Yan <yanx.xia@intel.com>
> ---
> test_plans/generic_flow_api_test_plan.rst | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/test_plans/generic_flow_api_test_plan.rst
> b/test_plans/generic_flow_api_test_plan.rst
> index 33f5ec1c..6a36a635 100644
> --- a/test_plans/generic_flow_api_test_plan.rst
> +++ b/test_plans/generic_flow_api_test_plan.rst
> @@ -252,11 +252,11 @@ Test case: Fortville fdir for ipv4
>
> ipv4-other-vf0::
>
> - testpmd> flow create 0 ingress pattern eth / ipv4 src is 192.168.0.1 dst is
> 192.168.0.2 proto is 3 / vf id is 0 / end actions queue index 1 / end
> + testpmd> flow create 0 ingress transfer pattern eth / ipv4 src is
> 192.168.0.1 dst is 192.168.0.2 proto is 3 / vf id is 0 / end actions queue index
> 1 / end
>
> ipv4-sctp-vf1::
>
> - testpmd> flow create 0 ingress pattern eth / vlan tci is 2 / ipv4 src is
> 192.168.0.1 dst is 192.168.0.2 tos is 4 ttl is 4 / sctp src is 46 dst is 47 tag is 1 /
> vf id is 1 / end actions queue index 2 / end
> + testpmd> flow create 0 ingress transfer pattern eth / vlan tci is 2 / ipv4 src
> is 192.168.0.1 dst is 192.168.0.2 tos is 4 ttl is 4 / sctp src is 46 dst is 47 tag is 1
> / vf id is 1 / end actions queue index 2 / end
>
> ipv4-sctp drop::
>
> @@ -357,11 +357,11 @@ Test case: Fortville fdir for ipv6
>
> ipv6-other-vf0::
>
> - testpmd> flow create 0 ingress pattern eth / vlan tci is 5 / ipv6 src is
> 2001::3 dst is 2001::4 tc is 5 proto is 5 hop is 50 / vf id is 0 / end actions queue
> index 1 / end
> + testpmd> flow create 0 ingress transfer pattern eth / vlan tci is 5 / ipv6 src
> is 2001::3 dst is 2001::4 tc is 5 proto is 5 hop is 50 / vf id is 0 / end actions
> queue index 1 / end
>
> ipv6-tcp-vf1::
>
> - testpmd> flow create 0 ingress pattern eth / vlan tci is 4095 / ipv6 src is
> 2001::3 dst is 2001::4 tc is 6 hop is 60 / tcp src is 32 dst is 33 / vf id is 1 / end
> actions queue index 3 / end
> + testpmd> flow create 0 ingress transfer pattern eth / vlan tci is 4095 / ipv6
> src is 2001::3 dst is 2001::4 tc is 6 hop is 60 / tcp src is 32 dst is 33 / vf id is 1 /
> end actions queue index 3 / end
>
> ipv6-sctp-drop::
>
> @@ -369,7 +369,7 @@ Test case: Fortville fdir for ipv6
>
> ipv6-tcp-vf1-drop::
>
> - testpmd> flow create 0 ingress pattern eth / vlan tci is 8 / ipv6 src is
> 2001::3 dst is 2001::4 tc is 8 hop is 80 / tcp src is 32 dst is 33 / vf id is 1 / end
> actions drop / end
> + testpmd> flow create 0 ingress transfer pattern eth / vlan tci is 8 / ipv6 src
> is 2001::3 dst is 2001::4 tc is 8 hop is 80 / tcp src is 32 dst is 33 / vf id is 1 / end
> actions drop / end
>
> 3. send packets::
>
> @@ -438,7 +438,7 @@ Test case: Fortville fdir wrong parameters
>
> If create a rule on vf that has invalid queue ID::
>
> - testpmd> flow create 0 ingress pattern eth / ipv4 src is 192.168.0.1 dst is
> 192.168.0.2 proto is 3 / vf id is 0 / end actions queue index 4 / end
> + testpmd> flow create 0 ingress transfer pattern eth / ipv4 src is
> 192.168.0.1 dst is 192.168.0.2 proto is 3 / vf id is 0 / end actions queue index
> 4 / end
>
> it shows "Caught error type 11 (specific action): cause: 0x7ffc7bb9a338,
> Invalid queue ID for FDIR".
> @@ -501,11 +501,11 @@ Test case: Fortville tunnel vxlan
>
> vni + inner mac + inner vlan + actions vf::
>
> - testpmd> flow create 0 ingress pattern eth / ipv4 / udp / vxlan vni is 6 /
> eth dst is 00:11:22:33:44:55 / vlan tci is 30 / end actions vf id 0 / queue index
> 1 / end
> + testpmd> flow create 0 ingress transfer pattern eth / ipv4 / udp / vxlan
> vni is 6 / eth dst is 00:11:22:33:44:55 / vlan tci is 30 / end actions vf id 0 /
> queue index 1 / end
>
> inner mac + outer mac + vni + actions vf::
>
> - testpmd> flow create 0 ingress pattern eth dst is 00:11:22:33:44:66 / ipv4 /
> udp / vxlan vni is 7 / eth dst is 00:11:22:33:44:55 / end actions vf id 0 / queue
> index 3 / end
> + testpmd> flow create 0 ingress transfer pattern eth dst is
> 00:11:22:33:44:66 / ipv4 / udp / vxlan vni is 7 / eth dst is 00:11:22:33:44:55 /
> end actions vf id 0 / queue index 3 / end
>
> 3. send packets::
>
> @@ -610,11 +610,11 @@ Test case: Fortville tunnel nvgre
>
> tni + inner mac + inner vlan + actions vf::
>
> - testpmd> flow create 0 ingress pattern eth / ipv4 / nvgre tni is 0x112266 /
> eth dst is 00:11:22:33:44:55 / vlan tci is 60 / end actions vf id 0 / queue index
> 1 / end
> + testpmd> flow create 0 ingress transfer pattern eth / ipv4 / nvgre tni is
> 0x112266 / eth dst is 00:11:22:33:44:55 / vlan tci is 60 / end actions vf id 0 /
> queue index 1 / end
>
> inner mac + outer mac + tni + actions vf::
>
> - testpmd> flow create 0 ingress pattern eth dst is 00:11:22:33:44:66 / ipv4 /
> nvgre tni is 0x112277 / eth dst is 00:11:22:33:44:55 / end actions vf id 1 /
> queue index 3 / end
> + testpmd> flow create 0 ingress transfer pattern eth dst is
> 00:11:22:33:44:66 / ipv4 / nvgre tni is 0x112277 / eth dst is 00:11:22:33:44:55
> / end actions vf id 1 / queue index 3 / end
>
> 3. send packets::
>
> --
> 2.17.1
next prev parent reply other threads:[~2021-01-27 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 6:54 Xia Yan
2021-01-27 8:45 ` Lin, Xueqin [this message]
2021-02-02 8:39 ` 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=BL0PR11MB33647966649D690E08E54BC094BB9@BL0PR11MB3364.namprd11.prod.outlook.com \
--to=xueqin.lin@intel.com \
--cc=dts@dpdk.org \
--cc=yanx.xia@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).