> -----Original Message----- > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of > long...@viettel.com.vn > Sent: Wednesday, January 31, 2018 8:48 AM > To: Dumitrescu, Cristian <cristian.dumitre...@intel.com> > Cc: dev@dpdk.org; longtb5 <long...@viettel.com.vn> > Subject: [dpdk-dev] [PATCH] examples/ip_pipeline: fix timer_period unit > > The timer_period option specified by users via config file should have unit of > 1 millisecond. However timer_period is internally converted to unit of 10 > millisecond. > > Fixes: 4e14069328fc ("examples/ip_pipeline: measure CPU utilization") > > Signed-off-by: Bao-Long Tran <long...@viettel.com.vn> > --- > examples/ip_pipeline/init.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/examples/ip_pipeline/init.c b/examples/ip_pipeline/init.c index > 55d246f..bb07efa 100644 > --- a/examples/ip_pipeline/init.c > +++ b/examples/ip_pipeline/init.c > @@ -1704,7 +1704,7 @@ app_init_pipelines(struct app_params *app) > data->ptype = ptype; > > data->timer_period = (rte_get_tsc_hz() * > - params->timer_period) / 100; > + params->timer_period) / 1000; > } > }
Reviewed-by: Jasvinder Singh <jasvinder.si...@intel.com>