This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: idle thread

From: Jonathan Larmour <jlarmour at redhat dot com>
To: Andrea Acquaviva <aacquaviva at deis dot unibo dot it>
Cc: Andrew Lunn <andrew dot lunn at ascom dot ch>,"ecos-discuss at sources dot redhat dot com" <ecos-discuss at sources dot redhat dot com>
Date: Wed, 30 Jan 2002 00:05:53 +0000
Subject: Re: [ECOS]idle thread
References: <3C4D5834.37033644@deis.unibo.it> <20020122143341.B24432@biferten.ma.tech.ascom.ch> <3C570EC8.7E14BF60@deis.unibo.it>

Andrea Acquaviva wrote:
> For example, if a thread is waiting for a blocking I/O device to fill the
> input buffer, the driver should put the thread into idle state until an
> interrupt arrives.
> How can I do this with ecos? When do the scheduler decide to switch to idle
> thread?

When there are no other runnable threads to switch to.

Drivers most often block by using some kernel synchronization primitive
like a mutex, condition variable or semaphore.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

References:
- idle thread
  - From: Andrea Acquaviva
- Re: idle thread
  - From: Andrew Lunn
- Re: idle thread
  - From: Andrea Acquaviva

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]