From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Zhu, ShuaiX" <shuaix.zhu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Wang, Yinan" <yinan.wang@intel.com>,
"Zhu, ShuaiX" <shuaix.zhu@intel.com>
Subject: Re: [dts] [PATCH V1] tests/virtio_event_idx_interrupt:add create_eal_parameters function.
Date: Tue, 3 Mar 2020 05:24:46 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BBE8E53@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1582623151-18473-2-git-send-email-shuaix.zhu@intel.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhu,shuai
> Sent: Tuesday, February 25, 2020 5:32 PM
> To: dts@dpdk.org
> Cc: Wang, Yinan <yinan.wang@intel.com>; Zhu, ShuaiX
> <shuaix.zhu@intel.com>
> Subject: [dts] [PATCH V1] tests/virtio_event_idx_interrupt:add
> create_eal_parameters function.
>
>
>
> Signed-off-by: zhu,shuai <shuaix.zhu@intel.com>
> ---
> tests/TestSuite_virtio_event_idx_interrupt.py | 13 +++++--------
> 1 file changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/tests/TestSuite_virtio_event_idx_interrupt.py
> b/tests/TestSuite_virtio_event_idx_interrupt.py
> index 022cb6d..1fb0622 100644
> --- a/tests/TestSuite_virtio_event_idx_interrupt.py
> +++ b/tests/TestSuite_virtio_event_idx_interrupt.py
> @@ -57,7 +57,6 @@ class TestVirtioIdxInterrupt(TestCase):
> self.ports_socket = self.dut.get_numa_id(self.dut_ports[0])
> self.cores_num = len([n for n in self.dut.cores if int(n['socket'])
> == self.ports_socket])
> - self.mem_channels = self.dut.get_memory_channels()
> self.dst_mac = self.dut.get_mac_address(self.dut_ports[0])
> self.base_dir = self.dut.base_dir.replace('~', '/root')
> self.pf_pci = self.dut.ports_info[0]['pci'] @@ -86,7 +85,6 @@ class
> TestVirtioIdxInterrupt(TestCase):
> "There has not enough cores to test this case %s" %
> self.running_case)
> self.core_list = self.dut.get_core_list(self.core_config)
> - self.core_mask = utils.create_mask(self.core_list)
>
> def start_vhost_testpmd(self):
> """
> @@ -94,12 +92,11 @@ class TestVirtioIdxInterrupt(TestCase):
> """
> # get the core mask depend on the nb_cores number
> self.get_core_mask()
> - command_line = self.dut.target + "/app/testpmd -c %s -n %d -w %s " + \
> - "--socket-mem 2048,2048 --legacy-mem --file-prefix=vhost " + \
> - "--vdev 'net_vhost,iface=%s/vhost-net,queues=%d' -- -i " + \
> - "--nb-cores=%d --txd=1024 --rxd=1024 --rxq=%d --txq=%d"
> - command_line = command_line % (self.core_mask, self.mem_channels,
> self.pf_pci,
> - self.base_dir, self.queues, self.nb_cores, self.queues,
> self.queues)
> + testcmd = self.dut.target + "/app/testpmd "
> + vdev = [r"--vdev 'net_vhost,iface=%s/vhost-net,queues=%d' -- -i " %
> (self.base_dir, self.queues)]
> + eal_params = self.dut.create_eal_parameters(cores=self.core_list,
> prefix='vhost', ports=[self.pf_pci], vdevs=vdev)
> + para = " --nb-cores=%d --txd=1024 --rxd=1024 --rxq=%d --txq=%d" %
> (self.nb_cores, self.queues, self.queues)
> + command_line = testcmd + eal_params + para
> self.vhost.send_expect(command_line, "testpmd> ", 30)
> self.vhost.send_expect("start", "testpmd> ", 30)
>
> --
> 2.17.2
next prev parent reply other threads:[~2020-03-03 5:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 9:32 [dts] [PATCH V1] tests/vdev_primary_secondary:add " zhu,shuai
2020-02-25 9:32 ` [dts] [PATCH V1] tests/virtio_event_idx_interrupt:add " zhu,shuai
2020-02-27 9:50 ` Zhu, ShuaiX
2020-03-03 5:24 ` Tu, Lijuan [this message]
2020-02-25 9:32 ` [dts] [PATCH V1] tests/virtio_user_as_exceptional_path:add " zhu,shuai
2020-02-25 9:32 ` [dts] [PATCH V1] tests/vm2vm_virtio_net_perf:add " zhu,shuai
2020-02-27 9:49 ` Zhu, ShuaiX
2020-03-03 5:24 ` Tu, Lijuan
2020-02-25 9:32 ` [dts] [PATCH V1] tests/vm2vm_virtio_pmd:add " zhu,shuai
2020-02-25 9:32 ` [dts] [PATCH V1] tests/vm2vm_virtio_user:add " zhu,shuai
2020-02-27 9:49 ` [dts] [PATCH V1] tests/vdev_primary_secondary:add " Zhu, ShuaiX
2020-03-03 5:24 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BBE8E53@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=shuaix.zhu@intel.com \
--cc=yinan.wang@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).