[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
BOUNCE rtl@rtlinux.org: Approval required: (fwd)
- To: rtl@rtlinux.org
- Subject: BOUNCE rtl@rtlinux.org: Approval required: (fwd)
- From: Der Herr Hofrat <der.herr@hofr.at>
- Date: Tue, 10 Jul 2001 19:08:43 +0200 (CEST)
>From owner-rtl Tue Jul 10 10:48:13 2001
Received: from web5202.mail.yahoo.com (web5202.mail.yahoo.com [216.115.106.170])
by localhost.localdomain (8.11.2/8.11.2) with SMTP id f6AGmDf07465
for <rtl@rtlinux.org>; Tue, 10 Jul 2001 10:48:13 -0600
Message-ID: <20010710164714.14354.qmail@web5202.mail.yahoo.com>
Received: from [193.62.235.62] by web5202.mail.yahoo.com via HTTP; Tue, 10 Jul 2001 17:47:14 BST
Date: Tue, 10 Jul 2001 17:47:14 +0100 (BST)
From: =?iso-8859-1?q?Raul?= <raulrtl@yahoo.co.uk>
Subject: usleep, rtl_delay and clock_nanosleep performance
To: Real Time Linux <rtl@rtlinux.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Hi all
I need a 25 usec delay within a rt thread. Somewhere I
read that rtl_delay() should not be used (I take it
because it is blocking), instead usleep() or
clock_nanosleep() are preferable. However when I
measured the actual delay of these functions I found
that clock_nanosleep and usleep make a wait of nearly
50 usec (somthing to do with the scheduling?) whereas
rtl_delay() is more precise, with a wait of 27 usec.
Is the use of a non-blocking function with a poorer
precission a compromise? Is rtl_delay not advisable to
use under any circunstances, even if I guarantee that
the rt thread period will be larger than 25 usec?
thanks again
Raul
____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie
----- End of forwarded message from owner-rtl@fsmlabs.com -----