From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: "Richardson,
Bruce" <bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: next releases
Date: Thu, 28 Aug 2014 11:06:07 +0200 [thread overview]
Message-ID: <2353283.PtiVvKdYNr@xps13> (raw)
In-Reply-To: <59AF69C657FD0841A61C55336867B5B0343ECAF0-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-08-28 08:41, Richardson, Bruce:
> As for rte_rdtsc_precise, I'm not sure about its origins, but I'm
> surprised to see that it does not correspond to the rdtscp instruction.
> Can anyone else comment on this one? I would assume it's designed
> to be used to get more accurate measurements of smaller blocks of
> code that we want to benchmark, since rdtsc works best when timing
> larger blocks (in terms of cycle counts, that is, not source lines :-) ).
The good thing with git history (and well written commit logs) is that
we can easily get such answer:
http://dpdk.org/browse/dpdk/commit/?id=3314648f83c3dc06d7d9a
Bruce, do you know how rdtscp is supported across Intel processors?
--
Thomas
next prev parent reply other threads:[~2014-08-28 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 17:15 next releases Thomas Monjalon
2014-08-27 17:04 ` Cyril Chemparathy
[not found] ` <53FE0FA5.8020900-kv+TWInifGbQT0dZR+AlfA@public.gmane.org>
2014-08-28 8:41 ` Richardson, Bruce
[not found] ` <59AF69C657FD0841A61C55336867B5B0343ECAF0-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-08-28 9:06 ` Thomas Monjalon [this message]
2014-08-28 9:22 ` Richardson, Bruce
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=2353283.PtiVvKdYNr@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=bruce.richardson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.