test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Liu, Yong" <yong.liu@intel.com>
To: "Yao, Lei A" <lei.a.yao@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1] tests: add test for vhost/virtio loopback	performance
Date: Wed, 28 Dec 2016 07:21:21 +0000	[thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E62D34366@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <2DBBFF226F7CF64BAFCA79B681719D953A149C77@shsmsx102.ccr.corp.intel.com>

Thanks, Lei.

> -----Original Message-----
> From: Yao, Lei A
> Sent: Wednesday, December 28, 2016 1:56 PM
> To: Liu, Yong; dts@dpdk.org
> Subject: RE: [dts] [PATCH V1] tests: add test for vhost/virtio loopback
> performance
> 
> Some update. Thanks.
> 
> > -----Original Message-----
> > From: Liu, Yong
> > Sent: Wednesday, December 28, 2016 1:28 PM
> > To: Yao, Lei A <lei.a.yao@intel.com>; dts@dpdk.org
> > Cc: Yao, Lei A <lei.a.yao@intel.com>
> > Subject: RE: [dts] [PATCH V1] tests: add test for vhost/virtio loopback
> > performance
> >
> > Lei, some comments below.
> >
> > > -----Original Message-----
> > > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of lei,yao
> > > Sent: Thursday, December 22, 2016 11:29 AM
> > > To: dts@dpdk.org
> > > Cc: Yao, Lei A
> > > Subject: [dts] [PATCH V1] tests: add test for vhost/virtio loopback
> > > performance
> > >
> > > From: lei yao <lei.a.yao@intel.com>
> > >
> > > +        self.dut.send_expect("killall -s INT vhost-switch", "#")
> > > +        self.dut.send_expect("killall -s INT testpmd", "#")
> >
> > Dpdk application will be automated killed by framework. There's no need
> to
> > kill dpdk application in set_up_all function.
> >
> So both vhost-switch and testpmd will be cleaned by framework, right?
> 

Yes. 

> > > +        self.header_row = ["FrameSize(B)", "Mode", "Throughput(Mpps)",
> > > "Virtio Version"]
> > > +        self.frame_sizes = [64, 128, 260, 520, 1024, 1500]
> > > +        self.test_cycles = {'Mpps': {}, 'pct': {}}
> > > +
> > > +    def set_up(self):
> > > +        """
> > > +        Run before each test case.
> > > +        """
> > > +        self.dut.restore_interfaces()
> > > +        pass
> >
> > This is critical function which will bind all ports to default driver.
> > You can use simple code like "port.bind_driver()" to bind port to
> default
> > driver and "port.bind_driver(driver=self.drivername)" to igb_uio driver.
> > Just in this suite, I can't see any requirement to do this.
> >
> Because this test cases don't need any NIC binned to pmd driver. So I use
> this function
> to clean it.
By now if you do that, all later suites will be failed. I remember that Lijuan is developing one patch for restore all ports before running suite. 
Based on that patch, you can do this function in set_up_all function.
But now I recommend that change drivername to blank and then run this suite.

      reply	other threads:[~2016-12-28  7:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-22  3:29 lei,yao
2016-12-28  5:28 ` Liu, Yong
2016-12-28  5:56   ` Yao, Lei A
2016-12-28  7:21     ` Liu, Yong [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=86228AFD5BCD8E4EBFD2B90117B5E81E62D34366@SHSMSX103.ccr.corp.intel.com \
    --to=yong.liu@intel.com \
    --cc=dts@dpdk.org \
    --cc=lei.a.yao@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).