From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Yao, BingX Y" <bingx.y.yao@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Yao, BingX Y" <bingx.y.yao@intel.com>
Subject: Re: [dts] [PATCH V1] tests/pmdrss_hash:forbidden packet
Date: Sun, 24 Mar 2019 18:39:29 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA45C21@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1552878231-39129-1-git-send-email-bingx.y.yao@intel.com>
Hi bing,
Fail to apply due to code base changed by your patch: [dts] [PATCH V2] tests/pmdrss_hash:change hard code
Could you please kindly to rework it?
thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of yaobing
> Sent: Sunday, March 17, 2019 8:04 PM
> To: dts@dpdk.org
> Cc: Yao, BingX Y <bingx.y.yao@intel.com>
> Subject: [dts] [PATCH V1] tests/pmdrss_hash:forbidden packet
>
> There will be some miscellaneous packetss appearing on the receiving port, and
> setting up command "set promisc all off"
> to forbidden packets.
>
> Signed-off-by: yaobing <bingx.y.yao@intel.com>
> ---
> tests/TestSuite_pmdrss_hash.py | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/tests/TestSuite_pmdrss_hash.py b/tests/TestSuite_pmdrss_hash.py
> index 60c9819..2daca36 100644
> --- a/tests/TestSuite_pmdrss_hash.py
> +++ b/tests/TestSuite_pmdrss_hash.py
> @@ -483,6 +483,7 @@ class TestPmdrssHash(TestCase):
> for iptype, rsstype in iptypes.items():
> self.dut.send_expect("set verbose 8", "testpmd> ")
> self.dut.send_expect("set fwd rxonly", "testpmd> ")
> + self.dut.send_expect("set promisc all off", "testpmd> ")
> self.dut.send_expect(
> "set nbcore %d" % (queue + 1), "testpmd> ")
>
> @@ -520,6 +521,7 @@ class TestPmdrssHash(TestCase):
> for iptype, rsstype in iptypes.items():
> self.dut.send_expect("set verbose 8", "testpmd> ")
> self.dut.send_expect("set fwd rxonly", "testpmd> ")
> + self.dut.send_expect("set promisc all off", "testpmd> ")
> self.dut.send_expect(
> "set nbcore %d" % (queue + 1), "testpmd> ")
>
> @@ -565,6 +567,7 @@ class TestPmdrssHash(TestCase):
> self.logger.info("***********************%s rss
> test********************************" % iptype)
> self.dut.send_expect("set verbose 8", "testpmd> ")
> self.dut.send_expect("set fwd rxonly", "testpmd> ")
> + self.dut.send_expect("set promisc all off", "testpmd> ")
> self.dut.send_expect(
> "set nbcore %d" % (queue + 1), "testpmd> ")
>
> @@ -603,6 +606,7 @@ class TestPmdrssHash(TestCase):
> for iptype, rsstype in iptypes.items():
> self.dut.send_expect("set verbose 8", "testpmd> ")
> self.dut.send_expect("set fwd rxonly", "testpmd> ")
> + self.dut.send_expect("set promisc all off", "testpmd> ")
> self.dut.send_expect(
> "set nbcore %d" % (queue + 1), "testpmd> ")
>
> @@ -633,6 +637,7 @@ class TestPmdrssHash(TestCase):
> "NIC Unsupported: " + str(self.nic))
>
> self.dut.send_expect("./%s/app/testpmd -c f -n 4 -- -i" % self.target,
> "testpmd> ", 120)
> + self.dut.send_expect("set promisc all off", "testpmd> ")
> out = self.dut.send_expect("create bonded device 3 0", "testpmd> ", 30)
> bond_device_id = int(re.search("port \d+", out).group().split(" ")[-1].strip())
>
> --
> 2.17.2
prev parent reply other threads:[~2019-03-24 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 3:03 yaobing
2019-03-19 2:57 ` Zhu, WenhuiX
2019-03-24 18:39 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BA45C21@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=bingx.y.yao@intel.com \
--cc=dts@dpdk.org \
/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).