From owner-freebsd-current  Wed Sep 24 22:54:23 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA27460
          for current-outgoing; Wed, 24 Sep 1997 22:54:23 -0700 (PDT)
Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA27452
          for <current@FreeBSD.ORG>; Wed, 24 Sep 1997 22:54:20 -0700 (PDT)
Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130])
	by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id XAA20672;
	Wed, 24 Sep 1997 23:54:15 -0600 (MDT)
Message-Id: <199709250554.XAA20672@pluto.plutotech.com>
To: Finn Arne Gangstad <finnag@guardian.no>
cc: "Justin T. Gibbs" <gibbs@plutotech.com>, Archie Cobbs <archie@whistle.com>,
        current@FreeBSD.ORG
Subject: Re: timeout management (was: Re: cvs commit: ...) 
In-reply-to: Your message of "Thu, 25 Sep 1997 07:47:14 +0200."
             <Pine.LNX.3.95.970925072713.29522A-100000@lucifer.guardian.no> 
Date: Wed, 24 Sep 1997 23:54:02 -0600
From: "Justin T. Gibbs" <gibbs@plutotech.com>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>There was a lot of discussion on the kernel list about cascace_timers
>enabling timers now and then, in practice cascade_timers never move many
>timers so it's not really a problem, even less of a problem when it just
>grabs the timer lock.
>
>- Finn Arne

If the granularity of the timer interval is large when compared to
the speed with which a given application generates timers for the same
interval, you could have a problem. 

If you want to do RT, I think you have to enable timers periodically,
or you may miss a deadline.

--
Justin T. Gibbs
===========================================
  FreeBSD: Turning PCs into workstations
===========================================