From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 290B81B704 for ; Tue, 6 Feb 2018 19:03:54 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Feb 2018 10:03:53 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,469,1511856000"; d="scan'208";a="32506439" Received: from irsmsx110.ger.corp.intel.com ([163.33.3.25]) by orsmga002.jf.intel.com with ESMTP; 06 Feb 2018 10:03:53 -0800 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.197]) by irsmsx110.ger.corp.intel.com ([169.254.15.15]) with mapi id 14.03.0319.002; Tue, 6 Feb 2018 18:03:52 +0000 From: "Singh, Jasvinder" To: "longtb5@viettel.com.vn" , "Dumitrescu, Cristian" CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH] examples/ip_pipeline: fix timer_period unit Thread-Index: AQHTmnBRDpB+TzmRFkeUJdFY5yqvqKOXtCwQ Date: Tue, 6 Feb 2018 18:03:51 +0000 Message-ID: <54CBAA185211B4429112C315DA58FF6D332F4B8D@IRSMSX103.ger.corp.intel.com> References: <1517388677-17533-1-git-send-email-longtb5@viettel.com.vn> In-Reply-To: <1517388677-17533-1-git-send-email-longtb5@viettel.com.vn> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiM2M2ZmJkN2EtNTQ1Ny00NDhhLTg1NTYtODE0YWFmMDdjZDVmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6InY4VnNlMkczaFhTZjRKTE56N09zQ09ad0hDUlVhMGczVWJHSzBTbHBWTTQ9In0= x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH] examples/ip_pipeline: fix timer_period unit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Feb 2018 18:03:55 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of > longtb5@viettel.com.vn > Sent: Wednesday, January 31, 2018 8:48 AM > To: Dumitrescu, Cristian > Cc: dev@dpdk.org; longtb5 > Subject: [dpdk-dev] [PATCH] examples/ip_pipeline: fix timer_period unit >=20 > The timer_period option specified by users via config file should have un= it of > 1 millisecond. However timer_period is internally converted to unit of 10 > millisecond. >=20 > Fixes: 4e14069328fc ("examples/ip_pipeline: measure CPU utilization") >=20 > Signed-off-by: Bao-Long Tran > --- > examples/ip_pipeline/init.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) >=20 > diff --git a/examples/ip_pipeline/init.c b/examples/ip_pipeline/init.c in= dex > 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 =3D ptype; >=20 > data->timer_period =3D (rte_get_tsc_hz() * > - params->timer_period) / 100; > + params->timer_period) / 1000; > } > } Reviewed-by: Jasvinder Singh