mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Terje Eggestad <terje.eggestad@scali.com>,
	Ben Greear <greearb@candelatech.com>,
	Davide Libenzi <davidel@xmailserver.org>
Subject: Re: a faster way to gettimeofday? rdtsc strangeness
Date: Fri, 8 Mar 2002 01:57:01 +0000	[thread overview]
Message-ID: <20020308015701.C14779@kushida.apsleyroad.org> (raw)
In-Reply-To: <E16iz57-0002SW-00@the-village.bc.nu> <1015515815.4373.61.camel@pc-16.office.scali.no> <a68bo4$b18$1@cesium.transmeta.com> <20020308013222.B14779@kushida.apsleyroad.org> <3C88157E.5010106@zytor.com>
In-Reply-To: <3C88157E.5010106@zytor.com>; from hpa@zytor.com on Thu, Mar 07, 2002 at 05:35:58PM -0800

H. Peter Anvin wrote:
> I would like to see the error bars on your measurement.

I just ran it on my laptop 20 times in a row and it printed exactly the
same values every time:

	Kernel reports clock frequency:  366.601 MHz
	Measured clock frequency:        366.584 MHz

Well we need more precision than that.  So here goes:

	Kernel reports clock frequency:  366.601000 MHz

	Measured clock frequency:        366.584116 MHz
	Measured clock frequency:        366.584071 MHz
	Measured clock frequency:        366.584108 MHz
	Measured clock frequency:        366.584116 MHz
	Measured clock frequency:        366.584090 MHz
	Measured clock frequency:        366.583968 MHz
	Measured clock frequency:        366.584069 MHz
	Measured clock frequency:        366.584106 MHz
	Measured clock frequency:        366.584172 MHz
	Measured clock frequency:        366.584093 MHz
	Measured clock frequency:        366.584077 MHz
	Measured clock frequency:        366.583939 MHz
	Measured clock frequency:        366.584083 MHz
	Measured clock frequency:        366.584118 MHz
	Measured clock frequency:        366.584062 MHz
	Measured clock frequency:        366.584085 MHz
	Measured clock frequency:        366.584066 MHz
	Measured clock frequency:        366.610417 MHz <- anomaly :-)
	Measured clock frequency:        366.584109 MHz
	Measured clock frequency:        366.584062 MHz
	Measured clock frequency:        366.582293 MHz
	Measured clock frequency:        366.584103 MHz
	Measured clock frequency:        366.584093 MHz
	Measured clock frequency:        366.584107 MHz
	Measured clock frequency:        366.584059 MHz
	Measured clock frequency:        366.583985 MHz
	Measured clock frequency:        366.584133 MHz
	Measured clock frequency:        366.584092 MHz
	Measured clock frequency:        366.584087 MHz
	Measured clock frequency:        366.555754 MHz <- another deviant!
	Measured clock frequency:        366.584044 MHz
	Measured clock frequency:        366.584109 MHz
	Measured clock frequency:        366.584084 MHz
	Measured clock frequency:        366.583608 MHz
	Measured clock frequency:        366.584112 MHz
	Measured clock frequency:        366.584134 MHz
	Measured clock frequency:        366.584049 MHz
	Measured clock frequency:        366.584090 MHz
	Measured clock frequency:        366.584155 MHz
	Measured clock frequency:        366.584006 MHz
	Measured clock frequency:        366.584182 MHz
	Measured clock frequency:        366.584009 MHz

It takes the median of 1000 samples of the TSC time taken to do a
rdtsc/gettimeofday/rdtsc measurement, then uses that as the threshold
for deciding which of the subsequent 1000000 measurements are accepted.
Then linear regression through the accepted points.

I see a couple of results there which suggests a probable fault in the
filtering algorithm.  Perhaps it should simply use the smallest TSC time
taken as the threshold.

Sorry, I'd need permission to post the code.

enjoy,
-- Jamie

  reply	other threads:[~2002-03-08  1:57 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-06  3:41 a faster way to gettimeofday? Ben Greear
2002-03-06  3:58 ` Davide Libenzi
2002-03-06  4:20   ` Ben Greear
2002-03-06  4:31     ` Davide Libenzi
2002-03-06  4:34       ` Davide Libenzi
2002-03-07 14:14       ` a faster way to gettimeofday? rdtsc strangeness Terje Eggestad
2002-03-07 14:41         ` Alan Cox
2002-03-07 15:43           ` Terje Eggestad
2002-03-07 16:17             ` Alan Cox
2002-03-07 18:32             ` H. Peter Anvin
2002-03-08  1:32               ` Jamie Lokier
2002-03-08  1:35                 ` H. Peter Anvin
2002-03-08  1:57                   ` Jamie Lokier [this message]
2002-03-08 18:30                     ` gettimeofday() system call timing curiosity Jamie Lokier
2002-03-08 18:50                       ` H. Peter Anvin
2002-03-08 20:16                         ` Jamie Lokier
2002-03-08 20:30                           ` Davide Libenzi
2002-03-08 18:54                       ` Richard B. Johnson
2002-03-08 19:06                         ` johan.adolfsson
2002-03-08 19:16                           ` H. Peter Anvin
2002-03-08 19:45                           ` Richard B. Johnson
2002-03-08 20:29                             ` johan.adolfsson
2002-03-08 20:43                             ` Alan Cox
2002-03-09  3:03                               ` pjd
2002-03-09 18:51                                 ` Alan Cox
2002-03-09  3:15                             ` Kelsey Hudson
2002-03-08 19:19                         ` Alan Cox
2002-03-08 20:40                         ` george anzinger
2002-03-06 20:45     ` a faster way to gettimeofday? dean gaudet
2002-03-06 21:31       ` Chris Ball
2002-03-06 22:25         ` george anzinger
2002-03-07  0:04         ` vsyscalls Mark Mielke
2002-03-06 16:16 ` a faster way to gettimeofday? Chris Friesen
2002-03-06 16:54   ` Richard B. Johnson
2002-03-11 22:47 ` OBATA Noboru
2002-03-12 13:06   ` Jamie Lokier
2002-03-12 15:12     ` OBATA Noboru

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=20020308015701.C14779@kushida.apsleyroad.org \
    --to=lk@tantalophile.demon.co.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davidel@xmailserver.org \
    --cc=greearb@candelatech.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=terje.eggestad@scali.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®