-----Original Message-----
> Date: Fri, 23 Jun 2017 13:07:10 +0000
> From: "Van Haaren, Harry" <harry.van.haa...@intel.com>
> To: Jerin Jacob <jerin.ja...@caviumnetworks.com>, "dev@dpdk.org"
>  <dev@dpdk.org>
> CC: "Richardson, Bruce" <bruce.richard...@intel.com>,
>  "hemant.agra...@nxp.com" <hemant.agra...@nxp.com>, "Eads, Gage"
>  <gage.e...@intel.com>, "nipun.gu...@nxp.com" <nipun.gu...@nxp.com>,
>  "Vangati, Narender" <narender.vang...@intel.com>, "Rao, Nikhil"
>  <nikhil....@intel.com>, "gprathyu...@caviumnetworks.com"
>  <gprathyu...@caviumnetworks.com>
> Subject: RE: [dpdk-dev] [PATCH 06/33] app/testeventdev: define the test
>  options
> 
> > From: Jerin Jacob [mailto:jerin.ja...@caviumnetworks.com]
> > Sent: Sunday, May 28, 2017 8:58 PM
> > To: dev@dpdk.org
> > Cc: Richardson, Bruce <bruce.richard...@intel.com>; Van Haaren, Harry
> > <harry.van.haa...@intel.com>; hemant.agra...@nxp.com; Eads, Gage 
> > <gage.e...@intel.com>;
> > nipun.gu...@nxp.com; Vangati, Narender <narender.vang...@intel.com>; Rao, 
> > Nikhil
> > <nikhil....@intel.com>; gprathyu...@caviumnetworks.com; Jerin Jacob
> > <jerin.ja...@caviumnetworks.com>
> > Subject: [dpdk-dev] [PATCH 06/33] app/testeventdev: define the test options
> > 
> > Define the test options that used across all test cases and
> > fill the default values for the same.
> > 
> > Signed-off-by: Jerin Jacob <jerin.ja...@caviumnetworks.com>
> > Signed-off-by: Guduri Prathyusha <gprathyu...@caviumnetworks.com>
> 
> <snip>
> 
> 
> > +void
> > +evt_options_default(struct evt_options *opt)
> > +{
> > +   memset(opt, 0, sizeof(*opt));
> > +   opt->verbose_level = 1; /* Enable minimal prints */
> > +   opt->dev_id = 0;
> > +   strncpy(opt->test_name, "queue_order", EVT_TEST_NAME_MAX_LEN);
> 
> I think "queue_order" isn't a valid test name, we should probably make the 
> default test to run something that is supported by all PMDs, performance 
> testing of atomic traffic?

Good catch. I will change to "order_queue". It supported on all PMD

> 
> With that resolved,
> 
> Acked-by: Harry van Haaren <harry.van.haa...@intel.com>

Reply via email to