Lines Matching full:up

26 …ens in a pollset, multiple threads are woken up and there are no guarantees on which thread actual…
28 …up. Let's say *Thread P* was calling a `grpc_completion_queue_pluck()` and was actually interested…
34 …ently call `epoll_wait()`, we are guaranteed that only one thread is woken up if one of the `fds` …
36 …dable/writable, all the threads in all the `pollsets` (in which that `fd` is present) are woken up.
47 …eans that for every incoming new channel, all the threads waiting on all the pollsets are woken up.
54 There are other scenarios especially on the client side where an fd can end up being on multiple po…
59 …nto a single epoll-based set. This would ensure that only one thread wakes up in case of an event …
65 * `event_fd`: A level triggered _event fd_ that is used to wake up all the threads waiting on this …
68 In this new model, only one thread wakes up whenever an event of interest happens in an epoll set.
88 …* Wake up all the threads waiting on the smaller `polling_island`'s `epoll_fd` (by signaling the `…
93 …es that the thread that is woken up is the thread that is actually interested in the event.  So th…
95 …ead also had a `event_fd` on which it was listening to and hence waking it up was as simple as sig…
119 …up polling threads typically when the event for which the polling thread is waiting is already com…