From owner-freebsd-current  Thu Sep 25 00:47:35 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id AAA03200
          for current-outgoing; Thu, 25 Sep 1997 00:47:35 -0700 (PDT)
Received: from usr03.primenet.com (tlambert@usr03.primenet.com [206.165.6.203])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA03193
          for <current@FreeBSD.ORG>; Thu, 25 Sep 1997 00:47:31 -0700 (PDT)
Received: (from tlambert@localhost)
	by usr03.primenet.com (8.8.5/8.8.5) id AAA10520;
	Thu, 25 Sep 1997 00:47:26 -0700 (MST)
From: Terry Lambert <tlambert@primenet.com>
Message-Id: <199709250747.AAA10520@usr03.primenet.com>
Subject: Re: timeout management (was: Re: cvs commit: ...)
To: gibbs@plutotech.com (Justin T. Gibbs)
Date: Thu, 25 Sep 1997 07:47:25 +0000 (GMT)
Cc: finnag@guardian.no, archie@whistle.com, current@FreeBSD.ORG
In-Reply-To: <199709250512.XAA19962@pluto.plutotech.com> from "Justin T. Gibbs" at Sep 24, 97 11:11:58 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
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.

I agree with Justin on this.  The Linux code is insufficient, in this case.

BTW, it's linux/kernel/sched.c, not just kernel/sched.c.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.