From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "nareddy@marvell.com" <nareddy@marvell.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "fmasood@marvell.com" <fmasood@marvell.com>,
"avijay@marvell.com" <avijay@marvell.com>
Subject: Re: [dts] [PATCH] TestSuite_vlan_ethertype_config.py: Added support for vector mode.
Date: Sat, 12 Oct 2019 06:11:00 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB3EC9C@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1570776728-8077-1-git-send-email-nareddy@marvell.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of
> nareddy@marvell.com
> Sent: Friday, October 11, 2019 2:52 PM
> To: dts@dpdk.org
> Cc: fmasood@marvell.com; avijay@marvell.com; Praneeth Reddy
> <nareddy@marvell.com>
> Subject: [dts] [PATCH] TestSuite_vlan_ethertype_config.py: Added support
> for vector mode.
>
> From: Praneeth Reddy <nareddy@marvell.com>
>
> Vector mode need 4 packets to forward, modified to send 4 packets from
> scapy
>
> Signed-off-by: Praneeth Reddy <nareddy@marvell.com>
> ---
> tests/TestSuite_vlan_ethertype_config.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/TestSuite_vlan_ethertype_config.py
> b/tests/TestSuite_vlan_ethertype_config.py
> index 3269b57..33e9948 100644
> --- a/tests/TestSuite_vlan_ethertype_config.py
> +++ b/tests/TestSuite_vlan_ethertype_config.py
> @@ -146,7 +146,7 @@ class TestVlanEthertypeConfig(TestCase):
>
> self.tester.scapy_foreground()
> self.tester.scapy_append("pkt=rdpcap('%s')" % self.tpid_new_file)
> - self.tester.scapy_append("sendp(pkt, iface='%s')" % self.txItf)
> + self.tester.scapy_append("sendp(pkt, iface='%s', count=4)" % self.txItf)
> self.tester.scapy_execute()
>
> def check_vlan_packets(self, vlan, tpid, rxItf, result=True):
> --
> 1.8.3.1
prev parent reply other threads:[~2019-10-12 6:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 6:52 nareddy
2019-10-12 6:11 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BB3EC9C@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=avijay@marvell.com \
--cc=dts@dpdk.org \
--cc=fmasood@marvell.com \
--cc=nareddy@marvell.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).