From owner-freebsd-current  Wed Sep 24 22:12:20 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA25617
          for current-outgoing; Wed, 24 Sep 1997 22:12:20 -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 WAA25612
          for <current@FreeBSD.ORG>; Wed, 24 Sep 1997 22:12:15 -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 XAA19962;
	Wed, 24 Sep 1997 23:12:10 -0600 (MDT)
Message-Id: <199709250512.XAA19962@pluto.plutotech.com>
To: Finn Arne Gangstad <finnag@guardian.no>
cc: 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 05:39:49 +0200."
             <Pine.LNX.3.95.970925053231.28877A-100000@lucifer.guardian.no> 
Date: Wed, 24 Sep 1997 23:11:58 -0600
From: "Justin T. Gibbs" <gibbs@plutotech.com>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>Have you guys looked at the timer code in Linux? It basically is a small
>variation of this, which makes all operations  O(1) for almost
>every timer.

It looks like a 5 level hierarchical timing wheel to me.  FreeBSD currently
has a one level timing wheel.  Cascade_timers should enable interrupts
at deterministic intervals so that interrupts are defered a deterministic
amount of time.

>
>- Finn Arne
>

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