EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: epicsEvent
From: Ben Franksen <[email protected]>
To: EPICS Techtalk <[email protected]>
Date: Thu, 28 Oct 2010 23:30:43 +0200
The documentation of libCom/osi/epicsEvent in the Developer's Guide 
carefully avoids saying anything about what happens if an event gets 
signalled and more than one thread waits for the event to happen.

The name "event" and most of what's written in the docs suggest that 
*any* thread waiting for an event will be able to continue as soon as 
the event gets signalled.

If this is true, how do I get the effect of a (binary) semaphore, i.e. 
only one thread waiting on the semaphore will continue, the others have 
to wait until the semaphore is given again?

Or, if it is false, i.e. epicsEvent really acts like a binary semaphore, 
I suggest that this be more clearly stated in the docs. It should also 
be stated how the library or system choses the thread to run; in 
VxWorks, this can be influenced when creating the semaphore (FIFO or 
priority based), but if other systems do not allow such a distinction 
then it should be explicitly stated in the documentation that no 
assumptions should be made about which thread is chosen. Note that this 
severely complicates things if you want e.g. FIFO semantics, because 
you'd have to implement all the queueing yourself.

Thanks
Ben

Replies:
Re: epicsEvent Eric Norum
Re: epicsEvent Till Straumann

Navigate by Date:
Prev: Re: OMS MAXv announces fix Ron Sluiter
Next: Opportunity to work at the Australian Synchrotron Lou Corvetti
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: YACAQ (Yet Another Channel Access Question) Benjamin Franksen
Next: Re: epicsEvent Eric Norum
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 28 Oct 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·