… | |
… | |
98 | =head2 FEATURES |
98 | =head2 FEATURES |
99 | |
99 | |
100 | Libev supports C<select>, C<poll>, the Linux-specific C<epoll>, the |
100 | Libev supports C<select>, C<poll>, the Linux-specific C<epoll>, the |
101 | BSD-specific C<kqueue> and the Solaris-specific event port mechanisms |
101 | BSD-specific C<kqueue> and the Solaris-specific event port mechanisms |
102 | for file descriptor events (C<ev_io>), the Linux C<inotify> interface |
102 | for file descriptor events (C<ev_io>), the Linux C<inotify> interface |
103 | (for C<ev_stat>), relative timers (C<ev_timer>), absolute timers |
103 | (for C<ev_stat>), Linux eventfd/signalfd (for faster and cleaner |
104 | with customised rescheduling (C<ev_periodic>), synchronous signals |
104 | inter-thread wakeup (C<ev_async>)/signal handling (C<ev_signal>)) relative |
105 | (C<ev_signal>), process status change events (C<ev_child>), and event |
105 | timers (C<ev_timer>), absolute timers with customised rescheduling |
106 | watchers dealing with the event loop mechanism itself (C<ev_idle>, |
106 | (C<ev_periodic>), synchronous signals (C<ev_signal>), process status |
107 | C<ev_embed>, C<ev_prepare> and C<ev_check> watchers) as well as |
107 | change events (C<ev_child>), and event watchers dealing with the event |
108 | file watchers (C<ev_stat>) and even limited support for fork events |
108 | loop mechanism itself (C<ev_idle>, C<ev_embed>, C<ev_prepare> and |
109 | (C<ev_fork>). |
109 | C<ev_check> watchers) as well as file watchers (C<ev_stat>) and even |
|
|
110 | limited support for fork events (C<ev_fork>). |
110 | |
111 | |
111 | It also is quite fast (see this |
112 | It also is quite fast (see this |
112 | L<benchmark|http://libev.schmorp.de/bench.html> comparing it to libevent |
113 | L<benchmark|http://libev.schmorp.de/bench.html> comparing it to libevent |
113 | for example). |
114 | for example). |
114 | |
115 | |
… | |
… | |
117 | Libev is very configurable. In this manual the default (and most common) |
118 | Libev is very configurable. In this manual the default (and most common) |
118 | configuration will be described, which supports multiple event loops. For |
119 | configuration will be described, which supports multiple event loops. For |
119 | more info about various configuration options please have a look at |
120 | more info about various configuration options please have a look at |
120 | B<EMBED> section in this manual. If libev was configured without support |
121 | B<EMBED> section in this manual. If libev was configured without support |
121 | for multiple event loops, then all functions taking an initial argument of |
122 | for multiple event loops, then all functions taking an initial argument of |
122 | name C<loop> (which is always of type C<ev_loop *>) will not have |
123 | name C<loop> (which is always of type C<struct ev_loop *>) will not have |
123 | this argument. |
124 | this argument. |
124 | |
125 | |
125 | =head2 TIME REPRESENTATION |
126 | =head2 TIME REPRESENTATION |
126 | |
127 | |
127 | Libev represents time as a single floating point number, representing |
128 | Libev represents time as a single floating point number, representing |
… | |
… | |
344 | useful to try out specific backends to test their performance, or to work |
345 | useful to try out specific backends to test their performance, or to work |
345 | around bugs. |
346 | around bugs. |
346 | |
347 | |
347 | =item C<EVFLAG_FORKCHECK> |
348 | =item C<EVFLAG_FORKCHECK> |
348 | |
349 | |
349 | Instead of calling C<ev_default_fork> or C<ev_loop_fork> manually after |
350 | Instead of calling C<ev_loop_fork> manually after a fork, you can also |
350 | a fork, you can also make libev check for a fork in each iteration by |
351 | make libev check for a fork in each iteration by enabling this flag. |
351 | enabling this flag. |
|
|
352 | |
352 | |
353 | This works by calling C<getpid ()> on every iteration of the loop, |
353 | This works by calling C<getpid ()> on every iteration of the loop, |
354 | and thus this might slow down your event loop if you do a lot of loop |
354 | and thus this might slow down your event loop if you do a lot of loop |
355 | iterations and little real work, but is usually not noticeable (on my |
355 | iterations and little real work, but is usually not noticeable (on my |
356 | GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence |
356 | GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence |
… | |
… | |
369 | When this flag is specified, then libev will not attempt to use the |
369 | When this flag is specified, then libev will not attempt to use the |
370 | I<inotify> API for it's C<ev_stat> watchers. Apart from debugging and |
370 | I<inotify> API for it's C<ev_stat> watchers. Apart from debugging and |
371 | testing, this flag can be useful to conserve inotify file descriptors, as |
371 | testing, this flag can be useful to conserve inotify file descriptors, as |
372 | otherwise each loop using C<ev_stat> watchers consumes one inotify handle. |
372 | otherwise each loop using C<ev_stat> watchers consumes one inotify handle. |
373 | |
373 | |
374 | =item C<EVFLAG_NOSIGNALFD> |
374 | =item C<EVFLAG_SIGNALFD> |
375 | |
375 | |
376 | When this flag is specified, then libev will not attempt to use the |
376 | When this flag is specified, then libev will attempt to use the |
377 | I<signalfd> API for it's C<ev_signal> (and C<ev_child>) watchers. This is |
377 | I<signalfd> API for it's C<ev_signal> (and C<ev_child>) watchers. This API |
378 | probably only useful to work around any bugs in libev. Consequently, this |
378 | delivers signals synchronously, which makes it both faster and might make |
379 | flag might go away once the signalfd functionality is considered stable, |
379 | it possible to get the queued signal data. It can also simplify signal |
380 | so it's useful mostly in environment variables and not in program code. |
380 | handling with threads, as long as you properly block signals in your |
|
|
381 | threads that are not interested in handling them. |
|
|
382 | |
|
|
383 | Signalfd will not be used by default as this changes your signal mask, and |
|
|
384 | there are a lot of shoddy libraries and programs (glib's threadpool for |
|
|
385 | example) that can't properly initialise their signal masks. |
381 | |
386 | |
382 | =item C<EVBACKEND_SELECT> (value 1, portable select backend) |
387 | =item C<EVBACKEND_SELECT> (value 1, portable select backend) |
383 | |
388 | |
384 | This is your standard select(2) backend. Not I<completely> standard, as |
389 | This is your standard select(2) backend. Not I<completely> standard, as |
385 | libev tries to roll its own fd_set with no limits on the number of fds, |
390 | libev tries to roll its own fd_set with no limits on the number of fds, |
… | |
… | |
409 | |
414 | |
410 | This backend maps C<EV_READ> to C<POLLIN | POLLERR | POLLHUP>, and |
415 | This backend maps C<EV_READ> to C<POLLIN | POLLERR | POLLHUP>, and |
411 | C<EV_WRITE> to C<POLLOUT | POLLERR | POLLHUP>. |
416 | C<EV_WRITE> to C<POLLOUT | POLLERR | POLLHUP>. |
412 | |
417 | |
413 | =item C<EVBACKEND_EPOLL> (value 4, Linux) |
418 | =item C<EVBACKEND_EPOLL> (value 4, Linux) |
|
|
419 | |
|
|
420 | Use the linux-specific epoll(7) interface (for both pre- and post-2.6.9 |
|
|
421 | kernels). |
414 | |
422 | |
415 | For few fds, this backend is a bit little slower than poll and select, |
423 | For few fds, this backend is a bit little slower than poll and select, |
416 | but it scales phenomenally better. While poll and select usually scale |
424 | but it scales phenomenally better. While poll and select usually scale |
417 | like O(total_fds) where n is the total number of fds (or the highest fd), |
425 | like O(total_fds) where n is the total number of fds (or the highest fd), |
418 | epoll scales either O(1) or O(active_fds). |
426 | epoll scales either O(1) or O(active_fds). |
… | |
… | |
558 | ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE); |
566 | ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE); |
559 | |
567 | |
560 | =item struct ev_loop *ev_loop_new (unsigned int flags) |
568 | =item struct ev_loop *ev_loop_new (unsigned int flags) |
561 | |
569 | |
562 | Similar to C<ev_default_loop>, but always creates a new event loop that is |
570 | Similar to C<ev_default_loop>, but always creates a new event loop that is |
563 | always distinct from the default loop. Unlike the default loop, it cannot |
571 | always distinct from the default loop. |
564 | handle signal and child watchers, and attempts to do so will be greeted by |
|
|
565 | undefined behaviour (or a failed assertion if assertions are enabled). |
|
|
566 | |
572 | |
567 | Note that this function I<is> thread-safe, and the recommended way to use |
573 | Note that this function I<is> thread-safe, and one common way to use |
568 | libev with threads is indeed to create one loop per thread, and using the |
574 | libev with threads is indeed to create one loop per thread, and using the |
569 | default loop in the "main" or "initial" thread. |
575 | default loop in the "main" or "initial" thread. |
570 | |
576 | |
571 | Example: Try to create a event loop that uses epoll and nothing else. |
577 | Example: Try to create a event loop that uses epoll and nothing else. |
572 | |
578 | |
… | |
… | |
574 | if (!epoller) |
580 | if (!epoller) |
575 | fatal ("no epoll found here, maybe it hides under your chair"); |
581 | fatal ("no epoll found here, maybe it hides under your chair"); |
576 | |
582 | |
577 | =item ev_default_destroy () |
583 | =item ev_default_destroy () |
578 | |
584 | |
579 | Destroys the default loop again (frees all memory and kernel state |
585 | Destroys the default loop (frees all memory and kernel state etc.). None |
580 | etc.). None of the active event watchers will be stopped in the normal |
586 | of the active event watchers will be stopped in the normal sense, so |
581 | sense, so e.g. C<ev_is_active> might still return true. It is your |
587 | e.g. C<ev_is_active> might still return true. It is your responsibility to |
582 | responsibility to either stop all watchers cleanly yourself I<before> |
588 | either stop all watchers cleanly yourself I<before> calling this function, |
583 | calling this function, or cope with the fact afterwards (which is usually |
589 | or cope with the fact afterwards (which is usually the easiest thing, you |
584 | the easiest thing, you can just ignore the watchers and/or C<free ()> them |
590 | can just ignore the watchers and/or C<free ()> them for example). |
585 | for example). |
|
|
586 | |
591 | |
587 | Note that certain global state, such as signal state (and installed signal |
592 | Note that certain global state, such as signal state (and installed signal |
588 | handlers), will not be freed by this function, and related watchers (such |
593 | handlers), will not be freed by this function, and related watchers (such |
589 | as signal and child watchers) would need to be stopped manually. |
594 | as signal and child watchers) would need to be stopped manually. |
590 | |
595 | |
591 | In general it is not advisable to call this function except in the |
596 | In general it is not advisable to call this function except in the |
592 | rare occasion where you really need to free e.g. the signal handling |
597 | rare occasion where you really need to free e.g. the signal handling |
593 | pipe fds. If you need dynamically allocated loops it is better to use |
598 | pipe fds. If you need dynamically allocated loops it is better to use |
594 | C<ev_loop_new> and C<ev_loop_destroy>). |
599 | C<ev_loop_new> and C<ev_loop_destroy>. |
595 | |
600 | |
596 | =item ev_loop_destroy (loop) |
601 | =item ev_loop_destroy (loop) |
597 | |
602 | |
598 | Like C<ev_default_destroy>, but destroys an event loop created by an |
603 | Like C<ev_default_destroy>, but destroys an event loop created by an |
599 | earlier call to C<ev_loop_new>. |
604 | earlier call to C<ev_loop_new>. |
… | |
… | |
605 | name, you can call it anytime, but it makes most sense after forking, in |
610 | name, you can call it anytime, but it makes most sense after forking, in |
606 | the child process (or both child and parent, but that again makes little |
611 | the child process (or both child and parent, but that again makes little |
607 | sense). You I<must> call it in the child before using any of the libev |
612 | sense). You I<must> call it in the child before using any of the libev |
608 | functions, and it will only take effect at the next C<ev_loop> iteration. |
613 | functions, and it will only take effect at the next C<ev_loop> iteration. |
609 | |
614 | |
|
|
615 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
|
|
616 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
|
|
617 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
|
|
618 | during fork. |
|
|
619 | |
610 | On the other hand, you only need to call this function in the child |
620 | On the other hand, you only need to call this function in the child |
611 | process if and only if you want to use the event library in the child. If |
621 | process if and only if you want to use the event loop in the child. If you |
612 | you just fork+exec, you don't have to call it at all. |
622 | just fork+exec or create a new loop in the child, you don't have to call |
|
|
623 | it at all. |
613 | |
624 | |
614 | The function itself is quite fast and it's usually not a problem to call |
625 | The function itself is quite fast and it's usually not a problem to call |
615 | it just in case after a fork. To make this easy, the function will fit in |
626 | it just in case after a fork. To make this easy, the function will fit in |
616 | quite nicely into a call to C<pthread_atfork>: |
627 | quite nicely into a call to C<pthread_atfork>: |
617 | |
628 | |
… | |
… | |
619 | |
630 | |
620 | =item ev_loop_fork (loop) |
631 | =item ev_loop_fork (loop) |
621 | |
632 | |
622 | Like C<ev_default_fork>, but acts on an event loop created by |
633 | Like C<ev_default_fork>, but acts on an event loop created by |
623 | C<ev_loop_new>. Yes, you have to call this on every allocated event loop |
634 | C<ev_loop_new>. Yes, you have to call this on every allocated event loop |
624 | after fork that you want to re-use in the child, and how you do this is |
635 | after fork that you want to re-use in the child, and how you keep track of |
625 | entirely your own problem. |
636 | them is entirely your own problem. |
626 | |
637 | |
627 | =item int ev_is_default_loop (loop) |
638 | =item int ev_is_default_loop (loop) |
628 | |
639 | |
629 | Returns true when the given loop is, in fact, the default loop, and false |
640 | Returns true when the given loop is, in fact, the default loop, and false |
630 | otherwise. |
641 | otherwise. |
631 | |
642 | |
632 | =item unsigned int ev_loop_count (loop) |
643 | =item unsigned int ev_iteration (loop) |
633 | |
644 | |
634 | Returns the count of loop iterations for the loop, which is identical to |
645 | Returns the current iteration count for the loop, which is identical to |
635 | the number of times libev did poll for new events. It starts at C<0> and |
646 | the number of times libev did poll for new events. It starts at C<0> and |
636 | happily wraps around with enough iterations. |
647 | happily wraps around with enough iterations. |
637 | |
648 | |
638 | This value can sometimes be useful as a generation counter of sorts (it |
649 | This value can sometimes be useful as a generation counter of sorts (it |
639 | "ticks" the number of loop iterations), as it roughly corresponds with |
650 | "ticks" the number of loop iterations), as it roughly corresponds with |
640 | C<ev_prepare> and C<ev_check> calls. |
651 | C<ev_prepare> and C<ev_check> calls - and is incremented between the |
|
|
652 | prepare and check phases. |
641 | |
653 | |
642 | =item unsigned int ev_loop_depth (loop) |
654 | =item unsigned int ev_depth (loop) |
643 | |
655 | |
644 | Returns the number of times C<ev_loop> was entered minus the number of |
656 | Returns the number of times C<ev_loop> was entered minus the number of |
645 | times C<ev_loop> was exited, in other words, the recursion depth. |
657 | times C<ev_loop> was exited, in other words, the recursion depth. |
646 | |
658 | |
647 | Outside C<ev_loop>, this number is zero. In a callback, this number is |
659 | Outside C<ev_loop>, this number is zero. In a callback, this number is |
648 | C<1>, unless C<ev_loop> was invoked recursively (or from another thread), |
660 | C<1>, unless C<ev_loop> was invoked recursively (or from another thread), |
649 | in which case it is higher. |
661 | in which case it is higher. |
650 | |
662 | |
651 | Leaving C<ev_loop> abnormally (setjmp/longjmp, cancelling the thread |
663 | Leaving C<ev_loop> abnormally (setjmp/longjmp, cancelling the thread |
652 | etc.), doesn't count as exit. |
664 | etc.), doesn't count as "exit" - consider this as a hint to avoid such |
|
|
665 | ungentleman behaviour unless it's really convenient. |
653 | |
666 | |
654 | =item unsigned int ev_backend (loop) |
667 | =item unsigned int ev_backend (loop) |
655 | |
668 | |
656 | Returns one of the C<EVBACKEND_*> flags indicating the event backend in |
669 | Returns one of the C<EVBACKEND_*> flags indicating the event backend in |
657 | use. |
670 | use. |
… | |
… | |
703 | event loop time (see C<ev_now_update>). |
716 | event loop time (see C<ev_now_update>). |
704 | |
717 | |
705 | =item ev_loop (loop, int flags) |
718 | =item ev_loop (loop, int flags) |
706 | |
719 | |
707 | Finally, this is it, the event handler. This function usually is called |
720 | Finally, this is it, the event handler. This function usually is called |
708 | after you initialised all your watchers and you want to start handling |
721 | after you have initialised all your watchers and you want to start |
709 | events. |
722 | handling events. |
710 | |
723 | |
711 | If the flags argument is specified as C<0>, it will not return until |
724 | If the flags argument is specified as C<0>, it will not return until |
712 | either no event watchers are active anymore or C<ev_unloop> was called. |
725 | either no event watchers are active anymore or C<ev_unloop> was called. |
713 | |
726 | |
714 | Please note that an explicit C<ev_unloop> is usually better than |
727 | Please note that an explicit C<ev_unloop> is usually better than |
… | |
… | |
788 | |
801 | |
789 | Ref/unref can be used to add or remove a reference count on the event |
802 | Ref/unref can be used to add or remove a reference count on the event |
790 | loop: Every watcher keeps one reference, and as long as the reference |
803 | loop: Every watcher keeps one reference, and as long as the reference |
791 | count is nonzero, C<ev_loop> will not return on its own. |
804 | count is nonzero, C<ev_loop> will not return on its own. |
792 | |
805 | |
793 | If you have a watcher you never unregister that should not keep C<ev_loop> |
806 | This is useful when you have a watcher that you never intend to |
794 | from returning, call ev_unref() after starting, and ev_ref() before |
807 | unregister, but that nevertheless should not keep C<ev_loop> from |
|
|
808 | returning. In such a case, call C<ev_unref> after starting, and C<ev_ref> |
795 | stopping it. |
809 | before stopping it. |
796 | |
810 | |
797 | As an example, libev itself uses this for its internal signal pipe: It |
811 | As an example, libev itself uses this for its internal signal pipe: It |
798 | is not visible to the libev user and should not keep C<ev_loop> from |
812 | is not visible to the libev user and should not keep C<ev_loop> from |
799 | exiting if no event watchers registered by it are active. It is also an |
813 | exiting if no event watchers registered by it are active. It is also an |
800 | excellent way to do this for generic recurring timers or from within |
814 | excellent way to do this for generic recurring timers or from within |
… | |
… | |
915 | |
929 | |
916 | While event loop modifications are allowed between invocations of |
930 | While event loop modifications are allowed between invocations of |
917 | C<release> and C<acquire> (that's their only purpose after all), no |
931 | C<release> and C<acquire> (that's their only purpose after all), no |
918 | modifications done will affect the event loop, i.e. adding watchers will |
932 | modifications done will affect the event loop, i.e. adding watchers will |
919 | have no effect on the set of file descriptors being watched, or the time |
933 | have no effect on the set of file descriptors being watched, or the time |
920 | waited. USe an C<ev_async> watcher to wake up C<ev_loop> when you want it |
934 | waited. Use an C<ev_async> watcher to wake up C<ev_loop> when you want it |
921 | to take note of any changes you made. |
935 | to take note of any changes you made. |
922 | |
936 | |
923 | In theory, threads executing C<ev_loop> will be async-cancel safe between |
937 | In theory, threads executing C<ev_loop> will be async-cancel safe between |
924 | invocations of C<release> and C<acquire>. |
938 | invocations of C<release> and C<acquire>. |
925 | |
939 | |
… | |
… | |
1022 | =item C<EV_WRITE> |
1036 | =item C<EV_WRITE> |
1023 | |
1037 | |
1024 | The file descriptor in the C<ev_io> watcher has become readable and/or |
1038 | The file descriptor in the C<ev_io> watcher has become readable and/or |
1025 | writable. |
1039 | writable. |
1026 | |
1040 | |
1027 | =item C<EV_TIMEOUT> |
1041 | =item C<EV_TIMER> |
1028 | |
1042 | |
1029 | The C<ev_timer> watcher has timed out. |
1043 | The C<ev_timer> watcher has timed out. |
1030 | |
1044 | |
1031 | =item C<EV_PERIODIC> |
1045 | =item C<EV_PERIODIC> |
1032 | |
1046 | |
… | |
… | |
1122 | |
1136 | |
1123 | ev_io w; |
1137 | ev_io w; |
1124 | ev_init (&w, my_cb); |
1138 | ev_init (&w, my_cb); |
1125 | ev_io_set (&w, STDIN_FILENO, EV_READ); |
1139 | ev_io_set (&w, STDIN_FILENO, EV_READ); |
1126 | |
1140 | |
1127 | =item C<ev_TYPE_set> (ev_TYPE *, [args]) |
1141 | =item C<ev_TYPE_set> (ev_TYPE *watcher, [args]) |
1128 | |
1142 | |
1129 | This macro initialises the type-specific parts of a watcher. You need to |
1143 | This macro initialises the type-specific parts of a watcher. You need to |
1130 | call C<ev_init> at least once before you call this macro, but you can |
1144 | call C<ev_init> at least once before you call this macro, but you can |
1131 | call C<ev_TYPE_set> any number of times. You must not, however, call this |
1145 | call C<ev_TYPE_set> any number of times. You must not, however, call this |
1132 | macro on a watcher that is active (it can be pending, however, which is a |
1146 | macro on a watcher that is active (it can be pending, however, which is a |
… | |
… | |
1145 | |
1159 | |
1146 | Example: Initialise and set an C<ev_io> watcher in one step. |
1160 | Example: Initialise and set an C<ev_io> watcher in one step. |
1147 | |
1161 | |
1148 | ev_io_init (&w, my_cb, STDIN_FILENO, EV_READ); |
1162 | ev_io_init (&w, my_cb, STDIN_FILENO, EV_READ); |
1149 | |
1163 | |
1150 | =item C<ev_TYPE_start> (loop *, ev_TYPE *watcher) |
1164 | =item C<ev_TYPE_start> (loop, ev_TYPE *watcher) |
1151 | |
1165 | |
1152 | Starts (activates) the given watcher. Only active watchers will receive |
1166 | Starts (activates) the given watcher. Only active watchers will receive |
1153 | events. If the watcher is already active nothing will happen. |
1167 | events. If the watcher is already active nothing will happen. |
1154 | |
1168 | |
1155 | Example: Start the C<ev_io> watcher that is being abused as example in this |
1169 | Example: Start the C<ev_io> watcher that is being abused as example in this |
1156 | whole section. |
1170 | whole section. |
1157 | |
1171 | |
1158 | ev_io_start (EV_DEFAULT_UC, &w); |
1172 | ev_io_start (EV_DEFAULT_UC, &w); |
1159 | |
1173 | |
1160 | =item C<ev_TYPE_stop> (loop *, ev_TYPE *watcher) |
1174 | =item C<ev_TYPE_stop> (loop, ev_TYPE *watcher) |
1161 | |
1175 | |
1162 | Stops the given watcher if active, and clears the pending status (whether |
1176 | Stops the given watcher if active, and clears the pending status (whether |
1163 | the watcher was active or not). |
1177 | the watcher was active or not). |
1164 | |
1178 | |
1165 | It is possible that stopped watchers are pending - for example, |
1179 | It is possible that stopped watchers are pending - for example, |
… | |
… | |
1190 | =item ev_cb_set (ev_TYPE *watcher, callback) |
1204 | =item ev_cb_set (ev_TYPE *watcher, callback) |
1191 | |
1205 | |
1192 | Change the callback. You can change the callback at virtually any time |
1206 | Change the callback. You can change the callback at virtually any time |
1193 | (modulo threads). |
1207 | (modulo threads). |
1194 | |
1208 | |
1195 | =item ev_set_priority (ev_TYPE *watcher, priority) |
1209 | =item ev_set_priority (ev_TYPE *watcher, int priority) |
1196 | |
1210 | |
1197 | =item int ev_priority (ev_TYPE *watcher) |
1211 | =item int ev_priority (ev_TYPE *watcher) |
1198 | |
1212 | |
1199 | Set and query the priority of the watcher. The priority is a small |
1213 | Set and query the priority of the watcher. The priority is a small |
1200 | integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI> |
1214 | integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI> |
… | |
… | |
1231 | returns its C<revents> bitset (as if its callback was invoked). If the |
1245 | returns its C<revents> bitset (as if its callback was invoked). If the |
1232 | watcher isn't pending it does nothing and returns C<0>. |
1246 | watcher isn't pending it does nothing and returns C<0>. |
1233 | |
1247 | |
1234 | Sometimes it can be useful to "poll" a watcher instead of waiting for its |
1248 | Sometimes it can be useful to "poll" a watcher instead of waiting for its |
1235 | callback to be invoked, which can be accomplished with this function. |
1249 | callback to be invoked, which can be accomplished with this function. |
|
|
1250 | |
|
|
1251 | =item ev_feed_event (loop, ev_TYPE *watcher, int revents) |
|
|
1252 | |
|
|
1253 | Feeds the given event set into the event loop, as if the specified event |
|
|
1254 | had happened for the specified watcher (which must be a pointer to an |
|
|
1255 | initialised but not necessarily started event watcher). Obviously you must |
|
|
1256 | not free the watcher as long as it has pending events. |
|
|
1257 | |
|
|
1258 | Stopping the watcher, letting libev invoke it, or calling |
|
|
1259 | C<ev_clear_pending> will clear the pending event, even if the watcher was |
|
|
1260 | not started in the first place. |
|
|
1261 | |
|
|
1262 | See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related |
|
|
1263 | functions that do not need a watcher. |
1236 | |
1264 | |
1237 | =back |
1265 | =back |
1238 | |
1266 | |
1239 | |
1267 | |
1240 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
1268 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
… | |
… | |
1514 | |
1542 | |
1515 | So when you encounter spurious, unexplained daemon exits, make sure you |
1543 | So when you encounter spurious, unexplained daemon exits, make sure you |
1516 | ignore SIGPIPE (and maybe make sure you log the exit status of your daemon |
1544 | ignore SIGPIPE (and maybe make sure you log the exit status of your daemon |
1517 | somewhere, as that would have given you a big clue). |
1545 | somewhere, as that would have given you a big clue). |
1518 | |
1546 | |
|
|
1547 | =head3 The special problem of accept()ing when you can't |
|
|
1548 | |
|
|
1549 | Many implementations of the POSIX C<accept> function (for example, |
|
|
1550 | found in port-2004 Linux) have the peculiar behaviour of not removing a |
|
|
1551 | connection from the pending queue in all error cases. |
|
|
1552 | |
|
|
1553 | For example, larger servers often run out of file descriptors (because |
|
|
1554 | of resource limits), causing C<accept> to fail with C<ENFILE> but not |
|
|
1555 | rejecting the connection, leading to libev signalling readiness on |
|
|
1556 | the next iteration again (the connection still exists after all), and |
|
|
1557 | typically causing the program to loop at 100% CPU usage. |
|
|
1558 | |
|
|
1559 | Unfortunately, the set of errors that cause this issue differs between |
|
|
1560 | operating systems, there is usually little the app can do to remedy the |
|
|
1561 | situation, and no known thread-safe method of removing the connection to |
|
|
1562 | cope with overload is known (to me). |
|
|
1563 | |
|
|
1564 | One of the easiest ways to handle this situation is to just ignore it |
|
|
1565 | - when the program encounters an overload, it will just loop until the |
|
|
1566 | situation is over. While this is a form of busy waiting, no OS offers an |
|
|
1567 | event-based way to handle this situation, so it's the best one can do. |
|
|
1568 | |
|
|
1569 | A better way to handle the situation is to log any errors other than |
|
|
1570 | C<EAGAIN> and C<EWOULDBLOCK>, making sure not to flood the log with such |
|
|
1571 | messages, and continue as usual, which at least gives the user an idea of |
|
|
1572 | what could be wrong ("raise the ulimit!"). For extra points one could stop |
|
|
1573 | the C<ev_io> watcher on the listening fd "for a while", which reduces CPU |
|
|
1574 | usage. |
|
|
1575 | |
|
|
1576 | If your program is single-threaded, then you could also keep a dummy file |
|
|
1577 | descriptor for overload situations (e.g. by opening F</dev/null>), and |
|
|
1578 | when you run into C<ENFILE> or C<EMFILE>, close it, run C<accept>, |
|
|
1579 | close that fd, and create a new dummy fd. This will gracefully refuse |
|
|
1580 | clients under typical overload conditions. |
|
|
1581 | |
|
|
1582 | The last way to handle it is to simply log the error and C<exit>, as |
|
|
1583 | is often done with C<malloc> failures, but this results in an easy |
|
|
1584 | opportunity for a DoS attack. |
1519 | |
1585 | |
1520 | =head3 Watcher-Specific Functions |
1586 | =head3 Watcher-Specific Functions |
1521 | |
1587 | |
1522 | =over 4 |
1588 | =over 4 |
1523 | |
1589 | |
… | |
… | |
1702 | to the current time (meaning we just have some activity :), then call the |
1768 | to the current time (meaning we just have some activity :), then call the |
1703 | callback, which will "do the right thing" and start the timer: |
1769 | callback, which will "do the right thing" and start the timer: |
1704 | |
1770 | |
1705 | ev_init (timer, callback); |
1771 | ev_init (timer, callback); |
1706 | last_activity = ev_now (loop); |
1772 | last_activity = ev_now (loop); |
1707 | callback (loop, timer, EV_TIMEOUT); |
1773 | callback (loop, timer, EV_TIMER); |
1708 | |
1774 | |
1709 | And when there is some activity, simply store the current time in |
1775 | And when there is some activity, simply store the current time in |
1710 | C<last_activity>, no libev calls at all: |
1776 | C<last_activity>, no libev calls at all: |
1711 | |
1777 | |
1712 | last_actiivty = ev_now (loop); |
1778 | last_actiivty = ev_now (loop); |
… | |
… | |
1836 | C<repeat> value), or reset the running timer to the C<repeat> value. |
1902 | C<repeat> value), or reset the running timer to the C<repeat> value. |
1837 | |
1903 | |
1838 | This sounds a bit complicated, see L<Be smart about timeouts>, above, for a |
1904 | This sounds a bit complicated, see L<Be smart about timeouts>, above, for a |
1839 | usage example. |
1905 | usage example. |
1840 | |
1906 | |
1841 | =item ev_timer_remaining (loop, ev_timer *) |
1907 | =item ev_tstamp ev_timer_remaining (loop, ev_timer *) |
1842 | |
1908 | |
1843 | Returns the remaining time until a timer fires. If the timer is active, |
1909 | Returns the remaining time until a timer fires. If the timer is active, |
1844 | then this time is relative to the current event loop time, otherwise it's |
1910 | then this time is relative to the current event loop time, otherwise it's |
1845 | the timeout value currently configured. |
1911 | the timeout value currently configured. |
1846 | |
1912 | |
1847 | That is, after an C<ev_timer_set (w, 5, 7)>, C<ev_timer_remaining> returns |
1913 | That is, after an C<ev_timer_set (w, 5, 7)>, C<ev_timer_remaining> returns |
1848 | C<5>. When the timer is started and one second passes, C<ev_timer_remain> |
1914 | C<5>. When the timer is started and one second passes, C<ev_timer_remaining> |
1849 | will return C<4>. When the timer expires and is restarted, it will return |
1915 | will return C<4>. When the timer expires and is restarted, it will return |
1850 | roughly C<7> (likely slightly less as callback invocation takes some time, |
1916 | roughly C<7> (likely slightly less as callback invocation takes some time, |
1851 | too), and so on. |
1917 | too), and so on. |
1852 | |
1918 | |
1853 | =item ev_tstamp repeat [read-write] |
1919 | =item ev_tstamp repeat [read-write] |
… | |
… | |
2107 | |
2173 | |
2108 | When the first watcher gets started will libev actually register something |
2174 | When the first watcher gets started will libev actually register something |
2109 | with the kernel (thus it coexists with your own signal handlers as long as |
2175 | with the kernel (thus it coexists with your own signal handlers as long as |
2110 | you don't register any with libev for the same signal). |
2176 | you don't register any with libev for the same signal). |
2111 | |
2177 | |
2112 | Both the signal mask state (C<sigprocmask>) and the signal handler state |
|
|
2113 | (C<sigaction>) are unspecified after starting a signal watcher (and after |
|
|
2114 | sotpping it again), that is, libev might or might not block the signal, |
|
|
2115 | and might or might not set or restore the installed signal handler. |
|
|
2116 | |
|
|
2117 | If possible and supported, libev will install its handlers with |
2178 | If possible and supported, libev will install its handlers with |
2118 | C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should |
2179 | C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should |
2119 | not be unduly interrupted. If you have a problem with system calls getting |
2180 | not be unduly interrupted. If you have a problem with system calls getting |
2120 | interrupted by signals you can block all signals in an C<ev_check> watcher |
2181 | interrupted by signals you can block all signals in an C<ev_check> watcher |
2121 | and unblock them in an C<ev_prepare> watcher. |
2182 | and unblock them in an C<ev_prepare> watcher. |
|
|
2183 | |
|
|
2184 | =head3 The special problem of inheritance over fork/execve/pthread_create |
|
|
2185 | |
|
|
2186 | Both the signal mask (C<sigprocmask>) and the signal disposition |
|
|
2187 | (C<sigaction>) are unspecified after starting a signal watcher (and after |
|
|
2188 | stopping it again), that is, libev might or might not block the signal, |
|
|
2189 | and might or might not set or restore the installed signal handler. |
|
|
2190 | |
|
|
2191 | While this does not matter for the signal disposition (libev never |
|
|
2192 | sets signals to C<SIG_IGN>, so handlers will be reset to C<SIG_DFL> on |
|
|
2193 | C<execve>), this matters for the signal mask: many programs do not expect |
|
|
2194 | certain signals to be blocked. |
|
|
2195 | |
|
|
2196 | This means that before calling C<exec> (from the child) you should reset |
|
|
2197 | the signal mask to whatever "default" you expect (all clear is a good |
|
|
2198 | choice usually). |
|
|
2199 | |
|
|
2200 | The simplest way to ensure that the signal mask is reset in the child is |
|
|
2201 | to install a fork handler with C<pthread_atfork> that resets it. That will |
|
|
2202 | catch fork calls done by libraries (such as the libc) as well. |
|
|
2203 | |
|
|
2204 | In current versions of libev, the signal will not be blocked indefinitely |
|
|
2205 | unless you use the C<signalfd> API (C<EV_SIGNALFD>). While this reduces |
|
|
2206 | the window of opportunity for problems, it will not go away, as libev |
|
|
2207 | I<has> to modify the signal mask, at least temporarily. |
|
|
2208 | |
|
|
2209 | So I can't stress this enough: I<If you do not reset your signal mask when |
|
|
2210 | you expect it to be empty, you have a race condition in your code>. This |
|
|
2211 | is not a libev-specific thing, this is true for most event libraries. |
2122 | |
2212 | |
2123 | =head3 Watcher-Specific Functions and Data Members |
2213 | =head3 Watcher-Specific Functions and Data Members |
2124 | |
2214 | |
2125 | =over 4 |
2215 | =over 4 |
2126 | |
2216 | |
… | |
… | |
2943 | =head3 Queueing |
3033 | =head3 Queueing |
2944 | |
3034 | |
2945 | C<ev_async> does not support queueing of data in any way. The reason |
3035 | C<ev_async> does not support queueing of data in any way. The reason |
2946 | is that the author does not know of a simple (or any) algorithm for a |
3036 | is that the author does not know of a simple (or any) algorithm for a |
2947 | multiple-writer-single-reader queue that works in all cases and doesn't |
3037 | multiple-writer-single-reader queue that works in all cases and doesn't |
2948 | need elaborate support such as pthreads. |
3038 | need elaborate support such as pthreads or unportable memory access |
|
|
3039 | semantics. |
2949 | |
3040 | |
2950 | That means that if you want to queue data, you have to provide your own |
3041 | That means that if you want to queue data, you have to provide your own |
2951 | queue. But at least I can tell you how to implement locking around your |
3042 | queue. But at least I can tell you how to implement locking around your |
2952 | queue: |
3043 | queue: |
2953 | |
3044 | |
… | |
… | |
3092 | |
3183 | |
3093 | If C<timeout> is less than 0, then no timeout watcher will be |
3184 | If C<timeout> is less than 0, then no timeout watcher will be |
3094 | started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and |
3185 | started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and |
3095 | repeat = 0) will be started. C<0> is a valid timeout. |
3186 | repeat = 0) will be started. C<0> is a valid timeout. |
3096 | |
3187 | |
3097 | The callback has the type C<void (*cb)(int revents, void *arg)> and gets |
3188 | The callback has the type C<void (*cb)(int revents, void *arg)> and is |
3098 | passed an C<revents> set like normal event callbacks (a combination of |
3189 | passed an C<revents> set like normal event callbacks (a combination of |
3099 | C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg> |
3190 | C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMER>) and the C<arg> |
3100 | value passed to C<ev_once>. Note that it is possible to receive I<both> |
3191 | value passed to C<ev_once>. Note that it is possible to receive I<both> |
3101 | a timeout and an io event at the same time - you probably should give io |
3192 | a timeout and an io event at the same time - you probably should give io |
3102 | events precedence. |
3193 | events precedence. |
3103 | |
3194 | |
3104 | Example: wait up to ten seconds for data to appear on STDIN_FILENO. |
3195 | Example: wait up to ten seconds for data to appear on STDIN_FILENO. |
3105 | |
3196 | |
3106 | static void stdin_ready (int revents, void *arg) |
3197 | static void stdin_ready (int revents, void *arg) |
3107 | { |
3198 | { |
3108 | if (revents & EV_READ) |
3199 | if (revents & EV_READ) |
3109 | /* stdin might have data for us, joy! */; |
3200 | /* stdin might have data for us, joy! */; |
3110 | else if (revents & EV_TIMEOUT) |
3201 | else if (revents & EV_TIMER) |
3111 | /* doh, nothing entered */; |
3202 | /* doh, nothing entered */; |
3112 | } |
3203 | } |
3113 | |
3204 | |
3114 | ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
3205 | ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
3115 | |
3206 | |
3116 | =item ev_feed_event (struct ev_loop *, watcher *, int revents) |
|
|
3117 | |
|
|
3118 | Feeds the given event set into the event loop, as if the specified event |
|
|
3119 | had happened for the specified watcher (which must be a pointer to an |
|
|
3120 | initialised but not necessarily started event watcher). |
|
|
3121 | |
|
|
3122 | =item ev_feed_fd_event (struct ev_loop *, int fd, int revents) |
3207 | =item ev_feed_fd_event (loop, int fd, int revents) |
3123 | |
3208 | |
3124 | Feed an event on the given fd, as if a file descriptor backend detected |
3209 | Feed an event on the given fd, as if a file descriptor backend detected |
3125 | the given events it. |
3210 | the given events it. |
3126 | |
3211 | |
3127 | =item ev_feed_signal_event (struct ev_loop *loop, int signum) |
3212 | =item ev_feed_signal_event (loop, int signum) |
3128 | |
3213 | |
3129 | Feed an event as if the given signal occurred (C<loop> must be the default |
3214 | Feed an event as if the given signal occurred (C<loop> must be the default |
3130 | loop!). |
3215 | loop!). |
3131 | |
3216 | |
3132 | =back |
3217 | =back |
… | |
… | |
3212 | |
3297 | |
3213 | =over 4 |
3298 | =over 4 |
3214 | |
3299 | |
3215 | =item ev::TYPE::TYPE () |
3300 | =item ev::TYPE::TYPE () |
3216 | |
3301 | |
3217 | =item ev::TYPE::TYPE (struct ev_loop *) |
3302 | =item ev::TYPE::TYPE (loop) |
3218 | |
3303 | |
3219 | =item ev::TYPE::~TYPE |
3304 | =item ev::TYPE::~TYPE |
3220 | |
3305 | |
3221 | The constructor (optionally) takes an event loop to associate the watcher |
3306 | The constructor (optionally) takes an event loop to associate the watcher |
3222 | with. If it is omitted, it will use C<EV_DEFAULT>. |
3307 | with. If it is omitted, it will use C<EV_DEFAULT>. |
… | |
… | |
3299 | Example: Use a plain function as callback. |
3384 | Example: Use a plain function as callback. |
3300 | |
3385 | |
3301 | static void io_cb (ev::io &w, int revents) { } |
3386 | static void io_cb (ev::io &w, int revents) { } |
3302 | iow.set <io_cb> (); |
3387 | iow.set <io_cb> (); |
3303 | |
3388 | |
3304 | =item w->set (struct ev_loop *) |
3389 | =item w->set (loop) |
3305 | |
3390 | |
3306 | Associates a different C<struct ev_loop> with this watcher. You can only |
3391 | Associates a different C<struct ev_loop> with this watcher. You can only |
3307 | do this when the watcher is inactive (and not pending either). |
3392 | do this when the watcher is inactive (and not pending either). |
3308 | |
3393 | |
3309 | =item w->set ([arguments]) |
3394 | =item w->set ([arguments]) |
… | |
… | |
3406 | =item Ocaml |
3491 | =item Ocaml |
3407 | |
3492 | |
3408 | Erkki Seppala has written Ocaml bindings for libev, to be found at |
3493 | Erkki Seppala has written Ocaml bindings for libev, to be found at |
3409 | L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>. |
3494 | L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>. |
3410 | |
3495 | |
|
|
3496 | =item Lua |
|
|
3497 | |
|
|
3498 | Brian Maher has written a partial interface to libev for lua (at the |
|
|
3499 | time of this writing, only C<ev_io> and C<ev_timer>), to be found at |
|
|
3500 | L<http://github.com/brimworks/lua-ev>. |
|
|
3501 | |
3411 | =back |
3502 | =back |
3412 | |
3503 | |
3413 | |
3504 | |
3414 | =head1 MACRO MAGIC |
3505 | =head1 MACRO MAGIC |
3415 | |
3506 | |
… | |
… | |
3568 | libev.m4 |
3659 | libev.m4 |
3569 | |
3660 | |
3570 | =head2 PREPROCESSOR SYMBOLS/MACROS |
3661 | =head2 PREPROCESSOR SYMBOLS/MACROS |
3571 | |
3662 | |
3572 | Libev can be configured via a variety of preprocessor symbols you have to |
3663 | Libev can be configured via a variety of preprocessor symbols you have to |
3573 | define before including any of its files. The default in the absence of |
3664 | define before including (or compiling) any of its files. The default in |
3574 | autoconf is documented for every option. |
3665 | the absence of autoconf is documented for every option. |
|
|
3666 | |
|
|
3667 | Symbols marked with "(h)" do not change the ABI, and can have different |
|
|
3668 | values when compiling libev vs. including F<ev.h>, so it is permissible |
|
|
3669 | to redefine them before including F<ev.h> without breakign compatibility |
|
|
3670 | to a compiled library. All other symbols change the ABI, which means all |
|
|
3671 | users of libev and the libev code itself must be compiled with compatible |
|
|
3672 | settings. |
3575 | |
3673 | |
3576 | =over 4 |
3674 | =over 4 |
3577 | |
3675 | |
3578 | =item EV_STANDALONE |
3676 | =item EV_STANDALONE (h) |
3579 | |
3677 | |
3580 | Must always be C<1> if you do not use autoconf configuration, which |
3678 | Must always be C<1> if you do not use autoconf configuration, which |
3581 | keeps libev from including F<config.h>, and it also defines dummy |
3679 | keeps libev from including F<config.h>, and it also defines dummy |
3582 | implementations for some libevent functions (such as logging, which is not |
3680 | implementations for some libevent functions (such as logging, which is not |
3583 | supported). It will also not define any of the structs usually found in |
3681 | supported). It will also not define any of the structs usually found in |
3584 | F<event.h> that are not directly supported by the libev core alone. |
3682 | F<event.h> that are not directly supported by the libev core alone. |
3585 | |
3683 | |
3586 | In stanbdalone mode, libev will still try to automatically deduce the |
3684 | In standalone mode, libev will still try to automatically deduce the |
3587 | configuration, but has to be more conservative. |
3685 | configuration, but has to be more conservative. |
3588 | |
3686 | |
3589 | =item EV_USE_MONOTONIC |
3687 | =item EV_USE_MONOTONIC |
3590 | |
3688 | |
3591 | If defined to be C<1>, libev will try to detect the availability of the |
3689 | If defined to be C<1>, libev will try to detect the availability of the |
… | |
… | |
3656 | be used is the winsock select). This means that it will call |
3754 | be used is the winsock select). This means that it will call |
3657 | C<_get_osfhandle> on the fd to convert it to an OS handle. Otherwise, |
3755 | C<_get_osfhandle> on the fd to convert it to an OS handle. Otherwise, |
3658 | it is assumed that all these functions actually work on fds, even |
3756 | it is assumed that all these functions actually work on fds, even |
3659 | on win32. Should not be defined on non-win32 platforms. |
3757 | on win32. Should not be defined on non-win32 platforms. |
3660 | |
3758 | |
3661 | =item EV_FD_TO_WIN32_HANDLE |
3759 | =item EV_FD_TO_WIN32_HANDLE(fd) |
3662 | |
3760 | |
3663 | If C<EV_SELECT_IS_WINSOCKET> is enabled, then libev needs a way to map |
3761 | If C<EV_SELECT_IS_WINSOCKET> is enabled, then libev needs a way to map |
3664 | file descriptors to socket handles. When not defining this symbol (the |
3762 | file descriptors to socket handles. When not defining this symbol (the |
3665 | default), then libev will call C<_get_osfhandle>, which is usually |
3763 | default), then libev will call C<_get_osfhandle>, which is usually |
3666 | correct. In some cases, programs use their own file descriptor management, |
3764 | correct. In some cases, programs use their own file descriptor management, |
3667 | in which case they can provide this function to map fds to socket handles. |
3765 | in which case they can provide this function to map fds to socket handles. |
|
|
3766 | |
|
|
3767 | =item EV_WIN32_HANDLE_TO_FD(handle) |
|
|
3768 | |
|
|
3769 | If C<EV_SELECT_IS_WINSOCKET> then libev maps handles to file descriptors |
|
|
3770 | using the standard C<_open_osfhandle> function. For programs implementing |
|
|
3771 | their own fd to handle mapping, overwriting this function makes it easier |
|
|
3772 | to do so. This can be done by defining this macro to an appropriate value. |
|
|
3773 | |
|
|
3774 | =item EV_WIN32_CLOSE_FD(fd) |
|
|
3775 | |
|
|
3776 | If programs implement their own fd to handle mapping on win32, then this |
|
|
3777 | macro can be used to override the C<close> function, useful to unregister |
|
|
3778 | file descriptors again. Note that the replacement function has to close |
|
|
3779 | the underlying OS handle. |
3668 | |
3780 | |
3669 | =item EV_USE_POLL |
3781 | =item EV_USE_POLL |
3670 | |
3782 | |
3671 | If defined to be C<1>, libev will compile in support for the C<poll>(2) |
3783 | If defined to be C<1>, libev will compile in support for the C<poll>(2) |
3672 | backend. Otherwise it will be enabled on non-win32 platforms. It |
3784 | backend. Otherwise it will be enabled on non-win32 platforms. It |
… | |
… | |
3719 | as well as for signal and thread safety in C<ev_async> watchers. |
3831 | as well as for signal and thread safety in C<ev_async> watchers. |
3720 | |
3832 | |
3721 | In the absence of this define, libev will use C<sig_atomic_t volatile> |
3833 | In the absence of this define, libev will use C<sig_atomic_t volatile> |
3722 | (from F<signal.h>), which is usually good enough on most platforms. |
3834 | (from F<signal.h>), which is usually good enough on most platforms. |
3723 | |
3835 | |
3724 | =item EV_H |
3836 | =item EV_H (h) |
3725 | |
3837 | |
3726 | The name of the F<ev.h> header file used to include it. The default if |
3838 | The name of the F<ev.h> header file used to include it. The default if |
3727 | undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be |
3839 | undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be |
3728 | used to virtually rename the F<ev.h> header file in case of conflicts. |
3840 | used to virtually rename the F<ev.h> header file in case of conflicts. |
3729 | |
3841 | |
3730 | =item EV_CONFIG_H |
3842 | =item EV_CONFIG_H (h) |
3731 | |
3843 | |
3732 | If C<EV_STANDALONE> isn't C<1>, this variable can be used to override |
3844 | If C<EV_STANDALONE> isn't C<1>, this variable can be used to override |
3733 | F<ev.c>'s idea of where to find the F<config.h> file, similarly to |
3845 | F<ev.c>'s idea of where to find the F<config.h> file, similarly to |
3734 | C<EV_H>, above. |
3846 | C<EV_H>, above. |
3735 | |
3847 | |
3736 | =item EV_EVENT_H |
3848 | =item EV_EVENT_H (h) |
3737 | |
3849 | |
3738 | Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea |
3850 | Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea |
3739 | of how the F<event.h> header can be found, the default is C<"event.h">. |
3851 | of how the F<event.h> header can be found, the default is C<"event.h">. |
3740 | |
3852 | |
3741 | =item EV_PROTOTYPES |
3853 | =item EV_PROTOTYPES (h) |
3742 | |
3854 | |
3743 | If defined to be C<0>, then F<ev.h> will not define any function |
3855 | If defined to be C<0>, then F<ev.h> will not define any function |
3744 | prototypes, but still define all the structs and other symbols. This is |
3856 | prototypes, but still define all the structs and other symbols. This is |
3745 | occasionally useful if you want to provide your own wrapper functions |
3857 | occasionally useful if you want to provide your own wrapper functions |
3746 | around libev functions. |
3858 | around libev functions. |
… | |
… | |
3768 | fine. |
3880 | fine. |
3769 | |
3881 | |
3770 | If your embedding application does not need any priorities, defining these |
3882 | If your embedding application does not need any priorities, defining these |
3771 | both to C<0> will save some memory and CPU. |
3883 | both to C<0> will save some memory and CPU. |
3772 | |
3884 | |
3773 | =item EV_PERIODIC_ENABLE |
3885 | =item EV_PERIODIC_ENABLE, EV_IDLE_ENABLE, EV_EMBED_ENABLE, EV_STAT_ENABLE, |
|
|
3886 | EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE, |
|
|
3887 | EV_ASYNC_ENABLE, EV_CHILD_ENABLE. |
3774 | |
3888 | |
3775 | If undefined or defined to be C<1>, then periodic timers are supported. If |
3889 | If undefined or defined to be C<1> (and the platform supports it), then |
3776 | defined to be C<0>, then they are not. Disabling them saves a few kB of |
3890 | the respective watcher type is supported. If defined to be C<0>, then it |
3777 | code. |
3891 | is not. Disabling watcher types mainly saves codesize. |
3778 | |
3892 | |
3779 | =item EV_IDLE_ENABLE |
3893 | =item EV_FEATURES |
3780 | |
|
|
3781 | If undefined or defined to be C<1>, then idle watchers are supported. If |
|
|
3782 | defined to be C<0>, then they are not. Disabling them saves a few kB of |
|
|
3783 | code. |
|
|
3784 | |
|
|
3785 | =item EV_EMBED_ENABLE |
|
|
3786 | |
|
|
3787 | If undefined or defined to be C<1>, then embed watchers are supported. If |
|
|
3788 | defined to be C<0>, then they are not. Embed watchers rely on most other |
|
|
3789 | watcher types, which therefore must not be disabled. |
|
|
3790 | |
|
|
3791 | =item EV_STAT_ENABLE |
|
|
3792 | |
|
|
3793 | If undefined or defined to be C<1>, then stat watchers are supported. If |
|
|
3794 | defined to be C<0>, then they are not. |
|
|
3795 | |
|
|
3796 | =item EV_FORK_ENABLE |
|
|
3797 | |
|
|
3798 | If undefined or defined to be C<1>, then fork watchers are supported. If |
|
|
3799 | defined to be C<0>, then they are not. |
|
|
3800 | |
|
|
3801 | =item EV_ASYNC_ENABLE |
|
|
3802 | |
|
|
3803 | If undefined or defined to be C<1>, then async watchers are supported. If |
|
|
3804 | defined to be C<0>, then they are not. |
|
|
3805 | |
|
|
3806 | =item EV_MINIMAL |
|
|
3807 | |
3894 | |
3808 | If you need to shave off some kilobytes of code at the expense of some |
3895 | If you need to shave off some kilobytes of code at the expense of some |
3809 | speed (but with the full API), define this symbol to C<1>. Currently this |
3896 | speed (but with the full API), you can define this symbol to request |
3810 | is used to override some inlining decisions, saves roughly 30% code size |
3897 | certain subsets of functionality. The default is to enable all features |
3811 | on amd64. It also selects a much smaller 2-heap for timer management over |
3898 | that can be enabled on the platform. |
3812 | the default 4-heap. |
|
|
3813 | |
3899 | |
3814 | You can save even more by disabling watcher types you do not need |
3900 | A typical way to use this symbol is to define it to C<0> (or to a bitset |
3815 | and setting C<EV_MAXPRI> == C<EV_MINPRI>. Also, disabling C<assert> |
3901 | with some broad features you want) and then selectively re-enable |
3816 | (C<-DNDEBUG>) will usually reduce code size a lot. |
3902 | additional parts you want, for example if you want everything minimal, |
|
|
3903 | but multiple event loop support, async and child watchers and the poll |
|
|
3904 | backend, use this: |
3817 | |
3905 | |
3818 | Defining C<EV_MINIMAL> to C<2> will additionally reduce the core API to |
3906 | #define EV_FEATURES 0 |
3819 | provide a bare-bones event library. See C<ev.h> for details on what parts |
3907 | #define EV_MULTIPLICITY 1 |
3820 | of the API are still available, and do not complain if this subset changes |
3908 | #define EV_USE_POLL 1 |
3821 | over time. |
3909 | #define EV_CHILD_ENABLE 1 |
|
|
3910 | #define EV_ASYNC_ENABLE 1 |
|
|
3911 | |
|
|
3912 | The actual value is a bitset, it can be a combination of the following |
|
|
3913 | values: |
|
|
3914 | |
|
|
3915 | =over 4 |
|
|
3916 | |
|
|
3917 | =item C<1> - faster/larger code |
|
|
3918 | |
|
|
3919 | Use larger code to speed up some operations. |
|
|
3920 | |
|
|
3921 | Currently this is used to override some inlining decisions (enlarging the roughly |
|
|
3922 | 30% code size on amd64. |
|
|
3923 | |
|
|
3924 | When optimising for size, use of compiler flags such as C<-Os> with |
|
|
3925 | gcc recommended, as well as C<-DNDEBUG>, as libev contains a number of |
|
|
3926 | assertions. |
|
|
3927 | |
|
|
3928 | =item C<2> - faster/larger data structures |
|
|
3929 | |
|
|
3930 | Replaces the small 2-heap for timer management by a faster 4-heap, larger |
|
|
3931 | hash table sizes and so on. This will usually further increase codesize |
|
|
3932 | and can additionally have an effect on the size of data structures at |
|
|
3933 | runtime. |
|
|
3934 | |
|
|
3935 | =item C<4> - full API configuration |
|
|
3936 | |
|
|
3937 | This enables priorities (sets C<EV_MAXPRI>=2 and C<EV_MINPRI>=-2), and |
|
|
3938 | enables multiplicity (C<EV_MULTIPLICITY>=1). |
|
|
3939 | |
|
|
3940 | =item C<8> - full API |
|
|
3941 | |
|
|
3942 | This enables a lot of the "lesser used" API functions. See C<ev.h> for |
|
|
3943 | details on which parts of the API are still available without this |
|
|
3944 | feature, and do not complain if this subset changes over time. |
|
|
3945 | |
|
|
3946 | =item C<16> - enable all optional watcher types |
|
|
3947 | |
|
|
3948 | Enables all optional watcher types. If you want to selectively enable |
|
|
3949 | only some watcher types other than I/O and timers (e.g. prepare, |
|
|
3950 | embed, async, child...) you can enable them manually by defining |
|
|
3951 | C<EV_watchertype_ENABLE> to C<1> instead. |
|
|
3952 | |
|
|
3953 | =item C<32> - enable all backends |
|
|
3954 | |
|
|
3955 | This enables all backends - without this feature, you need to enable at |
|
|
3956 | least one backend manually (C<EV_USE_SELECT> is a good choice). |
|
|
3957 | |
|
|
3958 | =item C<64> - enable OS-specific "helper" APIs |
|
|
3959 | |
|
|
3960 | Enable inotify, eventfd, signalfd and similar OS-specific helper APIs by |
|
|
3961 | default. |
|
|
3962 | |
|
|
3963 | =back |
|
|
3964 | |
|
|
3965 | Compiling with C<gcc -Os -DEV_STANDALONE -DEV_USE_EPOLL=1 -DEV_FEATURES=0> |
|
|
3966 | reduces the compiled size of libev from 24.7Kb code/2.8Kb data to 6.5Kb |
|
|
3967 | code/0.3Kb data on my GNU/Linux amd64 system, while still giving you I/O |
|
|
3968 | watchers, timers and monotonic clock support. |
|
|
3969 | |
|
|
3970 | With an intelligent-enough linker (gcc+binutils are intelligent enough |
|
|
3971 | when you use C<-Wl,--gc-sections -ffunction-sections>) functions unused by |
|
|
3972 | your program might be left out as well - a binary starting a timer and an |
|
|
3973 | I/O watcher then might come out at only 5Kb. |
|
|
3974 | |
|
|
3975 | =item EV_AVOID_STDIO |
|
|
3976 | |
|
|
3977 | If this is set to C<1> at compiletime, then libev will avoid using stdio |
|
|
3978 | functions (printf, scanf, perror etc.). This will increase the codesize |
|
|
3979 | somewhat, but if your program doesn't otherwise depend on stdio and your |
|
|
3980 | libc allows it, this avoids linking in the stdio library which is quite |
|
|
3981 | big. |
|
|
3982 | |
|
|
3983 | Note that error messages might become less precise when this option is |
|
|
3984 | enabled. |
3822 | |
3985 | |
3823 | =item EV_NSIG |
3986 | =item EV_NSIG |
3824 | |
3987 | |
3825 | The highest supported signal number, +1 (or, the number of |
3988 | The highest supported signal number, +1 (or, the number of |
3826 | signals): Normally, libev tries to deduce the maximum number of signals |
3989 | signals): Normally, libev tries to deduce the maximum number of signals |
… | |
… | |
3830 | statically allocates some 12-24 bytes per signal number. |
3993 | statically allocates some 12-24 bytes per signal number. |
3831 | |
3994 | |
3832 | =item EV_PID_HASHSIZE |
3995 | =item EV_PID_HASHSIZE |
3833 | |
3996 | |
3834 | C<ev_child> watchers use a small hash table to distribute workload by |
3997 | C<ev_child> watchers use a small hash table to distribute workload by |
3835 | pid. The default size is C<16> (or C<1> with C<EV_MINIMAL>), usually more |
3998 | pid. The default size is C<16> (or C<1> with C<EV_FEATURES> disabled), |
3836 | than enough. If you need to manage thousands of children you might want to |
3999 | usually more than enough. If you need to manage thousands of children you |
3837 | increase this value (I<must> be a power of two). |
4000 | might want to increase this value (I<must> be a power of two). |
3838 | |
4001 | |
3839 | =item EV_INOTIFY_HASHSIZE |
4002 | =item EV_INOTIFY_HASHSIZE |
3840 | |
4003 | |
3841 | C<ev_stat> watchers use a small hash table to distribute workload by |
4004 | C<ev_stat> watchers use a small hash table to distribute workload by |
3842 | inotify watch id. The default size is C<16> (or C<1> with C<EV_MINIMAL>), |
4005 | inotify watch id. The default size is C<16> (or C<1> with C<EV_FEATURES> |
3843 | usually more than enough. If you need to manage thousands of C<ev_stat> |
4006 | disabled), usually more than enough. If you need to manage thousands of |
3844 | watchers you might want to increase this value (I<must> be a power of |
4007 | C<ev_stat> watchers you might want to increase this value (I<must> be a |
3845 | two). |
4008 | power of two). |
3846 | |
4009 | |
3847 | =item EV_USE_4HEAP |
4010 | =item EV_USE_4HEAP |
3848 | |
4011 | |
3849 | Heaps are not very cache-efficient. To improve the cache-efficiency of the |
4012 | Heaps are not very cache-efficient. To improve the cache-efficiency of the |
3850 | timer and periodics heaps, libev uses a 4-heap when this symbol is defined |
4013 | timer and periodics heaps, libev uses a 4-heap when this symbol is defined |
3851 | to C<1>. The 4-heap uses more complicated (longer) code but has noticeably |
4014 | to C<1>. The 4-heap uses more complicated (longer) code but has noticeably |
3852 | faster performance with many (thousands) of watchers. |
4015 | faster performance with many (thousands) of watchers. |
3853 | |
4016 | |
3854 | The default is C<1> unless C<EV_MINIMAL> is set in which case it is C<0> |
4017 | The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it |
3855 | (disabled). |
4018 | will be C<0>. |
3856 | |
4019 | |
3857 | =item EV_HEAP_CACHE_AT |
4020 | =item EV_HEAP_CACHE_AT |
3858 | |
4021 | |
3859 | Heaps are not very cache-efficient. To improve the cache-efficiency of the |
4022 | Heaps are not very cache-efficient. To improve the cache-efficiency of the |
3860 | timer and periodics heaps, libev can cache the timestamp (I<at>) within |
4023 | timer and periodics heaps, libev can cache the timestamp (I<at>) within |
3861 | the heap structure (selected by defining C<EV_HEAP_CACHE_AT> to C<1>), |
4024 | the heap structure (selected by defining C<EV_HEAP_CACHE_AT> to C<1>), |
3862 | which uses 8-12 bytes more per watcher and a few hundred bytes more code, |
4025 | which uses 8-12 bytes more per watcher and a few hundred bytes more code, |
3863 | but avoids random read accesses on heap changes. This improves performance |
4026 | but avoids random read accesses on heap changes. This improves performance |
3864 | noticeably with many (hundreds) of watchers. |
4027 | noticeably with many (hundreds) of watchers. |
3865 | |
4028 | |
3866 | The default is C<1> unless C<EV_MINIMAL> is set in which case it is C<0> |
4029 | The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it |
3867 | (disabled). |
4030 | will be C<0>. |
3868 | |
4031 | |
3869 | =item EV_VERIFY |
4032 | =item EV_VERIFY |
3870 | |
4033 | |
3871 | Controls how much internal verification (see C<ev_loop_verify ()>) will |
4034 | Controls how much internal verification (see C<ev_loop_verify ()>) will |
3872 | be done: If set to C<0>, no internal verification code will be compiled |
4035 | be done: If set to C<0>, no internal verification code will be compiled |
… | |
… | |
3874 | called. If set to C<2>, then the internal verification code will be |
4037 | called. If set to C<2>, then the internal verification code will be |
3875 | called once per loop, which can slow down libev. If set to C<3>, then the |
4038 | called once per loop, which can slow down libev. If set to C<3>, then the |
3876 | verification code will be called very frequently, which will slow down |
4039 | verification code will be called very frequently, which will slow down |
3877 | libev considerably. |
4040 | libev considerably. |
3878 | |
4041 | |
3879 | The default is C<1>, unless C<EV_MINIMAL> is set, in which case it will be |
4042 | The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it |
3880 | C<0>. |
4043 | will be C<0>. |
3881 | |
4044 | |
3882 | =item EV_COMMON |
4045 | =item EV_COMMON |
3883 | |
4046 | |
3884 | By default, all watchers have a C<void *data> member. By redefining |
4047 | By default, all watchers have a C<void *data> member. By redefining |
3885 | this macro to a something else you can include more and other types of |
4048 | this macro to a something else you can include more and other types of |
… | |
… | |
3943 | file. |
4106 | file. |
3944 | |
4107 | |
3945 | The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file |
4108 | The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file |
3946 | that everybody includes and which overrides some configure choices: |
4109 | that everybody includes and which overrides some configure choices: |
3947 | |
4110 | |
3948 | #define EV_MINIMAL 1 |
4111 | #define EV_FEATURES 8 |
3949 | #define EV_USE_POLL 0 |
4112 | #define EV_USE_SELECT 1 |
3950 | #define EV_MULTIPLICITY 0 |
|
|
3951 | #define EV_PERIODIC_ENABLE 0 |
4113 | #define EV_PREPARE_ENABLE 1 |
|
|
4114 | #define EV_IDLE_ENABLE 1 |
3952 | #define EV_STAT_ENABLE 0 |
4115 | #define EV_SIGNAL_ENABLE 1 |
3953 | #define EV_FORK_ENABLE 0 |
4116 | #define EV_CHILD_ENABLE 1 |
|
|
4117 | #define EV_USE_STDEXCEPT 0 |
3954 | #define EV_CONFIG_H <config.h> |
4118 | #define EV_CONFIG_H <config.h> |
3955 | #define EV_MINPRI 0 |
|
|
3956 | #define EV_MAXPRI 0 |
|
|
3957 | |
4119 | |
3958 | #include "ev++.h" |
4120 | #include "ev++.h" |
3959 | |
4121 | |
3960 | And a F<ev_cpp.C> implementation file that contains libev proper and is compiled: |
4122 | And a F<ev_cpp.C> implementation file that contains libev proper and is compiled: |
3961 | |
4123 | |
… | |
… | |
4463 | involves iterating over all running async watchers or all signal numbers. |
4625 | involves iterating over all running async watchers or all signal numbers. |
4464 | |
4626 | |
4465 | =back |
4627 | =back |
4466 | |
4628 | |
4467 | |
4629 | |
|
|
4630 | =head1 PORTING FROM LIBEV 3.X TO 4.X |
|
|
4631 | |
|
|
4632 | The major version 4 introduced some minor incompatible changes to the API. |
|
|
4633 | |
|
|
4634 | At the moment, the C<ev.h> header file tries to implement superficial |
|
|
4635 | compatibility, so most programs should still compile. Those might be |
|
|
4636 | removed in later versions of libev, so better update early than late. |
|
|
4637 | |
|
|
4638 | =over 4 |
|
|
4639 | |
|
|
4640 | =item C<ev_loop_count> renamed to C<ev_iteration> |
|
|
4641 | |
|
|
4642 | =item C<ev_loop_depth> renamed to C<ev_depth> |
|
|
4643 | |
|
|
4644 | =item C<ev_loop_verify> renamed to C<ev_verify> |
|
|
4645 | |
|
|
4646 | Most functions working on C<struct ev_loop> objects don't have an |
|
|
4647 | C<ev_loop_> prefix, so it was removed. Note that C<ev_loop_fork> is |
|
|
4648 | still called C<ev_loop_fork> because it would otherwise clash with the |
|
|
4649 | C<ev_frok> typedef. |
|
|
4650 | |
|
|
4651 | =item C<EV_TIMEOUT> renamed to C<EV_TIMER> in C<revents> |
|
|
4652 | |
|
|
4653 | This is a simple rename - all other watcher types use their name |
|
|
4654 | as revents flag, and now C<ev_timer> does, too. |
|
|
4655 | |
|
|
4656 | Both C<EV_TIMER> and C<EV_TIMEOUT> symbols were present in 3.x versions |
|
|
4657 | and continue to be present for the forseeable future, so this is mostly a |
|
|
4658 | documentation change. |
|
|
4659 | |
|
|
4660 | =item C<EV_MINIMAL> mechanism replaced by C<EV_FEATURES> |
|
|
4661 | |
|
|
4662 | The preprocessor symbol C<EV_MINIMAL> has been replaced by a different |
|
|
4663 | mechanism, C<EV_FEATURES>. Programs using C<EV_MINIMAL> usually compile |
|
|
4664 | and work, but the library code will of course be larger. |
|
|
4665 | |
|
|
4666 | =back |
|
|
4667 | |
|
|
4668 | |
4468 | =head1 GLOSSARY |
4669 | =head1 GLOSSARY |
4469 | |
4670 | |
4470 | =over 4 |
4671 | =over 4 |
4471 | |
4672 | |
4472 | =item active |
4673 | =item active |
… | |
… | |
4493 | A change of state of some external event, such as data now being available |
4694 | A change of state of some external event, such as data now being available |
4494 | for reading on a file descriptor, time having passed or simply not having |
4695 | for reading on a file descriptor, time having passed or simply not having |
4495 | any other events happening anymore. |
4696 | any other events happening anymore. |
4496 | |
4697 | |
4497 | In libev, events are represented as single bits (such as C<EV_READ> or |
4698 | In libev, events are represented as single bits (such as C<EV_READ> or |
4498 | C<EV_TIMEOUT>). |
4699 | C<EV_TIMER>). |
4499 | |
4700 | |
4500 | =item event library |
4701 | =item event library |
4501 | |
4702 | |
4502 | A software package implementing an event model and loop. |
4703 | A software package implementing an event model and loop. |
4503 | |
4704 | |