test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Ma, LihongX" <lihongx.ma@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1] tests/perf_virtio_user_pvp: modify code to support py3
Date: Thu, 20 Feb 2020 06:18:10 +0000	[thread overview]
Message-ID: <ee5e9e3fc8c84344ba271b457c76547a@intel.com> (raw)
In-Reply-To: <1582152444-13314-1-git-send-email-lihongx.ma@intel.com>

Tested-by: ma,lhong<lihongx.ma@intel.com>

-----Original Message-----
From: Ma, LihongX 
Sent: Thursday, February 20, 2020 6:47 AM
To: dts@dpdk.org
Cc: Ma, LihongX <lihongx.ma@intel.com>
Subject: [dts][PATCH V1] tests/perf_virtio_user_pvp: modify code to support py3

Signed-off-by: lihong <lihongx.ma@intel.com>
---
 tests/TestSuite_perf_virtio_user_pvp.py | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/tests/TestSuite_perf_virtio_user_pvp.py b/tests/TestSuite_perf_virtio_user_pvp.py
index 91e21dc..d49bd19 100644
--- a/tests/TestSuite_perf_virtio_user_pvp.py
+++ b/tests/TestSuite_perf_virtio_user_pvp.py
@@ -71,6 +71,7 @@ class TestVirtioSingleCorePerf(TestCase):
         set_up_all in debug mode.
         """
 
+        self.dut.send_expect('rm vhost-net*', '# ')
         # test parameters include: frames size, descriptor numbers
         self.test_parameters = self.get_suite_cfg()['test_parameters']
 
@@ -201,7 +202,7 @@ class TestVirtioSingleCorePerf(TestCase):
             self.dut_ports[0])
         tx_port = self.tester.get_local_port(
             self.dut_ports[0])
-        for port in xrange(2):
+        for port in range(2):
             destination_mac = self.dut.get_mac_address(
                 self.dut_ports[(port) % self.number_of_ports])
             pkt = Packet(pkt_type='IP_RAW', pkt_len=frame_size) @@ -235,7 +236,7 @@ class TestVirtioSingleCorePerf(TestCase):
             eal_params = self.dut.create_eal_parameters(cores=self.core_list_host,
                             ports=[0], prefix='vhost')
         command_line_client = self.target + "/app/testpmd %s " + \
-                        "--socket-mem 1024,1024 --legacy-mem "  \
+                        "--socket-mem 1024,1024 "  \
                         "--vdev 'net_vhost0,iface=vhost-net,queues=1' " + \
                         "-- -i --nb-cores=%d  --txd=%d --rxd=%d"
         command_line_client = command_line_client % (eal_params, len(self.core_list_host)-1,
--
2.7.4


  reply	other threads:[~2020-02-20  6:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19 22:47 lihong
2020-02-20  6:18 ` Ma, LihongX [this message]
2020-02-21  2:03 ` 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=ee5e9e3fc8c84344ba271b457c76547a@intel.com \
    --to=lihongx.ma@intel.com \
    --cc=dts@dpdk.org \
    /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).