From: Matthew Hall <mhall@mhcomputing.net>
To: Ravi Kumar Iyer <Ravi.Iyer@aricent.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] cost of reading tsc register
Date: Mon, 20 Apr 2015 09:21:41 -0700 [thread overview]
Message-ID: <20150420162141.GB20826@mhcomputing.net> (raw)
In-Reply-To: <115e8a38d223487488d22a99f53cc926@GURMBXV03.AD.ARICENT.COM>
On Mon, Apr 20, 2015 at 02:37:53PM +0000, Ravi Kumar Iyer wrote:
> We were doing some code optimizations , running DPDK based applications, and chanced upon the rte_rdtsc function [ to read tsc timestamp register value ] consuming cpu cycles of the order of 100clock cycles with a delta of upto 40cycles at times [ 60-140 cycles]
>
> We are actually building up a cpu intensive application which is also very clock cycle sensitive and this is impacting our implementation.
>
> To validate the same using a small/vanilla application we wrote a small code and tested on a single core.
> Has anyone else faced a similar issue or are we doing something really atrocious here.
What happened when you tried rte_rdtsc_precise ?
Matthew.
next prev parent reply other threads:[~2015-04-20 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 14:37 Ravi Kumar Iyer
2015-04-20 15:37 ` Stephen Hemminger
2015-04-20 16:21 ` Matthew Hall [this message]
2015-04-22 7:53 ` Pawel Wodkowski
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150420162141.GB20826@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=Ravi.Iyer@aricent.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).