Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!seismo!mcvax!ukc!stc!ist!micas!jvs
From: jvs@micas.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: Device driver timeout question ...
Message-ID: <533@micas.UUCP>
Date: Wed, 19-Aug-87 04:26:06 EDT
Article-I.D.: micas.533
Posted: Wed Aug 19 04:26:06 1987
Date-Received: Sat, 22-Aug-87 09:06:13 EDT
References: <570@obiwan.UUCP>
Organization: Nodecrest Ltd., Byfleet, England
Lines: 25

in article <570@obiwan.UUCP>, roger@mips.UUCP (Roger March) says:
>  ...  So (finally) my question is: is there a way to kill outstanding an
> 	"timeout" when realize it is no longer neccessary? If not, is there
> 	a limit to how many "timeout"s can be issued before some buffer in
> 	the kernal fills? Or, is my algorithm totally brain damaged and I
> 	should go back to writting AI programs for microprocessor controlled
> 	toasters? Thanks.

I have been writting drivers for the Sun to do various things where it is
possible for interrupts to time out. Under Sun Unix 3.2 there is a timeout
routine AND an untimeout routine to cancel a previous timeout. I don't
remember seeing any mention of untimeout in the 3.0 release manuals so maybe
it is a Sun specific addition and "real" 4.[23] BSD doesn't have it. Anyone
know the truth?

Jo. Stockley. (jvs@micas.uucp or ...!mcvax!ukc!micas!jvs)

Nodecrest Computer Systems Ltd
Byfleet, UK.

Phone: +44 09323 40555