… | |
… | |
58 | ev_timer_start (loop, &timeout_watcher); |
58 | ev_timer_start (loop, &timeout_watcher); |
59 | |
59 | |
60 | // now wait for events to arrive |
60 | // now wait for events to arrive |
61 | ev_run (loop, 0); |
61 | ev_run (loop, 0); |
62 | |
62 | |
63 | // unloop was called, so exit |
63 | // break was called, so exit |
64 | return 0; |
64 | return 0; |
65 | } |
65 | } |
66 | |
66 | |
67 | =head1 ABOUT THIS DOCUMENT |
67 | =head1 ABOUT THIS DOCUMENT |
68 | |
68 | |
… | |
… | |
174 | =item ev_tstamp ev_time () |
174 | =item ev_tstamp ev_time () |
175 | |
175 | |
176 | Returns the current time as libev would use it. Please note that the |
176 | Returns the current time as libev would use it. Please note that the |
177 | C<ev_now> function is usually faster and also often returns the timestamp |
177 | C<ev_now> function is usually faster and also often returns the timestamp |
178 | you actually want to know. Also interesting is the combination of |
178 | you actually want to know. Also interesting is the combination of |
179 | C<ev_update_now> and C<ev_now>. |
179 | C<ev_now_update> and C<ev_now>. |
180 | |
180 | |
181 | =item ev_sleep (ev_tstamp interval) |
181 | =item ev_sleep (ev_tstamp interval) |
182 | |
182 | |
183 | Sleep for the given interval: The current thread will be blocked until |
183 | Sleep for the given interval: The current thread will be blocked |
184 | either it is interrupted or the given time interval has passed. Basically |
184 | until either it is interrupted or the given time interval has |
|
|
185 | passed (approximately - it might return a bit earlier even if not |
|
|
186 | interrupted). Returns immediately if C<< interval <= 0 >>. |
|
|
187 | |
185 | this is a sub-second-resolution C<sleep ()>. |
188 | Basically this is a sub-second-resolution C<sleep ()>. |
|
|
189 | |
|
|
190 | The range of the C<interval> is limited - libev only guarantees to work |
|
|
191 | with sleep times of up to one day (C<< interval <= 86400 >>). |
186 | |
192 | |
187 | =item int ev_version_major () |
193 | =item int ev_version_major () |
188 | |
194 | |
189 | =item int ev_version_minor () |
195 | =item int ev_version_minor () |
190 | |
196 | |
… | |
… | |
241 | the current system, you would need to look at C<ev_embeddable_backends () |
247 | the current system, you would need to look at C<ev_embeddable_backends () |
242 | & ev_supported_backends ()>, likewise for recommended ones. |
248 | & ev_supported_backends ()>, likewise for recommended ones. |
243 | |
249 | |
244 | See the description of C<ev_embed> watchers for more info. |
250 | See the description of C<ev_embed> watchers for more info. |
245 | |
251 | |
246 | =item ev_set_allocator (void *(*cb)(void *ptr, long size)) |
252 | =item ev_set_allocator (void *(*cb)(void *ptr, long size) throw ()) |
247 | |
253 | |
248 | Sets the allocation function to use (the prototype is similar - the |
254 | Sets the allocation function to use (the prototype is similar - the |
249 | semantics are identical to the C<realloc> C89/SuS/POSIX function). It is |
255 | semantics are identical to the C<realloc> C89/SuS/POSIX function). It is |
250 | used to allocate and free memory (no surprises here). If it returns zero |
256 | used to allocate and free memory (no surprises here). If it returns zero |
251 | when memory needs to be allocated (C<size != 0>), the library might abort |
257 | when memory needs to be allocated (C<size != 0>), the library might abort |
… | |
… | |
277 | } |
283 | } |
278 | |
284 | |
279 | ... |
285 | ... |
280 | ev_set_allocator (persistent_realloc); |
286 | ev_set_allocator (persistent_realloc); |
281 | |
287 | |
282 | =item ev_set_syserr_cb (void (*cb)(const char *msg)) |
288 | =item ev_set_syserr_cb (void (*cb)(const char *msg) throw ()) |
283 | |
289 | |
284 | Set the callback function to call on a retryable system call error (such |
290 | Set the callback function to call on a retryable system call error (such |
285 | as failed select, poll, epoll_wait). The message is a printable string |
291 | as failed select, poll, epoll_wait). The message is a printable string |
286 | indicating the system call or subsystem causing the problem. If this |
292 | indicating the system call or subsystem causing the problem. If this |
287 | callback is set, then libev will expect it to remedy the situation, no |
293 | callback is set, then libev will expect it to remedy the situation, no |
… | |
… | |
435 | example) that can't properly initialise their signal masks. |
441 | example) that can't properly initialise their signal masks. |
436 | |
442 | |
437 | =item C<EVFLAG_NOSIGMASK> |
443 | =item C<EVFLAG_NOSIGMASK> |
438 | |
444 | |
439 | When this flag is specified, then libev will avoid to modify the signal |
445 | When this flag is specified, then libev will avoid to modify the signal |
440 | mask. Specifically, this means you ahve to make sure signals are unblocked |
446 | mask. Specifically, this means you have to make sure signals are unblocked |
441 | when you want to receive them. |
447 | when you want to receive them. |
442 | |
448 | |
443 | This behaviour is useful when you want to do your own signal handling, or |
449 | This behaviour is useful when you want to do your own signal handling, or |
444 | want to handle signals only in specific threads and want to avoid libev |
450 | want to handle signals only in specific threads and want to avoid libev |
445 | unblocking the signals. |
451 | unblocking the signals. |
|
|
452 | |
|
|
453 | It's also required by POSIX in a threaded program, as libev calls |
|
|
454 | C<sigprocmask>, whose behaviour is officially unspecified. |
446 | |
455 | |
447 | This flag's behaviour will become the default in future versions of libev. |
456 | This flag's behaviour will become the default in future versions of libev. |
448 | |
457 | |
449 | =item C<EVBACKEND_SELECT> (value 1, portable select backend) |
458 | =item C<EVBACKEND_SELECT> (value 1, portable select backend) |
450 | |
459 | |
… | |
… | |
480 | =item C<EVBACKEND_EPOLL> (value 4, Linux) |
489 | =item C<EVBACKEND_EPOLL> (value 4, Linux) |
481 | |
490 | |
482 | Use the linux-specific epoll(7) interface (for both pre- and post-2.6.9 |
491 | Use the linux-specific epoll(7) interface (for both pre- and post-2.6.9 |
483 | kernels). |
492 | kernels). |
484 | |
493 | |
485 | For few fds, this backend is a bit little slower than poll and select, |
494 | For few fds, this backend is a bit little slower than poll and select, but |
486 | but it scales phenomenally better. While poll and select usually scale |
495 | it scales phenomenally better. While poll and select usually scale like |
487 | like O(total_fds) where n is the total number of fds (or the highest fd), |
496 | O(total_fds) where total_fds is the total number of fds (or the highest |
488 | epoll scales either O(1) or O(active_fds). |
497 | fd), epoll scales either O(1) or O(active_fds). |
489 | |
498 | |
490 | The epoll mechanism deserves honorable mention as the most misdesigned |
499 | The epoll mechanism deserves honorable mention as the most misdesigned |
491 | of the more advanced event mechanisms: mere annoyances include silently |
500 | of the more advanced event mechanisms: mere annoyances include silently |
492 | dropping file descriptors, requiring a system call per change per file |
501 | dropping file descriptors, requiring a system call per change per file |
493 | descriptor (and unnecessary guessing of parameters), problems with dup, |
502 | descriptor (and unnecessary guessing of parameters), problems with dup, |
… | |
… | |
496 | 0.1ms) and so on. The biggest issue is fork races, however - if a program |
505 | 0.1ms) and so on. The biggest issue is fork races, however - if a program |
497 | forks then I<both> parent and child process have to recreate the epoll |
506 | forks then I<both> parent and child process have to recreate the epoll |
498 | set, which can take considerable time (one syscall per file descriptor) |
507 | set, which can take considerable time (one syscall per file descriptor) |
499 | and is of course hard to detect. |
508 | and is of course hard to detect. |
500 | |
509 | |
501 | Epoll is also notoriously buggy - embedding epoll fds I<should> work, but |
510 | Epoll is also notoriously buggy - embedding epoll fds I<should> work, |
502 | of course I<doesn't>, and epoll just loves to report events for totally |
511 | but of course I<doesn't>, and epoll just loves to report events for |
503 | I<different> file descriptors (even already closed ones, so one cannot |
512 | totally I<different> file descriptors (even already closed ones, so |
504 | even remove them from the set) than registered in the set (especially |
513 | one cannot even remove them from the set) than registered in the set |
505 | on SMP systems). Libev tries to counter these spurious notifications by |
514 | (especially on SMP systems). Libev tries to counter these spurious |
506 | employing an additional generation counter and comparing that against the |
515 | notifications by employing an additional generation counter and comparing |
507 | events to filter out spurious ones, recreating the set when required. Last |
516 | that against the events to filter out spurious ones, recreating the set |
|
|
517 | when required. Epoll also erroneously rounds down timeouts, but gives you |
|
|
518 | no way to know when and by how much, so sometimes you have to busy-wait |
|
|
519 | because epoll returns immediately despite a nonzero timeout. And last |
508 | not least, it also refuses to work with some file descriptors which work |
520 | not least, it also refuses to work with some file descriptors which work |
509 | perfectly fine with C<select> (files, many character devices...). |
521 | perfectly fine with C<select> (files, many character devices...). |
510 | |
522 | |
511 | Epoll is truly the train wreck analog among event poll mechanisms. |
523 | Epoll is truly the train wreck among event poll mechanisms, a frankenpoll, |
|
|
524 | cobbled together in a hurry, no thought to design or interaction with |
|
|
525 | others. Oh, the pain, will it ever stop... |
512 | |
526 | |
513 | While stopping, setting and starting an I/O watcher in the same iteration |
527 | While stopping, setting and starting an I/O watcher in the same iteration |
514 | will result in some caching, there is still a system call per such |
528 | will result in some caching, there is still a system call per such |
515 | incident (because the same I<file descriptor> could point to a different |
529 | incident (because the same I<file descriptor> could point to a different |
516 | I<file description> now), so its best to avoid that. Also, C<dup ()>'ed |
530 | I<file description> now), so its best to avoid that. Also, C<dup ()>'ed |
… | |
… | |
553 | |
567 | |
554 | It scales in the same way as the epoll backend, but the interface to the |
568 | It scales in the same way as the epoll backend, but the interface to the |
555 | kernel is more efficient (which says nothing about its actual speed, of |
569 | kernel is more efficient (which says nothing about its actual speed, of |
556 | course). While stopping, setting and starting an I/O watcher does never |
570 | course). While stopping, setting and starting an I/O watcher does never |
557 | cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to |
571 | cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to |
558 | two event changes per incident. Support for C<fork ()> is very bad (but |
572 | two event changes per incident. Support for C<fork ()> is very bad (you |
559 | sane, unlike epoll) and it drops fds silently in similarly hard-to-detect |
573 | might have to leak fd's on fork, but it's more sane than epoll) and it |
560 | cases |
574 | drops fds silently in similarly hard-to-detect cases |
561 | |
575 | |
562 | This backend usually performs well under most conditions. |
576 | This backend usually performs well under most conditions. |
563 | |
577 | |
564 | While nominally embeddable in other event loops, this doesn't work |
578 | While nominally embeddable in other event loops, this doesn't work |
565 | everywhere, so you might need to test for this. And since it is broken |
579 | everywhere, so you might need to test for this. And since it is broken |
… | |
… | |
594 | among the OS-specific backends (I vastly prefer correctness over speed |
608 | among the OS-specific backends (I vastly prefer correctness over speed |
595 | hacks). |
609 | hacks). |
596 | |
610 | |
597 | On the negative side, the interface is I<bizarre> - so bizarre that |
611 | On the negative side, the interface is I<bizarre> - so bizarre that |
598 | even sun itself gets it wrong in their code examples: The event polling |
612 | even sun itself gets it wrong in their code examples: The event polling |
599 | function sometimes returning events to the caller even though an error |
613 | function sometimes returns events to the caller even though an error |
600 | occured, but with no indication whether it has done so or not (yes, it's |
614 | occurred, but with no indication whether it has done so or not (yes, it's |
601 | even documented that way) - deadly for edge-triggered interfaces where |
615 | even documented that way) - deadly for edge-triggered interfaces where you |
602 | you absolutely have to know whether an event occured or not because you |
616 | absolutely have to know whether an event occurred or not because you have |
603 | have to re-arm the watcher. |
617 | to re-arm the watcher. |
604 | |
618 | |
605 | Fortunately libev seems to be able to work around these idiocies. |
619 | Fortunately libev seems to be able to work around these idiocies. |
606 | |
620 | |
607 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
621 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
608 | C<EVBACKEND_POLL>. |
622 | C<EVBACKEND_POLL>. |
… | |
… | |
778 | without a previous call to C<ev_suspend>. |
792 | without a previous call to C<ev_suspend>. |
779 | |
793 | |
780 | Calling C<ev_suspend>/C<ev_resume> has the side effect of updating the |
794 | Calling C<ev_suspend>/C<ev_resume> has the side effect of updating the |
781 | event loop time (see C<ev_now_update>). |
795 | event loop time (see C<ev_now_update>). |
782 | |
796 | |
783 | =item ev_run (loop, int flags) |
797 | =item bool ev_run (loop, int flags) |
784 | |
798 | |
785 | Finally, this is it, the event handler. This function usually is called |
799 | Finally, this is it, the event handler. This function usually is called |
786 | after you have initialised all your watchers and you want to start |
800 | after you have initialised all your watchers and you want to start |
787 | handling events. It will ask the operating system for any new events, call |
801 | handling events. It will ask the operating system for any new events, call |
788 | the watcher callbacks, an then repeat the whole process indefinitely: This |
802 | the watcher callbacks, and then repeat the whole process indefinitely: This |
789 | is why event loops are called I<loops>. |
803 | is why event loops are called I<loops>. |
790 | |
804 | |
791 | If the flags argument is specified as C<0>, it will keep handling events |
805 | If the flags argument is specified as C<0>, it will keep handling events |
792 | until either no event watchers are active anymore or C<ev_break> was |
806 | until either no event watchers are active anymore or C<ev_break> was |
793 | called. |
807 | called. |
|
|
808 | |
|
|
809 | The return value is false if there are no more active watchers (which |
|
|
810 | usually means "all jobs done" or "deadlock"), and true in all other cases |
|
|
811 | (which usually means " you should call C<ev_run> again"). |
794 | |
812 | |
795 | Please note that an explicit C<ev_break> is usually better than |
813 | Please note that an explicit C<ev_break> is usually better than |
796 | relying on all watchers to be stopped when deciding when a program has |
814 | relying on all watchers to be stopped when deciding when a program has |
797 | finished (especially in interactive programs), but having a program |
815 | finished (especially in interactive programs), but having a program |
798 | that automatically loops as long as it has to and no longer by virtue |
816 | that automatically loops as long as it has to and no longer by virtue |
799 | of relying on its watchers stopping correctly, that is truly a thing of |
817 | of relying on its watchers stopping correctly, that is truly a thing of |
800 | beauty. |
818 | beauty. |
801 | |
819 | |
802 | This function is also I<mostly> exception-safe - you can break out of |
820 | This function is I<mostly> exception-safe - you can break out of a |
803 | a C<ev_run> call by calling C<longjmp> in a callback, throwing a C++ |
821 | C<ev_run> call by calling C<longjmp> in a callback, throwing a C++ |
804 | exception and so on. This does not decrement the C<ev_depth> value, nor |
822 | exception and so on. This does not decrement the C<ev_depth> value, nor |
805 | will it clear any outstanding C<EVBREAK_ONE> breaks. |
823 | will it clear any outstanding C<EVBREAK_ONE> breaks. |
806 | |
824 | |
807 | A flags value of C<EVRUN_NOWAIT> will look for new events, will handle |
825 | A flags value of C<EVRUN_NOWAIT> will look for new events, will handle |
808 | those events and any already outstanding ones, but will not wait and |
826 | those events and any already outstanding ones, but will not wait and |
… | |
… | |
820 | This is useful if you are waiting for some external event in conjunction |
838 | This is useful if you are waiting for some external event in conjunction |
821 | with something not expressible using other libev watchers (i.e. "roll your |
839 | with something not expressible using other libev watchers (i.e. "roll your |
822 | own C<ev_run>"). However, a pair of C<ev_prepare>/C<ev_check> watchers is |
840 | own C<ev_run>"). However, a pair of C<ev_prepare>/C<ev_check> watchers is |
823 | usually a better approach for this kind of thing. |
841 | usually a better approach for this kind of thing. |
824 | |
842 | |
825 | Here are the gory details of what C<ev_run> does: |
843 | Here are the gory details of what C<ev_run> does (this is for your |
|
|
844 | understanding, not a guarantee that things will work exactly like this in |
|
|
845 | future versions): |
826 | |
846 | |
827 | - Increment loop depth. |
847 | - Increment loop depth. |
828 | - Reset the ev_break status. |
848 | - Reset the ev_break status. |
829 | - Before the first iteration, call any pending watchers. |
849 | - Before the first iteration, call any pending watchers. |
830 | LOOP: |
850 | LOOP: |
… | |
… | |
863 | anymore. |
883 | anymore. |
864 | |
884 | |
865 | ... queue jobs here, make sure they register event watchers as long |
885 | ... queue jobs here, make sure they register event watchers as long |
866 | ... as they still have work to do (even an idle watcher will do..) |
886 | ... as they still have work to do (even an idle watcher will do..) |
867 | ev_run (my_loop, 0); |
887 | ev_run (my_loop, 0); |
868 | ... jobs done or somebody called unloop. yeah! |
888 | ... jobs done or somebody called break. yeah! |
869 | |
889 | |
870 | =item ev_break (loop, how) |
890 | =item ev_break (loop, how) |
871 | |
891 | |
872 | Can be used to make a call to C<ev_run> return early (but only after it |
892 | Can be used to make a call to C<ev_run> return early (but only after it |
873 | has processed all outstanding events). The C<how> argument must be either |
893 | has processed all outstanding events). The C<how> argument must be either |
… | |
… | |
936 | overhead for the actual polling but can deliver many events at once. |
956 | overhead for the actual polling but can deliver many events at once. |
937 | |
957 | |
938 | By setting a higher I<io collect interval> you allow libev to spend more |
958 | By setting a higher I<io collect interval> you allow libev to spend more |
939 | time collecting I/O events, so you can handle more events per iteration, |
959 | time collecting I/O events, so you can handle more events per iteration, |
940 | at the cost of increasing latency. Timeouts (both C<ev_periodic> and |
960 | at the cost of increasing latency. Timeouts (both C<ev_periodic> and |
941 | C<ev_timer>) will be not affected. Setting this to a non-null value will |
961 | C<ev_timer>) will not be affected. Setting this to a non-null value will |
942 | introduce an additional C<ev_sleep ()> call into most loop iterations. The |
962 | introduce an additional C<ev_sleep ()> call into most loop iterations. The |
943 | sleep time ensures that libev will not poll for I/O events more often then |
963 | sleep time ensures that libev will not poll for I/O events more often then |
944 | once per this interval, on average. |
964 | once per this interval, on average (as long as the host time resolution is |
|
|
965 | good enough). |
945 | |
966 | |
946 | Likewise, by setting a higher I<timeout collect interval> you allow libev |
967 | Likewise, by setting a higher I<timeout collect interval> you allow libev |
947 | to spend more time collecting timeouts, at the expense of increased |
968 | to spend more time collecting timeouts, at the expense of increased |
948 | latency/jitter/inexactness (the watcher callback will be called |
969 | latency/jitter/inexactness (the watcher callback will be called |
949 | later). C<ev_io> watchers will not be affected. Setting this to a non-null |
970 | later). C<ev_io> watchers will not be affected. Setting this to a non-null |
… | |
… | |
995 | invoke the actual watchers inside another context (another thread etc.). |
1016 | invoke the actual watchers inside another context (another thread etc.). |
996 | |
1017 | |
997 | If you want to reset the callback, use C<ev_invoke_pending> as new |
1018 | If you want to reset the callback, use C<ev_invoke_pending> as new |
998 | callback. |
1019 | callback. |
999 | |
1020 | |
1000 | =item ev_set_loop_release_cb (loop, void (*release)(EV_P), void (*acquire)(EV_P)) |
1021 | =item ev_set_loop_release_cb (loop, void (*release)(EV_P) throw (), void (*acquire)(EV_P) throw ()) |
1001 | |
1022 | |
1002 | Sometimes you want to share the same loop between multiple threads. This |
1023 | Sometimes you want to share the same loop between multiple threads. This |
1003 | can be done relatively simply by putting mutex_lock/unlock calls around |
1024 | can be done relatively simply by putting mutex_lock/unlock calls around |
1004 | each call to a libev function. |
1025 | each call to a libev function. |
1005 | |
1026 | |
1006 | However, C<ev_run> can run an indefinite time, so it is not feasible |
1027 | However, C<ev_run> can run an indefinite time, so it is not feasible |
1007 | to wait for it to return. One way around this is to wake up the event |
1028 | to wait for it to return. One way around this is to wake up the event |
1008 | loop via C<ev_break> and C<av_async_send>, another way is to set these |
1029 | loop via C<ev_break> and C<ev_async_send>, another way is to set these |
1009 | I<release> and I<acquire> callbacks on the loop. |
1030 | I<release> and I<acquire> callbacks on the loop. |
1010 | |
1031 | |
1011 | When set, then C<release> will be called just before the thread is |
1032 | When set, then C<release> will be called just before the thread is |
1012 | suspended waiting for new events, and C<acquire> is called just |
1033 | suspended waiting for new events, and C<acquire> is called just |
1013 | afterwards. |
1034 | afterwards. |
… | |
… | |
1355 | See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related |
1376 | See also C<ev_feed_fd_event> and C<ev_feed_signal_event> for related |
1356 | functions that do not need a watcher. |
1377 | functions that do not need a watcher. |
1357 | |
1378 | |
1358 | =back |
1379 | =back |
1359 | |
1380 | |
1360 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
1381 | See also the L<ASSOCIATING CUSTOM DATA WITH A WATCHER> and L<BUILDING YOUR |
1361 | |
1382 | OWN COMPOSITE WATCHERS> idioms. |
1362 | Each watcher has, by default, a member C<void *data> that you can change |
|
|
1363 | and read at any time: libev will completely ignore it. This can be used |
|
|
1364 | to associate arbitrary data with your watcher. If you need more data and |
|
|
1365 | don't want to allocate memory and store a pointer to it in that data |
|
|
1366 | member, you can also "subclass" the watcher type and provide your own |
|
|
1367 | data: |
|
|
1368 | |
|
|
1369 | struct my_io |
|
|
1370 | { |
|
|
1371 | ev_io io; |
|
|
1372 | int otherfd; |
|
|
1373 | void *somedata; |
|
|
1374 | struct whatever *mostinteresting; |
|
|
1375 | }; |
|
|
1376 | |
|
|
1377 | ... |
|
|
1378 | struct my_io w; |
|
|
1379 | ev_io_init (&w.io, my_cb, fd, EV_READ); |
|
|
1380 | |
|
|
1381 | And since your callback will be called with a pointer to the watcher, you |
|
|
1382 | can cast it back to your own type: |
|
|
1383 | |
|
|
1384 | static void my_cb (struct ev_loop *loop, ev_io *w_, int revents) |
|
|
1385 | { |
|
|
1386 | struct my_io *w = (struct my_io *)w_; |
|
|
1387 | ... |
|
|
1388 | } |
|
|
1389 | |
|
|
1390 | More interesting and less C-conformant ways of casting your callback type |
|
|
1391 | instead have been omitted. |
|
|
1392 | |
|
|
1393 | Another common scenario is to use some data structure with multiple |
|
|
1394 | embedded watchers: |
|
|
1395 | |
|
|
1396 | struct my_biggy |
|
|
1397 | { |
|
|
1398 | int some_data; |
|
|
1399 | ev_timer t1; |
|
|
1400 | ev_timer t2; |
|
|
1401 | } |
|
|
1402 | |
|
|
1403 | In this case getting the pointer to C<my_biggy> is a bit more |
|
|
1404 | complicated: Either you store the address of your C<my_biggy> struct |
|
|
1405 | in the C<data> member of the watcher (for woozies), or you need to use |
|
|
1406 | some pointer arithmetic using C<offsetof> inside your watchers (for real |
|
|
1407 | programmers): |
|
|
1408 | |
|
|
1409 | #include <stddef.h> |
|
|
1410 | |
|
|
1411 | static void |
|
|
1412 | t1_cb (EV_P_ ev_timer *w, int revents) |
|
|
1413 | { |
|
|
1414 | struct my_biggy big = (struct my_biggy *) |
|
|
1415 | (((char *)w) - offsetof (struct my_biggy, t1)); |
|
|
1416 | } |
|
|
1417 | |
|
|
1418 | static void |
|
|
1419 | t2_cb (EV_P_ ev_timer *w, int revents) |
|
|
1420 | { |
|
|
1421 | struct my_biggy big = (struct my_biggy *) |
|
|
1422 | (((char *)w) - offsetof (struct my_biggy, t2)); |
|
|
1423 | } |
|
|
1424 | |
1383 | |
1425 | =head2 WATCHER STATES |
1384 | =head2 WATCHER STATES |
1426 | |
1385 | |
1427 | There are various watcher states mentioned throughout this manual - |
1386 | There are various watcher states mentioned throughout this manual - |
1428 | active, pending and so on. In this section these states and the rules to |
1387 | active, pending and so on. In this section these states and the rules to |
… | |
… | |
1431 | |
1390 | |
1432 | =over 4 |
1391 | =over 4 |
1433 | |
1392 | |
1434 | =item initialiased |
1393 | =item initialiased |
1435 | |
1394 | |
1436 | Before a watcher can be registered with the event looop it has to be |
1395 | Before a watcher can be registered with the event loop it has to be |
1437 | initialised. This can be done with a call to C<ev_TYPE_init>, or calls to |
1396 | initialised. This can be done with a call to C<ev_TYPE_init>, or calls to |
1438 | C<ev_init> followed by the watcher-specific C<ev_TYPE_set> function. |
1397 | C<ev_init> followed by the watcher-specific C<ev_TYPE_set> function. |
1439 | |
1398 | |
1440 | In this state it is simply some block of memory that is suitable for use |
1399 | In this state it is simply some block of memory that is suitable for |
1441 | in an event loop. It can be moved around, freed, reused etc. at will. |
1400 | use in an event loop. It can be moved around, freed, reused etc. at |
|
|
1401 | will - as long as you either keep the memory contents intact, or call |
|
|
1402 | C<ev_TYPE_init> again. |
1442 | |
1403 | |
1443 | =item started/running/active |
1404 | =item started/running/active |
1444 | |
1405 | |
1445 | Once a watcher has been started with a call to C<ev_TYPE_start> it becomes |
1406 | Once a watcher has been started with a call to C<ev_TYPE_start> it becomes |
1446 | property of the event loop, and is actively waiting for events. While in |
1407 | property of the event loop, and is actively waiting for events. While in |
… | |
… | |
1474 | latter will clear any pending state the watcher might be in, regardless |
1435 | latter will clear any pending state the watcher might be in, regardless |
1475 | of whether it was active or not, so stopping a watcher explicitly before |
1436 | of whether it was active or not, so stopping a watcher explicitly before |
1476 | freeing it is often a good idea. |
1437 | freeing it is often a good idea. |
1477 | |
1438 | |
1478 | While stopped (and not pending) the watcher is essentially in the |
1439 | While stopped (and not pending) the watcher is essentially in the |
1479 | initialised state, that is it can be reused, moved, modified in any way |
1440 | initialised state, that is, it can be reused, moved, modified in any way |
1480 | you wish. |
1441 | you wish (but when you trash the memory block, you need to C<ev_TYPE_init> |
|
|
1442 | it again). |
1481 | |
1443 | |
1482 | =back |
1444 | =back |
1483 | |
1445 | |
1484 | =head2 WATCHER PRIORITY MODELS |
1446 | =head2 WATCHER PRIORITY MODELS |
1485 | |
1447 | |
… | |
… | |
1614 | In general you can register as many read and/or write event watchers per |
1576 | In general you can register as many read and/or write event watchers per |
1615 | fd as you want (as long as you don't confuse yourself). Setting all file |
1577 | fd as you want (as long as you don't confuse yourself). Setting all file |
1616 | descriptors to non-blocking mode is also usually a good idea (but not |
1578 | descriptors to non-blocking mode is also usually a good idea (but not |
1617 | required if you know what you are doing). |
1579 | required if you know what you are doing). |
1618 | |
1580 | |
1619 | If you cannot use non-blocking mode, then force the use of a |
|
|
1620 | known-to-be-good backend (at the time of this writing, this includes only |
|
|
1621 | C<EVBACKEND_SELECT> and C<EVBACKEND_POLL>). The same applies to file |
|
|
1622 | descriptors for which non-blocking operation makes no sense (such as |
|
|
1623 | files) - libev doesn't guarantee any specific behaviour in that case. |
|
|
1624 | |
|
|
1625 | Another thing you have to watch out for is that it is quite easy to |
1581 | Another thing you have to watch out for is that it is quite easy to |
1626 | receive "spurious" readiness notifications, that is your callback might |
1582 | receive "spurious" readiness notifications, that is, your callback might |
1627 | be called with C<EV_READ> but a subsequent C<read>(2) will actually block |
1583 | be called with C<EV_READ> but a subsequent C<read>(2) will actually block |
1628 | because there is no data. Not only are some backends known to create a |
1584 | because there is no data. It is very easy to get into this situation even |
1629 | lot of those (for example Solaris ports), it is very easy to get into |
1585 | with a relatively standard program structure. Thus it is best to always |
1630 | this situation even with a relatively standard program structure. Thus |
1586 | use non-blocking I/O: An extra C<read>(2) returning C<EAGAIN> is far |
1631 | it is best to always use non-blocking I/O: An extra C<read>(2) returning |
|
|
1632 | C<EAGAIN> is far preferable to a program hanging until some data arrives. |
1587 | preferable to a program hanging until some data arrives. |
1633 | |
1588 | |
1634 | If you cannot run the fd in non-blocking mode (for example you should |
1589 | If you cannot run the fd in non-blocking mode (for example you should |
1635 | not play around with an Xlib connection), then you have to separately |
1590 | not play around with an Xlib connection), then you have to separately |
1636 | re-test whether a file descriptor is really ready with a known-to-be good |
1591 | re-test whether a file descriptor is really ready with a known-to-be good |
1637 | interface such as poll (fortunately in our Xlib example, Xlib already |
1592 | interface such as poll (fortunately in the case of Xlib, it already does |
1638 | does this on its own, so its quite safe to use). Some people additionally |
1593 | this on its own, so its quite safe to use). Some people additionally |
1639 | use C<SIGALRM> and an interval timer, just to be sure you won't block |
1594 | use C<SIGALRM> and an interval timer, just to be sure you won't block |
1640 | indefinitely. |
1595 | indefinitely. |
1641 | |
1596 | |
1642 | But really, best use non-blocking mode. |
1597 | But really, best use non-blocking mode. |
1643 | |
1598 | |
… | |
… | |
1671 | |
1626 | |
1672 | There is no workaround possible except not registering events |
1627 | There is no workaround possible except not registering events |
1673 | for potentially C<dup ()>'ed file descriptors, or to resort to |
1628 | for potentially C<dup ()>'ed file descriptors, or to resort to |
1674 | C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>. |
1629 | C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>. |
1675 | |
1630 | |
|
|
1631 | =head3 The special problem of files |
|
|
1632 | |
|
|
1633 | Many people try to use C<select> (or libev) on file descriptors |
|
|
1634 | representing files, and expect it to become ready when their program |
|
|
1635 | doesn't block on disk accesses (which can take a long time on their own). |
|
|
1636 | |
|
|
1637 | However, this cannot ever work in the "expected" way - you get a readiness |
|
|
1638 | notification as soon as the kernel knows whether and how much data is |
|
|
1639 | there, and in the case of open files, that's always the case, so you |
|
|
1640 | always get a readiness notification instantly, and your read (or possibly |
|
|
1641 | write) will still block on the disk I/O. |
|
|
1642 | |
|
|
1643 | Another way to view it is that in the case of sockets, pipes, character |
|
|
1644 | devices and so on, there is another party (the sender) that delivers data |
|
|
1645 | on its own, but in the case of files, there is no such thing: the disk |
|
|
1646 | will not send data on its own, simply because it doesn't know what you |
|
|
1647 | wish to read - you would first have to request some data. |
|
|
1648 | |
|
|
1649 | Since files are typically not-so-well supported by advanced notification |
|
|
1650 | mechanism, libev tries hard to emulate POSIX behaviour with respect |
|
|
1651 | to files, even though you should not use it. The reason for this is |
|
|
1652 | convenience: sometimes you want to watch STDIN or STDOUT, which is |
|
|
1653 | usually a tty, often a pipe, but also sometimes files or special devices |
|
|
1654 | (for example, C<epoll> on Linux works with F</dev/random> but not with |
|
|
1655 | F</dev/urandom>), and even though the file might better be served with |
|
|
1656 | asynchronous I/O instead of with non-blocking I/O, it is still useful when |
|
|
1657 | it "just works" instead of freezing. |
|
|
1658 | |
|
|
1659 | So avoid file descriptors pointing to files when you know it (e.g. use |
|
|
1660 | libeio), but use them when it is convenient, e.g. for STDIN/STDOUT, or |
|
|
1661 | when you rarely read from a file instead of from a socket, and want to |
|
|
1662 | reuse the same code path. |
|
|
1663 | |
1676 | =head3 The special problem of fork |
1664 | =head3 The special problem of fork |
1677 | |
1665 | |
1678 | Some backends (epoll, kqueue) do not support C<fork ()> at all or exhibit |
1666 | Some backends (epoll, kqueue) do not support C<fork ()> at all or exhibit |
1679 | useless behaviour. Libev fully supports fork, but needs to be told about |
1667 | useless behaviour. Libev fully supports fork, but needs to be told about |
1680 | it in the child. |
1668 | it in the child if you want to continue to use it in the child. |
1681 | |
1669 | |
1682 | To support fork in your programs, you either have to call |
1670 | To support fork in your child processes, you have to call C<ev_loop_fork |
1683 | C<ev_default_fork ()> or C<ev_loop_fork ()> after a fork in the child, |
1671 | ()> after a fork in the child, enable C<EVFLAG_FORKCHECK>, or resort to |
1684 | enable C<EVFLAG_FORKCHECK>, or resort to C<EVBACKEND_SELECT> or |
1672 | C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>. |
1685 | C<EVBACKEND_POLL>. |
|
|
1686 | |
1673 | |
1687 | =head3 The special problem of SIGPIPE |
1674 | =head3 The special problem of SIGPIPE |
1688 | |
1675 | |
1689 | While not really specific to libev, it is easy to forget about C<SIGPIPE>: |
1676 | While not really specific to libev, it is easy to forget about C<SIGPIPE>: |
1690 | when writing to a pipe whose other end has been closed, your program gets |
1677 | when writing to a pipe whose other end has been closed, your program gets |
… | |
… | |
1788 | detecting time jumps is hard, and some inaccuracies are unavoidable (the |
1775 | detecting time jumps is hard, and some inaccuracies are unavoidable (the |
1789 | monotonic clock option helps a lot here). |
1776 | monotonic clock option helps a lot here). |
1790 | |
1777 | |
1791 | The callback is guaranteed to be invoked only I<after> its timeout has |
1778 | The callback is guaranteed to be invoked only I<after> its timeout has |
1792 | passed (not I<at>, so on systems with very low-resolution clocks this |
1779 | passed (not I<at>, so on systems with very low-resolution clocks this |
1793 | might introduce a small delay). If multiple timers become ready during the |
1780 | might introduce a small delay, see "the special problem of being too |
|
|
1781 | early", below). If multiple timers become ready during the same loop |
1794 | same loop iteration then the ones with earlier time-out values are invoked |
1782 | iteration then the ones with earlier time-out values are invoked before |
1795 | before ones of the same priority with later time-out values (but this is |
1783 | ones of the same priority with later time-out values (but this is no |
1796 | no longer true when a callback calls C<ev_run> recursively). |
1784 | longer true when a callback calls C<ev_run> recursively). |
1797 | |
1785 | |
1798 | =head3 Be smart about timeouts |
1786 | =head3 Be smart about timeouts |
1799 | |
1787 | |
1800 | Many real-world problems involve some kind of timeout, usually for error |
1788 | Many real-world problems involve some kind of timeout, usually for error |
1801 | recovery. A typical example is an HTTP request - if the other side hangs, |
1789 | recovery. A typical example is an HTTP request - if the other side hangs, |
… | |
… | |
1876 | |
1864 | |
1877 | In this case, it would be more efficient to leave the C<ev_timer> alone, |
1865 | In this case, it would be more efficient to leave the C<ev_timer> alone, |
1878 | but remember the time of last activity, and check for a real timeout only |
1866 | but remember the time of last activity, and check for a real timeout only |
1879 | within the callback: |
1867 | within the callback: |
1880 | |
1868 | |
|
|
1869 | ev_tstamp timeout = 60.; |
1881 | ev_tstamp last_activity; // time of last activity |
1870 | ev_tstamp last_activity; // time of last activity |
|
|
1871 | ev_timer timer; |
1882 | |
1872 | |
1883 | static void |
1873 | static void |
1884 | callback (EV_P_ ev_timer *w, int revents) |
1874 | callback (EV_P_ ev_timer *w, int revents) |
1885 | { |
1875 | { |
1886 | ev_tstamp now = ev_now (EV_A); |
1876 | // calculate when the timeout would happen |
1887 | ev_tstamp timeout = last_activity + 60.; |
1877 | ev_tstamp after = last_activity - ev_now (EV_A) + timeout; |
1888 | |
1878 | |
1889 | // if last_activity + 60. is older than now, we did time out |
1879 | // if negative, it means we the timeout already occured |
1890 | if (timeout < now) |
1880 | if (after < 0.) |
1891 | { |
1881 | { |
1892 | // timeout occurred, take action |
1882 | // timeout occurred, take action |
1893 | } |
1883 | } |
1894 | else |
1884 | else |
1895 | { |
1885 | { |
1896 | // callback was invoked, but there was some activity, re-arm |
1886 | // callback was invoked, but there was some recent |
1897 | // the watcher to fire in last_activity + 60, which is |
1887 | // activity. simply restart the timer to time out |
1898 | // guaranteed to be in the future, so "again" is positive: |
1888 | // after "after" seconds, which is the earliest time |
1899 | w->repeat = timeout - now; |
1889 | // the timeout can occur. |
|
|
1890 | ev_timer_set (w, after, 0.); |
1900 | ev_timer_again (EV_A_ w); |
1891 | ev_timer_start (EV_A_ w); |
1901 | } |
1892 | } |
1902 | } |
1893 | } |
1903 | |
1894 | |
1904 | To summarise the callback: first calculate the real timeout (defined |
1895 | To summarise the callback: first calculate in how many seconds the |
1905 | as "60 seconds after the last activity"), then check if that time has |
1896 | timeout will occur (by calculating the absolute time when it would occur, |
1906 | been reached, which means something I<did>, in fact, time out. Otherwise |
1897 | C<last_activity + timeout>, and subtracting the current time, C<ev_now |
1907 | the callback was invoked too early (C<timeout> is in the future), so |
1898 | (EV_A)> from that). |
1908 | re-schedule the timer to fire at that future time, to see if maybe we have |
|
|
1909 | a timeout then. |
|
|
1910 | |
1899 | |
1911 | Note how C<ev_timer_again> is used, taking advantage of the |
1900 | If this value is negative, then we are already past the timeout, i.e. we |
1912 | C<ev_timer_again> optimisation when the timer is already running. |
1901 | timed out, and need to do whatever is needed in this case. |
|
|
1902 | |
|
|
1903 | Otherwise, we now the earliest time at which the timeout would trigger, |
|
|
1904 | and simply start the timer with this timeout value. |
|
|
1905 | |
|
|
1906 | In other words, each time the callback is invoked it will check whether |
|
|
1907 | the timeout cocured. If not, it will simply reschedule itself to check |
|
|
1908 | again at the earliest time it could time out. Rinse. Repeat. |
1913 | |
1909 | |
1914 | This scheme causes more callback invocations (about one every 60 seconds |
1910 | This scheme causes more callback invocations (about one every 60 seconds |
1915 | minus half the average time between activity), but virtually no calls to |
1911 | minus half the average time between activity), but virtually no calls to |
1916 | libev to change the timeout. |
1912 | libev to change the timeout. |
1917 | |
1913 | |
1918 | To start the timer, simply initialise the watcher and set C<last_activity> |
1914 | To start the machinery, simply initialise the watcher and set |
1919 | to the current time (meaning we just have some activity :), then call the |
1915 | C<last_activity> to the current time (meaning there was some activity just |
1920 | callback, which will "do the right thing" and start the timer: |
1916 | now), then call the callback, which will "do the right thing" and start |
|
|
1917 | the timer: |
1921 | |
1918 | |
|
|
1919 | last_activity = ev_now (EV_A); |
1922 | ev_init (timer, callback); |
1920 | ev_init (&timer, callback); |
1923 | last_activity = ev_now (loop); |
1921 | callback (EV_A_ &timer, 0); |
1924 | callback (loop, timer, EV_TIMER); |
|
|
1925 | |
1922 | |
1926 | And when there is some activity, simply store the current time in |
1923 | When there is some activity, simply store the current time in |
1927 | C<last_activity>, no libev calls at all: |
1924 | C<last_activity>, no libev calls at all: |
1928 | |
1925 | |
|
|
1926 | if (activity detected) |
1929 | last_activity = ev_now (loop); |
1927 | last_activity = ev_now (EV_A); |
|
|
1928 | |
|
|
1929 | When your timeout value changes, then the timeout can be changed by simply |
|
|
1930 | providing a new value, stopping the timer and calling the callback, which |
|
|
1931 | will agaion do the right thing (for example, time out immediately :). |
|
|
1932 | |
|
|
1933 | timeout = new_value; |
|
|
1934 | ev_timer_stop (EV_A_ &timer); |
|
|
1935 | callback (EV_A_ &timer, 0); |
1930 | |
1936 | |
1931 | This technique is slightly more complex, but in most cases where the |
1937 | This technique is slightly more complex, but in most cases where the |
1932 | time-out is unlikely to be triggered, much more efficient. |
1938 | time-out is unlikely to be triggered, much more efficient. |
1933 | |
|
|
1934 | Changing the timeout is trivial as well (if it isn't hard-coded in the |
|
|
1935 | callback :) - just change the timeout and invoke the callback, which will |
|
|
1936 | fix things for you. |
|
|
1937 | |
1939 | |
1938 | =item 4. Wee, just use a double-linked list for your timeouts. |
1940 | =item 4. Wee, just use a double-linked list for your timeouts. |
1939 | |
1941 | |
1940 | If there is not one request, but many thousands (millions...), all |
1942 | If there is not one request, but many thousands (millions...), all |
1941 | employing some kind of timeout with the same timeout value, then one can |
1943 | employing some kind of timeout with the same timeout value, then one can |
… | |
… | |
1968 | Method #1 is almost always a bad idea, and buys you nothing. Method #4 is |
1970 | Method #1 is almost always a bad idea, and buys you nothing. Method #4 is |
1969 | rather complicated, but extremely efficient, something that really pays |
1971 | rather complicated, but extremely efficient, something that really pays |
1970 | off after the first million or so of active timers, i.e. it's usually |
1972 | off after the first million or so of active timers, i.e. it's usually |
1971 | overkill :) |
1973 | overkill :) |
1972 | |
1974 | |
|
|
1975 | =head3 The special problem of being too early |
|
|
1976 | |
|
|
1977 | If you ask a timer to call your callback after three seconds, then |
|
|
1978 | you expect it to be invoked after three seconds - but of course, this |
|
|
1979 | cannot be guaranteed to infinite precision. Less obviously, it cannot be |
|
|
1980 | guaranteed to any precision by libev - imagine somebody suspending the |
|
|
1981 | process with a STOP signal for a few hours for example. |
|
|
1982 | |
|
|
1983 | So, libev tries to invoke your callback as soon as possible I<after> the |
|
|
1984 | delay has occurred, but cannot guarantee this. |
|
|
1985 | |
|
|
1986 | A less obvious failure mode is calling your callback too early: many event |
|
|
1987 | loops compare timestamps with a "elapsed delay >= requested delay", but |
|
|
1988 | this can cause your callback to be invoked much earlier than you would |
|
|
1989 | expect. |
|
|
1990 | |
|
|
1991 | To see why, imagine a system with a clock that only offers full second |
|
|
1992 | resolution (think windows if you can't come up with a broken enough OS |
|
|
1993 | yourself). If you schedule a one-second timer at the time 500.9, then the |
|
|
1994 | event loop will schedule your timeout to elapse at a system time of 500 |
|
|
1995 | (500.9 truncated to the resolution) + 1, or 501. |
|
|
1996 | |
|
|
1997 | If an event library looks at the timeout 0.1s later, it will see "501 >= |
|
|
1998 | 501" and invoke the callback 0.1s after it was started, even though a |
|
|
1999 | one-second delay was requested - this is being "too early", despite best |
|
|
2000 | intentions. |
|
|
2001 | |
|
|
2002 | This is the reason why libev will never invoke the callback if the elapsed |
|
|
2003 | delay equals the requested delay, but only when the elapsed delay is |
|
|
2004 | larger than the requested delay. In the example above, libev would only invoke |
|
|
2005 | the callback at system time 502, or 1.1s after the timer was started. |
|
|
2006 | |
|
|
2007 | So, while libev cannot guarantee that your callback will be invoked |
|
|
2008 | exactly when requested, it I<can> and I<does> guarantee that the requested |
|
|
2009 | delay has actually elapsed, or in other words, it always errs on the "too |
|
|
2010 | late" side of things. |
|
|
2011 | |
1973 | =head3 The special problem of time updates |
2012 | =head3 The special problem of time updates |
1974 | |
2013 | |
1975 | Establishing the current time is a costly operation (it usually takes at |
2014 | Establishing the current time is a costly operation (it usually takes |
1976 | least two system calls): EV therefore updates its idea of the current |
2015 | at least one system call): EV therefore updates its idea of the current |
1977 | time only before and after C<ev_run> collects new events, which causes a |
2016 | time only before and after C<ev_run> collects new events, which causes a |
1978 | growing difference between C<ev_now ()> and C<ev_time ()> when handling |
2017 | growing difference between C<ev_now ()> and C<ev_time ()> when handling |
1979 | lots of events in one iteration. |
2018 | lots of events in one iteration. |
1980 | |
2019 | |
1981 | The relative timeouts are calculated relative to the C<ev_now ()> |
2020 | The relative timeouts are calculated relative to the C<ev_now ()> |
… | |
… | |
1987 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
2026 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
1988 | |
2027 | |
1989 | If the event loop is suspended for a long time, you can also force an |
2028 | If the event loop is suspended for a long time, you can also force an |
1990 | update of the time returned by C<ev_now ()> by calling C<ev_now_update |
2029 | update of the time returned by C<ev_now ()> by calling C<ev_now_update |
1991 | ()>. |
2030 | ()>. |
|
|
2031 | |
|
|
2032 | =head3 The special problem of unsynchronised clocks |
|
|
2033 | |
|
|
2034 | Modern systems have a variety of clocks - libev itself uses the normal |
|
|
2035 | "wall clock" clock and, if available, the monotonic clock (to avoid time |
|
|
2036 | jumps). |
|
|
2037 | |
|
|
2038 | Neither of these clocks is synchronised with each other or any other clock |
|
|
2039 | on the system, so C<ev_time ()> might return a considerably different time |
|
|
2040 | than C<gettimeofday ()> or C<time ()>. On a GNU/Linux system, for example, |
|
|
2041 | a call to C<gettimeofday> might return a second count that is one higher |
|
|
2042 | than a directly following call to C<time>. |
|
|
2043 | |
|
|
2044 | The moral of this is to only compare libev-related timestamps with |
|
|
2045 | C<ev_time ()> and C<ev_now ()>, at least if you want better precision than |
|
|
2046 | a second or so. |
|
|
2047 | |
|
|
2048 | One more problem arises due to this lack of synchronisation: if libev uses |
|
|
2049 | the system monotonic clock and you compare timestamps from C<ev_time> |
|
|
2050 | or C<ev_now> from when you started your timer and when your callback is |
|
|
2051 | invoked, you will find that sometimes the callback is a bit "early". |
|
|
2052 | |
|
|
2053 | This is because C<ev_timer>s work in real time, not wall clock time, so |
|
|
2054 | libev makes sure your callback is not invoked before the delay happened, |
|
|
2055 | I<measured according to the real time>, not the system clock. |
|
|
2056 | |
|
|
2057 | If your timeouts are based on a physical timescale (e.g. "time out this |
|
|
2058 | connection after 100 seconds") then this shouldn't bother you as it is |
|
|
2059 | exactly the right behaviour. |
|
|
2060 | |
|
|
2061 | If you want to compare wall clock/system timestamps to your timers, then |
|
|
2062 | you need to use C<ev_periodic>s, as these are based on the wall clock |
|
|
2063 | time, where your comparisons will always generate correct results. |
1992 | |
2064 | |
1993 | =head3 The special problems of suspended animation |
2065 | =head3 The special problems of suspended animation |
1994 | |
2066 | |
1995 | When you leave the server world it is quite customary to hit machines that |
2067 | When you leave the server world it is quite customary to hit machines that |
1996 | can suspend/hibernate - what happens to the clocks during such a suspend? |
2068 | can suspend/hibernate - what happens to the clocks during such a suspend? |
… | |
… | |
2040 | keep up with the timer (because it takes longer than those 10 seconds to |
2112 | keep up with the timer (because it takes longer than those 10 seconds to |
2041 | do stuff) the timer will not fire more than once per event loop iteration. |
2113 | do stuff) the timer will not fire more than once per event loop iteration. |
2042 | |
2114 | |
2043 | =item ev_timer_again (loop, ev_timer *) |
2115 | =item ev_timer_again (loop, ev_timer *) |
2044 | |
2116 | |
2045 | This will act as if the timer timed out and restart it again if it is |
2117 | This will act as if the timer timed out, and restarts it again if it is |
2046 | repeating. The exact semantics are: |
2118 | repeating. It basically works like calling C<ev_timer_stop>, updating the |
|
|
2119 | timeout to the C<repeat> value and calling C<ev_timer_start>. |
2047 | |
2120 | |
|
|
2121 | The exact semantics are as in the following rules, all of which will be |
|
|
2122 | applied to the watcher: |
|
|
2123 | |
|
|
2124 | =over 4 |
|
|
2125 | |
2048 | If the timer is pending, its pending status is cleared. |
2126 | =item If the timer is pending, the pending status is always cleared. |
2049 | |
2127 | |
2050 | If the timer is started but non-repeating, stop it (as if it timed out). |
2128 | =item If the timer is started but non-repeating, stop it (as if it timed |
|
|
2129 | out, without invoking it). |
2051 | |
2130 | |
2052 | If the timer is repeating, either start it if necessary (with the |
2131 | =item If the timer is repeating, make the C<repeat> value the new timeout |
2053 | C<repeat> value), or reset the running timer to the C<repeat> value. |
2132 | and start the timer, if necessary. |
|
|
2133 | |
|
|
2134 | =back |
2054 | |
2135 | |
2055 | This sounds a bit complicated, see L<Be smart about timeouts>, above, for a |
2136 | This sounds a bit complicated, see L<Be smart about timeouts>, above, for a |
2056 | usage example. |
2137 | usage example. |
2057 | |
2138 | |
2058 | =item ev_tstamp ev_timer_remaining (loop, ev_timer *) |
2139 | =item ev_tstamp ev_timer_remaining (loop, ev_timer *) |
… | |
… | |
2180 | |
2261 | |
2181 | Another way to think about it (for the mathematically inclined) is that |
2262 | Another way to think about it (for the mathematically inclined) is that |
2182 | C<ev_periodic> will try to run the callback in this mode at the next possible |
2263 | C<ev_periodic> will try to run the callback in this mode at the next possible |
2183 | time where C<time = offset (mod interval)>, regardless of any time jumps. |
2264 | time where C<time = offset (mod interval)>, regardless of any time jumps. |
2184 | |
2265 | |
2185 | For numerical stability it is preferable that the C<offset> value is near |
2266 | The C<interval> I<MUST> be positive, and for numerical stability, the |
2186 | C<ev_now ()> (the current time), but there is no range requirement for |
2267 | interval value should be higher than C<1/8192> (which is around 100 |
2187 | this value, and in fact is often specified as zero. |
2268 | microseconds) and C<offset> should be higher than C<0> and should have |
|
|
2269 | at most a similar magnitude as the current time (say, within a factor of |
|
|
2270 | ten). Typical values for offset are, in fact, C<0> or something between |
|
|
2271 | C<0> and C<interval>, which is also the recommended range. |
2188 | |
2272 | |
2189 | Note also that there is an upper limit to how often a timer can fire (CPU |
2273 | Note also that there is an upper limit to how often a timer can fire (CPU |
2190 | speed for example), so if C<interval> is very small then timing stability |
2274 | speed for example), so if C<interval> is very small then timing stability |
2191 | will of course deteriorate. Libev itself tries to be exact to be about one |
2275 | will of course deteriorate. Libev itself tries to be exact to be about one |
2192 | millisecond (if the OS supports it and the machine is fast enough). |
2276 | millisecond (if the OS supports it and the machine is fast enough). |
… | |
… | |
2335 | =head3 The special problem of inheritance over fork/execve/pthread_create |
2419 | =head3 The special problem of inheritance over fork/execve/pthread_create |
2336 | |
2420 | |
2337 | Both the signal mask (C<sigprocmask>) and the signal disposition |
2421 | Both the signal mask (C<sigprocmask>) and the signal disposition |
2338 | (C<sigaction>) are unspecified after starting a signal watcher (and after |
2422 | (C<sigaction>) are unspecified after starting a signal watcher (and after |
2339 | stopping it again), that is, libev might or might not block the signal, |
2423 | stopping it again), that is, libev might or might not block the signal, |
2340 | and might or might not set or restore the installed signal handler. |
2424 | and might or might not set or restore the installed signal handler (but |
|
|
2425 | see C<EVFLAG_NOSIGMASK>). |
2341 | |
2426 | |
2342 | While this does not matter for the signal disposition (libev never |
2427 | While this does not matter for the signal disposition (libev never |
2343 | sets signals to C<SIG_IGN>, so handlers will be reset to C<SIG_DFL> on |
2428 | sets signals to C<SIG_IGN>, so handlers will be reset to C<SIG_DFL> on |
2344 | C<execve>), this matters for the signal mask: many programs do not expect |
2429 | C<execve>), this matters for the signal mask: many programs do not expect |
2345 | certain signals to be blocked. |
2430 | certain signals to be blocked. |
… | |
… | |
3216 | atexit (program_exits); |
3301 | atexit (program_exits); |
3217 | |
3302 | |
3218 | |
3303 | |
3219 | =head2 C<ev_async> - how to wake up an event loop |
3304 | =head2 C<ev_async> - how to wake up an event loop |
3220 | |
3305 | |
3221 | In general, you cannot use an C<ev_run> from multiple threads or other |
3306 | In general, you cannot use an C<ev_loop> from multiple threads or other |
3222 | asynchronous sources such as signal handlers (as opposed to multiple event |
3307 | asynchronous sources such as signal handlers (as opposed to multiple event |
3223 | loops - those are of course safe to use in different threads). |
3308 | loops - those are of course safe to use in different threads). |
3224 | |
3309 | |
3225 | Sometimes, however, you need to wake up an event loop you do not control, |
3310 | Sometimes, however, you need to wake up an event loop you do not control, |
3226 | for example because it belongs to another thread. This is what C<ev_async> |
3311 | for example because it belongs to another thread. This is what C<ev_async> |
… | |
… | |
3233 | C<ev_async_sent> calls). In fact, you could use signal watchers as a kind |
3318 | C<ev_async_sent> calls). In fact, you could use signal watchers as a kind |
3234 | of "global async watchers" by using a watcher on an otherwise unused |
3319 | of "global async watchers" by using a watcher on an otherwise unused |
3235 | signal, and C<ev_feed_signal> to signal this watcher from another thread, |
3320 | signal, and C<ev_feed_signal> to signal this watcher from another thread, |
3236 | even without knowing which loop owns the signal. |
3321 | even without knowing which loop owns the signal. |
3237 | |
3322 | |
3238 | Unlike C<ev_signal> watchers, C<ev_async> works with any event loop, not |
|
|
3239 | just the default loop. |
|
|
3240 | |
|
|
3241 | =head3 Queueing |
3323 | =head3 Queueing |
3242 | |
3324 | |
3243 | C<ev_async> does not support queueing of data in any way. The reason |
3325 | C<ev_async> does not support queueing of data in any way. The reason |
3244 | is that the author does not know of a simple (or any) algorithm for a |
3326 | is that the author does not know of a simple (or any) algorithm for a |
3245 | multiple-writer-single-reader queue that works in all cases and doesn't |
3327 | multiple-writer-single-reader queue that works in all cases and doesn't |
… | |
… | |
3336 | trust me. |
3418 | trust me. |
3337 | |
3419 | |
3338 | =item ev_async_send (loop, ev_async *) |
3420 | =item ev_async_send (loop, ev_async *) |
3339 | |
3421 | |
3340 | Sends/signals/activates the given C<ev_async> watcher, that is, feeds |
3422 | Sends/signals/activates the given C<ev_async> watcher, that is, feeds |
3341 | an C<EV_ASYNC> event on the watcher into the event loop. Unlike |
3423 | an C<EV_ASYNC> event on the watcher into the event loop, and instantly |
|
|
3424 | returns. |
|
|
3425 | |
3342 | C<ev_feed_event>, this call is safe to do from other threads, signal or |
3426 | Unlike C<ev_feed_event>, this call is safe to do from other threads, |
3343 | similar contexts (see the discussion of C<EV_ATOMIC_T> in the embedding |
3427 | signal or similar contexts (see the discussion of C<EV_ATOMIC_T> in the |
3344 | section below on what exactly this means). |
3428 | embedding section below on what exactly this means). |
3345 | |
3429 | |
3346 | Note that, as with other watchers in libev, multiple events might get |
3430 | Note that, as with other watchers in libev, multiple events might get |
3347 | compressed into a single callback invocation (another way to look at this |
3431 | compressed into a single callback invocation (another way to look at |
3348 | is that C<ev_async> watchers are level-triggered, set on C<ev_async_send>, |
3432 | this is that C<ev_async> watchers are level-triggered: they are set on |
3349 | reset when the event loop detects that). |
3433 | C<ev_async_send>, reset when the event loop detects that). |
3350 | |
3434 | |
3351 | This call incurs the overhead of a system call only once per event loop |
3435 | This call incurs the overhead of at most one extra system call per event |
3352 | iteration, so while the overhead might be noticeable, it doesn't apply to |
3436 | loop iteration, if the event loop is blocked, and no syscall at all if |
3353 | repeated calls to C<ev_async_send> for the same event loop. |
3437 | the event loop (or your program) is processing events. That means that |
|
|
3438 | repeated calls are basically free (there is no need to avoid calls for |
|
|
3439 | performance reasons) and that the overhead becomes smaller (typically |
|
|
3440 | zero) under load. |
3354 | |
3441 | |
3355 | =item bool = ev_async_pending (ev_async *) |
3442 | =item bool = ev_async_pending (ev_async *) |
3356 | |
3443 | |
3357 | Returns a non-zero value when C<ev_async_send> has been called on the |
3444 | Returns a non-zero value when C<ev_async_send> has been called on the |
3358 | watcher but the event has not yet been processed (or even noted) by the |
3445 | watcher but the event has not yet been processed (or even noted) by the |
… | |
… | |
3413 | ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
3500 | ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
3414 | |
3501 | |
3415 | =item ev_feed_fd_event (loop, int fd, int revents) |
3502 | =item ev_feed_fd_event (loop, int fd, int revents) |
3416 | |
3503 | |
3417 | Feed an event on the given fd, as if a file descriptor backend detected |
3504 | Feed an event on the given fd, as if a file descriptor backend detected |
3418 | the given events it. |
3505 | the given events. |
3419 | |
3506 | |
3420 | =item ev_feed_signal_event (loop, int signum) |
3507 | =item ev_feed_signal_event (loop, int signum) |
3421 | |
3508 | |
3422 | Feed an event as if the given signal occurred. See also C<ev_feed_signal>, |
3509 | Feed an event as if the given signal occurred. See also C<ev_feed_signal>, |
3423 | which is async-safe. |
3510 | which is async-safe. |
… | |
… | |
3429 | |
3516 | |
3430 | This section explains some common idioms that are not immediately |
3517 | This section explains some common idioms that are not immediately |
3431 | obvious. Note that examples are sprinkled over the whole manual, and this |
3518 | obvious. Note that examples are sprinkled over the whole manual, and this |
3432 | section only contains stuff that wouldn't fit anywhere else. |
3519 | section only contains stuff that wouldn't fit anywhere else. |
3433 | |
3520 | |
3434 | =over 4 |
3521 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
3435 | |
3522 | |
3436 | =item Model/nested event loop invocations and exit conditions. |
3523 | Each watcher has, by default, a C<void *data> member that you can read |
|
|
3524 | or modify at any time: libev will completely ignore it. This can be used |
|
|
3525 | to associate arbitrary data with your watcher. If you need more data and |
|
|
3526 | don't want to allocate memory separately and store a pointer to it in that |
|
|
3527 | data member, you can also "subclass" the watcher type and provide your own |
|
|
3528 | data: |
|
|
3529 | |
|
|
3530 | struct my_io |
|
|
3531 | { |
|
|
3532 | ev_io io; |
|
|
3533 | int otherfd; |
|
|
3534 | void *somedata; |
|
|
3535 | struct whatever *mostinteresting; |
|
|
3536 | }; |
|
|
3537 | |
|
|
3538 | ... |
|
|
3539 | struct my_io w; |
|
|
3540 | ev_io_init (&w.io, my_cb, fd, EV_READ); |
|
|
3541 | |
|
|
3542 | And since your callback will be called with a pointer to the watcher, you |
|
|
3543 | can cast it back to your own type: |
|
|
3544 | |
|
|
3545 | static void my_cb (struct ev_loop *loop, ev_io *w_, int revents) |
|
|
3546 | { |
|
|
3547 | struct my_io *w = (struct my_io *)w_; |
|
|
3548 | ... |
|
|
3549 | } |
|
|
3550 | |
|
|
3551 | More interesting and less C-conformant ways of casting your callback |
|
|
3552 | function type instead have been omitted. |
|
|
3553 | |
|
|
3554 | =head2 BUILDING YOUR OWN COMPOSITE WATCHERS |
|
|
3555 | |
|
|
3556 | Another common scenario is to use some data structure with multiple |
|
|
3557 | embedded watchers, in effect creating your own watcher that combines |
|
|
3558 | multiple libev event sources into one "super-watcher": |
|
|
3559 | |
|
|
3560 | struct my_biggy |
|
|
3561 | { |
|
|
3562 | int some_data; |
|
|
3563 | ev_timer t1; |
|
|
3564 | ev_timer t2; |
|
|
3565 | } |
|
|
3566 | |
|
|
3567 | In this case getting the pointer to C<my_biggy> is a bit more |
|
|
3568 | complicated: Either you store the address of your C<my_biggy> struct in |
|
|
3569 | the C<data> member of the watcher (for woozies or C++ coders), or you need |
|
|
3570 | to use some pointer arithmetic using C<offsetof> inside your watchers (for |
|
|
3571 | real programmers): |
|
|
3572 | |
|
|
3573 | #include <stddef.h> |
|
|
3574 | |
|
|
3575 | static void |
|
|
3576 | t1_cb (EV_P_ ev_timer *w, int revents) |
|
|
3577 | { |
|
|
3578 | struct my_biggy big = (struct my_biggy *) |
|
|
3579 | (((char *)w) - offsetof (struct my_biggy, t1)); |
|
|
3580 | } |
|
|
3581 | |
|
|
3582 | static void |
|
|
3583 | t2_cb (EV_P_ ev_timer *w, int revents) |
|
|
3584 | { |
|
|
3585 | struct my_biggy big = (struct my_biggy *) |
|
|
3586 | (((char *)w) - offsetof (struct my_biggy, t2)); |
|
|
3587 | } |
|
|
3588 | |
|
|
3589 | =head2 AVOIDING FINISHING BEFORE RETURNING |
|
|
3590 | |
|
|
3591 | Often you have structures like this in event-based programs: |
|
|
3592 | |
|
|
3593 | callback () |
|
|
3594 | { |
|
|
3595 | free (request); |
|
|
3596 | } |
|
|
3597 | |
|
|
3598 | request = start_new_request (..., callback); |
|
|
3599 | |
|
|
3600 | The intent is to start some "lengthy" operation. The C<request> could be |
|
|
3601 | used to cancel the operation, or do other things with it. |
|
|
3602 | |
|
|
3603 | It's not uncommon to have code paths in C<start_new_request> that |
|
|
3604 | immediately invoke the callback, for example, to report errors. Or you add |
|
|
3605 | some caching layer that finds that it can skip the lengthy aspects of the |
|
|
3606 | operation and simply invoke the callback with the result. |
|
|
3607 | |
|
|
3608 | The problem here is that this will happen I<before> C<start_new_request> |
|
|
3609 | has returned, so C<request> is not set. |
|
|
3610 | |
|
|
3611 | Even if you pass the request by some safer means to the callback, you |
|
|
3612 | might want to do something to the request after starting it, such as |
|
|
3613 | canceling it, which probably isn't working so well when the callback has |
|
|
3614 | already been invoked. |
|
|
3615 | |
|
|
3616 | A common way around all these issues is to make sure that |
|
|
3617 | C<start_new_request> I<always> returns before the callback is invoked. If |
|
|
3618 | C<start_new_request> immediately knows the result, it can artificially |
|
|
3619 | delay invoking the callback by e.g. using a C<prepare> or C<idle> watcher |
|
|
3620 | for example, or more sneakily, by reusing an existing (stopped) watcher |
|
|
3621 | and pushing it into the pending queue: |
|
|
3622 | |
|
|
3623 | ev_set_cb (watcher, callback); |
|
|
3624 | ev_feed_event (EV_A_ watcher, 0); |
|
|
3625 | |
|
|
3626 | This way, C<start_new_request> can safely return before the callback is |
|
|
3627 | invoked, while not delaying callback invocation too much. |
|
|
3628 | |
|
|
3629 | =head2 MODEL/NESTED EVENT LOOP INVOCATIONS AND EXIT CONDITIONS |
3437 | |
3630 | |
3438 | Often (especially in GUI toolkits) there are places where you have |
3631 | Often (especially in GUI toolkits) there are places where you have |
3439 | I<modal> interaction, which is most easily implemented by recursively |
3632 | I<modal> interaction, which is most easily implemented by recursively |
3440 | invoking C<ev_run>. |
3633 | invoking C<ev_run>. |
3441 | |
3634 | |
… | |
… | |
3453 | int exit_main_loop = 0; |
3646 | int exit_main_loop = 0; |
3454 | |
3647 | |
3455 | while (!exit_main_loop) |
3648 | while (!exit_main_loop) |
3456 | ev_run (EV_DEFAULT_ EVRUN_ONCE); |
3649 | ev_run (EV_DEFAULT_ EVRUN_ONCE); |
3457 | |
3650 | |
3458 | // in a model watcher |
3651 | // in a modal watcher |
3459 | int exit_nested_loop = 0; |
3652 | int exit_nested_loop = 0; |
3460 | |
3653 | |
3461 | while (!exit_nested_loop) |
3654 | while (!exit_nested_loop) |
3462 | ev_run (EV_A_ EVRUN_ONCE); |
3655 | ev_run (EV_A_ EVRUN_ONCE); |
3463 | |
3656 | |
… | |
… | |
3470 | exit_main_loop = 1; |
3663 | exit_main_loop = 1; |
3471 | |
3664 | |
3472 | // exit both |
3665 | // exit both |
3473 | exit_main_loop = exit_nested_loop = 1; |
3666 | exit_main_loop = exit_nested_loop = 1; |
3474 | |
3667 | |
3475 | =back |
3668 | =head2 THREAD LOCKING EXAMPLE |
|
|
3669 | |
|
|
3670 | Here is a fictitious example of how to run an event loop in a different |
|
|
3671 | thread from where callbacks are being invoked and watchers are |
|
|
3672 | created/added/removed. |
|
|
3673 | |
|
|
3674 | For a real-world example, see the C<EV::Loop::Async> perl module, |
|
|
3675 | which uses exactly this technique (which is suited for many high-level |
|
|
3676 | languages). |
|
|
3677 | |
|
|
3678 | The example uses a pthread mutex to protect the loop data, a condition |
|
|
3679 | variable to wait for callback invocations, an async watcher to notify the |
|
|
3680 | event loop thread and an unspecified mechanism to wake up the main thread. |
|
|
3681 | |
|
|
3682 | First, you need to associate some data with the event loop: |
|
|
3683 | |
|
|
3684 | typedef struct { |
|
|
3685 | mutex_t lock; /* global loop lock */ |
|
|
3686 | ev_async async_w; |
|
|
3687 | thread_t tid; |
|
|
3688 | cond_t invoke_cv; |
|
|
3689 | } userdata; |
|
|
3690 | |
|
|
3691 | void prepare_loop (EV_P) |
|
|
3692 | { |
|
|
3693 | // for simplicity, we use a static userdata struct. |
|
|
3694 | static userdata u; |
|
|
3695 | |
|
|
3696 | ev_async_init (&u->async_w, async_cb); |
|
|
3697 | ev_async_start (EV_A_ &u->async_w); |
|
|
3698 | |
|
|
3699 | pthread_mutex_init (&u->lock, 0); |
|
|
3700 | pthread_cond_init (&u->invoke_cv, 0); |
|
|
3701 | |
|
|
3702 | // now associate this with the loop |
|
|
3703 | ev_set_userdata (EV_A_ u); |
|
|
3704 | ev_set_invoke_pending_cb (EV_A_ l_invoke); |
|
|
3705 | ev_set_loop_release_cb (EV_A_ l_release, l_acquire); |
|
|
3706 | |
|
|
3707 | // then create the thread running ev_run |
|
|
3708 | pthread_create (&u->tid, 0, l_run, EV_A); |
|
|
3709 | } |
|
|
3710 | |
|
|
3711 | The callback for the C<ev_async> watcher does nothing: the watcher is used |
|
|
3712 | solely to wake up the event loop so it takes notice of any new watchers |
|
|
3713 | that might have been added: |
|
|
3714 | |
|
|
3715 | static void |
|
|
3716 | async_cb (EV_P_ ev_async *w, int revents) |
|
|
3717 | { |
|
|
3718 | // just used for the side effects |
|
|
3719 | } |
|
|
3720 | |
|
|
3721 | The C<l_release> and C<l_acquire> callbacks simply unlock/lock the mutex |
|
|
3722 | protecting the loop data, respectively. |
|
|
3723 | |
|
|
3724 | static void |
|
|
3725 | l_release (EV_P) |
|
|
3726 | { |
|
|
3727 | userdata *u = ev_userdata (EV_A); |
|
|
3728 | pthread_mutex_unlock (&u->lock); |
|
|
3729 | } |
|
|
3730 | |
|
|
3731 | static void |
|
|
3732 | l_acquire (EV_P) |
|
|
3733 | { |
|
|
3734 | userdata *u = ev_userdata (EV_A); |
|
|
3735 | pthread_mutex_lock (&u->lock); |
|
|
3736 | } |
|
|
3737 | |
|
|
3738 | The event loop thread first acquires the mutex, and then jumps straight |
|
|
3739 | into C<ev_run>: |
|
|
3740 | |
|
|
3741 | void * |
|
|
3742 | l_run (void *thr_arg) |
|
|
3743 | { |
|
|
3744 | struct ev_loop *loop = (struct ev_loop *)thr_arg; |
|
|
3745 | |
|
|
3746 | l_acquire (EV_A); |
|
|
3747 | pthread_setcanceltype (PTHREAD_CANCEL_ASYNCHRONOUS, 0); |
|
|
3748 | ev_run (EV_A_ 0); |
|
|
3749 | l_release (EV_A); |
|
|
3750 | |
|
|
3751 | return 0; |
|
|
3752 | } |
|
|
3753 | |
|
|
3754 | Instead of invoking all pending watchers, the C<l_invoke> callback will |
|
|
3755 | signal the main thread via some unspecified mechanism (signals? pipe |
|
|
3756 | writes? C<Async::Interrupt>?) and then waits until all pending watchers |
|
|
3757 | have been called (in a while loop because a) spurious wakeups are possible |
|
|
3758 | and b) skipping inter-thread-communication when there are no pending |
|
|
3759 | watchers is very beneficial): |
|
|
3760 | |
|
|
3761 | static void |
|
|
3762 | l_invoke (EV_P) |
|
|
3763 | { |
|
|
3764 | userdata *u = ev_userdata (EV_A); |
|
|
3765 | |
|
|
3766 | while (ev_pending_count (EV_A)) |
|
|
3767 | { |
|
|
3768 | wake_up_other_thread_in_some_magic_or_not_so_magic_way (); |
|
|
3769 | pthread_cond_wait (&u->invoke_cv, &u->lock); |
|
|
3770 | } |
|
|
3771 | } |
|
|
3772 | |
|
|
3773 | Now, whenever the main thread gets told to invoke pending watchers, it |
|
|
3774 | will grab the lock, call C<ev_invoke_pending> and then signal the loop |
|
|
3775 | thread to continue: |
|
|
3776 | |
|
|
3777 | static void |
|
|
3778 | real_invoke_pending (EV_P) |
|
|
3779 | { |
|
|
3780 | userdata *u = ev_userdata (EV_A); |
|
|
3781 | |
|
|
3782 | pthread_mutex_lock (&u->lock); |
|
|
3783 | ev_invoke_pending (EV_A); |
|
|
3784 | pthread_cond_signal (&u->invoke_cv); |
|
|
3785 | pthread_mutex_unlock (&u->lock); |
|
|
3786 | } |
|
|
3787 | |
|
|
3788 | Whenever you want to start/stop a watcher or do other modifications to an |
|
|
3789 | event loop, you will now have to lock: |
|
|
3790 | |
|
|
3791 | ev_timer timeout_watcher; |
|
|
3792 | userdata *u = ev_userdata (EV_A); |
|
|
3793 | |
|
|
3794 | ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.); |
|
|
3795 | |
|
|
3796 | pthread_mutex_lock (&u->lock); |
|
|
3797 | ev_timer_start (EV_A_ &timeout_watcher); |
|
|
3798 | ev_async_send (EV_A_ &u->async_w); |
|
|
3799 | pthread_mutex_unlock (&u->lock); |
|
|
3800 | |
|
|
3801 | Note that sending the C<ev_async> watcher is required because otherwise |
|
|
3802 | an event loop currently blocking in the kernel will have no knowledge |
|
|
3803 | about the newly added timer. By waking up the loop it will pick up any new |
|
|
3804 | watchers in the next event loop iteration. |
|
|
3805 | |
|
|
3806 | =head2 THREADS, COROUTINES, CONTINUATIONS, QUEUES... INSTEAD OF CALLBACKS |
|
|
3807 | |
|
|
3808 | While the overhead of a callback that e.g. schedules a thread is small, it |
|
|
3809 | is still an overhead. If you embed libev, and your main usage is with some |
|
|
3810 | kind of threads or coroutines, you might want to customise libev so that |
|
|
3811 | doesn't need callbacks anymore. |
|
|
3812 | |
|
|
3813 | Imagine you have coroutines that you can switch to using a function |
|
|
3814 | C<switch_to (coro)>, that libev runs in a coroutine called C<libev_coro> |
|
|
3815 | and that due to some magic, the currently active coroutine is stored in a |
|
|
3816 | global called C<current_coro>. Then you can build your own "wait for libev |
|
|
3817 | event" primitive by changing C<EV_CB_DECLARE> and C<EV_CB_INVOKE> (note |
|
|
3818 | the differing C<;> conventions): |
|
|
3819 | |
|
|
3820 | #define EV_CB_DECLARE(type) struct my_coro *cb; |
|
|
3821 | #define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb) |
|
|
3822 | |
|
|
3823 | That means instead of having a C callback function, you store the |
|
|
3824 | coroutine to switch to in each watcher, and instead of having libev call |
|
|
3825 | your callback, you instead have it switch to that coroutine. |
|
|
3826 | |
|
|
3827 | A coroutine might now wait for an event with a function called |
|
|
3828 | C<wait_for_event>. (the watcher needs to be started, as always, but it doesn't |
|
|
3829 | matter when, or whether the watcher is active or not when this function is |
|
|
3830 | called): |
|
|
3831 | |
|
|
3832 | void |
|
|
3833 | wait_for_event (ev_watcher *w) |
|
|
3834 | { |
|
|
3835 | ev_cb_set (w) = current_coro; |
|
|
3836 | switch_to (libev_coro); |
|
|
3837 | } |
|
|
3838 | |
|
|
3839 | That basically suspends the coroutine inside C<wait_for_event> and |
|
|
3840 | continues the libev coroutine, which, when appropriate, switches back to |
|
|
3841 | this or any other coroutine. |
|
|
3842 | |
|
|
3843 | You can do similar tricks if you have, say, threads with an event queue - |
|
|
3844 | instead of storing a coroutine, you store the queue object and instead of |
|
|
3845 | switching to a coroutine, you push the watcher onto the queue and notify |
|
|
3846 | any waiters. |
|
|
3847 | |
|
|
3848 | To embed libev, see L<EMBEDDING>, but in short, it's easiest to create two |
|
|
3849 | files, F<my_ev.h> and F<my_ev.c> that include the respective libev files: |
|
|
3850 | |
|
|
3851 | // my_ev.h |
|
|
3852 | #define EV_CB_DECLARE(type) struct my_coro *cb; |
|
|
3853 | #define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb); |
|
|
3854 | #include "../libev/ev.h" |
|
|
3855 | |
|
|
3856 | // my_ev.c |
|
|
3857 | #define EV_H "my_ev.h" |
|
|
3858 | #include "../libev/ev.c" |
|
|
3859 | |
|
|
3860 | And then use F<my_ev.h> when you would normally use F<ev.h>, and compile |
|
|
3861 | F<my_ev.c> into your project. When properly specifying include paths, you |
|
|
3862 | can even use F<ev.h> as header file name directly. |
3476 | |
3863 | |
3477 | |
3864 | |
3478 | =head1 LIBEVENT EMULATION |
3865 | =head1 LIBEVENT EMULATION |
3479 | |
3866 | |
3480 | Libev offers a compatibility emulation layer for libevent. It cannot |
3867 | Libev offers a compatibility emulation layer for libevent. It cannot |
… | |
… | |
3509 | to use the libev header file and library. |
3896 | to use the libev header file and library. |
3510 | |
3897 | |
3511 | =back |
3898 | =back |
3512 | |
3899 | |
3513 | =head1 C++ SUPPORT |
3900 | =head1 C++ SUPPORT |
|
|
3901 | |
|
|
3902 | =head2 C API |
|
|
3903 | |
|
|
3904 | The normal C API should work fine when used from C++: both ev.h and the |
|
|
3905 | libev sources can be compiled as C++. Therefore, code that uses the C API |
|
|
3906 | will work fine. |
|
|
3907 | |
|
|
3908 | Proper exception specifications might have to be added to callbacks passed |
|
|
3909 | to libev: exceptions may be thrown only from watcher callbacks, all |
|
|
3910 | other callbacks (allocator, syserr, loop acquire/release and periodioc |
|
|
3911 | reschedule callbacks) must not throw exceptions, and might need a C<throw |
|
|
3912 | ()> specification. If you have code that needs to be compiled as both C |
|
|
3913 | and C++ you can use the C<EV_THROW> macro for this: |
|
|
3914 | |
|
|
3915 | static void |
|
|
3916 | fatal_error (const char *msg) EV_THROW |
|
|
3917 | { |
|
|
3918 | perror (msg); |
|
|
3919 | abort (); |
|
|
3920 | } |
|
|
3921 | |
|
|
3922 | ... |
|
|
3923 | ev_set_syserr_cb (fatal_error); |
|
|
3924 | |
|
|
3925 | The only API functions that can currently throw exceptions are C<ev_run>, |
|
|
3926 | C<ev_inoke>, C<ev_invoke_pending> and C<ev_loop_destroy> (the latter |
|
|
3927 | because it runs cleanup watchers). |
|
|
3928 | |
|
|
3929 | Throwing exceptions in watcher callbacks is only supported if libev itself |
|
|
3930 | is compiled with a C++ compiler or your C and C++ environments allow |
|
|
3931 | throwing exceptions through C libraries (most do). |
|
|
3932 | |
|
|
3933 | =head2 C++ API |
3514 | |
3934 | |
3515 | Libev comes with some simplistic wrapper classes for C++ that mainly allow |
3935 | Libev comes with some simplistic wrapper classes for C++ that mainly allow |
3516 | you to use some convenience methods to start/stop watchers and also change |
3936 | you to use some convenience methods to start/stop watchers and also change |
3517 | the callback model to a model using method callbacks on objects. |
3937 | the callback model to a model using method callbacks on objects. |
3518 | |
3938 | |
… | |
… | |
3534 | with C<operator ()> can be used as callbacks. Other types should be easy |
3954 | with C<operator ()> can be used as callbacks. Other types should be easy |
3535 | to add as long as they only need one additional pointer for context. If |
3955 | to add as long as they only need one additional pointer for context. If |
3536 | you need support for other types of functors please contact the author |
3956 | you need support for other types of functors please contact the author |
3537 | (preferably after implementing it). |
3957 | (preferably after implementing it). |
3538 | |
3958 | |
|
|
3959 | For all this to work, your C++ compiler either has to use the same calling |
|
|
3960 | conventions as your C compiler (for static member functions), or you have |
|
|
3961 | to embed libev and compile libev itself as C++. |
|
|
3962 | |
3539 | Here is a list of things available in the C<ev> namespace: |
3963 | Here is a list of things available in the C<ev> namespace: |
3540 | |
3964 | |
3541 | =over 4 |
3965 | =over 4 |
3542 | |
3966 | |
3543 | =item C<ev::READ>, C<ev::WRITE> etc. |
3967 | =item C<ev::READ>, C<ev::WRITE> etc. |
… | |
… | |
3552 | =item C<ev::io>, C<ev::timer>, C<ev::periodic>, C<ev::idle>, C<ev::sig> etc. |
3976 | =item C<ev::io>, C<ev::timer>, C<ev::periodic>, C<ev::idle>, C<ev::sig> etc. |
3553 | |
3977 | |
3554 | For each C<ev_TYPE> watcher in F<ev.h> there is a corresponding class of |
3978 | For each C<ev_TYPE> watcher in F<ev.h> there is a corresponding class of |
3555 | the same name in the C<ev> namespace, with the exception of C<ev_signal> |
3979 | the same name in the C<ev> namespace, with the exception of C<ev_signal> |
3556 | which is called C<ev::sig> to avoid clashes with the C<signal> macro |
3980 | which is called C<ev::sig> to avoid clashes with the C<signal> macro |
3557 | defines by many implementations. |
3981 | defined by many implementations. |
3558 | |
3982 | |
3559 | All of those classes have these methods: |
3983 | All of those classes have these methods: |
3560 | |
3984 | |
3561 | =over 4 |
3985 | =over 4 |
3562 | |
3986 | |
… | |
… | |
3695 | watchers in the constructor. |
4119 | watchers in the constructor. |
3696 | |
4120 | |
3697 | class myclass |
4121 | class myclass |
3698 | { |
4122 | { |
3699 | ev::io io ; void io_cb (ev::io &w, int revents); |
4123 | ev::io io ; void io_cb (ev::io &w, int revents); |
3700 | ev::io2 io2 ; void io2_cb (ev::io &w, int revents); |
4124 | ev::io io2 ; void io2_cb (ev::io &w, int revents); |
3701 | ev::idle idle; void idle_cb (ev::idle &w, int revents); |
4125 | ev::idle idle; void idle_cb (ev::idle &w, int revents); |
3702 | |
4126 | |
3703 | myclass (int fd) |
4127 | myclass (int fd) |
3704 | { |
4128 | { |
3705 | io .set <myclass, &myclass::io_cb > (this); |
4129 | io .set <myclass, &myclass::io_cb > (this); |
… | |
… | |
3756 | L<http://hackage.haskell.org/cgi-bin/hackage-scripts/package/hlibev>. |
4180 | L<http://hackage.haskell.org/cgi-bin/hackage-scripts/package/hlibev>. |
3757 | |
4181 | |
3758 | =item D |
4182 | =item D |
3759 | |
4183 | |
3760 | Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to |
4184 | Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to |
3761 | be found at L<http://proj.llucax.com.ar/wiki/evd>. |
4185 | be found at L<http://www.llucax.com.ar/proj/ev.d/index.html>. |
3762 | |
4186 | |
3763 | =item Ocaml |
4187 | =item Ocaml |
3764 | |
4188 | |
3765 | Erkki Seppala has written Ocaml bindings for libev, to be found at |
4189 | Erkki Seppala has written Ocaml bindings for libev, to be found at |
3766 | L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>. |
4190 | L<http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>. |
… | |
… | |
3814 | suitable for use with C<EV_A>. |
4238 | suitable for use with C<EV_A>. |
3815 | |
4239 | |
3816 | =item C<EV_DEFAULT>, C<EV_DEFAULT_> |
4240 | =item C<EV_DEFAULT>, C<EV_DEFAULT_> |
3817 | |
4241 | |
3818 | Similar to the other two macros, this gives you the value of the default |
4242 | Similar to the other two macros, this gives you the value of the default |
3819 | loop, if multiple loops are supported ("ev loop default"). |
4243 | loop, if multiple loops are supported ("ev loop default"). The default loop |
|
|
4244 | will be initialised if it isn't already initialised. |
|
|
4245 | |
|
|
4246 | For non-multiplicity builds, these macros do nothing, so you always have |
|
|
4247 | to initialise the loop somewhere. |
3820 | |
4248 | |
3821 | =item C<EV_DEFAULT_UC>, C<EV_DEFAULT_UC_> |
4249 | =item C<EV_DEFAULT_UC>, C<EV_DEFAULT_UC_> |
3822 | |
4250 | |
3823 | Usage identical to C<EV_DEFAULT> and C<EV_DEFAULT_>, but requires that the |
4251 | Usage identical to C<EV_DEFAULT> and C<EV_DEFAULT_>, but requires that the |
3824 | default loop has been initialised (C<UC> == unchecked). Their behaviour |
4252 | default loop has been initialised (C<UC> == unchecked). Their behaviour |
… | |
… | |
3969 | supported). It will also not define any of the structs usually found in |
4397 | supported). It will also not define any of the structs usually found in |
3970 | F<event.h> that are not directly supported by the libev core alone. |
4398 | F<event.h> that are not directly supported by the libev core alone. |
3971 | |
4399 | |
3972 | In standalone mode, libev will still try to automatically deduce the |
4400 | In standalone mode, libev will still try to automatically deduce the |
3973 | configuration, but has to be more conservative. |
4401 | configuration, but has to be more conservative. |
|
|
4402 | |
|
|
4403 | =item EV_USE_FLOOR |
|
|
4404 | |
|
|
4405 | If defined to be C<1>, libev will use the C<floor ()> function for its |
|
|
4406 | periodic reschedule calculations, otherwise libev will fall back on a |
|
|
4407 | portable (slower) implementation. If you enable this, you usually have to |
|
|
4408 | link against libm or something equivalent. Enabling this when the C<floor> |
|
|
4409 | function is not available will fail, so the safe default is to not enable |
|
|
4410 | this. |
3974 | |
4411 | |
3975 | =item EV_USE_MONOTONIC |
4412 | =item EV_USE_MONOTONIC |
3976 | |
4413 | |
3977 | If defined to be C<1>, libev will try to detect the availability of the |
4414 | If defined to be C<1>, libev will try to detect the availability of the |
3978 | monotonic clock option at both compile time and runtime. Otherwise no |
4415 | monotonic clock option at both compile time and runtime. Otherwise no |
… | |
… | |
4108 | If defined to be C<1>, libev will compile in support for the Linux inotify |
4545 | If defined to be C<1>, libev will compile in support for the Linux inotify |
4109 | interface to speed up C<ev_stat> watchers. Its actual availability will |
4546 | interface to speed up C<ev_stat> watchers. Its actual availability will |
4110 | be detected at runtime. If undefined, it will be enabled if the headers |
4547 | be detected at runtime. If undefined, it will be enabled if the headers |
4111 | indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
4548 | indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
4112 | |
4549 | |
|
|
4550 | =item EV_NO_SMP |
|
|
4551 | |
|
|
4552 | If defined to be C<1>, libev will assume that memory is always coherent |
|
|
4553 | between threads, that is, threads can be used, but threads never run on |
|
|
4554 | different cpus (or different cpu cores). This reduces dependencies |
|
|
4555 | and makes libev faster. |
|
|
4556 | |
|
|
4557 | =item EV_NO_THREADS |
|
|
4558 | |
|
|
4559 | If defined to be C<1>, libev will assume that it will never be called |
|
|
4560 | from different threads, which is a stronger assumption than C<EV_NO_SMP>, |
|
|
4561 | above. This reduces dependencies and makes libev faster. |
|
|
4562 | |
4113 | =item EV_ATOMIC_T |
4563 | =item EV_ATOMIC_T |
4114 | |
4564 | |
4115 | Libev requires an integer type (suitable for storing C<0> or C<1>) whose |
4565 | Libev requires an integer type (suitable for storing C<0> or C<1>) whose |
4116 | access is atomic with respect to other threads or signal contexts. No such |
4566 | access is atomic and serialised with respect to other threads or signal |
4117 | type is easily found in the C language, so you can provide your own type |
4567 | contexts. No such type is easily found in the C language, so you can |
4118 | that you know is safe for your purposes. It is used both for signal handler "locking" |
4568 | provide your own type that you know is safe for your purposes. It is used |
4119 | as well as for signal and thread safety in C<ev_async> watchers. |
4569 | both for signal handler "locking" as well as for signal and thread safety |
|
|
4570 | in C<ev_async> watchers. |
4120 | |
4571 | |
4121 | In the absence of this define, libev will use C<sig_atomic_t volatile> |
4572 | In the absence of this define, libev will use C<sig_atomic_t volatile> |
4122 | (from F<signal.h>), which is usually good enough on most platforms. |
4573 | (from F<signal.h>), which is usually good enough on most platforms, |
|
|
4574 | although strictly speaking using a type that also implies a memory fence |
|
|
4575 | is required. |
4123 | |
4576 | |
4124 | =item EV_H (h) |
4577 | =item EV_H (h) |
4125 | |
4578 | |
4126 | The name of the F<ev.h> header file used to include it. The default if |
4579 | The name of the F<ev.h> header file used to include it. The default if |
4127 | undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be |
4580 | undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be |
… | |
… | |
4151 | will have the C<struct ev_loop *> as first argument, and you can create |
4604 | will have the C<struct ev_loop *> as first argument, and you can create |
4152 | additional independent event loops. Otherwise there will be no support |
4605 | additional independent event loops. Otherwise there will be no support |
4153 | for multiple event loops and there is no first event loop pointer |
4606 | for multiple event loops and there is no first event loop pointer |
4154 | argument. Instead, all functions act on the single default loop. |
4607 | argument. Instead, all functions act on the single default loop. |
4155 | |
4608 | |
|
|
4609 | Note that C<EV_DEFAULT> and C<EV_DEFAULT_> will no longer provide a |
|
|
4610 | default loop when multiplicity is switched off - you always have to |
|
|
4611 | initialise the loop manually in this case. |
|
|
4612 | |
4156 | =item EV_MINPRI |
4613 | =item EV_MINPRI |
4157 | |
4614 | |
4158 | =item EV_MAXPRI |
4615 | =item EV_MAXPRI |
4159 | |
4616 | |
4160 | The range of allowed priorities. C<EV_MINPRI> must be smaller or equal to |
4617 | The range of allowed priorities. C<EV_MINPRI> must be smaller or equal to |
… | |
… | |
4196 | #define EV_USE_POLL 1 |
4653 | #define EV_USE_POLL 1 |
4197 | #define EV_CHILD_ENABLE 1 |
4654 | #define EV_CHILD_ENABLE 1 |
4198 | #define EV_ASYNC_ENABLE 1 |
4655 | #define EV_ASYNC_ENABLE 1 |
4199 | |
4656 | |
4200 | The actual value is a bitset, it can be a combination of the following |
4657 | The actual value is a bitset, it can be a combination of the following |
4201 | values: |
4658 | values (by default, all of these are enabled): |
4202 | |
4659 | |
4203 | =over 4 |
4660 | =over 4 |
4204 | |
4661 | |
4205 | =item C<1> - faster/larger code |
4662 | =item C<1> - faster/larger code |
4206 | |
4663 | |
… | |
… | |
4210 | code size by roughly 30% on amd64). |
4667 | code size by roughly 30% on amd64). |
4211 | |
4668 | |
4212 | When optimising for size, use of compiler flags such as C<-Os> with |
4669 | When optimising for size, use of compiler flags such as C<-Os> with |
4213 | gcc is recommended, as well as C<-DNDEBUG>, as libev contains a number of |
4670 | gcc is recommended, as well as C<-DNDEBUG>, as libev contains a number of |
4214 | assertions. |
4671 | assertions. |
|
|
4672 | |
|
|
4673 | The default is off when C<__OPTIMIZE_SIZE__> is defined by your compiler |
|
|
4674 | (e.g. gcc with C<-Os>). |
4215 | |
4675 | |
4216 | =item C<2> - faster/larger data structures |
4676 | =item C<2> - faster/larger data structures |
4217 | |
4677 | |
4218 | Replaces the small 2-heap for timer management by a faster 4-heap, larger |
4678 | Replaces the small 2-heap for timer management by a faster 4-heap, larger |
4219 | hash table sizes and so on. This will usually further increase code size |
4679 | hash table sizes and so on. This will usually further increase code size |
4220 | and can additionally have an effect on the size of data structures at |
4680 | and can additionally have an effect on the size of data structures at |
4221 | runtime. |
4681 | runtime. |
4222 | |
4682 | |
|
|
4683 | The default is off when C<__OPTIMIZE_SIZE__> is defined by your compiler |
|
|
4684 | (e.g. gcc with C<-Os>). |
|
|
4685 | |
4223 | =item C<4> - full API configuration |
4686 | =item C<4> - full API configuration |
4224 | |
4687 | |
4225 | This enables priorities (sets C<EV_MAXPRI>=2 and C<EV_MINPRI>=-2), and |
4688 | This enables priorities (sets C<EV_MAXPRI>=2 and C<EV_MINPRI>=-2), and |
4226 | enables multiplicity (C<EV_MULTIPLICITY>=1). |
4689 | enables multiplicity (C<EV_MULTIPLICITY>=1). |
4227 | |
4690 | |
… | |
… | |
4257 | |
4720 | |
4258 | With an intelligent-enough linker (gcc+binutils are intelligent enough |
4721 | With an intelligent-enough linker (gcc+binutils are intelligent enough |
4259 | when you use C<-Wl,--gc-sections -ffunction-sections>) functions unused by |
4722 | when you use C<-Wl,--gc-sections -ffunction-sections>) functions unused by |
4260 | your program might be left out as well - a binary starting a timer and an |
4723 | your program might be left out as well - a binary starting a timer and an |
4261 | I/O watcher then might come out at only 5Kb. |
4724 | I/O watcher then might come out at only 5Kb. |
|
|
4725 | |
|
|
4726 | =item EV_API_STATIC |
|
|
4727 | |
|
|
4728 | If this symbol is defined (by default it is not), then all identifiers |
|
|
4729 | will have static linkage. This means that libev will not export any |
|
|
4730 | identifiers, and you cannot link against libev anymore. This can be useful |
|
|
4731 | when you embed libev, only want to use libev functions in a single file, |
|
|
4732 | and do not want its identifiers to be visible. |
|
|
4733 | |
|
|
4734 | To use this, define C<EV_API_STATIC> and include F<ev.c> in the file that |
|
|
4735 | wants to use libev. |
|
|
4736 | |
|
|
4737 | This option only works when libev is compiled with a C compiler, as C++ |
|
|
4738 | doesn't support the required declaration syntax. |
4262 | |
4739 | |
4263 | =item EV_AVOID_STDIO |
4740 | =item EV_AVOID_STDIO |
4264 | |
4741 | |
4265 | If this is set to C<1> at compiletime, then libev will avoid using stdio |
4742 | If this is set to C<1> at compiletime, then libev will avoid using stdio |
4266 | functions (printf, scanf, perror etc.). This will increase the code size |
4743 | functions (printf, scanf, perror etc.). This will increase the code size |
… | |
… | |
4410 | And a F<ev_cpp.C> implementation file that contains libev proper and is compiled: |
4887 | And a F<ev_cpp.C> implementation file that contains libev proper and is compiled: |
4411 | |
4888 | |
4412 | #include "ev_cpp.h" |
4889 | #include "ev_cpp.h" |
4413 | #include "ev.c" |
4890 | #include "ev.c" |
4414 | |
4891 | |
4415 | =head1 INTERACTION WITH OTHER PROGRAMS OR LIBRARIES |
4892 | =head1 INTERACTION WITH OTHER PROGRAMS, LIBRARIES OR THE ENVIRONMENT |
4416 | |
4893 | |
4417 | =head2 THREADS AND COROUTINES |
4894 | =head2 THREADS AND COROUTINES |
4418 | |
4895 | |
4419 | =head3 THREADS |
4896 | =head3 THREADS |
4420 | |
4897 | |
… | |
… | |
4471 | default loop and triggering an C<ev_async> watcher from the default loop |
4948 | default loop and triggering an C<ev_async> watcher from the default loop |
4472 | watcher callback into the event loop interested in the signal. |
4949 | watcher callback into the event loop interested in the signal. |
4473 | |
4950 | |
4474 | =back |
4951 | =back |
4475 | |
4952 | |
4476 | =head4 THREAD LOCKING EXAMPLE |
4953 | See also L<THREAD LOCKING EXAMPLE>. |
4477 | |
|
|
4478 | Here is a fictitious example of how to run an event loop in a different |
|
|
4479 | thread than where callbacks are being invoked and watchers are |
|
|
4480 | created/added/removed. |
|
|
4481 | |
|
|
4482 | For a real-world example, see the C<EV::Loop::Async> perl module, |
|
|
4483 | which uses exactly this technique (which is suited for many high-level |
|
|
4484 | languages). |
|
|
4485 | |
|
|
4486 | The example uses a pthread mutex to protect the loop data, a condition |
|
|
4487 | variable to wait for callback invocations, an async watcher to notify the |
|
|
4488 | event loop thread and an unspecified mechanism to wake up the main thread. |
|
|
4489 | |
|
|
4490 | First, you need to associate some data with the event loop: |
|
|
4491 | |
|
|
4492 | typedef struct { |
|
|
4493 | mutex_t lock; /* global loop lock */ |
|
|
4494 | ev_async async_w; |
|
|
4495 | thread_t tid; |
|
|
4496 | cond_t invoke_cv; |
|
|
4497 | } userdata; |
|
|
4498 | |
|
|
4499 | void prepare_loop (EV_P) |
|
|
4500 | { |
|
|
4501 | // for simplicity, we use a static userdata struct. |
|
|
4502 | static userdata u; |
|
|
4503 | |
|
|
4504 | ev_async_init (&u->async_w, async_cb); |
|
|
4505 | ev_async_start (EV_A_ &u->async_w); |
|
|
4506 | |
|
|
4507 | pthread_mutex_init (&u->lock, 0); |
|
|
4508 | pthread_cond_init (&u->invoke_cv, 0); |
|
|
4509 | |
|
|
4510 | // now associate this with the loop |
|
|
4511 | ev_set_userdata (EV_A_ u); |
|
|
4512 | ev_set_invoke_pending_cb (EV_A_ l_invoke); |
|
|
4513 | ev_set_loop_release_cb (EV_A_ l_release, l_acquire); |
|
|
4514 | |
|
|
4515 | // then create the thread running ev_loop |
|
|
4516 | pthread_create (&u->tid, 0, l_run, EV_A); |
|
|
4517 | } |
|
|
4518 | |
|
|
4519 | The callback for the C<ev_async> watcher does nothing: the watcher is used |
|
|
4520 | solely to wake up the event loop so it takes notice of any new watchers |
|
|
4521 | that might have been added: |
|
|
4522 | |
|
|
4523 | static void |
|
|
4524 | async_cb (EV_P_ ev_async *w, int revents) |
|
|
4525 | { |
|
|
4526 | // just used for the side effects |
|
|
4527 | } |
|
|
4528 | |
|
|
4529 | The C<l_release> and C<l_acquire> callbacks simply unlock/lock the mutex |
|
|
4530 | protecting the loop data, respectively. |
|
|
4531 | |
|
|
4532 | static void |
|
|
4533 | l_release (EV_P) |
|
|
4534 | { |
|
|
4535 | userdata *u = ev_userdata (EV_A); |
|
|
4536 | pthread_mutex_unlock (&u->lock); |
|
|
4537 | } |
|
|
4538 | |
|
|
4539 | static void |
|
|
4540 | l_acquire (EV_P) |
|
|
4541 | { |
|
|
4542 | userdata *u = ev_userdata (EV_A); |
|
|
4543 | pthread_mutex_lock (&u->lock); |
|
|
4544 | } |
|
|
4545 | |
|
|
4546 | The event loop thread first acquires the mutex, and then jumps straight |
|
|
4547 | into C<ev_run>: |
|
|
4548 | |
|
|
4549 | void * |
|
|
4550 | l_run (void *thr_arg) |
|
|
4551 | { |
|
|
4552 | struct ev_loop *loop = (struct ev_loop *)thr_arg; |
|
|
4553 | |
|
|
4554 | l_acquire (EV_A); |
|
|
4555 | pthread_setcanceltype (PTHREAD_CANCEL_ASYNCHRONOUS, 0); |
|
|
4556 | ev_run (EV_A_ 0); |
|
|
4557 | l_release (EV_A); |
|
|
4558 | |
|
|
4559 | return 0; |
|
|
4560 | } |
|
|
4561 | |
|
|
4562 | Instead of invoking all pending watchers, the C<l_invoke> callback will |
|
|
4563 | signal the main thread via some unspecified mechanism (signals? pipe |
|
|
4564 | writes? C<Async::Interrupt>?) and then waits until all pending watchers |
|
|
4565 | have been called (in a while loop because a) spurious wakeups are possible |
|
|
4566 | and b) skipping inter-thread-communication when there are no pending |
|
|
4567 | watchers is very beneficial): |
|
|
4568 | |
|
|
4569 | static void |
|
|
4570 | l_invoke (EV_P) |
|
|
4571 | { |
|
|
4572 | userdata *u = ev_userdata (EV_A); |
|
|
4573 | |
|
|
4574 | while (ev_pending_count (EV_A)) |
|
|
4575 | { |
|
|
4576 | wake_up_other_thread_in_some_magic_or_not_so_magic_way (); |
|
|
4577 | pthread_cond_wait (&u->invoke_cv, &u->lock); |
|
|
4578 | } |
|
|
4579 | } |
|
|
4580 | |
|
|
4581 | Now, whenever the main thread gets told to invoke pending watchers, it |
|
|
4582 | will grab the lock, call C<ev_invoke_pending> and then signal the loop |
|
|
4583 | thread to continue: |
|
|
4584 | |
|
|
4585 | static void |
|
|
4586 | real_invoke_pending (EV_P) |
|
|
4587 | { |
|
|
4588 | userdata *u = ev_userdata (EV_A); |
|
|
4589 | |
|
|
4590 | pthread_mutex_lock (&u->lock); |
|
|
4591 | ev_invoke_pending (EV_A); |
|
|
4592 | pthread_cond_signal (&u->invoke_cv); |
|
|
4593 | pthread_mutex_unlock (&u->lock); |
|
|
4594 | } |
|
|
4595 | |
|
|
4596 | Whenever you want to start/stop a watcher or do other modifications to an |
|
|
4597 | event loop, you will now have to lock: |
|
|
4598 | |
|
|
4599 | ev_timer timeout_watcher; |
|
|
4600 | userdata *u = ev_userdata (EV_A); |
|
|
4601 | |
|
|
4602 | ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.); |
|
|
4603 | |
|
|
4604 | pthread_mutex_lock (&u->lock); |
|
|
4605 | ev_timer_start (EV_A_ &timeout_watcher); |
|
|
4606 | ev_async_send (EV_A_ &u->async_w); |
|
|
4607 | pthread_mutex_unlock (&u->lock); |
|
|
4608 | |
|
|
4609 | Note that sending the C<ev_async> watcher is required because otherwise |
|
|
4610 | an event loop currently blocking in the kernel will have no knowledge |
|
|
4611 | about the newly added timer. By waking up the loop it will pick up any new |
|
|
4612 | watchers in the next event loop iteration. |
|
|
4613 | |
4954 | |
4614 | =head3 COROUTINES |
4955 | =head3 COROUTINES |
4615 | |
4956 | |
4616 | Libev is very accommodating to coroutines ("cooperative threads"): |
4957 | Libev is very accommodating to coroutines ("cooperative threads"): |
4617 | libev fully supports nesting calls to its functions from different |
4958 | libev fully supports nesting calls to its functions from different |
… | |
… | |
4782 | requires, and its I/O model is fundamentally incompatible with the POSIX |
5123 | requires, and its I/O model is fundamentally incompatible with the POSIX |
4783 | model. Libev still offers limited functionality on this platform in |
5124 | model. Libev still offers limited functionality on this platform in |
4784 | the form of the C<EVBACKEND_SELECT> backend, and only supports socket |
5125 | the form of the C<EVBACKEND_SELECT> backend, and only supports socket |
4785 | descriptors. This only applies when using Win32 natively, not when using |
5126 | descriptors. This only applies when using Win32 natively, not when using |
4786 | e.g. cygwin. Actually, it only applies to the microsofts own compilers, |
5127 | e.g. cygwin. Actually, it only applies to the microsofts own compilers, |
4787 | as every compielr comes with a slightly differently broken/incompatible |
5128 | as every compiler comes with a slightly differently broken/incompatible |
4788 | environment. |
5129 | environment. |
4789 | |
5130 | |
4790 | Lifting these limitations would basically require the full |
5131 | Lifting these limitations would basically require the full |
4791 | re-implementation of the I/O system. If you are into this kind of thing, |
5132 | re-implementation of the I/O system. If you are into this kind of thing, |
4792 | then note that glib does exactly that for you in a very portable way (note |
5133 | then note that glib does exactly that for you in a very portable way (note |
… | |
… | |
4925 | |
5266 | |
4926 | The type C<double> is used to represent timestamps. It is required to |
5267 | The type C<double> is used to represent timestamps. It is required to |
4927 | have at least 51 bits of mantissa (and 9 bits of exponent), which is |
5268 | have at least 51 bits of mantissa (and 9 bits of exponent), which is |
4928 | good enough for at least into the year 4000 with millisecond accuracy |
5269 | good enough for at least into the year 4000 with millisecond accuracy |
4929 | (the design goal for libev). This requirement is overfulfilled by |
5270 | (the design goal for libev). This requirement is overfulfilled by |
4930 | implementations using IEEE 754, which is basically all existing ones. With |
5271 | implementations using IEEE 754, which is basically all existing ones. |
|
|
5272 | |
4931 | IEEE 754 doubles, you get microsecond accuracy until at least 2200. |
5273 | With IEEE 754 doubles, you get microsecond accuracy until at least the |
|
|
5274 | year 2255 (and millisecond accuracy till the year 287396 - by then, libev |
|
|
5275 | is either obsolete or somebody patched it to use C<long double> or |
|
|
5276 | something like that, just kidding). |
4932 | |
5277 | |
4933 | =back |
5278 | =back |
4934 | |
5279 | |
4935 | If you know of other additional requirements drop me a note. |
5280 | If you know of other additional requirements drop me a note. |
4936 | |
5281 | |
… | |
… | |
4998 | =item Processing ev_async_send: O(number_of_async_watchers) |
5343 | =item Processing ev_async_send: O(number_of_async_watchers) |
4999 | |
5344 | |
5000 | =item Processing signals: O(max_signal_number) |
5345 | =item Processing signals: O(max_signal_number) |
5001 | |
5346 | |
5002 | Sending involves a system call I<iff> there were no other C<ev_async_send> |
5347 | Sending involves a system call I<iff> there were no other C<ev_async_send> |
5003 | calls in the current loop iteration. Checking for async and signal events |
5348 | calls in the current loop iteration and the loop is currently |
|
|
5349 | blocked. Checking for async and signal events involves iterating over all |
5004 | involves iterating over all running async watchers or all signal numbers. |
5350 | running async watchers or all signal numbers. |
5005 | |
5351 | |
5006 | =back |
5352 | =back |
5007 | |
5353 | |
5008 | |
5354 | |
5009 | =head1 PORTING FROM LIBEV 3.X TO 4.X |
5355 | =head1 PORTING FROM LIBEV 3.X TO 4.X |
… | |
… | |
5126 | The physical time that is observed. It is apparently strictly monotonic :) |
5472 | The physical time that is observed. It is apparently strictly monotonic :) |
5127 | |
5473 | |
5128 | =item wall-clock time |
5474 | =item wall-clock time |
5129 | |
5475 | |
5130 | The time and date as shown on clocks. Unlike real time, it can actually |
5476 | The time and date as shown on clocks. Unlike real time, it can actually |
5131 | be wrong and jump forwards and backwards, e.g. when the you adjust your |
5477 | be wrong and jump forwards and backwards, e.g. when you adjust your |
5132 | clock. |
5478 | clock. |
5133 | |
5479 | |
5134 | =item watcher |
5480 | =item watcher |
5135 | |
5481 | |
5136 | A data structure that describes interest in certain events. Watchers need |
5482 | A data structure that describes interest in certain events. Watchers need |
… | |
… | |
5139 | =back |
5485 | =back |
5140 | |
5486 | |
5141 | =head1 AUTHOR |
5487 | =head1 AUTHOR |
5142 | |
5488 | |
5143 | Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael |
5489 | Marc Lehmann <libev@schmorp.de>, with repeated corrections by Mikael |
5144 | Magnusson and Emanuele Giaquinta. |
5490 | Magnusson and Emanuele Giaquinta, and minor corrections by many others. |
5145 | |
5491 | |