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: cyg_semaphore_post

From: Robin Farine <robin dot farine at acn-group dot ch>
To: Stijn Symons <stijn dot symons at acunia dot com>
Cc: eCos users <ecos-discuss at sources dot redhat dot com>
Date: 11 Feb 2002 14:22:08 +0100
Subject: Re: [ECOS] cyg_semaphore_post
References: <3C67B1CC.8D39A6E@acunia.com><20020211130932.W26360@biferten.ma.tech.ascom.ch> <3C67BB2A.4AE775C0@acunia.com>

On Mon, 2002-02-11 at 13:38, Stijn Symons wrote:

[snip]

> I'm mapping an API to eCos, the API states that  "When any threads are
> waiting on the semaphore count to become higher than zero, the thread with
> the highest priority will be woken up to acquire the semaphore".

... which in cases of heavy load of the semaphore will lead to
starvation of low priority threads :-\

> 
> Stijn

Robin



Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Follow-Ups:
- Re: cyg_semaphore_post
  - From: Chris Gray
- Re: cyg_semaphore_post
  - From: Nick Garnett

References:
- cyg_semaphore_post
  - From: Stijn Symons
- Re: cyg_semaphore_post
  - From: Andrew Lunn
- Re: cyg_semaphore_post
  - From: Stijn Symons

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