From: lingwei <weix.ling@intel.com>
To: dts@dpdk.org
Cc: lingwei <weix.ling@intel.com>
Subject: [dts] [PATCH V2 4/5] tests/vf_single_core_perf:support columbiaville_25gx2 nic
Date: Wed, 25 Nov 2020 22:29:29 +0800 [thread overview]
Message-ID: <20201125142930.77045-5-weix.ling@intel.com> (raw)
In-Reply-To: <20201125142930.77045-1-weix.ling@intel.com>
support columbiaville_25gx2 nic
Signed-off-by: lingwei <weix.ling@intel.com>
---
tests/TestSuite_vf_single_core_perf.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/TestSuite_vf_single_core_perf.py b/tests/TestSuite_vf_single_core_perf.py
index 47550bf8..05974eac 100644
--- a/tests/TestSuite_vf_single_core_perf.py
+++ b/tests/TestSuite_vf_single_core_perf.py
@@ -249,7 +249,7 @@ class TestVfSingleCorePerf(TestCase):
if self.nic in ["fortville_25g", "fortville_spirit"] or thread_num == 2:
param += " --rxq=2 --txq=2"
# columbiaville use one queue per port for best performance.
- elif self.nic in ["columbiaville_100g", "columbiaville_25g"]:
+ elif self.nic in ["columbiaville_100g", "columbiaville_25g", "columbiaville_25gx2"]:
param += " --rxq=1 --txq=1"
# workaround for that testpmd can't forward packets in io forward mode
param += " --port-topology=loop"
--
2.17.1
next prev parent reply other threads:[~2020-11-25 6:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 14:29 [dts] [PATCH V2 0/5] support " lingwei
2020-11-25 6:37 ` Ling, WeiX
2020-11-25 6:49 ` Zhao, HaiyangX
2020-11-25 14:29 ` [dts] [PATCH V2 1/5] conf/vf_l3fwd.cfg:support " lingwei
2020-11-25 14:29 ` [dts] [PATCH V2 2/5] tests/vf_l3fwd_kernelpf:support " lingwei
2020-11-25 14:29 ` [dts] [PATCH V2 3/5] tests/nic_single_core_perf:support " lingwei
2020-11-25 14:29 ` lingwei [this message]
2020-11-25 14:29 ` [dts] [PATCH V2 5/5] tests/l3fwd_base:support columbiaville_25gx2 nic and set-ice-16bytes when build dpdk lingwei
2020-11-26 8:29 ` [dts] [PATCH V2 0/5] support columbiaville_25gx2 nic 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=20201125142930.77045-5-weix.ling@intel.com \
--to=weix.ling@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).