Lines Matching defs:Wait
32 // was not willing to wait for all the threads to terminate. Such hasty
46 void ConditionVariable::Wait() {
47 // Default to "wait forever" timing, which means have to get a Signal()
48 // or Broadcast() to come out of this wait state.
109 // wait. This means that (worst case) we may over time create as many cv_event
110 // objects as there are threads simultaneously using this instance's Wait()
113 // We hold internal_lock, courtesy of Wait().
129 // RecycleEvent() takes a cv_event that was previously used for Wait()ing, and
130 // recycles it for use in future Wait() calls for this or other threads.
135 // We hold internal_lock, courtesy of Wait().
289 try to Wait() after a Broadcast() has been called, but before all the
293 Wait()? See FAQ-question-1, or consider the following: If a single
294 event were used, then numerous threads calling Wait() could release
338 the race will appear, and it would require MANY Wait() and signaling
340 would have to create and destroy events for every call to Wait().
342 would be costly (per wait), and would only be a rare benefit (when the
357 entry into a wait state? We commit to the wait activity when we
358 allocate the wait_event for use in a given call to Wait(). This
361 the defining moment when "the wait state has been entered," as that
363 Hence we actually "commit to wait" before releasing the lock, making
378 in each Wait() call). One of the constructors now takes a specific
379 lock as an argument, and a there are corresponding Wait() calls that
406 lock during a Wait(). This places Wait() functionality exactly
408 that there can be nested Acquire()'s of locks, and Wait() had to
420 a thread in or around the WaitForSingleObject() call of Wait(), and those
433 container. This requirement exposes itself in the Wait() method, where a
