Lines Matching refs:timers

115 timers (C<ev_timer>), absolute timers with customised rescheduling
764 time used for relative timers. You can treat it as the timestamp of the
875    - Queue all expired timers.
926 excellent way to do this for generic recurring timers or from within
930 (e.g. non-repeating timers) in which case you have to C<ev_ref>
1307 non-repeating timers are being stopped when they become pending - but
1495 other jobs, but since timers normally get invoked first, the timeout
1782 Timer watchers are simple relative timers that generate an event after a
1785 The timers are based on real time, that is, if you register an event that
1794 early", below). If multiple timers become ready during the same loop
1970 starting, stopping and updating the timers, at the expense of a major
1985 off after the first million or so of active timers, i.e. it's usually
2076 If you want to compare wall clock/system timestamps to your timers, then
2092 long suspend would be detected as a time jump by libev, and timers would
2102 will be counted towards the timers. When no monotonic clock source is in
2209 Periodic watchers are also timers of a kind, but they are very versatile
2228 timers, such as triggering an event on each "midnight, local time", or
2232 As with timers, the callback is guaranteed to be invoked only when the
2234 timers become ready during the same loop iteration then the ones with
2266 This can be used to create timers that do not drift with respect to the
2325 This can be used to create very complex timers, such as a timer that
4773 only some watcher types other than I/O and timers (e.g. prepare,
4792 watchers, timers and monotonic clock support.