mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: David Engraf <engraf.david@netcom-sicherheitstechnik.de>
Cc: linux-kernel@vger.kernel.org, "'Andrew Morton'" <akpm@osdl.org>
Subject: Re: [PATCH] Win32 equivalent to GetTickCount systemcall (i386)
Date: Tue, 06 Dec 2005 11:44:39 +0100	[thread overview]
Message-ID: <1133865880.2858.42.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <009201c5fa50$f3f58a10$0a016696@EW10>

On Tue, 2005-12-06 at 11:36 +0100, David Engraf wrote:
> This patch adds a new systemcall on i386 architectures returning the jiffies
> value to the application. 
> As a kernel developer you can use jiffies but from the user space there is
> no equivalent function which counts every millisecond like the Win32
> GetTickCount.

a few comments

1) jiffies are 64 bit not 32
2) jiffies are not a constant time, eg HZ is a config option,
   exposing that internal counter to userspace sounds wrong, after
   all what would it be used for
3) wouldn't it be better to expose a wallclock time thing which
   has a constant unit of time between all kernels?

(and.. wait.. isn't that called gettimeofday() )



  reply	other threads:[~2005-12-06 10:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-06 10:36 David Engraf
2005-12-06 10:44 ` Arjan van de Ven [this message]
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
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=1133865880.2858.42.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=akpm@osdl.org \
    --cc=engraf.david@netcom-sicherheitstechnik.de \
    --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

all inboxes | Powered by JetHome®