… | |
… | |
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 |
… | |
… | |
124 | this argument. |
124 | this argument. |
125 | |
125 | |
126 | =head2 TIME REPRESENTATION |
126 | =head2 TIME REPRESENTATION |
127 | |
127 | |
128 | Libev represents time as a single floating point number, representing |
128 | Libev represents time as a single floating point number, representing |
129 | the (fractional) number of seconds since the (POSIX) epoch (somewhere |
129 | the (fractional) number of seconds since the (POSIX) epoch (in practise |
130 | near the beginning of 1970, details are complicated, don't ask). This |
130 | somewhere near the beginning of 1970, details are complicated, don't |
131 | 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 |
132 | 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 |
133 | 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 | |
134 | 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 |
135 | throughout libev. |
136 | time differences (e.g. delays) throughout libev. |
136 | |
137 | |
137 | =head1 ERROR HANDLING |
138 | =head1 ERROR HANDLING |
138 | |
139 | |
139 | Libev knows three classes of errors: operating system errors, usage errors |
140 | Libev knows three classes of errors: operating system errors, usage errors |
140 | and internal errors (bugs). |
141 | and internal errors (bugs). |
… | |
… | |
191 | as this indicates an incompatible change. Minor versions are usually |
192 | as this indicates an incompatible change. Minor versions are usually |
192 | 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 |
193 | not a problem. |
194 | not a problem. |
194 | |
195 | |
195 | 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 |
196 | version. |
197 | version (note, however, that this will not detect ABI mismatches :). |
197 | |
198 | |
198 | assert (("libev version mismatch", |
199 | assert (("libev version mismatch", |
199 | ev_version_major () == EV_VERSION_MAJOR |
200 | ev_version_major () == EV_VERSION_MAJOR |
200 | && ev_version_minor () >= EV_VERSION_MINOR)); |
201 | && ev_version_minor () >= EV_VERSION_MINOR)); |
201 | |
202 | |
… | |
… | |
345 | 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 |
346 | around bugs. |
347 | around bugs. |
347 | |
348 | |
348 | =item C<EVFLAG_FORKCHECK> |
349 | =item C<EVFLAG_FORKCHECK> |
349 | |
350 | |
350 | 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 |
351 | 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. |
352 | enabling this flag. |
|
|
353 | |
353 | |
354 | 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, |
355 | 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 |
356 | 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 |
357 | 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 |
… | |
… | |
370 | When this flag is specified, then libev will not attempt to use the |
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 |
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 |
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. |
373 | otherwise each loop using C<ev_stat> watchers consumes one inotify handle. |
374 | |
374 | |
375 | =item C<EVFLAG_NOSIGFD> |
375 | =item C<EVFLAG_SIGNALFD> |
376 | |
376 | |
377 | When this flag is specified, then libev will not attempt to use the |
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 is |
378 | I<signalfd> API for it's C<ev_signal> (and C<ev_child>) watchers. This API |
379 | probably only useful to work around any bugs in libev. Consequently, this |
379 | delivers signals synchronously, which makes it both faster and might make |
380 | flag might go away once the signalfd functionality is considered stable, |
380 | it possible to get the queued signal data. It can also simplify signal |
381 | so it's useful mostly in environment variables and not in program code. |
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. |
382 | |
387 | |
383 | =item C<EVBACKEND_SELECT> (value 1, portable select backend) |
388 | =item C<EVBACKEND_SELECT> (value 1, portable select backend) |
384 | |
389 | |
385 | 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 |
386 | 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, |
… | |
… | |
434 | of course I<doesn't>, and epoll just loves to report events for totally |
439 | of course I<doesn't>, and epoll just loves to report events for totally |
435 | I<different> file descriptors (even already closed ones, so one cannot |
440 | I<different> file descriptors (even already closed ones, so one cannot |
436 | even remove them from the set) than registered in the set (especially |
441 | even remove them from the set) than registered in the set (especially |
437 | on SMP systems). Libev tries to counter these spurious notifications by |
442 | on SMP systems). Libev tries to counter these spurious notifications by |
438 | employing an additional generation counter and comparing that against the |
443 | employing an additional generation counter and comparing that against the |
439 | events to filter out spurious ones, recreating the set when required. |
444 | events to filter out spurious ones, recreating the set when required. Last |
|
|
445 | not least, it also refuses to work with some file descriptors which work |
|
|
446 | perfectly fine with C<select> (files, many character devices...). |
440 | |
447 | |
441 | While stopping, setting and starting an I/O watcher in the same iteration |
448 | While stopping, setting and starting an I/O watcher in the same iteration |
442 | will result in some caching, there is still a system call per such |
449 | will result in some caching, there is still a system call per such |
443 | incident (because the same I<file descriptor> could point to a different |
450 | incident (because the same I<file descriptor> could point to a different |
444 | I<file description> now), so its best to avoid that. Also, C<dup ()>'ed |
451 | I<file description> now), so its best to avoid that. Also, C<dup ()>'ed |
… | |
… | |
562 | ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE); |
569 | ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE); |
563 | |
570 | |
564 | =item struct ev_loop *ev_loop_new (unsigned int flags) |
571 | =item struct ev_loop *ev_loop_new (unsigned int flags) |
565 | |
572 | |
566 | Similar to C<ev_default_loop>, but always creates a new event loop that is |
573 | Similar to C<ev_default_loop>, but always creates a new event loop that is |
567 | always distinct from the default loop. Unlike the default loop, it cannot |
574 | always distinct from the default loop. |
568 | handle signal and child watchers, and attempts to do so will be greeted by |
|
|
569 | undefined behaviour (or a failed assertion if assertions are enabled). |
|
|
570 | |
575 | |
571 | Note that this function I<is> thread-safe, and the recommended way to use |
576 | Note that this function I<is> thread-safe, and one common way to use |
572 | libev with threads is indeed to create one loop per thread, and using the |
577 | libev with threads is indeed to create one loop per thread, and using the |
573 | default loop in the "main" or "initial" thread. |
578 | default loop in the "main" or "initial" thread. |
574 | |
579 | |
575 | Example: Try to create a event loop that uses epoll and nothing else. |
580 | Example: Try to create a event loop that uses epoll and nothing else. |
576 | |
581 | |
… | |
… | |
578 | if (!epoller) |
583 | if (!epoller) |
579 | fatal ("no epoll found here, maybe it hides under your chair"); |
584 | fatal ("no epoll found here, maybe it hides under your chair"); |
580 | |
585 | |
581 | =item ev_default_destroy () |
586 | =item ev_default_destroy () |
582 | |
587 | |
583 | Destroys the default loop again (frees all memory and kernel state |
588 | Destroys the default loop (frees all memory and kernel state etc.). None |
584 | etc.). None of the active event watchers will be stopped in the normal |
589 | of the active event watchers will be stopped in the normal sense, so |
585 | sense, so e.g. C<ev_is_active> might still return true. It is your |
590 | e.g. C<ev_is_active> might still return true. It is your responsibility to |
586 | responsibility to either stop all watchers cleanly yourself I<before> |
591 | either stop all watchers cleanly yourself I<before> calling this function, |
587 | calling this function, or cope with the fact afterwards (which is usually |
592 | or cope with the fact afterwards (which is usually the easiest thing, you |
588 | the easiest thing, you can just ignore the watchers and/or C<free ()> them |
593 | can just ignore the watchers and/or C<free ()> them for example). |
589 | for example). |
|
|
590 | |
594 | |
591 | Note that certain global state, such as signal state (and installed signal |
595 | Note that certain global state, such as signal state (and installed signal |
592 | handlers), will not be freed by this function, and related watchers (such |
596 | handlers), will not be freed by this function, and related watchers (such |
593 | as signal and child watchers) would need to be stopped manually. |
597 | as signal and child watchers) would need to be stopped manually. |
594 | |
598 | |
… | |
… | |
609 | name, you can call it anytime, but it makes most sense after forking, in |
613 | name, you can call it anytime, but it makes most sense after forking, in |
610 | the child process (or both child and parent, but that again makes little |
614 | the child process (or both child and parent, but that again makes little |
611 | sense). You I<must> call it in the child before using any of the libev |
615 | sense). You I<must> call it in the child before using any of the libev |
612 | functions, and it will only take effect at the next C<ev_loop> iteration. |
616 | functions, and it will only take effect at the next C<ev_loop> iteration. |
613 | |
617 | |
|
|
618 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
|
|
619 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
|
|
620 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
|
|
621 | during fork. |
|
|
622 | |
614 | On the other hand, you only need to call this function in the child |
623 | On the other hand, you only need to call this function in the child |
615 | process if and only if you want to use the event library in the child. If |
624 | process if and only if you want to use the event loop in the child. If you |
616 | you just fork+exec, you don't have to call it at all. |
625 | just fork+exec or create a new loop in the child, you don't have to call |
|
|
626 | it at all. |
617 | |
627 | |
618 | The function itself is quite fast and it's usually not a problem to call |
628 | The function itself is quite fast and it's usually not a problem to call |
619 | it just in case after a fork. To make this easy, the function will fit in |
629 | it just in case after a fork. To make this easy, the function will fit in |
620 | quite nicely into a call to C<pthread_atfork>: |
630 | quite nicely into a call to C<pthread_atfork>: |
621 | |
631 | |
… | |
… | |
623 | |
633 | |
624 | =item ev_loop_fork (loop) |
634 | =item ev_loop_fork (loop) |
625 | |
635 | |
626 | Like C<ev_default_fork>, but acts on an event loop created by |
636 | Like C<ev_default_fork>, but acts on an event loop created by |
627 | C<ev_loop_new>. Yes, you have to call this on every allocated event loop |
637 | C<ev_loop_new>. Yes, you have to call this on every allocated event loop |
628 | after fork that you want to re-use in the child, and how you do this is |
638 | after fork that you want to re-use in the child, and how you keep track of |
629 | entirely your own problem. |
639 | them is entirely your own problem. |
630 | |
640 | |
631 | =item int ev_is_default_loop (loop) |
641 | =item int ev_is_default_loop (loop) |
632 | |
642 | |
633 | Returns true when the given loop is, in fact, the default loop, and false |
643 | Returns true when the given loop is, in fact, the default loop, and false |
634 | otherwise. |
644 | otherwise. |
635 | |
645 | |
636 | =item unsigned int ev_loop_count (loop) |
646 | =item unsigned int ev_iteration (loop) |
637 | |
647 | |
638 | Returns the count of loop iterations for the loop, which is identical to |
648 | Returns the current iteration count for the loop, which is identical to |
639 | the number of times libev did poll for new events. It starts at C<0> and |
649 | the number of times libev did poll for new events. It starts at C<0> and |
640 | happily wraps around with enough iterations. |
650 | happily wraps around with enough iterations. |
641 | |
651 | |
642 | This value can sometimes be useful as a generation counter of sorts (it |
652 | This value can sometimes be useful as a generation counter of sorts (it |
643 | "ticks" the number of loop iterations), as it roughly corresponds with |
653 | "ticks" the number of loop iterations), as it roughly corresponds with |
644 | C<ev_prepare> and C<ev_check> calls. |
654 | C<ev_prepare> and C<ev_check> calls - and is incremented between the |
|
|
655 | prepare and check phases. |
645 | |
656 | |
646 | =item unsigned int ev_loop_depth (loop) |
657 | =item unsigned int ev_depth (loop) |
647 | |
658 | |
648 | Returns the number of times C<ev_loop> was entered minus the number of |
659 | Returns the number of times C<ev_loop> was entered minus the number of |
649 | times C<ev_loop> was exited, in other words, the recursion depth. |
660 | times C<ev_loop> was exited, in other words, the recursion depth. |
650 | |
661 | |
651 | Outside C<ev_loop>, this number is zero. In a callback, this number is |
662 | Outside C<ev_loop>, this number is zero. In a callback, this number is |
652 | C<1>, unless C<ev_loop> was invoked recursively (or from another thread), |
663 | C<1>, unless C<ev_loop> was invoked recursively (or from another thread), |
653 | in which case it is higher. |
664 | in which case it is higher. |
654 | |
665 | |
655 | Leaving C<ev_loop> abnormally (setjmp/longjmp, cancelling the thread |
666 | Leaving C<ev_loop> abnormally (setjmp/longjmp, cancelling the thread |
656 | etc.), doesn't count as exit. |
667 | etc.), doesn't count as "exit" - consider this as a hint to avoid such |
|
|
668 | ungentleman behaviour unless it's really convenient. |
657 | |
669 | |
658 | =item unsigned int ev_backend (loop) |
670 | =item unsigned int ev_backend (loop) |
659 | |
671 | |
660 | Returns one of the C<EVBACKEND_*> flags indicating the event backend in |
672 | Returns one of the C<EVBACKEND_*> flags indicating the event backend in |
661 | use. |
673 | use. |
… | |
… | |
695 | C<ev_resume> directly afterwards to resume timer processing. |
707 | C<ev_resume> directly afterwards to resume timer processing. |
696 | |
708 | |
697 | Effectively, all C<ev_timer> watchers will be delayed by the time spend |
709 | Effectively, all C<ev_timer> watchers will be delayed by the time spend |
698 | between C<ev_suspend> and C<ev_resume>, and all C<ev_periodic> watchers |
710 | between C<ev_suspend> and C<ev_resume>, and all C<ev_periodic> watchers |
699 | will be rescheduled (that is, they will lose any events that would have |
711 | will be rescheduled (that is, they will lose any events that would have |
700 | occured while suspended). |
712 | occurred while suspended). |
701 | |
713 | |
702 | After calling C<ev_suspend> you B<must not> call I<any> function on the |
714 | After calling C<ev_suspend> you B<must not> call I<any> function on the |
703 | given loop other than C<ev_resume>, and you B<must not> call C<ev_resume> |
715 | given loop other than C<ev_resume>, and you B<must not> call C<ev_resume> |
704 | without a previous call to C<ev_suspend>. |
716 | without a previous call to C<ev_suspend>. |
705 | |
717 | |
… | |
… | |
782 | C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or |
794 | C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or |
783 | C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return. |
795 | C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return. |
784 | |
796 | |
785 | This "unloop state" will be cleared when entering C<ev_loop> again. |
797 | This "unloop state" will be cleared when entering C<ev_loop> again. |
786 | |
798 | |
787 | It is safe to call C<ev_unloop> from otuside any C<ev_loop> calls. |
799 | It is safe to call C<ev_unloop> from outside any C<ev_loop> calls. |
788 | |
800 | |
789 | =item ev_ref (loop) |
801 | =item ev_ref (loop) |
790 | |
802 | |
791 | =item ev_unref (loop) |
803 | =item ev_unref (loop) |
792 | |
804 | |
793 | Ref/unref can be used to add or remove a reference count on the event |
805 | Ref/unref can be used to add or remove a reference count on the event |
794 | loop: Every watcher keeps one reference, and as long as the reference |
806 | loop: Every watcher keeps one reference, and as long as the reference |
795 | count is nonzero, C<ev_loop> will not return on its own. |
807 | count is nonzero, C<ev_loop> will not return on its own. |
796 | |
808 | |
797 | If you have a watcher you never unregister that should not keep C<ev_loop> |
809 | This is useful when you have a watcher that you never intend to |
798 | from returning, call ev_unref() after starting, and ev_ref() before |
810 | unregister, but that nevertheless should not keep C<ev_loop> from |
|
|
811 | returning. In such a case, call C<ev_unref> after starting, and C<ev_ref> |
799 | stopping it. |
812 | before stopping it. |
800 | |
813 | |
801 | As an example, libev itself uses this for its internal signal pipe: It |
814 | As an example, libev itself uses this for its internal signal pipe: It |
802 | is not visible to the libev user and should not keep C<ev_loop> from |
815 | is not visible to the libev user and should not keep C<ev_loop> from |
803 | exiting if no event watchers registered by it are active. It is also an |
816 | exiting if no event watchers registered by it are active. It is also an |
804 | excellent way to do this for generic recurring timers or from within |
817 | excellent way to do this for generic recurring timers or from within |
… | |
… | |
861 | usually doesn't make much sense to set it to a lower value than C<0.01>, |
874 | usually doesn't make much sense to set it to a lower value than C<0.01>, |
862 | as this approaches the timing granularity of most systems. Note that if |
875 | as this approaches the timing granularity of most systems. Note that if |
863 | you do transactions with the outside world and you can't increase the |
876 | you do transactions with the outside world and you can't increase the |
864 | parallelity, then this setting will limit your transaction rate (if you |
877 | parallelity, then this setting will limit your transaction rate (if you |
865 | need to poll once per transaction and the I/O collect interval is 0.01, |
878 | need to poll once per transaction and the I/O collect interval is 0.01, |
866 | then you can't do more than 100 transations per second). |
879 | then you can't do more than 100 transactions per second). |
867 | |
880 | |
868 | Setting the I<timeout collect interval> can improve the opportunity for |
881 | Setting the I<timeout collect interval> can improve the opportunity for |
869 | saving power, as the program will "bundle" timer callback invocations that |
882 | saving power, as the program will "bundle" timer callback invocations that |
870 | are "near" in time together, by delaying some, thus reducing the number of |
883 | are "near" in time together, by delaying some, thus reducing the number of |
871 | times the process sleeps and wakes up again. Another useful technique to |
884 | times the process sleeps and wakes up again. Another useful technique to |
… | |
… | |
941 | These two functions can be used to associate arbitrary data with a loop, |
954 | These two functions can be used to associate arbitrary data with a loop, |
942 | and are intended solely for the C<invoke_pending_cb>, C<release> and |
955 | and are intended solely for the C<invoke_pending_cb>, C<release> and |
943 | C<acquire> callbacks described above, but of course can be (ab-)used for |
956 | C<acquire> callbacks described above, but of course can be (ab-)used for |
944 | any other purpose as well. |
957 | any other purpose as well. |
945 | |
958 | |
946 | =item ev_loop_verify (loop) |
959 | =item ev_verify (loop) |
947 | |
960 | |
948 | This function only does something when C<EV_VERIFY> support has been |
961 | This function only does something when C<EV_VERIFY> support has been |
949 | compiled in, which is the default for non-minimal builds. It tries to go |
962 | compiled in, which is the default for non-minimal builds. It tries to go |
950 | through all internal structures and checks them for validity. If anything |
963 | through all internal structures and checks them for validity. If anything |
951 | is found to be inconsistent, it will print an error message to standard |
964 | is found to be inconsistent, it will print an error message to standard |
… | |
… | |
1026 | =item C<EV_WRITE> |
1039 | =item C<EV_WRITE> |
1027 | |
1040 | |
1028 | The file descriptor in the C<ev_io> watcher has become readable and/or |
1041 | The file descriptor in the C<ev_io> watcher has become readable and/or |
1029 | writable. |
1042 | writable. |
1030 | |
1043 | |
1031 | =item C<EV_TIMEOUT> |
1044 | =item C<EV_TIMER> |
1032 | |
1045 | |
1033 | The C<ev_timer> watcher has timed out. |
1046 | The C<ev_timer> watcher has timed out. |
1034 | |
1047 | |
1035 | =item C<EV_PERIODIC> |
1048 | =item C<EV_PERIODIC> |
1036 | |
1049 | |
… | |
… | |
1369 | |
1382 | |
1370 | For example, to emulate how many other event libraries handle priorities, |
1383 | For example, to emulate how many other event libraries handle priorities, |
1371 | you can associate an C<ev_idle> watcher to each such watcher, and in |
1384 | you can associate an C<ev_idle> watcher to each such watcher, and in |
1372 | the normal watcher callback, you just start the idle watcher. The real |
1385 | the normal watcher callback, you just start the idle watcher. The real |
1373 | processing is done in the idle watcher callback. This causes libev to |
1386 | processing is done in the idle watcher callback. This causes libev to |
1374 | continously poll and process kernel event data for the watcher, but when |
1387 | continuously poll and process kernel event data for the watcher, but when |
1375 | the lock-out case is known to be rare (which in turn is rare :), this is |
1388 | the lock-out case is known to be rare (which in turn is rare :), this is |
1376 | workable. |
1389 | workable. |
1377 | |
1390 | |
1378 | Usually, however, the lock-out model implemented that way will perform |
1391 | Usually, however, the lock-out model implemented that way will perform |
1379 | miserably under the type of load it was designed to handle. In that case, |
1392 | miserably under the type of load it was designed to handle. In that case, |
… | |
… | |
1393 | { |
1406 | { |
1394 | // stop the I/O watcher, we received the event, but |
1407 | // stop the I/O watcher, we received the event, but |
1395 | // are not yet ready to handle it. |
1408 | // are not yet ready to handle it. |
1396 | ev_io_stop (EV_A_ w); |
1409 | ev_io_stop (EV_A_ w); |
1397 | |
1410 | |
1398 | // start the idle watcher to ahndle the actual event. |
1411 | // start the idle watcher to handle the actual event. |
1399 | // it will not be executed as long as other watchers |
1412 | // it will not be executed as long as other watchers |
1400 | // with the default priority are receiving events. |
1413 | // with the default priority are receiving events. |
1401 | ev_idle_start (EV_A_ &idle); |
1414 | ev_idle_start (EV_A_ &idle); |
1402 | } |
1415 | } |
1403 | |
1416 | |
… | |
… | |
1457 | |
1470 | |
1458 | If you cannot use non-blocking mode, then force the use of a |
1471 | If you cannot use non-blocking mode, then force the use of a |
1459 | known-to-be-good backend (at the time of this writing, this includes only |
1472 | known-to-be-good backend (at the time of this writing, this includes only |
1460 | C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>). The same applies to file |
1473 | C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>). The same applies to file |
1461 | descriptors for which non-blocking operation makes no sense (such as |
1474 | descriptors for which non-blocking operation makes no sense (such as |
1462 | files) - libev doesn't guarentee any specific behaviour in that case. |
1475 | files) - libev doesn't guarantee any specific behaviour in that case. |
1463 | |
1476 | |
1464 | Another thing you have to watch out for is that it is quite easy to |
1477 | Another thing you have to watch out for is that it is quite easy to |
1465 | receive "spurious" readiness notifications, that is your callback might |
1478 | receive "spurious" readiness notifications, that is your callback might |
1466 | be called with C<EV_READ> but a subsequent C<read>(2) will actually block |
1479 | be called with C<EV_READ> but a subsequent C<read>(2) will actually block |
1467 | because there is no data. Not only are some backends known to create a |
1480 | because there is no data. Not only are some backends known to create a |
… | |
… | |
1532 | |
1545 | |
1533 | So when you encounter spurious, unexplained daemon exits, make sure you |
1546 | So when you encounter spurious, unexplained daemon exits, make sure you |
1534 | ignore SIGPIPE (and maybe make sure you log the exit status of your daemon |
1547 | ignore SIGPIPE (and maybe make sure you log the exit status of your daemon |
1535 | somewhere, as that would have given you a big clue). |
1548 | somewhere, as that would have given you a big clue). |
1536 | |
1549 | |
|
|
1550 | =head3 The special problem of accept()ing when you can't |
|
|
1551 | |
|
|
1552 | Many implementations of the POSIX C<accept> function (for example, |
|
|
1553 | found in post-2004 Linux) have the peculiar behaviour of not removing a |
|
|
1554 | connection from the pending queue in all error cases. |
|
|
1555 | |
|
|
1556 | For example, larger servers often run out of file descriptors (because |
|
|
1557 | of resource limits), causing C<accept> to fail with C<ENFILE> but not |
|
|
1558 | rejecting the connection, leading to libev signalling readiness on |
|
|
1559 | the next iteration again (the connection still exists after all), and |
|
|
1560 | typically causing the program to loop at 100% CPU usage. |
|
|
1561 | |
|
|
1562 | Unfortunately, the set of errors that cause this issue differs between |
|
|
1563 | operating systems, there is usually little the app can do to remedy the |
|
|
1564 | situation, and no known thread-safe method of removing the connection to |
|
|
1565 | cope with overload is known (to me). |
|
|
1566 | |
|
|
1567 | One of the easiest ways to handle this situation is to just ignore it |
|
|
1568 | - when the program encounters an overload, it will just loop until the |
|
|
1569 | situation is over. While this is a form of busy waiting, no OS offers an |
|
|
1570 | event-based way to handle this situation, so it's the best one can do. |
|
|
1571 | |
|
|
1572 | A better way to handle the situation is to log any errors other than |
|
|
1573 | C<EAGAIN> and C<EWOULDBLOCK>, making sure not to flood the log with such |
|
|
1574 | messages, and continue as usual, which at least gives the user an idea of |
|
|
1575 | what could be wrong ("raise the ulimit!"). For extra points one could stop |
|
|
1576 | the C<ev_io> watcher on the listening fd "for a while", which reduces CPU |
|
|
1577 | usage. |
|
|
1578 | |
|
|
1579 | If your program is single-threaded, then you could also keep a dummy file |
|
|
1580 | descriptor for overload situations (e.g. by opening F</dev/null>), and |
|
|
1581 | when you run into C<ENFILE> or C<EMFILE>, close it, run C<accept>, |
|
|
1582 | close that fd, and create a new dummy fd. This will gracefully refuse |
|
|
1583 | clients under typical overload conditions. |
|
|
1584 | |
|
|
1585 | The last way to handle it is to simply log the error and C<exit>, as |
|
|
1586 | is often done with C<malloc> failures, but this results in an easy |
|
|
1587 | opportunity for a DoS attack. |
1537 | |
1588 | |
1538 | =head3 Watcher-Specific Functions |
1589 | =head3 Watcher-Specific Functions |
1539 | |
1590 | |
1540 | =over 4 |
1591 | =over 4 |
1541 | |
1592 | |
… | |
… | |
1688 | ev_tstamp timeout = last_activity + 60.; |
1739 | ev_tstamp timeout = last_activity + 60.; |
1689 | |
1740 | |
1690 | // if last_activity + 60. is older than now, we did time out |
1741 | // if last_activity + 60. is older than now, we did time out |
1691 | if (timeout < now) |
1742 | if (timeout < now) |
1692 | { |
1743 | { |
1693 | // timeout occured, take action |
1744 | // timeout occurred, take action |
1694 | } |
1745 | } |
1695 | else |
1746 | else |
1696 | { |
1747 | { |
1697 | // callback was invoked, but there was some activity, re-arm |
1748 | // callback was invoked, but there was some activity, re-arm |
1698 | // the watcher to fire in last_activity + 60, which is |
1749 | // the watcher to fire in last_activity + 60, which is |
… | |
… | |
1720 | to the current time (meaning we just have some activity :), then call the |
1771 | to the current time (meaning we just have some activity :), then call the |
1721 | callback, which will "do the right thing" and start the timer: |
1772 | callback, which will "do the right thing" and start the timer: |
1722 | |
1773 | |
1723 | ev_init (timer, callback); |
1774 | ev_init (timer, callback); |
1724 | last_activity = ev_now (loop); |
1775 | last_activity = ev_now (loop); |
1725 | callback (loop, timer, EV_TIMEOUT); |
1776 | callback (loop, timer, EV_TIMER); |
1726 | |
1777 | |
1727 | And when there is some activity, simply store the current time in |
1778 | And when there is some activity, simply store the current time in |
1728 | C<last_activity>, no libev calls at all: |
1779 | C<last_activity>, no libev calls at all: |
1729 | |
1780 | |
1730 | last_actiivty = ev_now (loop); |
1781 | last_activity = ev_now (loop); |
1731 | |
1782 | |
1732 | This technique is slightly more complex, but in most cases where the |
1783 | This technique is slightly more complex, but in most cases where the |
1733 | time-out is unlikely to be triggered, much more efficient. |
1784 | time-out is unlikely to be triggered, much more efficient. |
1734 | |
1785 | |
1735 | Changing the timeout is trivial as well (if it isn't hard-coded in the |
1786 | Changing the timeout is trivial as well (if it isn't hard-coded in the |
… | |
… | |
1854 | C<repeat> value), or reset the running timer to the C<repeat> value. |
1905 | C<repeat> value), or reset the running timer to the C<repeat> value. |
1855 | |
1906 | |
1856 | This sounds a bit complicated, see L<Be smart about timeouts>, above, for a |
1907 | This sounds a bit complicated, see L<Be smart about timeouts>, above, for a |
1857 | usage example. |
1908 | usage example. |
1858 | |
1909 | |
1859 | =item ev_timer_remaining (loop, ev_timer *) |
1910 | =item ev_tstamp ev_timer_remaining (loop, ev_timer *) |
1860 | |
1911 | |
1861 | Returns the remaining time until a timer fires. If the timer is active, |
1912 | Returns the remaining time until a timer fires. If the timer is active, |
1862 | then this time is relative to the current event loop time, otherwise it's |
1913 | then this time is relative to the current event loop time, otherwise it's |
1863 | the timeout value currently configured. |
1914 | the timeout value currently configured. |
1864 | |
1915 | |
1865 | That is, after an C<ev_timer_set (w, 5, 7)>, C<ev_timer_remaining> returns |
1916 | That is, after an C<ev_timer_set (w, 5, 7)>, C<ev_timer_remaining> returns |
1866 | C<5>. When the timer is started and one second passes, C<ev_timer_remain> |
1917 | C<5>. When the timer is started and one second passes, C<ev_timer_remaining> |
1867 | will return C<4>. When the timer expires and is restarted, it will return |
1918 | will return C<4>. When the timer expires and is restarted, it will return |
1868 | roughly C<7> (likely slightly less as callback invocation takes some time, |
1919 | roughly C<7> (likely slightly less as callback invocation takes some time, |
1869 | too), and so on. |
1920 | too), and so on. |
1870 | |
1921 | |
1871 | =item ev_tstamp repeat [read-write] |
1922 | =item ev_tstamp repeat [read-write] |
… | |
… | |
2074 | Example: Call a callback every hour, or, more precisely, whenever the |
2125 | Example: Call a callback every hour, or, more precisely, whenever the |
2075 | system time is divisible by 3600. The callback invocation times have |
2126 | system time is divisible by 3600. The callback invocation times have |
2076 | potentially a lot of jitter, but good long-term stability. |
2127 | potentially a lot of jitter, but good long-term stability. |
2077 | |
2128 | |
2078 | static void |
2129 | static void |
2079 | clock_cb (struct ev_loop *loop, ev_io *w, int revents) |
2130 | clock_cb (struct ev_loop *loop, ev_periodic *w, int revents) |
2080 | { |
2131 | { |
2081 | ... its now a full hour (UTC, or TAI or whatever your clock follows) |
2132 | ... its now a full hour (UTC, or TAI or whatever your clock follows) |
2082 | } |
2133 | } |
2083 | |
2134 | |
2084 | ev_periodic hourly_tick; |
2135 | ev_periodic hourly_tick; |
… | |
… | |
2131 | C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should |
2182 | C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should |
2132 | not be unduly interrupted. If you have a problem with system calls getting |
2183 | not be unduly interrupted. If you have a problem with system calls getting |
2133 | interrupted by signals you can block all signals in an C<ev_check> watcher |
2184 | interrupted by signals you can block all signals in an C<ev_check> watcher |
2134 | and unblock them in an C<ev_prepare> watcher. |
2185 | and unblock them in an C<ev_prepare> watcher. |
2135 | |
2186 | |
2136 | =head3 The special problem of inheritance over execve |
2187 | =head3 The special problem of inheritance over fork/execve/pthread_create |
2137 | |
2188 | |
2138 | Both the signal mask (C<sigprocmask>) and the signal disposition |
2189 | Both the signal mask (C<sigprocmask>) and the signal disposition |
2139 | (C<sigaction>) are unspecified after starting a signal watcher (and after |
2190 | (C<sigaction>) are unspecified after starting a signal watcher (and after |
2140 | stopping it again), that is, libev might or might not block the signal, |
2191 | stopping it again), that is, libev might or might not block the signal, |
2141 | and might or might not set or restore the installed signal handler. |
2192 | and might or might not set or restore the installed signal handler. |
… | |
… | |
2151 | |
2202 | |
2152 | The simplest way to ensure that the signal mask is reset in the child is |
2203 | The simplest way to ensure that the signal mask is reset in the child is |
2153 | to install a fork handler with C<pthread_atfork> that resets it. That will |
2204 | to install a fork handler with C<pthread_atfork> that resets it. That will |
2154 | catch fork calls done by libraries (such as the libc) as well. |
2205 | catch fork calls done by libraries (such as the libc) as well. |
2155 | |
2206 | |
2156 | In current versions of libev, you can also ensure that the signal mask is |
2207 | In current versions of libev, the signal will not be blocked indefinitely |
2157 | not blocking any signals (except temporarily, so thread users watch out) |
2208 | unless you use the C<signalfd> API (C<EV_SIGNALFD>). While this reduces |
2158 | by specifying the C<EVFLAG_NOSIGFD> when creating the event loop. This |
2209 | the window of opportunity for problems, it will not go away, as libev |
2159 | is not guaranteed for future versions, however. |
2210 | I<has> to modify the signal mask, at least temporarily. |
|
|
2211 | |
|
|
2212 | So I can't stress this enough: I<If you do not reset your signal mask when |
|
|
2213 | you expect it to be empty, you have a race condition in your code>. This |
|
|
2214 | is not a libev-specific thing, this is true for most event libraries. |
2160 | |
2215 | |
2161 | =head3 Watcher-Specific Functions and Data Members |
2216 | =head3 Watcher-Specific Functions and Data Members |
2162 | |
2217 | |
2163 | =over 4 |
2218 | =over 4 |
2164 | |
2219 | |
… | |
… | |
2912 | C<ev_default_fork> cheats and calls it in the wrong process, the fork |
2967 | C<ev_default_fork> cheats and calls it in the wrong process, the fork |
2913 | handlers will be invoked, too, of course. |
2968 | handlers will be invoked, too, of course. |
2914 | |
2969 | |
2915 | =head3 The special problem of life after fork - how is it possible? |
2970 | =head3 The special problem of life after fork - how is it possible? |
2916 | |
2971 | |
2917 | Most uses of C<fork()> consist of forking, then some simple calls to ste |
2972 | Most uses of C<fork()> consist of forking, then some simple calls to set |
2918 | up/change the process environment, followed by a call to C<exec()>. This |
2973 | up/change the process environment, followed by a call to C<exec()>. This |
2919 | sequence should be handled by libev without any problems. |
2974 | sequence should be handled by libev without any problems. |
2920 | |
2975 | |
2921 | This changes when the application actually wants to do event handling |
2976 | This changes when the application actually wants to do event handling |
2922 | in the child, or both parent in child, in effect "continuing" after the |
2977 | in the child, or both parent in child, in effect "continuing" after the |
… | |
… | |
2956 | believe me. |
3011 | believe me. |
2957 | |
3012 | |
2958 | =back |
3013 | =back |
2959 | |
3014 | |
2960 | |
3015 | |
2961 | =head2 C<ev_async> - how to wake up another event loop |
3016 | =head2 C<ev_async> - how to wake up an event loop |
2962 | |
3017 | |
2963 | In general, you cannot use an C<ev_loop> from multiple threads or other |
3018 | In general, you cannot use an C<ev_loop> from multiple threads or other |
2964 | asynchronous sources such as signal handlers (as opposed to multiple event |
3019 | asynchronous sources such as signal handlers (as opposed to multiple event |
2965 | loops - those are of course safe to use in different threads). |
3020 | loops - those are of course safe to use in different threads). |
2966 | |
3021 | |
2967 | Sometimes, however, you need to wake up another event loop you do not |
3022 | Sometimes, however, you need to wake up an event loop you do not control, |
2968 | control, for example because it belongs to another thread. This is what |
3023 | for example because it belongs to another thread. This is what C<ev_async> |
2969 | C<ev_async> watchers do: as long as the C<ev_async> watcher is active, you |
3024 | watchers do: as long as the C<ev_async> watcher is active, you can signal |
2970 | can signal it by calling C<ev_async_send>, which is thread- and signal |
3025 | it by calling C<ev_async_send>, which is thread- and signal safe. |
2971 | safe. |
|
|
2972 | |
3026 | |
2973 | This functionality is very similar to C<ev_signal> watchers, as signals, |
3027 | This functionality is very similar to C<ev_signal> watchers, as signals, |
2974 | too, are asynchronous in nature, and signals, too, will be compressed |
3028 | too, are asynchronous in nature, and signals, too, will be compressed |
2975 | (i.e. the number of callback invocations may be less than the number of |
3029 | (i.e. the number of callback invocations may be less than the number of |
2976 | C<ev_async_sent> calls). |
3030 | C<ev_async_sent> calls). |
… | |
… | |
3131 | |
3185 | |
3132 | If C<timeout> is less than 0, then no timeout watcher will be |
3186 | If C<timeout> is less than 0, then no timeout watcher will be |
3133 | started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and |
3187 | started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and |
3134 | repeat = 0) will be started. C<0> is a valid timeout. |
3188 | repeat = 0) will be started. C<0> is a valid timeout. |
3135 | |
3189 | |
3136 | The callback has the type C<void (*cb)(int revents, void *arg)> and gets |
3190 | The callback has the type C<void (*cb)(int revents, void *arg)> and is |
3137 | passed an C<revents> set like normal event callbacks (a combination of |
3191 | passed an C<revents> set like normal event callbacks (a combination of |
3138 | C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg> |
3192 | C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMER>) and the C<arg> |
3139 | value passed to C<ev_once>. Note that it is possible to receive I<both> |
3193 | value passed to C<ev_once>. Note that it is possible to receive I<both> |
3140 | a timeout and an io event at the same time - you probably should give io |
3194 | a timeout and an io event at the same time - you probably should give io |
3141 | events precedence. |
3195 | events precedence. |
3142 | |
3196 | |
3143 | Example: wait up to ten seconds for data to appear on STDIN_FILENO. |
3197 | Example: wait up to ten seconds for data to appear on STDIN_FILENO. |
3144 | |
3198 | |
3145 | static void stdin_ready (int revents, void *arg) |
3199 | static void stdin_ready (int revents, void *arg) |
3146 | { |
3200 | { |
3147 | if (revents & EV_READ) |
3201 | if (revents & EV_READ) |
3148 | /* stdin might have data for us, joy! */; |
3202 | /* stdin might have data for us, joy! */; |
3149 | else if (revents & EV_TIMEOUT) |
3203 | else if (revents & EV_TIMER) |
3150 | /* doh, nothing entered */; |
3204 | /* doh, nothing entered */; |
3151 | } |
3205 | } |
3152 | |
3206 | |
3153 | ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
3207 | ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
3154 | |
3208 | |
… | |
… | |
3288 | myclass obj; |
3342 | myclass obj; |
3289 | ev::io iow; |
3343 | ev::io iow; |
3290 | iow.set <myclass, &myclass::io_cb> (&obj); |
3344 | iow.set <myclass, &myclass::io_cb> (&obj); |
3291 | |
3345 | |
3292 | =item w->set (object *) |
3346 | =item w->set (object *) |
3293 | |
|
|
3294 | This is an B<experimental> feature that might go away in a future version. |
|
|
3295 | |
3347 | |
3296 | This is a variation of a method callback - leaving out the method to call |
3348 | This is a variation of a method callback - leaving out the method to call |
3297 | will default the method to C<operator ()>, which makes it possible to use |
3349 | will default the method to C<operator ()>, which makes it possible to use |
3298 | functor objects without having to manually specify the C<operator ()> all |
3350 | functor objects without having to manually specify the C<operator ()> all |
3299 | the time. Incidentally, you can then also leave out the template argument |
3351 | the time. Incidentally, you can then also leave out the template argument |
… | |
… | |
3339 | Associates a different C<struct ev_loop> with this watcher. You can only |
3391 | Associates a different C<struct ev_loop> with this watcher. You can only |
3340 | do this when the watcher is inactive (and not pending either). |
3392 | do this when the watcher is inactive (and not pending either). |
3341 | |
3393 | |
3342 | =item w->set ([arguments]) |
3394 | =item w->set ([arguments]) |
3343 | |
3395 | |
3344 | Basically the same as C<ev_TYPE_set>, with the same arguments. Must be |
3396 | Basically the same as C<ev_TYPE_set>, with the same arguments. Either this |
3345 | called at least once. Unlike the C counterpart, an active watcher gets |
3397 | method or a suitable start method must be called at least once. Unlike the |
3346 | automatically stopped and restarted when reconfiguring it with this |
3398 | C counterpart, an active watcher gets automatically stopped and restarted |
3347 | method. |
3399 | when reconfiguring it with this method. |
3348 | |
3400 | |
3349 | =item w->start () |
3401 | =item w->start () |
3350 | |
3402 | |
3351 | Starts the watcher. Note that there is no C<loop> argument, as the |
3403 | Starts the watcher. Note that there is no C<loop> argument, as the |
3352 | constructor already stores the event loop. |
3404 | constructor already stores the event loop. |
3353 | |
3405 | |
|
|
3406 | =item w->start ([arguments]) |
|
|
3407 | |
|
|
3408 | Instead of calling C<set> and C<start> methods separately, it is often |
|
|
3409 | convenient to wrap them in one call. Uses the same type of arguments as |
|
|
3410 | the configure C<set> method of the watcher. |
|
|
3411 | |
3354 | =item w->stop () |
3412 | =item w->stop () |
3355 | |
3413 | |
3356 | Stops the watcher if it is active. Again, no C<loop> argument. |
3414 | Stops the watcher if it is active. Again, no C<loop> argument. |
3357 | |
3415 | |
3358 | =item w->again () (C<ev::timer>, C<ev::periodic> only) |
3416 | =item w->again () (C<ev::timer>, C<ev::periodic> only) |
… | |
… | |
3370 | |
3428 | |
3371 | =back |
3429 | =back |
3372 | |
3430 | |
3373 | =back |
3431 | =back |
3374 | |
3432 | |
3375 | Example: Define a class with an IO and idle watcher, start one of them in |
3433 | Example: Define a class with two I/O and idle watchers, start the I/O |
3376 | the constructor. |
3434 | watchers in the constructor. |
3377 | |
3435 | |
3378 | class myclass |
3436 | class myclass |
3379 | { |
3437 | { |
3380 | ev::io io ; void io_cb (ev::io &w, int revents); |
3438 | ev::io io ; void io_cb (ev::io &w, int revents); |
|
|
3439 | ev::io2 io2 ; void io2_cb (ev::io &w, int revents); |
3381 | ev::idle idle; void idle_cb (ev::idle &w, int revents); |
3440 | ev::idle idle; void idle_cb (ev::idle &w, int revents); |
3382 | |
3441 | |
3383 | myclass (int fd) |
3442 | myclass (int fd) |
3384 | { |
3443 | { |
3385 | io .set <myclass, &myclass::io_cb > (this); |
3444 | io .set <myclass, &myclass::io_cb > (this); |
|
|
3445 | io2 .set <myclass, &myclass::io2_cb > (this); |
3386 | idle.set <myclass, &myclass::idle_cb> (this); |
3446 | idle.set <myclass, &myclass::idle_cb> (this); |
3387 | |
3447 | |
3388 | io.start (fd, ev::READ); |
3448 | io.set (fd, ev::WRITE); // configure the watcher |
|
|
3449 | io.start (); // start it whenever convenient |
|
|
3450 | |
|
|
3451 | io2.start (fd, ev::READ); // set + start in one call |
3389 | } |
3452 | } |
3390 | }; |
3453 | }; |
3391 | |
3454 | |
3392 | |
3455 | |
3393 | =head1 OTHER LANGUAGE BINDINGS |
3456 | =head1 OTHER LANGUAGE BINDINGS |
… | |
… | |
3441 | Erkki Seppala has written Ocaml bindings for libev, to be found at |
3504 | Erkki Seppala has written Ocaml bindings for libev, to be found at |
3442 | L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>. |
3505 | L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>. |
3443 | |
3506 | |
3444 | =item Lua |
3507 | =item Lua |
3445 | |
3508 | |
3446 | Brian Maher has written a partial interface to libev |
3509 | Brian Maher has written a partial interface to libev for lua (at the |
3447 | for lua (only C<ev_io> and C<ev_timer>), to be found at |
3510 | time of this writing, only C<ev_io> and C<ev_timer>), to be found at |
3448 | L<http://github.com/brimworks/lua-ev>. |
3511 | L<http://github.com/brimworks/lua-ev>. |
3449 | |
3512 | |
3450 | =back |
3513 | =back |
3451 | |
3514 | |
3452 | |
3515 | |
… | |
… | |
3607 | libev.m4 |
3670 | libev.m4 |
3608 | |
3671 | |
3609 | =head2 PREPROCESSOR SYMBOLS/MACROS |
3672 | =head2 PREPROCESSOR SYMBOLS/MACROS |
3610 | |
3673 | |
3611 | Libev can be configured via a variety of preprocessor symbols you have to |
3674 | Libev can be configured via a variety of preprocessor symbols you have to |
3612 | define before including any of its files. The default in the absence of |
3675 | define before including (or compiling) any of its files. The default in |
3613 | autoconf is documented for every option. |
3676 | the absence of autoconf is documented for every option. |
|
|
3677 | |
|
|
3678 | Symbols marked with "(h)" do not change the ABI, and can have different |
|
|
3679 | values when compiling libev vs. including F<ev.h>, so it is permissible |
|
|
3680 | to redefine them before including F<ev.h> without breaking compatibility |
|
|
3681 | to a compiled library. All other symbols change the ABI, which means all |
|
|
3682 | users of libev and the libev code itself must be compiled with compatible |
|
|
3683 | settings. |
3614 | |
3684 | |
3615 | =over 4 |
3685 | =over 4 |
3616 | |
3686 | |
3617 | =item EV_STANDALONE |
3687 | =item EV_STANDALONE (h) |
3618 | |
3688 | |
3619 | Must always be C<1> if you do not use autoconf configuration, which |
3689 | Must always be C<1> if you do not use autoconf configuration, which |
3620 | keeps libev from including F<config.h>, and it also defines dummy |
3690 | keeps libev from including F<config.h>, and it also defines dummy |
3621 | implementations for some libevent functions (such as logging, which is not |
3691 | implementations for some libevent functions (such as logging, which is not |
3622 | supported). It will also not define any of the structs usually found in |
3692 | supported). It will also not define any of the structs usually found in |
… | |
… | |
3772 | as well as for signal and thread safety in C<ev_async> watchers. |
3842 | as well as for signal and thread safety in C<ev_async> watchers. |
3773 | |
3843 | |
3774 | In the absence of this define, libev will use C<sig_atomic_t volatile> |
3844 | In the absence of this define, libev will use C<sig_atomic_t volatile> |
3775 | (from F<signal.h>), which is usually good enough on most platforms. |
3845 | (from F<signal.h>), which is usually good enough on most platforms. |
3776 | |
3846 | |
3777 | =item EV_H |
3847 | =item EV_H (h) |
3778 | |
3848 | |
3779 | The name of the F<ev.h> header file used to include it. The default if |
3849 | The name of the F<ev.h> header file used to include it. The default if |
3780 | undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be |
3850 | undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be |
3781 | used to virtually rename the F<ev.h> header file in case of conflicts. |
3851 | used to virtually rename the F<ev.h> header file in case of conflicts. |
3782 | |
3852 | |
3783 | =item EV_CONFIG_H |
3853 | =item EV_CONFIG_H (h) |
3784 | |
3854 | |
3785 | If C<EV_STANDALONE> isn't C<1>, this variable can be used to override |
3855 | If C<EV_STANDALONE> isn't C<1>, this variable can be used to override |
3786 | F<ev.c>'s idea of where to find the F<config.h> file, similarly to |
3856 | F<ev.c>'s idea of where to find the F<config.h> file, similarly to |
3787 | C<EV_H>, above. |
3857 | C<EV_H>, above. |
3788 | |
3858 | |
3789 | =item EV_EVENT_H |
3859 | =item EV_EVENT_H (h) |
3790 | |
3860 | |
3791 | Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea |
3861 | Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea |
3792 | of how the F<event.h> header can be found, the default is C<"event.h">. |
3862 | of how the F<event.h> header can be found, the default is C<"event.h">. |
3793 | |
3863 | |
3794 | =item EV_PROTOTYPES |
3864 | =item EV_PROTOTYPES (h) |
3795 | |
3865 | |
3796 | If defined to be C<0>, then F<ev.h> will not define any function |
3866 | If defined to be C<0>, then F<ev.h> will not define any function |
3797 | prototypes, but still define all the structs and other symbols. This is |
3867 | prototypes, but still define all the structs and other symbols. This is |
3798 | occasionally useful if you want to provide your own wrapper functions |
3868 | occasionally useful if you want to provide your own wrapper functions |
3799 | around libev functions. |
3869 | around libev functions. |
… | |
… | |
3821 | fine. |
3891 | fine. |
3822 | |
3892 | |
3823 | If your embedding application does not need any priorities, defining these |
3893 | If your embedding application does not need any priorities, defining these |
3824 | both to C<0> will save some memory and CPU. |
3894 | both to C<0> will save some memory and CPU. |
3825 | |
3895 | |
3826 | =item EV_PERIODIC_ENABLE |
3896 | =item EV_PERIODIC_ENABLE, EV_IDLE_ENABLE, EV_EMBED_ENABLE, EV_STAT_ENABLE, |
|
|
3897 | EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE, |
|
|
3898 | EV_ASYNC_ENABLE, EV_CHILD_ENABLE. |
3827 | |
3899 | |
3828 | If undefined or defined to be C<1>, then periodic timers are supported. If |
3900 | If undefined or defined to be C<1> (and the platform supports it), then |
3829 | defined to be C<0>, then they are not. Disabling them saves a few kB of |
3901 | the respective watcher type is supported. If defined to be C<0>, then it |
3830 | code. |
3902 | is not. Disabling watcher types mainly saves code size. |
3831 | |
3903 | |
3832 | =item EV_IDLE_ENABLE |
3904 | =item EV_FEATURES |
3833 | |
|
|
3834 | If undefined or defined to be C<1>, then idle watchers are supported. If |
|
|
3835 | defined to be C<0>, then they are not. Disabling them saves a few kB of |
|
|
3836 | code. |
|
|
3837 | |
|
|
3838 | =item EV_EMBED_ENABLE |
|
|
3839 | |
|
|
3840 | If undefined or defined to be C<1>, then embed watchers are supported. If |
|
|
3841 | defined to be C<0>, then they are not. Embed watchers rely on most other |
|
|
3842 | watcher types, which therefore must not be disabled. |
|
|
3843 | |
|
|
3844 | =item EV_STAT_ENABLE |
|
|
3845 | |
|
|
3846 | If undefined or defined to be C<1>, then stat watchers are supported. If |
|
|
3847 | defined to be C<0>, then they are not. |
|
|
3848 | |
|
|
3849 | =item EV_FORK_ENABLE |
|
|
3850 | |
|
|
3851 | If undefined or defined to be C<1>, then fork watchers are supported. If |
|
|
3852 | defined to be C<0>, then they are not. |
|
|
3853 | |
|
|
3854 | =item EV_ASYNC_ENABLE |
|
|
3855 | |
|
|
3856 | If undefined or defined to be C<1>, then async watchers are supported. If |
|
|
3857 | defined to be C<0>, then they are not. |
|
|
3858 | |
|
|
3859 | =item EV_MINIMAL |
|
|
3860 | |
3905 | |
3861 | If you need to shave off some kilobytes of code at the expense of some |
3906 | If you need to shave off some kilobytes of code at the expense of some |
3862 | speed (but with the full API), define this symbol to C<1>. Currently this |
3907 | speed (but with the full API), you can define this symbol to request |
3863 | is used to override some inlining decisions, saves roughly 30% code size |
3908 | certain subsets of functionality. The default is to enable all features |
3864 | on amd64. It also selects a much smaller 2-heap for timer management over |
3909 | that can be enabled on the platform. |
3865 | the default 4-heap. |
|
|
3866 | |
3910 | |
3867 | You can save even more by disabling watcher types you do not need |
3911 | A typical way to use this symbol is to define it to C<0> (or to a bitset |
3868 | and setting C<EV_MAXPRI> == C<EV_MINPRI>. Also, disabling C<assert> |
3912 | with some broad features you want) and then selectively re-enable |
3869 | (C<-DNDEBUG>) will usually reduce code size a lot. |
3913 | additional parts you want, for example if you want everything minimal, |
|
|
3914 | but multiple event loop support, async and child watchers and the poll |
|
|
3915 | backend, use this: |
3870 | |
3916 | |
3871 | Defining C<EV_MINIMAL> to C<2> will additionally reduce the core API to |
3917 | #define EV_FEATURES 0 |
3872 | provide a bare-bones event library. See C<ev.h> for details on what parts |
3918 | #define EV_MULTIPLICITY 1 |
3873 | of the API are still available, and do not complain if this subset changes |
3919 | #define EV_USE_POLL 1 |
3874 | over time. |
3920 | #define EV_CHILD_ENABLE 1 |
|
|
3921 | #define EV_ASYNC_ENABLE 1 |
|
|
3922 | |
|
|
3923 | The actual value is a bitset, it can be a combination of the following |
|
|
3924 | values: |
|
|
3925 | |
|
|
3926 | =over 4 |
|
|
3927 | |
|
|
3928 | =item C<1> - faster/larger code |
|
|
3929 | |
|
|
3930 | Use larger code to speed up some operations. |
|
|
3931 | |
|
|
3932 | Currently this is used to override some inlining decisions (enlarging the |
|
|
3933 | code size by roughly 30% on amd64). |
|
|
3934 | |
|
|
3935 | When optimising for size, use of compiler flags such as C<-Os> with |
|
|
3936 | gcc is recommended, as well as C<-DNDEBUG>, as libev contains a number of |
|
|
3937 | assertions. |
|
|
3938 | |
|
|
3939 | =item C<2> - faster/larger data structures |
|
|
3940 | |
|
|
3941 | Replaces the small 2-heap for timer management by a faster 4-heap, larger |
|
|
3942 | hash table sizes and so on. This will usually further increase code size |
|
|
3943 | and can additionally have an effect on the size of data structures at |
|
|
3944 | runtime. |
|
|
3945 | |
|
|
3946 | =item C<4> - full API configuration |
|
|
3947 | |
|
|
3948 | This enables priorities (sets C<EV_MAXPRI>=2 and C<EV_MINPRI>=-2), and |
|
|
3949 | enables multiplicity (C<EV_MULTIPLICITY>=1). |
|
|
3950 | |
|
|
3951 | =item C<8> - full API |
|
|
3952 | |
|
|
3953 | This enables a lot of the "lesser used" API functions. See C<ev.h> for |
|
|
3954 | details on which parts of the API are still available without this |
|
|
3955 | feature, and do not complain if this subset changes over time. |
|
|
3956 | |
|
|
3957 | =item C<16> - enable all optional watcher types |
|
|
3958 | |
|
|
3959 | Enables all optional watcher types. If you want to selectively enable |
|
|
3960 | only some watcher types other than I/O and timers (e.g. prepare, |
|
|
3961 | embed, async, child...) you can enable them manually by defining |
|
|
3962 | C<EV_watchertype_ENABLE> to C<1> instead. |
|
|
3963 | |
|
|
3964 | =item C<32> - enable all backends |
|
|
3965 | |
|
|
3966 | This enables all backends - without this feature, you need to enable at |
|
|
3967 | least one backend manually (C<EV_USE_SELECT> is a good choice). |
|
|
3968 | |
|
|
3969 | =item C<64> - enable OS-specific "helper" APIs |
|
|
3970 | |
|
|
3971 | Enable inotify, eventfd, signalfd and similar OS-specific helper APIs by |
|
|
3972 | default. |
|
|
3973 | |
|
|
3974 | =back |
|
|
3975 | |
|
|
3976 | Compiling with C<gcc -Os -DEV_STANDALONE -DEV_USE_EPOLL=1 -DEV_FEATURES=0> |
|
|
3977 | reduces the compiled size of libev from 24.7Kb code/2.8Kb data to 6.5Kb |
|
|
3978 | code/0.3Kb data on my GNU/Linux amd64 system, while still giving you I/O |
|
|
3979 | watchers, timers and monotonic clock support. |
|
|
3980 | |
|
|
3981 | With an intelligent-enough linker (gcc+binutils are intelligent enough |
|
|
3982 | when you use C<-Wl,--gc-sections -ffunction-sections>) functions unused by |
|
|
3983 | your program might be left out as well - a binary starting a timer and an |
|
|
3984 | I/O watcher then might come out at only 5Kb. |
|
|
3985 | |
|
|
3986 | =item EV_AVOID_STDIO |
|
|
3987 | |
|
|
3988 | If this is set to C<1> at compiletime, then libev will avoid using stdio |
|
|
3989 | functions (printf, scanf, perror etc.). This will increase the code size |
|
|
3990 | somewhat, but if your program doesn't otherwise depend on stdio and your |
|
|
3991 | libc allows it, this avoids linking in the stdio library which is quite |
|
|
3992 | big. |
|
|
3993 | |
|
|
3994 | Note that error messages might become less precise when this option is |
|
|
3995 | enabled. |
3875 | |
3996 | |
3876 | =item EV_NSIG |
3997 | =item EV_NSIG |
3877 | |
3998 | |
3878 | The highest supported signal number, +1 (or, the number of |
3999 | The highest supported signal number, +1 (or, the number of |
3879 | signals): Normally, libev tries to deduce the maximum number of signals |
4000 | signals): Normally, libev tries to deduce the maximum number of signals |
3880 | automatically, but sometimes this fails, in which case it can be |
4001 | automatically, but sometimes this fails, in which case it can be |
3881 | specified. Also, using a lower number than detected (C<32> should be |
4002 | specified. Also, using a lower number than detected (C<32> should be |
3882 | good for about any system in existance) can save some memory, as libev |
4003 | good for about any system in existence) can save some memory, as libev |
3883 | statically allocates some 12-24 bytes per signal number. |
4004 | statically allocates some 12-24 bytes per signal number. |
3884 | |
4005 | |
3885 | =item EV_PID_HASHSIZE |
4006 | =item EV_PID_HASHSIZE |
3886 | |
4007 | |
3887 | C<ev_child> watchers use a small hash table to distribute workload by |
4008 | C<ev_child> watchers use a small hash table to distribute workload by |
3888 | pid. The default size is C<16> (or C<1> with C<EV_MINIMAL>), usually more |
4009 | pid. The default size is C<16> (or C<1> with C<EV_FEATURES> disabled), |
3889 | than enough. If you need to manage thousands of children you might want to |
4010 | usually more than enough. If you need to manage thousands of children you |
3890 | increase this value (I<must> be a power of two). |
4011 | might want to increase this value (I<must> be a power of two). |
3891 | |
4012 | |
3892 | =item EV_INOTIFY_HASHSIZE |
4013 | =item EV_INOTIFY_HASHSIZE |
3893 | |
4014 | |
3894 | C<ev_stat> watchers use a small hash table to distribute workload by |
4015 | C<ev_stat> watchers use a small hash table to distribute workload by |
3895 | inotify watch id. The default size is C<16> (or C<1> with C<EV_MINIMAL>), |
4016 | inotify watch id. The default size is C<16> (or C<1> with C<EV_FEATURES> |
3896 | usually more than enough. If you need to manage thousands of C<ev_stat> |
4017 | disabled), usually more than enough. If you need to manage thousands of |
3897 | watchers you might want to increase this value (I<must> be a power of |
4018 | C<ev_stat> watchers you might want to increase this value (I<must> be a |
3898 | two). |
4019 | power of two). |
3899 | |
4020 | |
3900 | =item EV_USE_4HEAP |
4021 | =item EV_USE_4HEAP |
3901 | |
4022 | |
3902 | Heaps are not very cache-efficient. To improve the cache-efficiency of the |
4023 | Heaps are not very cache-efficient. To improve the cache-efficiency of the |
3903 | timer and periodics heaps, libev uses a 4-heap when this symbol is defined |
4024 | timer and periodics heaps, libev uses a 4-heap when this symbol is defined |
3904 | to C<1>. The 4-heap uses more complicated (longer) code but has noticeably |
4025 | to C<1>. The 4-heap uses more complicated (longer) code but has noticeably |
3905 | faster performance with many (thousands) of watchers. |
4026 | faster performance with many (thousands) of watchers. |
3906 | |
4027 | |
3907 | The default is C<1> unless C<EV_MINIMAL> is set in which case it is C<0> |
4028 | The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it |
3908 | (disabled). |
4029 | will be C<0>. |
3909 | |
4030 | |
3910 | =item EV_HEAP_CACHE_AT |
4031 | =item EV_HEAP_CACHE_AT |
3911 | |
4032 | |
3912 | Heaps are not very cache-efficient. To improve the cache-efficiency of the |
4033 | Heaps are not very cache-efficient. To improve the cache-efficiency of the |
3913 | timer and periodics heaps, libev can cache the timestamp (I<at>) within |
4034 | timer and periodics heaps, libev can cache the timestamp (I<at>) within |
3914 | the heap structure (selected by defining C<EV_HEAP_CACHE_AT> to C<1>), |
4035 | the heap structure (selected by defining C<EV_HEAP_CACHE_AT> to C<1>), |
3915 | which uses 8-12 bytes more per watcher and a few hundred bytes more code, |
4036 | which uses 8-12 bytes more per watcher and a few hundred bytes more code, |
3916 | but avoids random read accesses on heap changes. This improves performance |
4037 | but avoids random read accesses on heap changes. This improves performance |
3917 | noticeably with many (hundreds) of watchers. |
4038 | noticeably with many (hundreds) of watchers. |
3918 | |
4039 | |
3919 | The default is C<1> unless C<EV_MINIMAL> is set in which case it is C<0> |
4040 | The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it |
3920 | (disabled). |
4041 | will be C<0>. |
3921 | |
4042 | |
3922 | =item EV_VERIFY |
4043 | =item EV_VERIFY |
3923 | |
4044 | |
3924 | Controls how much internal verification (see C<ev_loop_verify ()>) will |
4045 | Controls how much internal verification (see C<ev_verify ()>) will |
3925 | be done: If set to C<0>, no internal verification code will be compiled |
4046 | be done: If set to C<0>, no internal verification code will be compiled |
3926 | in. If set to C<1>, then verification code will be compiled in, but not |
4047 | in. If set to C<1>, then verification code will be compiled in, but not |
3927 | called. If set to C<2>, then the internal verification code will be |
4048 | called. If set to C<2>, then the internal verification code will be |
3928 | called once per loop, which can slow down libev. If set to C<3>, then the |
4049 | called once per loop, which can slow down libev. If set to C<3>, then the |
3929 | verification code will be called very frequently, which will slow down |
4050 | verification code will be called very frequently, which will slow down |
3930 | libev considerably. |
4051 | libev considerably. |
3931 | |
4052 | |
3932 | The default is C<1>, unless C<EV_MINIMAL> is set, in which case it will be |
4053 | The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it |
3933 | C<0>. |
4054 | will be C<0>. |
3934 | |
4055 | |
3935 | =item EV_COMMON |
4056 | =item EV_COMMON |
3936 | |
4057 | |
3937 | By default, all watchers have a C<void *data> member. By redefining |
4058 | By default, all watchers have a C<void *data> member. By redefining |
3938 | this macro to a something else you can include more and other types of |
4059 | this macro to something else you can include more and other types of |
3939 | members. You have to define it each time you include one of the files, |
4060 | members. You have to define it each time you include one of the files, |
3940 | though, and it must be identical each time. |
4061 | though, and it must be identical each time. |
3941 | |
4062 | |
3942 | For example, the perl EV module uses something like this: |
4063 | For example, the perl EV module uses something like this: |
3943 | |
4064 | |
… | |
… | |
3996 | file. |
4117 | file. |
3997 | |
4118 | |
3998 | The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file |
4119 | The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file |
3999 | that everybody includes and which overrides some configure choices: |
4120 | that everybody includes and which overrides some configure choices: |
4000 | |
4121 | |
4001 | #define EV_MINIMAL 1 |
4122 | #define EV_FEATURES 8 |
4002 | #define EV_USE_POLL 0 |
4123 | #define EV_USE_SELECT 1 |
4003 | #define EV_MULTIPLICITY 0 |
|
|
4004 | #define EV_PERIODIC_ENABLE 0 |
4124 | #define EV_PREPARE_ENABLE 1 |
|
|
4125 | #define EV_IDLE_ENABLE 1 |
4005 | #define EV_STAT_ENABLE 0 |
4126 | #define EV_SIGNAL_ENABLE 1 |
4006 | #define EV_FORK_ENABLE 0 |
4127 | #define EV_CHILD_ENABLE 1 |
|
|
4128 | #define EV_USE_STDEXCEPT 0 |
4007 | #define EV_CONFIG_H <config.h> |
4129 | #define EV_CONFIG_H <config.h> |
4008 | #define EV_MINPRI 0 |
|
|
4009 | #define EV_MAXPRI 0 |
|
|
4010 | |
4130 | |
4011 | #include "ev++.h" |
4131 | #include "ev++.h" |
4012 | |
4132 | |
4013 | And a F<ev_cpp.C> implementation file that contains libev proper and is compiled: |
4133 | And a F<ev_cpp.C> implementation file that contains libev proper and is compiled: |
4014 | |
4134 | |
… | |
… | |
4243 | maintainable. |
4363 | maintainable. |
4244 | |
4364 | |
4245 | And of course, some compiler warnings are just plain stupid, or simply |
4365 | And of course, some compiler warnings are just plain stupid, or simply |
4246 | wrong (because they don't actually warn about the condition their message |
4366 | wrong (because they don't actually warn about the condition their message |
4247 | seems to warn about). For example, certain older gcc versions had some |
4367 | seems to warn about). For example, certain older gcc versions had some |
4248 | warnings that resulted an extreme number of false positives. These have |
4368 | warnings that resulted in an extreme number of false positives. These have |
4249 | been fixed, but some people still insist on making code warn-free with |
4369 | been fixed, but some people still insist on making code warn-free with |
4250 | such buggy versions. |
4370 | such buggy versions. |
4251 | |
4371 | |
4252 | While libev is written to generate as few warnings as possible, |
4372 | While libev is written to generate as few warnings as possible, |
4253 | "warn-free" code is not a goal, and it is recommended not to build libev |
4373 | "warn-free" code is not a goal, and it is recommended not to build libev |
… | |
… | |
4289 | I suggest using suppression lists. |
4409 | I suggest using suppression lists. |
4290 | |
4410 | |
4291 | |
4411 | |
4292 | =head1 PORTABILITY NOTES |
4412 | =head1 PORTABILITY NOTES |
4293 | |
4413 | |
|
|
4414 | =head2 GNU/LINUX 32 BIT LIMITATIONS |
|
|
4415 | |
|
|
4416 | GNU/Linux is the only common platform that supports 64 bit file/large file |
|
|
4417 | interfaces but I<disables> them by default. |
|
|
4418 | |
|
|
4419 | That means that libev compiled in the default environment doesn't support |
|
|
4420 | files larger than 2GiB or so, which mainly affects C<ev_stat> watchers. |
|
|
4421 | |
|
|
4422 | Unfortunately, many programs try to work around this GNU/Linux issue |
|
|
4423 | by enabling the large file API, which makes them incompatible with the |
|
|
4424 | standard libev compiled for their system. |
|
|
4425 | |
|
|
4426 | Likewise, libev cannot enable the large file API itself as this would |
|
|
4427 | suddenly make it incompatible to the default compile time environment, |
|
|
4428 | i.e. all programs not using special compile switches. |
|
|
4429 | |
|
|
4430 | =head2 OS/X AND DARWIN BUGS |
|
|
4431 | |
|
|
4432 | The whole thing is a bug if you ask me - basically any system interface |
|
|
4433 | you touch is broken, whether it is locales, poll, kqueue or even the |
|
|
4434 | OpenGL drivers. |
|
|
4435 | |
|
|
4436 | =head3 C<kqueue> is buggy |
|
|
4437 | |
|
|
4438 | The kqueue syscall is broken in all known versions - most versions support |
|
|
4439 | only sockets, many support pipes. |
|
|
4440 | |
|
|
4441 | Libev tries to work around this by not using C<kqueue> by default on |
|
|
4442 | this rotten platform, but of course you can still ask for it when creating |
|
|
4443 | a loop. |
|
|
4444 | |
|
|
4445 | =head3 C<poll> is buggy |
|
|
4446 | |
|
|
4447 | Instead of fixing C<kqueue>, Apple replaced their (working) C<poll> |
|
|
4448 | implementation by something calling C<kqueue> internally around the 10.5.6 |
|
|
4449 | release, so now C<kqueue> I<and> C<poll> are broken. |
|
|
4450 | |
|
|
4451 | Libev tries to work around this by not using C<poll> by default on |
|
|
4452 | this rotten platform, but of course you can still ask for it when creating |
|
|
4453 | a loop. |
|
|
4454 | |
|
|
4455 | =head3 C<select> is buggy |
|
|
4456 | |
|
|
4457 | All that's left is C<select>, and of course Apple found a way to fuck this |
|
|
4458 | one up as well: On OS/X, C<select> actively limits the number of file |
|
|
4459 | descriptors you can pass in to 1024 - your program suddenly crashes when |
|
|
4460 | you use more. |
|
|
4461 | |
|
|
4462 | There is an undocumented "workaround" for this - defining |
|
|
4463 | C<_DARWIN_UNLIMITED_SELECT>, which libev tries to use, so select I<should> |
|
|
4464 | work on OS/X. |
|
|
4465 | |
|
|
4466 | =head2 SOLARIS PROBLEMS AND WORKAROUNDS |
|
|
4467 | |
|
|
4468 | =head3 C<errno> reentrancy |
|
|
4469 | |
|
|
4470 | The default compile environment on Solaris is unfortunately so |
|
|
4471 | thread-unsafe that you can't even use components/libraries compiled |
|
|
4472 | without C<-D_REENTRANT> (as long as they use C<errno>), which, of course, |
|
|
4473 | isn't defined by default. |
|
|
4474 | |
|
|
4475 | If you want to use libev in threaded environments you have to make sure |
|
|
4476 | it's compiled with C<_REENTRANT> defined. |
|
|
4477 | |
|
|
4478 | =head3 Event port backend |
|
|
4479 | |
|
|
4480 | The scalable event interface for Solaris is called "event ports". Unfortunately, |
|
|
4481 | this mechanism is very buggy. If you run into high CPU usage, your program |
|
|
4482 | freezes or you get a large number of spurious wakeups, make sure you have |
|
|
4483 | all the relevant and latest kernel patches applied. No, I don't know which |
|
|
4484 | ones, but there are multiple ones. |
|
|
4485 | |
|
|
4486 | If you can't get it to work, you can try running the program by setting |
|
|
4487 | the environment variable C<LIBEV_FLAGS=3> to only allow C<poll> and |
|
|
4488 | C<select> backends. |
|
|
4489 | |
|
|
4490 | =head2 AIX POLL BUG |
|
|
4491 | |
|
|
4492 | AIX unfortunately has a broken C<poll.h> header. Libev works around |
|
|
4493 | this by trying to avoid the poll backend altogether (i.e. it's not even |
|
|
4494 | compiled in), which normally isn't a big problem as C<select> works fine |
|
|
4495 | with large bitsets, and AIX is dead anyway. |
|
|
4496 | |
4294 | =head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS |
4497 | =head2 WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS |
|
|
4498 | |
|
|
4499 | =head3 General issues |
4295 | |
4500 | |
4296 | Win32 doesn't support any of the standards (e.g. POSIX) that libev |
4501 | Win32 doesn't support any of the standards (e.g. POSIX) that libev |
4297 | requires, and its I/O model is fundamentally incompatible with the POSIX |
4502 | requires, and its I/O model is fundamentally incompatible with the POSIX |
4298 | model. Libev still offers limited functionality on this platform in |
4503 | model. Libev still offers limited functionality on this platform in |
4299 | the form of the C<EVBACKEND_SELECT> backend, and only supports socket |
4504 | the form of the C<EVBACKEND_SELECT> backend, and only supports socket |
4300 | descriptors. This only applies when using Win32 natively, not when using |
4505 | descriptors. This only applies when using Win32 natively, not when using |
4301 | e.g. cygwin. |
4506 | e.g. cygwin. Actually, it only applies to the microsofts own compilers, |
|
|
4507 | as every compielr comes with a slightly differently broken/incompatible |
|
|
4508 | environment. |
4302 | |
4509 | |
4303 | Lifting these limitations would basically require the full |
4510 | Lifting these limitations would basically require the full |
4304 | re-implementation of the I/O system. If you are into these kinds of |
4511 | re-implementation of the I/O system. If you are into this kind of thing, |
4305 | things, then note that glib does exactly that for you in a very portable |
4512 | then note that glib does exactly that for you in a very portable way (note |
4306 | way (note also that glib is the slowest event library known to man). |
4513 | also that glib is the slowest event library known to man). |
4307 | |
4514 | |
4308 | There is no supported compilation method available on windows except |
4515 | There is no supported compilation method available on windows except |
4309 | embedding it into other applications. |
4516 | embedding it into other applications. |
4310 | |
4517 | |
4311 | Sensible signal handling is officially unsupported by Microsoft - libev |
4518 | Sensible signal handling is officially unsupported by Microsoft - libev |
… | |
… | |
4339 | you do I<not> compile the F<ev.c> or any other embedded source files!): |
4546 | you do I<not> compile the F<ev.c> or any other embedded source files!): |
4340 | |
4547 | |
4341 | #include "evwrap.h" |
4548 | #include "evwrap.h" |
4342 | #include "ev.c" |
4549 | #include "ev.c" |
4343 | |
4550 | |
4344 | =over 4 |
|
|
4345 | |
|
|
4346 | =item The winsocket select function |
4551 | =head3 The winsocket C<select> function |
4347 | |
4552 | |
4348 | The winsocket C<select> function doesn't follow POSIX in that it |
4553 | The winsocket C<select> function doesn't follow POSIX in that it |
4349 | requires socket I<handles> and not socket I<file descriptors> (it is |
4554 | requires socket I<handles> and not socket I<file descriptors> (it is |
4350 | also extremely buggy). This makes select very inefficient, and also |
4555 | also extremely buggy). This makes select very inefficient, and also |
4351 | requires a mapping from file descriptors to socket handles (the Microsoft |
4556 | requires a mapping from file descriptors to socket handles (the Microsoft |
… | |
… | |
4360 | #define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */ |
4565 | #define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */ |
4361 | |
4566 | |
4362 | Note that winsockets handling of fd sets is O(n), so you can easily get a |
4567 | Note that winsockets handling of fd sets is O(n), so you can easily get a |
4363 | complexity in the O(n²) range when using win32. |
4568 | complexity in the O(n²) range when using win32. |
4364 | |
4569 | |
4365 | =item Limited number of file descriptors |
4570 | =head3 Limited number of file descriptors |
4366 | |
4571 | |
4367 | Windows has numerous arbitrary (and low) limits on things. |
4572 | Windows has numerous arbitrary (and low) limits on things. |
4368 | |
4573 | |
4369 | Early versions of winsocket's select only supported waiting for a maximum |
4574 | Early versions of winsocket's select only supported waiting for a maximum |
4370 | of C<64> handles (probably owning to the fact that all windows kernels |
4575 | of C<64> handles (probably owning to the fact that all windows kernels |
… | |
… | |
4385 | runtime libraries. This might get you to about C<512> or C<2048> sockets |
4590 | runtime libraries. This might get you to about C<512> or C<2048> sockets |
4386 | (depending on windows version and/or the phase of the moon). To get more, |
4591 | (depending on windows version and/or the phase of the moon). To get more, |
4387 | you need to wrap all I/O functions and provide your own fd management, but |
4592 | you need to wrap all I/O functions and provide your own fd management, but |
4388 | the cost of calling select (O(n²)) will likely make this unworkable. |
4593 | the cost of calling select (O(n²)) will likely make this unworkable. |
4389 | |
4594 | |
4390 | =back |
|
|
4391 | |
|
|
4392 | =head2 PORTABILITY REQUIREMENTS |
4595 | =head2 PORTABILITY REQUIREMENTS |
4393 | |
4596 | |
4394 | In addition to a working ISO-C implementation and of course the |
4597 | In addition to a working ISO-C implementation and of course the |
4395 | backend-specific APIs, libev relies on a few additional extensions: |
4598 | backend-specific APIs, libev relies on a few additional extensions: |
4396 | |
4599 | |
… | |
… | |
4434 | watchers. |
4637 | watchers. |
4435 | |
4638 | |
4436 | =item C<double> must hold a time value in seconds with enough accuracy |
4639 | =item C<double> must hold a time value in seconds with enough accuracy |
4437 | |
4640 | |
4438 | The type C<double> is used to represent timestamps. It is required to |
4641 | The type C<double> is used to represent timestamps. It is required to |
4439 | have at least 51 bits of mantissa (and 9 bits of exponent), which is good |
4642 | have at least 51 bits of mantissa (and 9 bits of exponent), which is |
4440 | enough for at least into the year 4000. This requirement is fulfilled by |
4643 | good enough for at least into the year 4000 with millisecond accuracy |
|
|
4644 | (the design goal for libev). This requirement is overfulfilled by |
4441 | implementations implementing IEEE 754, which is basically all existing |
4645 | implementations using IEEE 754, which is basically all existing ones. With |
4442 | ones. With IEEE 754 doubles, you get microsecond accuracy until at least |
4646 | IEEE 754 doubles, you get microsecond accuracy until at least 2200. |
4443 | 2200. |
|
|
4444 | |
4647 | |
4445 | =back |
4648 | =back |
4446 | |
4649 | |
4447 | If you know of other additional requirements drop me a note. |
4650 | If you know of other additional requirements drop me a note. |
4448 | |
4651 | |
… | |
… | |
4516 | involves iterating over all running async watchers or all signal numbers. |
4719 | involves iterating over all running async watchers or all signal numbers. |
4517 | |
4720 | |
4518 | =back |
4721 | =back |
4519 | |
4722 | |
4520 | |
4723 | |
|
|
4724 | =head1 PORTING FROM LIBEV 3.X TO 4.X |
|
|
4725 | |
|
|
4726 | The major version 4 introduced some minor incompatible changes to the API. |
|
|
4727 | |
|
|
4728 | At the moment, the C<ev.h> header file tries to implement superficial |
|
|
4729 | compatibility, so most programs should still compile. Those might be |
|
|
4730 | removed in later versions of libev, so better update early than late. |
|
|
4731 | |
|
|
4732 | =over 4 |
|
|
4733 | |
|
|
4734 | =item C<ev_loop_count> renamed to C<ev_iteration> |
|
|
4735 | |
|
|
4736 | =item C<ev_loop_depth> renamed to C<ev_depth> |
|
|
4737 | |
|
|
4738 | =item C<ev_loop_verify> renamed to C<ev_verify> |
|
|
4739 | |
|
|
4740 | Most functions working on C<struct ev_loop> objects don't have an |
|
|
4741 | C<ev_loop_> prefix, so it was removed. Note that C<ev_loop_fork> is |
|
|
4742 | still called C<ev_loop_fork> because it would otherwise clash with the |
|
|
4743 | C<ev_fork> typedef. |
|
|
4744 | |
|
|
4745 | =item C<EV_TIMEOUT> renamed to C<EV_TIMER> in C<revents> |
|
|
4746 | |
|
|
4747 | This is a simple rename - all other watcher types use their name |
|
|
4748 | as revents flag, and now C<ev_timer> does, too. |
|
|
4749 | |
|
|
4750 | Both C<EV_TIMER> and C<EV_TIMEOUT> symbols were present in 3.x versions |
|
|
4751 | and continue to be present for the foreseeable future, so this is mostly a |
|
|
4752 | documentation change. |
|
|
4753 | |
|
|
4754 | =item C<EV_MINIMAL> mechanism replaced by C<EV_FEATURES> |
|
|
4755 | |
|
|
4756 | The preprocessor symbol C<EV_MINIMAL> has been replaced by a different |
|
|
4757 | mechanism, C<EV_FEATURES>. Programs using C<EV_MINIMAL> usually compile |
|
|
4758 | and work, but the library code will of course be larger. |
|
|
4759 | |
|
|
4760 | =back |
|
|
4761 | |
|
|
4762 | |
4521 | =head1 GLOSSARY |
4763 | =head1 GLOSSARY |
4522 | |
4764 | |
4523 | =over 4 |
4765 | =over 4 |
4524 | |
4766 | |
4525 | =item active |
4767 | =item active |
… | |
… | |
4546 | A change of state of some external event, such as data now being available |
4788 | A change of state of some external event, such as data now being available |
4547 | for reading on a file descriptor, time having passed or simply not having |
4789 | for reading on a file descriptor, time having passed or simply not having |
4548 | any other events happening anymore. |
4790 | any other events happening anymore. |
4549 | |
4791 | |
4550 | In libev, events are represented as single bits (such as C<EV_READ> or |
4792 | In libev, events are represented as single bits (such as C<EV_READ> or |
4551 | C<EV_TIMEOUT>). |
4793 | C<EV_TIMER>). |
4552 | |
4794 | |
4553 | =item event library |
4795 | =item event library |
4554 | |
4796 | |
4555 | A software package implementing an event model and loop. |
4797 | A software package implementing an event model and loop. |
4556 | |
4798 | |