public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: george@mvista.com
Cc: evan@coolrunningconcepts.com, linux-kernel@vger.kernel.org
Subject: Re: Timer idea
Date: Tue, 15 Nov 2005 11:12:20 -0800	[thread overview]
Message-ID: <1132081941.2906.5.camel@leatherman> (raw)
In-Reply-To: <437A2FDA.6090204@mvista.com>

On Tue, 2005-11-15 at 10:58 -0800, George Anzinger wrote:
> evan@coolrunningconcepts.com wrote:
> > I was thinking about benchmarking, profiling, and various other applications
> > that might need frequent access to the current time.  Polling timers or
> > frequent timer signal delivery both seem like there would be a lot of overhead.
> >  I was thinking it would be nice if you could just read the time information
> > without making an OS call.
> > 
> > I figure the kernel keeps accurate records of current time information and the
> > values of various timers.  I then had the idea that one could have a /dev or
> > maybe a /proc entry that would allow you to mmap() the kernel records (read
> > only) and then you could read this information right from the kernel without
> > any overhead.
> > 
> 
> Your are describing the vsyscall.  John Stultz and company are actively working on this as we speak. 
>   If memory serves, it is already available on some platforms.

Yep. x86-64 already supports this as does ppc64 via vsyscall/VDSOs. ia64
has a different variant on it as well (fast syscalls).

thanks
-john


  reply	other threads:[~2005-11-15 19:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15 17:24 Timer idea evan
2005-11-15 18:20 ` Kenichi Okuyama
2005-11-15 18:58 ` George Anzinger
2005-11-15 19:12   ` john stultz [this message]
2005-11-15 19:13 ` linux-os (Dick Johnson)
2005-11-15 19:34   ` George Anzinger
2005-11-15 20:20   ` Christopher Friesen
2005-11-15 21:11     ` linux-os (Dick Johnson)

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=1132081941.2906.5.camel@leatherman \
    --to=johnstul@us.ibm.com \
    --cc=evan@coolrunningconcepts.com \
    --cc=george@mvista.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