… | |
… | |
39 | F<README.embed> in the libev distribution. If libev was configured without |
39 | F<README.embed> in the libev distribution. If libev was configured without |
40 | support for multiple event loops, then all functions taking an initial |
40 | support for multiple event loops, then all functions taking an initial |
41 | argument of name C<loop> (which is always of type C<struct ev_loop *>) |
41 | argument of name C<loop> (which is always of type C<struct ev_loop *>) |
42 | will not have this argument. |
42 | will not have this argument. |
43 | |
43 | |
44 | =head1 TIME AND OTHER GLOBAL FUNCTIONS |
44 | =head1 TIME REPRESENTATION |
45 | |
45 | |
46 | Libev represents time as a single floating point number, representing the |
46 | Libev represents time as a single floating point number, representing the |
47 | (fractional) number of seconds since the (POSIX) epoch (somewhere near |
47 | (fractional) number of seconds since the (POSIX) epoch (somewhere near |
48 | the beginning of 1970, details are complicated, don't ask). This type is |
48 | the beginning of 1970, details are complicated, don't ask). This type is |
49 | called C<ev_tstamp>, which is what you should use too. It usually aliases |
49 | called C<ev_tstamp>, which is what you should use too. It usually aliases |
50 | to the double type in C. |
50 | to the double type in C. |
|
|
51 | |
|
|
52 | =head1 GLOBAL FUNCTIONS |
|
|
53 | |
|
|
54 | These functions can be called anytime, even before initialising the |
|
|
55 | library in any way. |
51 | |
56 | |
52 | =over 4 |
57 | =over 4 |
53 | |
58 | |
54 | =item ev_tstamp ev_time () |
59 | =item ev_tstamp ev_time () |
55 | |
60 | |
… | |
… | |
99 | An event loop is described by a C<struct ev_loop *>. The library knows two |
104 | An event loop is described by a C<struct ev_loop *>. The library knows two |
100 | types of such loops, the I<default> loop, which supports signals and child |
105 | types of such loops, the I<default> loop, which supports signals and child |
101 | events, and dynamically created loops which do not. |
106 | events, and dynamically created loops which do not. |
102 | |
107 | |
103 | If you use threads, a common model is to run the default event loop |
108 | If you use threads, a common model is to run the default event loop |
104 | in your main thread (or in a separate thrad) and for each thread you |
109 | in your main thread (or in a separate thread) and for each thread you |
105 | create, you also create another event loop. Libev itself does no locking |
110 | create, you also create another event loop. Libev itself does no locking |
106 | whatsoever, so if you mix calls to the same event loop in different |
111 | whatsoever, so if you mix calls to the same event loop in different |
107 | threads, make sure you lock (this is usually a bad idea, though, even if |
112 | threads, make sure you lock (this is usually a bad idea, though, even if |
108 | done correctly, because it's hideous and inefficient). |
113 | done correctly, because it's hideous and inefficient). |
109 | |
114 | |
… | |
… | |
299 | |
304 | |
300 | As long as your watcher is active (has been started but not stopped) you |
305 | As long as your watcher is active (has been started but not stopped) you |
301 | must not touch the values stored in it. Most specifically you must never |
306 | must not touch the values stored in it. Most specifically you must never |
302 | reinitialise it or call its set method. |
307 | reinitialise it or call its set method. |
303 | |
308 | |
304 | You cna check whether an event is active by calling the C<ev_is_active |
309 | You can check whether an event is active by calling the C<ev_is_active |
305 | (watcher *)> macro. To see whether an event is outstanding (but the |
310 | (watcher *)> macro. To see whether an event is outstanding (but the |
306 | callback for it has not been called yet) you cna use the C<ev_is_pending |
311 | callback for it has not been called yet) you can use the C<ev_is_pending |
307 | (watcher *)> macro. |
312 | (watcher *)> macro. |
308 | |
313 | |
309 | Each and every callback receives the event loop pointer as first, the |
314 | Each and every callback receives the event loop pointer as first, the |
310 | registered watcher structure as second, and a bitset of received events as |
315 | registered watcher structure as second, and a bitset of received events as |
311 | third argument. |
316 | third argument. |
312 | |
317 | |
313 | The rceeived events usually include a single bit per event type received |
318 | The received events usually include a single bit per event type received |
314 | (you can receive multiple events at the same time). The possible bit masks |
319 | (you can receive multiple events at the same time). The possible bit masks |
315 | are: |
320 | are: |
316 | |
321 | |
317 | =over 4 |
322 | =over 4 |
318 | |
323 | |
… | |
… | |
372 | =back |
377 | =back |
373 | |
378 | |
374 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
379 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
375 | |
380 | |
376 | Each watcher has, by default, a member C<void *data> that you can change |
381 | Each watcher has, by default, a member C<void *data> that you can change |
377 | and read at any time, libev will completely ignore it. This cna be used |
382 | and read at any time, libev will completely ignore it. This can be used |
378 | to associate arbitrary data with your watcher. If you need more data and |
383 | to associate arbitrary data with your watcher. If you need more data and |
379 | don't want to allocate memory and store a pointer to it in that data |
384 | don't want to allocate memory and store a pointer to it in that data |
380 | member, you can also "subclass" the watcher type and provide your own |
385 | member, you can also "subclass" the watcher type and provide your own |
381 | data: |
386 | data: |
382 | |
387 | |
… | |
… | |
409 | =head2 C<ev_io> - is this file descriptor readable or writable |
414 | =head2 C<ev_io> - is this file descriptor readable or writable |
410 | |
415 | |
411 | I/O watchers check whether a file descriptor is readable or writable |
416 | I/O watchers check whether a file descriptor is readable or writable |
412 | in each iteration of the event loop (This behaviour is called |
417 | in each iteration of the event loop (This behaviour is called |
413 | level-triggering because you keep receiving events as long as the |
418 | level-triggering because you keep receiving events as long as the |
414 | condition persists. Remember you cna stop the watcher if you don't want to |
419 | condition persists. Remember you can stop the watcher if you don't want to |
415 | act on the event and neither want to receive future events). |
420 | act on the event and neither want to receive future events). |
416 | |
421 | |
417 | In general you can register as many read and/or write event watchers oer |
422 | In general you can register as many read and/or write event watchers oer |
418 | fd as you want (as long as you don't confuse yourself). Setting all file |
423 | fd as you want (as long as you don't confuse yourself). Setting all file |
419 | descriptors to non-blocking mode is also usually a good idea (but not |
424 | descriptors to non-blocking mode is also usually a good idea (but not |
… | |
… | |
495 | state where you do not expect data to travel on the socket, you can stop |
500 | state where you do not expect data to travel on the socket, you can stop |
496 | the timer, and again will automatically restart it if need be. |
501 | the timer, and again will automatically restart it if need be. |
497 | |
502 | |
498 | =back |
503 | =back |
499 | |
504 | |
500 | =head2 C<ev_periodic> - to cron or not to cron it |
505 | =head2 C<ev_periodic> - to cron or not to cron |
501 | |
506 | |
502 | Periodic watchers are also timers of a kind, but they are very versatile |
507 | Periodic watchers are also timers of a kind, but they are very versatile |
503 | (and unfortunately a bit complex). |
508 | (and unfortunately a bit complex). |
504 | |
509 | |
505 | Unlike C<ev_timer>'s, they are not based on real time (or relative time) |
510 | Unlike C<ev_timer>'s, they are not based on real time (or relative time) |
… | |
… | |
544 | |
549 | |
545 | ev_periodic_set (&periodic, 0., 3600., 0); |
550 | ev_periodic_set (&periodic, 0., 3600., 0); |
546 | |
551 | |
547 | This doesn't mean there will always be 3600 seconds in between triggers, |
552 | This doesn't mean there will always be 3600 seconds in between triggers, |
548 | but only that the the callback will be called when the system time shows a |
553 | but only that the the callback will be called when the system time shows a |
549 | full hour (UTC), or more correct, when the system time is evenly divisible |
554 | full hour (UTC), or more correctly, when the system time is evenly divisible |
550 | by 3600. |
555 | by 3600. |
551 | |
556 | |
552 | Another way to think about it (for the mathematically inclined) is that |
557 | Another way to think about it (for the mathematically inclined) is that |
553 | C<ev_periodic> will try to run the callback in this mode at the next possible |
558 | C<ev_periodic> will try to run the callback in this mode at the next possible |
554 | time where C<time = at (mod interval)>, regardless of any time jumps. |
559 | time where C<time = at (mod interval)>, regardless of any time jumps. |
… | |
… | |
558 | In this mode the values for C<interval> and C<at> are both being |
563 | In this mode the values for C<interval> and C<at> are both being |
559 | ignored. Instead, each time the periodic watcher gets scheduled, the |
564 | ignored. Instead, each time the periodic watcher gets scheduled, the |
560 | reschedule callback will be called with the watcher as first, and the |
565 | reschedule callback will be called with the watcher as first, and the |
561 | current time as second argument. |
566 | current time as second argument. |
562 | |
567 | |
563 | NOTE: I<This callback MUST NOT stop or destroy the periodic or any other |
568 | NOTE: I<This callback MUST NOT stop or destroy any periodic watcher, |
564 | periodic watcher, ever, or make any event loop modificstions>. If you need |
569 | ever, or make any event loop modifications>. If you need to stop it, |
565 | to stop it, return 1e30 (or so, fudge fudge) and stop it afterwards. |
570 | return C<now + 1e30> (or so, fudge fudge) and stop it afterwards (e.g. by |
|
|
571 | starting a prepare watcher). |
566 | |
572 | |
567 | Its prototype is c<ev_tstamp (*reschedule_cb)(struct ev_periodic *w, |
573 | Its prototype is C<ev_tstamp (*reschedule_cb)(struct ev_periodic *w, |
568 | ev_tstamp now)>, e.g.: |
574 | ev_tstamp now)>, e.g.: |
569 | |
575 | |
570 | static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) |
576 | static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) |
571 | { |
577 | { |
572 | return now + 60.; |
578 | return now + 60.; |
… | |
… | |
575 | It must return the next time to trigger, based on the passed time value |
581 | It must return the next time to trigger, based on the passed time value |
576 | (that is, the lowest time value larger than to the second argument). It |
582 | (that is, the lowest time value larger than to the second argument). It |
577 | will usually be called just before the callback will be triggered, but |
583 | will usually be called just before the callback will be triggered, but |
578 | might be called at other times, too. |
584 | might be called at other times, too. |
579 | |
585 | |
|
|
586 | NOTE: I<< This callback must always return a time that is later than the |
|
|
587 | passed C<now> value >>. Not even C<now> itself will do, it must be larger. |
|
|
588 | |
580 | This can be used to create very complex timers, such as a timer that |
589 | This can be used to create very complex timers, such as a timer that |
581 | triggers on each midnight, local time. To do this, you would calculate the |
590 | triggers on each midnight, local time. To do this, you would calculate the |
582 | next midnight after C<now> and return the timestamp value for this. How you do this |
591 | next midnight after C<now> and return the timestamp value for this. How you do this |
583 | is, again, up to you (but it is not trivial). |
592 | is, again, up to you (but it is not trivial). |
584 | |
593 | |
… | |
… | |
598 | Signal watchers will trigger an event when the process receives a specific |
607 | Signal watchers will trigger an event when the process receives a specific |
599 | signal one or more times. Even though signals are very asynchronous, libev |
608 | signal one or more times. Even though signals are very asynchronous, libev |
600 | will try it's best to deliver signals synchronously, i.e. as part of the |
609 | will try it's best to deliver signals synchronously, i.e. as part of the |
601 | normal event processing, like any other event. |
610 | normal event processing, like any other event. |
602 | |
611 | |
603 | You cna configure as many watchers as you like per signal. Only when the |
612 | You can configure as many watchers as you like per signal. Only when the |
604 | first watcher gets started will libev actually register a signal watcher |
613 | first watcher gets started will libev actually register a signal watcher |
605 | with the kernel (thus it coexists with your own signal handlers as long |
614 | with the kernel (thus it coexists with your own signal handlers as long |
606 | as you don't register any with libev). Similarly, when the last signal |
615 | as you don't register any with libev). Similarly, when the last signal |
607 | watcher for a signal is stopped libev will reset the signal handler to |
616 | watcher for a signal is stopped libev will reset the signal handler to |
608 | SIG_DFL (regardless of what it was set to before). |
617 | SIG_DFL (regardless of what it was set to before). |
… | |
… | |
630 | =item ev_child_set (ev_child *, int pid) |
639 | =item ev_child_set (ev_child *, int pid) |
631 | |
640 | |
632 | Configures the watcher to wait for status changes of process C<pid> (or |
641 | Configures the watcher to wait for status changes of process C<pid> (or |
633 | I<any> process if C<pid> is specified as C<0>). The callback can look |
642 | I<any> process if C<pid> is specified as C<0>). The callback can look |
634 | at the C<rstatus> member of the C<ev_child> watcher structure to see |
643 | at the C<rstatus> member of the C<ev_child> watcher structure to see |
635 | the status word (use the macros from C<sys/wait.h>). The C<rpid> member |
644 | the status word (use the macros from C<sys/wait.h> and see your systems |
636 | contains the pid of the process causing the status change. |
645 | C<waitpid> documentation). The C<rpid> member contains the pid of the |
|
|
646 | process causing the status change. |
637 | |
647 | |
638 | =back |
648 | =back |
639 | |
649 | |
640 | =head2 C<ev_idle> - when you've got nothing better to do |
650 | =head2 C<ev_idle> - when you've got nothing better to do |
641 | |
651 | |
642 | Idle watchers trigger events when there are no other I/O or timer (or |
652 | Idle watchers trigger events when there are no other events are pending |
643 | periodic) events pending. That is, as long as your process is busy |
653 | (prepare, check and other idle watchers do not count). That is, as long |
644 | handling sockets or timeouts it will not be called. But when your process |
654 | as your process is busy handling sockets or timeouts (or even signals, |
645 | is idle all idle watchers are being called again and again - until |
655 | imagine) it will not be triggered. But when your process is idle all idle |
|
|
656 | watchers are being called again and again, once per event loop iteration - |
646 | stopped, that is, or your process receives more events. |
657 | until stopped, that is, or your process receives more events and becomes |
|
|
658 | busy. |
647 | |
659 | |
648 | The most noteworthy effect is that as long as any idle watchers are |
660 | The most noteworthy effect is that as long as any idle watchers are |
649 | active, the process will not block when waiting for new events. |
661 | active, the process will not block when waiting for new events. |
650 | |
662 | |
651 | Apart from keeping your process non-blocking (which is a useful |
663 | Apart from keeping your process non-blocking (which is a useful |
… | |
… | |
661 | kind. There is a C<ev_idle_set> macro, but using it is utterly pointless, |
673 | kind. There is a C<ev_idle_set> macro, but using it is utterly pointless, |
662 | believe me. |
674 | believe me. |
663 | |
675 | |
664 | =back |
676 | =back |
665 | |
677 | |
666 | =head2 prepare and check - your hooks into the event loop |
678 | =head2 C<ev_prepare> and C<ev_check> - customise your event loop |
667 | |
679 | |
668 | Prepare and check watchers usually (but not always) are used in |
680 | Prepare and check watchers are usually (but not always) used in tandem: |
669 | tandom. Prepare watchers get invoked before the process blocks and check |
681 | Prepare watchers get invoked before the process blocks and check watchers |
670 | watchers afterwards. |
682 | afterwards. |
671 | |
683 | |
672 | Their main purpose is to integrate other event mechanisms into libev. This |
684 | Their main purpose is to integrate other event mechanisms into libev. This |
673 | could be used, for example, to track variable changes, implement your own |
685 | could be used, for example, to track variable changes, implement your own |
674 | watchers, integrate net-snmp or a coroutine library and lots more. |
686 | watchers, integrate net-snmp or a coroutine library and lots more. |
675 | |
687 | |
676 | This is done by examining in each prepare call which file descriptors need |
688 | This is done by examining in each prepare call which file descriptors need |
677 | to be watched by the other library, registering C<ev_io> watchers for them |
689 | to be watched by the other library, registering C<ev_io> watchers for |
678 | and starting an C<ev_timer> watcher for any timeouts (many libraries provide |
690 | them and starting an C<ev_timer> watcher for any timeouts (many libraries |
679 | just this functionality). Then, in the check watcher you check for any |
691 | provide just this functionality). Then, in the check watcher you check for |
680 | events that occured (by making your callbacks set soem flags for example) |
692 | any events that occured (by checking the pending status of all watchers |
681 | and call back into the library. |
693 | and stopping them) and call back into the library. The I/O and timer |
|
|
694 | callbacks will never actually be called (but must be valid neverthelles, |
|
|
695 | because you never know, you know?). |
682 | |
696 | |
683 | As another example, the perl Coro module uses these hooks to integrate |
697 | As another example, the Perl Coro module uses these hooks to integrate |
684 | coroutines into libev programs, by yielding to other active coroutines |
698 | coroutines into libev programs, by yielding to other active coroutines |
685 | during each prepare and only letting the process block if no coroutines |
699 | during each prepare and only letting the process block if no coroutines |
686 | are ready to run. |
700 | are ready to run (its actually more complicated, it only runs coroutines |
|
|
701 | with priority higher than the event loop and one lower priority once, |
|
|
702 | using idle watchers to keep the event loop from blocking if lower-priority |
|
|
703 | coroutines exist, thus mapping low-priority coroutines to idle/background |
|
|
704 | tasks). |
687 | |
705 | |
688 | =over 4 |
706 | =over 4 |
689 | |
707 | |
690 | =item ev_prepare_init (ev_prepare *, callback) |
708 | =item ev_prepare_init (ev_prepare *, callback) |
691 | |
709 | |
692 | =item ev_check_init (ev_check *, callback) |
710 | =item ev_check_init (ev_check *, callback) |
693 | |
711 | |
694 | Initialises and configures the prepare or check watcher - they have no |
712 | Initialises and configures the prepare or check watcher - they have no |
695 | parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set> |
713 | parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set> |
696 | macros, but using them is utterly, utterly pointless. |
714 | macros, but using them is utterly, utterly and completely pointless. |
697 | |
715 | |
698 | =back |
716 | =back |
699 | |
717 | |
700 | =head1 OTHER FUNCTIONS |
718 | =head1 OTHER FUNCTIONS |
701 | |
719 | |
702 | There are some other fucntions of possible interest. Described. Here. Now. |
720 | There are some other functions of possible interest. Described. Here. Now. |
703 | |
721 | |
704 | =over 4 |
722 | =over 4 |
705 | |
723 | |
706 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
724 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
707 | |
725 | |
… | |
… | |
709 | callback on whichever event happens first and automatically stop both |
727 | callback on whichever event happens first and automatically stop both |
710 | watchers. This is useful if you want to wait for a single event on an fd |
728 | watchers. This is useful if you want to wait for a single event on an fd |
711 | or timeout without havign to allocate/configure/start/stop/free one or |
729 | or timeout without havign to allocate/configure/start/stop/free one or |
712 | more watchers yourself. |
730 | more watchers yourself. |
713 | |
731 | |
714 | If C<fd> is less than 0, then no I/O watcher will be started and events is |
732 | If C<fd> is less than 0, then no I/O watcher will be started and events |
715 | ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and C<events> set |
733 | is being ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and |
716 | will be craeted and started. |
734 | C<events> set will be craeted and started. |
717 | |
735 | |
718 | If C<timeout> is less than 0, then no timeout watcher will be |
736 | If C<timeout> is less than 0, then no timeout watcher will be |
719 | started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and repeat |
737 | started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and |
720 | = 0) will be started. |
738 | repeat = 0) will be started. While C<0> is a valid timeout, it is of |
|
|
739 | dubious value. |
721 | |
740 | |
722 | The callback has the type C<void (*cb)(int revents, void *arg)> and |
741 | The callback has the type C<void (*cb)(int revents, void *arg)> and gets |
723 | gets passed an events set (normally a combination of C<EV_ERROR>, C<EV_READ>, |
742 | passed an events set like normal event callbacks (with a combination of |
724 | C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg> value passed to C<ev_once>: |
743 | C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg> |
|
|
744 | value passed to C<ev_once>: |
725 | |
745 | |
726 | static void stdin_ready (int revents, void *arg) |
746 | static void stdin_ready (int revents, void *arg) |
727 | { |
747 | { |
728 | if (revents & EV_TIMEOUT) |
748 | if (revents & EV_TIMEOUT) |
729 | /* doh, nothing entered */ |
749 | /* doh, nothing entered */; |
730 | else if (revents & EV_READ) |
750 | else if (revents & EV_READ) |
731 | /* stdin might have data for us, joy! */ |
751 | /* stdin might have data for us, joy! */; |
732 | } |
752 | } |
733 | |
753 | |
734 | ev_once (STDIN_FILENO, EV_READm 10., stdin_ready, 0); |
754 | ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
735 | |
755 | |
736 | =item ev_feed_event (loop, watcher, int events) |
756 | =item ev_feed_event (loop, watcher, int events) |
737 | |
757 | |
738 | Feeds the given event set into the event loop, as if the specified event |
758 | Feeds the given event set into the event loop, as if the specified event |
739 | has happened for the specified watcher (which must be a pointer to an |
759 | had happened for the specified watcher (which must be a pointer to an |
740 | initialised but not necessarily active event watcher). |
760 | initialised but not necessarily started event watcher). |
741 | |
761 | |
742 | =item ev_feed_fd_event (loop, int fd, int revents) |
762 | =item ev_feed_fd_event (loop, int fd, int revents) |
743 | |
763 | |
744 | Feed an event on the given fd, as if a file descriptor backend detected it. |
764 | Feed an event on the given fd, as if a file descriptor backend detected |
|
|
765 | the given events it. |
745 | |
766 | |
746 | =item ev_feed_signal_event (loop, int signum) |
767 | =item ev_feed_signal_event (loop, int signum) |
747 | |
768 | |
748 | Feed an event as if the given signal occured (loop must be the default loop!). |
769 | Feed an event as if the given signal occured (loop must be the default loop!). |
749 | |
770 | |