From: george anzinger <george@mvista.com>
To: Chris Ball <chris@void.printf.net>
Cc: dean gaudet <dean-list-linux-kernel@arctic.org>,
Ben Greear <greearb@candelatech.com>,
Davide Libenzi <davidel@xmailserver.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: a faster way to gettimeofday?
Date: Wed, 06 Mar 2002 14:25:02 -0800 [thread overview]
Message-ID: <3C86973E.C029095F@mvista.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0203061238380.17114-100000@twinlark.arctic.org> <87bse14c4h.fsf@lexis.house.pkl.net>
Chris Ball wrote:
>
> >>>>> "dean" == dean gaudet <dean-list-linux-kernel@arctic.org> writes:
>
> dean> ingo started the proper work for this, for example, see:
> dean> <http://people.redhat.com/mingo/vsyscall-patches/vsyscall-2.3.32-F4>
> dean> (there's a documentation file near the bottom of the patch)
> dean> but it doesn't appear to support gettimeofday via rdtsc yet.
>
> Interesting patch; when last I looked, vsyscalls were only being
> implemented on the new 64-bit architectures.
>
> Does this patch break binary compatibility? I seem to recall that being
> Andrea's reason for not running vsyscalls on standard x86 back in August
> last year.
>
In keeping with the subject, the gettimeofday call in this patch does
NOT get the current timeofday, but the time it was last updated, which
is usually every 1/HZ. The REAL gettimeofday adds a converted delta of
the TSC to get the time to NOW with a resolution of 1 micro second.
(Oh, and by the way, it does not update xtime in the process of doing
this.)
As a wonder, just how long is your system taking to do a gettimeofday.
Mine does it in under one micro second (800 MHZ PIII).
-g
> - Chris.
> --
> $a="printf.net"; Chris Ball | chris@void.$a | www.$a | finger: chris@$a
> "In the beginning there was nothing, which exploded."
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
George george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Real time sched: http://sourceforge.net/projects/rtsched/
next prev parent reply other threads:[~2002-03-06 22:26 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
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 [this message]
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=3C86973E.C029095F@mvista.com \
--to=george@mvista.com \
--cc=chris@void.printf.net \
--cc=davidel@xmailserver.org \
--cc=dean-list-linux-kernel@arctic.org \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.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