From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Li, WenjieX A" <wenjiex.a.li@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Li, WenjieX A" <wenjiex.a.li@intel.com>
Subject: Re: [dts] [PATCH V3] tests/dynamic_queue: unbind the unused ports
Date: Sat, 22 Dec 2018 01:52:26 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0B9E5A82@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1544769033-29893-1-git-send-email-wenjiex.a.li@intel.com>
Could you clarify why it' s necessary to reduce the ports to only one?
BTW, though you'd like to use only one port, unbind/bind ports is not a good option, prefer to add testpmd parameter "-w self.dut.get_port_pci(self.dut_ports[0])".
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Wenjie Li
> Sent: Friday, December 14, 2018 2:31 PM
> To: dts@dpdk.org
> Cc: Li, WenjieX A <wenjiex.a.li@intel.com>
> Subject: [dts] [PATCH V3] tests/dynamic_queue: unbind the unused ports
>
> Instead of reduce the queue number for fvl_40G, unbind the unused ports for
> all nics during test, and bind them after this test suite is done.
>
> Signed-off-by: Wenjie Li <wenjiex.a.li@intel.com>
> ---
> tests/TestSuite_dynamic_queue.py | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/tests/TestSuite_dynamic_queue.py
> b/tests/TestSuite_dynamic_queue.py
> index f155686..e145f53 100644
> --- a/tests/TestSuite_dynamic_queue.py
> +++ b/tests/TestSuite_dynamic_queue.py
> @@ -25,6 +25,11 @@ class TestDynamicQueue(TestCase):
> tester_port = self.tester.get_local_port(self.used_dut_port)
> self.tester_intf = self.tester.get_interface(tester_port)
> self.dut_testpmd = PmdOutput(self.dut)
> + unbind_nics = []
> + if len(self.dut_ports) >= 2:
> + for i in range (1, len(self.dut_ports)):
> + unbind_nics.append(self.dut_ports[1])
> + self.dut.unbind_interfaces_linux(unbind_nics)
>
> def set_up(self):
> self.dut_testpmd.start_testpmd( @@ -194,4 +199,4 @@ class
> TestDynamicQueue(TestCase):
> self.dut_testpmd.quit()
>
> def tear_down_all(self):
> - pass
> + self.dut.bind_interfaces_linux(driver=self.drivername)
> --
> 2.17.2
prev parent reply other threads:[~2018-12-22 1:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 6:30 Wenjie Li
2018-12-18 5:50 ` Zhu, WenhuiX
2018-12-22 1:52 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0B9E5A82@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=wenjiex.a.li@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).