From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Zeng, XiaoxiaoX" <xiaoxiaox.zeng@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Zeng, XiaoxiaoX" <xiaoxiaox.zeng@intel.com>
Subject: Re: [dts] [PATCH V4] tests/kernelpf_iavf:add vlan filter for CVL on case test_vf_vlan_strip
Date: Fri, 20 Dec 2019 07:48:32 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB8A0F1@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20191211194301.25202-1-xiaoxiaox.zeng@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Xiaoxiao Zeng
> Sent: Thursday, December 12, 2019 3:43 AM
> To: dts@dpdk.org
> Cc: Zeng, XiaoxiaoX <xiaoxiaox.zeng@intel.com>
> Subject: [dts] [PATCH V4] tests/kernelpf_iavf:add vlan filter for CVL on case
> test_vf_vlan_strip
>
> *.As FW/HW problem which caused older FW works and newer FW not
> work,need to add 'vlan set filter' in testpmd to pass this case.
>
> Signed-off-by: Xiaoxiao Zeng <xiaoxiaox.zeng@intel.com>
> ---
> tests/TestSuite_kernelpf_iavf.py | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/tests/TestSuite_kernelpf_iavf.py
> b/tests/TestSuite_kernelpf_iavf.py
> index 668eb28..3995238 100644
> --- a/tests/TestSuite_kernelpf_iavf.py
> +++ b/tests/TestSuite_kernelpf_iavf.py
> @@ -510,6 +510,9 @@ class TestKernelpfIavf(TestCase):
>
> # disable strip
> self.vm_testpmd.execute_cmd("vlan set strip off 0")
> + if self.nic.startswith('columbiaville'):
> + self.vm_testpmd.execute_cmd("vlan set filter on 0")
> + self.vm_testpmd.execute_cmd("rx_vlan add %d 0" % random_vlan)
> self.start_tcpdump(self.tester_intf)
> out = self.send_and_getout(vlan=random_vlan, pkt_type="VLAN_UDP")
> tcpdump_out = self.get_tcpdump_package()
> --
> 2.17.0
prev parent reply other threads:[~2019-12-20 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 19:43 Xiaoxiao Zeng
2019-12-11 7:57 ` Peng, ZhihongX
2019-12-13 2:48 ` Ma, LihongX
2019-12-20 7:48 ` Tu, Lijuan [this message]
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=8CE3E05A3F976642AAB0F4675D0AD20E0BB8A0F1@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=xiaoxiaox.zeng@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).