All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: kurt.hackel@oracle.com, Ian Pratt <Ian.Pratt@eu.citrix.com>,
	"Xen-Devel (E-mail)" <xen-devel@lists.xensource.com>,
	Tim Deegan <Tim.Deegan@citrix.com>,
	Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [RFC] Correct/fast timestamping in apps under Xen [1	of 4]: Reliable TSC
Date: Fri, 09 Oct 2009 22:55:01 -0700	[thread overview]
Message-ID: <4AD021B5.5070806@goop.org> (raw)
In-Reply-To: <211b66c7-968f-446f-ab3d-5a0b27d67e93@default>

On 10/09/09 19:36, Dan Magenheimer wrote:
> Very nice!
>
> One more measurement if you haven't already torn down
> your test environment:   If you are at xen-unstable tip,
> with tsc emulation on, please try something like:
>
> for i in {0..100}; do
> xm debug-key s; xm dmesg | tail; sleep 1;
> done
>
> to get an idea of the number of rdtsc's being
> done per second (and also divide by the number
> of cores so we have rdtsc's/sec/core).  This is
> of course unloaded, so if you have a favorite
> load to throw on it, that would be very interesting
> also.
>   

The kernel does about between 400k and 1.4M/sec, median around ~600k,
for a git pull (which I think is single-threaded), and about
200k-500k/sec for a kernel compile (-j4 on 2 vcpus).  Usermode is a much
lower rate; around 1000/sec for the kernel compile.

Baseline idle is around 1000/sec kernel, 10/sec user.

Also, my inline naked rdtsc benchmark shows that the emulated rdtsc is
taking around 465ns (vs 30, a 15x slowdown).

    J

  reply	other threads:[~2009-10-10  5:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 17:51 [RFC] Correct/fast timestamping in apps under Xen [1 of 4]: Reliable TSC Dan Magenheimer
2009-10-07 21:07 ` Dan Magenheimer
2009-10-08  6:45   ` Keir Fraser
2009-10-08  6:54     ` Keir Fraser
2009-10-08  9:13   ` Tim Deegan
2009-10-08  9:22     ` Keir Fraser
2009-10-08 16:24       ` Dan Magenheimer
2009-10-09  9:34         ` Tim Deegan
2009-10-09 14:38           ` Dan Magenheimer
2009-10-12  9:51             ` Tim Deegan
2009-10-09 20:28           ` Jeremy Fitzhardinge
2009-10-09 21:35             ` Dan Magenheimer
2009-10-10  0:22               ` Jeremy Fitzhardinge
2009-10-10  2:36                 ` Dan Magenheimer
2009-10-10  5:55                   ` Jeremy Fitzhardinge [this message]
2009-10-10  6:35                     ` Keir Fraser
2009-10-10 14:22                       ` Dan Magenheimer

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=4AD021B5.5070806@goop.org \
    --to=jeremy@goop.org \
    --cc=Ian.Pratt@eu.citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=Tim.Deegan@citrix.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=kurt.hackel@oracle.com \
    --cc=xen-devel@lists.xensource.com \
    /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.