From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Ma, LihongX" <lihongx.ma@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Peng, Yuan" <yuan.peng@intel.com>, "Ma, LihongX" <lihongx.ma@intel.com>
Subject: Re: [dts] [PATCH V1] tests/rxtx_offload: add -c params when use tcpdump read pcap file
Date: Wed, 12 Jun 2019 06:45:45 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BABA750@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1559775807-12500-1-git-send-email-lihongx.ma@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of lihong
> Sent: Thursday, June 6, 2019 7:03 AM
> To: dts@dpdk.org
> Cc: Peng, Yuan <yuan.peng@intel.com>; Ma, LihongX <lihongx.ma@intel.com>
> Subject: [dts] [PATCH V1] tests/rxtx_offload: add -c params when use
> tcpdump read pcap file
>
> The tcpdump capture all the tx packets from testpmd, read the pcap file will
> use too much time, and it not need to read all the packet in the pcap file.
> Using 1024 packets to verify the tx packets is enough.
>
> Signed-off-by: lihong <lihongx.ma@intel.com>
> ---
> tests/TestSuite_rxtx_offload.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/TestSuite_rxtx_offload.py b/tests/TestSuite_rxtx_offload.py
> index 53f7cf9..0ae83f4 100644
> --- a/tests/TestSuite_rxtx_offload.py
> +++ b/tests/TestSuite_rxtx_offload.py
> @@ -269,7 +269,7 @@ class TestRxTx_Offload(TestCase):
> def get_tcpdump_package(self):
>
> self.tester.send_expect("killall tcpdump", "#")
> - return self.tester.send_expect("tcpdump -nn -e -v -
> r ./getPackageByTcpdump.cap", "#", 120)
> + return self.tester.send_expect("tcpdump -nn -e -v -c 1024 -r
> + ./getPackageByTcpdump.cap", "#", 120)
>
> def test_rxoffload_port(self):
> """
> --
> 2.7.4
prev parent reply other threads:[~2019-06-12 6:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 23:03 lihong
2019-06-06 7:21 ` Zhu, WenhuiX
2019-06-12 6:45 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BABA750@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=lihongx.ma@intel.com \
--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).