Lines Matching refs:active
540 i.e. keep at least one watcher active per fd at all times. Stopping and
605 While this backend scales well, it requires one system call per active
665 etc.). None of the active event watchers will be stopped in the normal
814 until either no event watchers are active anymore or C<ev_break> was
817 The return value is false if there are no more active watchers (which
868 (active idle watchers, EVRUN_NOWAIT or not having
869 any active watchers at all will result in not sleeping).
883 were used, or there are no active watchers, goto FINISH, otherwise
925 exiting if no event watchers registered by it are active. It is also an
928 before stop> (but only if the watcher wasn't active before, or was active
934 running when nothing else is active.
1138 As long as your watcher is active (has been started but not stopped) you
1273 macro on a watcher that is active (it can be pending, however, which is a
1293 Starts (activates) the given watcher. Only active watchers will receive
1294 events. If the watcher is already active nothing will happen.
1303 Stops the given watcher if active, and clears the pending status (whether
1304 the watcher was active or not).
1308 calling C<ev_TYPE_stop> ensures that the watcher is neither active nor
1314 Returns a true value iff the watcher is active (i.e. it has been started
1315 and not yet been stopped). As long as a watcher is active you must not modify
1322 is pending (but not active) you must not call an init function on it (but
1349 You I<must not> change the priority of a watcher as long as it is active or
1400 active, pending and so on. In this section these states and the rules to
1417 =item started/running/active
1423 and call libev functions on it that are documented to work on active watchers.
1427 If a watcher is active and libev determines that an event it is interested
1433 The watcher might or might not be active while it is pending (for example,
1434 an expired non-repeating timer can be pending but no longer active). If it
1437 moved, freed or reused. And if it is active the rules described in the
1440 It is also possible to feed an event on a watcher that is not active (e.g.
1442 active.
1449 of whether it was active or not, so stopping a watcher explicitly before
1570 while the watcher is active, you can look at the member and expect some
1574 is active, but you can also modify it. Modifying it may not do something
1860 whether the watcher is active or not:
1985 off after the first million or so of active timers, i.e. it's usually
2156 Returns the remaining time until a timer fires. If the timer is active,
2342 When active, returns the absolute time that the watcher is supposed
2748 path for as long as the watcher is active.
2856 active, the process will not block when waiting for new events.
2865 As long as there is at least one active idle watcher, libev will never
2944 coroutines into libev programs, by yielding to other active coroutines
2949 loop from blocking if lower-priority coroutines are active, thus mapping
2970 normally only do a bit of work for each active connection, and if there
2979 single global idle watcher that is active as long as you have one active
3155 As long as the watcher is active, the callback will be invoked every
3166 is active, i.e., the embedded loop will automatically be forked when the
3289 process typically wants to start fresh, i.e. without any active watchers.
3367 watchers do: as long as the C<ev_async> watcher is active, you can signal
3504 the loop iterates next and checks for the watcher to have become active,
3870 and that due to some magic, the currently active coroutine is stored in a
3884 matter when, or whether the watcher is active or not when this function is
4060 The destructor automatically stops the watcher if it is active.
4138 must be called at least once. Unlike the C counterpart, an active watcher
4158 Stops the watcher if it is active. Again, no C<loop> argument.
5492 =item active
5494 A watcher is active as long as it has been started and not yet stopped.