From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ee9e417a0503251057779bdb8f@mail.gmail.com>
Date: Fri, 25 Mar 2005 13:57:41 -0500
From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] tsleep / timer questions
In-Reply-To: <20050325183606.GA93332@smp500.sitetronics.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
References: <26029ec71211f29300ddd8b5225f1e38@coraid.com>
	<Pine.LNX.4.58.0503240853330.17754@enigma.lanl.gov>
	<Pine.LNX.4.60.0503241539520.12105@athena>
	<20050325183606.GA93332@smp500.sitetronics.com>
Topicbox-Message-UUID: 2b91950c-ead0-11e9-9d60-3106f5b1d025

> Eric Van Hensbergen write for Inferno, I see that he's making
> use of addclock0link(), which makes sense. This seems to be
> overkill for my needs though. I'm not sure the resolution of the
> timer on the ZT5512 blades, but mine have a minimum resolution
> of 250ms, which means that they'd be strobed twice in their
> timeout period.

the plan 9 addclock0link has an extra argument
that lets you specify how many milliseconds should go by
between calls to the function you register.

russ