BOUNCE rtl@rtlinux.org: Approval required: (fwd)

[Der Herr Hofrat <der.herr@hofr.at>]

>From owner-rtl Sun May 20 07:13:20 2001
Received: from kanga.hofr.at (N733P030.adsl.highway.telekom.at [62.47.35.158])
	by hq.fsmlabs.com (8.11.2/8.11.2) with ESMTP id f4KDDIr12110;
	Sun, 20 May 2001 07:13:19 -0600
Received: (from hofrat@localhost)
	by kanga.hofr.at (8.10.2/8.10.2/SuSE Linux 8.10.0-0.3) id f4KCAjr14672;
	Sun, 20 May 2001 14:10:45 +0200
From: Der Herr Hofrat <der.herr@hofr.at>
Message-Id: <200105201210.f4KCAjr14672@kanga.hofr.at>
Subject: Re: [rtl] general question about nanosleep, usleep, semaphores and other
 waits.
In-Reply-To: <3B07AE23.F833430@city.dk> from root at "May 20, 2001 01:44:35 pm"
To: rtl@fsmlabs.com
Date: Sun, 20 May 2001 14:10:45 +0200 (CEST)
CC: rtlinux <rtl@rtlinux.org>
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

> Hi all
> This is a general question.
> 
> When using nanosleep, sem_wait, usleep etc. in RT - threds these
> funktion is performed as sleep. it meens the thread is suspended until
> the wakeuptime ore call to sem_post from other thred. thats fine.
> 
> But what happens withe these funktions is called from a fifo handler or
> in init_module. I know that nanosleep is busy wait, but what about fx.

nanosleep is not busy wait, it calls clock_nanosleep wich sets up the timer
marks it selfe suspended and then calls rtl_schedul(). 

hofrat

----- End of forwarded message from owner-rtl@fsmlabs.com -----