… | |
… | |
9 | =head2 EXAMPLE PROGRAM |
9 | =head2 EXAMPLE PROGRAM |
10 | |
10 | |
11 | // a single header file is required |
11 | // a single header file is required |
12 | #include <ev.h> |
12 | #include <ev.h> |
13 | |
13 | |
|
|
14 | #include <stdio.h> // for puts |
|
|
15 | |
14 | // every watcher type has its own typedef'd struct |
16 | // every watcher type has its own typedef'd struct |
15 | // with the name ev_<type> |
17 | // with the name ev_TYPE |
16 | ev_io stdin_watcher; |
18 | ev_io stdin_watcher; |
17 | ev_timer timeout_watcher; |
19 | ev_timer timeout_watcher; |
18 | |
20 | |
19 | // all watcher callbacks have a similar signature |
21 | // all watcher callbacks have a similar signature |
20 | // this callback is called when data is readable on stdin |
22 | // this callback is called when data is readable on stdin |
21 | static void |
23 | static void |
22 | stdin_cb (EV_P_ struct ev_io *w, int revents) |
24 | stdin_cb (EV_P_ ev_io *w, int revents) |
23 | { |
25 | { |
24 | puts ("stdin ready"); |
26 | puts ("stdin ready"); |
25 | // for one-shot events, one must manually stop the watcher |
27 | // for one-shot events, one must manually stop the watcher |
26 | // with its corresponding stop function. |
28 | // with its corresponding stop function. |
27 | ev_io_stop (EV_A_ w); |
29 | ev_io_stop (EV_A_ w); |
… | |
… | |
30 | ev_unloop (EV_A_ EVUNLOOP_ALL); |
32 | ev_unloop (EV_A_ EVUNLOOP_ALL); |
31 | } |
33 | } |
32 | |
34 | |
33 | // another callback, this time for a time-out |
35 | // another callback, this time for a time-out |
34 | static void |
36 | static void |
35 | timeout_cb (EV_P_ struct ev_timer *w, int revents) |
37 | timeout_cb (EV_P_ ev_timer *w, int revents) |
36 | { |
38 | { |
37 | puts ("timeout"); |
39 | puts ("timeout"); |
38 | // this causes the innermost ev_loop to stop iterating |
40 | // this causes the innermost ev_loop to stop iterating |
39 | ev_unloop (EV_A_ EVUNLOOP_ONE); |
41 | ev_unloop (EV_A_ EVUNLOOP_ONE); |
40 | } |
42 | } |
… | |
… | |
60 | |
62 | |
61 | // unloop was called, so exit |
63 | // unloop was called, so exit |
62 | return 0; |
64 | return 0; |
63 | } |
65 | } |
64 | |
66 | |
65 | =head1 DESCRIPTION |
67 | =head1 ABOUT THIS DOCUMENT |
|
|
68 | |
|
|
69 | This document documents the libev software package. |
66 | |
70 | |
67 | The newest version of this document is also available as an html-formatted |
71 | The newest version of this document is also available as an html-formatted |
68 | web page you might find easier to navigate when reading it for the first |
72 | web page you might find easier to navigate when reading it for the first |
69 | time: L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod>. |
73 | time: L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod>. |
|
|
74 | |
|
|
75 | While this document tries to be as complete as possible in documenting |
|
|
76 | libev, its usage and the rationale behind its design, it is not a tutorial |
|
|
77 | on event-based programming, nor will it introduce event-based programming |
|
|
78 | with libev. |
|
|
79 | |
|
|
80 | Familarity with event based programming techniques in general is assumed |
|
|
81 | throughout this document. |
|
|
82 | |
|
|
83 | =head1 ABOUT LIBEV |
70 | |
84 | |
71 | Libev is an event loop: you register interest in certain events (such as a |
85 | Libev is an event loop: you register interest in certain events (such as a |
72 | file descriptor being readable or a timeout occurring), and it will manage |
86 | file descriptor being readable or a timeout occurring), and it will manage |
73 | these event sources and provide your program with events. |
87 | these event sources and provide your program with events. |
74 | |
88 | |
… | |
… | |
103 | Libev is very configurable. In this manual the default (and most common) |
117 | Libev is very configurable. In this manual the default (and most common) |
104 | configuration will be described, which supports multiple event loops. For |
118 | configuration will be described, which supports multiple event loops. For |
105 | more info about various configuration options please have a look at |
119 | more info about various configuration options please have a look at |
106 | B<EMBED> section in this manual. If libev was configured without support |
120 | B<EMBED> section in this manual. If libev was configured without support |
107 | for multiple event loops, then all functions taking an initial argument of |
121 | for multiple event loops, then all functions taking an initial argument of |
108 | name C<loop> (which is always of type C<struct ev_loop *>) will not have |
122 | name C<loop> (which is always of type C<ev_loop *>) will not have |
109 | this argument. |
123 | this argument. |
110 | |
124 | |
111 | =head2 TIME REPRESENTATION |
125 | =head2 TIME REPRESENTATION |
112 | |
126 | |
113 | Libev represents time as a single floating point number, representing the |
127 | Libev represents time as a single floating point number, representing |
114 | (fractional) number of seconds since the (POSIX) epoch (somewhere near |
128 | the (fractional) number of seconds since the (POSIX) epoch (somewhere |
115 | the beginning of 1970, details are complicated, don't ask). This type is |
129 | near the beginning of 1970, details are complicated, don't ask). This |
116 | called C<ev_tstamp>, which is what you should use too. It usually aliases |
130 | type is called C<ev_tstamp>, which is what you should use too. It usually |
117 | to the C<double> type in C, and when you need to do any calculations on |
131 | aliases to the C<double> type in C. When you need to do any calculations |
118 | it, you should treat it as some floating point value. Unlike the name |
132 | on it, you should treat it as some floating point value. Unlike the name |
119 | component C<stamp> might indicate, it is also used for time differences |
133 | component C<stamp> might indicate, it is also used for time differences |
120 | throughout libev. |
134 | throughout libev. |
121 | |
135 | |
122 | =head1 ERROR HANDLING |
136 | =head1 ERROR HANDLING |
123 | |
137 | |
… | |
… | |
276 | |
290 | |
277 | =back |
291 | =back |
278 | |
292 | |
279 | =head1 FUNCTIONS CONTROLLING THE EVENT LOOP |
293 | =head1 FUNCTIONS CONTROLLING THE EVENT LOOP |
280 | |
294 | |
281 | An event loop is described by a C<struct ev_loop *>. The library knows two |
295 | An event loop is described by a C<struct ev_loop *> (the C<struct> |
282 | types of such loops, the I<default> loop, which supports signals and child |
296 | is I<not> optional in this case, as there is also an C<ev_loop> |
283 | events, and dynamically created loops which do not. |
297 | I<function>). |
|
|
298 | |
|
|
299 | The library knows two types of such loops, the I<default> loop, which |
|
|
300 | supports signals and child events, and dynamically created loops which do |
|
|
301 | not. |
284 | |
302 | |
285 | =over 4 |
303 | =over 4 |
286 | |
304 | |
287 | =item struct ev_loop *ev_default_loop (unsigned int flags) |
305 | =item struct ev_loop *ev_default_loop (unsigned int flags) |
288 | |
306 | |
… | |
… | |
294 | If you don't know what event loop to use, use the one returned from this |
312 | If you don't know what event loop to use, use the one returned from this |
295 | function. |
313 | function. |
296 | |
314 | |
297 | Note that this function is I<not> thread-safe, so if you want to use it |
315 | Note that this function is I<not> thread-safe, so if you want to use it |
298 | from multiple threads, you have to lock (note also that this is unlikely, |
316 | from multiple threads, you have to lock (note also that this is unlikely, |
299 | as loops cannot bes hared easily between threads anyway). |
317 | as loops cannot be shared easily between threads anyway). |
300 | |
318 | |
301 | The default loop is the only loop that can handle C<ev_signal> and |
319 | The default loop is the only loop that can handle C<ev_signal> and |
302 | C<ev_child> watchers, and to do this, it always registers a handler |
320 | C<ev_child> watchers, and to do this, it always registers a handler |
303 | for C<SIGCHLD>. If this is a problem for your application you can either |
321 | for C<SIGCHLD>. If this is a problem for your application you can either |
304 | create a dynamic loop with C<ev_loop_new> that doesn't do that, or you |
322 | create a dynamic loop with C<ev_loop_new> that doesn't do that, or you |
… | |
… | |
380 | =item C<EVBACKEND_EPOLL> (value 4, Linux) |
398 | =item C<EVBACKEND_EPOLL> (value 4, Linux) |
381 | |
399 | |
382 | For few fds, this backend is a bit little slower than poll and select, |
400 | For few fds, this backend is a bit little slower than poll and select, |
383 | but it scales phenomenally better. While poll and select usually scale |
401 | but it scales phenomenally better. While poll and select usually scale |
384 | like O(total_fds) where n is the total number of fds (or the highest fd), |
402 | like O(total_fds) where n is the total number of fds (or the highest fd), |
385 | epoll scales either O(1) or O(active_fds). The epoll design has a number |
403 | epoll scales either O(1) or O(active_fds). |
386 | of shortcomings, such as silently dropping events in some hard-to-detect |
404 | |
387 | cases and requiring a system call per fd change, no fork support and bad |
405 | The epoll mechanism deserves honorable mention as the most misdesigned |
388 | support for dup. |
406 | of the more advanced event mechanisms: mere annoyances include silently |
|
|
407 | dropping file descriptors, requiring a system call per change per file |
|
|
408 | descriptor (and unnecessary guessing of parameters), problems with dup and |
|
|
409 | so on. The biggest issue is fork races, however - if a program forks then |
|
|
410 | I<both> parent and child process have to recreate the epoll set, which can |
|
|
411 | take considerable time (one syscall per file descriptor) and is of course |
|
|
412 | hard to detect. |
|
|
413 | |
|
|
414 | Epoll is also notoriously buggy - embedding epoll fds I<should> work, but |
|
|
415 | of course I<doesn't>, and epoll just loves to report events for totally |
|
|
416 | I<different> file descriptors (even already closed ones, so one cannot |
|
|
417 | even remove them from the set) than registered in the set (especially |
|
|
418 | on SMP systems). Libev tries to counter these spurious notifications by |
|
|
419 | employing an additional generation counter and comparing that against the |
|
|
420 | events to filter out spurious ones, recreating the set when required. |
389 | |
421 | |
390 | While stopping, setting and starting an I/O watcher in the same iteration |
422 | While stopping, setting and starting an I/O watcher in the same iteration |
391 | will result in some caching, there is still a system call per such incident |
423 | will result in some caching, there is still a system call per such |
392 | (because the fd could point to a different file description now), so its |
424 | incident (because the same I<file descriptor> could point to a different |
393 | best to avoid that. Also, C<dup ()>'ed file descriptors might not work |
425 | I<file description> now), so its best to avoid that. Also, C<dup ()>'ed |
394 | very well if you register events for both fds. |
426 | file descriptors might not work very well if you register events for both |
395 | |
427 | file descriptors. |
396 | Please note that epoll sometimes generates spurious notifications, so you |
|
|
397 | need to use non-blocking I/O or other means to avoid blocking when no data |
|
|
398 | (or space) is available. |
|
|
399 | |
428 | |
400 | Best performance from this backend is achieved by not unregistering all |
429 | Best performance from this backend is achieved by not unregistering all |
401 | watchers for a file descriptor until it has been closed, if possible, |
430 | watchers for a file descriptor until it has been closed, if possible, |
402 | i.e. keep at least one watcher active per fd at all times. Stopping and |
431 | i.e. keep at least one watcher active per fd at all times. Stopping and |
403 | starting a watcher (without re-setting it) also usually doesn't cause |
432 | starting a watcher (without re-setting it) also usually doesn't cause |
404 | extra overhead. |
433 | extra overhead. A fork can both result in spurious notifications as well |
|
|
434 | as in libev having to destroy and recreate the epoll object, which can |
|
|
435 | take considerable time and thus should be avoided. |
|
|
436 | |
|
|
437 | All this means that, in practice, C<EVBACKEND_SELECT> can be as fast or |
|
|
438 | faster than epoll for maybe up to a hundred file descriptors, depending on |
|
|
439 | the usage. So sad. |
405 | |
440 | |
406 | While nominally embeddable in other event loops, this feature is broken in |
441 | While nominally embeddable in other event loops, this feature is broken in |
407 | all kernel versions tested so far. |
442 | all kernel versions tested so far. |
408 | |
443 | |
409 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
444 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
410 | C<EVBACKEND_POLL>. |
445 | C<EVBACKEND_POLL>. |
411 | |
446 | |
412 | =item C<EVBACKEND_KQUEUE> (value 8, most BSD clones) |
447 | =item C<EVBACKEND_KQUEUE> (value 8, most BSD clones) |
413 | |
448 | |
414 | Kqueue deserves special mention, as at the time of this writing, it was |
449 | Kqueue deserves special mention, as at the time of this writing, it |
415 | broken on all BSDs except NetBSD (usually it doesn't work reliably with |
450 | was broken on all BSDs except NetBSD (usually it doesn't work reliably |
416 | anything but sockets and pipes, except on Darwin, where of course it's |
451 | with anything but sockets and pipes, except on Darwin, where of course |
417 | completely useless). For this reason it's not being "auto-detected" unless |
452 | it's completely useless). Unlike epoll, however, whose brokenness |
418 | you explicitly specify it in the flags (i.e. using C<EVBACKEND_KQUEUE>) or |
453 | is by design, these kqueue bugs can (and eventually will) be fixed |
419 | libev was compiled on a known-to-be-good (-enough) system like NetBSD. |
454 | without API changes to existing programs. For this reason it's not being |
|
|
455 | "auto-detected" unless you explicitly specify it in the flags (i.e. using |
|
|
456 | C<EVBACKEND_KQUEUE>) or libev was compiled on a known-to-be-good (-enough) |
|
|
457 | system like NetBSD. |
420 | |
458 | |
421 | You still can embed kqueue into a normal poll or select backend and use it |
459 | You still can embed kqueue into a normal poll or select backend and use it |
422 | only for sockets (after having made sure that sockets work with kqueue on |
460 | only for sockets (after having made sure that sockets work with kqueue on |
423 | the target platform). See C<ev_embed> watchers for more info. |
461 | the target platform). See C<ev_embed> watchers for more info. |
424 | |
462 | |
425 | It scales in the same way as the epoll backend, but the interface to the |
463 | It scales in the same way as the epoll backend, but the interface to the |
426 | kernel is more efficient (which says nothing about its actual speed, of |
464 | kernel is more efficient (which says nothing about its actual speed, of |
427 | course). While stopping, setting and starting an I/O watcher does never |
465 | course). While stopping, setting and starting an I/O watcher does never |
428 | cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to |
466 | cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to |
429 | two event changes per incident. Support for C<fork ()> is very bad and it |
467 | two event changes per incident. Support for C<fork ()> is very bad (but |
430 | drops fds silently in similarly hard-to-detect cases. |
468 | sane, unlike epoll) and it drops fds silently in similarly hard-to-detect |
|
|
469 | cases |
431 | |
470 | |
432 | This backend usually performs well under most conditions. |
471 | This backend usually performs well under most conditions. |
433 | |
472 | |
434 | While nominally embeddable in other event loops, this doesn't work |
473 | While nominally embeddable in other event loops, this doesn't work |
435 | everywhere, so you might need to test for this. And since it is broken |
474 | everywhere, so you might need to test for this. And since it is broken |
436 | almost everywhere, you should only use it when you have a lot of sockets |
475 | almost everywhere, you should only use it when you have a lot of sockets |
437 | (for which it usually works), by embedding it into another event loop |
476 | (for which it usually works), by embedding it into another event loop |
438 | (e.g. C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>) and, did I mention it, |
477 | (e.g. C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> (but C<poll> is of course |
439 | using it only for sockets. |
478 | also broken on OS X)) and, did I mention it, using it only for sockets. |
440 | |
479 | |
441 | This backend maps C<EV_READ> into an C<EVFILT_READ> kevent with |
480 | This backend maps C<EV_READ> into an C<EVFILT_READ> kevent with |
442 | C<NOTE_EOF>, and C<EV_WRITE> into an C<EVFILT_WRITE> kevent with |
481 | C<NOTE_EOF>, and C<EV_WRITE> into an C<EVFILT_WRITE> kevent with |
443 | C<NOTE_EOF>. |
482 | C<NOTE_EOF>. |
444 | |
483 | |
… | |
… | |
464 | might perform better. |
503 | might perform better. |
465 | |
504 | |
466 | On the positive side, with the exception of the spurious readiness |
505 | On the positive side, with the exception of the spurious readiness |
467 | notifications, this backend actually performed fully to specification |
506 | notifications, this backend actually performed fully to specification |
468 | in all tests and is fully embeddable, which is a rare feat among the |
507 | in all tests and is fully embeddable, which is a rare feat among the |
469 | OS-specific backends. |
508 | OS-specific backends (I vastly prefer correctness over speed hacks). |
470 | |
509 | |
471 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
510 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
472 | C<EVBACKEND_POLL>. |
511 | C<EVBACKEND_POLL>. |
473 | |
512 | |
474 | =item C<EVBACKEND_ALL> |
513 | =item C<EVBACKEND_ALL> |
… | |
… | |
527 | responsibility to either stop all watchers cleanly yourself I<before> |
566 | responsibility to either stop all watchers cleanly yourself I<before> |
528 | calling this function, or cope with the fact afterwards (which is usually |
567 | calling this function, or cope with the fact afterwards (which is usually |
529 | the easiest thing, you can just ignore the watchers and/or C<free ()> them |
568 | the easiest thing, you can just ignore the watchers and/or C<free ()> them |
530 | for example). |
569 | for example). |
531 | |
570 | |
532 | Note that certain global state, such as signal state, will not be freed by |
571 | Note that certain global state, such as signal state (and installed signal |
533 | this function, and related watchers (such as signal and child watchers) |
572 | handlers), will not be freed by this function, and related watchers (such |
534 | would need to be stopped manually. |
573 | as signal and child watchers) would need to be stopped manually. |
535 | |
574 | |
536 | In general it is not advisable to call this function except in the |
575 | In general it is not advisable to call this function except in the |
537 | rare occasion where you really need to free e.g. the signal handling |
576 | rare occasion where you really need to free e.g. the signal handling |
538 | pipe fds. If you need dynamically allocated loops it is better to use |
577 | pipe fds. If you need dynamically allocated loops it is better to use |
539 | C<ev_loop_new> and C<ev_loop_destroy>). |
578 | C<ev_loop_new> and C<ev_loop_destroy>). |
… | |
… | |
605 | |
644 | |
606 | This function is rarely useful, but when some event callback runs for a |
645 | This function is rarely useful, but when some event callback runs for a |
607 | very long time without entering the event loop, updating libev's idea of |
646 | very long time without entering the event loop, updating libev's idea of |
608 | the current time is a good idea. |
647 | the current time is a good idea. |
609 | |
648 | |
610 | See also "The special problem of time updates" in the C<ev_timer> section. |
649 | See also L<The special problem of time updates> in the C<ev_timer> section. |
|
|
650 | |
|
|
651 | =item ev_suspend (loop) |
|
|
652 | |
|
|
653 | =item ev_resume (loop) |
|
|
654 | |
|
|
655 | These two functions suspend and resume a loop, for use when the loop is |
|
|
656 | not used for a while and timeouts should not be processed. |
|
|
657 | |
|
|
658 | A typical use case would be an interactive program such as a game: When |
|
|
659 | the user presses C<^Z> to suspend the game and resumes it an hour later it |
|
|
660 | would be best to handle timeouts as if no time had actually passed while |
|
|
661 | the program was suspended. This can be achieved by calling C<ev_suspend> |
|
|
662 | in your C<SIGTSTP> handler, sending yourself a C<SIGSTOP> and calling |
|
|
663 | C<ev_resume> directly afterwards to resume timer processing. |
|
|
664 | |
|
|
665 | Effectively, all C<ev_timer> watchers will be delayed by the time spend |
|
|
666 | between C<ev_suspend> and C<ev_resume>, and all C<ev_periodic> watchers |
|
|
667 | will be rescheduled (that is, they will lose any events that would have |
|
|
668 | occured while suspended). |
|
|
669 | |
|
|
670 | After calling C<ev_suspend> you B<must not> call I<any> function on the |
|
|
671 | given loop other than C<ev_resume>, and you B<must not> call C<ev_resume> |
|
|
672 | without a previous call to C<ev_suspend>. |
|
|
673 | |
|
|
674 | Calling C<ev_suspend>/C<ev_resume> has the side effect of updating the |
|
|
675 | event loop time (see C<ev_now_update>). |
611 | |
676 | |
612 | =item ev_loop (loop, int flags) |
677 | =item ev_loop (loop, int flags) |
613 | |
678 | |
614 | Finally, this is it, the event handler. This function usually is called |
679 | Finally, this is it, the event handler. This function usually is called |
615 | after you initialised all your watchers and you want to start handling |
680 | after you initialised all your watchers and you want to start handling |
… | |
… | |
631 | the loop. |
696 | the loop. |
632 | |
697 | |
633 | A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if |
698 | A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if |
634 | necessary) and will handle those and any already outstanding ones. It |
699 | necessary) and will handle those and any already outstanding ones. It |
635 | will block your process until at least one new event arrives (which could |
700 | will block your process until at least one new event arrives (which could |
636 | be an event internal to libev itself, so there is no guarentee that a |
701 | be an event internal to libev itself, so there is no guarantee that a |
637 | user-registered callback will be called), and will return after one |
702 | user-registered callback will be called), and will return after one |
638 | iteration of the loop. |
703 | iteration of the loop. |
639 | |
704 | |
640 | This is useful if you are waiting for some external event in conjunction |
705 | This is useful if you are waiting for some external event in conjunction |
641 | with something not expressible using other libev watchers (i.e. "roll your |
706 | with something not expressible using other libev watchers (i.e. "roll your |
… | |
… | |
685 | C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or |
750 | C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or |
686 | C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return. |
751 | C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return. |
687 | |
752 | |
688 | This "unloop state" will be cleared when entering C<ev_loop> again. |
753 | This "unloop state" will be cleared when entering C<ev_loop> again. |
689 | |
754 | |
|
|
755 | It is safe to call C<ev_unloop> from otuside any C<ev_loop> calls. |
|
|
756 | |
690 | =item ev_ref (loop) |
757 | =item ev_ref (loop) |
691 | |
758 | |
692 | =item ev_unref (loop) |
759 | =item ev_unref (loop) |
693 | |
760 | |
694 | Ref/unref can be used to add or remove a reference count on the event |
761 | Ref/unref can be used to add or remove a reference count on the event |
… | |
… | |
697 | |
764 | |
698 | If you have a watcher you never unregister that should not keep C<ev_loop> |
765 | If you have a watcher you never unregister that should not keep C<ev_loop> |
699 | from returning, call ev_unref() after starting, and ev_ref() before |
766 | from returning, call ev_unref() after starting, and ev_ref() before |
700 | stopping it. |
767 | stopping it. |
701 | |
768 | |
702 | As an example, libev itself uses this for its internal signal pipe: It is |
769 | As an example, libev itself uses this for its internal signal pipe: It |
703 | not visible to the libev user and should not keep C<ev_loop> from exiting |
770 | is not visible to the libev user and should not keep C<ev_loop> from |
704 | if no event watchers registered by it are active. It is also an excellent |
771 | exiting if no event watchers registered by it are active. It is also an |
705 | way to do this for generic recurring timers or from within third-party |
772 | excellent way to do this for generic recurring timers or from within |
706 | libraries. Just remember to I<unref after start> and I<ref before stop> |
773 | third-party libraries. Just remember to I<unref after start> and I<ref |
707 | (but only if the watcher wasn't active before, or was active before, |
774 | before stop> (but only if the watcher wasn't active before, or was active |
708 | respectively). |
775 | before, respectively. Note also that libev might stop watchers itself |
|
|
776 | (e.g. non-repeating timers) in which case you have to C<ev_ref> |
|
|
777 | in the callback). |
709 | |
778 | |
710 | Example: Create a signal watcher, but keep it from keeping C<ev_loop> |
779 | Example: Create a signal watcher, but keep it from keeping C<ev_loop> |
711 | running when nothing else is active. |
780 | running when nothing else is active. |
712 | |
781 | |
713 | struct ev_signal exitsig; |
782 | ev_signal exitsig; |
714 | ev_signal_init (&exitsig, sig_cb, SIGINT); |
783 | ev_signal_init (&exitsig, sig_cb, SIGINT); |
715 | ev_signal_start (loop, &exitsig); |
784 | ev_signal_start (loop, &exitsig); |
716 | evf_unref (loop); |
785 | evf_unref (loop); |
717 | |
786 | |
718 | Example: For some weird reason, unregister the above signal handler again. |
787 | Example: For some weird reason, unregister the above signal handler again. |
… | |
… | |
766 | they fire on, say, one-second boundaries only. |
835 | they fire on, say, one-second boundaries only. |
767 | |
836 | |
768 | =item ev_loop_verify (loop) |
837 | =item ev_loop_verify (loop) |
769 | |
838 | |
770 | This function only does something when C<EV_VERIFY> support has been |
839 | This function only does something when C<EV_VERIFY> support has been |
771 | compiled in. which is the default for non-minimal builds. It tries to go |
840 | compiled in, which is the default for non-minimal builds. It tries to go |
772 | through all internal structures and checks them for validity. If anything |
841 | through all internal structures and checks them for validity. If anything |
773 | is found to be inconsistent, it will print an error message to standard |
842 | is found to be inconsistent, it will print an error message to standard |
774 | error and call C<abort ()>. |
843 | error and call C<abort ()>. |
775 | |
844 | |
776 | This can be used to catch bugs inside libev itself: under normal |
845 | This can be used to catch bugs inside libev itself: under normal |
… | |
… | |
780 | =back |
849 | =back |
781 | |
850 | |
782 | |
851 | |
783 | =head1 ANATOMY OF A WATCHER |
852 | =head1 ANATOMY OF A WATCHER |
784 | |
853 | |
|
|
854 | In the following description, uppercase C<TYPE> in names stands for the |
|
|
855 | watcher type, e.g. C<ev_TYPE_start> can mean C<ev_timer_start> for timer |
|
|
856 | watchers and C<ev_io_start> for I/O watchers. |
|
|
857 | |
785 | A watcher is a structure that you create and register to record your |
858 | A watcher is a structure that you create and register to record your |
786 | interest in some event. For instance, if you want to wait for STDIN to |
859 | interest in some event. For instance, if you want to wait for STDIN to |
787 | become readable, you would create an C<ev_io> watcher for that: |
860 | become readable, you would create an C<ev_io> watcher for that: |
788 | |
861 | |
789 | static void my_cb (struct ev_loop *loop, struct ev_io *w, int revents) |
862 | static void my_cb (struct ev_loop *loop, ev_io *w, int revents) |
790 | { |
863 | { |
791 | ev_io_stop (w); |
864 | ev_io_stop (w); |
792 | ev_unloop (loop, EVUNLOOP_ALL); |
865 | ev_unloop (loop, EVUNLOOP_ALL); |
793 | } |
866 | } |
794 | |
867 | |
795 | struct ev_loop *loop = ev_default_loop (0); |
868 | struct ev_loop *loop = ev_default_loop (0); |
|
|
869 | |
796 | struct ev_io stdin_watcher; |
870 | ev_io stdin_watcher; |
|
|
871 | |
797 | ev_init (&stdin_watcher, my_cb); |
872 | ev_init (&stdin_watcher, my_cb); |
798 | ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ); |
873 | ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ); |
799 | ev_io_start (loop, &stdin_watcher); |
874 | ev_io_start (loop, &stdin_watcher); |
|
|
875 | |
800 | ev_loop (loop, 0); |
876 | ev_loop (loop, 0); |
801 | |
877 | |
802 | As you can see, you are responsible for allocating the memory for your |
878 | As you can see, you are responsible for allocating the memory for your |
803 | watcher structures (and it is usually a bad idea to do this on the stack, |
879 | watcher structures (and it is I<usually> a bad idea to do this on the |
804 | although this can sometimes be quite valid). |
880 | stack). |
|
|
881 | |
|
|
882 | Each watcher has an associated watcher structure (called C<struct ev_TYPE> |
|
|
883 | or simply C<ev_TYPE>, as typedefs are provided for all watcher structs). |
805 | |
884 | |
806 | Each watcher structure must be initialised by a call to C<ev_init |
885 | Each watcher structure must be initialised by a call to C<ev_init |
807 | (watcher *, callback)>, which expects a callback to be provided. This |
886 | (watcher *, callback)>, which expects a callback to be provided. This |
808 | callback gets invoked each time the event occurs (or, in the case of I/O |
887 | callback gets invoked each time the event occurs (or, in the case of I/O |
809 | watchers, each time the event loop detects that the file descriptor given |
888 | watchers, each time the event loop detects that the file descriptor given |
810 | is readable and/or writable). |
889 | is readable and/or writable). |
811 | |
890 | |
812 | Each watcher type has its own C<< ev_<type>_set (watcher *, ...) >> macro |
891 | Each watcher type further has its own C<< ev_TYPE_set (watcher *, ...) >> |
813 | with arguments specific to this watcher type. There is also a macro |
892 | macro to configure it, with arguments specific to the watcher type. There |
814 | to combine initialisation and setting in one call: C<< ev_<type>_init |
893 | is also a macro to combine initialisation and setting in one call: C<< |
815 | (watcher *, callback, ...) >>. |
894 | ev_TYPE_init (watcher *, callback, ...) >>. |
816 | |
895 | |
817 | To make the watcher actually watch out for events, you have to start it |
896 | To make the watcher actually watch out for events, you have to start it |
818 | with a watcher-specific start function (C<< ev_<type>_start (loop, watcher |
897 | with a watcher-specific start function (C<< ev_TYPE_start (loop, watcher |
819 | *) >>), and you can stop watching for events at any time by calling the |
898 | *) >>), and you can stop watching for events at any time by calling the |
820 | corresponding stop function (C<< ev_<type>_stop (loop, watcher *) >>. |
899 | corresponding stop function (C<< ev_TYPE_stop (loop, watcher *) >>. |
821 | |
900 | |
822 | As long as your watcher is active (has been started but not stopped) you |
901 | As long as your watcher is active (has been started but not stopped) you |
823 | must not touch the values stored in it. Most specifically you must never |
902 | must not touch the values stored in it. Most specifically you must never |
824 | reinitialise it or call its C<set> macro. |
903 | reinitialise it or call its C<ev_TYPE_set> macro. |
825 | |
904 | |
826 | Each and every callback receives the event loop pointer as first, the |
905 | Each and every callback receives the event loop pointer as first, the |
827 | registered watcher structure as second, and a bitset of received events as |
906 | registered watcher structure as second, and a bitset of received events as |
828 | third argument. |
907 | third argument. |
829 | |
908 | |
… | |
… | |
887 | |
966 | |
888 | =item C<EV_ASYNC> |
967 | =item C<EV_ASYNC> |
889 | |
968 | |
890 | The given async watcher has been asynchronously notified (see C<ev_async>). |
969 | The given async watcher has been asynchronously notified (see C<ev_async>). |
891 | |
970 | |
|
|
971 | =item C<EV_CUSTOM> |
|
|
972 | |
|
|
973 | Not ever sent (or otherwise used) by libev itself, but can be freely used |
|
|
974 | by libev users to signal watchers (e.g. via C<ev_feed_event>). |
|
|
975 | |
892 | =item C<EV_ERROR> |
976 | =item C<EV_ERROR> |
893 | |
977 | |
894 | An unspecified error has occurred, the watcher has been stopped. This might |
978 | An unspecified error has occurred, the watcher has been stopped. This might |
895 | happen because the watcher could not be properly started because libev |
979 | happen because the watcher could not be properly started because libev |
896 | ran out of memory, a file descriptor was found to be closed or any other |
980 | ran out of memory, a file descriptor was found to be closed or any other |
|
|
981 | problem. Libev considers these application bugs. |
|
|
982 | |
897 | problem. You best act on it by reporting the problem and somehow coping |
983 | You best act on it by reporting the problem and somehow coping with the |
898 | with the watcher being stopped. |
984 | watcher being stopped. Note that well-written programs should not receive |
|
|
985 | an error ever, so when your watcher receives it, this usually indicates a |
|
|
986 | bug in your program. |
899 | |
987 | |
900 | Libev will usually signal a few "dummy" events together with an error, for |
988 | Libev will usually signal a few "dummy" events together with an error, for |
901 | example it might indicate that a fd is readable or writable, and if your |
989 | example it might indicate that a fd is readable or writable, and if your |
902 | callbacks is well-written it can just attempt the operation and cope with |
990 | callbacks is well-written it can just attempt the operation and cope with |
903 | the error from read() or write(). This will not work in multi-threaded |
991 | the error from read() or write(). This will not work in multi-threaded |
… | |
… | |
906 | |
994 | |
907 | =back |
995 | =back |
908 | |
996 | |
909 | =head2 GENERIC WATCHER FUNCTIONS |
997 | =head2 GENERIC WATCHER FUNCTIONS |
910 | |
998 | |
911 | In the following description, C<TYPE> stands for the watcher type, |
|
|
912 | e.g. C<timer> for C<ev_timer> watchers and C<io> for C<ev_io> watchers. |
|
|
913 | |
|
|
914 | =over 4 |
999 | =over 4 |
915 | |
1000 | |
916 | =item C<ev_init> (ev_TYPE *watcher, callback) |
1001 | =item C<ev_init> (ev_TYPE *watcher, callback) |
917 | |
1002 | |
918 | This macro initialises the generic portion of a watcher. The contents |
1003 | This macro initialises the generic portion of a watcher. The contents |
… | |
… | |
923 | which rolls both calls into one. |
1008 | which rolls both calls into one. |
924 | |
1009 | |
925 | You can reinitialise a watcher at any time as long as it has been stopped |
1010 | You can reinitialise a watcher at any time as long as it has been stopped |
926 | (or never started) and there are no pending events outstanding. |
1011 | (or never started) and there are no pending events outstanding. |
927 | |
1012 | |
928 | The callback is always of type C<void (*)(ev_loop *loop, ev_TYPE *watcher, |
1013 | The callback is always of type C<void (*)(struct ev_loop *loop, ev_TYPE *watcher, |
929 | int revents)>. |
1014 | int revents)>. |
930 | |
1015 | |
931 | Example: Initialise an C<ev_io> watcher in two steps. |
1016 | Example: Initialise an C<ev_io> watcher in two steps. |
932 | |
1017 | |
933 | ev_io w; |
1018 | ev_io w; |
… | |
… | |
967 | |
1052 | |
968 | ev_io_start (EV_DEFAULT_UC, &w); |
1053 | ev_io_start (EV_DEFAULT_UC, &w); |
969 | |
1054 | |
970 | =item C<ev_TYPE_stop> (loop *, ev_TYPE *watcher) |
1055 | =item C<ev_TYPE_stop> (loop *, ev_TYPE *watcher) |
971 | |
1056 | |
972 | Stops the given watcher again (if active) and clears the pending |
1057 | Stops the given watcher if active, and clears the pending status (whether |
|
|
1058 | the watcher was active or not). |
|
|
1059 | |
973 | status. It is possible that stopped watchers are pending (for example, |
1060 | It is possible that stopped watchers are pending - for example, |
974 | non-repeating timers are being stopped when they become pending), but |
1061 | non-repeating timers are being stopped when they become pending - but |
975 | C<ev_TYPE_stop> ensures that the watcher is neither active nor pending. If |
1062 | calling C<ev_TYPE_stop> ensures that the watcher is neither active nor |
976 | you want to free or reuse the memory used by the watcher it is therefore a |
1063 | pending. If you want to free or reuse the memory used by the watcher it is |
977 | good idea to always call its C<ev_TYPE_stop> function. |
1064 | therefore a good idea to always call its C<ev_TYPE_stop> function. |
978 | |
1065 | |
979 | =item bool ev_is_active (ev_TYPE *watcher) |
1066 | =item bool ev_is_active (ev_TYPE *watcher) |
980 | |
1067 | |
981 | Returns a true value iff the watcher is active (i.e. it has been started |
1068 | Returns a true value iff the watcher is active (i.e. it has been started |
982 | and not yet been stopped). As long as a watcher is active you must not modify |
1069 | and not yet been stopped). As long as a watcher is active you must not modify |
… | |
… | |
1008 | integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI> |
1095 | integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI> |
1009 | (default: C<-2>). Pending watchers with higher priority will be invoked |
1096 | (default: C<-2>). Pending watchers with higher priority will be invoked |
1010 | before watchers with lower priority, but priority will not keep watchers |
1097 | before watchers with lower priority, but priority will not keep watchers |
1011 | from being executed (except for C<ev_idle> watchers). |
1098 | from being executed (except for C<ev_idle> watchers). |
1012 | |
1099 | |
1013 | This means that priorities are I<only> used for ordering callback |
|
|
1014 | invocation after new events have been received. This is useful, for |
|
|
1015 | example, to reduce latency after idling, or more often, to bind two |
|
|
1016 | watchers on the same event and make sure one is called first. |
|
|
1017 | |
|
|
1018 | If you need to suppress invocation when higher priority events are pending |
1100 | If you need to suppress invocation when higher priority events are pending |
1019 | you need to look at C<ev_idle> watchers, which provide this functionality. |
1101 | you need to look at C<ev_idle> watchers, which provide this functionality. |
1020 | |
1102 | |
1021 | You I<must not> change the priority of a watcher as long as it is active or |
1103 | You I<must not> change the priority of a watcher as long as it is active or |
1022 | pending. |
1104 | pending. |
1023 | |
1105 | |
|
|
1106 | Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is |
|
|
1107 | fine, as long as you do not mind that the priority value you query might |
|
|
1108 | or might not have been clamped to the valid range. |
|
|
1109 | |
1024 | The default priority used by watchers when no priority has been set is |
1110 | The default priority used by watchers when no priority has been set is |
1025 | always C<0>, which is supposed to not be too high and not be too low :). |
1111 | always C<0>, which is supposed to not be too high and not be too low :). |
1026 | |
1112 | |
1027 | Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is |
1113 | See L<WATCHER PRIORITY MODELS>, below, for a more thorough treatment of |
1028 | fine, as long as you do not mind that the priority value you query might |
1114 | priorities. |
1029 | or might not have been adjusted to be within valid range. |
|
|
1030 | |
1115 | |
1031 | =item ev_invoke (loop, ev_TYPE *watcher, int revents) |
1116 | =item ev_invoke (loop, ev_TYPE *watcher, int revents) |
1032 | |
1117 | |
1033 | Invoke the C<watcher> with the given C<loop> and C<revents>. Neither |
1118 | Invoke the C<watcher> with the given C<loop> and C<revents>. Neither |
1034 | C<loop> nor C<revents> need to be valid as long as the watcher callback |
1119 | C<loop> nor C<revents> need to be valid as long as the watcher callback |
… | |
… | |
1056 | member, you can also "subclass" the watcher type and provide your own |
1141 | member, you can also "subclass" the watcher type and provide your own |
1057 | data: |
1142 | data: |
1058 | |
1143 | |
1059 | struct my_io |
1144 | struct my_io |
1060 | { |
1145 | { |
1061 | struct ev_io io; |
1146 | ev_io io; |
1062 | int otherfd; |
1147 | int otherfd; |
1063 | void *somedata; |
1148 | void *somedata; |
1064 | struct whatever *mostinteresting; |
1149 | struct whatever *mostinteresting; |
1065 | }; |
1150 | }; |
1066 | |
1151 | |
… | |
… | |
1069 | ev_io_init (&w.io, my_cb, fd, EV_READ); |
1154 | ev_io_init (&w.io, my_cb, fd, EV_READ); |
1070 | |
1155 | |
1071 | And since your callback will be called with a pointer to the watcher, you |
1156 | And since your callback will be called with a pointer to the watcher, you |
1072 | can cast it back to your own type: |
1157 | can cast it back to your own type: |
1073 | |
1158 | |
1074 | static void my_cb (struct ev_loop *loop, struct ev_io *w_, int revents) |
1159 | static void my_cb (struct ev_loop *loop, ev_io *w_, int revents) |
1075 | { |
1160 | { |
1076 | struct my_io *w = (struct my_io *)w_; |
1161 | struct my_io *w = (struct my_io *)w_; |
1077 | ... |
1162 | ... |
1078 | } |
1163 | } |
1079 | |
1164 | |
… | |
… | |
1097 | programmers): |
1182 | programmers): |
1098 | |
1183 | |
1099 | #include <stddef.h> |
1184 | #include <stddef.h> |
1100 | |
1185 | |
1101 | static void |
1186 | static void |
1102 | t1_cb (EV_P_ struct ev_timer *w, int revents) |
1187 | t1_cb (EV_P_ ev_timer *w, int revents) |
1103 | { |
1188 | { |
1104 | struct my_biggy big = (struct my_biggy * |
1189 | struct my_biggy big = (struct my_biggy * |
1105 | (((char *)w) - offsetof (struct my_biggy, t1)); |
1190 | (((char *)w) - offsetof (struct my_biggy, t1)); |
1106 | } |
1191 | } |
1107 | |
1192 | |
1108 | static void |
1193 | static void |
1109 | t2_cb (EV_P_ struct ev_timer *w, int revents) |
1194 | t2_cb (EV_P_ ev_timer *w, int revents) |
1110 | { |
1195 | { |
1111 | struct my_biggy big = (struct my_biggy * |
1196 | struct my_biggy big = (struct my_biggy * |
1112 | (((char *)w) - offsetof (struct my_biggy, t2)); |
1197 | (((char *)w) - offsetof (struct my_biggy, t2)); |
1113 | } |
1198 | } |
|
|
1199 | |
|
|
1200 | =head2 WATCHER PRIORITY MODELS |
|
|
1201 | |
|
|
1202 | Many event loops support I<watcher priorities>, which are usually small |
|
|
1203 | integers that influence the ordering of event callback invocation |
|
|
1204 | between watchers in some way, all else being equal. |
|
|
1205 | |
|
|
1206 | In libev, Watcher priorities can be set using C<ev_set_priority>. See its |
|
|
1207 | description for the more technical details such as the actual priority |
|
|
1208 | range. |
|
|
1209 | |
|
|
1210 | There are two common ways how these these priorities are being interpreted |
|
|
1211 | by event loops: |
|
|
1212 | |
|
|
1213 | In the more common lock-out model, higher priorities "lock out" invocation |
|
|
1214 | of lower priority watchers, which means as long as higher priority |
|
|
1215 | watchers receive events, lower priority watchers are not being invoked. |
|
|
1216 | |
|
|
1217 | The less common only-for-ordering model uses priorities solely to order |
|
|
1218 | callback invocation within a single event loop iteration: Higher priority |
|
|
1219 | watchers are invoked before lower priority ones, but they all get invoked |
|
|
1220 | before polling for new events. |
|
|
1221 | |
|
|
1222 | Libev uses the second (only-for-ordering) model for all its watchers |
|
|
1223 | except for idle watchers (which use the lock-out model). |
|
|
1224 | |
|
|
1225 | The rationale behind this is that implementing the lock-out model for |
|
|
1226 | watchers is not well supported by most kernel interfaces, and most event |
|
|
1227 | libraries will just poll for the same events again and again as long as |
|
|
1228 | their callbacks have not been executed, which is very inefficient in the |
|
|
1229 | common case of one high-priority watcher locking out a mass of lower |
|
|
1230 | priority ones. |
|
|
1231 | |
|
|
1232 | Static (ordering) priorities are most useful when you have two or more |
|
|
1233 | watchers handling the same resource: a typical usage example is having an |
|
|
1234 | C<ev_io> watcher to receive data, and an associated C<ev_timer> to handle |
|
|
1235 | timeouts. Under load, data might be received while the program handles |
|
|
1236 | other jobs, but since timers normally get invoked first, the timeout |
|
|
1237 | handler will be executed before checking for data. In that case, giving |
|
|
1238 | the timer a lower priority than the I/O watcher ensures that I/O will be |
|
|
1239 | handled first even under adverse conditions (which is usually, but not |
|
|
1240 | always, what you want). |
|
|
1241 | |
|
|
1242 | Since idle watchers use the "lock-out" model, meaning that idle watchers |
|
|
1243 | will only be executed when no same or higher priority watchers have |
|
|
1244 | received events, they can be used to implement the "lock-out" model when |
|
|
1245 | required. |
|
|
1246 | |
|
|
1247 | For example, to emulate how many other event libraries handle priorities, |
|
|
1248 | you can associate an C<ev_idle> watcher to each such watcher, and in |
|
|
1249 | the normal watcher callback, you just start the idle watcher. The real |
|
|
1250 | processing is done in the idle watcher callback. This causes libev to |
|
|
1251 | continously poll and process kernel event data for the watcher, but when |
|
|
1252 | the lock-out case is known to be rare (which in turn is rare :), this is |
|
|
1253 | workable. |
|
|
1254 | |
|
|
1255 | Usually, however, the lock-out model implemented that way will perform |
|
|
1256 | miserably under the type of load it was designed to handle. In that case, |
|
|
1257 | it might be preferable to stop the real watcher before starting the |
|
|
1258 | idle watcher, so the kernel will not have to process the event in case |
|
|
1259 | the actual processing will be delayed for considerable time. |
|
|
1260 | |
|
|
1261 | Here is an example of an I/O watcher that should run at a strictly lower |
|
|
1262 | priority than the default, and which should only process data when no |
|
|
1263 | other events are pending: |
|
|
1264 | |
|
|
1265 | ev_idle idle; // actual processing watcher |
|
|
1266 | ev_io io; // actual event watcher |
|
|
1267 | |
|
|
1268 | static void |
|
|
1269 | io_cb (EV_P_ ev_io *w, int revents) |
|
|
1270 | { |
|
|
1271 | // stop the I/O watcher, we received the event, but |
|
|
1272 | // are not yet ready to handle it. |
|
|
1273 | ev_io_stop (EV_A_ w); |
|
|
1274 | |
|
|
1275 | // start the idle watcher to ahndle the actual event. |
|
|
1276 | // it will not be executed as long as other watchers |
|
|
1277 | // with the default priority are receiving events. |
|
|
1278 | ev_idle_start (EV_A_ &idle); |
|
|
1279 | } |
|
|
1280 | |
|
|
1281 | static void |
|
|
1282 | idle-cb (EV_P_ ev_idle *w, int revents) |
|
|
1283 | { |
|
|
1284 | // actual processing |
|
|
1285 | read (STDIN_FILENO, ...); |
|
|
1286 | |
|
|
1287 | // have to start the I/O watcher again, as |
|
|
1288 | // we have handled the event |
|
|
1289 | ev_io_start (EV_P_ &io); |
|
|
1290 | } |
|
|
1291 | |
|
|
1292 | // initialisation |
|
|
1293 | ev_idle_init (&idle, idle_cb); |
|
|
1294 | ev_io_init (&io, io_cb, STDIN_FILENO, EV_READ); |
|
|
1295 | ev_io_start (EV_DEFAULT_ &io); |
|
|
1296 | |
|
|
1297 | In the "real" world, it might also be beneficial to start a timer, so that |
|
|
1298 | low-priority connections can not be locked out forever under load. This |
|
|
1299 | enables your program to keep a lower latency for important connections |
|
|
1300 | during short periods of high load, while not completely locking out less |
|
|
1301 | important ones. |
1114 | |
1302 | |
1115 | |
1303 | |
1116 | =head1 WATCHER TYPES |
1304 | =head1 WATCHER TYPES |
1117 | |
1305 | |
1118 | This section describes each watcher in detail, but will not repeat |
1306 | This section describes each watcher in detail, but will not repeat |
… | |
… | |
1144 | descriptors to non-blocking mode is also usually a good idea (but not |
1332 | descriptors to non-blocking mode is also usually a good idea (but not |
1145 | required if you know what you are doing). |
1333 | required if you know what you are doing). |
1146 | |
1334 | |
1147 | If you cannot use non-blocking mode, then force the use of a |
1335 | If you cannot use non-blocking mode, then force the use of a |
1148 | known-to-be-good backend (at the time of this writing, this includes only |
1336 | known-to-be-good backend (at the time of this writing, this includes only |
1149 | C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>). |
1337 | C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>). The same applies to file |
|
|
1338 | descriptors for which non-blocking operation makes no sense (such as |
|
|
1339 | files) - libev doesn't guarentee any specific behaviour in that case. |
1150 | |
1340 | |
1151 | Another thing you have to watch out for is that it is quite easy to |
1341 | Another thing you have to watch out for is that it is quite easy to |
1152 | receive "spurious" readiness notifications, that is your callback might |
1342 | receive "spurious" readiness notifications, that is your callback might |
1153 | be called with C<EV_READ> but a subsequent C<read>(2) will actually block |
1343 | be called with C<EV_READ> but a subsequent C<read>(2) will actually block |
1154 | because there is no data. Not only are some backends known to create a |
1344 | because there is no data. Not only are some backends known to create a |
… | |
… | |
1249 | Example: Call C<stdin_readable_cb> when STDIN_FILENO has become, well |
1439 | Example: Call C<stdin_readable_cb> when STDIN_FILENO has become, well |
1250 | readable, but only once. Since it is likely line-buffered, you could |
1440 | readable, but only once. Since it is likely line-buffered, you could |
1251 | attempt to read a whole line in the callback. |
1441 | attempt to read a whole line in the callback. |
1252 | |
1442 | |
1253 | static void |
1443 | static void |
1254 | stdin_readable_cb (struct ev_loop *loop, struct ev_io *w, int revents) |
1444 | stdin_readable_cb (struct ev_loop *loop, ev_io *w, int revents) |
1255 | { |
1445 | { |
1256 | ev_io_stop (loop, w); |
1446 | ev_io_stop (loop, w); |
1257 | .. read from stdin here (or from w->fd) and handle any I/O errors |
1447 | .. read from stdin here (or from w->fd) and handle any I/O errors |
1258 | } |
1448 | } |
1259 | |
1449 | |
1260 | ... |
1450 | ... |
1261 | struct ev_loop *loop = ev_default_init (0); |
1451 | struct ev_loop *loop = ev_default_init (0); |
1262 | struct ev_io stdin_readable; |
1452 | ev_io stdin_readable; |
1263 | ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ); |
1453 | ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ); |
1264 | ev_io_start (loop, &stdin_readable); |
1454 | ev_io_start (loop, &stdin_readable); |
1265 | ev_loop (loop, 0); |
1455 | ev_loop (loop, 0); |
1266 | |
1456 | |
1267 | |
1457 | |
… | |
… | |
1275 | year, it will still time out after (roughly) one hour. "Roughly" because |
1465 | year, it will still time out after (roughly) one hour. "Roughly" because |
1276 | detecting time jumps is hard, and some inaccuracies are unavoidable (the |
1466 | detecting time jumps is hard, and some inaccuracies are unavoidable (the |
1277 | monotonic clock option helps a lot here). |
1467 | monotonic clock option helps a lot here). |
1278 | |
1468 | |
1279 | The callback is guaranteed to be invoked only I<after> its timeout has |
1469 | The callback is guaranteed to be invoked only I<after> its timeout has |
1280 | passed, but if multiple timers become ready during the same loop iteration |
1470 | passed. If multiple timers become ready during the same loop iteration |
1281 | then order of execution is undefined. |
1471 | then the ones with earlier time-out values are invoked before ones with |
|
|
1472 | later time-out values (but this is no longer true when a callback calls |
|
|
1473 | C<ev_loop> recursively). |
|
|
1474 | |
|
|
1475 | =head3 Be smart about timeouts |
|
|
1476 | |
|
|
1477 | Many real-world problems involve some kind of timeout, usually for error |
|
|
1478 | recovery. A typical example is an HTTP request - if the other side hangs, |
|
|
1479 | you want to raise some error after a while. |
|
|
1480 | |
|
|
1481 | What follows are some ways to handle this problem, from obvious and |
|
|
1482 | inefficient to smart and efficient. |
|
|
1483 | |
|
|
1484 | In the following, a 60 second activity timeout is assumed - a timeout that |
|
|
1485 | gets reset to 60 seconds each time there is activity (e.g. each time some |
|
|
1486 | data or other life sign was received). |
|
|
1487 | |
|
|
1488 | =over 4 |
|
|
1489 | |
|
|
1490 | =item 1. Use a timer and stop, reinitialise and start it on activity. |
|
|
1491 | |
|
|
1492 | This is the most obvious, but not the most simple way: In the beginning, |
|
|
1493 | start the watcher: |
|
|
1494 | |
|
|
1495 | ev_timer_init (timer, callback, 60., 0.); |
|
|
1496 | ev_timer_start (loop, timer); |
|
|
1497 | |
|
|
1498 | Then, each time there is some activity, C<ev_timer_stop> it, initialise it |
|
|
1499 | and start it again: |
|
|
1500 | |
|
|
1501 | ev_timer_stop (loop, timer); |
|
|
1502 | ev_timer_set (timer, 60., 0.); |
|
|
1503 | ev_timer_start (loop, timer); |
|
|
1504 | |
|
|
1505 | This is relatively simple to implement, but means that each time there is |
|
|
1506 | some activity, libev will first have to remove the timer from its internal |
|
|
1507 | data structure and then add it again. Libev tries to be fast, but it's |
|
|
1508 | still not a constant-time operation. |
|
|
1509 | |
|
|
1510 | =item 2. Use a timer and re-start it with C<ev_timer_again> inactivity. |
|
|
1511 | |
|
|
1512 | This is the easiest way, and involves using C<ev_timer_again> instead of |
|
|
1513 | C<ev_timer_start>. |
|
|
1514 | |
|
|
1515 | To implement this, configure an C<ev_timer> with a C<repeat> value |
|
|
1516 | of C<60> and then call C<ev_timer_again> at start and each time you |
|
|
1517 | successfully read or write some data. If you go into an idle state where |
|
|
1518 | you do not expect data to travel on the socket, you can C<ev_timer_stop> |
|
|
1519 | the timer, and C<ev_timer_again> will automatically restart it if need be. |
|
|
1520 | |
|
|
1521 | That means you can ignore both the C<ev_timer_start> function and the |
|
|
1522 | C<after> argument to C<ev_timer_set>, and only ever use the C<repeat> |
|
|
1523 | member and C<ev_timer_again>. |
|
|
1524 | |
|
|
1525 | At start: |
|
|
1526 | |
|
|
1527 | ev_timer_init (timer, callback); |
|
|
1528 | timer->repeat = 60.; |
|
|
1529 | ev_timer_again (loop, timer); |
|
|
1530 | |
|
|
1531 | Each time there is some activity: |
|
|
1532 | |
|
|
1533 | ev_timer_again (loop, timer); |
|
|
1534 | |
|
|
1535 | It is even possible to change the time-out on the fly, regardless of |
|
|
1536 | whether the watcher is active or not: |
|
|
1537 | |
|
|
1538 | timer->repeat = 30.; |
|
|
1539 | ev_timer_again (loop, timer); |
|
|
1540 | |
|
|
1541 | This is slightly more efficient then stopping/starting the timer each time |
|
|
1542 | you want to modify its timeout value, as libev does not have to completely |
|
|
1543 | remove and re-insert the timer from/into its internal data structure. |
|
|
1544 | |
|
|
1545 | It is, however, even simpler than the "obvious" way to do it. |
|
|
1546 | |
|
|
1547 | =item 3. Let the timer time out, but then re-arm it as required. |
|
|
1548 | |
|
|
1549 | This method is more tricky, but usually most efficient: Most timeouts are |
|
|
1550 | relatively long compared to the intervals between other activity - in |
|
|
1551 | our example, within 60 seconds, there are usually many I/O events with |
|
|
1552 | associated activity resets. |
|
|
1553 | |
|
|
1554 | In this case, it would be more efficient to leave the C<ev_timer> alone, |
|
|
1555 | but remember the time of last activity, and check for a real timeout only |
|
|
1556 | within the callback: |
|
|
1557 | |
|
|
1558 | ev_tstamp last_activity; // time of last activity |
|
|
1559 | |
|
|
1560 | static void |
|
|
1561 | callback (EV_P_ ev_timer *w, int revents) |
|
|
1562 | { |
|
|
1563 | ev_tstamp now = ev_now (EV_A); |
|
|
1564 | ev_tstamp timeout = last_activity + 60.; |
|
|
1565 | |
|
|
1566 | // if last_activity + 60. is older than now, we did time out |
|
|
1567 | if (timeout < now) |
|
|
1568 | { |
|
|
1569 | // timeout occured, take action |
|
|
1570 | } |
|
|
1571 | else |
|
|
1572 | { |
|
|
1573 | // callback was invoked, but there was some activity, re-arm |
|
|
1574 | // the watcher to fire in last_activity + 60, which is |
|
|
1575 | // guaranteed to be in the future, so "again" is positive: |
|
|
1576 | w->repeat = timeout - now; |
|
|
1577 | ev_timer_again (EV_A_ w); |
|
|
1578 | } |
|
|
1579 | } |
|
|
1580 | |
|
|
1581 | To summarise the callback: first calculate the real timeout (defined |
|
|
1582 | as "60 seconds after the last activity"), then check if that time has |
|
|
1583 | been reached, which means something I<did>, in fact, time out. Otherwise |
|
|
1584 | the callback was invoked too early (C<timeout> is in the future), so |
|
|
1585 | re-schedule the timer to fire at that future time, to see if maybe we have |
|
|
1586 | a timeout then. |
|
|
1587 | |
|
|
1588 | Note how C<ev_timer_again> is used, taking advantage of the |
|
|
1589 | C<ev_timer_again> optimisation when the timer is already running. |
|
|
1590 | |
|
|
1591 | This scheme causes more callback invocations (about one every 60 seconds |
|
|
1592 | minus half the average time between activity), but virtually no calls to |
|
|
1593 | libev to change the timeout. |
|
|
1594 | |
|
|
1595 | To start the timer, simply initialise the watcher and set C<last_activity> |
|
|
1596 | to the current time (meaning we just have some activity :), then call the |
|
|
1597 | callback, which will "do the right thing" and start the timer: |
|
|
1598 | |
|
|
1599 | ev_timer_init (timer, callback); |
|
|
1600 | last_activity = ev_now (loop); |
|
|
1601 | callback (loop, timer, EV_TIMEOUT); |
|
|
1602 | |
|
|
1603 | And when there is some activity, simply store the current time in |
|
|
1604 | C<last_activity>, no libev calls at all: |
|
|
1605 | |
|
|
1606 | last_actiivty = ev_now (loop); |
|
|
1607 | |
|
|
1608 | This technique is slightly more complex, but in most cases where the |
|
|
1609 | time-out is unlikely to be triggered, much more efficient. |
|
|
1610 | |
|
|
1611 | Changing the timeout is trivial as well (if it isn't hard-coded in the |
|
|
1612 | callback :) - just change the timeout and invoke the callback, which will |
|
|
1613 | fix things for you. |
|
|
1614 | |
|
|
1615 | =item 4. Wee, just use a double-linked list for your timeouts. |
|
|
1616 | |
|
|
1617 | If there is not one request, but many thousands (millions...), all |
|
|
1618 | employing some kind of timeout with the same timeout value, then one can |
|
|
1619 | do even better: |
|
|
1620 | |
|
|
1621 | When starting the timeout, calculate the timeout value and put the timeout |
|
|
1622 | at the I<end> of the list. |
|
|
1623 | |
|
|
1624 | Then use an C<ev_timer> to fire when the timeout at the I<beginning> of |
|
|
1625 | the list is expected to fire (for example, using the technique #3). |
|
|
1626 | |
|
|
1627 | When there is some activity, remove the timer from the list, recalculate |
|
|
1628 | the timeout, append it to the end of the list again, and make sure to |
|
|
1629 | update the C<ev_timer> if it was taken from the beginning of the list. |
|
|
1630 | |
|
|
1631 | This way, one can manage an unlimited number of timeouts in O(1) time for |
|
|
1632 | starting, stopping and updating the timers, at the expense of a major |
|
|
1633 | complication, and having to use a constant timeout. The constant timeout |
|
|
1634 | ensures that the list stays sorted. |
|
|
1635 | |
|
|
1636 | =back |
|
|
1637 | |
|
|
1638 | So which method the best? |
|
|
1639 | |
|
|
1640 | Method #2 is a simple no-brain-required solution that is adequate in most |
|
|
1641 | situations. Method #3 requires a bit more thinking, but handles many cases |
|
|
1642 | better, and isn't very complicated either. In most case, choosing either |
|
|
1643 | one is fine, with #3 being better in typical situations. |
|
|
1644 | |
|
|
1645 | Method #1 is almost always a bad idea, and buys you nothing. Method #4 is |
|
|
1646 | rather complicated, but extremely efficient, something that really pays |
|
|
1647 | off after the first million or so of active timers, i.e. it's usually |
|
|
1648 | overkill :) |
1282 | |
1649 | |
1283 | =head3 The special problem of time updates |
1650 | =head3 The special problem of time updates |
1284 | |
1651 | |
1285 | Establishing the current time is a costly operation (it usually takes at |
1652 | Establishing the current time is a costly operation (it usually takes at |
1286 | least two system calls): EV therefore updates its idea of the current |
1653 | least two system calls): EV therefore updates its idea of the current |
… | |
… | |
1330 | If the timer is started but non-repeating, stop it (as if it timed out). |
1697 | If the timer is started but non-repeating, stop it (as if it timed out). |
1331 | |
1698 | |
1332 | If the timer is repeating, either start it if necessary (with the |
1699 | If the timer is repeating, either start it if necessary (with the |
1333 | C<repeat> value), or reset the running timer to the C<repeat> value. |
1700 | C<repeat> value), or reset the running timer to the C<repeat> value. |
1334 | |
1701 | |
1335 | This sounds a bit complicated, but here is a useful and typical |
1702 | This sounds a bit complicated, see L<Be smart about timeouts>, above, for a |
1336 | example: Imagine you have a TCP connection and you want a so-called idle |
1703 | usage example. |
1337 | timeout, that is, you want to be called when there have been, say, 60 |
|
|
1338 | seconds of inactivity on the socket. The easiest way to do this is to |
|
|
1339 | configure an C<ev_timer> with a C<repeat> value of C<60> and then call |
|
|
1340 | C<ev_timer_again> each time you successfully read or write some data. If |
|
|
1341 | you go into an idle state where you do not expect data to travel on the |
|
|
1342 | socket, you can C<ev_timer_stop> the timer, and C<ev_timer_again> will |
|
|
1343 | automatically restart it if need be. |
|
|
1344 | |
|
|
1345 | That means you can ignore the C<after> value and C<ev_timer_start> |
|
|
1346 | altogether and only ever use the C<repeat> value and C<ev_timer_again>: |
|
|
1347 | |
|
|
1348 | ev_timer_init (timer, callback, 0., 5.); |
|
|
1349 | ev_timer_again (loop, timer); |
|
|
1350 | ... |
|
|
1351 | timer->again = 17.; |
|
|
1352 | ev_timer_again (loop, timer); |
|
|
1353 | ... |
|
|
1354 | timer->again = 10.; |
|
|
1355 | ev_timer_again (loop, timer); |
|
|
1356 | |
|
|
1357 | This is more slightly efficient then stopping/starting the timer each time |
|
|
1358 | you want to modify its timeout value. |
|
|
1359 | |
|
|
1360 | Note, however, that it is often even more efficient to remember the |
|
|
1361 | time of the last activity and let the timer time-out naturally. In the |
|
|
1362 | callback, you then check whether the time-out is real, or, if there was |
|
|
1363 | some activity, you reschedule the watcher to time-out in "last_activity + |
|
|
1364 | timeout - ev_now ()" seconds. |
|
|
1365 | |
1704 | |
1366 | =item ev_tstamp repeat [read-write] |
1705 | =item ev_tstamp repeat [read-write] |
1367 | |
1706 | |
1368 | The current C<repeat> value. Will be used each time the watcher times out |
1707 | The current C<repeat> value. Will be used each time the watcher times out |
1369 | or C<ev_timer_again> is called, and determines the next timeout (if any), |
1708 | or C<ev_timer_again> is called, and determines the next timeout (if any), |
… | |
… | |
1374 | =head3 Examples |
1713 | =head3 Examples |
1375 | |
1714 | |
1376 | Example: Create a timer that fires after 60 seconds. |
1715 | Example: Create a timer that fires after 60 seconds. |
1377 | |
1716 | |
1378 | static void |
1717 | static void |
1379 | one_minute_cb (struct ev_loop *loop, struct ev_timer *w, int revents) |
1718 | one_minute_cb (struct ev_loop *loop, ev_timer *w, int revents) |
1380 | { |
1719 | { |
1381 | .. one minute over, w is actually stopped right here |
1720 | .. one minute over, w is actually stopped right here |
1382 | } |
1721 | } |
1383 | |
1722 | |
1384 | struct ev_timer mytimer; |
1723 | ev_timer mytimer; |
1385 | ev_timer_init (&mytimer, one_minute_cb, 60., 0.); |
1724 | ev_timer_init (&mytimer, one_minute_cb, 60., 0.); |
1386 | ev_timer_start (loop, &mytimer); |
1725 | ev_timer_start (loop, &mytimer); |
1387 | |
1726 | |
1388 | Example: Create a timeout timer that times out after 10 seconds of |
1727 | Example: Create a timeout timer that times out after 10 seconds of |
1389 | inactivity. |
1728 | inactivity. |
1390 | |
1729 | |
1391 | static void |
1730 | static void |
1392 | timeout_cb (struct ev_loop *loop, struct ev_timer *w, int revents) |
1731 | timeout_cb (struct ev_loop *loop, ev_timer *w, int revents) |
1393 | { |
1732 | { |
1394 | .. ten seconds without any activity |
1733 | .. ten seconds without any activity |
1395 | } |
1734 | } |
1396 | |
1735 | |
1397 | struct ev_timer mytimer; |
1736 | ev_timer mytimer; |
1398 | ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */ |
1737 | ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */ |
1399 | ev_timer_again (&mytimer); /* start timer */ |
1738 | ev_timer_again (&mytimer); /* start timer */ |
1400 | ev_loop (loop, 0); |
1739 | ev_loop (loop, 0); |
1401 | |
1740 | |
1402 | // and in some piece of code that gets executed on any "activity": |
1741 | // and in some piece of code that gets executed on any "activity": |
… | |
… | |
1407 | =head2 C<ev_periodic> - to cron or not to cron? |
1746 | =head2 C<ev_periodic> - to cron or not to cron? |
1408 | |
1747 | |
1409 | Periodic watchers are also timers of a kind, but they are very versatile |
1748 | Periodic watchers are also timers of a kind, but they are very versatile |
1410 | (and unfortunately a bit complex). |
1749 | (and unfortunately a bit complex). |
1411 | |
1750 | |
1412 | Unlike C<ev_timer>'s, they are not based on real time (or relative time) |
1751 | Unlike C<ev_timer>, periodic watchers are not based on real time (or |
1413 | but on wall clock time (absolute time). You can tell a periodic watcher |
1752 | relative time, the physical time that passes) but on wall clock time |
1414 | to trigger after some specific point in time. For example, if you tell a |
1753 | (absolute time, the thing you can read on your calender or clock). The |
1415 | periodic watcher to trigger in 10 seconds (by specifying e.g. C<ev_now () |
1754 | difference is that wall clock time can run faster or slower than real |
1416 | + 10.>, that is, an absolute time not a delay) and then reset your system |
1755 | time, and time jumps are not uncommon (e.g. when you adjust your |
1417 | clock to January of the previous year, then it will take more than year |
1756 | wrist-watch). |
1418 | to trigger the event (unlike an C<ev_timer>, which would still trigger |
|
|
1419 | roughly 10 seconds later as it uses a relative timeout). |
|
|
1420 | |
1757 | |
|
|
1758 | You can tell a periodic watcher to trigger after some specific point |
|
|
1759 | in time: for example, if you tell a periodic watcher to trigger "in 10 |
|
|
1760 | seconds" (by specifying e.g. C<ev_now () + 10.>, that is, an absolute time |
|
|
1761 | not a delay) and then reset your system clock to January of the previous |
|
|
1762 | year, then it will take a year or more to trigger the event (unlike an |
|
|
1763 | C<ev_timer>, which would still trigger roughly 10 seconds after starting |
|
|
1764 | it, as it uses a relative timeout). |
|
|
1765 | |
1421 | C<ev_periodic>s can also be used to implement vastly more complex timers, |
1766 | C<ev_periodic> watchers can also be used to implement vastly more complex |
1422 | such as triggering an event on each "midnight, local time", or other |
1767 | timers, such as triggering an event on each "midnight, local time", or |
1423 | complicated rules. |
1768 | other complicated rules. This cannot be done with C<ev_timer> watchers, as |
|
|
1769 | those cannot react to time jumps. |
1424 | |
1770 | |
1425 | As with timers, the callback is guaranteed to be invoked only when the |
1771 | As with timers, the callback is guaranteed to be invoked only when the |
1426 | time (C<at>) has passed, but if multiple periodic timers become ready |
1772 | point in time where it is supposed to trigger has passed. If multiple |
1427 | during the same loop iteration, then order of execution is undefined. |
1773 | timers become ready during the same loop iteration then the ones with |
|
|
1774 | earlier time-out values are invoked before ones with later time-out values |
|
|
1775 | (but this is no longer true when a callback calls C<ev_loop> recursively). |
1428 | |
1776 | |
1429 | =head3 Watcher-Specific Functions and Data Members |
1777 | =head3 Watcher-Specific Functions and Data Members |
1430 | |
1778 | |
1431 | =over 4 |
1779 | =over 4 |
1432 | |
1780 | |
1433 | =item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb) |
1781 | =item ev_periodic_init (ev_periodic *, callback, ev_tstamp offset, ev_tstamp interval, reschedule_cb) |
1434 | |
1782 | |
1435 | =item ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb) |
1783 | =item ev_periodic_set (ev_periodic *, ev_tstamp offset, ev_tstamp interval, reschedule_cb) |
1436 | |
1784 | |
1437 | Lots of arguments, lets sort it out... There are basically three modes of |
1785 | Lots of arguments, let's sort it out... There are basically three modes of |
1438 | operation, and we will explain them from simplest to most complex: |
1786 | operation, and we will explain them from simplest to most complex: |
1439 | |
1787 | |
1440 | =over 4 |
1788 | =over 4 |
1441 | |
1789 | |
1442 | =item * absolute timer (at = time, interval = reschedule_cb = 0) |
1790 | =item * absolute timer (offset = absolute time, interval = 0, reschedule_cb = 0) |
1443 | |
1791 | |
1444 | In this configuration the watcher triggers an event after the wall clock |
1792 | In this configuration the watcher triggers an event after the wall clock |
1445 | time C<at> has passed. It will not repeat and will not adjust when a time |
1793 | time C<offset> has passed. It will not repeat and will not adjust when a |
1446 | jump occurs, that is, if it is to be run at January 1st 2011 then it will |
1794 | time jump occurs, that is, if it is to be run at January 1st 2011 then it |
1447 | only run when the system clock reaches or surpasses this time. |
1795 | will be stopped and invoked when the system clock reaches or surpasses |
|
|
1796 | this point in time. |
1448 | |
1797 | |
1449 | =item * repeating interval timer (at = offset, interval > 0, reschedule_cb = 0) |
1798 | =item * repeating interval timer (offset = offset within interval, interval > 0, reschedule_cb = 0) |
1450 | |
1799 | |
1451 | In this mode the watcher will always be scheduled to time out at the next |
1800 | In this mode the watcher will always be scheduled to time out at the next |
1452 | C<at + N * interval> time (for some integer N, which can also be negative) |
1801 | C<offset + N * interval> time (for some integer N, which can also be |
1453 | and then repeat, regardless of any time jumps. |
1802 | negative) and then repeat, regardless of any time jumps. The C<offset> |
|
|
1803 | argument is merely an offset into the C<interval> periods. |
1454 | |
1804 | |
1455 | This can be used to create timers that do not drift with respect to the |
1805 | This can be used to create timers that do not drift with respect to the |
1456 | system clock, for example, here is a C<ev_periodic> that triggers each |
1806 | system clock, for example, here is an C<ev_periodic> that triggers each |
1457 | hour, on the hour: |
1807 | hour, on the hour (with respect to UTC): |
1458 | |
1808 | |
1459 | ev_periodic_set (&periodic, 0., 3600., 0); |
1809 | ev_periodic_set (&periodic, 0., 3600., 0); |
1460 | |
1810 | |
1461 | This doesn't mean there will always be 3600 seconds in between triggers, |
1811 | This doesn't mean there will always be 3600 seconds in between triggers, |
1462 | but only that the callback will be called when the system time shows a |
1812 | but only that the callback will be called when the system time shows a |
1463 | full hour (UTC), or more correctly, when the system time is evenly divisible |
1813 | full hour (UTC), or more correctly, when the system time is evenly divisible |
1464 | by 3600. |
1814 | by 3600. |
1465 | |
1815 | |
1466 | Another way to think about it (for the mathematically inclined) is that |
1816 | Another way to think about it (for the mathematically inclined) is that |
1467 | C<ev_periodic> will try to run the callback in this mode at the next possible |
1817 | C<ev_periodic> will try to run the callback in this mode at the next possible |
1468 | time where C<time = at (mod interval)>, regardless of any time jumps. |
1818 | time where C<time = offset (mod interval)>, regardless of any time jumps. |
1469 | |
1819 | |
1470 | For numerical stability it is preferable that the C<at> value is near |
1820 | For numerical stability it is preferable that the C<offset> value is near |
1471 | C<ev_now ()> (the current time), but there is no range requirement for |
1821 | C<ev_now ()> (the current time), but there is no range requirement for |
1472 | this value, and in fact is often specified as zero. |
1822 | this value, and in fact is often specified as zero. |
1473 | |
1823 | |
1474 | Note also that there is an upper limit to how often a timer can fire (CPU |
1824 | Note also that there is an upper limit to how often a timer can fire (CPU |
1475 | speed for example), so if C<interval> is very small then timing stability |
1825 | speed for example), so if C<interval> is very small then timing stability |
1476 | will of course deteriorate. Libev itself tries to be exact to be about one |
1826 | will of course deteriorate. Libev itself tries to be exact to be about one |
1477 | millisecond (if the OS supports it and the machine is fast enough). |
1827 | millisecond (if the OS supports it and the machine is fast enough). |
1478 | |
1828 | |
1479 | =item * manual reschedule mode (at and interval ignored, reschedule_cb = callback) |
1829 | =item * manual reschedule mode (offset ignored, interval ignored, reschedule_cb = callback) |
1480 | |
1830 | |
1481 | In this mode the values for C<interval> and C<at> are both being |
1831 | In this mode the values for C<interval> and C<offset> are both being |
1482 | ignored. Instead, each time the periodic watcher gets scheduled, the |
1832 | ignored. Instead, each time the periodic watcher gets scheduled, the |
1483 | reschedule callback will be called with the watcher as first, and the |
1833 | reschedule callback will be called with the watcher as first, and the |
1484 | current time as second argument. |
1834 | current time as second argument. |
1485 | |
1835 | |
1486 | NOTE: I<This callback MUST NOT stop or destroy any periodic watcher, |
1836 | NOTE: I<This callback MUST NOT stop or destroy any periodic watcher, ever, |
1487 | ever, or make ANY event loop modifications whatsoever>. |
1837 | or make ANY other event loop modifications whatsoever, unless explicitly |
|
|
1838 | allowed by documentation here>. |
1488 | |
1839 | |
1489 | If you need to stop it, return C<now + 1e30> (or so, fudge fudge) and stop |
1840 | If you need to stop it, return C<now + 1e30> (or so, fudge fudge) and stop |
1490 | it afterwards (e.g. by starting an C<ev_prepare> watcher, which is the |
1841 | it afterwards (e.g. by starting an C<ev_prepare> watcher, which is the |
1491 | only event loop modification you are allowed to do). |
1842 | only event loop modification you are allowed to do). |
1492 | |
1843 | |
1493 | The callback prototype is C<ev_tstamp (*reschedule_cb)(struct ev_periodic |
1844 | The callback prototype is C<ev_tstamp (*reschedule_cb)(ev_periodic |
1494 | *w, ev_tstamp now)>, e.g.: |
1845 | *w, ev_tstamp now)>, e.g.: |
1495 | |
1846 | |
|
|
1847 | static ev_tstamp |
1496 | static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) |
1848 | my_rescheduler (ev_periodic *w, ev_tstamp now) |
1497 | { |
1849 | { |
1498 | return now + 60.; |
1850 | return now + 60.; |
1499 | } |
1851 | } |
1500 | |
1852 | |
1501 | It must return the next time to trigger, based on the passed time value |
1853 | It must return the next time to trigger, based on the passed time value |
… | |
… | |
1521 | a different time than the last time it was called (e.g. in a crond like |
1873 | a different time than the last time it was called (e.g. in a crond like |
1522 | program when the crontabs have changed). |
1874 | program when the crontabs have changed). |
1523 | |
1875 | |
1524 | =item ev_tstamp ev_periodic_at (ev_periodic *) |
1876 | =item ev_tstamp ev_periodic_at (ev_periodic *) |
1525 | |
1877 | |
1526 | When active, returns the absolute time that the watcher is supposed to |
1878 | When active, returns the absolute time that the watcher is supposed |
1527 | trigger next. |
1879 | to trigger next. This is not the same as the C<offset> argument to |
|
|
1880 | C<ev_periodic_set>, but indeed works even in interval and manual |
|
|
1881 | rescheduling modes. |
1528 | |
1882 | |
1529 | =item ev_tstamp offset [read-write] |
1883 | =item ev_tstamp offset [read-write] |
1530 | |
1884 | |
1531 | When repeating, this contains the offset value, otherwise this is the |
1885 | When repeating, this contains the offset value, otherwise this is the |
1532 | absolute point in time (the C<at> value passed to C<ev_periodic_set>). |
1886 | absolute point in time (the C<offset> value passed to C<ev_periodic_set>, |
|
|
1887 | although libev might modify this value for better numerical stability). |
1533 | |
1888 | |
1534 | Can be modified any time, but changes only take effect when the periodic |
1889 | Can be modified any time, but changes only take effect when the periodic |
1535 | timer fires or C<ev_periodic_again> is being called. |
1890 | timer fires or C<ev_periodic_again> is being called. |
1536 | |
1891 | |
1537 | =item ev_tstamp interval [read-write] |
1892 | =item ev_tstamp interval [read-write] |
1538 | |
1893 | |
1539 | The current interval value. Can be modified any time, but changes only |
1894 | The current interval value. Can be modified any time, but changes only |
1540 | take effect when the periodic timer fires or C<ev_periodic_again> is being |
1895 | take effect when the periodic timer fires or C<ev_periodic_again> is being |
1541 | called. |
1896 | called. |
1542 | |
1897 | |
1543 | =item ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read-write] |
1898 | =item ev_tstamp (*reschedule_cb)(ev_periodic *w, ev_tstamp now) [read-write] |
1544 | |
1899 | |
1545 | The current reschedule callback, or C<0>, if this functionality is |
1900 | The current reschedule callback, or C<0>, if this functionality is |
1546 | switched off. Can be changed any time, but changes only take effect when |
1901 | switched off. Can be changed any time, but changes only take effect when |
1547 | the periodic timer fires or C<ev_periodic_again> is being called. |
1902 | the periodic timer fires or C<ev_periodic_again> is being called. |
1548 | |
1903 | |
… | |
… | |
1553 | Example: Call a callback every hour, or, more precisely, whenever the |
1908 | Example: Call a callback every hour, or, more precisely, whenever the |
1554 | system time is divisible by 3600. The callback invocation times have |
1909 | system time is divisible by 3600. The callback invocation times have |
1555 | potentially a lot of jitter, but good long-term stability. |
1910 | potentially a lot of jitter, but good long-term stability. |
1556 | |
1911 | |
1557 | static void |
1912 | static void |
1558 | clock_cb (struct ev_loop *loop, struct ev_io *w, int revents) |
1913 | clock_cb (struct ev_loop *loop, ev_io *w, int revents) |
1559 | { |
1914 | { |
1560 | ... its now a full hour (UTC, or TAI or whatever your clock follows) |
1915 | ... its now a full hour (UTC, or TAI or whatever your clock follows) |
1561 | } |
1916 | } |
1562 | |
1917 | |
1563 | struct ev_periodic hourly_tick; |
1918 | ev_periodic hourly_tick; |
1564 | ev_periodic_init (&hourly_tick, clock_cb, 0., 3600., 0); |
1919 | ev_periodic_init (&hourly_tick, clock_cb, 0., 3600., 0); |
1565 | ev_periodic_start (loop, &hourly_tick); |
1920 | ev_periodic_start (loop, &hourly_tick); |
1566 | |
1921 | |
1567 | Example: The same as above, but use a reschedule callback to do it: |
1922 | Example: The same as above, but use a reschedule callback to do it: |
1568 | |
1923 | |
1569 | #include <math.h> |
1924 | #include <math.h> |
1570 | |
1925 | |
1571 | static ev_tstamp |
1926 | static ev_tstamp |
1572 | my_scheduler_cb (struct ev_periodic *w, ev_tstamp now) |
1927 | my_scheduler_cb (ev_periodic *w, ev_tstamp now) |
1573 | { |
1928 | { |
1574 | return now + (3600. - fmod (now, 3600.)); |
1929 | return now + (3600. - fmod (now, 3600.)); |
1575 | } |
1930 | } |
1576 | |
1931 | |
1577 | ev_periodic_init (&hourly_tick, clock_cb, 0., 0., my_scheduler_cb); |
1932 | ev_periodic_init (&hourly_tick, clock_cb, 0., 0., my_scheduler_cb); |
1578 | |
1933 | |
1579 | Example: Call a callback every hour, starting now: |
1934 | Example: Call a callback every hour, starting now: |
1580 | |
1935 | |
1581 | struct ev_periodic hourly_tick; |
1936 | ev_periodic hourly_tick; |
1582 | ev_periodic_init (&hourly_tick, clock_cb, |
1937 | ev_periodic_init (&hourly_tick, clock_cb, |
1583 | fmod (ev_now (loop), 3600.), 3600., 0); |
1938 | fmod (ev_now (loop), 3600.), 3600., 0); |
1584 | ev_periodic_start (loop, &hourly_tick); |
1939 | ev_periodic_start (loop, &hourly_tick); |
1585 | |
1940 | |
1586 | |
1941 | |
… | |
… | |
1628 | =head3 Examples |
1983 | =head3 Examples |
1629 | |
1984 | |
1630 | Example: Try to exit cleanly on SIGINT. |
1985 | Example: Try to exit cleanly on SIGINT. |
1631 | |
1986 | |
1632 | static void |
1987 | static void |
1633 | sigint_cb (struct ev_loop *loop, struct ev_signal *w, int revents) |
1988 | sigint_cb (struct ev_loop *loop, ev_signal *w, int revents) |
1634 | { |
1989 | { |
1635 | ev_unloop (loop, EVUNLOOP_ALL); |
1990 | ev_unloop (loop, EVUNLOOP_ALL); |
1636 | } |
1991 | } |
1637 | |
1992 | |
1638 | struct ev_signal signal_watcher; |
1993 | ev_signal signal_watcher; |
1639 | ev_signal_init (&signal_watcher, sigint_cb, SIGINT); |
1994 | ev_signal_init (&signal_watcher, sigint_cb, SIGINT); |
1640 | ev_signal_start (loop, &signal_watcher); |
1995 | ev_signal_start (loop, &signal_watcher); |
1641 | |
1996 | |
1642 | |
1997 | |
1643 | =head2 C<ev_child> - watch out for process status changes |
1998 | =head2 C<ev_child> - watch out for process status changes |
… | |
… | |
1718 | its completion. |
2073 | its completion. |
1719 | |
2074 | |
1720 | ev_child cw; |
2075 | ev_child cw; |
1721 | |
2076 | |
1722 | static void |
2077 | static void |
1723 | child_cb (EV_P_ struct ev_child *w, int revents) |
2078 | child_cb (EV_P_ ev_child *w, int revents) |
1724 | { |
2079 | { |
1725 | ev_child_stop (EV_A_ w); |
2080 | ev_child_stop (EV_A_ w); |
1726 | printf ("process %d exited with status %x\n", w->rpid, w->rstatus); |
2081 | printf ("process %d exited with status %x\n", w->rpid, w->rstatus); |
1727 | } |
2082 | } |
1728 | |
2083 | |
… | |
… | |
1743 | |
2098 | |
1744 | |
2099 | |
1745 | =head2 C<ev_stat> - did the file attributes just change? |
2100 | =head2 C<ev_stat> - did the file attributes just change? |
1746 | |
2101 | |
1747 | This watches a file system path for attribute changes. That is, it calls |
2102 | This watches a file system path for attribute changes. That is, it calls |
1748 | C<stat> regularly (or when the OS says it changed) and sees if it changed |
2103 | C<stat> on that path in regular intervals (or when the OS says it changed) |
1749 | compared to the last time, invoking the callback if it did. |
2104 | and sees if it changed compared to the last time, invoking the callback if |
|
|
2105 | it did. |
1750 | |
2106 | |
1751 | The path does not need to exist: changing from "path exists" to "path does |
2107 | The path does not need to exist: changing from "path exists" to "path does |
1752 | not exist" is a status change like any other. The condition "path does |
2108 | not exist" is a status change like any other. The condition "path does not |
1753 | not exist" is signified by the C<st_nlink> field being zero (which is |
2109 | exist" (or more correctly "path cannot be stat'ed") is signified by the |
1754 | otherwise always forced to be at least one) and all the other fields of |
2110 | C<st_nlink> field being zero (which is otherwise always forced to be at |
1755 | the stat buffer having unspecified contents. |
2111 | least one) and all the other fields of the stat buffer having unspecified |
|
|
2112 | contents. |
1756 | |
2113 | |
1757 | The path I<should> be absolute and I<must not> end in a slash. If it is |
2114 | The path I<must not> end in a slash or contain special components such as |
|
|
2115 | C<.> or C<..>. The path I<should> be absolute: If it is relative and |
1758 | relative and your working directory changes, the behaviour is undefined. |
2116 | your working directory changes, then the behaviour is undefined. |
1759 | |
2117 | |
1760 | Since there is no standard kernel interface to do this, the portable |
2118 | Since there is no portable change notification interface available, the |
1761 | implementation simply calls C<stat (2)> regularly on the path to see if |
2119 | portable implementation simply calls C<stat(2)> regularly on the path |
1762 | it changed somehow. You can specify a recommended polling interval for |
2120 | to see if it changed somehow. You can specify a recommended polling |
1763 | this case. If you specify a polling interval of C<0> (highly recommended!) |
2121 | interval for this case. If you specify a polling interval of C<0> (highly |
1764 | then a I<suitable, unspecified default> value will be used (which |
2122 | recommended!) then a I<suitable, unspecified default> value will be used |
1765 | you can expect to be around five seconds, although this might change |
2123 | (which you can expect to be around five seconds, although this might |
1766 | dynamically). Libev will also impose a minimum interval which is currently |
2124 | change dynamically). Libev will also impose a minimum interval which is |
1767 | around C<0.1>, but thats usually overkill. |
2125 | currently around C<0.1>, but that's usually overkill. |
1768 | |
2126 | |
1769 | This watcher type is not meant for massive numbers of stat watchers, |
2127 | This watcher type is not meant for massive numbers of stat watchers, |
1770 | as even with OS-supported change notifications, this can be |
2128 | as even with OS-supported change notifications, this can be |
1771 | resource-intensive. |
2129 | resource-intensive. |
1772 | |
2130 | |
1773 | At the time of this writing, the only OS-specific interface implemented |
2131 | At the time of this writing, the only OS-specific interface implemented |
1774 | is the Linux inotify interface (implementing kqueue support is left as |
2132 | is the Linux inotify interface (implementing kqueue support is left as an |
1775 | an exercise for the reader. Note, however, that the author sees no way |
2133 | exercise for the reader. Note, however, that the author sees no way of |
1776 | of implementing C<ev_stat> semantics with kqueue). |
2134 | implementing C<ev_stat> semantics with kqueue, except as a hint). |
1777 | |
2135 | |
1778 | =head3 ABI Issues (Largefile Support) |
2136 | =head3 ABI Issues (Largefile Support) |
1779 | |
2137 | |
1780 | Libev by default (unless the user overrides this) uses the default |
2138 | Libev by default (unless the user overrides this) uses the default |
1781 | compilation environment, which means that on systems with large file |
2139 | compilation environment, which means that on systems with large file |
1782 | support disabled by default, you get the 32 bit version of the stat |
2140 | support disabled by default, you get the 32 bit version of the stat |
1783 | structure. When using the library from programs that change the ABI to |
2141 | structure. When using the library from programs that change the ABI to |
1784 | use 64 bit file offsets the programs will fail. In that case you have to |
2142 | use 64 bit file offsets the programs will fail. In that case you have to |
1785 | compile libev with the same flags to get binary compatibility. This is |
2143 | compile libev with the same flags to get binary compatibility. This is |
1786 | obviously the case with any flags that change the ABI, but the problem is |
2144 | obviously the case with any flags that change the ABI, but the problem is |
1787 | most noticeably disabled with ev_stat and large file support. |
2145 | most noticeably displayed with ev_stat and large file support. |
1788 | |
2146 | |
1789 | The solution for this is to lobby your distribution maker to make large |
2147 | The solution for this is to lobby your distribution maker to make large |
1790 | file interfaces available by default (as e.g. FreeBSD does) and not |
2148 | file interfaces available by default (as e.g. FreeBSD does) and not |
1791 | optional. Libev cannot simply switch on large file support because it has |
2149 | optional. Libev cannot simply switch on large file support because it has |
1792 | to exchange stat structures with application programs compiled using the |
2150 | to exchange stat structures with application programs compiled using the |
1793 | default compilation environment. |
2151 | default compilation environment. |
1794 | |
2152 | |
1795 | =head3 Inotify and Kqueue |
2153 | =head3 Inotify and Kqueue |
1796 | |
2154 | |
1797 | When C<inotify (7)> support has been compiled into libev (generally only |
2155 | When C<inotify (7)> support has been compiled into libev and present at |
1798 | available with Linux) and present at runtime, it will be used to speed up |
2156 | runtime, it will be used to speed up change detection where possible. The |
1799 | change detection where possible. The inotify descriptor will be created lazily |
2157 | inotify descriptor will be created lazily when the first C<ev_stat> |
1800 | when the first C<ev_stat> watcher is being started. |
2158 | watcher is being started. |
1801 | |
2159 | |
1802 | Inotify presence does not change the semantics of C<ev_stat> watchers |
2160 | Inotify presence does not change the semantics of C<ev_stat> watchers |
1803 | except that changes might be detected earlier, and in some cases, to avoid |
2161 | except that changes might be detected earlier, and in some cases, to avoid |
1804 | making regular C<stat> calls. Even in the presence of inotify support |
2162 | making regular C<stat> calls. Even in the presence of inotify support |
1805 | there are many cases where libev has to resort to regular C<stat> polling, |
2163 | there are many cases where libev has to resort to regular C<stat> polling, |
1806 | but as long as the path exists, libev usually gets away without polling. |
2164 | but as long as kernel 2.6.25 or newer is used (2.6.24 and older have too |
|
|
2165 | many bugs), the path exists (i.e. stat succeeds), and the path resides on |
|
|
2166 | a local filesystem (libev currently assumes only ext2/3, jfs, reiserfs and |
|
|
2167 | xfs are fully working) libev usually gets away without polling. |
1807 | |
2168 | |
1808 | There is no support for kqueue, as apparently it cannot be used to |
2169 | There is no support for kqueue, as apparently it cannot be used to |
1809 | implement this functionality, due to the requirement of having a file |
2170 | implement this functionality, due to the requirement of having a file |
1810 | descriptor open on the object at all times, and detecting renames, unlinks |
2171 | descriptor open on the object at all times, and detecting renames, unlinks |
1811 | etc. is difficult. |
2172 | etc. is difficult. |
1812 | |
2173 | |
|
|
2174 | =head3 C<stat ()> is a synchronous operation |
|
|
2175 | |
|
|
2176 | Libev doesn't normally do any kind of I/O itself, and so is not blocking |
|
|
2177 | the process. The exception are C<ev_stat> watchers - those call C<stat |
|
|
2178 | ()>, which is a synchronous operation. |
|
|
2179 | |
|
|
2180 | For local paths, this usually doesn't matter: unless the system is very |
|
|
2181 | busy or the intervals between stat's are large, a stat call will be fast, |
|
|
2182 | as the path data is usually in memory already (except when starting the |
|
|
2183 | watcher). |
|
|
2184 | |
|
|
2185 | For networked file systems, calling C<stat ()> can block an indefinite |
|
|
2186 | time due to network issues, and even under good conditions, a stat call |
|
|
2187 | often takes multiple milliseconds. |
|
|
2188 | |
|
|
2189 | Therefore, it is best to avoid using C<ev_stat> watchers on networked |
|
|
2190 | paths, although this is fully supported by libev. |
|
|
2191 | |
1813 | =head3 The special problem of stat time resolution |
2192 | =head3 The special problem of stat time resolution |
1814 | |
2193 | |
1815 | The C<stat ()> system call only supports full-second resolution portably, and |
2194 | The C<stat ()> system call only supports full-second resolution portably, |
1816 | even on systems where the resolution is higher, most file systems still |
2195 | and even on systems where the resolution is higher, most file systems |
1817 | only support whole seconds. |
2196 | still only support whole seconds. |
1818 | |
2197 | |
1819 | That means that, if the time is the only thing that changes, you can |
2198 | That means that, if the time is the only thing that changes, you can |
1820 | easily miss updates: on the first update, C<ev_stat> detects a change and |
2199 | easily miss updates: on the first update, C<ev_stat> detects a change and |
1821 | calls your callback, which does something. When there is another update |
2200 | calls your callback, which does something. When there is another update |
1822 | within the same second, C<ev_stat> will be unable to detect unless the |
2201 | within the same second, C<ev_stat> will be unable to detect unless the |
… | |
… | |
1965 | |
2344 | |
1966 | =head3 Watcher-Specific Functions and Data Members |
2345 | =head3 Watcher-Specific Functions and Data Members |
1967 | |
2346 | |
1968 | =over 4 |
2347 | =over 4 |
1969 | |
2348 | |
1970 | =item ev_idle_init (ev_signal *, callback) |
2349 | =item ev_idle_init (ev_idle *, callback) |
1971 | |
2350 | |
1972 | Initialises and configures the idle watcher - it has no parameters of any |
2351 | Initialises and configures the idle watcher - it has no parameters of any |
1973 | kind. There is a C<ev_idle_set> macro, but using it is utterly pointless, |
2352 | kind. There is a C<ev_idle_set> macro, but using it is utterly pointless, |
1974 | believe me. |
2353 | believe me. |
1975 | |
2354 | |
… | |
… | |
1979 | |
2358 | |
1980 | Example: Dynamically allocate an C<ev_idle> watcher, start it, and in the |
2359 | Example: Dynamically allocate an C<ev_idle> watcher, start it, and in the |
1981 | callback, free it. Also, use no error checking, as usual. |
2360 | callback, free it. Also, use no error checking, as usual. |
1982 | |
2361 | |
1983 | static void |
2362 | static void |
1984 | idle_cb (struct ev_loop *loop, struct ev_idle *w, int revents) |
2363 | idle_cb (struct ev_loop *loop, ev_idle *w, int revents) |
1985 | { |
2364 | { |
1986 | free (w); |
2365 | free (w); |
1987 | // now do something you wanted to do when the program has |
2366 | // now do something you wanted to do when the program has |
1988 | // no longer anything immediate to do. |
2367 | // no longer anything immediate to do. |
1989 | } |
2368 | } |
1990 | |
2369 | |
1991 | struct ev_idle *idle_watcher = malloc (sizeof (struct ev_idle)); |
2370 | ev_idle *idle_watcher = malloc (sizeof (ev_idle)); |
1992 | ev_idle_init (idle_watcher, idle_cb); |
2371 | ev_idle_init (idle_watcher, idle_cb); |
1993 | ev_idle_start (loop, idle_cb); |
2372 | ev_idle_start (loop, idle_cb); |
1994 | |
2373 | |
1995 | |
2374 | |
1996 | =head2 C<ev_prepare> and C<ev_check> - customise your event loop! |
2375 | =head2 C<ev_prepare> and C<ev_check> - customise your event loop! |
… | |
… | |
2077 | |
2456 | |
2078 | static ev_io iow [nfd]; |
2457 | static ev_io iow [nfd]; |
2079 | static ev_timer tw; |
2458 | static ev_timer tw; |
2080 | |
2459 | |
2081 | static void |
2460 | static void |
2082 | io_cb (ev_loop *loop, ev_io *w, int revents) |
2461 | io_cb (struct ev_loop *loop, ev_io *w, int revents) |
2083 | { |
2462 | { |
2084 | } |
2463 | } |
2085 | |
2464 | |
2086 | // create io watchers for each fd and a timer before blocking |
2465 | // create io watchers for each fd and a timer before blocking |
2087 | static void |
2466 | static void |
2088 | adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) |
2467 | adns_prepare_cb (struct ev_loop *loop, ev_prepare *w, int revents) |
2089 | { |
2468 | { |
2090 | int timeout = 3600000; |
2469 | int timeout = 3600000; |
2091 | struct pollfd fds [nfd]; |
2470 | struct pollfd fds [nfd]; |
2092 | // actual code will need to loop here and realloc etc. |
2471 | // actual code will need to loop here and realloc etc. |
2093 | adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ())); |
2472 | adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ())); |
… | |
… | |
2108 | } |
2487 | } |
2109 | } |
2488 | } |
2110 | |
2489 | |
2111 | // stop all watchers after blocking |
2490 | // stop all watchers after blocking |
2112 | static void |
2491 | static void |
2113 | adns_check_cb (ev_loop *loop, ev_check *w, int revents) |
2492 | adns_check_cb (struct ev_loop *loop, ev_check *w, int revents) |
2114 | { |
2493 | { |
2115 | ev_timer_stop (loop, &tw); |
2494 | ev_timer_stop (loop, &tw); |
2116 | |
2495 | |
2117 | for (int i = 0; i < nfd; ++i) |
2496 | for (int i = 0; i < nfd; ++i) |
2118 | { |
2497 | { |
… | |
… | |
2214 | some fds have to be watched and handled very quickly (with low latency), |
2593 | some fds have to be watched and handled very quickly (with low latency), |
2215 | and even priorities and idle watchers might have too much overhead. In |
2594 | and even priorities and idle watchers might have too much overhead. In |
2216 | this case you would put all the high priority stuff in one loop and all |
2595 | this case you would put all the high priority stuff in one loop and all |
2217 | the rest in a second one, and embed the second one in the first. |
2596 | the rest in a second one, and embed the second one in the first. |
2218 | |
2597 | |
2219 | As long as the watcher is active, the callback will be invoked every time |
2598 | As long as the watcher is active, the callback will be invoked every |
2220 | there might be events pending in the embedded loop. The callback must then |
2599 | time there might be events pending in the embedded loop. The callback |
2221 | call C<ev_embed_sweep (mainloop, watcher)> to make a single sweep and invoke |
2600 | must then call C<ev_embed_sweep (mainloop, watcher)> to make a single |
2222 | their callbacks (you could also start an idle watcher to give the embedded |
2601 | sweep and invoke their callbacks (the callback doesn't need to invoke the |
2223 | loop strictly lower priority for example). You can also set the callback |
2602 | C<ev_embed_sweep> function directly, it could also start an idle watcher |
2224 | to C<0>, in which case the embed watcher will automatically execute the |
2603 | to give the embedded loop strictly lower priority for example). |
2225 | embedded loop sweep. |
|
|
2226 | |
2604 | |
2227 | As long as the watcher is started it will automatically handle events. The |
2605 | You can also set the callback to C<0>, in which case the embed watcher |
2228 | callback will be invoked whenever some events have been handled. You can |
2606 | will automatically execute the embedded loop sweep whenever necessary. |
2229 | set the callback to C<0> to avoid having to specify one if you are not |
|
|
2230 | interested in that. |
|
|
2231 | |
2607 | |
2232 | Also, there have not currently been made special provisions for forking: |
2608 | Fork detection will be handled transparently while the C<ev_embed> watcher |
2233 | when you fork, you not only have to call C<ev_loop_fork> on both loops, |
2609 | is active, i.e., the embedded loop will automatically be forked when the |
2234 | but you will also have to stop and restart any C<ev_embed> watchers |
2610 | embedding loop forks. In other cases, the user is responsible for calling |
2235 | yourself - but you can use a fork watcher to handle this automatically, |
2611 | C<ev_loop_fork> on the embedded loop. |
2236 | and future versions of libev might do just that. |
|
|
2237 | |
2612 | |
2238 | Unfortunately, not all backends are embeddable: only the ones returned by |
2613 | Unfortunately, not all backends are embeddable: only the ones returned by |
2239 | C<ev_embeddable_backends> are, which, unfortunately, does not include any |
2614 | C<ev_embeddable_backends> are, which, unfortunately, does not include any |
2240 | portable one. |
2615 | portable one. |
2241 | |
2616 | |
… | |
… | |
2286 | C<loop_lo> (which is C<loop_hi> in the case no embeddable loop can be |
2661 | C<loop_lo> (which is C<loop_hi> in the case no embeddable loop can be |
2287 | used). |
2662 | used). |
2288 | |
2663 | |
2289 | struct ev_loop *loop_hi = ev_default_init (0); |
2664 | struct ev_loop *loop_hi = ev_default_init (0); |
2290 | struct ev_loop *loop_lo = 0; |
2665 | struct ev_loop *loop_lo = 0; |
2291 | struct ev_embed embed; |
2666 | ev_embed embed; |
2292 | |
2667 | |
2293 | // see if there is a chance of getting one that works |
2668 | // see if there is a chance of getting one that works |
2294 | // (remember that a flags value of 0 means autodetection) |
2669 | // (remember that a flags value of 0 means autodetection) |
2295 | loop_lo = ev_embeddable_backends () & ev_recommended_backends () |
2670 | loop_lo = ev_embeddable_backends () & ev_recommended_backends () |
2296 | ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ()) |
2671 | ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ()) |
… | |
… | |
2310 | kqueue implementation). Store the kqueue/socket-only event loop in |
2685 | kqueue implementation). Store the kqueue/socket-only event loop in |
2311 | C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too). |
2686 | C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too). |
2312 | |
2687 | |
2313 | struct ev_loop *loop = ev_default_init (0); |
2688 | struct ev_loop *loop = ev_default_init (0); |
2314 | struct ev_loop *loop_socket = 0; |
2689 | struct ev_loop *loop_socket = 0; |
2315 | struct ev_embed embed; |
2690 | ev_embed embed; |
2316 | |
2691 | |
2317 | if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE) |
2692 | if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE) |
2318 | if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE)) |
2693 | if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE)) |
2319 | { |
2694 | { |
2320 | ev_embed_init (&embed, 0, loop_socket); |
2695 | ev_embed_init (&embed, 0, loop_socket); |
… | |
… | |
2335 | event loop blocks next and before C<ev_check> watchers are being called, |
2710 | event loop blocks next and before C<ev_check> watchers are being called, |
2336 | and only in the child after the fork. If whoever good citizen calling |
2711 | and only in the child after the fork. If whoever good citizen calling |
2337 | C<ev_default_fork> cheats and calls it in the wrong process, the fork |
2712 | C<ev_default_fork> cheats and calls it in the wrong process, the fork |
2338 | handlers will be invoked, too, of course. |
2713 | handlers will be invoked, too, of course. |
2339 | |
2714 | |
|
|
2715 | =head3 The special problem of life after fork - how is it possible? |
|
|
2716 | |
|
|
2717 | Most uses of C<fork()> consist of forking, then some simple calls to ste |
|
|
2718 | up/change the process environment, followed by a call to C<exec()>. This |
|
|
2719 | sequence should be handled by libev without any problems. |
|
|
2720 | |
|
|
2721 | This changes when the application actually wants to do event handling |
|
|
2722 | in the child, or both parent in child, in effect "continuing" after the |
|
|
2723 | fork. |
|
|
2724 | |
|
|
2725 | The default mode of operation (for libev, with application help to detect |
|
|
2726 | forks) is to duplicate all the state in the child, as would be expected |
|
|
2727 | when I<either> the parent I<or> the child process continues. |
|
|
2728 | |
|
|
2729 | When both processes want to continue using libev, then this is usually the |
|
|
2730 | wrong result. In that case, usually one process (typically the parent) is |
|
|
2731 | supposed to continue with all watchers in place as before, while the other |
|
|
2732 | process typically wants to start fresh, i.e. without any active watchers. |
|
|
2733 | |
|
|
2734 | The cleanest and most efficient way to achieve that with libev is to |
|
|
2735 | simply create a new event loop, which of course will be "empty", and |
|
|
2736 | use that for new watchers. This has the advantage of not touching more |
|
|
2737 | memory than necessary, and thus avoiding the copy-on-write, and the |
|
|
2738 | disadvantage of having to use multiple event loops (which do not support |
|
|
2739 | signal watchers). |
|
|
2740 | |
|
|
2741 | When this is not possible, or you want to use the default loop for |
|
|
2742 | other reasons, then in the process that wants to start "fresh", call |
|
|
2743 | C<ev_default_destroy ()> followed by C<ev_default_loop (...)>. Destroying |
|
|
2744 | the default loop will "orphan" (not stop) all registered watchers, so you |
|
|
2745 | have to be careful not to execute code that modifies those watchers. Note |
|
|
2746 | also that in that case, you have to re-register any signal watchers. |
|
|
2747 | |
2340 | =head3 Watcher-Specific Functions and Data Members |
2748 | =head3 Watcher-Specific Functions and Data Members |
2341 | |
2749 | |
2342 | =over 4 |
2750 | =over 4 |
2343 | |
2751 | |
2344 | =item ev_fork_init (ev_signal *, callback) |
2752 | =item ev_fork_init (ev_signal *, callback) |
… | |
… | |
2384 | =over 4 |
2792 | =over 4 |
2385 | |
2793 | |
2386 | =item queueing from a signal handler context |
2794 | =item queueing from a signal handler context |
2387 | |
2795 | |
2388 | To implement race-free queueing, you simply add to the queue in the signal |
2796 | To implement race-free queueing, you simply add to the queue in the signal |
2389 | handler but you block the signal handler in the watcher callback. Here is an example that does that for |
2797 | handler but you block the signal handler in the watcher callback. Here is |
2390 | some fictitious SIGUSR1 handler: |
2798 | an example that does that for some fictitious SIGUSR1 handler: |
2391 | |
2799 | |
2392 | static ev_async mysig; |
2800 | static ev_async mysig; |
2393 | |
2801 | |
2394 | static void |
2802 | static void |
2395 | sigusr1_handler (void) |
2803 | sigusr1_handler (void) |
… | |
… | |
2461 | =over 4 |
2869 | =over 4 |
2462 | |
2870 | |
2463 | =item ev_async_init (ev_async *, callback) |
2871 | =item ev_async_init (ev_async *, callback) |
2464 | |
2872 | |
2465 | Initialises and configures the async watcher - it has no parameters of any |
2873 | Initialises and configures the async watcher - it has no parameters of any |
2466 | kind. There is a C<ev_asynd_set> macro, but using it is utterly pointless, |
2874 | kind. There is a C<ev_async_set> macro, but using it is utterly pointless, |
2467 | trust me. |
2875 | trust me. |
2468 | |
2876 | |
2469 | =item ev_async_send (loop, ev_async *) |
2877 | =item ev_async_send (loop, ev_async *) |
2470 | |
2878 | |
2471 | Sends/signals/activates the given C<ev_async> watcher, that is, feeds |
2879 | Sends/signals/activates the given C<ev_async> watcher, that is, feeds |
2472 | an C<EV_ASYNC> event on the watcher into the event loop. Unlike |
2880 | an C<EV_ASYNC> event on the watcher into the event loop. Unlike |
2473 | C<ev_feed_event>, this call is safe to do from other threads, signal or |
2881 | C<ev_feed_event>, this call is safe to do from other threads, signal or |
2474 | similar contexts (see the discussion of C<EV_ATOMIC_T> in the embedding |
2882 | similar contexts (see the discussion of C<EV_ATOMIC_T> in the embedding |
2475 | section below on what exactly this means). |
2883 | section below on what exactly this means). |
2476 | |
2884 | |
|
|
2885 | Note that, as with other watchers in libev, multiple events might get |
|
|
2886 | compressed into a single callback invocation (another way to look at this |
|
|
2887 | is that C<ev_async> watchers are level-triggered, set on C<ev_async_send>, |
|
|
2888 | reset when the event loop detects that). |
|
|
2889 | |
2477 | This call incurs the overhead of a system call only once per loop iteration, |
2890 | This call incurs the overhead of a system call only once per event loop |
2478 | so while the overhead might be noticeable, it doesn't apply to repeated |
2891 | iteration, so while the overhead might be noticeable, it doesn't apply to |
2479 | calls to C<ev_async_send>. |
2892 | repeated calls to C<ev_async_send> for the same event loop. |
2480 | |
2893 | |
2481 | =item bool = ev_async_pending (ev_async *) |
2894 | =item bool = ev_async_pending (ev_async *) |
2482 | |
2895 | |
2483 | Returns a non-zero value when C<ev_async_send> has been called on the |
2896 | Returns a non-zero value when C<ev_async_send> has been called on the |
2484 | watcher but the event has not yet been processed (or even noted) by the |
2897 | watcher but the event has not yet been processed (or even noted) by the |
… | |
… | |
2487 | C<ev_async_send> sets a flag in the watcher and wakes up the loop. When |
2900 | C<ev_async_send> sets a flag in the watcher and wakes up the loop. When |
2488 | the loop iterates next and checks for the watcher to have become active, |
2901 | the loop iterates next and checks for the watcher to have become active, |
2489 | it will reset the flag again. C<ev_async_pending> can be used to very |
2902 | it will reset the flag again. C<ev_async_pending> can be used to very |
2490 | quickly check whether invoking the loop might be a good idea. |
2903 | quickly check whether invoking the loop might be a good idea. |
2491 | |
2904 | |
2492 | Not that this does I<not> check whether the watcher itself is pending, only |
2905 | Not that this does I<not> check whether the watcher itself is pending, |
2493 | whether it has been requested to make this watcher pending. |
2906 | only whether it has been requested to make this watcher pending: there |
|
|
2907 | is a time window between the event loop checking and resetting the async |
|
|
2908 | notification, and the callback being invoked. |
2494 | |
2909 | |
2495 | =back |
2910 | =back |
2496 | |
2911 | |
2497 | |
2912 | |
2498 | =head1 OTHER FUNCTIONS |
2913 | =head1 OTHER FUNCTIONS |
… | |
… | |
2502 | =over 4 |
2917 | =over 4 |
2503 | |
2918 | |
2504 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
2919 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
2505 | |
2920 | |
2506 | This function combines a simple timer and an I/O watcher, calls your |
2921 | This function combines a simple timer and an I/O watcher, calls your |
2507 | callback on whichever event happens first and automatically stop both |
2922 | callback on whichever event happens first and automatically stops both |
2508 | watchers. This is useful if you want to wait for a single event on an fd |
2923 | watchers. This is useful if you want to wait for a single event on an fd |
2509 | or timeout without having to allocate/configure/start/stop/free one or |
2924 | or timeout without having to allocate/configure/start/stop/free one or |
2510 | more watchers yourself. |
2925 | more watchers yourself. |
2511 | |
2926 | |
2512 | If C<fd> is less than 0, then no I/O watcher will be started and events |
2927 | If C<fd> is less than 0, then no I/O watcher will be started and the |
2513 | is being ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and |
2928 | C<events> argument is being ignored. Otherwise, an C<ev_io> watcher for |
2514 | C<events> set will be created and started. |
2929 | the given C<fd> and C<events> set will be created and started. |
2515 | |
2930 | |
2516 | If C<timeout> is less than 0, then no timeout watcher will be |
2931 | If C<timeout> is less than 0, then no timeout watcher will be |
2517 | started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and |
2932 | started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and |
2518 | repeat = 0) will be started. While C<0> is a valid timeout, it is of |
2933 | repeat = 0) will be started. C<0> is a valid timeout. |
2519 | dubious value. |
|
|
2520 | |
2934 | |
2521 | The callback has the type C<void (*cb)(int revents, void *arg)> and gets |
2935 | The callback has the type C<void (*cb)(int revents, void *arg)> and gets |
2522 | passed an C<revents> set like normal event callbacks (a combination of |
2936 | passed an C<revents> set like normal event callbacks (a combination of |
2523 | C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg> |
2937 | C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg> |
2524 | value passed to C<ev_once>: |
2938 | value passed to C<ev_once>. Note that it is possible to receive I<both> |
|
|
2939 | a timeout and an io event at the same time - you probably should give io |
|
|
2940 | events precedence. |
|
|
2941 | |
|
|
2942 | Example: wait up to ten seconds for data to appear on STDIN_FILENO. |
2525 | |
2943 | |
2526 | static void stdin_ready (int revents, void *arg) |
2944 | static void stdin_ready (int revents, void *arg) |
2527 | { |
2945 | { |
|
|
2946 | if (revents & EV_READ) |
|
|
2947 | /* stdin might have data for us, joy! */; |
2528 | if (revents & EV_TIMEOUT) |
2948 | else if (revents & EV_TIMEOUT) |
2529 | /* doh, nothing entered */; |
2949 | /* doh, nothing entered */; |
2530 | else if (revents & EV_READ) |
|
|
2531 | /* stdin might have data for us, joy! */; |
|
|
2532 | } |
2950 | } |
2533 | |
2951 | |
2534 | ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
2952 | ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
2535 | |
2953 | |
2536 | =item ev_feed_event (ev_loop *, watcher *, int revents) |
2954 | =item ev_feed_event (struct ev_loop *, watcher *, int revents) |
2537 | |
2955 | |
2538 | Feeds the given event set into the event loop, as if the specified event |
2956 | Feeds the given event set into the event loop, as if the specified event |
2539 | had happened for the specified watcher (which must be a pointer to an |
2957 | had happened for the specified watcher (which must be a pointer to an |
2540 | initialised but not necessarily started event watcher). |
2958 | initialised but not necessarily started event watcher). |
2541 | |
2959 | |
2542 | =item ev_feed_fd_event (ev_loop *, int fd, int revents) |
2960 | =item ev_feed_fd_event (struct ev_loop *, int fd, int revents) |
2543 | |
2961 | |
2544 | Feed an event on the given fd, as if a file descriptor backend detected |
2962 | Feed an event on the given fd, as if a file descriptor backend detected |
2545 | the given events it. |
2963 | the given events it. |
2546 | |
2964 | |
2547 | =item ev_feed_signal_event (ev_loop *loop, int signum) |
2965 | =item ev_feed_signal_event (struct ev_loop *loop, int signum) |
2548 | |
2966 | |
2549 | Feed an event as if the given signal occurred (C<loop> must be the default |
2967 | Feed an event as if the given signal occurred (C<loop> must be the default |
2550 | loop!). |
2968 | loop!). |
2551 | |
2969 | |
2552 | =back |
2970 | =back |
… | |
… | |
2673 | } |
3091 | } |
2674 | |
3092 | |
2675 | myclass obj; |
3093 | myclass obj; |
2676 | ev::io iow; |
3094 | ev::io iow; |
2677 | iow.set <myclass, &myclass::io_cb> (&obj); |
3095 | iow.set <myclass, &myclass::io_cb> (&obj); |
|
|
3096 | |
|
|
3097 | =item w->set (object *) |
|
|
3098 | |
|
|
3099 | This is an B<experimental> feature that might go away in a future version. |
|
|
3100 | |
|
|
3101 | This is a variation of a method callback - leaving out the method to call |
|
|
3102 | will default the method to C<operator ()>, which makes it possible to use |
|
|
3103 | functor objects without having to manually specify the C<operator ()> all |
|
|
3104 | the time. Incidentally, you can then also leave out the template argument |
|
|
3105 | list. |
|
|
3106 | |
|
|
3107 | The C<operator ()> method prototype must be C<void operator ()(watcher &w, |
|
|
3108 | int revents)>. |
|
|
3109 | |
|
|
3110 | See the method-C<set> above for more details. |
|
|
3111 | |
|
|
3112 | Example: use a functor object as callback. |
|
|
3113 | |
|
|
3114 | struct myfunctor |
|
|
3115 | { |
|
|
3116 | void operator() (ev::io &w, int revents) |
|
|
3117 | { |
|
|
3118 | ... |
|
|
3119 | } |
|
|
3120 | } |
|
|
3121 | |
|
|
3122 | myfunctor f; |
|
|
3123 | |
|
|
3124 | ev::io w; |
|
|
3125 | w.set (&f); |
2678 | |
3126 | |
2679 | =item w->set<function> (void *data = 0) |
3127 | =item w->set<function> (void *data = 0) |
2680 | |
3128 | |
2681 | Also sets a callback, but uses a static method or plain function as |
3129 | Also sets a callback, but uses a static method or plain function as |
2682 | callback. The optional C<data> argument will be stored in the watcher's |
3130 | callback. The optional C<data> argument will be stored in the watcher's |
… | |
… | |
2769 | L<http://software.schmorp.de/pkg/EV>. |
3217 | L<http://software.schmorp.de/pkg/EV>. |
2770 | |
3218 | |
2771 | =item Python |
3219 | =item Python |
2772 | |
3220 | |
2773 | Python bindings can be found at L<http://code.google.com/p/pyev/>. It |
3221 | Python bindings can be found at L<http://code.google.com/p/pyev/>. It |
2774 | seems to be quite complete and well-documented. Note, however, that the |
3222 | seems to be quite complete and well-documented. |
2775 | patch they require for libev is outright dangerous as it breaks the ABI |
|
|
2776 | for everybody else, and therefore, should never be applied in an installed |
|
|
2777 | libev (if python requires an incompatible ABI then it needs to embed |
|
|
2778 | libev). |
|
|
2779 | |
3223 | |
2780 | =item Ruby |
3224 | =item Ruby |
2781 | |
3225 | |
2782 | Tony Arcieri has written a ruby extension that offers access to a subset |
3226 | Tony Arcieri has written a ruby extension that offers access to a subset |
2783 | of the libev API and adds file handle abstractions, asynchronous DNS and |
3227 | of the libev API and adds file handle abstractions, asynchronous DNS and |
2784 | more on top of it. It can be found via gem servers. Its homepage is at |
3228 | more on top of it. It can be found via gem servers. Its homepage is at |
2785 | L<http://rev.rubyforge.org/>. |
3229 | L<http://rev.rubyforge.org/>. |
2786 | |
3230 | |
|
|
3231 | Roger Pack reports that using the link order C<-lws2_32 -lmsvcrt-ruby-190> |
|
|
3232 | makes rev work even on mingw. |
|
|
3233 | |
|
|
3234 | =item Haskell |
|
|
3235 | |
|
|
3236 | A haskell binding to libev is available at |
|
|
3237 | L<http://hackage.haskell.org/cgi-bin/hackage-scripts/package/hlibev>. |
|
|
3238 | |
2787 | =item D |
3239 | =item D |
2788 | |
3240 | |
2789 | Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to |
3241 | Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to |
2790 | be found at L<http://proj.llucax.com.ar/wiki/evd>. |
3242 | be found at L<http://proj.llucax.com.ar/wiki/evd>. |
|
|
3243 | |
|
|
3244 | =item Ocaml |
|
|
3245 | |
|
|
3246 | Erkki Seppala has written Ocaml bindings for libev, to be found at |
|
|
3247 | L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>. |
2791 | |
3248 | |
2792 | =back |
3249 | =back |
2793 | |
3250 | |
2794 | |
3251 | |
2795 | =head1 MACRO MAGIC |
3252 | =head1 MACRO MAGIC |
… | |
… | |
2896 | |
3353 | |
2897 | #define EV_STANDALONE 1 |
3354 | #define EV_STANDALONE 1 |
2898 | #include "ev.h" |
3355 | #include "ev.h" |
2899 | |
3356 | |
2900 | Both header files and implementation files can be compiled with a C++ |
3357 | Both header files and implementation files can be compiled with a C++ |
2901 | compiler (at least, thats a stated goal, and breakage will be treated |
3358 | compiler (at least, that's a stated goal, and breakage will be treated |
2902 | as a bug). |
3359 | as a bug). |
2903 | |
3360 | |
2904 | You need the following files in your source tree, or in a directory |
3361 | You need the following files in your source tree, or in a directory |
2905 | in your include path (e.g. in libev/ when using -Ilibev): |
3362 | in your include path (e.g. in libev/ when using -Ilibev): |
2906 | |
3363 | |
… | |
… | |
2962 | keeps libev from including F<config.h>, and it also defines dummy |
3419 | keeps libev from including F<config.h>, and it also defines dummy |
2963 | implementations for some libevent functions (such as logging, which is not |
3420 | implementations for some libevent functions (such as logging, which is not |
2964 | supported). It will also not define any of the structs usually found in |
3421 | supported). It will also not define any of the structs usually found in |
2965 | F<event.h> that are not directly supported by the libev core alone. |
3422 | F<event.h> that are not directly supported by the libev core alone. |
2966 | |
3423 | |
|
|
3424 | In stanbdalone mode, libev will still try to automatically deduce the |
|
|
3425 | configuration, but has to be more conservative. |
|
|
3426 | |
2967 | =item EV_USE_MONOTONIC |
3427 | =item EV_USE_MONOTONIC |
2968 | |
3428 | |
2969 | If defined to be C<1>, libev will try to detect the availability of the |
3429 | If defined to be C<1>, libev will try to detect the availability of the |
2970 | monotonic clock option at both compile time and runtime. Otherwise no use |
3430 | monotonic clock option at both compile time and runtime. Otherwise no |
2971 | of the monotonic clock option will be attempted. If you enable this, you |
3431 | use of the monotonic clock option will be attempted. If you enable this, |
2972 | usually have to link against librt or something similar. Enabling it when |
3432 | you usually have to link against librt or something similar. Enabling it |
2973 | the functionality isn't available is safe, though, although you have |
3433 | when the functionality isn't available is safe, though, although you have |
2974 | to make sure you link against any libraries where the C<clock_gettime> |
3434 | to make sure you link against any libraries where the C<clock_gettime> |
2975 | function is hiding in (often F<-lrt>). |
3435 | function is hiding in (often F<-lrt>). See also C<EV_USE_CLOCK_SYSCALL>. |
2976 | |
3436 | |
2977 | =item EV_USE_REALTIME |
3437 | =item EV_USE_REALTIME |
2978 | |
3438 | |
2979 | If defined to be C<1>, libev will try to detect the availability of the |
3439 | If defined to be C<1>, libev will try to detect the availability of the |
2980 | real-time clock option at compile time (and assume its availability at |
3440 | real-time clock option at compile time (and assume its availability |
2981 | runtime if successful). Otherwise no use of the real-time clock option will |
3441 | at runtime if successful). Otherwise no use of the real-time clock |
2982 | be attempted. This effectively replaces C<gettimeofday> by C<clock_get |
3442 | option will be attempted. This effectively replaces C<gettimeofday> |
2983 | (CLOCK_REALTIME, ...)> and will not normally affect correctness. See the |
3443 | by C<clock_get (CLOCK_REALTIME, ...)> and will not normally affect |
2984 | note about libraries in the description of C<EV_USE_MONOTONIC>, though. |
3444 | correctness. See the note about libraries in the description of |
|
|
3445 | C<EV_USE_MONOTONIC>, though. Defaults to the opposite value of |
|
|
3446 | C<EV_USE_CLOCK_SYSCALL>. |
|
|
3447 | |
|
|
3448 | =item EV_USE_CLOCK_SYSCALL |
|
|
3449 | |
|
|
3450 | If defined to be C<1>, libev will try to use a direct syscall instead |
|
|
3451 | of calling the system-provided C<clock_gettime> function. This option |
|
|
3452 | exists because on GNU/Linux, C<clock_gettime> is in C<librt>, but C<librt> |
|
|
3453 | unconditionally pulls in C<libpthread>, slowing down single-threaded |
|
|
3454 | programs needlessly. Using a direct syscall is slightly slower (in |
|
|
3455 | theory), because no optimised vdso implementation can be used, but avoids |
|
|
3456 | the pthread dependency. Defaults to C<1> on GNU/Linux with glibc 2.x or |
|
|
3457 | higher, as it simplifies linking (no need for C<-lrt>). |
2985 | |
3458 | |
2986 | =item EV_USE_NANOSLEEP |
3459 | =item EV_USE_NANOSLEEP |
2987 | |
3460 | |
2988 | If defined to be C<1>, libev will assume that C<nanosleep ()> is available |
3461 | If defined to be C<1>, libev will assume that C<nanosleep ()> is available |
2989 | and will use it for delays. Otherwise it will use C<select ()>. |
3462 | and will use it for delays. Otherwise it will use C<select ()>. |
… | |
… | |
3005 | |
3478 | |
3006 | =item EV_SELECT_USE_FD_SET |
3479 | =item EV_SELECT_USE_FD_SET |
3007 | |
3480 | |
3008 | If defined to C<1>, then the select backend will use the system C<fd_set> |
3481 | If defined to C<1>, then the select backend will use the system C<fd_set> |
3009 | structure. This is useful if libev doesn't compile due to a missing |
3482 | structure. This is useful if libev doesn't compile due to a missing |
3010 | C<NFDBITS> or C<fd_mask> definition or it mis-guesses the bitset layout on |
3483 | C<NFDBITS> or C<fd_mask> definition or it mis-guesses the bitset layout |
3011 | exotic systems. This usually limits the range of file descriptors to some |
3484 | on exotic systems. This usually limits the range of file descriptors to |
3012 | low limit such as 1024 or might have other limitations (winsocket only |
3485 | some low limit such as 1024 or might have other limitations (winsocket |
3013 | allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation, might |
3486 | only allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation, |
3014 | influence the size of the C<fd_set> used. |
3487 | configures the maximum size of the C<fd_set>. |
3015 | |
3488 | |
3016 | =item EV_SELECT_IS_WINSOCKET |
3489 | =item EV_SELECT_IS_WINSOCKET |
3017 | |
3490 | |
3018 | When defined to C<1>, the select backend will assume that |
3491 | When defined to C<1>, the select backend will assume that |
3019 | select/socket/connect etc. don't understand file descriptors but |
3492 | select/socket/connect etc. don't understand file descriptors but |
… | |
… | |
3313 | =head2 THREADS AND COROUTINES |
3786 | =head2 THREADS AND COROUTINES |
3314 | |
3787 | |
3315 | =head3 THREADS |
3788 | =head3 THREADS |
3316 | |
3789 | |
3317 | All libev functions are reentrant and thread-safe unless explicitly |
3790 | All libev functions are reentrant and thread-safe unless explicitly |
3318 | documented otherwise, but it uses no locking itself. This means that you |
3791 | documented otherwise, but libev implements no locking itself. This means |
3319 | can use as many loops as you want in parallel, as long as there are no |
3792 | that you can use as many loops as you want in parallel, as long as there |
3320 | concurrent calls into any libev function with the same loop parameter |
3793 | are no concurrent calls into any libev function with the same loop |
3321 | (C<ev_default_*> calls have an implicit default loop parameter, of |
3794 | parameter (C<ev_default_*> calls have an implicit default loop parameter, |
3322 | course): libev guarantees that different event loops share no data |
3795 | of course): libev guarantees that different event loops share no data |
3323 | structures that need any locking. |
3796 | structures that need any locking. |
3324 | |
3797 | |
3325 | Or to put it differently: calls with different loop parameters can be done |
3798 | Or to put it differently: calls with different loop parameters can be done |
3326 | concurrently from multiple threads, calls with the same loop parameter |
3799 | concurrently from multiple threads, calls with the same loop parameter |
3327 | must be done serially (but can be done from different threads, as long as |
3800 | must be done serially (but can be done from different threads, as long as |
… | |
… | |
3369 | |
3842 | |
3370 | =back |
3843 | =back |
3371 | |
3844 | |
3372 | =head3 COROUTINES |
3845 | =head3 COROUTINES |
3373 | |
3846 | |
3374 | Libev is much more accommodating to coroutines ("cooperative threads"): |
3847 | Libev is very accommodating to coroutines ("cooperative threads"): |
3375 | libev fully supports nesting calls to it's functions from different |
3848 | libev fully supports nesting calls to its functions from different |
3376 | coroutines (e.g. you can call C<ev_loop> on the same loop from two |
3849 | coroutines (e.g. you can call C<ev_loop> on the same loop from two |
3377 | different coroutines and switch freely between both coroutines running the |
3850 | different coroutines, and switch freely between both coroutines running the |
3378 | loop, as long as you don't confuse yourself). The only exception is that |
3851 | loop, as long as you don't confuse yourself). The only exception is that |
3379 | you must not do this from C<ev_periodic> reschedule callbacks. |
3852 | you must not do this from C<ev_periodic> reschedule callbacks. |
3380 | |
3853 | |
3381 | Care has been taken to ensure that libev does not keep local state inside |
3854 | Care has been taken to ensure that libev does not keep local state inside |
3382 | C<ev_loop>, and other calls do not usually allow coroutine switches. |
3855 | C<ev_loop>, and other calls do not usually allow for coroutine switches as |
|
|
3856 | they do not call any callbacks. |
3383 | |
3857 | |
3384 | =head2 COMPILER WARNINGS |
3858 | =head2 COMPILER WARNINGS |
3385 | |
3859 | |
3386 | Depending on your compiler and compiler settings, you might get no or a |
3860 | Depending on your compiler and compiler settings, you might get no or a |
3387 | lot of warnings when compiling libev code. Some people are apparently |
3861 | lot of warnings when compiling libev code. Some people are apparently |
… | |
… | |
3408 | with any compiler warnings enabled unless you are prepared to cope with |
3882 | with any compiler warnings enabled unless you are prepared to cope with |
3409 | them (e.g. by ignoring them). Remember that warnings are just that: |
3883 | them (e.g. by ignoring them). Remember that warnings are just that: |
3410 | warnings, not errors, or proof of bugs. |
3884 | warnings, not errors, or proof of bugs. |
3411 | |
3885 | |
3412 | |
3886 | |
3413 | =head1 VALGRIND |
3887 | =head2 VALGRIND |
3414 | |
3888 | |
3415 | Valgrind has a special section here because it is a popular tool that is |
3889 | Valgrind has a special section here because it is a popular tool that is |
3416 | highly useful. Unfortunately, valgrind reports are very hard to interpret. |
3890 | highly useful. Unfortunately, valgrind reports are very hard to interpret. |
3417 | |
3891 | |
3418 | If you think you found a bug (memory leak, uninitialised data access etc.) |
3892 | If you think you found a bug (memory leak, uninitialised data access etc.) |
… | |
… | |
3421 | ==2274== definitely lost: 0 bytes in 0 blocks. |
3895 | ==2274== definitely lost: 0 bytes in 0 blocks. |
3422 | ==2274== possibly lost: 0 bytes in 0 blocks. |
3896 | ==2274== possibly lost: 0 bytes in 0 blocks. |
3423 | ==2274== still reachable: 256 bytes in 1 blocks. |
3897 | ==2274== still reachable: 256 bytes in 1 blocks. |
3424 | |
3898 | |
3425 | Then there is no memory leak, just as memory accounted to global variables |
3899 | Then there is no memory leak, just as memory accounted to global variables |
3426 | is not a memleak - the memory is still being refernced, and didn't leak. |
3900 | is not a memleak - the memory is still being referenced, and didn't leak. |
3427 | |
3901 | |
3428 | Similarly, under some circumstances, valgrind might report kernel bugs |
3902 | Similarly, under some circumstances, valgrind might report kernel bugs |
3429 | as if it were a bug in libev (e.g. in realloc or in the poll backend, |
3903 | as if it were a bug in libev (e.g. in realloc or in the poll backend, |
3430 | although an acceptable workaround has been found here), or it might be |
3904 | although an acceptable workaround has been found here), or it might be |
3431 | confused. |
3905 | confused. |
… | |
… | |
3441 | |
3915 | |
3442 | If you need, for some reason, empty reports from valgrind for your project |
3916 | If you need, for some reason, empty reports from valgrind for your project |
3443 | I suggest using suppression lists. |
3917 | I suggest using suppression lists. |
3444 | |
3918 | |
3445 | |
3919 | |
3446 | |
|
|
3447 | =head1 COMPLEXITIES |
|
|
3448 | |
|
|
3449 | In this section the complexities of (many of) the algorithms used inside |
|
|
3450 | libev will be explained. For complexity discussions about backends see the |
|
|
3451 | documentation for C<ev_default_init>. |
|
|
3452 | |
|
|
3453 | All of the following are about amortised time: If an array needs to be |
|
|
3454 | extended, libev needs to realloc and move the whole array, but this |
|
|
3455 | happens asymptotically never with higher number of elements, so O(1) might |
|
|
3456 | mean it might do a lengthy realloc operation in rare cases, but on average |
|
|
3457 | it is much faster and asymptotically approaches constant time. |
|
|
3458 | |
|
|
3459 | =over 4 |
|
|
3460 | |
|
|
3461 | =item Starting and stopping timer/periodic watchers: O(log skipped_other_timers) |
|
|
3462 | |
|
|
3463 | This means that, when you have a watcher that triggers in one hour and |
|
|
3464 | there are 100 watchers that would trigger before that then inserting will |
|
|
3465 | have to skip roughly seven (C<ld 100>) of these watchers. |
|
|
3466 | |
|
|
3467 | =item Changing timer/periodic watchers (by autorepeat or calling again): O(log skipped_other_timers) |
|
|
3468 | |
|
|
3469 | That means that changing a timer costs less than removing/adding them |
|
|
3470 | as only the relative motion in the event queue has to be paid for. |
|
|
3471 | |
|
|
3472 | =item Starting io/check/prepare/idle/signal/child/fork/async watchers: O(1) |
|
|
3473 | |
|
|
3474 | These just add the watcher into an array or at the head of a list. |
|
|
3475 | |
|
|
3476 | =item Stopping check/prepare/idle/fork/async watchers: O(1) |
|
|
3477 | |
|
|
3478 | =item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE)) |
|
|
3479 | |
|
|
3480 | These watchers are stored in lists then need to be walked to find the |
|
|
3481 | correct watcher to remove. The lists are usually short (you don't usually |
|
|
3482 | have many watchers waiting for the same fd or signal). |
|
|
3483 | |
|
|
3484 | =item Finding the next timer in each loop iteration: O(1) |
|
|
3485 | |
|
|
3486 | By virtue of using a binary or 4-heap, the next timer is always found at a |
|
|
3487 | fixed position in the storage array. |
|
|
3488 | |
|
|
3489 | =item Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd) |
|
|
3490 | |
|
|
3491 | A change means an I/O watcher gets started or stopped, which requires |
|
|
3492 | libev to recalculate its status (and possibly tell the kernel, depending |
|
|
3493 | on backend and whether C<ev_io_set> was used). |
|
|
3494 | |
|
|
3495 | =item Activating one watcher (putting it into the pending state): O(1) |
|
|
3496 | |
|
|
3497 | =item Priority handling: O(number_of_priorities) |
|
|
3498 | |
|
|
3499 | Priorities are implemented by allocating some space for each |
|
|
3500 | priority. When doing priority-based operations, libev usually has to |
|
|
3501 | linearly search all the priorities, but starting/stopping and activating |
|
|
3502 | watchers becomes O(1) with respect to priority handling. |
|
|
3503 | |
|
|
3504 | =item Sending an ev_async: O(1) |
|
|
3505 | |
|
|
3506 | =item Processing ev_async_send: O(number_of_async_watchers) |
|
|
3507 | |
|
|
3508 | =item Processing signals: O(max_signal_number) |
|
|
3509 | |
|
|
3510 | Sending involves a system call I<iff> there were no other C<ev_async_send> |
|
|
3511 | calls in the current loop iteration. Checking for async and signal events |
|
|
3512 | involves iterating over all running async watchers or all signal numbers. |
|
|
3513 | |
|
|
3514 | =back |
|
|
3515 | |
|
|
3516 | |
|
|
3517 | =head1 PORTABILITY |
3920 | =head1 PORTABILITY NOTES |
3518 | |
3921 | |
3519 | =head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS |
3922 | =head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS |
3520 | |
3923 | |
3521 | Win32 doesn't support any of the standards (e.g. POSIX) that libev |
3924 | Win32 doesn't support any of the standards (e.g. POSIX) that libev |
3522 | requires, and its I/O model is fundamentally incompatible with the POSIX |
3925 | requires, and its I/O model is fundamentally incompatible with the POSIX |
… | |
… | |
3667 | =back |
4070 | =back |
3668 | |
4071 | |
3669 | If you know of other additional requirements drop me a note. |
4072 | If you know of other additional requirements drop me a note. |
3670 | |
4073 | |
3671 | |
4074 | |
|
|
4075 | =head1 ALGORITHMIC COMPLEXITIES |
|
|
4076 | |
|
|
4077 | In this section the complexities of (many of) the algorithms used inside |
|
|
4078 | libev will be documented. For complexity discussions about backends see |
|
|
4079 | the documentation for C<ev_default_init>. |
|
|
4080 | |
|
|
4081 | All of the following are about amortised time: If an array needs to be |
|
|
4082 | extended, libev needs to realloc and move the whole array, but this |
|
|
4083 | happens asymptotically rarer with higher number of elements, so O(1) might |
|
|
4084 | mean that libev does a lengthy realloc operation in rare cases, but on |
|
|
4085 | average it is much faster and asymptotically approaches constant time. |
|
|
4086 | |
|
|
4087 | =over 4 |
|
|
4088 | |
|
|
4089 | =item Starting and stopping timer/periodic watchers: O(log skipped_other_timers) |
|
|
4090 | |
|
|
4091 | This means that, when you have a watcher that triggers in one hour and |
|
|
4092 | there are 100 watchers that would trigger before that, then inserting will |
|
|
4093 | have to skip roughly seven (C<ld 100>) of these watchers. |
|
|
4094 | |
|
|
4095 | =item Changing timer/periodic watchers (by autorepeat or calling again): O(log skipped_other_timers) |
|
|
4096 | |
|
|
4097 | That means that changing a timer costs less than removing/adding them, |
|
|
4098 | as only the relative motion in the event queue has to be paid for. |
|
|
4099 | |
|
|
4100 | =item Starting io/check/prepare/idle/signal/child/fork/async watchers: O(1) |
|
|
4101 | |
|
|
4102 | These just add the watcher into an array or at the head of a list. |
|
|
4103 | |
|
|
4104 | =item Stopping check/prepare/idle/fork/async watchers: O(1) |
|
|
4105 | |
|
|
4106 | =item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE)) |
|
|
4107 | |
|
|
4108 | These watchers are stored in lists, so they need to be walked to find the |
|
|
4109 | correct watcher to remove. The lists are usually short (you don't usually |
|
|
4110 | have many watchers waiting for the same fd or signal: one is typical, two |
|
|
4111 | is rare). |
|
|
4112 | |
|
|
4113 | =item Finding the next timer in each loop iteration: O(1) |
|
|
4114 | |
|
|
4115 | By virtue of using a binary or 4-heap, the next timer is always found at a |
|
|
4116 | fixed position in the storage array. |
|
|
4117 | |
|
|
4118 | =item Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd) |
|
|
4119 | |
|
|
4120 | A change means an I/O watcher gets started or stopped, which requires |
|
|
4121 | libev to recalculate its status (and possibly tell the kernel, depending |
|
|
4122 | on backend and whether C<ev_io_set> was used). |
|
|
4123 | |
|
|
4124 | =item Activating one watcher (putting it into the pending state): O(1) |
|
|
4125 | |
|
|
4126 | =item Priority handling: O(number_of_priorities) |
|
|
4127 | |
|
|
4128 | Priorities are implemented by allocating some space for each |
|
|
4129 | priority. When doing priority-based operations, libev usually has to |
|
|
4130 | linearly search all the priorities, but starting/stopping and activating |
|
|
4131 | watchers becomes O(1) with respect to priority handling. |
|
|
4132 | |
|
|
4133 | =item Sending an ev_async: O(1) |
|
|
4134 | |
|
|
4135 | =item Processing ev_async_send: O(number_of_async_watchers) |
|
|
4136 | |
|
|
4137 | =item Processing signals: O(max_signal_number) |
|
|
4138 | |
|
|
4139 | Sending involves a system call I<iff> there were no other C<ev_async_send> |
|
|
4140 | calls in the current loop iteration. Checking for async and signal events |
|
|
4141 | involves iterating over all running async watchers or all signal numbers. |
|
|
4142 | |
|
|
4143 | =back |
|
|
4144 | |
|
|
4145 | |
|
|
4146 | =head1 GLOSSARY |
|
|
4147 | |
|
|
4148 | =over 4 |
|
|
4149 | |
|
|
4150 | =item active |
|
|
4151 | |
|
|
4152 | A watcher is active as long as it has been started (has been attached to |
|
|
4153 | an event loop) but not yet stopped (disassociated from the event loop). |
|
|
4154 | |
|
|
4155 | =item application |
|
|
4156 | |
|
|
4157 | In this document, an application is whatever is using libev. |
|
|
4158 | |
|
|
4159 | =item callback |
|
|
4160 | |
|
|
4161 | The address of a function that is called when some event has been |
|
|
4162 | detected. Callbacks are being passed the event loop, the watcher that |
|
|
4163 | received the event, and the actual event bitset. |
|
|
4164 | |
|
|
4165 | =item callback invocation |
|
|
4166 | |
|
|
4167 | The act of calling the callback associated with a watcher. |
|
|
4168 | |
|
|
4169 | =item event |
|
|
4170 | |
|
|
4171 | A change of state of some external event, such as data now being available |
|
|
4172 | for reading on a file descriptor, time having passed or simply not having |
|
|
4173 | any other events happening anymore. |
|
|
4174 | |
|
|
4175 | In libev, events are represented as single bits (such as C<EV_READ> or |
|
|
4176 | C<EV_TIMEOUT>). |
|
|
4177 | |
|
|
4178 | =item event library |
|
|
4179 | |
|
|
4180 | A software package implementing an event model and loop. |
|
|
4181 | |
|
|
4182 | =item event loop |
|
|
4183 | |
|
|
4184 | An entity that handles and processes external events and converts them |
|
|
4185 | into callback invocations. |
|
|
4186 | |
|
|
4187 | =item event model |
|
|
4188 | |
|
|
4189 | The model used to describe how an event loop handles and processes |
|
|
4190 | watchers and events. |
|
|
4191 | |
|
|
4192 | =item pending |
|
|
4193 | |
|
|
4194 | A watcher is pending as soon as the corresponding event has been detected, |
|
|
4195 | and stops being pending as soon as the watcher will be invoked or its |
|
|
4196 | pending status is explicitly cleared by the application. |
|
|
4197 | |
|
|
4198 | A watcher can be pending, but not active. Stopping a watcher also clears |
|
|
4199 | its pending status. |
|
|
4200 | |
|
|
4201 | =item real time |
|
|
4202 | |
|
|
4203 | The physical time that is observed. It is apparently strictly monotonic :) |
|
|
4204 | |
|
|
4205 | =item wall-clock time |
|
|
4206 | |
|
|
4207 | The time and date as shown on clocks. Unlike real time, it can actually |
|
|
4208 | be wrong and jump forwards and backwards, e.g. when the you adjust your |
|
|
4209 | clock. |
|
|
4210 | |
|
|
4211 | =item watcher |
|
|
4212 | |
|
|
4213 | A data structure that describes interest in certain events. Watchers need |
|
|
4214 | to be started (attached to an event loop) before they can receive events. |
|
|
4215 | |
|
|
4216 | =item watcher invocation |
|
|
4217 | |
|
|
4218 | The act of calling the callback associated with a watcher. |
|
|
4219 | |
|
|
4220 | =back |
|
|
4221 | |
3672 | =head1 AUTHOR |
4222 | =head1 AUTHOR |
3673 | |
4223 | |
3674 | Marc Lehmann <libev@schmorp.de>. |
4224 | Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael Magnusson. |
3675 | |
4225 | |