From patchwork Wed Jan 31 08:48:16 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: longtb5@viettel.com.vn X-Patchwork-Id: 34750 X-Patchwork-Delegate: thomas@monjalon.net Return-Path: X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8D7821B72C; Wed, 31 Jan 2018 09:48:34 +0100 (CET) Received: from mailfilter02.viettel.com.vn (mailfilter02.viettel.com.vn [125.235.240.54]) by dpdk.org (Postfix) with ESMTP id 085C81B6EC for ; Wed, 31 Jan 2018 09:48:25 +0100 (CET) X-IronPort-AV: E=Sophos;i="5.46,438,1511802000"; d="scan'208";a="73620501" Received: from 125.235.240.44.adsl.viettel.vn (HELO mta1.viettel.com.vn) ([125.235.240.44]) by mailfilter02.viettel.com.vn with ESMTP; 31 Jan 2018 15:48:21 +0700 Received: from localhost (localhost [127.0.0.1]) by mta1.viettel.com.vn (Postfix) with ESMTP id 90609640D4D; Wed, 31 Jan 2018 15:48:16 +0700 (ICT) Received: from mta1.viettel.com.vn ([127.0.0.1]) by localhost (mta1.viettel.com.vn [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id d5A1dhezvpPC; Wed, 31 Jan 2018 15:48:16 +0700 (ICT) Received: from localhost (localhost [127.0.0.1]) by mta1.viettel.com.vn (Postfix) with ESMTP id 6A3BE61E9B7; Wed, 31 Jan 2018 15:48:16 +0700 (ICT) X-Virus-Scanned: amavisd-new at Received: from mta1.viettel.com.vn ([127.0.0.1]) by localhost (mta1.viettel.com.vn [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id lABl3A4V4xRN; Wed, 31 Jan 2018 15:48:16 +0700 (ICT) Received: from localhost.localdomain (unknown [27.68.241.28]) by mta1.viettel.com.vn (Postfix) with ESMTPSA id 3EFC7640C07; Wed, 31 Jan 2018 15:48:16 +0700 (ICT) To: cristian.dumitrescu@intel.com Cc: dev@dpdk.org, longtb5 Message-Id: <1517388677-17533-1-git-send-email-longtb5@viettel.com.vn> X-Mailer: git-send-email 2.7.4 MilterAction: FORWARD Date: Wed, 31 Jan 2018 15:48:16 +0700 (ICT) From: longtb5@viettel.com.vn Subject: [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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 Reviewed-by: Jasvinder Singh --- 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; } }