DPDK patches and discussions
 help / color / mirror / Atom feed
From: longtb5@viettel.com.vn
To: cristian.dumitrescu@intel.com
Cc: dev@dpdk.org, longtb5 <longtb5@viettel.com.vn>
Subject: [dpdk-dev] [PATCH] examples/ip_pipeline: fix timer_period unit
Date: Wed, 31 Jan 2018 15:48:16 +0700 (ICT)	[thread overview]
Message-ID: <1517388677-17533-1-git-send-email-longtb5@viettel.com.vn> (raw)

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 <longtb5@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;

             reply	other threads:[~2018-01-31  8:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31  8:48 longtb5 [this message]
2018-02-06 18:03 ` Singh, Jasvinder
2018-02-06 18:45   ` Thomas Monjalon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1517388677-17533-1-git-send-email-longtb5@viettel.com.vn \
    --to=longtb5@viettel.com.vn \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \


* 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).