From: "Liu, Yong" <yong.liu@intel.com>
To: Peng Yuan <yuan.peng@intel.com>, dts@dpdk.org
Subject: Re: [dts] [PATCH] test_plans: modify the L2 tunnel filter command format
Date: Mon, 20 Nov 2017 20:44:49 +0800 [thread overview]
Message-ID: <5A12CE41.6070103@intel.com> (raw)
In-Reply-To: <1510735766-48243-1-git-send-email-yuan.peng@intel.com>
Yuan,
Could you please explain in commit log why disable-rss option is removed
from PF testpmd?
I only saw flow commands for l2-tunnel is changed, how about others?
Thanks,
Marvin
On 11/15/2017 04:49 PM, Peng Yuan wrote:
> Signed-off-by: Peng Yuan <yuan.peng@intel.com>
>
> diff --git a/test_plans/generic_flow_api_test_plan.rst b/test_plans/generic_flow_api_test_plan.rst
> index f7ce61e..73d1a9a 100644
> --- a/test_plans/generic_flow_api_test_plan.rst
> +++ b/test_plans/generic_flow_api_test_plan.rst
> @@ -805,7 +805,7 @@ Test case: IXGBE L2-tunnel(supported by x552 and x550)
>
> 1. Launch the app ``testpmd`` with the following arguments::
>
> - ./x86_64-native-linuxapp-gcc/app/testpmd -c 1ffff -n 4 -w 05:00.0 --file-prefix=pf --socket-mem=1024,1024 -- -i --rxq=16 --txq=16 --disable-rss
> + ./x86_64-native-linuxapp-gcc/app/testpmd -c 1ffff -n 4 -w 05:00.0 --file-prefix=pf --socket-mem=1024,1024 -- -i --rxq=16 --txq=16
> testpmd> set fwd rxonly
> testpmd> set verbose 1
> testpmd> start
> @@ -830,9 +830,9 @@ Test case: IXGBE L2-tunnel(supported by x552 and x550)
>
> 2. create filter rules::
>
> - testpmd> flow create 0 ingress pattern e_tag grp_ecid_b is 0x1309 / end actions queue index 0 / end
> - testpmd> flow create 0 ingress pattern e_tag grp_ecid_b is 0x1308 / end actions queue index 1 / end
> - testpmd> flow create 0 ingress pattern e_tag grp_ecid_b is 0x1307 / end actions queue index 2 / end
> + testpmd> flow create 0 ingress pattern e_tag grp_ecid_b is 0x1309 / end actions vf id 0 / end
> + testpmd> flow create 0 ingress pattern e_tag grp_ecid_b is 0x1308 / end actions vf id 1 / end
> + testpmd> flow create 0 ingress pattern e_tag grp_ecid_b is 0x1307 / end actions pf / end
>
> 3. send packets::
>
> @@ -841,7 +841,7 @@ Test case: IXGBE L2-tunnel(supported by x552 and x550)
> pkt3 = Ether(dst="00:11:22:33:44:55")/Dot1BR(GRP=0x1, ECIDbase=0x307)/Raw('x' * 20)
> pkt4 = Ether(dst="00:11:22:33:44:55")/Dot1BR(GRP=0x2, ECIDbase=0x309)/Raw('x' * 20)
>
> - verify pkt1 to vf0 queue0, pkt2 to vf1 queue0, pkt3 to pf queue0,
> + verify pkt1 to vf0, pkt2 to vf1, pkt3 to pf,
> pkt4 can't received by pf and vfs.
>
> 4. verify rules can be listed and destroyed::
next prev parent reply other threads:[~2017-11-20 4:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 8:49 Peng Yuan
2017-11-20 12:44 ` Liu, Yong [this message]
2017-11-16 6:05 Peng Yuan
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=5A12CE41.6070103@intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=yuan.peng@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).