From: zhuwenhui <wenhuix.zhu@intel.com>
To: dts@dpdk.org
Cc: zhuwenhui <wenhuix.zhu@intel.com>
Subject: [dts] [PATCH V3] tests/dynamic_queue add more cores for testpmd
Date: Wed, 8 May 2019 13:34:46 +0800 [thread overview]
Message-ID: <1557293686-30708-1-git-send-email-wenhuix.zhu@intel.com> (raw)
When fortville spirit binds multiple ports,
starting testpmd requires more cores.
Signed-off-by: zhuwenhui <wenhuix.zhu@intel.com>
---
tests/TestSuite_dynamic_queue.py | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/tests/TestSuite_dynamic_queue.py b/tests/TestSuite_dynamic_queue.py
index 3aad63f..9cd0073 100644
--- a/tests/TestSuite_dynamic_queue.py
+++ b/tests/TestSuite_dynamic_queue.py
@@ -27,12 +27,12 @@ class TestDynamicQueue(TestCase):
self.dut_testpmd = PmdOutput(self.dut)
def set_up(self):
- # Because of fortville spirit limitation,can't use 2 ports for testing
+ # Fortville_spirit needs more cores to run properly
if (self.nic in ["fortville_spirit"]):
+ self.verify("len(self.dut.cores)>=7", "Less than seven cores can't run testpmd")
self.dut_testpmd.start_testpmd(
- "Default", "--port-topology=chained --txq=%s --rxq=%s"
- % (self.PF_QUEUE, self.PF_QUEUE), eal_param="-w %s"
- % (self.dut.get_port_pci(self.dut_ports[0])))
+ "all", "--port-topology=chained --txq=%s --rxq=%s"
+ % (self.PF_QUEUE, self.PF_QUEUE))
elif (self.nic in ["cavium_a063"]):
eal_opts = ""
for port in self.dut_ports:
--
2.17.2
next reply other threads:[~2019-05-08 5:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 5:34 zhuwenhui [this message]
2019-05-08 5:32 ` Li, WenjieX A
2019-05-08 6:26 ` Yao, BingX Y
2019-05-22 3:31 ` Tu, Lijuan
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=1557293686-30708-1-git-send-email-wenhuix.zhu@intel.com \
--to=wenhuix.zhu@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).