posted October 28, 2005 08:58            

I'd like to suggest that the FAQ in the manual be updated to include your answer.

thanks,
Jeff

posted October 28, 2005 08:52            

Event flag processing is a "special case" and is a bit different from all the other event types.

Specifically, if, say, a binSem is signaled, since the binSem's event queue is a priority queue and only a single task can be at the head of a queue (even if multiple tasks are waiting the binSem), then just that one task is made eligible when the binSem is signaled.

eFlags are different because of the fact that multiple tasks can wait on individual bits of an eFlag -- i.e. there is no real sense of priority associated with tasks waiting an eFlag, because a change in any bit must be seen by every task that's watching that bit. Therefore, Salvo has to make all tasks that wait an eFlag eligible whenever the eFlag is signaled. The now-eligible tasks all retain their priorities, of course, with regard to when they'll actually run.

So, yes, the FAQ is talking about all event types except eFlags. eFlags behave slightly differently, and one sees this when more than one task waits a particular eFlag.

posted October 28, 2005 07:45            

In the notes for OSSetEFlag() (p.344), it states that all tasks waiting an event flag are made eligible by forcing any zeroed bits to one.

However, in the FAQ (p. 235) 'when an event occurs and there are tasks waiting for it, which task(s) become eligible?', it states that only a single task will become eligible.

Which statement is correct?

It sounds like the FAQ is only talking about semaphores and not event flags. Is that the case?