… | |
… | |
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 | |
… | |
… | |
237 | |
239 | |
238 | This flags value could be used to implement alternative looping |
240 | This flags value could be used to implement alternative looping |
239 | constructs, but the C<prepare> and C<check> watchers provide a better and |
241 | constructs, but the C<prepare> and C<check> watchers provide a better and |
240 | more generic mechanism. |
242 | more generic mechanism. |
241 | |
243 | |
|
|
244 | Here are the gory details of what ev_loop does: |
|
|
245 | |
|
|
246 | 1. If there are no active watchers (reference count is zero), return. |
|
|
247 | 2. Queue and immediately call all prepare watchers. |
|
|
248 | 3. If we have been forked, recreate the kernel state. |
|
|
249 | 4. Update the kernel state with all outstanding changes. |
|
|
250 | 5. Update the "event loop time". |
|
|
251 | 6. Calculate for how long to block. |
|
|
252 | 7. Block the process, waiting for events. |
|
|
253 | 8. Update the "event loop time" and do time jump handling. |
|
|
254 | 9. Queue all outstanding timers. |
|
|
255 | 10. Queue all outstanding periodics. |
|
|
256 | 11. If no events are pending now, queue all idle watchers. |
|
|
257 | 12. Queue all check watchers. |
|
|
258 | 13. Call all queued watchers in reverse order (i.e. check watchers first). |
|
|
259 | 14. If ev_unloop has been called or EVLOOP_ONESHOT or EVLOOP_NONBLOCK |
|
|
260 | was used, return, otherwise continue with step #1. |
|
|
261 | |
242 | =item ev_unloop (loop, how) |
262 | =item ev_unloop (loop, how) |
243 | |
263 | |
244 | Can be used to make a call to C<ev_loop> return early (but only after it |
264 | 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 |
265 | 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 |
266 | 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. |
267 | C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return. |
248 | |
268 | |
249 | =item ev_ref (loop) |
269 | =item ev_ref (loop) |
250 | |
270 | |
251 | =item ev_unref (loop) |
271 | =item ev_unref (loop) |
… | |
… | |
417 | in each iteration of the event loop (This behaviour is called |
437 | in each iteration of the event loop (This behaviour is called |
418 | level-triggering because you keep receiving events as long as the |
438 | 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 |
439 | 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). |
440 | act on the event and neither want to receive future events). |
421 | |
441 | |
422 | In general you can register as many read and/or write event watchers oer |
442 | 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 |
443 | 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 |
444 | descriptors to non-blocking mode is also usually a good idea (but not |
425 | required if you know what you are doing). |
445 | required if you know what you are doing). |
426 | |
446 | |
427 | You have to be careful with dup'ed file descriptors, though. Some backends |
447 | 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 |
448 | (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 |
449 | descriptors correctly if you register interest in two or more fds pointing |
430 | to the same file/socket etc. description. |
450 | to the same underlying file/socket etc. description (that is, they share |
|
|
451 | the same underlying "file open"). |
431 | |
452 | |
432 | If you must do this, then force the use of a known-to-be-good backend |
453 | 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 |
454 | (at the time of this writing, this includes only EVMETHOD_SELECT and |
434 | EVMETHOD_POLL). |
455 | EVMETHOD_POLL). |
435 | |
456 | |
… | |
… | |
449 | |
470 | |
450 | Timer watchers are simple relative timers that generate an event after a |
471 | Timer watchers are simple relative timers that generate an event after a |
451 | given time, and optionally repeating in regular intervals after that. |
472 | given time, and optionally repeating in regular intervals after that. |
452 | |
473 | |
453 | The timers are based on real time, that is, if you register an event that |
474 | 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 |
475 | 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 |
476 | time, it will still time out after (roughly) and hour. "Roughly" because |
456 | detecting time jumps is hard, and soem inaccuracies are unavoidable (the |
477 | detecting time jumps is hard, and soem inaccuracies are unavoidable (the |
457 | monotonic clock option helps a lot here). |
478 | monotonic clock option helps a lot here). |
458 | |
479 | |
459 | The relative timeouts are calculated relative to the C<ev_now ()> |
480 | 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 |
481 | 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 |
482 | 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 |
483 | 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: |
484 | on the current time, use something like this to adjust for this: |
464 | |
485 | |
465 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
486 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
466 | |
487 | |
467 | =over 4 |
488 | =over 4 |
468 | |
489 | |
… | |
… | |
476 | later, again, and again, until stopped manually. |
497 | later, again, and again, until stopped manually. |
477 | |
498 | |
478 | The timer itself will do a best-effort at avoiding drift, that is, if you |
499 | 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 |
500 | 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 |
501 | 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 |
502 | 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. |
503 | timer will not fire more than once per event loop iteration. |
483 | |
504 | |
484 | =item ev_timer_again (loop) |
505 | =item ev_timer_again (loop) |
485 | |
506 | |
486 | This will act as if the timer timed out and restart it again if it is |
507 | 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 |
603 | (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 |
604 | will usually be called just before the callback will be triggered, but |
584 | might be called at other times, too. |
605 | might be called at other times, too. |
585 | |
606 | |
586 | NOTE: I<< This callback must always return a time that is later than the |
607 | 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. |
608 | passed C<now> value >>. Not even C<now> itself will do, it I<must> be larger. |
588 | |
609 | |
589 | This can be used to create very complex timers, such as a timer that |
610 | 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 |
611 | 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 |
612 | next midnight after C<now> and return the timestamp value for this. How |
592 | is, again, up to you (but it is not trivial). |
613 | you do this is, again, up to you (but it is not trivial, which is the main |
|
|
614 | reason I omitted it as an example). |
593 | |
615 | |
594 | =back |
616 | =back |
595 | |
617 | |
596 | =item ev_periodic_again (loop, ev_periodic *) |
618 | =item ev_periodic_again (loop, ev_periodic *) |
597 | |
619 | |
… | |
… | |
676 | =back |
698 | =back |
677 | |
699 | |
678 | =head2 C<ev_prepare> and C<ev_check> - customise your event loop |
700 | =head2 C<ev_prepare> and C<ev_check> - customise your event loop |
679 | |
701 | |
680 | Prepare and check watchers are usually (but not always) used in tandem: |
702 | Prepare and check watchers are usually (but not always) used in tandem: |
681 | Prepare watchers get invoked before the process blocks and check watchers |
703 | prepare watchers get invoked before the process blocks and check watchers |
682 | afterwards. |
704 | afterwards. |
683 | |
705 | |
684 | Their main purpose is to integrate other event mechanisms into libev. This |
706 | 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 |
707 | could be used, for example, to track variable changes, implement your own |
686 | watchers, integrate net-snmp or a coroutine library and lots more. |
708 | 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 |
711 | 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 |
712 | 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 |
713 | 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 |
714 | 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 |
715 | 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, |
716 | callbacks will never actually be called (but must be valid nevertheless, |
695 | because you never know, you know?). |
717 | because you never know, you know?). |
696 | |
718 | |
697 | As another example, the Perl Coro module uses these hooks to integrate |
719 | As another example, the Perl Coro module uses these hooks to integrate |
698 | coroutines into libev programs, by yielding to other active coroutines |
720 | coroutines into libev programs, by yielding to other active coroutines |
699 | during each prepare and only letting the process block if no coroutines |
721 | 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 |
722 | 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, |
723 | 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 |
724 | of lower priority, but only once, using idle watchers to keep the event |
703 | coroutines exist, thus mapping low-priority coroutines to idle/background |
725 | loop from blocking if lower-priority coroutines are active, thus mapping |
704 | tasks). |
726 | low-priority coroutines to idle/background tasks). |
705 | |
727 | |
706 | =over 4 |
728 | =over 4 |
707 | |
729 | |
708 | =item ev_prepare_init (ev_prepare *, callback) |
730 | =item ev_prepare_init (ev_prepare *, callback) |
709 | |
731 | |
… | |
… | |
724 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
746 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
725 | |
747 | |
726 | This function combines a simple timer and an I/O watcher, calls your |
748 | This function combines a simple timer and an I/O watcher, calls your |
727 | callback on whichever event happens first and automatically stop both |
749 | 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 |
750 | 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 |
751 | or timeout without having to allocate/configure/start/stop/free one or |
730 | more watchers yourself. |
752 | more watchers yourself. |
731 | |
753 | |
732 | If C<fd> is less than 0, then no I/O watcher will be started and events |
754 | 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 |
755 | is being ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and |
734 | C<events> set will be craeted and started. |
756 | C<events> set will be craeted and started. |
… | |
… | |
737 | started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and |
759 | 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 |
760 | repeat = 0) will be started. While C<0> is a valid timeout, it is of |
739 | dubious value. |
761 | dubious value. |
740 | |
762 | |
741 | The callback has the type C<void (*cb)(int revents, void *arg)> and gets |
763 | 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 |
764 | 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> |
765 | C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg> |
744 | value passed to C<ev_once>: |
766 | value passed to C<ev_once>: |
745 | |
767 | |
746 | static void stdin_ready (int revents, void *arg) |
768 | static void stdin_ready (int revents, void *arg) |
747 | { |
769 | { |
… | |
… | |
768 | |
790 | |
769 | Feed an event as if the given signal occured (loop must be the default loop!). |
791 | Feed an event as if the given signal occured (loop must be the default loop!). |
770 | |
792 | |
771 | =back |
793 | =back |
772 | |
794 | |
|
|
795 | =head1 LIBEVENT EMULATION |
|
|
796 | |
|
|
797 | Libev offers a compatibility emulation layer for libevent. It cannot |
|
|
798 | emulate the internals of libevent, so here are some usage hints: |
|
|
799 | |
|
|
800 | =over 4 |
|
|
801 | |
|
|
802 | =item * Use it by including <event.h>, as usual. |
|
|
803 | |
|
|
804 | =item * The following members are fully supported: ev_base, ev_callback, |
|
|
805 | ev_arg, ev_fd, ev_res, ev_events. |
|
|
806 | |
|
|
807 | =item * Avoid using ev_flags and the EVLIST_*-macros, while it is |
|
|
808 | maintained by libev, it does not work exactly the same way as in libevent (consider |
|
|
809 | it a private API). |
|
|
810 | |
|
|
811 | =item * Priorities are not currently supported. Initialising priorities |
|
|
812 | will fail and all watchers will have the same priority, even though there |
|
|
813 | is an ev_pri field. |
|
|
814 | |
|
|
815 | =item * Other members are not supported. |
|
|
816 | |
|
|
817 | =item * The libev emulation is I<not> ABI compatible to libevent, you need |
|
|
818 | to use the libev header file and library. |
|
|
819 | |
|
|
820 | =back |
|
|
821 | |
|
|
822 | =head1 C++ SUPPORT |
|
|
823 | |
|
|
824 | TBD. |
|
|
825 | |
773 | =head1 AUTHOR |
826 | =head1 AUTHOR |
774 | |
827 | |
775 | Marc Lehmann <libev@schmorp.de>. |
828 | Marc Lehmann <libev@schmorp.de>. |
776 | |
829 | |