From: "David Engraf" <engraf.david@netcom-sicherheitstechnik.de>
To: "'Bernd Petrovitsch'" <bernd@firmix.at>
Cc: <linux-kernel@vger.kernel.org>, "'Andrew Morton'" <akpm@osdl.org>
Subject: Re: [PATCH] Win32 equivalent to GetTickCount systemcall (i386)
Date: Tue, 6 Dec 2005 13:26:43 +0100 [thread overview]
Message-ID: <000201c5fa60$52bb53e0$0a016696@EW10> (raw)
In-Reply-To: <1133871202.3664.34.camel@tara.firmix.at>
> On Tue, 2005-12-06 at 12:23 +0100, David Engraf wrote:
> > > On Tue, 2005-12-06 at 11:36 +0100, David Engraf wrote:
> [.../9
> > > 3) wouldn't it be better to expose a wallclock time thing which
> > > has a constant unit of time between all kernels?
> >
> > What is it?
> >
> >
> > > (and.. wait.. isn't that called gettimeofday() )
> > Not really gettimeofday is based on the date and time, but what if the
> user
> > changes the date, the counter would also change.
>
> man 2 times
> And use the returned value.
>
> Bernd
> --
> Firmix Software GmbH http://www.firmix.at/
> mobil: +43 664 4416156 fax: +43 1 7890849-55
> Embedded Linux Development and Services
times has only 10ms resolution, we need at least 1ms.
David
____________
Virus checked by G DATA AntiVirusKit
Version: AVK 16.2039 from 06.12.2005
Virus news: www.antiviruslab.com
next prev parent reply other threads:[~2005-12-06 12:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 10:36 [PATCH] Win32 equivalent to GetTickCount systemcall (i386) David Engraf
2005-12-06 10:44 ` Arjan van de Ven
2005-12-06 11:23 ` David Engraf
2005-12-06 11:29 ` Ingo Molnar
2005-12-06 12:06 ` David Engraf
2005-12-06 11:35 ` Arjan van de Ven
2005-12-06 11:37 ` Jakub Jelinek
2005-12-06 12:13 ` Bernd Petrovitsch
2005-12-06 12:26 ` David Engraf [this message]
2005-12-06 19:48 ` Andi Kleen
2005-12-06 18:00 ` Eric Dumazet
2005-12-06 18:01 ` Andi Kleen
2005-12-06 19:47 ` Andi Kleen
2005-12-06 15:25 ` AW: " David Engraf
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='000201c5fa60$52bb53e0$0a016696@EW10' \
--to=engraf.david@netcom-sicherheitstechnik.de \
--cc=akpm@osdl.org \
--cc=bernd@firmix.at \
--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 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.