Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!labrea!decwrl!decvax!savax!elrond!muffy!nawaf
From: nawaf@muffy.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: Device driver timeout question ...
Message-ID: <666@muffy.CalComp.COM>
Date: Tue, 18-Aug-87 09:38:45 EDT
Article-I.D.: muffy.666
Posted: Tue Aug 18 09:38:45 1987
Date-Received: Thu, 20-Aug-87 01:39:49 EDT
References: <570@obiwan.UUCP>
Organization: CalComp, A Lockheed Company, Hudson, NH, USA
Lines: 24
Keywords: device driver, timeouts, sick devices
Summary: untimeout function - callout structure

In article <570@obiwan.UUCP>, roger@mips.UUCP (Roger March) writes:
> 	  So (finally) my question is: is there a way to kill outstanding an
> 	"timeout" when realize it is no longer neccessary?

My understanding is that you can call:

	untimeout(fun, arg)
	int (*fun)();
	caddr_t arg;

to remove a function timeout call from the callout structure queue.

> If not, is there a limit to how many "timeout"s can be issued before
> some buffer in the kernal fills?

A number of callout structures are allocated, 16 + MAXUSERS I believe.
No free ones results in a "timeout table overflow" panic.  Look in
sys/kern_clock.c conf/param.c and h/callout.h for details.

-- 
Nawaf Bitar
uucp:	 ...{harvard,decvax}!elrond!nawaf or nawaf@elrond.CalComp.COM
usps:    CalComp (A Lockheed Company), Display Products Division,
	 Mail Stop PTP2-2D01, CS 908, Hudson NH 03051 (603) 885 8135