… | |
… | |
75 | While this document tries to be as complete as possible in documenting |
75 | While this document tries to be as complete as possible in documenting |
76 | libev, its usage and the rationale behind its design, it is not a tutorial |
76 | libev, its usage and the rationale behind its design, it is not a tutorial |
77 | on event-based programming, nor will it introduce event-based programming |
77 | on event-based programming, nor will it introduce event-based programming |
78 | with libev. |
78 | with libev. |
79 | |
79 | |
80 | Familarity with event based programming techniques in general is assumed |
80 | Familiarity with event based programming techniques in general is assumed |
81 | throughout this document. |
81 | throughout this document. |
82 | |
82 | |
83 | =head1 ABOUT LIBEV |
83 | =head1 ABOUT LIBEV |
84 | |
84 | |
85 | Libev is an event loop: you register interest in certain events (such as a |
85 | Libev is an event loop: you register interest in certain events (such as a |
… | |
… | |
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 |
128 | the (fractional) number of seconds since the (POSIX) epoch (somewhere |
129 | the (fractional) number of seconds since the (POSIX) epoch (in practise |
129 | near the beginning of 1970, details are complicated, don't ask). This |
130 | somewhere near the beginning of 1970, details are complicated, don't |
130 | type is called C<ev_tstamp>, which is what you should use too. It usually |
131 | ask). This type is called C<ev_tstamp>, which is what you should use |
131 | aliases to the C<double> type in C. When you need to do any calculations |
132 | too. It usually aliases to the C<double> type in C. When you need to do |
132 | on it, you should treat it as some floating point value. Unlike the name |
133 | any calculations on it, you should treat it as some floating point value. |
|
|
134 | |
133 | component C<stamp> might indicate, it is also used for time differences |
135 | Unlike the name component C<stamp> might indicate, it is also used for |
134 | throughout libev. |
136 | time differences (e.g. delays) throughout libev. |
135 | |
137 | |
136 | =head1 ERROR HANDLING |
138 | =head1 ERROR HANDLING |
137 | |
139 | |
138 | Libev knows three classes of errors: operating system errors, usage errors |
140 | Libev knows three classes of errors: operating system errors, usage errors |
139 | and internal errors (bugs). |
141 | and internal errors (bugs). |
… | |
… | |
190 | as this indicates an incompatible change. Minor versions are usually |
192 | as this indicates an incompatible change. Minor versions are usually |
191 | compatible to older versions, so a larger minor version alone is usually |
193 | compatible to older versions, so a larger minor version alone is usually |
192 | not a problem. |
194 | not a problem. |
193 | |
195 | |
194 | Example: Make sure we haven't accidentally been linked against the wrong |
196 | Example: Make sure we haven't accidentally been linked against the wrong |
195 | version. |
197 | version (note, however, that this will not detect ABI mismatches :). |
196 | |
198 | |
197 | assert (("libev version mismatch", |
199 | assert (("libev version mismatch", |
198 | ev_version_major () == EV_VERSION_MAJOR |
200 | ev_version_major () == EV_VERSION_MAJOR |
199 | && ev_version_minor () >= EV_VERSION_MINOR)); |
201 | && ev_version_minor () >= EV_VERSION_MINOR)); |
200 | |
202 | |
… | |
… | |
344 | useful to try out specific backends to test their performance, or to work |
346 | useful to try out specific backends to test their performance, or to work |
345 | around bugs. |
347 | around bugs. |
346 | |
348 | |
347 | =item C<EVFLAG_FORKCHECK> |
349 | =item C<EVFLAG_FORKCHECK> |
348 | |
350 | |
349 | Instead of calling C<ev_default_fork> or C<ev_loop_fork> manually after |
351 | 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 |
352 | make libev check for a fork in each iteration by enabling this flag. |
351 | enabling this flag. |
|
|
352 | |
353 | |
353 | This works by calling C<getpid ()> on every iteration of the loop, |
354 | 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 |
355 | 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 |
356 | 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 |
357 | GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence |
… | |
… | |
362 | flag. |
363 | flag. |
363 | |
364 | |
364 | This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS> |
365 | This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS> |
365 | environment variable. |
366 | environment variable. |
366 | |
367 | |
|
|
368 | =item C<EVFLAG_NOINOTIFY> |
|
|
369 | |
|
|
370 | When this flag is specified, then libev will not attempt to use the |
|
|
371 | I<inotify> API for it's C<ev_stat> watchers. Apart from debugging and |
|
|
372 | testing, this flag can be useful to conserve inotify file descriptors, as |
|
|
373 | otherwise each loop using C<ev_stat> watchers consumes one inotify handle. |
|
|
374 | |
|
|
375 | =item C<EVFLAG_SIGNALFD> |
|
|
376 | |
|
|
377 | When this flag is specified, then libev will attempt to use the |
|
|
378 | I<signalfd> API for it's C<ev_signal> (and C<ev_child>) watchers. This API |
|
|
379 | delivers signals synchronously, which makes it both faster and might make |
|
|
380 | it possible to get the queued signal data. It can also simplify signal |
|
|
381 | handling with threads, as long as you properly block signals in your |
|
|
382 | threads that are not interested in handling them. |
|
|
383 | |
|
|
384 | Signalfd will not be used by default as this changes your signal mask, and |
|
|
385 | there are a lot of shoddy libraries and programs (glib's threadpool for |
|
|
386 | example) that can't properly initialise their signal masks. |
|
|
387 | |
367 | =item C<EVBACKEND_SELECT> (value 1, portable select backend) |
388 | =item C<EVBACKEND_SELECT> (value 1, portable select backend) |
368 | |
389 | |
369 | This is your standard select(2) backend. Not I<completely> standard, as |
390 | This is your standard select(2) backend. Not I<completely> standard, as |
370 | libev tries to roll its own fd_set with no limits on the number of fds, |
391 | libev tries to roll its own fd_set with no limits on the number of fds, |
371 | but if that fails, expect a fairly low limit on the number of fds when |
392 | but if that fails, expect a fairly low limit on the number of fds when |
… | |
… | |
394 | |
415 | |
395 | This backend maps C<EV_READ> to C<POLLIN | POLLERR | POLLHUP>, and |
416 | This backend maps C<EV_READ> to C<POLLIN | POLLERR | POLLHUP>, and |
396 | C<EV_WRITE> to C<POLLOUT | POLLERR | POLLHUP>. |
417 | C<EV_WRITE> to C<POLLOUT | POLLERR | POLLHUP>. |
397 | |
418 | |
398 | =item C<EVBACKEND_EPOLL> (value 4, Linux) |
419 | =item C<EVBACKEND_EPOLL> (value 4, Linux) |
|
|
420 | |
|
|
421 | Use the linux-specific epoll(7) interface (for both pre- and post-2.6.9 |
|
|
422 | kernels). |
399 | |
423 | |
400 | For few fds, this backend is a bit little slower than poll and select, |
424 | For few fds, this backend is a bit little slower than poll and select, |
401 | but it scales phenomenally better. While poll and select usually scale |
425 | but it scales phenomenally better. While poll and select usually scale |
402 | like O(total_fds) where n is the total number of fds (or the highest fd), |
426 | like O(total_fds) where n is the total number of fds (or the highest fd), |
403 | epoll scales either O(1) or O(active_fds). |
427 | epoll scales either O(1) or O(active_fds). |
… | |
… | |
518 | |
542 | |
519 | It is definitely not recommended to use this flag. |
543 | It is definitely not recommended to use this flag. |
520 | |
544 | |
521 | =back |
545 | =back |
522 | |
546 | |
523 | If one or more of these are or'ed into the flags value, then only these |
547 | If one or more of the backend flags are or'ed into the flags value, |
524 | backends will be tried (in the reverse order as listed here). If none are |
548 | then only these backends will be tried (in the reverse order as listed |
525 | specified, all backends in C<ev_recommended_backends ()> will be tried. |
549 | here). If none are specified, all backends in C<ev_recommended_backends |
|
|
550 | ()> will be tried. |
526 | |
551 | |
527 | Example: This is the most typical usage. |
552 | Example: This is the most typical usage. |
528 | |
553 | |
529 | if (!ev_default_loop (0)) |
554 | if (!ev_default_loop (0)) |
530 | fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?"); |
555 | fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?"); |
… | |
… | |
542 | ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE); |
567 | ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE); |
543 | |
568 | |
544 | =item struct ev_loop *ev_loop_new (unsigned int flags) |
569 | =item struct ev_loop *ev_loop_new (unsigned int flags) |
545 | |
570 | |
546 | Similar to C<ev_default_loop>, but always creates a new event loop that is |
571 | Similar to C<ev_default_loop>, but always creates a new event loop that is |
547 | always distinct from the default loop. Unlike the default loop, it cannot |
572 | always distinct from the default loop. |
548 | handle signal and child watchers, and attempts to do so will be greeted by |
|
|
549 | undefined behaviour (or a failed assertion if assertions are enabled). |
|
|
550 | |
573 | |
551 | Note that this function I<is> thread-safe, and the recommended way to use |
574 | Note that this function I<is> thread-safe, and one common way to use |
552 | libev with threads is indeed to create one loop per thread, and using the |
575 | libev with threads is indeed to create one loop per thread, and using the |
553 | default loop in the "main" or "initial" thread. |
576 | default loop in the "main" or "initial" thread. |
554 | |
577 | |
555 | Example: Try to create a event loop that uses epoll and nothing else. |
578 | Example: Try to create a event loop that uses epoll and nothing else. |
556 | |
579 | |
… | |
… | |
558 | if (!epoller) |
581 | if (!epoller) |
559 | fatal ("no epoll found here, maybe it hides under your chair"); |
582 | fatal ("no epoll found here, maybe it hides under your chair"); |
560 | |
583 | |
561 | =item ev_default_destroy () |
584 | =item ev_default_destroy () |
562 | |
585 | |
563 | Destroys the default loop again (frees all memory and kernel state |
586 | Destroys the default loop (frees all memory and kernel state etc.). None |
564 | etc.). None of the active event watchers will be stopped in the normal |
587 | of the active event watchers will be stopped in the normal sense, so |
565 | sense, so e.g. C<ev_is_active> might still return true. It is your |
588 | e.g. C<ev_is_active> might still return true. It is your responsibility to |
566 | responsibility to either stop all watchers cleanly yourself I<before> |
589 | either stop all watchers cleanly yourself I<before> calling this function, |
567 | calling this function, or cope with the fact afterwards (which is usually |
590 | or cope with the fact afterwards (which is usually the easiest thing, you |
568 | the easiest thing, you can just ignore the watchers and/or C<free ()> them |
591 | can just ignore the watchers and/or C<free ()> them for example). |
569 | for example). |
|
|
570 | |
592 | |
571 | Note that certain global state, such as signal state (and installed signal |
593 | Note that certain global state, such as signal state (and installed signal |
572 | handlers), will not be freed by this function, and related watchers (such |
594 | handlers), will not be freed by this function, and related watchers (such |
573 | as signal and child watchers) would need to be stopped manually. |
595 | as signal and child watchers) would need to be stopped manually. |
574 | |
596 | |
575 | In general it is not advisable to call this function except in the |
597 | In general it is not advisable to call this function except in the |
576 | rare occasion where you really need to free e.g. the signal handling |
598 | rare occasion where you really need to free e.g. the signal handling |
577 | pipe fds. If you need dynamically allocated loops it is better to use |
599 | pipe fds. If you need dynamically allocated loops it is better to use |
578 | C<ev_loop_new> and C<ev_loop_destroy>). |
600 | C<ev_loop_new> and C<ev_loop_destroy>. |
579 | |
601 | |
580 | =item ev_loop_destroy (loop) |
602 | =item ev_loop_destroy (loop) |
581 | |
603 | |
582 | Like C<ev_default_destroy>, but destroys an event loop created by an |
604 | Like C<ev_default_destroy>, but destroys an event loop created by an |
583 | earlier call to C<ev_loop_new>. |
605 | earlier call to C<ev_loop_new>. |
… | |
… | |
589 | name, you can call it anytime, but it makes most sense after forking, in |
611 | name, you can call it anytime, but it makes most sense after forking, in |
590 | the child process (or both child and parent, but that again makes little |
612 | the child process (or both child and parent, but that again makes little |
591 | sense). You I<must> call it in the child before using any of the libev |
613 | sense). You I<must> call it in the child before using any of the libev |
592 | functions, and it will only take effect at the next C<ev_loop> iteration. |
614 | functions, and it will only take effect at the next C<ev_loop> iteration. |
593 | |
615 | |
|
|
616 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
|
|
617 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
|
|
618 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
|
|
619 | during fork. |
|
|
620 | |
594 | On the other hand, you only need to call this function in the child |
621 | On the other hand, you only need to call this function in the child |
595 | process if and only if you want to use the event library in the child. If |
622 | process if and only if you want to use the event loop in the child. If you |
596 | you just fork+exec, you don't have to call it at all. |
623 | just fork+exec or create a new loop in the child, you don't have to call |
|
|
624 | it at all. |
597 | |
625 | |
598 | The function itself is quite fast and it's usually not a problem to call |
626 | The function itself is quite fast and it's usually not a problem to call |
599 | it just in case after a fork. To make this easy, the function will fit in |
627 | it just in case after a fork. To make this easy, the function will fit in |
600 | quite nicely into a call to C<pthread_atfork>: |
628 | quite nicely into a call to C<pthread_atfork>: |
601 | |
629 | |
… | |
… | |
603 | |
631 | |
604 | =item ev_loop_fork (loop) |
632 | =item ev_loop_fork (loop) |
605 | |
633 | |
606 | Like C<ev_default_fork>, but acts on an event loop created by |
634 | Like C<ev_default_fork>, but acts on an event loop created by |
607 | C<ev_loop_new>. Yes, you have to call this on every allocated event loop |
635 | C<ev_loop_new>. Yes, you have to call this on every allocated event loop |
608 | after fork that you want to re-use in the child, and how you do this is |
636 | after fork that you want to re-use in the child, and how you keep track of |
609 | entirely your own problem. |
637 | them is entirely your own problem. |
610 | |
638 | |
611 | =item int ev_is_default_loop (loop) |
639 | =item int ev_is_default_loop (loop) |
612 | |
640 | |
613 | Returns true when the given loop is, in fact, the default loop, and false |
641 | Returns true when the given loop is, in fact, the default loop, and false |
614 | otherwise. |
642 | otherwise. |
615 | |
643 | |
616 | =item unsigned int ev_loop_count (loop) |
644 | =item unsigned int ev_iteration (loop) |
617 | |
645 | |
618 | Returns the count of loop iterations for the loop, which is identical to |
646 | Returns the current iteration count for the loop, which is identical to |
619 | the number of times libev did poll for new events. It starts at C<0> and |
647 | the number of times libev did poll for new events. It starts at C<0> and |
620 | happily wraps around with enough iterations. |
648 | happily wraps around with enough iterations. |
621 | |
649 | |
622 | This value can sometimes be useful as a generation counter of sorts (it |
650 | This value can sometimes be useful as a generation counter of sorts (it |
623 | "ticks" the number of loop iterations), as it roughly corresponds with |
651 | "ticks" the number of loop iterations), as it roughly corresponds with |
624 | C<ev_prepare> and C<ev_check> calls. |
652 | C<ev_prepare> and C<ev_check> calls - and is incremented between the |
|
|
653 | prepare and check phases. |
|
|
654 | |
|
|
655 | =item unsigned int ev_depth (loop) |
|
|
656 | |
|
|
657 | Returns the number of times C<ev_loop> was entered minus the number of |
|
|
658 | times C<ev_loop> was exited, in other words, the recursion depth. |
|
|
659 | |
|
|
660 | Outside C<ev_loop>, this number is zero. In a callback, this number is |
|
|
661 | C<1>, unless C<ev_loop> was invoked recursively (or from another thread), |
|
|
662 | in which case it is higher. |
|
|
663 | |
|
|
664 | Leaving C<ev_loop> abnormally (setjmp/longjmp, cancelling the thread |
|
|
665 | etc.), doesn't count as "exit" - consider this as a hint to avoid such |
|
|
666 | ungentleman behaviour unless it's really convenient. |
625 | |
667 | |
626 | =item unsigned int ev_backend (loop) |
668 | =item unsigned int ev_backend (loop) |
627 | |
669 | |
628 | Returns one of the C<EVBACKEND_*> flags indicating the event backend in |
670 | Returns one of the C<EVBACKEND_*> flags indicating the event backend in |
629 | use. |
671 | use. |
… | |
… | |
663 | C<ev_resume> directly afterwards to resume timer processing. |
705 | C<ev_resume> directly afterwards to resume timer processing. |
664 | |
706 | |
665 | Effectively, all C<ev_timer> watchers will be delayed by the time spend |
707 | Effectively, all C<ev_timer> watchers will be delayed by the time spend |
666 | between C<ev_suspend> and C<ev_resume>, and all C<ev_periodic> watchers |
708 | between C<ev_suspend> and C<ev_resume>, and all C<ev_periodic> watchers |
667 | will be rescheduled (that is, they will lose any events that would have |
709 | will be rescheduled (that is, they will lose any events that would have |
668 | occured while suspended). |
710 | occurred while suspended). |
669 | |
711 | |
670 | After calling C<ev_suspend> you B<must not> call I<any> function on the |
712 | After calling C<ev_suspend> you B<must not> call I<any> function on the |
671 | given loop other than C<ev_resume>, and you B<must not> call C<ev_resume> |
713 | given loop other than C<ev_resume>, and you B<must not> call C<ev_resume> |
672 | without a previous call to C<ev_suspend>. |
714 | without a previous call to C<ev_suspend>. |
673 | |
715 | |
… | |
… | |
675 | event loop time (see C<ev_now_update>). |
717 | event loop time (see C<ev_now_update>). |
676 | |
718 | |
677 | =item ev_loop (loop, int flags) |
719 | =item ev_loop (loop, int flags) |
678 | |
720 | |
679 | Finally, this is it, the event handler. This function usually is called |
721 | Finally, this is it, the event handler. This function usually is called |
680 | after you initialised all your watchers and you want to start handling |
722 | after you have initialised all your watchers and you want to start |
681 | events. |
723 | handling events. |
682 | |
724 | |
683 | If the flags argument is specified as C<0>, it will not return until |
725 | If the flags argument is specified as C<0>, it will not return until |
684 | either no event watchers are active anymore or C<ev_unloop> was called. |
726 | either no event watchers are active anymore or C<ev_unloop> was called. |
685 | |
727 | |
686 | Please note that an explicit C<ev_unloop> is usually better than |
728 | Please note that an explicit C<ev_unloop> is usually better than |
… | |
… | |
750 | C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or |
792 | C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or |
751 | C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return. |
793 | C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return. |
752 | |
794 | |
753 | This "unloop state" will be cleared when entering C<ev_loop> again. |
795 | This "unloop state" will be cleared when entering C<ev_loop> again. |
754 | |
796 | |
755 | It is safe to call C<ev_unloop> from otuside any C<ev_loop> calls. |
797 | It is safe to call C<ev_unloop> from outside any C<ev_loop> calls. |
756 | |
798 | |
757 | =item ev_ref (loop) |
799 | =item ev_ref (loop) |
758 | |
800 | |
759 | =item ev_unref (loop) |
801 | =item ev_unref (loop) |
760 | |
802 | |
761 | Ref/unref can be used to add or remove a reference count on the event |
803 | Ref/unref can be used to add or remove a reference count on the event |
762 | loop: Every watcher keeps one reference, and as long as the reference |
804 | loop: Every watcher keeps one reference, and as long as the reference |
763 | count is nonzero, C<ev_loop> will not return on its own. |
805 | count is nonzero, C<ev_loop> will not return on its own. |
764 | |
806 | |
765 | If you have a watcher you never unregister that should not keep C<ev_loop> |
807 | This is useful when you have a watcher that you never intend to |
766 | from returning, call ev_unref() after starting, and ev_ref() before |
808 | unregister, but that nevertheless should not keep C<ev_loop> from |
|
|
809 | returning. In such a case, call C<ev_unref> after starting, and C<ev_ref> |
767 | stopping it. |
810 | before stopping it. |
768 | |
811 | |
769 | As an example, libev itself uses this for its internal signal pipe: It |
812 | As an example, libev itself uses this for its internal signal pipe: It |
770 | is not visible to the libev user and should not keep C<ev_loop> from |
813 | is not visible to the libev user and should not keep C<ev_loop> from |
771 | exiting if no event watchers registered by it are active. It is also an |
814 | exiting if no event watchers registered by it are active. It is also an |
772 | excellent way to do this for generic recurring timers or from within |
815 | excellent way to do this for generic recurring timers or from within |
… | |
… | |
811 | |
854 | |
812 | By setting a higher I<io collect interval> you allow libev to spend more |
855 | By setting a higher I<io collect interval> you allow libev to spend more |
813 | time collecting I/O events, so you can handle more events per iteration, |
856 | time collecting I/O events, so you can handle more events per iteration, |
814 | at the cost of increasing latency. Timeouts (both C<ev_periodic> and |
857 | at the cost of increasing latency. Timeouts (both C<ev_periodic> and |
815 | C<ev_timer>) will be not affected. Setting this to a non-null value will |
858 | C<ev_timer>) will be not affected. Setting this to a non-null value will |
816 | introduce an additional C<ev_sleep ()> call into most loop iterations. |
859 | introduce an additional C<ev_sleep ()> call into most loop iterations. The |
|
|
860 | sleep time ensures that libev will not poll for I/O events more often then |
|
|
861 | once per this interval, on average. |
817 | |
862 | |
818 | Likewise, by setting a higher I<timeout collect interval> you allow libev |
863 | Likewise, by setting a higher I<timeout collect interval> you allow libev |
819 | to spend more time collecting timeouts, at the expense of increased |
864 | to spend more time collecting timeouts, at the expense of increased |
820 | latency/jitter/inexactness (the watcher callback will be called |
865 | latency/jitter/inexactness (the watcher callback will be called |
821 | later). C<ev_io> watchers will not be affected. Setting this to a non-null |
866 | later). C<ev_io> watchers will not be affected. Setting this to a non-null |
… | |
… | |
823 | |
868 | |
824 | Many (busy) programs can usually benefit by setting the I/O collect |
869 | Many (busy) programs can usually benefit by setting the I/O collect |
825 | interval to a value near C<0.1> or so, which is often enough for |
870 | interval to a value near C<0.1> or so, which is often enough for |
826 | interactive servers (of course not for games), likewise for timeouts. It |
871 | interactive servers (of course not for games), likewise for timeouts. It |
827 | usually doesn't make much sense to set it to a lower value than C<0.01>, |
872 | usually doesn't make much sense to set it to a lower value than C<0.01>, |
828 | as this approaches the timing granularity of most systems. |
873 | as this approaches the timing granularity of most systems. Note that if |
|
|
874 | you do transactions with the outside world and you can't increase the |
|
|
875 | parallelity, then this setting will limit your transaction rate (if you |
|
|
876 | need to poll once per transaction and the I/O collect interval is 0.01, |
|
|
877 | then you can't do more than 100 transactions per second). |
829 | |
878 | |
830 | Setting the I<timeout collect interval> can improve the opportunity for |
879 | Setting the I<timeout collect interval> can improve the opportunity for |
831 | saving power, as the program will "bundle" timer callback invocations that |
880 | saving power, as the program will "bundle" timer callback invocations that |
832 | are "near" in time together, by delaying some, thus reducing the number of |
881 | are "near" in time together, by delaying some, thus reducing the number of |
833 | times the process sleeps and wakes up again. Another useful technique to |
882 | times the process sleeps and wakes up again. Another useful technique to |
834 | reduce iterations/wake-ups is to use C<ev_periodic> watchers and make sure |
883 | reduce iterations/wake-ups is to use C<ev_periodic> watchers and make sure |
835 | they fire on, say, one-second boundaries only. |
884 | they fire on, say, one-second boundaries only. |
836 | |
885 | |
|
|
886 | Example: we only need 0.1s timeout granularity, and we wish not to poll |
|
|
887 | more often than 100 times per second: |
|
|
888 | |
|
|
889 | ev_set_timeout_collect_interval (EV_DEFAULT_UC_ 0.1); |
|
|
890 | ev_set_io_collect_interval (EV_DEFAULT_UC_ 0.01); |
|
|
891 | |
|
|
892 | =item ev_invoke_pending (loop) |
|
|
893 | |
|
|
894 | This call will simply invoke all pending watchers while resetting their |
|
|
895 | pending state. Normally, C<ev_loop> does this automatically when required, |
|
|
896 | but when overriding the invoke callback this call comes handy. |
|
|
897 | |
|
|
898 | =item int ev_pending_count (loop) |
|
|
899 | |
|
|
900 | Returns the number of pending watchers - zero indicates that no watchers |
|
|
901 | are pending. |
|
|
902 | |
|
|
903 | =item ev_set_invoke_pending_cb (loop, void (*invoke_pending_cb)(EV_P)) |
|
|
904 | |
|
|
905 | This overrides the invoke pending functionality of the loop: Instead of |
|
|
906 | invoking all pending watchers when there are any, C<ev_loop> will call |
|
|
907 | this callback instead. This is useful, for example, when you want to |
|
|
908 | invoke the actual watchers inside another context (another thread etc.). |
|
|
909 | |
|
|
910 | If you want to reset the callback, use C<ev_invoke_pending> as new |
|
|
911 | callback. |
|
|
912 | |
|
|
913 | =item ev_set_loop_release_cb (loop, void (*release)(EV_P), void (*acquire)(EV_P)) |
|
|
914 | |
|
|
915 | Sometimes you want to share the same loop between multiple threads. This |
|
|
916 | can be done relatively simply by putting mutex_lock/unlock calls around |
|
|
917 | each call to a libev function. |
|
|
918 | |
|
|
919 | However, C<ev_loop> can run an indefinite time, so it is not feasible to |
|
|
920 | wait for it to return. One way around this is to wake up the loop via |
|
|
921 | C<ev_unloop> and C<av_async_send>, another way is to set these I<release> |
|
|
922 | and I<acquire> callbacks on the loop. |
|
|
923 | |
|
|
924 | When set, then C<release> will be called just before the thread is |
|
|
925 | suspended waiting for new events, and C<acquire> is called just |
|
|
926 | afterwards. |
|
|
927 | |
|
|
928 | Ideally, C<release> will just call your mutex_unlock function, and |
|
|
929 | C<acquire> will just call the mutex_lock function again. |
|
|
930 | |
|
|
931 | While event loop modifications are allowed between invocations of |
|
|
932 | C<release> and C<acquire> (that's their only purpose after all), no |
|
|
933 | modifications done will affect the event loop, i.e. adding watchers will |
|
|
934 | have no effect on the set of file descriptors being watched, or the time |
|
|
935 | waited. Use an C<ev_async> watcher to wake up C<ev_loop> when you want it |
|
|
936 | to take note of any changes you made. |
|
|
937 | |
|
|
938 | In theory, threads executing C<ev_loop> will be async-cancel safe between |
|
|
939 | invocations of C<release> and C<acquire>. |
|
|
940 | |
|
|
941 | See also the locking example in the C<THREADS> section later in this |
|
|
942 | document. |
|
|
943 | |
|
|
944 | =item ev_set_userdata (loop, void *data) |
|
|
945 | |
|
|
946 | =item ev_userdata (loop) |
|
|
947 | |
|
|
948 | Set and retrieve a single C<void *> associated with a loop. When |
|
|
949 | C<ev_set_userdata> has never been called, then C<ev_userdata> returns |
|
|
950 | C<0.> |
|
|
951 | |
|
|
952 | These two functions can be used to associate arbitrary data with a loop, |
|
|
953 | and are intended solely for the C<invoke_pending_cb>, C<release> and |
|
|
954 | C<acquire> callbacks described above, but of course can be (ab-)used for |
|
|
955 | any other purpose as well. |
|
|
956 | |
837 | =item ev_loop_verify (loop) |
957 | =item ev_loop_verify (loop) |
838 | |
958 | |
839 | This function only does something when C<EV_VERIFY> support has been |
959 | This function only does something when C<EV_VERIFY> support has been |
840 | compiled in, which is the default for non-minimal builds. It tries to go |
960 | compiled in, which is the default for non-minimal builds. It tries to go |
841 | through all internal structures and checks them for validity. If anything |
961 | through all internal structures and checks them for validity. If anything |
… | |
… | |
917 | =item C<EV_WRITE> |
1037 | =item C<EV_WRITE> |
918 | |
1038 | |
919 | The file descriptor in the C<ev_io> watcher has become readable and/or |
1039 | The file descriptor in the C<ev_io> watcher has become readable and/or |
920 | writable. |
1040 | writable. |
921 | |
1041 | |
922 | =item C<EV_TIMEOUT> |
1042 | =item C<EV_TIMER> |
923 | |
1043 | |
924 | The C<ev_timer> watcher has timed out. |
1044 | The C<ev_timer> watcher has timed out. |
925 | |
1045 | |
926 | =item C<EV_PERIODIC> |
1046 | =item C<EV_PERIODIC> |
927 | |
1047 | |
… | |
… | |
1017 | |
1137 | |
1018 | ev_io w; |
1138 | ev_io w; |
1019 | ev_init (&w, my_cb); |
1139 | ev_init (&w, my_cb); |
1020 | ev_io_set (&w, STDIN_FILENO, EV_READ); |
1140 | ev_io_set (&w, STDIN_FILENO, EV_READ); |
1021 | |
1141 | |
1022 | =item C<ev_TYPE_set> (ev_TYPE *, [args]) |
1142 | =item C<ev_TYPE_set> (ev_TYPE *watcher, [args]) |
1023 | |
1143 | |
1024 | This macro initialises the type-specific parts of a watcher. You need to |
1144 | This macro initialises the type-specific parts of a watcher. You need to |
1025 | call C<ev_init> at least once before you call this macro, but you can |
1145 | call C<ev_init> at least once before you call this macro, but you can |
1026 | call C<ev_TYPE_set> any number of times. You must not, however, call this |
1146 | call C<ev_TYPE_set> any number of times. You must not, however, call this |
1027 | macro on a watcher that is active (it can be pending, however, which is a |
1147 | macro on a watcher that is active (it can be pending, however, which is a |
… | |
… | |
1040 | |
1160 | |
1041 | Example: Initialise and set an C<ev_io> watcher in one step. |
1161 | Example: Initialise and set an C<ev_io> watcher in one step. |
1042 | |
1162 | |
1043 | ev_io_init (&w, my_cb, STDIN_FILENO, EV_READ); |
1163 | ev_io_init (&w, my_cb, STDIN_FILENO, EV_READ); |
1044 | |
1164 | |
1045 | =item C<ev_TYPE_start> (loop *, ev_TYPE *watcher) |
1165 | =item C<ev_TYPE_start> (loop, ev_TYPE *watcher) |
1046 | |
1166 | |
1047 | Starts (activates) the given watcher. Only active watchers will receive |
1167 | Starts (activates) the given watcher. Only active watchers will receive |
1048 | events. If the watcher is already active nothing will happen. |
1168 | events. If the watcher is already active nothing will happen. |
1049 | |
1169 | |
1050 | Example: Start the C<ev_io> watcher that is being abused as example in this |
1170 | Example: Start the C<ev_io> watcher that is being abused as example in this |
1051 | whole section. |
1171 | whole section. |
1052 | |
1172 | |
1053 | ev_io_start (EV_DEFAULT_UC, &w); |
1173 | ev_io_start (EV_DEFAULT_UC, &w); |
1054 | |
1174 | |
1055 | =item C<ev_TYPE_stop> (loop *, ev_TYPE *watcher) |
1175 | =item C<ev_TYPE_stop> (loop, ev_TYPE *watcher) |
1056 | |
1176 | |
1057 | Stops the given watcher if active, and clears the pending status (whether |
1177 | Stops the given watcher if active, and clears the pending status (whether |
1058 | the watcher was active or not). |
1178 | the watcher was active or not). |
1059 | |
1179 | |
1060 | It is possible that stopped watchers are pending - for example, |
1180 | It is possible that stopped watchers are pending - for example, |
… | |
… | |
1085 | =item ev_cb_set (ev_TYPE *watcher, callback) |
1205 | =item ev_cb_set (ev_TYPE *watcher, callback) |
1086 | |
1206 | |
1087 | Change the callback. You can change the callback at virtually any time |
1207 | Change the callback. You can change the callback at virtually any time |
1088 | (modulo threads). |
1208 | (modulo threads). |
1089 | |
1209 | |
1090 | =item ev_set_priority (ev_TYPE *watcher, priority) |
1210 | =item ev_set_priority (ev_TYPE *watcher, int priority) |
1091 | |
1211 | |
1092 | =item int ev_priority (ev_TYPE *watcher) |
1212 | =item int ev_priority (ev_TYPE *watcher) |
1093 | |
1213 | |
1094 | Set and query the priority of the watcher. The priority is a small |
1214 | Set and query the priority of the watcher. The priority is a small |
1095 | integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI> |
1215 | integer between C<EV_MAXPRI> (default: C<2>) and C<EV_MINPRI> |
… | |
… | |
1126 | returns its C<revents> bitset (as if its callback was invoked). If the |
1246 | returns its C<revents> bitset (as if its callback was invoked). If the |
1127 | watcher isn't pending it does nothing and returns C<0>. |
1247 | watcher isn't pending it does nothing and returns C<0>. |
1128 | |
1248 | |
1129 | Sometimes it can be useful to "poll" a watcher instead of waiting for its |
1249 | Sometimes it can be useful to "poll" a watcher instead of waiting for its |
1130 | callback to be invoked, which can be accomplished with this function. |
1250 | callback to be invoked, which can be accomplished with this function. |
|
|
1251 | |
|
|
1252 | =item ev_feed_event (loop, ev_TYPE *watcher, int revents) |
|
|
1253 | |
|
|
1254 | Feeds the given event set into the event loop, as if the specified event |
|
|
1255 | had happened for the specified watcher (which must be a pointer to an |
|
|
1256 | initialised but not necessarily started event watcher). Obviously you must |
|
|
1257 | not free the watcher as long as it has pending events. |
|
|
1258 | |
|
|
1259 | Stopping the watcher, letting libev invoke it, or calling |
|
|
1260 | C<ev_clear_pending> will clear the pending event, even if the watcher was |
|
|
1261 | not started in the first place. |
|
|
1262 | |
|
|
1263 | See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related |
|
|
1264 | functions that do not need a watcher. |
1131 | |
1265 | |
1132 | =back |
1266 | =back |
1133 | |
1267 | |
1134 | |
1268 | |
1135 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
1269 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
… | |
… | |
1184 | #include <stddef.h> |
1318 | #include <stddef.h> |
1185 | |
1319 | |
1186 | static void |
1320 | static void |
1187 | t1_cb (EV_P_ ev_timer *w, int revents) |
1321 | t1_cb (EV_P_ ev_timer *w, int revents) |
1188 | { |
1322 | { |
1189 | struct my_biggy big = (struct my_biggy * |
1323 | struct my_biggy big = (struct my_biggy *) |
1190 | (((char *)w) - offsetof (struct my_biggy, t1)); |
1324 | (((char *)w) - offsetof (struct my_biggy, t1)); |
1191 | } |
1325 | } |
1192 | |
1326 | |
1193 | static void |
1327 | static void |
1194 | t2_cb (EV_P_ ev_timer *w, int revents) |
1328 | t2_cb (EV_P_ ev_timer *w, int revents) |
1195 | { |
1329 | { |
1196 | struct my_biggy big = (struct my_biggy * |
1330 | struct my_biggy big = (struct my_biggy *) |
1197 | (((char *)w) - offsetof (struct my_biggy, t2)); |
1331 | (((char *)w) - offsetof (struct my_biggy, t2)); |
1198 | } |
1332 | } |
1199 | |
1333 | |
1200 | =head2 WATCHER PRIORITY MODELS |
1334 | =head2 WATCHER PRIORITY MODELS |
1201 | |
1335 | |
… | |
… | |
1246 | |
1380 | |
1247 | For example, to emulate how many other event libraries handle priorities, |
1381 | For example, to emulate how many other event libraries handle priorities, |
1248 | you can associate an C<ev_idle> watcher to each such watcher, and in |
1382 | you can associate an C<ev_idle> watcher to each such watcher, and in |
1249 | the normal watcher callback, you just start the idle watcher. The real |
1383 | the normal watcher callback, you just start the idle watcher. The real |
1250 | processing is done in the idle watcher callback. This causes libev to |
1384 | processing is done in the idle watcher callback. This causes libev to |
1251 | continously poll and process kernel event data for the watcher, but when |
1385 | continuously poll and process kernel event data for the watcher, but when |
1252 | the lock-out case is known to be rare (which in turn is rare :), this is |
1386 | the lock-out case is known to be rare (which in turn is rare :), this is |
1253 | workable. |
1387 | workable. |
1254 | |
1388 | |
1255 | Usually, however, the lock-out model implemented that way will perform |
1389 | Usually, however, the lock-out model implemented that way will perform |
1256 | miserably under the type of load it was designed to handle. In that case, |
1390 | miserably under the type of load it was designed to handle. In that case, |
… | |
… | |
1270 | { |
1404 | { |
1271 | // stop the I/O watcher, we received the event, but |
1405 | // stop the I/O watcher, we received the event, but |
1272 | // are not yet ready to handle it. |
1406 | // are not yet ready to handle it. |
1273 | ev_io_stop (EV_A_ w); |
1407 | ev_io_stop (EV_A_ w); |
1274 | |
1408 | |
1275 | // start the idle watcher to ahndle the actual event. |
1409 | // start the idle watcher to handle the actual event. |
1276 | // it will not be executed as long as other watchers |
1410 | // it will not be executed as long as other watchers |
1277 | // with the default priority are receiving events. |
1411 | // with the default priority are receiving events. |
1278 | ev_idle_start (EV_A_ &idle); |
1412 | ev_idle_start (EV_A_ &idle); |
1279 | } |
1413 | } |
1280 | |
1414 | |
1281 | static void |
1415 | static void |
1282 | idle-cb (EV_P_ ev_idle *w, int revents) |
1416 | idle_cb (EV_P_ ev_idle *w, int revents) |
1283 | { |
1417 | { |
1284 | // actual processing |
1418 | // actual processing |
1285 | read (STDIN_FILENO, ...); |
1419 | read (STDIN_FILENO, ...); |
1286 | |
1420 | |
1287 | // have to start the I/O watcher again, as |
1421 | // have to start the I/O watcher again, as |
… | |
… | |
1334 | |
1468 | |
1335 | If you cannot use non-blocking mode, then force the use of a |
1469 | If you cannot use non-blocking mode, then force the use of a |
1336 | known-to-be-good backend (at the time of this writing, this includes only |
1470 | known-to-be-good backend (at the time of this writing, this includes only |
1337 | C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>). The same applies to file |
1471 | C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>). The same applies to file |
1338 | descriptors for which non-blocking operation makes no sense (such as |
1472 | descriptors for which non-blocking operation makes no sense (such as |
1339 | files) - libev doesn't guarentee any specific behaviour in that case. |
1473 | files) - libev doesn't guarantee any specific behaviour in that case. |
1340 | |
1474 | |
1341 | Another thing you have to watch out for is that it is quite easy to |
1475 | Another thing you have to watch out for is that it is quite easy to |
1342 | receive "spurious" readiness notifications, that is your callback might |
1476 | receive "spurious" readiness notifications, that is your callback might |
1343 | be called with C<EV_READ> but a subsequent C<read>(2) will actually block |
1477 | be called with C<EV_READ> but a subsequent C<read>(2) will actually block |
1344 | because there is no data. Not only are some backends known to create a |
1478 | because there is no data. Not only are some backends known to create a |
… | |
… | |
1409 | |
1543 | |
1410 | So when you encounter spurious, unexplained daemon exits, make sure you |
1544 | So when you encounter spurious, unexplained daemon exits, make sure you |
1411 | ignore SIGPIPE (and maybe make sure you log the exit status of your daemon |
1545 | ignore SIGPIPE (and maybe make sure you log the exit status of your daemon |
1412 | somewhere, as that would have given you a big clue). |
1546 | somewhere, as that would have given you a big clue). |
1413 | |
1547 | |
|
|
1548 | =head3 The special problem of accept()ing when you can't |
|
|
1549 | |
|
|
1550 | Many implementations of the POSIX C<accept> function (for example, |
|
|
1551 | found in post-2004 Linux) have the peculiar behaviour of not removing a |
|
|
1552 | connection from the pending queue in all error cases. |
|
|
1553 | |
|
|
1554 | For example, larger servers often run out of file descriptors (because |
|
|
1555 | of resource limits), causing C<accept> to fail with C<ENFILE> but not |
|
|
1556 | rejecting the connection, leading to libev signalling readiness on |
|
|
1557 | the next iteration again (the connection still exists after all), and |
|
|
1558 | typically causing the program to loop at 100% CPU usage. |
|
|
1559 | |
|
|
1560 | Unfortunately, the set of errors that cause this issue differs between |
|
|
1561 | operating systems, there is usually little the app can do to remedy the |
|
|
1562 | situation, and no known thread-safe method of removing the connection to |
|
|
1563 | cope with overload is known (to me). |
|
|
1564 | |
|
|
1565 | One of the easiest ways to handle this situation is to just ignore it |
|
|
1566 | - when the program encounters an overload, it will just loop until the |
|
|
1567 | situation is over. While this is a form of busy waiting, no OS offers an |
|
|
1568 | event-based way to handle this situation, so it's the best one can do. |
|
|
1569 | |
|
|
1570 | A better way to handle the situation is to log any errors other than |
|
|
1571 | C<EAGAIN> and C<EWOULDBLOCK>, making sure not to flood the log with such |
|
|
1572 | messages, and continue as usual, which at least gives the user an idea of |
|
|
1573 | what could be wrong ("raise the ulimit!"). For extra points one could stop |
|
|
1574 | the C<ev_io> watcher on the listening fd "for a while", which reduces CPU |
|
|
1575 | usage. |
|
|
1576 | |
|
|
1577 | If your program is single-threaded, then you could also keep a dummy file |
|
|
1578 | descriptor for overload situations (e.g. by opening F</dev/null>), and |
|
|
1579 | when you run into C<ENFILE> or C<EMFILE>, close it, run C<accept>, |
|
|
1580 | close that fd, and create a new dummy fd. This will gracefully refuse |
|
|
1581 | clients under typical overload conditions. |
|
|
1582 | |
|
|
1583 | The last way to handle it is to simply log the error and C<exit>, as |
|
|
1584 | is often done with C<malloc> failures, but this results in an easy |
|
|
1585 | opportunity for a DoS attack. |
1414 | |
1586 | |
1415 | =head3 Watcher-Specific Functions |
1587 | =head3 Watcher-Specific Functions |
1416 | |
1588 | |
1417 | =over 4 |
1589 | =over 4 |
1418 | |
1590 | |
… | |
… | |
1465 | year, it will still time out after (roughly) one hour. "Roughly" because |
1637 | year, it will still time out after (roughly) one hour. "Roughly" because |
1466 | detecting time jumps is hard, and some inaccuracies are unavoidable (the |
1638 | detecting time jumps is hard, and some inaccuracies are unavoidable (the |
1467 | monotonic clock option helps a lot here). |
1639 | monotonic clock option helps a lot here). |
1468 | |
1640 | |
1469 | The callback is guaranteed to be invoked only I<after> its timeout has |
1641 | The callback is guaranteed to be invoked only I<after> its timeout has |
1470 | passed. If multiple timers become ready during the same loop iteration |
1642 | passed (not I<at>, so on systems with very low-resolution clocks this |
1471 | then the ones with earlier time-out values are invoked before ones with |
1643 | might introduce a small delay). If multiple timers become ready during the |
1472 | later time-out values (but this is no longer true when a callback calls |
1644 | same loop iteration then the ones with earlier time-out values are invoked |
1473 | C<ev_loop> recursively). |
1645 | before ones of the same priority with later time-out values (but this is |
|
|
1646 | no longer true when a callback calls C<ev_loop> recursively). |
1474 | |
1647 | |
1475 | =head3 Be smart about timeouts |
1648 | =head3 Be smart about timeouts |
1476 | |
1649 | |
1477 | Many real-world problems involve some kind of timeout, usually for error |
1650 | Many real-world problems involve some kind of timeout, usually for error |
1478 | recovery. A typical example is an HTTP request - if the other side hangs, |
1651 | recovery. A typical example is an HTTP request - if the other side hangs, |
… | |
… | |
1522 | C<after> argument to C<ev_timer_set>, and only ever use the C<repeat> |
1695 | C<after> argument to C<ev_timer_set>, and only ever use the C<repeat> |
1523 | member and C<ev_timer_again>. |
1696 | member and C<ev_timer_again>. |
1524 | |
1697 | |
1525 | At start: |
1698 | At start: |
1526 | |
1699 | |
1527 | ev_timer_init (timer, callback); |
1700 | ev_init (timer, callback); |
1528 | timer->repeat = 60.; |
1701 | timer->repeat = 60.; |
1529 | ev_timer_again (loop, timer); |
1702 | ev_timer_again (loop, timer); |
1530 | |
1703 | |
1531 | Each time there is some activity: |
1704 | Each time there is some activity: |
1532 | |
1705 | |
… | |
… | |
1564 | ev_tstamp timeout = last_activity + 60.; |
1737 | ev_tstamp timeout = last_activity + 60.; |
1565 | |
1738 | |
1566 | // if last_activity + 60. is older than now, we did time out |
1739 | // if last_activity + 60. is older than now, we did time out |
1567 | if (timeout < now) |
1740 | if (timeout < now) |
1568 | { |
1741 | { |
1569 | // timeout occured, take action |
1742 | // timeout occurred, take action |
1570 | } |
1743 | } |
1571 | else |
1744 | else |
1572 | { |
1745 | { |
1573 | // callback was invoked, but there was some activity, re-arm |
1746 | // callback was invoked, but there was some activity, re-arm |
1574 | // the watcher to fire in last_activity + 60, which is |
1747 | // the watcher to fire in last_activity + 60, which is |
… | |
… | |
1594 | |
1767 | |
1595 | To start the timer, simply initialise the watcher and set C<last_activity> |
1768 | To start the timer, simply initialise the watcher and set C<last_activity> |
1596 | to the current time (meaning we just have some activity :), then call the |
1769 | to the current time (meaning we just have some activity :), then call the |
1597 | callback, which will "do the right thing" and start the timer: |
1770 | callback, which will "do the right thing" and start the timer: |
1598 | |
1771 | |
1599 | ev_timer_init (timer, callback); |
1772 | ev_init (timer, callback); |
1600 | last_activity = ev_now (loop); |
1773 | last_activity = ev_now (loop); |
1601 | callback (loop, timer, EV_TIMEOUT); |
1774 | callback (loop, timer, EV_TIMER); |
1602 | |
1775 | |
1603 | And when there is some activity, simply store the current time in |
1776 | And when there is some activity, simply store the current time in |
1604 | C<last_activity>, no libev calls at all: |
1777 | C<last_activity>, no libev calls at all: |
1605 | |
1778 | |
1606 | last_actiivty = ev_now (loop); |
1779 | last_activity = ev_now (loop); |
1607 | |
1780 | |
1608 | This technique is slightly more complex, but in most cases where the |
1781 | This technique is slightly more complex, but in most cases where the |
1609 | time-out is unlikely to be triggered, much more efficient. |
1782 | time-out is unlikely to be triggered, much more efficient. |
1610 | |
1783 | |
1611 | Changing the timeout is trivial as well (if it isn't hard-coded in the |
1784 | Changing the timeout is trivial as well (if it isn't hard-coded in the |
… | |
… | |
1665 | |
1838 | |
1666 | If the event loop is suspended for a long time, you can also force an |
1839 | If the event loop is suspended for a long time, you can also force an |
1667 | update of the time returned by C<ev_now ()> by calling C<ev_now_update |
1840 | update of the time returned by C<ev_now ()> by calling C<ev_now_update |
1668 | ()>. |
1841 | ()>. |
1669 | |
1842 | |
|
|
1843 | =head3 The special problems of suspended animation |
|
|
1844 | |
|
|
1845 | When you leave the server world it is quite customary to hit machines that |
|
|
1846 | can suspend/hibernate - what happens to the clocks during such a suspend? |
|
|
1847 | |
|
|
1848 | Some quick tests made with a Linux 2.6.28 indicate that a suspend freezes |
|
|
1849 | all processes, while the clocks (C<times>, C<CLOCK_MONOTONIC>) continue |
|
|
1850 | to run until the system is suspended, but they will not advance while the |
|
|
1851 | system is suspended. That means, on resume, it will be as if the program |
|
|
1852 | was frozen for a few seconds, but the suspend time will not be counted |
|
|
1853 | towards C<ev_timer> when a monotonic clock source is used. The real time |
|
|
1854 | clock advanced as expected, but if it is used as sole clocksource, then a |
|
|
1855 | long suspend would be detected as a time jump by libev, and timers would |
|
|
1856 | be adjusted accordingly. |
|
|
1857 | |
|
|
1858 | I would not be surprised to see different behaviour in different between |
|
|
1859 | operating systems, OS versions or even different hardware. |
|
|
1860 | |
|
|
1861 | The other form of suspend (job control, or sending a SIGSTOP) will see a |
|
|
1862 | time jump in the monotonic clocks and the realtime clock. If the program |
|
|
1863 | is suspended for a very long time, and monotonic clock sources are in use, |
|
|
1864 | then you can expect C<ev_timer>s to expire as the full suspension time |
|
|
1865 | will be counted towards the timers. When no monotonic clock source is in |
|
|
1866 | use, then libev will again assume a timejump and adjust accordingly. |
|
|
1867 | |
|
|
1868 | It might be beneficial for this latter case to call C<ev_suspend> |
|
|
1869 | and C<ev_resume> in code that handles C<SIGTSTP>, to at least get |
|
|
1870 | deterministic behaviour in this case (you can do nothing against |
|
|
1871 | C<SIGSTOP>). |
|
|
1872 | |
1670 | =head3 Watcher-Specific Functions and Data Members |
1873 | =head3 Watcher-Specific Functions and Data Members |
1671 | |
1874 | |
1672 | =over 4 |
1875 | =over 4 |
1673 | |
1876 | |
1674 | =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat) |
1877 | =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat) |
… | |
… | |
1699 | If the timer is repeating, either start it if necessary (with the |
1902 | If the timer is repeating, either start it if necessary (with the |
1700 | C<repeat> value), or reset the running timer to the C<repeat> value. |
1903 | C<repeat> value), or reset the running timer to the C<repeat> value. |
1701 | |
1904 | |
1702 | This sounds a bit complicated, see L<Be smart about timeouts>, above, for a |
1905 | This sounds a bit complicated, see L<Be smart about timeouts>, above, for a |
1703 | usage example. |
1906 | usage example. |
|
|
1907 | |
|
|
1908 | =item ev_tstamp ev_timer_remaining (loop, ev_timer *) |
|
|
1909 | |
|
|
1910 | Returns the remaining time until a timer fires. If the timer is active, |
|
|
1911 | then this time is relative to the current event loop time, otherwise it's |
|
|
1912 | the timeout value currently configured. |
|
|
1913 | |
|
|
1914 | That is, after an C<ev_timer_set (w, 5, 7)>, C<ev_timer_remaining> returns |
|
|
1915 | C<5>. When the timer is started and one second passes, C<ev_timer_remaining> |
|
|
1916 | will return C<4>. When the timer expires and is restarted, it will return |
|
|
1917 | roughly C<7> (likely slightly less as callback invocation takes some time, |
|
|
1918 | too), and so on. |
1704 | |
1919 | |
1705 | =item ev_tstamp repeat [read-write] |
1920 | =item ev_tstamp repeat [read-write] |
1706 | |
1921 | |
1707 | The current C<repeat> value. Will be used each time the watcher times out |
1922 | The current C<repeat> value. Will be used each time the watcher times out |
1708 | or C<ev_timer_again> is called, and determines the next timeout (if any), |
1923 | or C<ev_timer_again> is called, and determines the next timeout (if any), |
… | |
… | |
1908 | Example: Call a callback every hour, or, more precisely, whenever the |
2123 | Example: Call a callback every hour, or, more precisely, whenever the |
1909 | system time is divisible by 3600. The callback invocation times have |
2124 | system time is divisible by 3600. The callback invocation times have |
1910 | potentially a lot of jitter, but good long-term stability. |
2125 | potentially a lot of jitter, but good long-term stability. |
1911 | |
2126 | |
1912 | static void |
2127 | static void |
1913 | clock_cb (struct ev_loop *loop, ev_io *w, int revents) |
2128 | clock_cb (struct ev_loop *loop, ev_periodic *w, int revents) |
1914 | { |
2129 | { |
1915 | ... its now a full hour (UTC, or TAI or whatever your clock follows) |
2130 | ... its now a full hour (UTC, or TAI or whatever your clock follows) |
1916 | } |
2131 | } |
1917 | |
2132 | |
1918 | ev_periodic hourly_tick; |
2133 | ev_periodic hourly_tick; |
… | |
… | |
1944 | Signal watchers will trigger an event when the process receives a specific |
2159 | Signal watchers will trigger an event when the process receives a specific |
1945 | signal one or more times. Even though signals are very asynchronous, libev |
2160 | signal one or more times. Even though signals are very asynchronous, libev |
1946 | will try it's best to deliver signals synchronously, i.e. as part of the |
2161 | will try it's best to deliver signals synchronously, i.e. as part of the |
1947 | normal event processing, like any other event. |
2162 | normal event processing, like any other event. |
1948 | |
2163 | |
1949 | If you want signals asynchronously, just use C<sigaction> as you would |
2164 | If you want signals to be delivered truly asynchronously, just use |
1950 | do without libev and forget about sharing the signal. You can even use |
2165 | C<sigaction> as you would do without libev and forget about sharing |
1951 | C<ev_async> from a signal handler to synchronously wake up an event loop. |
2166 | the signal. You can even use C<ev_async> from a signal handler to |
|
|
2167 | synchronously wake up an event loop. |
1952 | |
2168 | |
1953 | You can configure as many watchers as you like per signal. Only when the |
2169 | You can configure as many watchers as you like for the same signal, but |
|
|
2170 | only within the same loop, i.e. you can watch for C<SIGINT> in your |
|
|
2171 | default loop and for C<SIGIO> in another loop, but you cannot watch for |
|
|
2172 | C<SIGINT> in both the default loop and another loop at the same time. At |
|
|
2173 | the moment, C<SIGCHLD> is permanently tied to the default loop. |
|
|
2174 | |
1954 | first watcher gets started will libev actually register a signal handler |
2175 | When the first watcher gets started will libev actually register something |
1955 | with the kernel (thus it coexists with your own signal handlers as long as |
2176 | with the kernel (thus it coexists with your own signal handlers as long as |
1956 | you don't register any with libev for the same signal). Similarly, when |
2177 | you don't register any with libev for the same signal). |
1957 | the last signal watcher for a signal is stopped, libev will reset the |
|
|
1958 | signal handler to SIG_DFL (regardless of what it was set to before). |
|
|
1959 | |
2178 | |
1960 | If possible and supported, libev will install its handlers with |
2179 | If possible and supported, libev will install its handlers with |
1961 | C<SA_RESTART> behaviour enabled, so system calls should not be unduly |
2180 | C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should |
1962 | interrupted. If you have a problem with system calls getting interrupted by |
2181 | not be unduly interrupted. If you have a problem with system calls getting |
1963 | signals you can block all signals in an C<ev_check> watcher and unblock |
2182 | interrupted by signals you can block all signals in an C<ev_check> watcher |
1964 | them in an C<ev_prepare> watcher. |
2183 | and unblock them in an C<ev_prepare> watcher. |
|
|
2184 | |
|
|
2185 | =head3 The special problem of inheritance over fork/execve/pthread_create |
|
|
2186 | |
|
|
2187 | Both the signal mask (C<sigprocmask>) and the signal disposition |
|
|
2188 | (C<sigaction>) are unspecified after starting a signal watcher (and after |
|
|
2189 | stopping it again), that is, libev might or might not block the signal, |
|
|
2190 | and might or might not set or restore the installed signal handler. |
|
|
2191 | |
|
|
2192 | While this does not matter for the signal disposition (libev never |
|
|
2193 | sets signals to C<SIG_IGN>, so handlers will be reset to C<SIG_DFL> on |
|
|
2194 | C<execve>), this matters for the signal mask: many programs do not expect |
|
|
2195 | certain signals to be blocked. |
|
|
2196 | |
|
|
2197 | This means that before calling C<exec> (from the child) you should reset |
|
|
2198 | the signal mask to whatever "default" you expect (all clear is a good |
|
|
2199 | choice usually). |
|
|
2200 | |
|
|
2201 | The simplest way to ensure that the signal mask is reset in the child is |
|
|
2202 | to install a fork handler with C<pthread_atfork> that resets it. That will |
|
|
2203 | catch fork calls done by libraries (such as the libc) as well. |
|
|
2204 | |
|
|
2205 | In current versions of libev, the signal will not be blocked indefinitely |
|
|
2206 | unless you use the C<signalfd> API (C<EV_SIGNALFD>). While this reduces |
|
|
2207 | the window of opportunity for problems, it will not go away, as libev |
|
|
2208 | I<has> to modify the signal mask, at least temporarily. |
|
|
2209 | |
|
|
2210 | So I can't stress this enough: I<If you do not reset your signal mask when |
|
|
2211 | you expect it to be empty, you have a race condition in your code>. This |
|
|
2212 | is not a libev-specific thing, this is true for most event libraries. |
1965 | |
2213 | |
1966 | =head3 Watcher-Specific Functions and Data Members |
2214 | =head3 Watcher-Specific Functions and Data Members |
1967 | |
2215 | |
1968 | =over 4 |
2216 | =over 4 |
1969 | |
2217 | |
… | |
… | |
2001 | some child status changes (most typically when a child of yours dies or |
2249 | some child status changes (most typically when a child of yours dies or |
2002 | exits). It is permissible to install a child watcher I<after> the child |
2250 | exits). It is permissible to install a child watcher I<after> the child |
2003 | has been forked (which implies it might have already exited), as long |
2251 | has been forked (which implies it might have already exited), as long |
2004 | as the event loop isn't entered (or is continued from a watcher), i.e., |
2252 | as the event loop isn't entered (or is continued from a watcher), i.e., |
2005 | forking and then immediately registering a watcher for the child is fine, |
2253 | forking and then immediately registering a watcher for the child is fine, |
2006 | but forking and registering a watcher a few event loop iterations later is |
2254 | but forking and registering a watcher a few event loop iterations later or |
2007 | not. |
2255 | in the next callback invocation is not. |
2008 | |
2256 | |
2009 | Only the default event loop is capable of handling signals, and therefore |
2257 | Only the default event loop is capable of handling signals, and therefore |
2010 | you can only register child watchers in the default event loop. |
2258 | you can only register child watchers in the default event loop. |
2011 | |
2259 | |
|
|
2260 | Due to some design glitches inside libev, child watchers will always be |
|
|
2261 | handled at maximum priority (their priority is set to C<EV_MAXPRI> by |
|
|
2262 | libev) |
|
|
2263 | |
2012 | =head3 Process Interaction |
2264 | =head3 Process Interaction |
2013 | |
2265 | |
2014 | Libev grabs C<SIGCHLD> as soon as the default event loop is |
2266 | Libev grabs C<SIGCHLD> as soon as the default event loop is |
2015 | initialised. This is necessary to guarantee proper behaviour even if |
2267 | initialised. This is necessary to guarantee proper behaviour even if the |
2016 | the first child watcher is started after the child exits. The occurrence |
2268 | first child watcher is started after the child exits. The occurrence |
2017 | of C<SIGCHLD> is recorded asynchronously, but child reaping is done |
2269 | of C<SIGCHLD> is recorded asynchronously, but child reaping is done |
2018 | synchronously as part of the event loop processing. Libev always reaps all |
2270 | synchronously as part of the event loop processing. Libev always reaps all |
2019 | children, even ones not watched. |
2271 | children, even ones not watched. |
2020 | |
2272 | |
2021 | =head3 Overriding the Built-In Processing |
2273 | =head3 Overriding the Built-In Processing |
… | |
… | |
2031 | =head3 Stopping the Child Watcher |
2283 | =head3 Stopping the Child Watcher |
2032 | |
2284 | |
2033 | Currently, the child watcher never gets stopped, even when the |
2285 | Currently, the child watcher never gets stopped, even when the |
2034 | child terminates, so normally one needs to stop the watcher in the |
2286 | child terminates, so normally one needs to stop the watcher in the |
2035 | callback. Future versions of libev might stop the watcher automatically |
2287 | callback. Future versions of libev might stop the watcher automatically |
2036 | when a child exit is detected. |
2288 | when a child exit is detected (calling C<ev_child_stop> twice is not a |
|
|
2289 | problem). |
2037 | |
2290 | |
2038 | =head3 Watcher-Specific Functions and Data Members |
2291 | =head3 Watcher-Specific Functions and Data Members |
2039 | |
2292 | |
2040 | =over 4 |
2293 | =over 4 |
2041 | |
2294 | |
… | |
… | |
2367 | // no longer anything immediate to do. |
2620 | // no longer anything immediate to do. |
2368 | } |
2621 | } |
2369 | |
2622 | |
2370 | ev_idle *idle_watcher = malloc (sizeof (ev_idle)); |
2623 | ev_idle *idle_watcher = malloc (sizeof (ev_idle)); |
2371 | ev_idle_init (idle_watcher, idle_cb); |
2624 | ev_idle_init (idle_watcher, idle_cb); |
2372 | ev_idle_start (loop, idle_cb); |
2625 | ev_idle_start (loop, idle_watcher); |
2373 | |
2626 | |
2374 | |
2627 | |
2375 | =head2 C<ev_prepare> and C<ev_check> - customise your event loop! |
2628 | =head2 C<ev_prepare> and C<ev_check> - customise your event loop! |
2376 | |
2629 | |
2377 | Prepare and check watchers are usually (but not always) used in pairs: |
2630 | Prepare and check watchers are usually (but not always) used in pairs: |
… | |
… | |
2470 | struct pollfd fds [nfd]; |
2723 | struct pollfd fds [nfd]; |
2471 | // actual code will need to loop here and realloc etc. |
2724 | // actual code will need to loop here and realloc etc. |
2472 | adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ())); |
2725 | adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ())); |
2473 | |
2726 | |
2474 | /* the callback is illegal, but won't be called as we stop during check */ |
2727 | /* the callback is illegal, but won't be called as we stop during check */ |
2475 | ev_timer_init (&tw, 0, timeout * 1e-3); |
2728 | ev_timer_init (&tw, 0, timeout * 1e-3, 0.); |
2476 | ev_timer_start (loop, &tw); |
2729 | ev_timer_start (loop, &tw); |
2477 | |
2730 | |
2478 | // create one ev_io per pollfd |
2731 | // create one ev_io per pollfd |
2479 | for (int i = 0; i < nfd; ++i) |
2732 | for (int i = 0; i < nfd; ++i) |
2480 | { |
2733 | { |
… | |
… | |
2712 | C<ev_default_fork> cheats and calls it in the wrong process, the fork |
2965 | C<ev_default_fork> cheats and calls it in the wrong process, the fork |
2713 | handlers will be invoked, too, of course. |
2966 | handlers will be invoked, too, of course. |
2714 | |
2967 | |
2715 | =head3 The special problem of life after fork - how is it possible? |
2968 | =head3 The special problem of life after fork - how is it possible? |
2716 | |
2969 | |
2717 | Most uses of C<fork()> consist of forking, then some simple calls to ste |
2970 | Most uses of C<fork()> consist of forking, then some simple calls to set |
2718 | up/change the process environment, followed by a call to C<exec()>. This |
2971 | up/change the process environment, followed by a call to C<exec()>. This |
2719 | sequence should be handled by libev without any problems. |
2972 | sequence should be handled by libev without any problems. |
2720 | |
2973 | |
2721 | This changes when the application actually wants to do event handling |
2974 | This changes when the application actually wants to do event handling |
2722 | in the child, or both parent in child, in effect "continuing" after the |
2975 | in the child, or both parent in child, in effect "continuing" after the |
… | |
… | |
2756 | believe me. |
3009 | believe me. |
2757 | |
3010 | |
2758 | =back |
3011 | =back |
2759 | |
3012 | |
2760 | |
3013 | |
2761 | =head2 C<ev_async> - how to wake up another event loop |
3014 | =head2 C<ev_async> - how to wake up an event loop |
2762 | |
3015 | |
2763 | In general, you cannot use an C<ev_loop> from multiple threads or other |
3016 | In general, you cannot use an C<ev_loop> from multiple threads or other |
2764 | asynchronous sources such as signal handlers (as opposed to multiple event |
3017 | asynchronous sources such as signal handlers (as opposed to multiple event |
2765 | loops - those are of course safe to use in different threads). |
3018 | loops - those are of course safe to use in different threads). |
2766 | |
3019 | |
2767 | Sometimes, however, you need to wake up another event loop you do not |
3020 | Sometimes, however, you need to wake up an event loop you do not control, |
2768 | control, for example because it belongs to another thread. This is what |
3021 | for example because it belongs to another thread. This is what C<ev_async> |
2769 | C<ev_async> watchers do: as long as the C<ev_async> watcher is active, you |
3022 | watchers do: as long as the C<ev_async> watcher is active, you can signal |
2770 | can signal it by calling C<ev_async_send>, which is thread- and signal |
3023 | it by calling C<ev_async_send>, which is thread- and signal safe. |
2771 | safe. |
|
|
2772 | |
3024 | |
2773 | This functionality is very similar to C<ev_signal> watchers, as signals, |
3025 | This functionality is very similar to C<ev_signal> watchers, as signals, |
2774 | too, are asynchronous in nature, and signals, too, will be compressed |
3026 | too, are asynchronous in nature, and signals, too, will be compressed |
2775 | (i.e. the number of callback invocations may be less than the number of |
3027 | (i.e. the number of callback invocations may be less than the number of |
2776 | C<ev_async_sent> calls). |
3028 | C<ev_async_sent> calls). |
… | |
… | |
2781 | =head3 Queueing |
3033 | =head3 Queueing |
2782 | |
3034 | |
2783 | 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 |
2784 | 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 |
2785 | 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 |
2786 | need elaborate support such as pthreads. |
3038 | need elaborate support such as pthreads or unportable memory access |
|
|
3039 | semantics. |
2787 | |
3040 | |
2788 | 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 |
2789 | 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 |
2790 | queue: |
3043 | queue: |
2791 | |
3044 | |
… | |
… | |
2930 | |
3183 | |
2931 | 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 |
2932 | 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 |
2933 | repeat = 0) will be started. C<0> is a valid timeout. |
3186 | repeat = 0) will be started. C<0> is a valid timeout. |
2934 | |
3187 | |
2935 | 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 |
2936 | 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 |
2937 | 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> |
2938 | 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> |
2939 | 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 |
2940 | events precedence. |
3193 | events precedence. |
2941 | |
3194 | |
2942 | 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. |
2943 | |
3196 | |
2944 | static void stdin_ready (int revents, void *arg) |
3197 | static void stdin_ready (int revents, void *arg) |
2945 | { |
3198 | { |
2946 | if (revents & EV_READ) |
3199 | if (revents & EV_READ) |
2947 | /* stdin might have data for us, joy! */; |
3200 | /* stdin might have data for us, joy! */; |
2948 | else if (revents & EV_TIMEOUT) |
3201 | else if (revents & EV_TIMER) |
2949 | /* doh, nothing entered */; |
3202 | /* doh, nothing entered */; |
2950 | } |
3203 | } |
2951 | |
3204 | |
2952 | ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
3205 | ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
2953 | |
3206 | |
2954 | =item ev_feed_event (struct ev_loop *, watcher *, int revents) |
|
|
2955 | |
|
|
2956 | Feeds the given event set into the event loop, as if the specified event |
|
|
2957 | had happened for the specified watcher (which must be a pointer to an |
|
|
2958 | initialised but not necessarily started event watcher). |
|
|
2959 | |
|
|
2960 | =item ev_feed_fd_event (struct ev_loop *, int fd, int revents) |
3207 | =item ev_feed_fd_event (loop, int fd, int revents) |
2961 | |
3208 | |
2962 | 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 |
2963 | the given events it. |
3210 | the given events it. |
2964 | |
3211 | |
2965 | =item ev_feed_signal_event (struct ev_loop *loop, int signum) |
3212 | =item ev_feed_signal_event (loop, int signum) |
2966 | |
3213 | |
2967 | 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 |
2968 | loop!). |
3215 | loop!). |
2969 | |
3216 | |
2970 | =back |
3217 | =back |
… | |
… | |
3050 | |
3297 | |
3051 | =over 4 |
3298 | =over 4 |
3052 | |
3299 | |
3053 | =item ev::TYPE::TYPE () |
3300 | =item ev::TYPE::TYPE () |
3054 | |
3301 | |
3055 | =item ev::TYPE::TYPE (struct ev_loop *) |
3302 | =item ev::TYPE::TYPE (loop) |
3056 | |
3303 | |
3057 | =item ev::TYPE::~TYPE |
3304 | =item ev::TYPE::~TYPE |
3058 | |
3305 | |
3059 | The constructor (optionally) takes an event loop to associate the watcher |
3306 | The constructor (optionally) takes an event loop to associate the watcher |
3060 | with. If it is omitted, it will use C<EV_DEFAULT>. |
3307 | with. If it is omitted, it will use C<EV_DEFAULT>. |
… | |
… | |
3093 | myclass obj; |
3340 | myclass obj; |
3094 | ev::io iow; |
3341 | ev::io iow; |
3095 | iow.set <myclass, &myclass::io_cb> (&obj); |
3342 | iow.set <myclass, &myclass::io_cb> (&obj); |
3096 | |
3343 | |
3097 | =item w->set (object *) |
3344 | =item w->set (object *) |
3098 | |
|
|
3099 | This is an B<experimental> feature that might go away in a future version. |
|
|
3100 | |
3345 | |
3101 | This is a variation of a method callback - leaving out the method to call |
3346 | This is a variation of a method callback - leaving out the method to call |
3102 | will default the method to C<operator ()>, which makes it possible to use |
3347 | will default the method to C<operator ()>, which makes it possible to use |
3103 | functor objects without having to manually specify the C<operator ()> all |
3348 | functor objects without having to manually specify the C<operator ()> all |
3104 | the time. Incidentally, you can then also leave out the template argument |
3349 | the time. Incidentally, you can then also leave out the template argument |
… | |
… | |
3137 | Example: Use a plain function as callback. |
3382 | Example: Use a plain function as callback. |
3138 | |
3383 | |
3139 | static void io_cb (ev::io &w, int revents) { } |
3384 | static void io_cb (ev::io &w, int revents) { } |
3140 | iow.set <io_cb> (); |
3385 | iow.set <io_cb> (); |
3141 | |
3386 | |
3142 | =item w->set (struct ev_loop *) |
3387 | =item w->set (loop) |
3143 | |
3388 | |
3144 | Associates a different C<struct ev_loop> with this watcher. You can only |
3389 | Associates a different C<struct ev_loop> with this watcher. You can only |
3145 | do this when the watcher is inactive (and not pending either). |
3390 | do this when the watcher is inactive (and not pending either). |
3146 | |
3391 | |
3147 | =item w->set ([arguments]) |
3392 | =item w->set ([arguments]) |
… | |
… | |
3244 | =item Ocaml |
3489 | =item Ocaml |
3245 | |
3490 | |
3246 | Erkki Seppala has written Ocaml bindings for libev, to be found at |
3491 | Erkki Seppala has written Ocaml bindings for libev, to be found at |
3247 | L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>. |
3492 | L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>. |
3248 | |
3493 | |
|
|
3494 | =item Lua |
|
|
3495 | |
|
|
3496 | Brian Maher has written a partial interface to libev for lua (at the |
|
|
3497 | time of this writing, only C<ev_io> and C<ev_timer>), to be found at |
|
|
3498 | L<http://github.com/brimworks/lua-ev>. |
|
|
3499 | |
3249 | =back |
3500 | =back |
3250 | |
3501 | |
3251 | |
3502 | |
3252 | =head1 MACRO MAGIC |
3503 | =head1 MACRO MAGIC |
3253 | |
3504 | |
… | |
… | |
3406 | libev.m4 |
3657 | libev.m4 |
3407 | |
3658 | |
3408 | =head2 PREPROCESSOR SYMBOLS/MACROS |
3659 | =head2 PREPROCESSOR SYMBOLS/MACROS |
3409 | |
3660 | |
3410 | Libev can be configured via a variety of preprocessor symbols you have to |
3661 | Libev can be configured via a variety of preprocessor symbols you have to |
3411 | define before including any of its files. The default in the absence of |
3662 | define before including (or compiling) any of its files. The default in |
3412 | autoconf is documented for every option. |
3663 | the absence of autoconf is documented for every option. |
|
|
3664 | |
|
|
3665 | Symbols marked with "(h)" do not change the ABI, and can have different |
|
|
3666 | values when compiling libev vs. including F<ev.h>, so it is permissible |
|
|
3667 | to redefine them before including F<ev.h> without breaking compatibility |
|
|
3668 | to a compiled library. All other symbols change the ABI, which means all |
|
|
3669 | users of libev and the libev code itself must be compiled with compatible |
|
|
3670 | settings. |
3413 | |
3671 | |
3414 | =over 4 |
3672 | =over 4 |
3415 | |
3673 | |
3416 | =item EV_STANDALONE |
3674 | =item EV_STANDALONE (h) |
3417 | |
3675 | |
3418 | Must always be C<1> if you do not use autoconf configuration, which |
3676 | Must always be C<1> if you do not use autoconf configuration, which |
3419 | keeps libev from including F<config.h>, and it also defines dummy |
3677 | keeps libev from including F<config.h>, and it also defines dummy |
3420 | implementations for some libevent functions (such as logging, which is not |
3678 | implementations for some libevent functions (such as logging, which is not |
3421 | supported). It will also not define any of the structs usually found in |
3679 | supported). It will also not define any of the structs usually found in |
3422 | F<event.h> that are not directly supported by the libev core alone. |
3680 | F<event.h> that are not directly supported by the libev core alone. |
3423 | |
3681 | |
3424 | In stanbdalone mode, libev will still try to automatically deduce the |
3682 | In standalone mode, libev will still try to automatically deduce the |
3425 | configuration, but has to be more conservative. |
3683 | configuration, but has to be more conservative. |
3426 | |
3684 | |
3427 | =item EV_USE_MONOTONIC |
3685 | =item EV_USE_MONOTONIC |
3428 | |
3686 | |
3429 | If defined to be C<1>, libev will try to detect the availability of the |
3687 | If defined to be C<1>, libev will try to detect the availability of the |
… | |
… | |
3494 | be used is the winsock select). This means that it will call |
3752 | be used is the winsock select). This means that it will call |
3495 | C<_get_osfhandle> on the fd to convert it to an OS handle. Otherwise, |
3753 | C<_get_osfhandle> on the fd to convert it to an OS handle. Otherwise, |
3496 | it is assumed that all these functions actually work on fds, even |
3754 | it is assumed that all these functions actually work on fds, even |
3497 | on win32. Should not be defined on non-win32 platforms. |
3755 | on win32. Should not be defined on non-win32 platforms. |
3498 | |
3756 | |
3499 | =item EV_FD_TO_WIN32_HANDLE |
3757 | =item EV_FD_TO_WIN32_HANDLE(fd) |
3500 | |
3758 | |
3501 | If C<EV_SELECT_IS_WINSOCKET> is enabled, then libev needs a way to map |
3759 | If C<EV_SELECT_IS_WINSOCKET> is enabled, then libev needs a way to map |
3502 | file descriptors to socket handles. When not defining this symbol (the |
3760 | file descriptors to socket handles. When not defining this symbol (the |
3503 | default), then libev will call C<_get_osfhandle>, which is usually |
3761 | default), then libev will call C<_get_osfhandle>, which is usually |
3504 | correct. In some cases, programs use their own file descriptor management, |
3762 | correct. In some cases, programs use their own file descriptor management, |
3505 | in which case they can provide this function to map fds to socket handles. |
3763 | in which case they can provide this function to map fds to socket handles. |
|
|
3764 | |
|
|
3765 | =item EV_WIN32_HANDLE_TO_FD(handle) |
|
|
3766 | |
|
|
3767 | If C<EV_SELECT_IS_WINSOCKET> then libev maps handles to file descriptors |
|
|
3768 | using the standard C<_open_osfhandle> function. For programs implementing |
|
|
3769 | their own fd to handle mapping, overwriting this function makes it easier |
|
|
3770 | to do so. This can be done by defining this macro to an appropriate value. |
|
|
3771 | |
|
|
3772 | =item EV_WIN32_CLOSE_FD(fd) |
|
|
3773 | |
|
|
3774 | If programs implement their own fd to handle mapping on win32, then this |
|
|
3775 | macro can be used to override the C<close> function, useful to unregister |
|
|
3776 | file descriptors again. Note that the replacement function has to close |
|
|
3777 | the underlying OS handle. |
3506 | |
3778 | |
3507 | =item EV_USE_POLL |
3779 | =item EV_USE_POLL |
3508 | |
3780 | |
3509 | If defined to be C<1>, libev will compile in support for the C<poll>(2) |
3781 | If defined to be C<1>, libev will compile in support for the C<poll>(2) |
3510 | backend. Otherwise it will be enabled on non-win32 platforms. It |
3782 | backend. Otherwise it will be enabled on non-win32 platforms. It |
… | |
… | |
3557 | as well as for signal and thread safety in C<ev_async> watchers. |
3829 | as well as for signal and thread safety in C<ev_async> watchers. |
3558 | |
3830 | |
3559 | In the absence of this define, libev will use C<sig_atomic_t volatile> |
3831 | In the absence of this define, libev will use C<sig_atomic_t volatile> |
3560 | (from F<signal.h>), which is usually good enough on most platforms. |
3832 | (from F<signal.h>), which is usually good enough on most platforms. |
3561 | |
3833 | |
3562 | =item EV_H |
3834 | =item EV_H (h) |
3563 | |
3835 | |
3564 | The name of the F<ev.h> header file used to include it. The default if |
3836 | The name of the F<ev.h> header file used to include it. The default if |
3565 | undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be |
3837 | undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be |
3566 | used to virtually rename the F<ev.h> header file in case of conflicts. |
3838 | used to virtually rename the F<ev.h> header file in case of conflicts. |
3567 | |
3839 | |
3568 | =item EV_CONFIG_H |
3840 | =item EV_CONFIG_H (h) |
3569 | |
3841 | |
3570 | If C<EV_STANDALONE> isn't C<1>, this variable can be used to override |
3842 | If C<EV_STANDALONE> isn't C<1>, this variable can be used to override |
3571 | F<ev.c>'s idea of where to find the F<config.h> file, similarly to |
3843 | F<ev.c>'s idea of where to find the F<config.h> file, similarly to |
3572 | C<EV_H>, above. |
3844 | C<EV_H>, above. |
3573 | |
3845 | |
3574 | =item EV_EVENT_H |
3846 | =item EV_EVENT_H (h) |
3575 | |
3847 | |
3576 | Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea |
3848 | Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea |
3577 | of how the F<event.h> header can be found, the default is C<"event.h">. |
3849 | of how the F<event.h> header can be found, the default is C<"event.h">. |
3578 | |
3850 | |
3579 | =item EV_PROTOTYPES |
3851 | =item EV_PROTOTYPES (h) |
3580 | |
3852 | |
3581 | If defined to be C<0>, then F<ev.h> will not define any function |
3853 | If defined to be C<0>, then F<ev.h> will not define any function |
3582 | prototypes, but still define all the structs and other symbols. This is |
3854 | prototypes, but still define all the structs and other symbols. This is |
3583 | occasionally useful if you want to provide your own wrapper functions |
3855 | occasionally useful if you want to provide your own wrapper functions |
3584 | around libev functions. |
3856 | around libev functions. |
… | |
… | |
3606 | fine. |
3878 | fine. |
3607 | |
3879 | |
3608 | If your embedding application does not need any priorities, defining these |
3880 | If your embedding application does not need any priorities, defining these |
3609 | both to C<0> will save some memory and CPU. |
3881 | both to C<0> will save some memory and CPU. |
3610 | |
3882 | |
3611 | =item EV_PERIODIC_ENABLE |
3883 | =item EV_PERIODIC_ENABLE, EV_IDLE_ENABLE, EV_EMBED_ENABLE, EV_STAT_ENABLE, |
|
|
3884 | EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE, |
|
|
3885 | EV_ASYNC_ENABLE, EV_CHILD_ENABLE. |
3612 | |
3886 | |
3613 | If undefined or defined to be C<1>, then periodic timers are supported. If |
3887 | If undefined or defined to be C<1> (and the platform supports it), then |
3614 | defined to be C<0>, then they are not. Disabling them saves a few kB of |
3888 | the respective watcher type is supported. If defined to be C<0>, then it |
3615 | code. |
3889 | is not. Disabling watcher types mainly saves code size. |
3616 | |
3890 | |
3617 | =item EV_IDLE_ENABLE |
3891 | =item EV_FEATURES |
3618 | |
|
|
3619 | If undefined or defined to be C<1>, then idle watchers are supported. If |
|
|
3620 | defined to be C<0>, then they are not. Disabling them saves a few kB of |
|
|
3621 | code. |
|
|
3622 | |
|
|
3623 | =item EV_EMBED_ENABLE |
|
|
3624 | |
|
|
3625 | If undefined or defined to be C<1>, then embed watchers are supported. If |
|
|
3626 | defined to be C<0>, then they are not. Embed watchers rely on most other |
|
|
3627 | watcher types, which therefore must not be disabled. |
|
|
3628 | |
|
|
3629 | =item EV_STAT_ENABLE |
|
|
3630 | |
|
|
3631 | If undefined or defined to be C<1>, then stat watchers are supported. If |
|
|
3632 | defined to be C<0>, then they are not. |
|
|
3633 | |
|
|
3634 | =item EV_FORK_ENABLE |
|
|
3635 | |
|
|
3636 | If undefined or defined to be C<1>, then fork watchers are supported. If |
|
|
3637 | defined to be C<0>, then they are not. |
|
|
3638 | |
|
|
3639 | =item EV_ASYNC_ENABLE |
|
|
3640 | |
|
|
3641 | If undefined or defined to be C<1>, then async watchers are supported. If |
|
|
3642 | defined to be C<0>, then they are not. |
|
|
3643 | |
|
|
3644 | =item EV_MINIMAL |
|
|
3645 | |
3892 | |
3646 | If you need to shave off some kilobytes of code at the expense of some |
3893 | If you need to shave off some kilobytes of code at the expense of some |
3647 | speed, define this symbol to C<1>. Currently this is used to override some |
3894 | speed (but with the full API), you can define this symbol to request |
3648 | inlining decisions, saves roughly 30% code size on amd64. It also selects a |
3895 | certain subsets of functionality. The default is to enable all features |
3649 | much smaller 2-heap for timer management over the default 4-heap. |
3896 | that can be enabled on the platform. |
|
|
3897 | |
|
|
3898 | A typical way to use this symbol is to define it to C<0> (or to a bitset |
|
|
3899 | with some broad features you want) and then selectively re-enable |
|
|
3900 | additional parts you want, for example if you want everything minimal, |
|
|
3901 | but multiple event loop support, async and child watchers and the poll |
|
|
3902 | backend, use this: |
|
|
3903 | |
|
|
3904 | #define EV_FEATURES 0 |
|
|
3905 | #define EV_MULTIPLICITY 1 |
|
|
3906 | #define EV_USE_POLL 1 |
|
|
3907 | #define EV_CHILD_ENABLE 1 |
|
|
3908 | #define EV_ASYNC_ENABLE 1 |
|
|
3909 | |
|
|
3910 | The actual value is a bitset, it can be a combination of the following |
|
|
3911 | values: |
|
|
3912 | |
|
|
3913 | =over 4 |
|
|
3914 | |
|
|
3915 | =item C<1> - faster/larger code |
|
|
3916 | |
|
|
3917 | Use larger code to speed up some operations. |
|
|
3918 | |
|
|
3919 | Currently this is used to override some inlining decisions (enlarging the |
|
|
3920 | code size by roughly 30% on amd64). |
|
|
3921 | |
|
|
3922 | When optimising for size, use of compiler flags such as C<-Os> with |
|
|
3923 | gcc is recommended, as well as C<-DNDEBUG>, as libev contains a number of |
|
|
3924 | assertions. |
|
|
3925 | |
|
|
3926 | =item C<2> - faster/larger data structures |
|
|
3927 | |
|
|
3928 | Replaces the small 2-heap for timer management by a faster 4-heap, larger |
|
|
3929 | hash table sizes and so on. This will usually further increase code size |
|
|
3930 | and can additionally have an effect on the size of data structures at |
|
|
3931 | runtime. |
|
|
3932 | |
|
|
3933 | =item C<4> - full API configuration |
|
|
3934 | |
|
|
3935 | This enables priorities (sets C<EV_MAXPRI>=2 and C<EV_MINPRI>=-2), and |
|
|
3936 | enables multiplicity (C<EV_MULTIPLICITY>=1). |
|
|
3937 | |
|
|
3938 | =item C<8> - full API |
|
|
3939 | |
|
|
3940 | This enables a lot of the "lesser used" API functions. See C<ev.h> for |
|
|
3941 | details on which parts of the API are still available without this |
|
|
3942 | feature, and do not complain if this subset changes over time. |
|
|
3943 | |
|
|
3944 | =item C<16> - enable all optional watcher types |
|
|
3945 | |
|
|
3946 | Enables all optional watcher types. If you want to selectively enable |
|
|
3947 | only some watcher types other than I/O and timers (e.g. prepare, |
|
|
3948 | embed, async, child...) you can enable them manually by defining |
|
|
3949 | C<EV_watchertype_ENABLE> to C<1> instead. |
|
|
3950 | |
|
|
3951 | =item C<32> - enable all backends |
|
|
3952 | |
|
|
3953 | This enables all backends - without this feature, you need to enable at |
|
|
3954 | least one backend manually (C<EV_USE_SELECT> is a good choice). |
|
|
3955 | |
|
|
3956 | =item C<64> - enable OS-specific "helper" APIs |
|
|
3957 | |
|
|
3958 | Enable inotify, eventfd, signalfd and similar OS-specific helper APIs by |
|
|
3959 | default. |
|
|
3960 | |
|
|
3961 | =back |
|
|
3962 | |
|
|
3963 | Compiling with C<gcc -Os -DEV_STANDALONE -DEV_USE_EPOLL=1 -DEV_FEATURES=0> |
|
|
3964 | reduces the compiled size of libev from 24.7Kb code/2.8Kb data to 6.5Kb |
|
|
3965 | code/0.3Kb data on my GNU/Linux amd64 system, while still giving you I/O |
|
|
3966 | watchers, timers and monotonic clock support. |
|
|
3967 | |
|
|
3968 | With an intelligent-enough linker (gcc+binutils are intelligent enough |
|
|
3969 | when you use C<-Wl,--gc-sections -ffunction-sections>) functions unused by |
|
|
3970 | your program might be left out as well - a binary starting a timer and an |
|
|
3971 | I/O watcher then might come out at only 5Kb. |
|
|
3972 | |
|
|
3973 | =item EV_AVOID_STDIO |
|
|
3974 | |
|
|
3975 | If this is set to C<1> at compiletime, then libev will avoid using stdio |
|
|
3976 | functions (printf, scanf, perror etc.). This will increase the code size |
|
|
3977 | somewhat, but if your program doesn't otherwise depend on stdio and your |
|
|
3978 | libc allows it, this avoids linking in the stdio library which is quite |
|
|
3979 | big. |
|
|
3980 | |
|
|
3981 | Note that error messages might become less precise when this option is |
|
|
3982 | enabled. |
|
|
3983 | |
|
|
3984 | =item EV_NSIG |
|
|
3985 | |
|
|
3986 | The highest supported signal number, +1 (or, the number of |
|
|
3987 | signals): Normally, libev tries to deduce the maximum number of signals |
|
|
3988 | automatically, but sometimes this fails, in which case it can be |
|
|
3989 | specified. Also, using a lower number than detected (C<32> should be |
|
|
3990 | good for about any system in existence) can save some memory, as libev |
|
|
3991 | statically allocates some 12-24 bytes per signal number. |
3650 | |
3992 | |
3651 | =item EV_PID_HASHSIZE |
3993 | =item EV_PID_HASHSIZE |
3652 | |
3994 | |
3653 | C<ev_child> watchers use a small hash table to distribute workload by |
3995 | C<ev_child> watchers use a small hash table to distribute workload by |
3654 | pid. The default size is C<16> (or C<1> with C<EV_MINIMAL>), usually more |
3996 | pid. The default size is C<16> (or C<1> with C<EV_FEATURES> disabled), |
3655 | than enough. If you need to manage thousands of children you might want to |
3997 | usually more than enough. If you need to manage thousands of children you |
3656 | increase this value (I<must> be a power of two). |
3998 | might want to increase this value (I<must> be a power of two). |
3657 | |
3999 | |
3658 | =item EV_INOTIFY_HASHSIZE |
4000 | =item EV_INOTIFY_HASHSIZE |
3659 | |
4001 | |
3660 | C<ev_stat> watchers use a small hash table to distribute workload by |
4002 | C<ev_stat> watchers use a small hash table to distribute workload by |
3661 | inotify watch id. The default size is C<16> (or C<1> with C<EV_MINIMAL>), |
4003 | inotify watch id. The default size is C<16> (or C<1> with C<EV_FEATURES> |
3662 | usually more than enough. If you need to manage thousands of C<ev_stat> |
4004 | disabled), usually more than enough. If you need to manage thousands of |
3663 | watchers you might want to increase this value (I<must> be a power of |
4005 | C<ev_stat> watchers you might want to increase this value (I<must> be a |
3664 | two). |
4006 | power of two). |
3665 | |
4007 | |
3666 | =item EV_USE_4HEAP |
4008 | =item EV_USE_4HEAP |
3667 | |
4009 | |
3668 | Heaps are not very cache-efficient. To improve the cache-efficiency of the |
4010 | Heaps are not very cache-efficient. To improve the cache-efficiency of the |
3669 | timer and periodics heaps, libev uses a 4-heap when this symbol is defined |
4011 | timer and periodics heaps, libev uses a 4-heap when this symbol is defined |
3670 | to C<1>. The 4-heap uses more complicated (longer) code but has noticeably |
4012 | to C<1>. The 4-heap uses more complicated (longer) code but has noticeably |
3671 | faster performance with many (thousands) of watchers. |
4013 | faster performance with many (thousands) of watchers. |
3672 | |
4014 | |
3673 | The default is C<1> unless C<EV_MINIMAL> is set in which case it is C<0> |
4015 | The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it |
3674 | (disabled). |
4016 | will be C<0>. |
3675 | |
4017 | |
3676 | =item EV_HEAP_CACHE_AT |
4018 | =item EV_HEAP_CACHE_AT |
3677 | |
4019 | |
3678 | Heaps are not very cache-efficient. To improve the cache-efficiency of the |
4020 | Heaps are not very cache-efficient. To improve the cache-efficiency of the |
3679 | timer and periodics heaps, libev can cache the timestamp (I<at>) within |
4021 | timer and periodics heaps, libev can cache the timestamp (I<at>) within |
3680 | the heap structure (selected by defining C<EV_HEAP_CACHE_AT> to C<1>), |
4022 | the heap structure (selected by defining C<EV_HEAP_CACHE_AT> to C<1>), |
3681 | which uses 8-12 bytes more per watcher and a few hundred bytes more code, |
4023 | which uses 8-12 bytes more per watcher and a few hundred bytes more code, |
3682 | but avoids random read accesses on heap changes. This improves performance |
4024 | but avoids random read accesses on heap changes. This improves performance |
3683 | noticeably with many (hundreds) of watchers. |
4025 | noticeably with many (hundreds) of watchers. |
3684 | |
4026 | |
3685 | The default is C<1> unless C<EV_MINIMAL> is set in which case it is C<0> |
4027 | The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it |
3686 | (disabled). |
4028 | will be C<0>. |
3687 | |
4029 | |
3688 | =item EV_VERIFY |
4030 | =item EV_VERIFY |
3689 | |
4031 | |
3690 | Controls how much internal verification (see C<ev_loop_verify ()>) will |
4032 | Controls how much internal verification (see C<ev_loop_verify ()>) will |
3691 | be done: If set to C<0>, no internal verification code will be compiled |
4033 | be done: If set to C<0>, no internal verification code will be compiled |
… | |
… | |
3693 | called. If set to C<2>, then the internal verification code will be |
4035 | called. If set to C<2>, then the internal verification code will be |
3694 | called once per loop, which can slow down libev. If set to C<3>, then the |
4036 | called once per loop, which can slow down libev. If set to C<3>, then the |
3695 | verification code will be called very frequently, which will slow down |
4037 | verification code will be called very frequently, which will slow down |
3696 | libev considerably. |
4038 | libev considerably. |
3697 | |
4039 | |
3698 | The default is C<1>, unless C<EV_MINIMAL> is set, in which case it will be |
4040 | The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it |
3699 | C<0>. |
4041 | will be C<0>. |
3700 | |
4042 | |
3701 | =item EV_COMMON |
4043 | =item EV_COMMON |
3702 | |
4044 | |
3703 | By default, all watchers have a C<void *data> member. By redefining |
4045 | By default, all watchers have a C<void *data> member. By redefining |
3704 | this macro to a something else you can include more and other types of |
4046 | this macro to something else you can include more and other types of |
3705 | members. You have to define it each time you include one of the files, |
4047 | members. You have to define it each time you include one of the files, |
3706 | though, and it must be identical each time. |
4048 | though, and it must be identical each time. |
3707 | |
4049 | |
3708 | For example, the perl EV module uses something like this: |
4050 | For example, the perl EV module uses something like this: |
3709 | |
4051 | |
… | |
… | |
3762 | file. |
4104 | file. |
3763 | |
4105 | |
3764 | The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file |
4106 | The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file |
3765 | that everybody includes and which overrides some configure choices: |
4107 | that everybody includes and which overrides some configure choices: |
3766 | |
4108 | |
3767 | #define EV_MINIMAL 1 |
4109 | #define EV_FEATURES 8 |
3768 | #define EV_USE_POLL 0 |
4110 | #define EV_USE_SELECT 1 |
3769 | #define EV_MULTIPLICITY 0 |
|
|
3770 | #define EV_PERIODIC_ENABLE 0 |
4111 | #define EV_PREPARE_ENABLE 1 |
|
|
4112 | #define EV_IDLE_ENABLE 1 |
3771 | #define EV_STAT_ENABLE 0 |
4113 | #define EV_SIGNAL_ENABLE 1 |
3772 | #define EV_FORK_ENABLE 0 |
4114 | #define EV_CHILD_ENABLE 1 |
|
|
4115 | #define EV_USE_STDEXCEPT 0 |
3773 | #define EV_CONFIG_H <config.h> |
4116 | #define EV_CONFIG_H <config.h> |
3774 | #define EV_MINPRI 0 |
|
|
3775 | #define EV_MAXPRI 0 |
|
|
3776 | |
4117 | |
3777 | #include "ev++.h" |
4118 | #include "ev++.h" |
3778 | |
4119 | |
3779 | And a F<ev_cpp.C> implementation file that contains libev proper and is compiled: |
4120 | And a F<ev_cpp.C> implementation file that contains libev proper and is compiled: |
3780 | |
4121 | |
… | |
… | |
3840 | default loop and triggering an C<ev_async> watcher from the default loop |
4181 | default loop and triggering an C<ev_async> watcher from the default loop |
3841 | watcher callback into the event loop interested in the signal. |
4182 | watcher callback into the event loop interested in the signal. |
3842 | |
4183 | |
3843 | =back |
4184 | =back |
3844 | |
4185 | |
|
|
4186 | =head4 THREAD LOCKING EXAMPLE |
|
|
4187 | |
|
|
4188 | Here is a fictitious example of how to run an event loop in a different |
|
|
4189 | thread than where callbacks are being invoked and watchers are |
|
|
4190 | created/added/removed. |
|
|
4191 | |
|
|
4192 | For a real-world example, see the C<EV::Loop::Async> perl module, |
|
|
4193 | which uses exactly this technique (which is suited for many high-level |
|
|
4194 | languages). |
|
|
4195 | |
|
|
4196 | The example uses a pthread mutex to protect the loop data, a condition |
|
|
4197 | variable to wait for callback invocations, an async watcher to notify the |
|
|
4198 | event loop thread and an unspecified mechanism to wake up the main thread. |
|
|
4199 | |
|
|
4200 | First, you need to associate some data with the event loop: |
|
|
4201 | |
|
|
4202 | typedef struct { |
|
|
4203 | mutex_t lock; /* global loop lock */ |
|
|
4204 | ev_async async_w; |
|
|
4205 | thread_t tid; |
|
|
4206 | cond_t invoke_cv; |
|
|
4207 | } userdata; |
|
|
4208 | |
|
|
4209 | void prepare_loop (EV_P) |
|
|
4210 | { |
|
|
4211 | // for simplicity, we use a static userdata struct. |
|
|
4212 | static userdata u; |
|
|
4213 | |
|
|
4214 | ev_async_init (&u->async_w, async_cb); |
|
|
4215 | ev_async_start (EV_A_ &u->async_w); |
|
|
4216 | |
|
|
4217 | pthread_mutex_init (&u->lock, 0); |
|
|
4218 | pthread_cond_init (&u->invoke_cv, 0); |
|
|
4219 | |
|
|
4220 | // now associate this with the loop |
|
|
4221 | ev_set_userdata (EV_A_ u); |
|
|
4222 | ev_set_invoke_pending_cb (EV_A_ l_invoke); |
|
|
4223 | ev_set_loop_release_cb (EV_A_ l_release, l_acquire); |
|
|
4224 | |
|
|
4225 | // then create the thread running ev_loop |
|
|
4226 | pthread_create (&u->tid, 0, l_run, EV_A); |
|
|
4227 | } |
|
|
4228 | |
|
|
4229 | The callback for the C<ev_async> watcher does nothing: the watcher is used |
|
|
4230 | solely to wake up the event loop so it takes notice of any new watchers |
|
|
4231 | that might have been added: |
|
|
4232 | |
|
|
4233 | static void |
|
|
4234 | async_cb (EV_P_ ev_async *w, int revents) |
|
|
4235 | { |
|
|
4236 | // just used for the side effects |
|
|
4237 | } |
|
|
4238 | |
|
|
4239 | The C<l_release> and C<l_acquire> callbacks simply unlock/lock the mutex |
|
|
4240 | protecting the loop data, respectively. |
|
|
4241 | |
|
|
4242 | static void |
|
|
4243 | l_release (EV_P) |
|
|
4244 | { |
|
|
4245 | userdata *u = ev_userdata (EV_A); |
|
|
4246 | pthread_mutex_unlock (&u->lock); |
|
|
4247 | } |
|
|
4248 | |
|
|
4249 | static void |
|
|
4250 | l_acquire (EV_P) |
|
|
4251 | { |
|
|
4252 | userdata *u = ev_userdata (EV_A); |
|
|
4253 | pthread_mutex_lock (&u->lock); |
|
|
4254 | } |
|
|
4255 | |
|
|
4256 | The event loop thread first acquires the mutex, and then jumps straight |
|
|
4257 | into C<ev_loop>: |
|
|
4258 | |
|
|
4259 | void * |
|
|
4260 | l_run (void *thr_arg) |
|
|
4261 | { |
|
|
4262 | struct ev_loop *loop = (struct ev_loop *)thr_arg; |
|
|
4263 | |
|
|
4264 | l_acquire (EV_A); |
|
|
4265 | pthread_setcanceltype (PTHREAD_CANCEL_ASYNCHRONOUS, 0); |
|
|
4266 | ev_loop (EV_A_ 0); |
|
|
4267 | l_release (EV_A); |
|
|
4268 | |
|
|
4269 | return 0; |
|
|
4270 | } |
|
|
4271 | |
|
|
4272 | Instead of invoking all pending watchers, the C<l_invoke> callback will |
|
|
4273 | signal the main thread via some unspecified mechanism (signals? pipe |
|
|
4274 | writes? C<Async::Interrupt>?) and then waits until all pending watchers |
|
|
4275 | have been called (in a while loop because a) spurious wakeups are possible |
|
|
4276 | and b) skipping inter-thread-communication when there are no pending |
|
|
4277 | watchers is very beneficial): |
|
|
4278 | |
|
|
4279 | static void |
|
|
4280 | l_invoke (EV_P) |
|
|
4281 | { |
|
|
4282 | userdata *u = ev_userdata (EV_A); |
|
|
4283 | |
|
|
4284 | while (ev_pending_count (EV_A)) |
|
|
4285 | { |
|
|
4286 | wake_up_other_thread_in_some_magic_or_not_so_magic_way (); |
|
|
4287 | pthread_cond_wait (&u->invoke_cv, &u->lock); |
|
|
4288 | } |
|
|
4289 | } |
|
|
4290 | |
|
|
4291 | Now, whenever the main thread gets told to invoke pending watchers, it |
|
|
4292 | will grab the lock, call C<ev_invoke_pending> and then signal the loop |
|
|
4293 | thread to continue: |
|
|
4294 | |
|
|
4295 | static void |
|
|
4296 | real_invoke_pending (EV_P) |
|
|
4297 | { |
|
|
4298 | userdata *u = ev_userdata (EV_A); |
|
|
4299 | |
|
|
4300 | pthread_mutex_lock (&u->lock); |
|
|
4301 | ev_invoke_pending (EV_A); |
|
|
4302 | pthread_cond_signal (&u->invoke_cv); |
|
|
4303 | pthread_mutex_unlock (&u->lock); |
|
|
4304 | } |
|
|
4305 | |
|
|
4306 | Whenever you want to start/stop a watcher or do other modifications to an |
|
|
4307 | event loop, you will now have to lock: |
|
|
4308 | |
|
|
4309 | ev_timer timeout_watcher; |
|
|
4310 | userdata *u = ev_userdata (EV_A); |
|
|
4311 | |
|
|
4312 | ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.); |
|
|
4313 | |
|
|
4314 | pthread_mutex_lock (&u->lock); |
|
|
4315 | ev_timer_start (EV_A_ &timeout_watcher); |
|
|
4316 | ev_async_send (EV_A_ &u->async_w); |
|
|
4317 | pthread_mutex_unlock (&u->lock); |
|
|
4318 | |
|
|
4319 | Note that sending the C<ev_async> watcher is required because otherwise |
|
|
4320 | an event loop currently blocking in the kernel will have no knowledge |
|
|
4321 | about the newly added timer. By waking up the loop it will pick up any new |
|
|
4322 | watchers in the next event loop iteration. |
|
|
4323 | |
3845 | =head3 COROUTINES |
4324 | =head3 COROUTINES |
3846 | |
4325 | |
3847 | Libev is very accommodating to coroutines ("cooperative threads"): |
4326 | Libev is very accommodating to coroutines ("cooperative threads"): |
3848 | libev fully supports nesting calls to its functions from different |
4327 | libev fully supports nesting calls to its functions from different |
3849 | coroutines (e.g. you can call C<ev_loop> on the same loop from two |
4328 | coroutines (e.g. you can call C<ev_loop> on the same loop from two |
3850 | different coroutines, and switch freely between both coroutines running the |
4329 | different coroutines, and switch freely between both coroutines running |
3851 | loop, as long as you don't confuse yourself). The only exception is that |
4330 | the loop, as long as you don't confuse yourself). The only exception is |
3852 | you must not do this from C<ev_periodic> reschedule callbacks. |
4331 | that you must not do this from C<ev_periodic> reschedule callbacks. |
3853 | |
4332 | |
3854 | Care has been taken to ensure that libev does not keep local state inside |
4333 | Care has been taken to ensure that libev does not keep local state inside |
3855 | C<ev_loop>, and other calls do not usually allow for coroutine switches as |
4334 | C<ev_loop>, and other calls do not usually allow for coroutine switches as |
3856 | they do not call any callbacks. |
4335 | they do not call any callbacks. |
3857 | |
4336 | |
… | |
… | |
3871 | maintainable. |
4350 | maintainable. |
3872 | |
4351 | |
3873 | And of course, some compiler warnings are just plain stupid, or simply |
4352 | And of course, some compiler warnings are just plain stupid, or simply |
3874 | wrong (because they don't actually warn about the condition their message |
4353 | wrong (because they don't actually warn about the condition their message |
3875 | seems to warn about). For example, certain older gcc versions had some |
4354 | seems to warn about). For example, certain older gcc versions had some |
3876 | warnings that resulted an extreme number of false positives. These have |
4355 | warnings that resulted in an extreme number of false positives. These have |
3877 | been fixed, but some people still insist on making code warn-free with |
4356 | been fixed, but some people still insist on making code warn-free with |
3878 | such buggy versions. |
4357 | such buggy versions. |
3879 | |
4358 | |
3880 | While libev is written to generate as few warnings as possible, |
4359 | While libev is written to generate as few warnings as possible, |
3881 | "warn-free" code is not a goal, and it is recommended not to build libev |
4360 | "warn-free" code is not a goal, and it is recommended not to build libev |
… | |
… | |
3917 | I suggest using suppression lists. |
4396 | I suggest using suppression lists. |
3918 | |
4397 | |
3919 | |
4398 | |
3920 | =head1 PORTABILITY NOTES |
4399 | =head1 PORTABILITY NOTES |
3921 | |
4400 | |
|
|
4401 | =head2 GNU/LINUX 32 BIT LIMITATIONS |
|
|
4402 | |
|
|
4403 | GNU/Linux is the only common platform that supports 64 bit file/large file |
|
|
4404 | interfaces but I<disables> them by default. |
|
|
4405 | |
|
|
4406 | That means that libev compiled in the default environment doesn't support |
|
|
4407 | files larger than 2GiB or so, which mainly affects C<ev_stat> watchers. |
|
|
4408 | |
|
|
4409 | Unfortunately, many programs try to work around this GNU/Linux issue |
|
|
4410 | by enabling the large file API, which makes them incompatible with the |
|
|
4411 | standard libev compiled for their system. |
|
|
4412 | |
|
|
4413 | Likewise, libev cannot enable the large file API itself as this would |
|
|
4414 | suddenly make it incompatible to the default compile time environment, |
|
|
4415 | i.e. all programs not using special compile switches. |
|
|
4416 | |
|
|
4417 | =head2 OS/X AND DARWIN BUGS |
|
|
4418 | |
|
|
4419 | The whole thing is a bug if you ask me - basically any system interface |
|
|
4420 | you touch is broken, whether it is locales, poll, kqueue or even the |
|
|
4421 | OpenGL drivers. |
|
|
4422 | |
|
|
4423 | =head3 C<kqueue> is buggy |
|
|
4424 | |
|
|
4425 | The kqueue syscall is broken in all known versions - most versions support |
|
|
4426 | only sockets, many support pipes. |
|
|
4427 | |
|
|
4428 | Libev tries to work around this by not using C<kqueue> by default on |
|
|
4429 | this rotten platform, but of course you can still ask for it when creating |
|
|
4430 | a loop. |
|
|
4431 | |
|
|
4432 | =head3 C<poll> is buggy |
|
|
4433 | |
|
|
4434 | Instead of fixing C<kqueue>, Apple replaced their (working) C<poll> |
|
|
4435 | implementation by something calling C<kqueue> internally around the 10.5.6 |
|
|
4436 | release, so now C<kqueue> I<and> C<poll> are broken. |
|
|
4437 | |
|
|
4438 | Libev tries to work around this by not using C<poll> by default on |
|
|
4439 | this rotten platform, but of course you can still ask for it when creating |
|
|
4440 | a loop. |
|
|
4441 | |
|
|
4442 | =head3 C<select> is buggy |
|
|
4443 | |
|
|
4444 | All that's left is C<select>, and of course Apple found a way to fuck this |
|
|
4445 | one up as well: On OS/X, C<select> actively limits the number of file |
|
|
4446 | descriptors you can pass in to 1024 - your program suddenly crashes when |
|
|
4447 | you use more. |
|
|
4448 | |
|
|
4449 | There is an undocumented "workaround" for this - defining |
|
|
4450 | C<_DARWIN_UNLIMITED_SELECT>, which libev tries to use, so select I<should> |
|
|
4451 | work on OS/X. |
|
|
4452 | |
|
|
4453 | =head2 SOLARIS PROBLEMS AND WORKAROUNDS |
|
|
4454 | |
|
|
4455 | =head3 C<errno> reentrancy |
|
|
4456 | |
|
|
4457 | The default compile environment on Solaris is unfortunately so |
|
|
4458 | thread-unsafe that you can't even use components/libraries compiled |
|
|
4459 | without C<-D_REENTRANT> (as long as they use C<errno>), which, of course, |
|
|
4460 | isn't defined by default. |
|
|
4461 | |
|
|
4462 | If you want to use libev in threaded environments you have to make sure |
|
|
4463 | it's compiled with C<_REENTRANT> defined. |
|
|
4464 | |
|
|
4465 | =head3 Event port backend |
|
|
4466 | |
|
|
4467 | The scalable event interface for Solaris is called "event ports". Unfortunately, |
|
|
4468 | this mechanism is very buggy. If you run into high CPU usage, your program |
|
|
4469 | freezes or you get a large number of spurious wakeups, make sure you have |
|
|
4470 | all the relevant and latest kernel patches applied. No, I don't know which |
|
|
4471 | ones, but there are multiple ones. |
|
|
4472 | |
|
|
4473 | If you can't get it to work, you can try running the program by setting |
|
|
4474 | the environment variable C<LIBEV_FLAGS=3> to only allow C<poll> and |
|
|
4475 | C<select> backends. |
|
|
4476 | |
|
|
4477 | =head2 AIX POLL BUG |
|
|
4478 | |
|
|
4479 | AIX unfortunately has a broken C<poll.h> header. Libev works around |
|
|
4480 | this by trying to avoid the poll backend altogether (i.e. it's not even |
|
|
4481 | compiled in), which normally isn't a big problem as C<select> works fine |
|
|
4482 | with large bitsets, and AIX is dead anyway. |
|
|
4483 | |
3922 | =head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS |
4484 | =head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS |
|
|
4485 | |
|
|
4486 | =head3 General issues |
3923 | |
4487 | |
3924 | Win32 doesn't support any of the standards (e.g. POSIX) that libev |
4488 | Win32 doesn't support any of the standards (e.g. POSIX) that libev |
3925 | requires, and its I/O model is fundamentally incompatible with the POSIX |
4489 | requires, and its I/O model is fundamentally incompatible with the POSIX |
3926 | model. Libev still offers limited functionality on this platform in |
4490 | model. Libev still offers limited functionality on this platform in |
3927 | the form of the C<EVBACKEND_SELECT> backend, and only supports socket |
4491 | the form of the C<EVBACKEND_SELECT> backend, and only supports socket |
3928 | descriptors. This only applies when using Win32 natively, not when using |
4492 | descriptors. This only applies when using Win32 natively, not when using |
3929 | e.g. cygwin. |
4493 | e.g. cygwin. Actually, it only applies to the microsofts own compilers, |
|
|
4494 | as every compielr comes with a slightly differently broken/incompatible |
|
|
4495 | environment. |
3930 | |
4496 | |
3931 | Lifting these limitations would basically require the full |
4497 | Lifting these limitations would basically require the full |
3932 | re-implementation of the I/O system. If you are into these kinds of |
4498 | re-implementation of the I/O system. If you are into this kind of thing, |
3933 | things, then note that glib does exactly that for you in a very portable |
4499 | then note that glib does exactly that for you in a very portable way (note |
3934 | way (note also that glib is the slowest event library known to man). |
4500 | also that glib is the slowest event library known to man). |
3935 | |
4501 | |
3936 | There is no supported compilation method available on windows except |
4502 | There is no supported compilation method available on windows except |
3937 | embedding it into other applications. |
4503 | embedding it into other applications. |
|
|
4504 | |
|
|
4505 | Sensible signal handling is officially unsupported by Microsoft - libev |
|
|
4506 | tries its best, but under most conditions, signals will simply not work. |
3938 | |
4507 | |
3939 | Not a libev limitation but worth mentioning: windows apparently doesn't |
4508 | Not a libev limitation but worth mentioning: windows apparently doesn't |
3940 | accept large writes: instead of resulting in a partial write, windows will |
4509 | accept large writes: instead of resulting in a partial write, windows will |
3941 | either accept everything or return C<ENOBUFS> if the buffer is too large, |
4510 | either accept everything or return C<ENOBUFS> if the buffer is too large, |
3942 | so make sure you only write small amounts into your sockets (less than a |
4511 | so make sure you only write small amounts into your sockets (less than a |
… | |
… | |
3947 | the abysmal performance of winsockets, using a large number of sockets |
4516 | the abysmal performance of winsockets, using a large number of sockets |
3948 | is not recommended (and not reasonable). If your program needs to use |
4517 | is not recommended (and not reasonable). If your program needs to use |
3949 | more than a hundred or so sockets, then likely it needs to use a totally |
4518 | more than a hundred or so sockets, then likely it needs to use a totally |
3950 | different implementation for windows, as libev offers the POSIX readiness |
4519 | different implementation for windows, as libev offers the POSIX readiness |
3951 | notification model, which cannot be implemented efficiently on windows |
4520 | notification model, which cannot be implemented efficiently on windows |
3952 | (Microsoft monopoly games). |
4521 | (due to Microsoft monopoly games). |
3953 | |
4522 | |
3954 | A typical way to use libev under windows is to embed it (see the embedding |
4523 | A typical way to use libev under windows is to embed it (see the embedding |
3955 | section for details) and use the following F<evwrap.h> header file instead |
4524 | section for details) and use the following F<evwrap.h> header file instead |
3956 | of F<ev.h>: |
4525 | of F<ev.h>: |
3957 | |
4526 | |
… | |
… | |
3964 | you do I<not> compile the F<ev.c> or any other embedded source files!): |
4533 | you do I<not> compile the F<ev.c> or any other embedded source files!): |
3965 | |
4534 | |
3966 | #include "evwrap.h" |
4535 | #include "evwrap.h" |
3967 | #include "ev.c" |
4536 | #include "ev.c" |
3968 | |
4537 | |
3969 | =over 4 |
|
|
3970 | |
|
|
3971 | =item The winsocket select function |
4538 | =head3 The winsocket C<select> function |
3972 | |
4539 | |
3973 | The winsocket C<select> function doesn't follow POSIX in that it |
4540 | The winsocket C<select> function doesn't follow POSIX in that it |
3974 | requires socket I<handles> and not socket I<file descriptors> (it is |
4541 | requires socket I<handles> and not socket I<file descriptors> (it is |
3975 | also extremely buggy). This makes select very inefficient, and also |
4542 | also extremely buggy). This makes select very inefficient, and also |
3976 | requires a mapping from file descriptors to socket handles (the Microsoft |
4543 | requires a mapping from file descriptors to socket handles (the Microsoft |
… | |
… | |
3985 | #define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */ |
4552 | #define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */ |
3986 | |
4553 | |
3987 | Note that winsockets handling of fd sets is O(n), so you can easily get a |
4554 | Note that winsockets handling of fd sets is O(n), so you can easily get a |
3988 | complexity in the O(n²) range when using win32. |
4555 | complexity in the O(n²) range when using win32. |
3989 | |
4556 | |
3990 | =item Limited number of file descriptors |
4557 | =head3 Limited number of file descriptors |
3991 | |
4558 | |
3992 | Windows has numerous arbitrary (and low) limits on things. |
4559 | Windows has numerous arbitrary (and low) limits on things. |
3993 | |
4560 | |
3994 | Early versions of winsocket's select only supported waiting for a maximum |
4561 | Early versions of winsocket's select only supported waiting for a maximum |
3995 | of C<64> handles (probably owning to the fact that all windows kernels |
4562 | of C<64> handles (probably owning to the fact that all windows kernels |
3996 | can only wait for C<64> things at the same time internally; Microsoft |
4563 | can only wait for C<64> things at the same time internally; Microsoft |
3997 | recommends spawning a chain of threads and wait for 63 handles and the |
4564 | recommends spawning a chain of threads and wait for 63 handles and the |
3998 | previous thread in each. Great). |
4565 | previous thread in each. Sounds great!). |
3999 | |
4566 | |
4000 | Newer versions support more handles, but you need to define C<FD_SETSIZE> |
4567 | Newer versions support more handles, but you need to define C<FD_SETSIZE> |
4001 | to some high number (e.g. C<2048>) before compiling the winsocket select |
4568 | to some high number (e.g. C<2048>) before compiling the winsocket select |
4002 | call (which might be in libev or elsewhere, for example, perl does its own |
4569 | call (which might be in libev or elsewhere, for example, perl and many |
4003 | select emulation on windows). |
4570 | other interpreters do their own select emulation on windows). |
4004 | |
4571 | |
4005 | Another limit is the number of file descriptors in the Microsoft runtime |
4572 | Another limit is the number of file descriptors in the Microsoft runtime |
4006 | libraries, which by default is C<64> (there must be a hidden I<64> fetish |
4573 | libraries, which by default is C<64> (there must be a hidden I<64> |
4007 | or something like this inside Microsoft). You can increase this by calling |
4574 | fetish or something like this inside Microsoft). You can increase this |
4008 | C<_setmaxstdio>, which can increase this limit to C<2048> (another |
4575 | by calling C<_setmaxstdio>, which can increase this limit to C<2048> |
4009 | arbitrary limit), but is broken in many versions of the Microsoft runtime |
4576 | (another arbitrary limit), but is broken in many versions of the Microsoft |
4010 | libraries. |
|
|
4011 | |
|
|
4012 | This might get you to about C<512> or C<2048> sockets (depending on |
4577 | runtime libraries. This might get you to about C<512> or C<2048> sockets |
4013 | windows version and/or the phase of the moon). To get more, you need to |
4578 | (depending on windows version and/or the phase of the moon). To get more, |
4014 | wrap all I/O functions and provide your own fd management, but the cost of |
4579 | you need to wrap all I/O functions and provide your own fd management, but |
4015 | calling select (O(n²)) will likely make this unworkable. |
4580 | the cost of calling select (O(n²)) will likely make this unworkable. |
4016 | |
|
|
4017 | =back |
|
|
4018 | |
4581 | |
4019 | =head2 PORTABILITY REQUIREMENTS |
4582 | =head2 PORTABILITY REQUIREMENTS |
4020 | |
4583 | |
4021 | In addition to a working ISO-C implementation and of course the |
4584 | In addition to a working ISO-C implementation and of course the |
4022 | backend-specific APIs, libev relies on a few additional extensions: |
4585 | backend-specific APIs, libev relies on a few additional extensions: |
… | |
… | |
4063 | =item C<double> must hold a time value in seconds with enough accuracy |
4626 | =item C<double> must hold a time value in seconds with enough accuracy |
4064 | |
4627 | |
4065 | The type C<double> is used to represent timestamps. It is required to |
4628 | The type C<double> is used to represent timestamps. It is required to |
4066 | have at least 51 bits of mantissa (and 9 bits of exponent), which is good |
4629 | have at least 51 bits of mantissa (and 9 bits of exponent), which is good |
4067 | enough for at least into the year 4000. This requirement is fulfilled by |
4630 | enough for at least into the year 4000. This requirement is fulfilled by |
4068 | implementations implementing IEEE 754 (basically all existing ones). |
4631 | implementations implementing IEEE 754, which is basically all existing |
|
|
4632 | ones. With IEEE 754 doubles, you get microsecond accuracy until at least |
|
|
4633 | 2200. |
4069 | |
4634 | |
4070 | =back |
4635 | =back |
4071 | |
4636 | |
4072 | If you know of other additional requirements drop me a note. |
4637 | If you know of other additional requirements drop me a note. |
4073 | |
4638 | |
… | |
… | |
4141 | involves iterating over all running async watchers or all signal numbers. |
4706 | involves iterating over all running async watchers or all signal numbers. |
4142 | |
4707 | |
4143 | =back |
4708 | =back |
4144 | |
4709 | |
4145 | |
4710 | |
|
|
4711 | =head1 PORTING FROM LIBEV 3.X TO 4.X |
|
|
4712 | |
|
|
4713 | The major version 4 introduced some minor incompatible changes to the API. |
|
|
4714 | |
|
|
4715 | At the moment, the C<ev.h> header file tries to implement superficial |
|
|
4716 | compatibility, so most programs should still compile. Those might be |
|
|
4717 | removed in later versions of libev, so better update early than late. |
|
|
4718 | |
|
|
4719 | =over 4 |
|
|
4720 | |
|
|
4721 | =item C<ev_loop_count> renamed to C<ev_iteration> |
|
|
4722 | |
|
|
4723 | =item C<ev_loop_depth> renamed to C<ev_depth> |
|
|
4724 | |
|
|
4725 | =item C<ev_loop_verify> renamed to C<ev_verify> |
|
|
4726 | |
|
|
4727 | Most functions working on C<struct ev_loop> objects don't have an |
|
|
4728 | C<ev_loop_> prefix, so it was removed. Note that C<ev_loop_fork> is |
|
|
4729 | still called C<ev_loop_fork> because it would otherwise clash with the |
|
|
4730 | C<ev_fork> typedef. |
|
|
4731 | |
|
|
4732 | =item C<EV_TIMEOUT> renamed to C<EV_TIMER> in C<revents> |
|
|
4733 | |
|
|
4734 | This is a simple rename - all other watcher types use their name |
|
|
4735 | as revents flag, and now C<ev_timer> does, too. |
|
|
4736 | |
|
|
4737 | Both C<EV_TIMER> and C<EV_TIMEOUT> symbols were present in 3.x versions |
|
|
4738 | and continue to be present for the foreseeable future, so this is mostly a |
|
|
4739 | documentation change. |
|
|
4740 | |
|
|
4741 | =item C<EV_MINIMAL> mechanism replaced by C<EV_FEATURES> |
|
|
4742 | |
|
|
4743 | The preprocessor symbol C<EV_MINIMAL> has been replaced by a different |
|
|
4744 | mechanism, C<EV_FEATURES>. Programs using C<EV_MINIMAL> usually compile |
|
|
4745 | and work, but the library code will of course be larger. |
|
|
4746 | |
|
|
4747 | =back |
|
|
4748 | |
|
|
4749 | |
4146 | =head1 GLOSSARY |
4750 | =head1 GLOSSARY |
4147 | |
4751 | |
4148 | =over 4 |
4752 | =over 4 |
4149 | |
4753 | |
4150 | =item active |
4754 | =item active |
… | |
… | |
4171 | A change of state of some external event, such as data now being available |
4775 | A change of state of some external event, such as data now being available |
4172 | for reading on a file descriptor, time having passed or simply not having |
4776 | for reading on a file descriptor, time having passed or simply not having |
4173 | any other events happening anymore. |
4777 | any other events happening anymore. |
4174 | |
4778 | |
4175 | In libev, events are represented as single bits (such as C<EV_READ> or |
4779 | In libev, events are represented as single bits (such as C<EV_READ> or |
4176 | C<EV_TIMEOUT>). |
4780 | C<EV_TIMER>). |
4177 | |
4781 | |
4178 | =item event library |
4782 | =item event library |
4179 | |
4783 | |
4180 | A software package implementing an event model and loop. |
4784 | A software package implementing an event model and loop. |
4181 | |
4785 | |