Lines Matching refs:in

85       spends in the event provider.
105 Returns the initialized default loop. It may return NULL in case of
109 an application, the default loop is in no way different than the ones
125 zero in all other cases.
129 you should run the event loop again sometime in the future).
133 you should run the event loop again sometime in the future).
140 requests or closing handles in the loop.
159 This can be used in conjunction with `uv_run(loop, UV_RUN_NOWAIT)` to
160 poll in one thread and run the event loop's callbacks in another see
164 Embedding a kqueue fd in another kqueue pollset doesn't work on all platforms. It's not
169 Get the poll timeout. The return value is in milliseconds, or -1 for no
174 Return the current timestamp in milliseconds. The timestamp is cached at
178 The timestamp increases monotonically from some arbitrary point in time.
188 at the start of the event loop tick in order to reduce the number of
203 Reinitialize any kernel state necessary in the child process after
206 Previously started watchers will continue to be started in the
210 loop created in the parent process that you plan to continue to
211 use in the child, including the default loop (even if you don't
212 continue to use it in the parent). This function must be called
214 the loop in the child. Failure to do so will result in undefined
218 When possible, it is preferred to create a new loop in the child
219 process instead of reusing a loop created in the parent. New loops
220 created in the child process after the fork should not use this
232 On Mac OS X, if directory FS event handles were in use in the
235 implementation. Instead, uses of directory FS event handles in
241 On AIX and SunOS, FS event handles that were already started in
243 events in the child process; they must be closed and restarted.