Date: Sat, 18 Nov 2000 17:48:21 +0200 From: Mark Murray <mark@grondar.za> To: Daniel Eischen <eischen@vigrid.com> Cc: Mike Smith <msmith@FreeBSD.ORG>, arch@FreeBSD.ORG Subject: Re: "Monotonic" counter/register call - commit candidate. Message-ID: <200011181548.eAIFmOJ12563@gratis.grondar.za> In-Reply-To: <Pine.SUN.3.91.1001118101705.11966A-100000@pcnet1.pcnet.com> ; from Daniel Eischen <eischen@vigrid.com> "Sat, 18 Nov 2000 10:25:22 EST." References: <Pine.SUN.3.91.1001118101705.11966A-100000@pcnet1.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
If this thread is going to go in this direction, then please change the subject. I still haven't got resolution on _my_ thread. M > On Sat, 18 Nov 2000, Mike Smith wrote: > > > On a somewhat related note, I could use something to measure time > > > that wasn't a system call in the threads library. Is there a way > > > we can get a timer or something that was mmap'able? > > > > You could probably arrange for some portion of the timecounter space to > > be mapped read-only into userspace. How precise does it need to be? > > Scheduling tick resolution or better. I would like to use it for > waking up threads that are in states that timeout. The smallest > resolution would be for something like pthread_cond_timedwait() > which is timespec (nanosecs), but we don't need to be that resolute. > Right now we use gettimeofday(). -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011181548.eAIFmOJ12563>