From: Anupam Kapoor <anupam.kapoor@gmail.com>
To: Chinmaya Dwibedy <ckdwibedy@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Is rte_get_timer_cycles()is same on all cores?
Date: Tue, 15 Nov 2016 12:56:51 +0530 [thread overview]
Message-ID: <CAEXHiZEStV=i6A398E02UyOmQm83r5e+_ysDSpy_AMqLxi5sZw@mail.gmail.com> (raw)
In-Reply-To: <CAMHS8REXbMA-Ra9pHCqdtpmOJwLFt9hf_8TUDpNFkSGXSOMgjQ@mail.gmail.com>
On Tue, Nov 15, 2016 at 12:44 PM, Chinmaya Dwibedy <ckdwibedy@gmail.com>
wrote:
> I think, it is same on all cores. Can
> anyone please correct me if I am wrong?
>
it *should* be same but because of invariant-tsc support in latest intel
machines (see if cpuid gives you "0x80000007/edx" which indicates its
presence)
--
kind regards
anupam
In the beginning was the lambda, and the lambda was with Emacs, and Emacs
was the lambda.
prev parent reply other threads:[~2016-11-15 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 7:14 Chinmaya Dwibedy
2016-11-15 7:26 ` Anupam Kapoor [this message]
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='CAEXHiZEStV=i6A398E02UyOmQm83r5e+_ysDSpy_AMqLxi5sZw@mail.gmail.com' \
--to=anupam.kapoor@gmail.com \
--cc=ckdwibedy@gmail.com \
--cc=users@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).