From: "han,yingya" <yingyax.han@intel.com>
To: dts@dpdk.org
Cc: "han,yingya" <yingyax.han@intel.com>
Subject: [dts] [PATCH V1]tests/runtime_queue_number: fix the issue ofcreating VF on eagle in two ports
Date: Fri, 2 Nov 2018 15:57:18 +0800 [thread overview]
Message-ID: <1541145438-21684-1-git-send-email-yingyax.han@intel.com> (raw)
FVL_eagle nic has two specifications, namely 2*10G and 4*10G.
Signed-off-by: han,yingya <yingyax.han@intel.com>
---
tests/TestSuite_runtime_queue_number.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/TestSuite_runtime_queue_number.py b/tests/TestSuite_runtime_queue_number.py
index 12263f3..4a51fa2 100644
--- a/tests/TestSuite_runtime_queue_number.py
+++ b/tests/TestSuite_runtime_queue_number.py
@@ -251,12 +251,12 @@ class TestRuntime_Queue_Number(TestCase):
"""
set max queue number when setting max VFs on 1 PF port.
"""
- if (self.nic in ["fortville_eagle", "fortpark_TLV"]):
+ if (self.nic in ["fortville_eagle", "fortpark_TLV"]) and len(self.dut_ports) > 2:
self.setup_env(32)
# failed to set VF max queue num to 16.
out = self.pmdout.start_testpmd("%s" % self.cores, eal_param="-w %s,queue-num-per-vf=16 --file-prefix=test1 --socket-mem 1024,1024" % self.pf_pci)
self.verify("exceeds the hardware maximum 384" in out, "the queue num exceeds the hardware maximum 384")
- elif (self.nic in ["fortville_spirit", "fortville_spirit_single"]):
+ elif (self.nic in ["fortville_spirit", "fortville_spirit_single", "fortville_eagle"]):
self.setup_env(64)
# failed to set VF max queue num to 16.
out = self.pmdout.start_testpmd("%s" % self.cores, eal_param="-w %s,queue-num-per-vf=16 --file-prefix=test1 --socket-mem 1024,1024" % self.pf_pci)
--
2.17.2
next reply other threads:[~2018-11-02 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 7:57 han,yingya [this message]
2018-11-05 1:34 ` Tu, Lijuan
2018-11-05 2:40 ` Han, YingyaX
2018-11-05 5:11 ` 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=1541145438-21684-1-git-send-email-yingyax.han@intel.com \
--to=yingyax.han@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).