From: Haiyang Zhao <haiyangx.zhao@intel.com>
To: dts@dpdk.org, lijuan.tu@intel.com
Cc: Haiyang Zhao <haiyangx.zhao@intel.com>
Subject: [dts] [PATCH V1 2/2] framework/dut: optmize code when setting eal param for rx mode
Date: Wed, 18 Nov 2020 14:01:14 +0800 [thread overview]
Message-ID: <20201118060114.14553-3-haiyangx.zhao@intel.com> (raw)
In-Reply-To: <20201118060114.14553-1-haiyangx.zhao@intel.com>
Dynamically adding rx mode eal parameter is only supported with meson
build, so add a jugement to fix the potential bug.
Signed-off-by: Haiyang Zhao <haiyangx.zhao@intel.com>
---
framework/dut.py | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/framework/dut.py b/framework/dut.py
index d6862e8..2863848 100644
--- a/framework/dut.py
+++ b/framework/dut.py
@@ -230,7 +230,9 @@ class Dut(Crb):
if use_shared_lib == 'true' and shared_lib_path and 'Virt' not in str(self):
eal_str = eal_str + ' -d {} '.format(shared_lib_path)
rx_mode = settings.load_global_setting(settings.DPDK_RXMODE_SETTING)
- if 'other_eal_param' not in config or 'force-max-simd-bitwidth' not in config['other_eal_param']:
+ build_type = settings.load_global_setting(settings.HOST_BUILD_TYPE_SETTING)
+ if build_type == 'meson' and ('other_eal_param' not in config or
+ 'force-max-simd-bitwidth' not in config['other_eal_param']):
if rx_mode == 'novector':
eal_str = eal_str + ' --force-max-simd-bitwidth=64 '
elif rx_mode == 'sse':
--
2.17.1
next prev parent reply other threads:[~2020-11-18 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 6:01 [dts] [PATCH V1 0/2] framework: fix meson compile failed when set " Haiyang Zhao
2020-11-18 6:01 ` [dts] [PATCH V1 1/2] framework/project_dpdk: " Haiyang Zhao
2020-11-18 6:01 ` Haiyang Zhao [this message]
2020-11-18 7:10 ` [dts] [PATCH V1 0/2] framework: " Zhao, HaiyangX
2020-11-19 8:39 ` 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=20201118060114.14553-3-haiyangx.zhao@intel.com \
--to=haiyangx.zhao@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@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).