From alsa-devel-owner@alsa.jcu.cz  Thu Jan 14 00:22:10 1999
Received: from renoir.op.net (root@renoir.op.net [209.152.193.4])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id AAA08747
	for <alsa-devel@alsa.jcu.cz>; Thu, 14 Jan 1999 00:21:52 +0100
Received: from someip.ppp.op.net (d-bm3-1a.ppp.op.net [209.152.194.90]) by renoir.op.net (o1/$Revision: 1.18 $) with ESMTP id SAA13988; Wed, 13 Jan 1999 18:21:17 -0500 (EST)
Message-Id: <199901132321.SAA13988@renoir.op.net>
To: alsa-devel@alsa.jcu.cz
cc: Thomas Hudson <thudson@cygnus.com>,
        linux-audio-dev@ginette.musique.umontreal.ca
Subject: Re: [linux-audio-dev] Re: Linux scheduler issues. 
In-reply-to: Your message of "Wed, 13 Jan 1999 14:53:08 +0100."
             <369CA544.1A653C79@ife.ee.ethz.ch> 
Date: Wed, 13 Jan 1999 18:22:14 -0500
From: Paul Barton-Davis <pbd@op.net>
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

>> For example, from the book "CLOCK_REALTIME exists on all
>> Posix.4 conformant systems...", but I can find no mention
>
>Indeed, it doesn't exist AFAIK. But you may use gettimeofday,
>which does much effort to give you the time as accurately
>as possible, and on modern PC's (read Pentium) its resolution
>is a couple of microseconds.

if you are prepared to do pentium-specific stuff, you can also use the
rdtsc instruction, and get resolution to about 60-70 cycles. 

--p

