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: Andrew Lunn <andrew dot lunn at ascom dot ch>
To: "Woller, Thomas" <tom dot woller at cirrus dot com>
Cc: eCos users <ecos-discuss at sources dot redhat dot com>
Date: Mon, 11 Feb 2002 16:19:23 +0100
Subject: Re: [ECOS] cyg_semaphore_post
References: <973C11FE0E3ED41183B200508BC7774C022FBA8D@csexchange.crystal.cirrus.com>

On Mon, Feb 11, 2002 at 09:10:16AM -0600, Woller, Thomas wrote:
> When there are a series of
> threads waiting on the same semaphore, we basically want the
> highest priority thread to run, NOT the first one that happened
> to wait on the semaphore.

OK. You use this sort of Semaphore. You should be able to answer my
question... to me it still does not make sense. Why do you want
prioritization on what gets woken up? Please can you give an
example...

        Andrew

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

References:
- RE: cyg_semaphore_post
  - From: Woller, Thomas

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