… | |
… | |
56 | |
56 | |
57 | =over 4 |
57 | =over 4 |
58 | |
58 | |
59 | =item ev_tstamp ev_time () |
59 | =item ev_tstamp ev_time () |
60 | |
60 | |
61 | Returns the current time as libev would use it. |
61 | Returns the current time as libev would use it. Please note that the |
|
|
62 | C<ev_now> function is usually faster and also often returns the timestamp |
|
|
63 | you actually want to know. |
62 | |
64 | |
63 | =item int ev_version_major () |
65 | =item int ev_version_major () |
64 | |
66 | |
65 | =item int ev_version_minor () |
67 | =item int ev_version_minor () |
66 | |
68 | |
… | |
… | |
241 | |
243 | |
242 | =item ev_unloop (loop, how) |
244 | =item ev_unloop (loop, how) |
243 | |
245 | |
244 | Can be used to make a call to C<ev_loop> return early (but only after it |
246 | Can be used to make a call to C<ev_loop> return early (but only after it |
245 | has processed all outstanding events). The C<how> argument must be either |
247 | has processed all outstanding events). The C<how> argument must be either |
246 | C<EVUNLOOP_ONCE>, which will make the innermost C<ev_loop> call return, or |
248 | C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or |
247 | C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return. |
249 | C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return. |
248 | |
250 | |
249 | =item ev_ref (loop) |
251 | =item ev_ref (loop) |
250 | |
252 | |
251 | =item ev_unref (loop) |
253 | =item ev_unref (loop) |
… | |
… | |
417 | in each iteration of the event loop (This behaviour is called |
419 | in each iteration of the event loop (This behaviour is called |
418 | level-triggering because you keep receiving events as long as the |
420 | level-triggering because you keep receiving events as long as the |
419 | condition persists. Remember you can stop the watcher if you don't want to |
421 | condition persists. Remember you can stop the watcher if you don't want to |
420 | act on the event and neither want to receive future events). |
422 | act on the event and neither want to receive future events). |
421 | |
423 | |
422 | In general you can register as many read and/or write event watchers oer |
424 | In general you can register as many read and/or write event watchers per |
423 | fd as you want (as long as you don't confuse yourself). Setting all file |
425 | fd as you want (as long as you don't confuse yourself). Setting all file |
424 | descriptors to non-blocking mode is also usually a good idea (but not |
426 | descriptors to non-blocking mode is also usually a good idea (but not |
425 | required if you know what you are doing). |
427 | required if you know what you are doing). |
426 | |
428 | |
427 | You have to be careful with dup'ed file descriptors, though. Some backends |
429 | You have to be careful with dup'ed file descriptors, though. Some backends |
428 | (the linux epoll backend is a notable example) cannot handle dup'ed file |
430 | (the linux epoll backend is a notable example) cannot handle dup'ed file |
429 | descriptors correctly if you register interest in two or more fds pointing |
431 | descriptors correctly if you register interest in two or more fds pointing |
430 | to the same file/socket etc. description. |
432 | to the same underlying file/socket etc. description (that is, they share |
|
|
433 | the same underlying "file open"). |
431 | |
434 | |
432 | If you must do this, then force the use of a known-to-be-good backend |
435 | If you must do this, then force the use of a known-to-be-good backend |
433 | (at the time of this writing, this includes only EVMETHOD_SELECT and |
436 | (at the time of this writing, this includes only EVMETHOD_SELECT and |
434 | EVMETHOD_POLL). |
437 | EVMETHOD_POLL). |
435 | |
438 | |
… | |
… | |
449 | |
452 | |
450 | Timer watchers are simple relative timers that generate an event after a |
453 | Timer watchers are simple relative timers that generate an event after a |
451 | given time, and optionally repeating in regular intervals after that. |
454 | given time, and optionally repeating in regular intervals after that. |
452 | |
455 | |
453 | The timers are based on real time, that is, if you register an event that |
456 | The timers are based on real time, that is, if you register an event that |
454 | times out after an hour and youreset your system clock to last years |
457 | times out after an hour and you reset your system clock to last years |
455 | time, it will still time out after (roughly) and hour. "Roughly" because |
458 | time, it will still time out after (roughly) and hour. "Roughly" because |
456 | detecting time jumps is hard, and soem inaccuracies are unavoidable (the |
459 | detecting time jumps is hard, and soem inaccuracies are unavoidable (the |
457 | monotonic clock option helps a lot here). |
460 | monotonic clock option helps a lot here). |
458 | |
461 | |
459 | The relative timeouts are calculated relative to the C<ev_now ()> |
462 | The relative timeouts are calculated relative to the C<ev_now ()> |
460 | time. This is usually the right thing as this timestamp refers to the time |
463 | time. This is usually the right thing as this timestamp refers to the time |
461 | of the event triggering whatever timeout you are modifying/starting. If |
464 | of the event triggering whatever timeout you are modifying/starting. If |
462 | you suspect event processing to be delayed and you *need* to base the timeout |
465 | you suspect event processing to be delayed and you *need* to base the timeout |
463 | ion the current time, use something like this to adjust for this: |
466 | on the current time, use something like this to adjust for this: |
464 | |
467 | |
465 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
468 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
466 | |
469 | |
467 | =over 4 |
470 | =over 4 |
468 | |
471 | |
… | |
… | |
476 | later, again, and again, until stopped manually. |
479 | later, again, and again, until stopped manually. |
477 | |
480 | |
478 | The timer itself will do a best-effort at avoiding drift, that is, if you |
481 | The timer itself will do a best-effort at avoiding drift, that is, if you |
479 | configure a timer to trigger every 10 seconds, then it will trigger at |
482 | configure a timer to trigger every 10 seconds, then it will trigger at |
480 | exactly 10 second intervals. If, however, your program cannot keep up with |
483 | exactly 10 second intervals. If, however, your program cannot keep up with |
481 | the timer (ecause it takes longer than those 10 seconds to do stuff) the |
484 | the timer (because it takes longer than those 10 seconds to do stuff) the |
482 | timer will not fire more than once per event loop iteration. |
485 | timer will not fire more than once per event loop iteration. |
483 | |
486 | |
484 | =item ev_timer_again (loop) |
487 | =item ev_timer_again (loop) |
485 | |
488 | |
486 | This will act as if the timer timed out and restart it again if it is |
489 | This will act as if the timer timed out and restart it again if it is |
… | |
… | |
582 | (that is, the lowest time value larger than to the second argument). It |
585 | (that is, the lowest time value larger than to the second argument). It |
583 | will usually be called just before the callback will be triggered, but |
586 | will usually be called just before the callback will be triggered, but |
584 | might be called at other times, too. |
587 | might be called at other times, too. |
585 | |
588 | |
586 | NOTE: I<< This callback must always return a time that is later than the |
589 | 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. |
590 | passed C<now> value >>. Not even C<now> itself will do, it I<must> be larger. |
588 | |
591 | |
589 | This can be used to create very complex timers, such as a timer that |
592 | This can be used to create very complex timers, such as a timer that |
590 | triggers on each midnight, local time. To do this, you would calculate the |
593 | triggers on each midnight, local time. To do this, you would calculate the |
591 | next midnight after C<now> and return the timestamp value for this. How you do this |
594 | next midnight after C<now> and return the timestamp value for this. How |
592 | is, again, up to you (but it is not trivial). |
595 | you do this is, again, up to you (but it is not trivial, which is the main |
|
|
596 | reason I omitted it as an example). |
593 | |
597 | |
594 | =back |
598 | =back |
595 | |
599 | |
596 | =item ev_periodic_again (loop, ev_periodic *) |
600 | =item ev_periodic_again (loop, ev_periodic *) |
597 | |
601 | |
… | |
… | |
676 | =back |
680 | =back |
677 | |
681 | |
678 | =head2 C<ev_prepare> and C<ev_check> - customise your event loop |
682 | =head2 C<ev_prepare> and C<ev_check> - customise your event loop |
679 | |
683 | |
680 | Prepare and check watchers are usually (but not always) used in tandem: |
684 | Prepare and check watchers are usually (but not always) used in tandem: |
681 | Prepare watchers get invoked before the process blocks and check watchers |
685 | prepare watchers get invoked before the process blocks and check watchers |
682 | afterwards. |
686 | afterwards. |
683 | |
687 | |
684 | Their main purpose is to integrate other event mechanisms into libev. This |
688 | Their main purpose is to integrate other event mechanisms into libev. This |
685 | could be used, for example, to track variable changes, implement your own |
689 | could be used, for example, to track variable changes, implement your own |
686 | watchers, integrate net-snmp or a coroutine library and lots more. |
690 | watchers, integrate net-snmp or a coroutine library and lots more. |
… | |
… | |
689 | to be watched by the other library, registering C<ev_io> watchers for |
693 | to be watched by the other library, registering C<ev_io> watchers for |
690 | them and starting an C<ev_timer> watcher for any timeouts (many libraries |
694 | them and starting an C<ev_timer> watcher for any timeouts (many libraries |
691 | provide just this functionality). Then, in the check watcher you check for |
695 | provide just this functionality). Then, in the check watcher you check for |
692 | any events that occured (by checking the pending status of all watchers |
696 | any events that occured (by checking the pending status of all watchers |
693 | and stopping them) and call back into the library. The I/O and timer |
697 | 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, |
698 | callbacks will never actually be called (but must be valid nevertheless, |
695 | because you never know, you know?). |
699 | because you never know, you know?). |
696 | |
700 | |
697 | As another example, the Perl Coro module uses these hooks to integrate |
701 | As another example, the Perl Coro module uses these hooks to integrate |
698 | coroutines into libev programs, by yielding to other active coroutines |
702 | coroutines into libev programs, by yielding to other active coroutines |
699 | during each prepare and only letting the process block if no coroutines |
703 | during each prepare and only letting the process block if no coroutines |
700 | are ready to run (its actually more complicated, it only runs coroutines |
704 | are ready to run (it's actually more complicated: it only runs coroutines |
701 | with priority higher than the event loop and one lower priority once, |
705 | with priority higher than or equal to the event loop and one coroutine |
702 | using idle watchers to keep the event loop from blocking if lower-priority |
706 | of lower priority, but only once, using idle watchers to keep the event |
703 | coroutines exist, thus mapping low-priority coroutines to idle/background |
707 | loop from blocking if lower-priority coroutines are active, thus mapping |
704 | tasks). |
708 | low-priority coroutines to idle/background tasks). |
705 | |
709 | |
706 | =over 4 |
710 | =over 4 |
707 | |
711 | |
708 | =item ev_prepare_init (ev_prepare *, callback) |
712 | =item ev_prepare_init (ev_prepare *, callback) |
709 | |
713 | |
… | |
… | |
724 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
728 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
725 | |
729 | |
726 | This function combines a simple timer and an I/O watcher, calls your |
730 | This function combines a simple timer and an I/O watcher, calls your |
727 | callback on whichever event happens first and automatically stop both |
731 | callback on whichever event happens first and automatically stop both |
728 | watchers. This is useful if you want to wait for a single event on an fd |
732 | watchers. This is useful if you want to wait for a single event on an fd |
729 | or timeout without havign to allocate/configure/start/stop/free one or |
733 | or timeout without having to allocate/configure/start/stop/free one or |
730 | more watchers yourself. |
734 | more watchers yourself. |
731 | |
735 | |
732 | If C<fd> is less than 0, then no I/O watcher will be started and events |
736 | If C<fd> is less than 0, then no I/O watcher will be started and events |
733 | is being ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and |
737 | is being ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and |
734 | C<events> set will be craeted and started. |
738 | C<events> set will be craeted and started. |
… | |
… | |
737 | started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and |
741 | started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and |
738 | repeat = 0) will be started. While C<0> is a valid timeout, it is of |
742 | repeat = 0) will be started. While C<0> is a valid timeout, it is of |
739 | dubious value. |
743 | dubious value. |
740 | |
744 | |
741 | The callback has the type C<void (*cb)(int revents, void *arg)> and gets |
745 | The callback has the type C<void (*cb)(int revents, void *arg)> and gets |
742 | passed an events set like normal event callbacks (with a combination of |
746 | passed an C<revents> set like normal event callbacks (a combination of |
743 | C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg> |
747 | C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg> |
744 | value passed to C<ev_once>: |
748 | value passed to C<ev_once>: |
745 | |
749 | |
746 | static void stdin_ready (int revents, void *arg) |
750 | static void stdin_ready (int revents, void *arg) |
747 | { |
751 | { |
… | |
… | |
768 | |
772 | |
769 | Feed an event as if the given signal occured (loop must be the default loop!). |
773 | Feed an event as if the given signal occured (loop must be the default loop!). |
770 | |
774 | |
771 | =back |
775 | =back |
772 | |
776 | |
|
|
777 | =head1 LIBEVENT EMULATION |
|
|
778 | |
|
|
779 | Libev offers a compatibility emulation layer for libevent. It cannot |
|
|
780 | emulate the internals of libevent, so here are some usage hints: |
|
|
781 | |
|
|
782 | =over 4 |
|
|
783 | |
|
|
784 | =item * Use it by including <event.h>, as usual. |
|
|
785 | |
|
|
786 | =item * The following members are fully supported: ev_base, ev_callback, |
|
|
787 | ev_arg, ev_fd, ev_res, ev_events. |
|
|
788 | |
|
|
789 | =item * Avoid using ev_flags and the EVLIST_*-macros, while it is |
|
|
790 | maintained by libev, it does not work exactly the same way as in libevent (consider |
|
|
791 | it a private API). |
|
|
792 | |
|
|
793 | =item * Priorities are not currently supported. Initialising priorities |
|
|
794 | will fail and all watchers will have the same priority, even though there |
|
|
795 | is an ev_pri field. |
|
|
796 | |
|
|
797 | =item * Other members are not supported. |
|
|
798 | |
|
|
799 | =item * The libev emulation is I<not> ABI compatible to libevent, you need |
|
|
800 | to use the libev header file and library. |
|
|
801 | |
|
|
802 | =back |
|
|
803 | |
|
|
804 | =head1 C++ SUPPORT |
|
|
805 | |
|
|
806 | TBD. |
|
|
807 | |
773 | =head1 AUTHOR |
808 | =head1 AUTHOR |
774 | |
809 | |
775 | Marc Lehmann <libev@schmorp.de>. |
810 | Marc Lehmann <libev@schmorp.de>. |
776 | |
811 | |