From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "thaq@marvell.com" <thaq@marvell.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "fmasood@marvell.com" <fmasood@marvell.com>,
"avijay@marvell.com" <avijay@marvell.com>
Subject: Re: [dts] [PATCH] TestSuite_unit_tests_pmd_perf.py:Added support to match Single socket CPU list using Regular-Expression(Regex)
Date: Tue, 23 Apr 2019 20:40:12 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA659E5@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1555996190-23344-1-git-send-email-thaq@marvell.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of thaq@marvell.com
> Sent: Monday, April 22, 2019 10:10 PM
> To: dts@dpdk.org
> Cc: fmasood@marvell.com; avijay@marvell.com; thaq <thaq@marvell.com>
> Subject: [dts] [PATCH] TestSuite_unit_tests_pmd_perf.py:Added support to
> match Single socket CPU list using Regular-Expression(Regex)
>
> From: thaq <thaq@marvell.com>
>
> Cores listed using "/usertools/cpu_layout.py" scripts is based on the
> socket/cores.
> Currently RE.match "match String expression" matchs only dual socket cpu
> list, Incase case of single socket RE.match "string" fails. So modifyed to
> support both the single/dual sockets cases.
>
> Signed-off-by: thaq <thaq@marvell.com>
> ---
> tests/TestSuite_unit_tests_pmd_perf.py | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tests/TestSuite_unit_tests_pmd_perf.py
> b/tests/TestSuite_unit_tests_pmd_perf.py
> index 6938839..0d332bf 100644
> --- a/tests/TestSuite_unit_tests_pmd_perf.py
> +++ b/tests/TestSuite_unit_tests_pmd_perf.py
> @@ -92,11 +92,12 @@ class TestUnitTestsPmdPerf(TestCase):
>
> out = self.dut.send_expect("./usertools/cpu_layout.py", "#", 10)
> k = re.search("Core 0 (.*)", out)
> - result = re.findall("(\d+),", k.group())
> socket_id = self.dut.ports_info[0]['port'].socket
> if socket_id == 0 or socket_id == -1:
> + result = re.findall("(\d+)", k.group())
> return int(result[0])
> else:
> + result = re.findall("(\d+),", k.group())
> return int(result[1])
>
> def test_pmd_burst(self):
> --
> 1.8.3.1
prev parent reply other threads:[~2019-04-23 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 5:09 thaq
2019-04-23 20:40 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BA659E5@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=avijay@marvell.com \
--cc=dts@dpdk.org \
--cc=fmasood@marvell.com \
--cc=thaq@marvell.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).