linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de>
To: jim.houston@ccur.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] High-res-timers part 2 (x86 platform code) take 5.1
Date: Mon, 14 Oct 2002 08:50:59 +0200	[thread overview]
Message-ID: <3DAA8571.5439.26F0B5@localhost> (raw)
In-Reply-To: <3DA89C29.93F5622E@ccur.com>

On 12 Oct 2002, at 18:03, Jim Houston wrote:

> 
> >> This patch, in conjunction with the "core" high-res-timers 
> >> patch implements high resolution timers on the i386 
> >> platforms. 
> >
> > I really don't get the notion of partial ticks, and quite frankly, this 
> > isn't going into my tree until some major distribution kicks me in the 
> > head and explains to me why the hell we have partial ticks instead of just 
> > making the ticks shorter. 
> > 
> >                Linus 
> 
> Hi Linus,
> 
> Concurrent has been using previous versions of the Posix timers patch
> in our 2.4.18 based kernel.  I like this interface and would like to 
> see it included in your kernel.

Hi,

I think nobody objects seeing the interface implemented. Maybe just how 
it's implemented. I did not have a close look, but the concept seems 
odd at first sight.

Using a individial timer as interrupt source may be a different idea 
(if avaliable for the particular hardware), but the there must be a 
balance between busy looping in the kernel and setting up of such an 
individual interrupt.

The other thing is how to correlate it with the wall clock.

Sorry for not giving answers, I just know the problems...

Regards,
Ulrich


  reply	other threads:[~2002-10-14  6:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-12 22:03 [PATCH 2/3] High-res-timers part 2 (x86 platform code) take 5.1 Jim Houston
2002-10-14  6:50 ` Ulrich Windl [this message]
2002-10-15 22:03   ` george anzinger
  -- strict thread matches above, loose matches on Subject: below --
2002-10-19  1:02 Brad Bozarth
2002-10-10  0:50 Dan Kegel
2002-10-10  1:33 ` Ben Greear
2002-10-10  3:55 ` Jeff Dike
2002-10-10  3:32   ` Dan Kegel
2002-10-10 12:34 ` mbs
2002-10-09 22:47 george anzinger
2002-10-09 23:14 ` Linus Torvalds
2002-10-09 23:42   ` george anzinger
2002-10-10 15:03     ` Eric W. Biederman
2002-10-10 15:45       ` george anzinger
2002-10-10 15:54     ` Oliver Xymoron
2002-10-10 16:24       ` george anzinger
2002-10-10 17:04         ` Oliver Xymoron
2002-10-10 17:47           ` george anzinger
2002-10-13 10:46   ` Ingo Adlung
2002-10-14  7:18     ` Vojtech Pavlik
2002-10-14 22:17       ` Pavel Machek
2002-10-15  7:13         ` Vojtech Pavlik
2002-10-15 21:45           ` george anzinger
2002-10-17 21:54   ` Randy.Dunlap
2002-10-17 22:11     ` Robert Love
2002-10-18 13:11     ` mbs

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=3DAA8571.5439.26F0B5@localhost \
    --to=ulrich.windl@rz.uni-regensburg.de \
    --cc=jim.houston@ccur.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;
as well as URLs for NNTP newsgroup(s).