Lines Matching defs:Signal
47 // Default to "wait forever" timing, which means have to get a Signal()
66 // Minimize spurious signal creation window by recycling asap.
73 // Broadcast() is guaranteed to signal all threads that were waiting (i.e., had
91 // Signal() will select one of the waiting threads, and signal it (signal its
92 // cv_event). For better performance we signal the thread that went to sleep
95 void ConditionVariable::Signal() {
100 return; // No one to signal.
137 // waiting_list_. If it was selected by Broadcast() or Signal(), then it is
297 a second thread, it would be impossible to actually signal all
307 3) How does this implementation cause spurious signal events? The
308 cause in this implementation involves a race between a signal via
309 time-out and a signal via Signal() or Broadcast(). The series of
320 c) A call to Signal() (or Broadcast()) on a second thread proceeds, and
324 d) The Signal() method (step c) calls SetEvent() on waiting_event (step b).
337 Signal/Broadcast() actions. When both are used, it will be rare that
343 race was "lost" and a spurious signal took place). That would be bad
362 thread *can* now be signaled by a call to Broadcast() or Signal().
368 Release() our internal lock during Signal() and Broadcast(). If we tried
371 hold a lock on one thread while calling Signal() on another, and that would
372 block Signal().
382 Signal() and Broadcast(), to access internal data structures. As a
417 12) Why is it that the cv_events removed from list in Broadcast() and Signal()
