All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <markh@compro.net>
To: Arjan van de Ven <arjan@infradead.org>
Cc: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
	Jan Engelhardt <jengelh@medozas.de>,
	"Kok, Auke" <auke-jan.h.kok@intel.com>,
	"solsTiCe d'Hiver" <solstice.dhiver@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: no cpu MHz in /proc/cpuinfo on 2.6.25.4-rt6
Date: Wed, 11 Jun 2008 16:59:15 -0400	[thread overview]
Message-ID: <48503CA3.9060808@compro.net> (raw)
In-Reply-To: <20080611135532.651fb5ae@infradead.org>

Arjan van de Ven wrote:
> On Wed, 11 Jun 2008 16:37:38 -0400
>>> Mark 
>>>
>> Ok, what would one use besides the tsc to take a fast high-res time
>> stamp in a kernel module that could also be used in user land (same
>> time source) to for instance calculate  the the time between an event
>> in the kernel to an event in user land?
>>
>> do_gettimeofday / gettimeofday are not really acceptable.
> 
> 
> why not? both of these (they're teh same) are the best the kernel can
> do. If there was a better way to do it, gettimeofday() would use it.
> It's not even a system call if we can get away with it
> (although system calls are pretty cheap)
> 
> really, think about it. if there was a better way, gettimeofday() would
> use it.
> 
> 

The results of gettimeofday are worse that what you describe about the tsc.
NTP etc... and take considerably longer the a tsc read.

Mark

  reply	other threads:[~2008-06-11 21:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 19:52 PROBLEM: no cpu MHz in /proc/cpuinfo on 2.6.25.4-rt6 solsTiCe d'Hiver
2008-06-10 20:13 ` Arjan van de Ven
2008-06-10 20:42   ` Kok, Auke
2008-06-11 12:42     ` Jan Engelhardt
2008-06-11 13:36       ` Arjan van de Ven
2008-06-11 13:52         ` Jan Engelhardt
2008-06-11 13:58           ` Arjan van de Ven
2008-06-11 14:14             ` linux-os (Dick Johnson)
2008-06-11 15:10               ` Peter Zijlstra
2008-06-11 15:36               ` Arjan van de Ven
2008-06-11 16:59                 ` Mark Hounschell
2008-06-11 17:44                   ` Arjan van de Ven
2008-06-11 17:54                     ` Mark Hounschell
2008-06-11 20:29                       ` Arjan van de Ven
2008-06-11 20:37                       ` Mark Hounschell
2008-06-11 20:55                         ` Arjan van de Ven
2008-06-11 20:59                           ` Mark Hounschell [this message]
2008-06-11 20:58                         ` Arjan van de Ven
2008-06-11 21:08                           ` Mark Hounschell
2008-06-11 21:28                             ` Arjan van de Ven
2008-06-11 21:39                             ` Chris Friesen
2008-06-11 23:08                       ` Andi Kleen
2008-06-11 16:08         ` Ray Lee
2008-06-11 16:32           ` Arjan van de Ven
2008-06-11 12:40 ` Jan Engelhardt
2008-06-11 14:15   ` solsTiCe d'Hiver
2008-06-11 14:36     ` Jan Engelhardt
2008-06-11 15:35       ` solsTiCe d'Hiver

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=48503CA3.9060808@compro.net \
    --to=markh@compro.net \
    --cc=arjan@infradead.org \
    --cc=auke-jan.h.kok@intel.com \
    --cc=jengelh@medozas.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=solstice.dhiver@gmail.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.