All of lore.kernel.org
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: dank@kegel.com
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"high-res-timers-discourse@lists.sourceforge.net" 
	<high-res-timers-discourse@lists.sourceforge.net>
Subject: Re: high resolution timers in 2.5? (was: [2.6] The List, pass #2)
Date: Fri, 19 Jul 2002 13:26:15 -0700	[thread overview]
Message-ID: <3D3875E7.BDFC00DE@mvista.com> (raw)
In-Reply-To: 3D38442B.FC307ADE@kegel.com

dank@kegel.com wrote:
> 
> Mark Salisbury wrote:
> > On Friday 19 July 2002 00:47, Guillaume Boissiere wrote:
> > > Would be nice to have before feature freeze, but most likely 2.7:
> > >   o High resolution timers
> >
> > this has been done for almost a year now, what is holding it up?
> 
> I don't know, but it's about time.  George Anziger should know.
> 
> George,
> Have you submitted a high-resolution-timers patch to Linux for 2.5?
> I seem to recall he didn't like the patch when he first saw
> it, but that was so long ago presumably it's much cleaner now?
> - Dan
That was really a very different patch.  The hang up has
been time to work on the code.  There are a few, minor,
changes, like eliminating nanosleep() (it should call
clock_nanosleep()), and then the code clean up to remove all
the debug cruft.  

The next bit I want to submit is the changes to the timer
queue to allow subjiffie timers...

I am hoping to convince my boss to allow me to work on this
full time so I can make some real progress.  As always, any
help will be gratefully accepted :)

-- 
George Anzinger   george@mvista.com
High-res-timers: 
http://sourceforge.net/projects/high-res-timers/
Real time sched:  http://sourceforge.net/projects/rtsched/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml

      reply	other threads:[~2002-07-19 20:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-19 16:54 high resolution timers in 2.5? (was: [2.6] The List, pass #2) dank
2002-07-19 20:26 ` george anzinger [this message]

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=3D3875E7.BDFC00DE@mvista.com \
    --to=george@mvista.com \
    --cc=dank@kegel.com \
    --cc=high-res-timers-discourse@lists.sourceforge.net \
    --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.