… | |
… | |
323 | fatal ("no epoll found here, maybe it hides under your chair"); |
323 | fatal ("no epoll found here, maybe it hides under your chair"); |
324 | |
324 | |
325 | =item ev_default_destroy () |
325 | =item ev_default_destroy () |
326 | |
326 | |
327 | Destroys the default loop again (frees all memory and kernel state |
327 | Destroys the default loop again (frees all memory and kernel state |
328 | etc.). This stops all registered event watchers (by not touching them in |
328 | etc.). None of the active event watchers will be stopped in the normal |
329 | any way whatsoever, although you cannot rely on this :). |
329 | sense, so e.g. C<ev_is_active> might still return true. It is your |
|
|
330 | responsibility to either stop all watchers cleanly yoursef I<before> |
|
|
331 | calling this function, or cope with the fact afterwards (which is usually |
|
|
332 | the easiest thing, youc na just ignore the watchers and/or C<free ()> them |
|
|
333 | for example). |
330 | |
334 | |
331 | =item ev_loop_destroy (loop) |
335 | =item ev_loop_destroy (loop) |
332 | |
336 | |
333 | Like C<ev_default_destroy>, but destroys an event loop created by an |
337 | Like C<ev_default_destroy>, but destroys an event loop created by an |
334 | earlier call to C<ev_loop_new>. |
338 | earlier call to C<ev_loop_new>. |
… | |
… | |
464 | ev_ref (myloop); |
468 | ev_ref (myloop); |
465 | ev_signal_stop (myloop, &exitsig); |
469 | ev_signal_stop (myloop, &exitsig); |
466 | |
470 | |
467 | =back |
471 | =back |
468 | |
472 | |
|
|
473 | |
469 | =head1 ANATOMY OF A WATCHER |
474 | =head1 ANATOMY OF A WATCHER |
470 | |
475 | |
471 | A watcher is a structure that you create and register to record your |
476 | A watcher is a structure that you create and register to record your |
472 | interest in some event. For instance, if you want to wait for STDIN to |
477 | interest in some event. For instance, if you want to wait for STDIN to |
473 | become readable, you would create an C<ev_io> watcher for that: |
478 | become readable, you would create an C<ev_io> watcher for that: |
… | |
… | |
505 | *) >>), and you can stop watching for events at any time by calling the |
510 | *) >>), and you can stop watching for events at any time by calling the |
506 | corresponding stop function (C<< ev_<type>_stop (loop, watcher *) >>. |
511 | corresponding stop function (C<< ev_<type>_stop (loop, watcher *) >>. |
507 | |
512 | |
508 | As long as your watcher is active (has been started but not stopped) you |
513 | As long as your watcher is active (has been started but not stopped) you |
509 | must not touch the values stored in it. Most specifically you must never |
514 | must not touch the values stored in it. Most specifically you must never |
510 | reinitialise it or call its set macro. |
515 | reinitialise it or call its C<set> macro. |
511 | |
|
|
512 | You can check whether an event is active by calling the C<ev_is_active |
|
|
513 | (watcher *)> macro. To see whether an event is outstanding (but the |
|
|
514 | callback for it has not been called yet) you can use the C<ev_is_pending |
|
|
515 | (watcher *)> macro. |
|
|
516 | |
516 | |
517 | Each and every callback receives the event loop pointer as first, the |
517 | Each and every callback receives the event loop pointer as first, the |
518 | registered watcher structure as second, and a bitset of received events as |
518 | registered watcher structure as second, and a bitset of received events as |
519 | third argument. |
519 | third argument. |
520 | |
520 | |
… | |
… | |
544 | The signal specified in the C<ev_signal> watcher has been received by a thread. |
544 | The signal specified in the C<ev_signal> watcher has been received by a thread. |
545 | |
545 | |
546 | =item C<EV_CHILD> |
546 | =item C<EV_CHILD> |
547 | |
547 | |
548 | The pid specified in the C<ev_child> watcher has received a status change. |
548 | The pid specified in the C<ev_child> watcher has received a status change. |
|
|
549 | |
|
|
550 | =item C<EV_STAT> |
|
|
551 | |
|
|
552 | The path specified in the C<ev_stat> watcher changed its attributes somehow. |
549 | |
553 | |
550 | =item C<EV_IDLE> |
554 | =item C<EV_IDLE> |
551 | |
555 | |
552 | The C<ev_idle> watcher has determined that you have nothing better to do. |
556 | The C<ev_idle> watcher has determined that you have nothing better to do. |
553 | |
557 | |
… | |
… | |
577 | with the error from read() or write(). This will not work in multithreaded |
581 | with the error from read() or write(). This will not work in multithreaded |
578 | programs, though, so beware. |
582 | programs, though, so beware. |
579 | |
583 | |
580 | =back |
584 | =back |
581 | |
585 | |
|
|
586 | =head2 GENERIC WATCHER FUNCTIONS |
|
|
587 | |
|
|
588 | In the following description, C<TYPE> stands for the watcher type, |
|
|
589 | e.g. C<timer> for C<ev_timer> watchers and C<io> for C<ev_io> watchers. |
|
|
590 | |
|
|
591 | =over 4 |
|
|
592 | |
|
|
593 | =item C<ev_init> (ev_TYPE *watcher, callback) |
|
|
594 | |
|
|
595 | This macro initialises the generic portion of a watcher. The contents |
|
|
596 | of the watcher object can be arbitrary (so C<malloc> will do). Only |
|
|
597 | the generic parts of the watcher are initialised, you I<need> to call |
|
|
598 | the type-specific C<ev_TYPE_set> macro afterwards to initialise the |
|
|
599 | type-specific parts. For each type there is also a C<ev_TYPE_init> macro |
|
|
600 | which rolls both calls into one. |
|
|
601 | |
|
|
602 | You can reinitialise a watcher at any time as long as it has been stopped |
|
|
603 | (or never started) and there are no pending events outstanding. |
|
|
604 | |
|
|
605 | The callback is always of type C<void (*)(ev_loop *loop, ev_TYPE *watcher, |
|
|
606 | int revents)>. |
|
|
607 | |
|
|
608 | =item C<ev_TYPE_set> (ev_TYPE *, [args]) |
|
|
609 | |
|
|
610 | This macro initialises the type-specific parts of a watcher. You need to |
|
|
611 | call C<ev_init> at least once before you call this macro, but you can |
|
|
612 | call C<ev_TYPE_set> any number of times. You must not, however, call this |
|
|
613 | macro on a watcher that is active (it can be pending, however, which is a |
|
|
614 | difference to the C<ev_init> macro). |
|
|
615 | |
|
|
616 | Although some watcher types do not have type-specific arguments |
|
|
617 | (e.g. C<ev_prepare>) you still need to call its C<set> macro. |
|
|
618 | |
|
|
619 | =item C<ev_TYPE_init> (ev_TYPE *watcher, callback, [args]) |
|
|
620 | |
|
|
621 | This convinience macro rolls both C<ev_init> and C<ev_TYPE_set> macro |
|
|
622 | calls into a single call. This is the most convinient method to initialise |
|
|
623 | a watcher. The same limitations apply, of course. |
|
|
624 | |
|
|
625 | =item C<ev_TYPE_start> (loop *, ev_TYPE *watcher) |
|
|
626 | |
|
|
627 | Starts (activates) the given watcher. Only active watchers will receive |
|
|
628 | events. If the watcher is already active nothing will happen. |
|
|
629 | |
|
|
630 | =item C<ev_TYPE_stop> (loop *, ev_TYPE *watcher) |
|
|
631 | |
|
|
632 | Stops the given watcher again (if active) and clears the pending |
|
|
633 | status. It is possible that stopped watchers are pending (for example, |
|
|
634 | non-repeating timers are being stopped when they become pending), but |
|
|
635 | C<ev_TYPE_stop> ensures that the watcher is neither active nor pending. If |
|
|
636 | you want to free or reuse the memory used by the watcher it is therefore a |
|
|
637 | good idea to always call its C<ev_TYPE_stop> function. |
|
|
638 | |
|
|
639 | =item bool ev_is_active (ev_TYPE *watcher) |
|
|
640 | |
|
|
641 | Returns a true value iff the watcher is active (i.e. it has been started |
|
|
642 | and not yet been stopped). As long as a watcher is active you must not modify |
|
|
643 | it. |
|
|
644 | |
|
|
645 | =item bool ev_is_pending (ev_TYPE *watcher) |
|
|
646 | |
|
|
647 | Returns a true value iff the watcher is pending, (i.e. it has outstanding |
|
|
648 | events but its callback has not yet been invoked). As long as a watcher |
|
|
649 | is pending (but not active) you must not call an init function on it (but |
|
|
650 | C<ev_TYPE_set> is safe) and you must make sure the watcher is available to |
|
|
651 | libev (e.g. you cnanot C<free ()> it). |
|
|
652 | |
|
|
653 | =item callback = ev_cb (ev_TYPE *watcher) |
|
|
654 | |
|
|
655 | Returns the callback currently set on the watcher. |
|
|
656 | |
|
|
657 | =item ev_cb_set (ev_TYPE *watcher, callback) |
|
|
658 | |
|
|
659 | Change the callback. You can change the callback at virtually any time |
|
|
660 | (modulo threads). |
|
|
661 | |
|
|
662 | =back |
|
|
663 | |
|
|
664 | |
582 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
665 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
583 | |
666 | |
584 | Each watcher has, by default, a member C<void *data> that you can change |
667 | Each watcher has, by default, a member C<void *data> that you can change |
585 | and read at any time, libev will completely ignore it. This can be used |
668 | and read at any time, libev will completely ignore it. This can be used |
586 | to associate arbitrary data with your watcher. If you need more data and |
669 | to associate arbitrary data with your watcher. If you need more data and |
… | |
… | |
610 | |
693 | |
611 | |
694 | |
612 | =head1 WATCHER TYPES |
695 | =head1 WATCHER TYPES |
613 | |
696 | |
614 | This section describes each watcher in detail, but will not repeat |
697 | This section describes each watcher in detail, but will not repeat |
615 | information given in the last section. |
698 | information given in the last section. Any initialisation/set macros, |
|
|
699 | functions and members specific to the watcher type are explained. |
616 | |
700 | |
|
|
701 | Members are additionally marked with either I<[read-only]>, meaning that, |
|
|
702 | while the watcher is active, you can look at the member and expect some |
|
|
703 | sensible content, but you must not modify it (you can modify it while the |
|
|
704 | watcher is stopped to your hearts content), or I<[read-write]>, which |
|
|
705 | means you can expect it to have some sensible content while the watcher |
|
|
706 | is active, but you can also modify it. Modifying it may not do something |
|
|
707 | sensible or take immediate effect (or do anything at all), but libev will |
|
|
708 | not crash or malfunction in any way. |
617 | |
709 | |
|
|
710 | |
618 | =head2 C<ev_io> - is this file descriptor readable or writable |
711 | =head2 C<ev_io> - is this file descriptor readable or writable? |
619 | |
712 | |
620 | I/O watchers check whether a file descriptor is readable or writable |
713 | I/O watchers check whether a file descriptor is readable or writable |
621 | in each iteration of the event loop (This behaviour is called |
714 | in each iteration of the event loop, or, more precisely, when reading |
622 | level-triggering because you keep receiving events as long as the |
715 | would not block the process and writing would at least be able to write |
623 | condition persists. Remember you can stop the watcher if you don't want to |
716 | some data. This behaviour is called level-triggering because you keep |
624 | act on the event and neither want to receive future events). |
717 | receiving events as long as the condition persists. Remember you can stop |
|
|
718 | the watcher if you don't want to act on the event and neither want to |
|
|
719 | receive future events. |
625 | |
720 | |
626 | In general you can register as many read and/or write event watchers per |
721 | In general you can register as many read and/or write event watchers per |
627 | fd as you want (as long as you don't confuse yourself). Setting all file |
722 | fd as you want (as long as you don't confuse yourself). Setting all file |
628 | descriptors to non-blocking mode is also usually a good idea (but not |
723 | descriptors to non-blocking mode is also usually a good idea (but not |
629 | required if you know what you are doing). |
724 | required if you know what you are doing). |
630 | |
725 | |
631 | You have to be careful with dup'ed file descriptors, though. Some backends |
726 | You have to be careful with dup'ed file descriptors, though. Some backends |
632 | (the linux epoll backend is a notable example) cannot handle dup'ed file |
727 | (the linux epoll backend is a notable example) cannot handle dup'ed file |
633 | descriptors correctly if you register interest in two or more fds pointing |
728 | descriptors correctly if you register interest in two or more fds pointing |
634 | to the same underlying file/socket etc. description (that is, they share |
729 | to the same underlying file/socket/etc. description (that is, they share |
635 | the same underlying "file open"). |
730 | the same underlying "file open"). |
636 | |
731 | |
637 | If you must do this, then force the use of a known-to-be-good backend |
732 | If you must do this, then force the use of a known-to-be-good backend |
638 | (at the time of this writing, this includes only C<EVBACKEND_SELECT> and |
733 | (at the time of this writing, this includes only C<EVBACKEND_SELECT> and |
639 | C<EVBACKEND_POLL>). |
734 | C<EVBACKEND_POLL>). |
640 | |
735 | |
|
|
736 | Another thing you have to watch out for is that it is quite easy to |
|
|
737 | receive "spurious" readyness notifications, that is your callback might |
|
|
738 | be called with C<EV_READ> but a subsequent C<read>(2) will actually block |
|
|
739 | because there is no data. Not only are some backends known to create a |
|
|
740 | lot of those (for example solaris ports), it is very easy to get into |
|
|
741 | this situation even with a relatively standard program structure. Thus |
|
|
742 | it is best to always use non-blocking I/O: An extra C<read>(2) returning |
|
|
743 | C<EAGAIN> is far preferable to a program hanging until some data arrives. |
|
|
744 | |
|
|
745 | If you cannot run the fd in non-blocking mode (for example you should not |
|
|
746 | play around with an Xlib connection), then you have to seperately re-test |
|
|
747 | wether a file descriptor is really ready with a known-to-be good interface |
|
|
748 | such as poll (fortunately in our Xlib example, Xlib already does this on |
|
|
749 | its own, so its quite safe to use). |
|
|
750 | |
641 | =over 4 |
751 | =over 4 |
642 | |
752 | |
643 | =item ev_io_init (ev_io *, callback, int fd, int events) |
753 | =item ev_io_init (ev_io *, callback, int fd, int events) |
644 | |
754 | |
645 | =item ev_io_set (ev_io *, int fd, int events) |
755 | =item ev_io_set (ev_io *, int fd, int events) |
646 | |
756 | |
647 | Configures an C<ev_io> watcher. The fd is the file descriptor to rceeive |
757 | Configures an C<ev_io> watcher. The C<fd> is the file descriptor to |
648 | events for and events is either C<EV_READ>, C<EV_WRITE> or C<EV_READ | |
758 | rceeive events for and events is either C<EV_READ>, C<EV_WRITE> or |
649 | EV_WRITE> to receive the given events. |
759 | C<EV_READ | EV_WRITE> to receive the given events. |
650 | |
760 | |
651 | Please note that most of the more scalable backend mechanisms (for example |
761 | =item int fd [read-only] |
652 | epoll and solaris ports) can result in spurious readyness notifications |
762 | |
653 | for file descriptors, so you practically need to use non-blocking I/O (and |
763 | The file descriptor being watched. |
654 | treat callback invocation as hint only), or retest separately with a safe |
764 | |
655 | interface before doing I/O (XLib can do this), or force the use of either |
765 | =item int events [read-only] |
656 | C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>, which don't suffer from this |
766 | |
657 | problem. Also note that it is quite easy to have your callback invoked |
767 | The events being watched. |
658 | when the readyness condition is no longer valid even when employing |
|
|
659 | typical ways of handling events, so its a good idea to use non-blocking |
|
|
660 | I/O unconditionally. |
|
|
661 | |
768 | |
662 | =back |
769 | =back |
663 | |
770 | |
664 | Example: call C<stdin_readable_cb> when STDIN_FILENO has become, well |
771 | Example: call C<stdin_readable_cb> when STDIN_FILENO has become, well |
665 | readable, but only once. Since it is likely line-buffered, you could |
772 | readable, but only once. Since it is likely line-buffered, you could |
… | |
… | |
678 | ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ); |
785 | ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ); |
679 | ev_io_start (loop, &stdin_readable); |
786 | ev_io_start (loop, &stdin_readable); |
680 | ev_loop (loop, 0); |
787 | ev_loop (loop, 0); |
681 | |
788 | |
682 | |
789 | |
683 | =head2 C<ev_timer> - relative and optionally recurring timeouts |
790 | =head2 C<ev_timer> - relative and optionally repeating timeouts |
684 | |
791 | |
685 | Timer watchers are simple relative timers that generate an event after a |
792 | Timer watchers are simple relative timers that generate an event after a |
686 | given time, and optionally repeating in regular intervals after that. |
793 | given time, and optionally repeating in regular intervals after that. |
687 | |
794 | |
688 | The timers are based on real time, that is, if you register an event that |
795 | The timers are based on real time, that is, if you register an event that |
… | |
… | |
729 | |
836 | |
730 | If the timer is repeating, either start it if necessary (with the repeat |
837 | If the timer is repeating, either start it if necessary (with the repeat |
731 | value), or reset the running timer to the repeat value. |
838 | value), or reset the running timer to the repeat value. |
732 | |
839 | |
733 | This sounds a bit complicated, but here is a useful and typical |
840 | This sounds a bit complicated, but here is a useful and typical |
734 | example: Imagine you have a tcp connection and you want a so-called idle |
841 | example: Imagine you have a tcp connection and you want a so-called |
735 | timeout, that is, you want to be called when there have been, say, 60 |
842 | idle timeout, that is, you want to be called when there have been, |
736 | seconds of inactivity on the socket. The easiest way to do this is to |
843 | say, 60 seconds of inactivity on the socket. The easiest way to do |
737 | configure an C<ev_timer> with after=repeat=60 and calling ev_timer_again each |
844 | this is to configure an C<ev_timer> with C<after>=C<repeat>=C<60> and calling |
738 | time you successfully read or write some data. If you go into an idle |
845 | C<ev_timer_again> each time you successfully read or write some data. If |
739 | state where you do not expect data to travel on the socket, you can stop |
846 | you go into an idle state where you do not expect data to travel on the |
740 | the timer, and again will automatically restart it if need be. |
847 | socket, you can stop the timer, and again will automatically restart it if |
|
|
848 | need be. |
|
|
849 | |
|
|
850 | You can also ignore the C<after> value and C<ev_timer_start> altogether |
|
|
851 | and only ever use the C<repeat> value: |
|
|
852 | |
|
|
853 | ev_timer_init (timer, callback, 0., 5.); |
|
|
854 | ev_timer_again (loop, timer); |
|
|
855 | ... |
|
|
856 | timer->again = 17.; |
|
|
857 | ev_timer_again (loop, timer); |
|
|
858 | ... |
|
|
859 | timer->again = 10.; |
|
|
860 | ev_timer_again (loop, timer); |
|
|
861 | |
|
|
862 | This is more efficient then stopping/starting the timer eahc time you want |
|
|
863 | to modify its timeout value. |
|
|
864 | |
|
|
865 | =item ev_tstamp repeat [read-write] |
|
|
866 | |
|
|
867 | The current C<repeat> value. Will be used each time the watcher times out |
|
|
868 | or C<ev_timer_again> is called and determines the next timeout (if any), |
|
|
869 | which is also when any modifications are taken into account. |
741 | |
870 | |
742 | =back |
871 | =back |
743 | |
872 | |
744 | Example: create a timer that fires after 60 seconds. |
873 | Example: create a timer that fires after 60 seconds. |
745 | |
874 | |
… | |
… | |
770 | // and in some piece of code that gets executed on any "activity": |
899 | // and in some piece of code that gets executed on any "activity": |
771 | // reset the timeout to start ticking again at 10 seconds |
900 | // reset the timeout to start ticking again at 10 seconds |
772 | ev_timer_again (&mytimer); |
901 | ev_timer_again (&mytimer); |
773 | |
902 | |
774 | |
903 | |
775 | =head2 C<ev_periodic> - to cron or not to cron |
904 | =head2 C<ev_periodic> - to cron or not to cron? |
776 | |
905 | |
777 | Periodic watchers are also timers of a kind, but they are very versatile |
906 | Periodic watchers are also timers of a kind, but they are very versatile |
778 | (and unfortunately a bit complex). |
907 | (and unfortunately a bit complex). |
779 | |
908 | |
780 | Unlike C<ev_timer>'s, they are not based on real time (or relative time) |
909 | Unlike C<ev_timer>'s, they are not based on real time (or relative time) |
781 | but on wallclock time (absolute time). You can tell a periodic watcher |
910 | but on wallclock time (absolute time). You can tell a periodic watcher |
782 | to trigger "at" some specific point in time. For example, if you tell a |
911 | to trigger "at" some specific point in time. For example, if you tell a |
783 | periodic watcher to trigger in 10 seconds (by specifiying e.g. c<ev_now () |
912 | periodic watcher to trigger in 10 seconds (by specifiying e.g. C<ev_now () |
784 | + 10.>) and then reset your system clock to the last year, then it will |
913 | + 10.>) and then reset your system clock to the last year, then it will |
785 | take a year to trigger the event (unlike an C<ev_timer>, which would trigger |
914 | take a year to trigger the event (unlike an C<ev_timer>, which would trigger |
786 | roughly 10 seconds later and of course not if you reset your system time |
915 | roughly 10 seconds later and of course not if you reset your system time |
787 | again). |
916 | again). |
788 | |
917 | |
… | |
… | |
872 | Simply stops and restarts the periodic watcher again. This is only useful |
1001 | Simply stops and restarts the periodic watcher again. This is only useful |
873 | when you changed some parameters or the reschedule callback would return |
1002 | when you changed some parameters or the reschedule callback would return |
874 | a different time than the last time it was called (e.g. in a crond like |
1003 | a different time than the last time it was called (e.g. in a crond like |
875 | program when the crontabs have changed). |
1004 | program when the crontabs have changed). |
876 | |
1005 | |
|
|
1006 | =item ev_tstamp interval [read-write] |
|
|
1007 | |
|
|
1008 | The current interval value. Can be modified any time, but changes only |
|
|
1009 | take effect when the periodic timer fires or C<ev_periodic_again> is being |
|
|
1010 | called. |
|
|
1011 | |
|
|
1012 | =item ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read-write] |
|
|
1013 | |
|
|
1014 | The current reschedule callback, or C<0>, if this functionality is |
|
|
1015 | switched off. Can be changed any time, but changes only take effect when |
|
|
1016 | the periodic timer fires or C<ev_periodic_again> is being called. |
|
|
1017 | |
877 | =back |
1018 | =back |
878 | |
1019 | |
879 | Example: call a callback every hour, or, more precisely, whenever the |
1020 | Example: call a callback every hour, or, more precisely, whenever the |
880 | system clock is divisible by 3600. The callback invocation times have |
1021 | system clock is divisible by 3600. The callback invocation times have |
881 | potentially a lot of jittering, but good long-term stability. |
1022 | potentially a lot of jittering, but good long-term stability. |
… | |
… | |
908 | ev_periodic_init (&hourly_tick, clock_cb, |
1049 | ev_periodic_init (&hourly_tick, clock_cb, |
909 | fmod (ev_now (loop), 3600.), 3600., 0); |
1050 | fmod (ev_now (loop), 3600.), 3600., 0); |
910 | ev_periodic_start (loop, &hourly_tick); |
1051 | ev_periodic_start (loop, &hourly_tick); |
911 | |
1052 | |
912 | |
1053 | |
913 | =head2 C<ev_signal> - signal me when a signal gets signalled |
1054 | =head2 C<ev_signal> - signal me when a signal gets signalled! |
914 | |
1055 | |
915 | Signal watchers will trigger an event when the process receives a specific |
1056 | Signal watchers will trigger an event when the process receives a specific |
916 | signal one or more times. Even though signals are very asynchronous, libev |
1057 | signal one or more times. Even though signals are very asynchronous, libev |
917 | will try it's best to deliver signals synchronously, i.e. as part of the |
1058 | will try it's best to deliver signals synchronously, i.e. as part of the |
918 | normal event processing, like any other event. |
1059 | normal event processing, like any other event. |
… | |
… | |
931 | =item ev_signal_set (ev_signal *, int signum) |
1072 | =item ev_signal_set (ev_signal *, int signum) |
932 | |
1073 | |
933 | Configures the watcher to trigger on the given signal number (usually one |
1074 | Configures the watcher to trigger on the given signal number (usually one |
934 | of the C<SIGxxx> constants). |
1075 | of the C<SIGxxx> constants). |
935 | |
1076 | |
|
|
1077 | =item int signum [read-only] |
|
|
1078 | |
|
|
1079 | The signal the watcher watches out for. |
|
|
1080 | |
936 | =back |
1081 | =back |
937 | |
1082 | |
938 | |
1083 | |
939 | =head2 C<ev_child> - wait for pid status changes |
1084 | =head2 C<ev_child> - watch out for process status changes |
940 | |
1085 | |
941 | Child watchers trigger when your process receives a SIGCHLD in response to |
1086 | Child watchers trigger when your process receives a SIGCHLD in response to |
942 | some child status changes (most typically when a child of yours dies). |
1087 | some child status changes (most typically when a child of yours dies). |
943 | |
1088 | |
944 | =over 4 |
1089 | =over 4 |
… | |
… | |
952 | at the C<rstatus> member of the C<ev_child> watcher structure to see |
1097 | at the C<rstatus> member of the C<ev_child> watcher structure to see |
953 | the status word (use the macros from C<sys/wait.h> and see your systems |
1098 | the status word (use the macros from C<sys/wait.h> and see your systems |
954 | C<waitpid> documentation). The C<rpid> member contains the pid of the |
1099 | C<waitpid> documentation). The C<rpid> member contains the pid of the |
955 | process causing the status change. |
1100 | process causing the status change. |
956 | |
1101 | |
|
|
1102 | =item int pid [read-only] |
|
|
1103 | |
|
|
1104 | The process id this watcher watches out for, or C<0>, meaning any process id. |
|
|
1105 | |
|
|
1106 | =item int rpid [read-write] |
|
|
1107 | |
|
|
1108 | The process id that detected a status change. |
|
|
1109 | |
|
|
1110 | =item int rstatus [read-write] |
|
|
1111 | |
|
|
1112 | The process exit/trace status caused by C<rpid> (see your systems |
|
|
1113 | C<waitpid> and C<sys/wait.h> documentation for details). |
|
|
1114 | |
957 | =back |
1115 | =back |
958 | |
1116 | |
959 | Example: try to exit cleanly on SIGINT and SIGTERM. |
1117 | Example: try to exit cleanly on SIGINT and SIGTERM. |
960 | |
1118 | |
961 | static void |
1119 | static void |
… | |
… | |
967 | struct ev_signal signal_watcher; |
1125 | struct ev_signal signal_watcher; |
968 | ev_signal_init (&signal_watcher, sigint_cb, SIGINT); |
1126 | ev_signal_init (&signal_watcher, sigint_cb, SIGINT); |
969 | ev_signal_start (loop, &sigint_cb); |
1127 | ev_signal_start (loop, &sigint_cb); |
970 | |
1128 | |
971 | |
1129 | |
|
|
1130 | =head2 C<ev_stat> - did the file attributes just change? |
|
|
1131 | |
|
|
1132 | This watches a filesystem path for attribute changes. That is, it calls |
|
|
1133 | C<stat> regularly (or when the OS says it changed) and sees if it changed |
|
|
1134 | compared to the last time, invoking the callback if it did. |
|
|
1135 | |
|
|
1136 | The path does not need to exist: changing from "path exists" to "path does |
|
|
1137 | not exist" is a status change like any other. The condition "path does |
|
|
1138 | not exist" is signified by the C<st_nlink> field being zero (which is |
|
|
1139 | otherwise always forced to be at least one) and all the other fields of |
|
|
1140 | the stat buffer having unspecified contents. |
|
|
1141 | |
|
|
1142 | Since there is no standard to do this, the portable implementation simply |
|
|
1143 | calls C<stat (2)> regulalry on the path to see if it changed somehow. You |
|
|
1144 | can specify a recommended polling interval for this case. If you specify |
|
|
1145 | a polling interval of C<0> (highly recommended!) then a I<suitable, |
|
|
1146 | unspecified default> value will be used (which you can expect to be around |
|
|
1147 | five seconds, although this might change dynamically). Libev will also |
|
|
1148 | impose a minimum interval which is currently around C<0.1>, but thats |
|
|
1149 | usually overkill. |
|
|
1150 | |
|
|
1151 | This watcher type is not meant for massive numbers of stat watchers, |
|
|
1152 | as even with OS-supported change notifications, this can be |
|
|
1153 | resource-intensive. |
|
|
1154 | |
|
|
1155 | At the time of this writing, no specific OS backends are implemented, but |
|
|
1156 | if demand increases, at least a kqueue and inotify backend will be added. |
|
|
1157 | |
|
|
1158 | =over 4 |
|
|
1159 | |
|
|
1160 | =item ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval) |
|
|
1161 | |
|
|
1162 | =item ev_stat_set (ev_stat *, const char *path, ev_tstamp interval) |
|
|
1163 | |
|
|
1164 | Configures the watcher to wait for status changes of the given |
|
|
1165 | C<path>. The C<interval> is a hint on how quickly a change is expected to |
|
|
1166 | be detected and should normally be specified as C<0> to let libev choose |
|
|
1167 | a suitable value. The memory pointed to by C<path> must point to the same |
|
|
1168 | path for as long as the watcher is active. |
|
|
1169 | |
|
|
1170 | The callback will be receive C<EV_STAT> when a change was detected, |
|
|
1171 | relative to the attributes at the time the watcher was started (or the |
|
|
1172 | last change was detected). |
|
|
1173 | |
|
|
1174 | =item ev_stat_stat (ev_stat *) |
|
|
1175 | |
|
|
1176 | Updates the stat buffer immediately with new values. If you change the |
|
|
1177 | watched path in your callback, you could call this fucntion to avoid |
|
|
1178 | detecting this change (while introducing a race condition). Can also be |
|
|
1179 | useful simply to find out the new values. |
|
|
1180 | |
|
|
1181 | =item ev_statdata attr [read-only] |
|
|
1182 | |
|
|
1183 | The most-recently detected attributes of the file. Although the type is of |
|
|
1184 | C<ev_statdata>, this is usually the (or one of the) C<struct stat> types |
|
|
1185 | suitable for your system. If the C<st_nlink> member is C<0>, then there |
|
|
1186 | was some error while C<stat>ing the file. |
|
|
1187 | |
|
|
1188 | =item ev_statdata prev [read-only] |
|
|
1189 | |
|
|
1190 | The previous attributes of the file. The callback gets invoked whenever |
|
|
1191 | C<prev> != C<attr>. |
|
|
1192 | |
|
|
1193 | =item ev_tstamp interval [read-only] |
|
|
1194 | |
|
|
1195 | The specified interval. |
|
|
1196 | |
|
|
1197 | =item const char *path [read-only] |
|
|
1198 | |
|
|
1199 | The filesystem path that is being watched. |
|
|
1200 | |
|
|
1201 | =back |
|
|
1202 | |
|
|
1203 | Example: Watch C</etc/passwd> for attribute changes. |
|
|
1204 | |
|
|
1205 | static void |
|
|
1206 | passwd_cb (struct ev_loop *loop, ev_stat *w, int revents) |
|
|
1207 | { |
|
|
1208 | /* /etc/passwd changed in some way */ |
|
|
1209 | if (w->attr.st_nlink) |
|
|
1210 | { |
|
|
1211 | printf ("passwd current size %ld\n", (long)w->attr.st_size); |
|
|
1212 | printf ("passwd current atime %ld\n", (long)w->attr.st_mtime); |
|
|
1213 | printf ("passwd current mtime %ld\n", (long)w->attr.st_mtime); |
|
|
1214 | } |
|
|
1215 | else |
|
|
1216 | /* you shalt not abuse printf for puts */ |
|
|
1217 | puts ("wow, /etc/passwd is not there, expect problems. " |
|
|
1218 | "if this is windows, they already arrived\n"); |
|
|
1219 | } |
|
|
1220 | |
|
|
1221 | ... |
|
|
1222 | ev_stat passwd; |
|
|
1223 | |
|
|
1224 | ev_stat_init (&passwd, passwd_cb, "/etc/passwd"); |
|
|
1225 | ev_stat_start (loop, &passwd); |
|
|
1226 | |
|
|
1227 | |
972 | =head2 C<ev_idle> - when you've got nothing better to do |
1228 | =head2 C<ev_idle> - when you've got nothing better to do... |
973 | |
1229 | |
974 | Idle watchers trigger events when there are no other events are pending |
1230 | Idle watchers trigger events when there are no other events are pending |
975 | (prepare, check and other idle watchers do not count). That is, as long |
1231 | (prepare, check and other idle watchers do not count). That is, as long |
976 | as your process is busy handling sockets or timeouts (or even signals, |
1232 | as your process is busy handling sockets or timeouts (or even signals, |
977 | imagine) it will not be triggered. But when your process is idle all idle |
1233 | imagine) it will not be triggered. But when your process is idle all idle |
… | |
… | |
1011 | struct ev_idle *idle_watcher = malloc (sizeof (struct ev_idle)); |
1267 | struct ev_idle *idle_watcher = malloc (sizeof (struct ev_idle)); |
1012 | ev_idle_init (idle_watcher, idle_cb); |
1268 | ev_idle_init (idle_watcher, idle_cb); |
1013 | ev_idle_start (loop, idle_cb); |
1269 | ev_idle_start (loop, idle_cb); |
1014 | |
1270 | |
1015 | |
1271 | |
1016 | =head2 C<ev_prepare> and C<ev_check> - customise your event loop |
1272 | =head2 C<ev_prepare> and C<ev_check> - customise your event loop! |
1017 | |
1273 | |
1018 | Prepare and check watchers are usually (but not always) used in tandem: |
1274 | Prepare and check watchers are usually (but not always) used in tandem: |
1019 | prepare watchers get invoked before the process blocks and check watchers |
1275 | prepare watchers get invoked before the process blocks and check watchers |
1020 | afterwards. |
1276 | afterwards. |
1021 | |
1277 | |
|
|
1278 | You I<must not> call C<ev_loop> or similar functions that enter |
|
|
1279 | the current event loop from either C<ev_prepare> or C<ev_check> |
|
|
1280 | watchers. Other loops than the current one are fine, however. The |
|
|
1281 | rationale behind this is that you do not need to check for recursion in |
|
|
1282 | those watchers, i.e. the sequence will always be C<ev_prepare>, blocking, |
|
|
1283 | C<ev_check> so if you have one watcher of each kind they will always be |
|
|
1284 | called in pairs bracketing the blocking call. |
|
|
1285 | |
1022 | Their main purpose is to integrate other event mechanisms into libev and |
1286 | Their main purpose is to integrate other event mechanisms into libev and |
1023 | their use is somewhat advanced. This could be used, for example, to track |
1287 | their use is somewhat advanced. This could be used, for example, to track |
1024 | variable changes, implement your own watchers, integrate net-snmp or a |
1288 | variable changes, implement your own watchers, integrate net-snmp or a |
1025 | coroutine library and lots more. |
1289 | coroutine library and lots more. They are also occasionally useful if |
|
|
1290 | you cache some data and want to flush it before blocking (for example, |
|
|
1291 | in X programs you might want to do an C<XFlush ()> in an C<ev_prepare> |
|
|
1292 | watcher). |
1026 | |
1293 | |
1027 | This is done by examining in each prepare call which file descriptors need |
1294 | This is done by examining in each prepare call which file descriptors need |
1028 | to be watched by the other library, registering C<ev_io> watchers for |
1295 | to be watched by the other library, registering C<ev_io> watchers for |
1029 | them and starting an C<ev_timer> watcher for any timeouts (many libraries |
1296 | them and starting an C<ev_timer> watcher for any timeouts (many libraries |
1030 | provide just this functionality). Then, in the check watcher you check for |
1297 | provide just this functionality). Then, in the check watcher you check for |
… | |
… | |
1052 | parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set> |
1319 | parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set> |
1053 | macros, but using them is utterly, utterly and completely pointless. |
1320 | macros, but using them is utterly, utterly and completely pointless. |
1054 | |
1321 | |
1055 | =back |
1322 | =back |
1056 | |
1323 | |
1057 | Example: *TODO*. |
1324 | Example: To include a library such as adns, you would add IO watchers |
|
|
1325 | and a timeout watcher in a prepare handler, as required by libadns, and |
|
|
1326 | in a check watcher, destroy them and call into libadns. What follows is |
|
|
1327 | pseudo-code only of course: |
1058 | |
1328 | |
|
|
1329 | static ev_io iow [nfd]; |
|
|
1330 | static ev_timer tw; |
1059 | |
1331 | |
|
|
1332 | static void |
|
|
1333 | io_cb (ev_loop *loop, ev_io *w, int revents) |
|
|
1334 | { |
|
|
1335 | // set the relevant poll flags |
|
|
1336 | // could also call adns_processreadable etc. here |
|
|
1337 | struct pollfd *fd = (struct pollfd *)w->data; |
|
|
1338 | if (revents & EV_READ ) fd->revents |= fd->events & POLLIN; |
|
|
1339 | if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT; |
|
|
1340 | } |
|
|
1341 | |
|
|
1342 | // create io watchers for each fd and a timer before blocking |
|
|
1343 | static void |
|
|
1344 | adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) |
|
|
1345 | { |
|
|
1346 | int timeout = 3600000;truct pollfd fds [nfd]; |
|
|
1347 | // actual code will need to loop here and realloc etc. |
|
|
1348 | adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ())); |
|
|
1349 | |
|
|
1350 | /* the callback is illegal, but won't be called as we stop during check */ |
|
|
1351 | ev_timer_init (&tw, 0, timeout * 1e-3); |
|
|
1352 | ev_timer_start (loop, &tw); |
|
|
1353 | |
|
|
1354 | // create on ev_io per pollfd |
|
|
1355 | for (int i = 0; i < nfd; ++i) |
|
|
1356 | { |
|
|
1357 | ev_io_init (iow + i, io_cb, fds [i].fd, |
|
|
1358 | ((fds [i].events & POLLIN ? EV_READ : 0) |
|
|
1359 | | (fds [i].events & POLLOUT ? EV_WRITE : 0))); |
|
|
1360 | |
|
|
1361 | fds [i].revents = 0; |
|
|
1362 | iow [i].data = fds + i; |
|
|
1363 | ev_io_start (loop, iow + i); |
|
|
1364 | } |
|
|
1365 | } |
|
|
1366 | |
|
|
1367 | // stop all watchers after blocking |
|
|
1368 | static void |
|
|
1369 | adns_check_cb (ev_loop *loop, ev_check *w, int revents) |
|
|
1370 | { |
|
|
1371 | ev_timer_stop (loop, &tw); |
|
|
1372 | |
|
|
1373 | for (int i = 0; i < nfd; ++i) |
|
|
1374 | ev_io_stop (loop, iow + i); |
|
|
1375 | |
|
|
1376 | adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop)); |
|
|
1377 | } |
|
|
1378 | |
|
|
1379 | |
1060 | =head2 C<ev_embed> - when one backend isn't enough |
1380 | =head2 C<ev_embed> - when one backend isn't enough... |
1061 | |
1381 | |
1062 | This is a rather advanced watcher type that lets you embed one event loop |
1382 | This is a rather advanced watcher type that lets you embed one event loop |
1063 | into another. |
1383 | into another (currently only C<ev_io> events are supported in the embedded |
|
|
1384 | loop, other types of watchers might be handled in a delayed or incorrect |
|
|
1385 | fashion and must not be used). |
1064 | |
1386 | |
1065 | There are primarily two reasons you would want that: work around bugs and |
1387 | There are primarily two reasons you would want that: work around bugs and |
1066 | prioritise I/O. |
1388 | prioritise I/O. |
1067 | |
1389 | |
1068 | As an example for a bug workaround, the kqueue backend might only support |
1390 | As an example for a bug workaround, the kqueue backend might only support |
… | |
… | |
1076 | As for prioritising I/O: rarely you have the case where some fds have |
1398 | As for prioritising I/O: rarely you have the case where some fds have |
1077 | to be watched and handled very quickly (with low latency), and even |
1399 | to be watched and handled very quickly (with low latency), and even |
1078 | priorities and idle watchers might have too much overhead. In this case |
1400 | priorities and idle watchers might have too much overhead. In this case |
1079 | you would put all the high priority stuff in one loop and all the rest in |
1401 | you would put all the high priority stuff in one loop and all the rest in |
1080 | a second one, and embed the second one in the first. |
1402 | a second one, and embed the second one in the first. |
|
|
1403 | |
|
|
1404 | As long as the watcher is active, the callback will be invoked every time |
|
|
1405 | there might be events pending in the embedded loop. The callback must then |
|
|
1406 | call C<ev_embed_sweep (mainloop, watcher)> to make a single sweep and invoke |
|
|
1407 | their callbacks (you could also start an idle watcher to give the embedded |
|
|
1408 | loop strictly lower priority for example). You can also set the callback |
|
|
1409 | to C<0>, in which case the embed watcher will automatically execute the |
|
|
1410 | embedded loop sweep. |
1081 | |
1411 | |
1082 | As long as the watcher is started it will automatically handle events. The |
1412 | As long as the watcher is started it will automatically handle events. The |
1083 | callback will be invoked whenever some events have been handled. You can |
1413 | callback will be invoked whenever some events have been handled. You can |
1084 | set the callback to C<0> to avoid having to specify one if you are not |
1414 | set the callback to C<0> to avoid having to specify one if you are not |
1085 | interested in that. |
1415 | interested in that. |
… | |
… | |
1117 | else |
1447 | else |
1118 | loop_lo = loop_hi; |
1448 | loop_lo = loop_hi; |
1119 | |
1449 | |
1120 | =over 4 |
1450 | =over 4 |
1121 | |
1451 | |
1122 | =item ev_embed_init (ev_embed *, callback, struct ev_loop *loop) |
1452 | =item ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop) |
1123 | |
1453 | |
1124 | =item ev_embed_set (ev_embed *, callback, struct ev_loop *loop) |
1454 | =item ev_embed_set (ev_embed *, callback, struct ev_loop *embedded_loop) |
1125 | |
1455 | |
1126 | Configures the watcher to embed the given loop, which must be embeddable. |
1456 | Configures the watcher to embed the given loop, which must be |
|
|
1457 | embeddable. If the callback is C<0>, then C<ev_embed_sweep> will be |
|
|
1458 | invoked automatically, otherwise it is the responsibility of the callback |
|
|
1459 | to invoke it (it will continue to be called until the sweep has been done, |
|
|
1460 | if you do not want thta, you need to temporarily stop the embed watcher). |
|
|
1461 | |
|
|
1462 | =item ev_embed_sweep (loop, ev_embed *) |
|
|
1463 | |
|
|
1464 | Make a single, non-blocking sweep over the embedded loop. This works |
|
|
1465 | similarly to C<ev_loop (embedded_loop, EVLOOP_NONBLOCK)>, but in the most |
|
|
1466 | apropriate way for embedded loops. |
|
|
1467 | |
|
|
1468 | =item struct ev_loop *loop [read-only] |
|
|
1469 | |
|
|
1470 | The embedded event loop. |
1127 | |
1471 | |
1128 | =back |
1472 | =back |
1129 | |
1473 | |
1130 | |
1474 | |
1131 | =head1 OTHER FUNCTIONS |
1475 | =head1 OTHER FUNCTIONS |
… | |
… | |
1164 | /* stdin might have data for us, joy! */; |
1508 | /* stdin might have data for us, joy! */; |
1165 | } |
1509 | } |
1166 | |
1510 | |
1167 | ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
1511 | ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
1168 | |
1512 | |
1169 | =item ev_feed_event (loop, watcher, int events) |
1513 | =item ev_feed_event (ev_loop *, watcher *, int revents) |
1170 | |
1514 | |
1171 | Feeds the given event set into the event loop, as if the specified event |
1515 | Feeds the given event set into the event loop, as if the specified event |
1172 | had happened for the specified watcher (which must be a pointer to an |
1516 | had happened for the specified watcher (which must be a pointer to an |
1173 | initialised but not necessarily started event watcher). |
1517 | initialised but not necessarily started event watcher). |
1174 | |
1518 | |
1175 | =item ev_feed_fd_event (loop, int fd, int revents) |
1519 | =item ev_feed_fd_event (ev_loop *, int fd, int revents) |
1176 | |
1520 | |
1177 | Feed an event on the given fd, as if a file descriptor backend detected |
1521 | Feed an event on the given fd, as if a file descriptor backend detected |
1178 | the given events it. |
1522 | the given events it. |
1179 | |
1523 | |
1180 | =item ev_feed_signal_event (loop, int signum) |
1524 | =item ev_feed_signal_event (ev_loop *loop, int signum) |
1181 | |
1525 | |
1182 | Feed an event as if the given signal occured (loop must be the default loop!). |
1526 | Feed an event as if the given signal occured (C<loop> must be the default |
|
|
1527 | loop!). |
1183 | |
1528 | |
1184 | =back |
1529 | =back |
1185 | |
1530 | |
1186 | |
1531 | |
1187 | =head1 LIBEVENT EMULATION |
1532 | =head1 LIBEVENT EMULATION |
… | |
… | |
1211 | |
1556 | |
1212 | =back |
1557 | =back |
1213 | |
1558 | |
1214 | =head1 C++ SUPPORT |
1559 | =head1 C++ SUPPORT |
1215 | |
1560 | |
1216 | TBD. |
1561 | Libev comes with some simplistic wrapper classes for C++ that mainly allow |
|
|
1562 | you to use some convinience methods to start/stop watchers and also change |
|
|
1563 | the callback model to a model using method callbacks on objects. |
|
|
1564 | |
|
|
1565 | To use it, |
|
|
1566 | |
|
|
1567 | #include <ev++.h> |
|
|
1568 | |
|
|
1569 | (it is not installed by default). This automatically includes F<ev.h> |
|
|
1570 | and puts all of its definitions (many of them macros) into the global |
|
|
1571 | namespace. All C++ specific things are put into the C<ev> namespace. |
|
|
1572 | |
|
|
1573 | It should support all the same embedding options as F<ev.h>, most notably |
|
|
1574 | C<EV_MULTIPLICITY>. |
|
|
1575 | |
|
|
1576 | Here is a list of things available in the C<ev> namespace: |
|
|
1577 | |
|
|
1578 | =over 4 |
|
|
1579 | |
|
|
1580 | =item C<ev::READ>, C<ev::WRITE> etc. |
|
|
1581 | |
|
|
1582 | These are just enum values with the same values as the C<EV_READ> etc. |
|
|
1583 | macros from F<ev.h>. |
|
|
1584 | |
|
|
1585 | =item C<ev::tstamp>, C<ev::now> |
|
|
1586 | |
|
|
1587 | Aliases to the same types/functions as with the C<ev_> prefix. |
|
|
1588 | |
|
|
1589 | =item C<ev::io>, C<ev::timer>, C<ev::periodic>, C<ev::idle>, C<ev::sig> etc. |
|
|
1590 | |
|
|
1591 | For each C<ev_TYPE> watcher in F<ev.h> there is a corresponding class of |
|
|
1592 | the same name in the C<ev> namespace, with the exception of C<ev_signal> |
|
|
1593 | which is called C<ev::sig> to avoid clashes with the C<signal> macro |
|
|
1594 | defines by many implementations. |
|
|
1595 | |
|
|
1596 | All of those classes have these methods: |
|
|
1597 | |
|
|
1598 | =over 4 |
|
|
1599 | |
|
|
1600 | =item ev::TYPE::TYPE (object *, object::method *) |
|
|
1601 | |
|
|
1602 | =item ev::TYPE::TYPE (object *, object::method *, struct ev_loop *) |
|
|
1603 | |
|
|
1604 | =item ev::TYPE::~TYPE |
|
|
1605 | |
|
|
1606 | The constructor takes a pointer to an object and a method pointer to |
|
|
1607 | the event handler callback to call in this class. The constructor calls |
|
|
1608 | C<ev_init> for you, which means you have to call the C<set> method |
|
|
1609 | before starting it. If you do not specify a loop then the constructor |
|
|
1610 | automatically associates the default loop with this watcher. |
|
|
1611 | |
|
|
1612 | The destructor automatically stops the watcher if it is active. |
|
|
1613 | |
|
|
1614 | =item w->set (struct ev_loop *) |
|
|
1615 | |
|
|
1616 | Associates a different C<struct ev_loop> with this watcher. You can only |
|
|
1617 | do this when the watcher is inactive (and not pending either). |
|
|
1618 | |
|
|
1619 | =item w->set ([args]) |
|
|
1620 | |
|
|
1621 | Basically the same as C<ev_TYPE_set>, with the same args. Must be |
|
|
1622 | called at least once. Unlike the C counterpart, an active watcher gets |
|
|
1623 | automatically stopped and restarted. |
|
|
1624 | |
|
|
1625 | =item w->start () |
|
|
1626 | |
|
|
1627 | Starts the watcher. Note that there is no C<loop> argument as the |
|
|
1628 | constructor already takes the loop. |
|
|
1629 | |
|
|
1630 | =item w->stop () |
|
|
1631 | |
|
|
1632 | Stops the watcher if it is active. Again, no C<loop> argument. |
|
|
1633 | |
|
|
1634 | =item w->again () C<ev::timer>, C<ev::periodic> only |
|
|
1635 | |
|
|
1636 | For C<ev::timer> and C<ev::periodic>, this invokes the corresponding |
|
|
1637 | C<ev_TYPE_again> function. |
|
|
1638 | |
|
|
1639 | =item w->sweep () C<ev::embed> only |
|
|
1640 | |
|
|
1641 | Invokes C<ev_embed_sweep>. |
|
|
1642 | |
|
|
1643 | =item w->update () C<ev::stat> only |
|
|
1644 | |
|
|
1645 | Invokes C<ev_stat_stat>. |
|
|
1646 | |
|
|
1647 | =back |
|
|
1648 | |
|
|
1649 | =back |
|
|
1650 | |
|
|
1651 | Example: Define a class with an IO and idle watcher, start one of them in |
|
|
1652 | the constructor. |
|
|
1653 | |
|
|
1654 | class myclass |
|
|
1655 | { |
|
|
1656 | ev_io io; void io_cb (ev::io &w, int revents); |
|
|
1657 | ev_idle idle void idle_cb (ev::idle &w, int revents); |
|
|
1658 | |
|
|
1659 | myclass (); |
|
|
1660 | } |
|
|
1661 | |
|
|
1662 | myclass::myclass (int fd) |
|
|
1663 | : io (this, &myclass::io_cb), |
|
|
1664 | idle (this, &myclass::idle_cb) |
|
|
1665 | { |
|
|
1666 | io.start (fd, ev::READ); |
|
|
1667 | } |
|
|
1668 | |
|
|
1669 | =head1 EMBEDDING |
|
|
1670 | |
|
|
1671 | Libev can (and often is) directly embedded into host |
|
|
1672 | applications. Examples of applications that embed it include the Deliantra |
|
|
1673 | Game Server, the EV perl module, the GNU Virtual Private Ethernet (gvpe) |
|
|
1674 | and rxvt-unicode. |
|
|
1675 | |
|
|
1676 | The goal is to enable you to just copy the neecssary files into your |
|
|
1677 | source directory without having to change even a single line in them, so |
|
|
1678 | you can easily upgrade by simply copying (or having a checked-out copy of |
|
|
1679 | libev somewhere in your source tree). |
|
|
1680 | |
|
|
1681 | =head2 FILESETS |
|
|
1682 | |
|
|
1683 | Depending on what features you need you need to include one or more sets of files |
|
|
1684 | in your app. |
|
|
1685 | |
|
|
1686 | =head3 CORE EVENT LOOP |
|
|
1687 | |
|
|
1688 | To include only the libev core (all the C<ev_*> functions), with manual |
|
|
1689 | configuration (no autoconf): |
|
|
1690 | |
|
|
1691 | #define EV_STANDALONE 1 |
|
|
1692 | #include "ev.c" |
|
|
1693 | |
|
|
1694 | This will automatically include F<ev.h>, too, and should be done in a |
|
|
1695 | single C source file only to provide the function implementations. To use |
|
|
1696 | it, do the same for F<ev.h> in all files wishing to use this API (best |
|
|
1697 | done by writing a wrapper around F<ev.h> that you can include instead and |
|
|
1698 | where you can put other configuration options): |
|
|
1699 | |
|
|
1700 | #define EV_STANDALONE 1 |
|
|
1701 | #include "ev.h" |
|
|
1702 | |
|
|
1703 | Both header files and implementation files can be compiled with a C++ |
|
|
1704 | compiler (at least, thats a stated goal, and breakage will be treated |
|
|
1705 | as a bug). |
|
|
1706 | |
|
|
1707 | You need the following files in your source tree, or in a directory |
|
|
1708 | in your include path (e.g. in libev/ when using -Ilibev): |
|
|
1709 | |
|
|
1710 | ev.h |
|
|
1711 | ev.c |
|
|
1712 | ev_vars.h |
|
|
1713 | ev_wrap.h |
|
|
1714 | |
|
|
1715 | ev_win32.c required on win32 platforms only |
|
|
1716 | |
|
|
1717 | ev_select.c only when select backend is enabled (which is by default) |
|
|
1718 | ev_poll.c only when poll backend is enabled (disabled by default) |
|
|
1719 | ev_epoll.c only when the epoll backend is enabled (disabled by default) |
|
|
1720 | ev_kqueue.c only when the kqueue backend is enabled (disabled by default) |
|
|
1721 | ev_port.c only when the solaris port backend is enabled (disabled by default) |
|
|
1722 | |
|
|
1723 | F<ev.c> includes the backend files directly when enabled, so you only need |
|
|
1724 | to compile this single file. |
|
|
1725 | |
|
|
1726 | =head3 LIBEVENT COMPATIBILITY API |
|
|
1727 | |
|
|
1728 | To include the libevent compatibility API, also include: |
|
|
1729 | |
|
|
1730 | #include "event.c" |
|
|
1731 | |
|
|
1732 | in the file including F<ev.c>, and: |
|
|
1733 | |
|
|
1734 | #include "event.h" |
|
|
1735 | |
|
|
1736 | in the files that want to use the libevent API. This also includes F<ev.h>. |
|
|
1737 | |
|
|
1738 | You need the following additional files for this: |
|
|
1739 | |
|
|
1740 | event.h |
|
|
1741 | event.c |
|
|
1742 | |
|
|
1743 | =head3 AUTOCONF SUPPORT |
|
|
1744 | |
|
|
1745 | Instead of using C<EV_STANDALONE=1> and providing your config in |
|
|
1746 | whatever way you want, you can also C<m4_include([libev.m4])> in your |
|
|
1747 | F<configure.ac> and leave C<EV_STANDALONE> undefined. F<ev.c> will then |
|
|
1748 | include F<config.h> and configure itself accordingly. |
|
|
1749 | |
|
|
1750 | For this of course you need the m4 file: |
|
|
1751 | |
|
|
1752 | libev.m4 |
|
|
1753 | |
|
|
1754 | =head2 PREPROCESSOR SYMBOLS/MACROS |
|
|
1755 | |
|
|
1756 | Libev can be configured via a variety of preprocessor symbols you have to define |
|
|
1757 | before including any of its files. The default is not to build for multiplicity |
|
|
1758 | and only include the select backend. |
|
|
1759 | |
|
|
1760 | =over 4 |
|
|
1761 | |
|
|
1762 | =item EV_STANDALONE |
|
|
1763 | |
|
|
1764 | Must always be C<1> if you do not use autoconf configuration, which |
|
|
1765 | keeps libev from including F<config.h>, and it also defines dummy |
|
|
1766 | implementations for some libevent functions (such as logging, which is not |
|
|
1767 | supported). It will also not define any of the structs usually found in |
|
|
1768 | F<event.h> that are not directly supported by the libev core alone. |
|
|
1769 | |
|
|
1770 | =item EV_USE_MONOTONIC |
|
|
1771 | |
|
|
1772 | If defined to be C<1>, libev will try to detect the availability of the |
|
|
1773 | monotonic clock option at both compiletime and runtime. Otherwise no use |
|
|
1774 | of the monotonic clock option will be attempted. If you enable this, you |
|
|
1775 | usually have to link against librt or something similar. Enabling it when |
|
|
1776 | the functionality isn't available is safe, though, althoguh you have |
|
|
1777 | to make sure you link against any libraries where the C<clock_gettime> |
|
|
1778 | function is hiding in (often F<-lrt>). |
|
|
1779 | |
|
|
1780 | =item EV_USE_REALTIME |
|
|
1781 | |
|
|
1782 | If defined to be C<1>, libev will try to detect the availability of the |
|
|
1783 | realtime clock option at compiletime (and assume its availability at |
|
|
1784 | runtime if successful). Otherwise no use of the realtime clock option will |
|
|
1785 | be attempted. This effectively replaces C<gettimeofday> by C<clock_get |
|
|
1786 | (CLOCK_REALTIME, ...)> and will not normally affect correctness. See tzhe note about libraries |
|
|
1787 | in the description of C<EV_USE_MONOTONIC>, though. |
|
|
1788 | |
|
|
1789 | =item EV_USE_SELECT |
|
|
1790 | |
|
|
1791 | If undefined or defined to be C<1>, libev will compile in support for the |
|
|
1792 | C<select>(2) backend. No attempt at autodetection will be done: if no |
|
|
1793 | other method takes over, select will be it. Otherwise the select backend |
|
|
1794 | will not be compiled in. |
|
|
1795 | |
|
|
1796 | =item EV_SELECT_USE_FD_SET |
|
|
1797 | |
|
|
1798 | If defined to C<1>, then the select backend will use the system C<fd_set> |
|
|
1799 | structure. This is useful if libev doesn't compile due to a missing |
|
|
1800 | C<NFDBITS> or C<fd_mask> definition or it misguesses the bitset layout on |
|
|
1801 | exotic systems. This usually limits the range of file descriptors to some |
|
|
1802 | low limit such as 1024 or might have other limitations (winsocket only |
|
|
1803 | allows 64 sockets). The C<FD_SETSIZE> macro, set before compilation, might |
|
|
1804 | influence the size of the C<fd_set> used. |
|
|
1805 | |
|
|
1806 | =item EV_SELECT_IS_WINSOCKET |
|
|
1807 | |
|
|
1808 | When defined to C<1>, the select backend will assume that |
|
|
1809 | select/socket/connect etc. don't understand file descriptors but |
|
|
1810 | wants osf handles on win32 (this is the case when the select to |
|
|
1811 | be used is the winsock select). This means that it will call |
|
|
1812 | C<_get_osfhandle> on the fd to convert it to an OS handle. Otherwise, |
|
|
1813 | it is assumed that all these functions actually work on fds, even |
|
|
1814 | on win32. Should not be defined on non-win32 platforms. |
|
|
1815 | |
|
|
1816 | =item EV_USE_POLL |
|
|
1817 | |
|
|
1818 | If defined to be C<1>, libev will compile in support for the C<poll>(2) |
|
|
1819 | backend. Otherwise it will be enabled on non-win32 platforms. It |
|
|
1820 | takes precedence over select. |
|
|
1821 | |
|
|
1822 | =item EV_USE_EPOLL |
|
|
1823 | |
|
|
1824 | If defined to be C<1>, libev will compile in support for the Linux |
|
|
1825 | C<epoll>(7) backend. Its availability will be detected at runtime, |
|
|
1826 | otherwise another method will be used as fallback. This is the |
|
|
1827 | preferred backend for GNU/Linux systems. |
|
|
1828 | |
|
|
1829 | =item EV_USE_KQUEUE |
|
|
1830 | |
|
|
1831 | If defined to be C<1>, libev will compile in support for the BSD style |
|
|
1832 | C<kqueue>(2) backend. Its actual availability will be detected at runtime, |
|
|
1833 | otherwise another method will be used as fallback. This is the preferred |
|
|
1834 | backend for BSD and BSD-like systems, although on most BSDs kqueue only |
|
|
1835 | supports some types of fds correctly (the only platform we found that |
|
|
1836 | supports ptys for example was NetBSD), so kqueue might be compiled in, but |
|
|
1837 | not be used unless explicitly requested. The best way to use it is to find |
|
|
1838 | out whether kqueue supports your type of fd properly and use an embedded |
|
|
1839 | kqueue loop. |
|
|
1840 | |
|
|
1841 | =item EV_USE_PORT |
|
|
1842 | |
|
|
1843 | If defined to be C<1>, libev will compile in support for the Solaris |
|
|
1844 | 10 port style backend. Its availability will be detected at runtime, |
|
|
1845 | otherwise another method will be used as fallback. This is the preferred |
|
|
1846 | backend for Solaris 10 systems. |
|
|
1847 | |
|
|
1848 | =item EV_USE_DEVPOLL |
|
|
1849 | |
|
|
1850 | reserved for future expansion, works like the USE symbols above. |
|
|
1851 | |
|
|
1852 | =item EV_H |
|
|
1853 | |
|
|
1854 | The name of the F<ev.h> header file used to include it. The default if |
|
|
1855 | undefined is C<< <ev.h> >> in F<event.h> and C<"ev.h"> in F<ev.c>. This |
|
|
1856 | can be used to virtually rename the F<ev.h> header file in case of conflicts. |
|
|
1857 | |
|
|
1858 | =item EV_CONFIG_H |
|
|
1859 | |
|
|
1860 | If C<EV_STANDALONE> isn't C<1>, this variable can be used to override |
|
|
1861 | F<ev.c>'s idea of where to find the F<config.h> file, similarly to |
|
|
1862 | C<EV_H>, above. |
|
|
1863 | |
|
|
1864 | =item EV_EVENT_H |
|
|
1865 | |
|
|
1866 | Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea |
|
|
1867 | of how the F<event.h> header can be found. |
|
|
1868 | |
|
|
1869 | =item EV_PROTOTYPES |
|
|
1870 | |
|
|
1871 | If defined to be C<0>, then F<ev.h> will not define any function |
|
|
1872 | prototypes, but still define all the structs and other symbols. This is |
|
|
1873 | occasionally useful if you want to provide your own wrapper functions |
|
|
1874 | around libev functions. |
|
|
1875 | |
|
|
1876 | =item EV_MULTIPLICITY |
|
|
1877 | |
|
|
1878 | If undefined or defined to C<1>, then all event-loop-specific functions |
|
|
1879 | will have the C<struct ev_loop *> as first argument, and you can create |
|
|
1880 | additional independent event loops. Otherwise there will be no support |
|
|
1881 | for multiple event loops and there is no first event loop pointer |
|
|
1882 | argument. Instead, all functions act on the single default loop. |
|
|
1883 | |
|
|
1884 | =item EV_PERIODIC_ENABLE |
|
|
1885 | |
|
|
1886 | If undefined or defined to be C<1>, then periodic timers are supported. If |
|
|
1887 | defined to be C<0>, then they are not. Disabling them saves a few kB of |
|
|
1888 | code. |
|
|
1889 | |
|
|
1890 | =item EV_EMBED_ENABLE |
|
|
1891 | |
|
|
1892 | If undefined or defined to be C<1>, then embed watchers are supported. If |
|
|
1893 | defined to be C<0>, then they are not. |
|
|
1894 | |
|
|
1895 | =item EV_STAT_ENABLE |
|
|
1896 | |
|
|
1897 | If undefined or defined to be C<1>, then stat watchers are supported. If |
|
|
1898 | defined to be C<0>, then they are not. |
|
|
1899 | |
|
|
1900 | =item EV_MINIMAL |
|
|
1901 | |
|
|
1902 | If you need to shave off some kilobytes of code at the expense of some |
|
|
1903 | speed, define this symbol to C<1>. Currently only used for gcc to override |
|
|
1904 | some inlining decisions, saves roughly 30% codesize of amd64. |
|
|
1905 | |
|
|
1906 | =item EV_COMMON |
|
|
1907 | |
|
|
1908 | By default, all watchers have a C<void *data> member. By redefining |
|
|
1909 | this macro to a something else you can include more and other types of |
|
|
1910 | members. You have to define it each time you include one of the files, |
|
|
1911 | though, and it must be identical each time. |
|
|
1912 | |
|
|
1913 | For example, the perl EV module uses something like this: |
|
|
1914 | |
|
|
1915 | #define EV_COMMON \ |
|
|
1916 | SV *self; /* contains this struct */ \ |
|
|
1917 | SV *cb_sv, *fh /* note no trailing ";" */ |
|
|
1918 | |
|
|
1919 | =item EV_CB_DECLARE (type) |
|
|
1920 | |
|
|
1921 | =item EV_CB_INVOKE (watcher, revents) |
|
|
1922 | |
|
|
1923 | =item ev_set_cb (ev, cb) |
|
|
1924 | |
|
|
1925 | Can be used to change the callback member declaration in each watcher, |
|
|
1926 | and the way callbacks are invoked and set. Must expand to a struct member |
|
|
1927 | definition and a statement, respectively. See the F<ev.v> header file for |
|
|
1928 | their default definitions. One possible use for overriding these is to |
|
|
1929 | avoid the C<struct ev_loop *> as first argument in all cases, or to use |
|
|
1930 | method calls instead of plain function calls in C++. |
|
|
1931 | |
|
|
1932 | =head2 EXAMPLES |
|
|
1933 | |
|
|
1934 | For a real-world example of a program the includes libev |
|
|
1935 | verbatim, you can have a look at the EV perl module |
|
|
1936 | (L<http://software.schmorp.de/pkg/EV.html>). It has the libev files in |
|
|
1937 | the F<libev/> subdirectory and includes them in the F<EV/EVAPI.h> (public |
|
|
1938 | interface) and F<EV.xs> (implementation) files. Only the F<EV.xs> file |
|
|
1939 | will be compiled. It is pretty complex because it provides its own header |
|
|
1940 | file. |
|
|
1941 | |
|
|
1942 | The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file |
|
|
1943 | that everybody includes and which overrides some autoconf choices: |
|
|
1944 | |
|
|
1945 | #define EV_USE_POLL 0 |
|
|
1946 | #define EV_MULTIPLICITY 0 |
|
|
1947 | #define EV_PERIODICS 0 |
|
|
1948 | #define EV_CONFIG_H <config.h> |
|
|
1949 | |
|
|
1950 | #include "ev++.h" |
|
|
1951 | |
|
|
1952 | And a F<ev_cpp.C> implementation file that contains libev proper and is compiled: |
|
|
1953 | |
|
|
1954 | #include "ev_cpp.h" |
|
|
1955 | #include "ev.c" |
|
|
1956 | |
|
|
1957 | |
|
|
1958 | =head1 COMPLEXITIES |
|
|
1959 | |
|
|
1960 | In this section the complexities of (many of) the algorithms used inside |
|
|
1961 | libev will be explained. For complexity discussions about backends see the |
|
|
1962 | documentation for C<ev_default_init>. |
|
|
1963 | |
|
|
1964 | =over 4 |
|
|
1965 | |
|
|
1966 | =item Starting and stopping timer/periodic watchers: O(log skipped_other_timers) |
|
|
1967 | |
|
|
1968 | =item Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers) |
|
|
1969 | |
|
|
1970 | =item Starting io/check/prepare/idle/signal/child watchers: O(1) |
|
|
1971 | |
|
|
1972 | =item Stopping check/prepare/idle watchers: O(1) |
|
|
1973 | |
|
|
1974 | =item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % 16)) |
|
|
1975 | |
|
|
1976 | =item Finding the next timer per loop iteration: O(1) |
|
|
1977 | |
|
|
1978 | =item Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd) |
|
|
1979 | |
|
|
1980 | =item Activating one watcher: O(1) |
|
|
1981 | |
|
|
1982 | =back |
|
|
1983 | |
1217 | |
1984 | |
1218 | =head1 AUTHOR |
1985 | =head1 AUTHOR |
1219 | |
1986 | |
1220 | Marc Lehmann <libev@schmorp.de>. |
1987 | Marc Lehmann <libev@schmorp.de>. |
1221 | |
1988 | |