From: "Ma, LihongX" <lihongx.ma@intel.com>
To: "Xie, WeiX" <weix.xie@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Xie, WeiX" <weix.xie@intel.com>
Subject: Re: [dts] [PATCH V1] tests/eventdev_pipeline:modify parameter
Date: Tue, 26 Nov 2019 05:18:37 +0000 [thread overview]
Message-ID: <BE1E572D0441E34284F1F8B7AC28F1970BB291A6@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1574666121-116152-1-git-send-email-weix.xie@intel.com>
Hi, wei
I think we should optimization the dut code instead of change the suite code.
-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Xie Wei
Sent: Monday, November 25, 2019 3:15 PM
To: dts@dpdk.org
Cc: Xie, WeiX <weix.xie@intel.com>
Subject: [dts] [PATCH V1] tests/eventdev_pipeline:modify parameter
modify command parameter
Signed-off-by: Xie Wei <weix.xie@intel.com>
---
tests/TestSuite_eventdev_pipeline.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/TestSuite_eventdev_pipeline.py b/tests/TestSuite_eventdev_pipeline.py
index 1e99389..2fc2ded 100644
--- a/tests/TestSuite_eventdev_pipeline.py
+++ b/tests/TestSuite_eventdev_pipeline.py
@@ -95,7 +95,7 @@ class TestEventdevPipeline(TestCase):
"""
run eventdev_pipeline command
"""
- eal_params = self.dut.create_eal_parameters(cores=self.core_list,
+ eal_params = self.dut.create_eal_parameters(cores=self.self.core_config,
ports=[self.dut.ports_info[0]['pci']])
command_line = "taskset -c %s " + self.app_command + \
"/build/app/eventdev_pipeline %s " + \
--
2.17.2
next prev parent reply other threads:[~2019-11-26 5:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 7:15 Xie Wei
2019-11-25 8:02 ` Mo, YufengX
2019-11-27 9:19 ` Tu, Lijuan
2019-11-26 5:18 ` Ma, LihongX [this message]
2019-11-27 9:18 ` 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=BE1E572D0441E34284F1F8B7AC28F1970BB291A6@SHSMSX101.ccr.corp.intel.com \
--to=lihongx.ma@intel.com \
--cc=dts@dpdk.org \
--cc=weix.xie@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).