From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Zhao, MeijuanX" <meijuanx.zhao@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhao, MeijuanX" <meijuanx.zhao@intel.com>
Subject: Re: [dts] [next][PATCH V1] tests/fm10k_perf fix syntax error
Date: Wed, 26 Jun 2019 09:11:33 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BAC5512@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20190610172642.20512-1-meijuanx.zhao@intel.com>
Applied into master branch
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhaomeijuan
> Sent: Tuesday, June 11, 2019 1:27 AM
> To: dts@dpdk.org
> Cc: Zhao, MeijuanX <meijuanx.zhao@intel.com>
> Subject: [dts] [next][PATCH V1] tests/fm10k_perf fix syntax error
>
> Signed-off-by: zhaomeijuan <meijuanx.zhao@intel.com>
> ---
> tests/TestSuite_fm10k_perf.py | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/tests/TestSuite_fm10k_perf.py b/tests/TestSuite_fm10k_perf.py
> index b18d0d5..a991ee9 100644
> --- a/tests/TestSuite_fm10k_perf.py
> +++ b/tests/TestSuite_fm10k_perf.py
> @@ -136,6 +136,7 @@ class TestFM10kL3fwd(TestCase):
> self.dut.build_install_dpdk(self.target)
>
> self.l3fwd_test_results = {'header': [],
> + 'data': []}
>
> self.rebuild_l3fwd()
>
> @@ -500,9 +501,10 @@ class TestFM10kL3fwd(TestCase):
>
> subtitle.append(cores)
> cmdline = rtCmdLines[cores] % (TestFM10kL3fwd.path +
> "l3fwd_" + mode, coreMask[cores],
> +
> + self.dut.get_memory_channels(), utils.create_mask(valports[:2]))
>
> if frame_size > 1518:
> - cmdline = cmdline + "--max-pkt-len %d" % frame_size
> + cmdline = cmdline + " --max-pkt-len %d" %
> + frame_size
> self.rst_report(cmdline + "\n", frame=True, annex=True)
>
> out = self.dut.send_expect(cmdline, "L3FWD:", 120)
> --
> 2.17.1
prev parent reply other threads:[~2019-06-26 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 17:26 zhaomeijuan
2019-06-26 9:11 ` Tu, Lijuan [this message]
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=8CE3E05A3F976642AAB0F4675D0AD20E0BAC5512@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=meijuanx.zhao@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).