From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Xiao, QimaiX" <qimaix.xiao@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Xiao, QimaiX" <qimaix.xiao@intel.com>
Subject: Re: [dts] [PATCH V1]perf_vm2vm_virtio_net_perf: use same socket cores with nic port numa id
Date: Wed, 1 Jul 2020 06:06:16 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC68088@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1592900828-288902-1-git-send-email-qimaix.xiao@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Xiao Qimai
> Sent: 2020年6月23日 16:27
> To: dts@dpdk.org
> Cc: Xiao, QimaiX <qimaix.xiao@intel.com>
> Subject: [dts] [PATCH V1]perf_vm2vm_virtio_net_perf: use same socket cores
> with nic port numa id
>
> Signed-off-by: Xiao Qimai <qimaix.xiao@intel.com>
> ---
> tests/TestSuite_perf_vm2vm_virtio_net_perf.py | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/tests/TestSuite_perf_vm2vm_virtio_net_perf.py
> b/tests/TestSuite_perf_vm2vm_virtio_net_perf.py
> index 532cdf7..bc9cb3a 100644
> --- a/tests/TestSuite_perf_vm2vm_virtio_net_perf.py
> +++ b/tests/TestSuite_perf_vm2vm_virtio_net_perf.py
> @@ -54,8 +54,11 @@ from copy import deepcopy
>
> class TestPerfVM2VMVirtioNetPerf(TestCase):
> def set_up_all(self):
> - core_config = "1S/4C/1T"
> - self.cores_list = self.dut.get_core_list(core_config)
> + self.dut_ports = self.dut.get_ports()
> + self.verify(len(self.dut_ports) >= 1, "Insufficient ports for testing")
> + # get core mask
> + self.ports_socket = self.dut.get_numa_id(self.dut_ports[0])
> + self.cores_list = self.dut.get_core_list('all', socket=self.ports_socket)
> self.verify(len(self.cores_list) >= 4,
> "There has not enough cores to test this suite %s" %
> self.suite_name)
> --
> 1.8.3.1
prev parent reply other threads:[~2020-07-01 6:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 8:27 Xiao Qimai
2020-06-23 8:36 ` Xiao, QimaiX
2020-07-01 6:06 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BC68088@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=qimaix.xiao@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).