From: Michael Raymond <mraymond@sgi.com>
To: Mark Salisbury <gonar@mediaone.net>
Cc: george anzinger <george@mvista.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andre Hedrick <andre@linux-ide.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
schwidefsky@de.ibm.com, linux-kernel@vger.kernel.org,
high-res-timers-discourse@lists.sourceforge.net
Subject: Re: Linux-Kernel Archive: No 100 HZ timer !
Date: Fri, 13 Apr 2001 07:55:53 -0500 [thread overview]
Message-ID: <20010413075553.A102611@fsgi654.americas.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10104122102170.4564-100000@master.linux-ide.org> <m1snjdtgcc.fsf@frodo.biederman.org> <3AD6B894.39848F3F@mvista.com> <002d01c0c414$346b2140$6501a8c0@gonar.com>
In-Reply-To: <002d01c0c414$346b2140$6501a8c0@gonar.com>; from gonar@mediaone.net on Fri, Apr 13, 2001 at 08:20:56AM -0400
On Fri, Apr 13, 2001 at 08:20:56AM -0400, Mark Salisbury wrote:
> inner loop, i.e. interrupt timer code should never have to convert from some
> real time value into number of decrementer ticks in order to set up the next
> interrupt as that requires devides (and 64 bit ones at that) in a tickless
> system.
>
> this is why any variable interval list/heap/tree/whatever should be kept in
> local ticks. frequently used values can be pre-computed at boot time to
> speed up certain calculations (like how many local ticks/proc quantum)
What about machines without synchronized local ticks? We're going to
have to end up doing conversions anyway because of drift and machines
without even the same speed CPUs. A time based system using local cached
values such as cycles_per_usec would better be able to handle this.
Michael
--
Michael A. Raymond Office: (651) 683-3434
Irix Core Kernel Group
next prev parent reply other threads:[~2001-04-13 12:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3AD622AB.5F0A061B@linux-ide.org>
2001-04-12 21:52 ` Andre Hedrick
2001-04-12 23:12 ` Alan Cox
2001-04-12 23:21 ` Andre Hedrick
2001-04-13 2:58 ` george anzinger
2001-04-13 4:04 ` Andre Hedrick
2001-04-13 7:21 ` Eric W. Biederman
2001-04-13 8:28 ` george anzinger
2001-04-13 12:20 ` Mark Salisbury
2001-04-13 12:55 ` Michael Raymond [this message]
2001-04-13 15:50 ` george anzinger
2001-04-13 9:05 ` David Schleef
2001-04-13 12:47 ` Alan Cox
2001-04-14 13:57 ` Rogier Wolff
2001-04-15 2:10 ` Roger Larsson
2001-04-15 7:22 ` george anzinger
2001-04-16 15:32 ` Pavel Machek
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=20010413075553.A102611@fsgi654.americas.sgi.com \
--to=mraymond@sgi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=ebiederm@xmission.com \
--cc=george@mvista.com \
--cc=gonar@mediaone.net \
--cc=high-res-timers-discourse@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.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 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®