From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 25 Mar 2005 21:04:01 +0100 From: "Devon H. O'Dell " To: Russ Cox , Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] tsleep / timer questions Message-ID: <20050325200401.GB93332@smp500.sitetronics.com> References: <26029ec71211f29300ddd8b5225f1e38@coraid.com> <20050325183606.GA93332@smp500.sitetronics.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2B/JsCI69OhZNC5r" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i Cc: Topicbox-Message-UUID: 2bac40f0-ead0-11e9-9d60-3106f5b1d025 --2B/JsCI69OhZNC5r Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 25, 2005 at 01:57:41PM -0500, Russ Cox wrote: > > 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. >=20 > 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. >=20 > russ Oh -- I didn't see this -- the only one I found was defined in portfns.h as: void addclock0link(void (*)(void)); I must be missing something -- I don't see code for that in the kernel either. If I'm missing something, I guess this would be ideal rather than a kproc. --Devon --2B/JsCI69OhZNC5r Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCRG6xSkf3jVXOdl0RAiQDAJ4qib/DpSVh/G3D9nUWvkOd85WNNwCcCWyz L2nLObQWCjZ/sjjZfsxtFyE= =3oRZ -----END PGP SIGNATURE----- --2B/JsCI69OhZNC5r--