This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Blocking restricted in DSRs
- From: Bob Koninckx <bob dot koninckx at o-3s dot com>
- To: "Miguel J. Vega" <mserrano at engin dot umich dot edu>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Mon, 26 Jul 2004 22:13:32 +0200
- Subject: Re: [ECOS] Blocking restricted in DSRs
- Organization: o-3s
- References: <Pine.LNX.4.58.0407261456540.18423@red.engin.umich.edu>
- Reply-to: bob dot koninckx at o-3s dot com
Things like waiting for a semaphore. Blocking is something you do at
thread level. The thread "blocks" (or goes to sleep) until another
thread or interrupt wakes it up again. Basically, this waking up is done
by the scheduler, which explains why you should not block in a DSR,
which is called _before_ the scheduler.
Hope this makes it a little bit clearer,
Bob
On Mon, 2004-07-26 at 21:01, Miguel J. Vega wrote:
> Hi everyone,
>
> I have read that DSRs should not include calling functions that "block".
> What exactly is meant by "blocking"?
>
> Thanks,
>
> Miguel J. Vega
> FEGI C&DH Team
> University of Michigan
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss