… | |
… | |
126 | . ds Ae AE |
126 | . ds Ae AE |
127 | .\} |
127 | .\} |
128 | .rm #[ #] #H #V #F C |
128 | .rm #[ #] #H #V #F C |
129 | .\" ======================================================================== |
129 | .\" ======================================================================== |
130 | .\" |
130 | .\" |
131 | .IX Title ""<STANDARD INPUT>" 1" |
131 | .IX Title "EV 1" |
132 | .TH "<STANDARD INPUT>" 1 "2007-12-07" "perl v5.8.8" "User Contributed Perl Documentation" |
132 | .TH EV 1 "2007-12-22" "perl v5.8.8" "User Contributed Perl Documentation" |
133 | .SH "NAME" |
133 | .SH "NAME" |
134 | libev \- a high performance full\-featured event loop written in C |
134 | libev \- a high performance full\-featured event loop written in C |
135 | .SH "SYNOPSIS" |
135 | .SH "SYNOPSIS" |
136 | .IX Header "SYNOPSIS" |
136 | .IX Header "SYNOPSIS" |
137 | .Vb 1 |
137 | .Vb 1 |
… | |
… | |
201 | The newest version of this document is also available as a html-formatted |
201 | The newest version of this document is also available as a html-formatted |
202 | web page you might find easier to navigate when reading it for the first |
202 | web page you might find easier to navigate when reading it for the first |
203 | time: <http://cvs.schmorp.de/libev/ev.html>. |
203 | time: <http://cvs.schmorp.de/libev/ev.html>. |
204 | .PP |
204 | .PP |
205 | Libev is an event loop: you register interest in certain events (such as a |
205 | Libev is an event loop: you register interest in certain events (such as a |
206 | file descriptor being readable or a timeout occuring), and it will manage |
206 | file descriptor being readable or a timeout occurring), and it will manage |
207 | these event sources and provide your program with events. |
207 | these event sources and provide your program with events. |
208 | .PP |
208 | .PP |
209 | To do this, it must take more or less complete control over your process |
209 | To do this, it must take more or less complete control over your process |
210 | (or thread) by executing the \fIevent loop\fR handler, and will then |
210 | (or thread) by executing the \fIevent loop\fR handler, and will then |
211 | communicate events via a callback mechanism. |
211 | communicate events via a callback mechanism. |
… | |
… | |
243 | Libev represents time as a single floating point number, representing the |
243 | Libev represents time as a single floating point number, representing the |
244 | (fractional) number of seconds since the (\s-1POSIX\s0) epoch (somewhere near |
244 | (fractional) number of seconds since the (\s-1POSIX\s0) epoch (somewhere near |
245 | the beginning of 1970, details are complicated, don't ask). This type is |
245 | the beginning of 1970, details are complicated, don't ask). This type is |
246 | called \f(CW\*(C`ev_tstamp\*(C'\fR, which is what you should use too. It usually aliases |
246 | called \f(CW\*(C`ev_tstamp\*(C'\fR, which is what you should use too. It usually aliases |
247 | to the \f(CW\*(C`double\*(C'\fR type in C, and when you need to do any calculations on |
247 | to the \f(CW\*(C`double\*(C'\fR type in C, and when you need to do any calculations on |
248 | it, you should treat it as such. |
248 | it, you should treat it as some floatingpoint value. Unlike the name |
|
|
249 | component \f(CW\*(C`stamp\*(C'\fR might indicate, it is also used for time differences |
|
|
250 | throughout libev. |
249 | .SH "GLOBAL FUNCTIONS" |
251 | .SH "GLOBAL FUNCTIONS" |
250 | .IX Header "GLOBAL FUNCTIONS" |
252 | .IX Header "GLOBAL FUNCTIONS" |
251 | These functions can be called anytime, even before initialising the |
253 | These functions can be called anytime, even before initialising the |
252 | library in any way. |
254 | library in any way. |
253 | .IP "ev_tstamp ev_time ()" 4 |
255 | .IP "ev_tstamp ev_time ()" 4 |
254 | .IX Item "ev_tstamp ev_time ()" |
256 | .IX Item "ev_tstamp ev_time ()" |
255 | Returns the current time as libev would use it. Please note that the |
257 | Returns the current time as libev would use it. Please note that the |
256 | \&\f(CW\*(C`ev_now\*(C'\fR function is usually faster and also often returns the timestamp |
258 | \&\f(CW\*(C`ev_now\*(C'\fR function is usually faster and also often returns the timestamp |
257 | you actually want to know. |
259 | you actually want to know. |
|
|
260 | .IP "void ev_sleep (ev_tstamp interval)" 4 |
|
|
261 | .IX Item "void ev_sleep (ev_tstamp interval)" |
|
|
262 | Sleep for the given interval: The current thread will be blocked until |
|
|
263 | either it is interrupted or the given time interval has passed. Basically |
|
|
264 | this is a subsecond-resolution \f(CW\*(C`sleep ()\*(C'\fR. |
258 | .IP "int ev_version_major ()" 4 |
265 | .IP "int ev_version_major ()" 4 |
259 | .IX Item "int ev_version_major ()" |
266 | .IX Item "int ev_version_major ()" |
260 | .PD 0 |
267 | .PD 0 |
261 | .IP "int ev_version_minor ()" 4 |
268 | .IP "int ev_version_minor ()" 4 |
262 | .IX Item "int ev_version_minor ()" |
269 | .IX Item "int ev_version_minor ()" |
263 | .PD |
270 | .PD |
264 | You can find out the major and minor version numbers of the library |
271 | You can find out the major and minor \s-1ABI\s0 version numbers of the library |
265 | you linked against by calling the functions \f(CW\*(C`ev_version_major\*(C'\fR and |
272 | you linked against by calling the functions \f(CW\*(C`ev_version_major\*(C'\fR and |
266 | \&\f(CW\*(C`ev_version_minor\*(C'\fR. If you want, you can compare against the global |
273 | \&\f(CW\*(C`ev_version_minor\*(C'\fR. If you want, you can compare against the global |
267 | symbols \f(CW\*(C`EV_VERSION_MAJOR\*(C'\fR and \f(CW\*(C`EV_VERSION_MINOR\*(C'\fR, which specify the |
274 | symbols \f(CW\*(C`EV_VERSION_MAJOR\*(C'\fR and \f(CW\*(C`EV_VERSION_MINOR\*(C'\fR, which specify the |
268 | version of the library your program was compiled against. |
275 | version of the library your program was compiled against. |
269 | .Sp |
276 | .Sp |
|
|
277 | These version numbers refer to the \s-1ABI\s0 version of the library, not the |
|
|
278 | release version. |
|
|
279 | .Sp |
270 | Usually, it's a good idea to terminate if the major versions mismatch, |
280 | Usually, it's a good idea to terminate if the major versions mismatch, |
271 | as this indicates an incompatible change. Minor versions are usually |
281 | as this indicates an incompatible change. Minor versions are usually |
272 | compatible to older versions, so a larger minor version alone is usually |
282 | compatible to older versions, so a larger minor version alone is usually |
273 | not a problem. |
283 | not a problem. |
274 | .Sp |
284 | .Sp |
275 | Example: Make sure we haven't accidentally been linked against the wrong |
285 | Example: Make sure we haven't accidentally been linked against the wrong |
276 | version. |
286 | version. |
… | |
… | |
454 | lot of inactive fds). It scales similarly to select, i.e. O(total_fds). |
464 | lot of inactive fds). It scales similarly to select, i.e. O(total_fds). |
455 | .ie n .IP """EVBACKEND_EPOLL"" (value 4, Linux)" 4 |
465 | .ie n .IP """EVBACKEND_EPOLL"" (value 4, Linux)" 4 |
456 | .el .IP "\f(CWEVBACKEND_EPOLL\fR (value 4, Linux)" 4 |
466 | .el .IP "\f(CWEVBACKEND_EPOLL\fR (value 4, Linux)" 4 |
457 | .IX Item "EVBACKEND_EPOLL (value 4, Linux)" |
467 | .IX Item "EVBACKEND_EPOLL (value 4, Linux)" |
458 | For few fds, this backend is a bit little slower than poll and select, |
468 | For few fds, this backend is a bit little slower than poll and select, |
459 | but it scales phenomenally better. While poll and select usually scale like |
469 | but it scales phenomenally better. While poll and select usually scale |
460 | O(total_fds) where n is the total number of fds (or the highest fd), epoll scales |
470 | like O(total_fds) where n is the total number of fds (or the highest fd), |
461 | either O(1) or O(active_fds). |
471 | epoll scales either O(1) or O(active_fds). The epoll design has a number |
|
|
472 | of shortcomings, such as silently dropping events in some hard-to-detect |
|
|
473 | cases and rewiring a syscall per fd change, no fork support and bad |
|
|
474 | support for dup: |
462 | .Sp |
475 | .Sp |
463 | While stopping and starting an I/O watcher in the same iteration will |
476 | While stopping, setting and starting an I/O watcher in the same iteration |
464 | result in some caching, there is still a syscall per such incident |
477 | will result in some caching, there is still a syscall per such incident |
465 | (because the fd could point to a different file description now), so its |
478 | (because the fd could point to a different file description now), so its |
466 | best to avoid that. Also, \fIdup()\fRed file descriptors might not work very |
479 | best to avoid that. Also, \f(CW\*(C`dup ()\*(C'\fR'ed file descriptors might not work |
467 | well if you register events for both fds. |
480 | very well if you register events for both fds. |
468 | .Sp |
481 | .Sp |
469 | Please note that epoll sometimes generates spurious notifications, so you |
482 | Please note that epoll sometimes generates spurious notifications, so you |
470 | need to use non-blocking I/O or other means to avoid blocking when no data |
483 | need to use non-blocking I/O or other means to avoid blocking when no data |
471 | (or space) is available. |
484 | (or space) is available. |
472 | .ie n .IP """EVBACKEND_KQUEUE"" (value 8, most \s-1BSD\s0 clones)" 4 |
485 | .ie n .IP """EVBACKEND_KQUEUE"" (value 8, most \s-1BSD\s0 clones)" 4 |
473 | .el .IP "\f(CWEVBACKEND_KQUEUE\fR (value 8, most \s-1BSD\s0 clones)" 4 |
486 | .el .IP "\f(CWEVBACKEND_KQUEUE\fR (value 8, most \s-1BSD\s0 clones)" 4 |
474 | .IX Item "EVBACKEND_KQUEUE (value 8, most BSD clones)" |
487 | .IX Item "EVBACKEND_KQUEUE (value 8, most BSD clones)" |
475 | Kqueue deserves special mention, as at the time of this writing, it |
488 | Kqueue deserves special mention, as at the time of this writing, it |
476 | was broken on all BSDs except NetBSD (usually it doesn't work with |
489 | was broken on \fIall\fR BSDs (usually it doesn't work with anything but |
477 | anything but sockets and pipes, except on Darwin, where of course its |
490 | sockets and pipes, except on Darwin, where of course it's completely |
|
|
491 | useless. On NetBSD, it seems to work for all the \s-1FD\s0 types I tested, so it |
478 | completely useless). For this reason its not being \*(L"autodetected\*(R" |
492 | is used by default there). For this reason it's not being \*(L"autodetected\*(R" |
479 | unless you explicitly specify it explicitly in the flags (i.e. using |
493 | unless you explicitly specify it explicitly in the flags (i.e. using |
480 | \&\f(CW\*(C`EVBACKEND_KQUEUE\*(C'\fR). |
494 | \&\f(CW\*(C`EVBACKEND_KQUEUE\*(C'\fR) or libev was compiled on a known-to-be-good (\-enough) |
|
|
495 | system like NetBSD. |
481 | .Sp |
496 | .Sp |
482 | It scales in the same way as the epoll backend, but the interface to the |
497 | It scales in the same way as the epoll backend, but the interface to the |
483 | kernel is more efficient (which says nothing about its actual speed, of |
498 | kernel is more efficient (which says nothing about its actual speed, |
484 | course). While starting and stopping an I/O watcher does not cause an |
499 | of course). While stopping, setting and starting an I/O watcher does |
485 | extra syscall as with epoll, it still adds up to four event changes per |
500 | never cause an extra syscall as with epoll, it still adds up to two event |
486 | incident, so its best to avoid that. |
501 | changes per incident, support for \f(CW\*(C`fork ()\*(C'\fR is very bad and it drops fds |
|
|
502 | silently in similarly hard-to-detetc cases. |
487 | .ie n .IP """EVBACKEND_DEVPOLL"" (value 16, Solaris 8)" 4 |
503 | .ie n .IP """EVBACKEND_DEVPOLL"" (value 16, Solaris 8)" 4 |
488 | .el .IP "\f(CWEVBACKEND_DEVPOLL\fR (value 16, Solaris 8)" 4 |
504 | .el .IP "\f(CWEVBACKEND_DEVPOLL\fR (value 16, Solaris 8)" 4 |
489 | .IX Item "EVBACKEND_DEVPOLL (value 16, Solaris 8)" |
505 | .IX Item "EVBACKEND_DEVPOLL (value 16, Solaris 8)" |
490 | This is not implemented yet (and might never be). |
506 | This is not implemented yet (and might never be). |
491 | .ie n .IP """EVBACKEND_PORT"" (value 32, Solaris 10)" 4 |
507 | .ie n .IP """EVBACKEND_PORT"" (value 32, Solaris 10)" 4 |
492 | .el .IP "\f(CWEVBACKEND_PORT\fR (value 32, Solaris 10)" 4 |
508 | .el .IP "\f(CWEVBACKEND_PORT\fR (value 32, Solaris 10)" 4 |
493 | .IX Item "EVBACKEND_PORT (value 32, Solaris 10)" |
509 | .IX Item "EVBACKEND_PORT (value 32, Solaris 10)" |
494 | This uses the Solaris 10 port mechanism. As with everything on Solaris, |
510 | This uses the Solaris 10 event port mechanism. As with everything on Solaris, |
495 | it's really slow, but it still scales very well (O(active_fds)). |
511 | it's really slow, but it still scales very well (O(active_fds)). |
496 | .Sp |
512 | .Sp |
497 | Please note that solaris ports can result in a lot of spurious |
513 | Please note that solaris event ports can deliver a lot of spurious |
498 | notifications, so you need to use non-blocking I/O or other means to avoid |
514 | notifications, so you need to use non-blocking I/O or other means to avoid |
499 | blocking when no data (or space) is available. |
515 | blocking when no data (or space) is available. |
500 | .ie n .IP """EVBACKEND_ALL""" 4 |
516 | .ie n .IP """EVBACKEND_ALL""" 4 |
501 | .el .IP "\f(CWEVBACKEND_ALL\fR" 4 |
517 | .el .IP "\f(CWEVBACKEND_ALL\fR" 4 |
502 | .IX Item "EVBACKEND_ALL" |
518 | .IX Item "EVBACKEND_ALL" |
… | |
… | |
552 | Destroys the default loop again (frees all memory and kernel state |
568 | Destroys the default loop again (frees all memory and kernel state |
553 | etc.). None of the active event watchers will be stopped in the normal |
569 | etc.). None of the active event watchers will be stopped in the normal |
554 | sense, so e.g. \f(CW\*(C`ev_is_active\*(C'\fR might still return true. It is your |
570 | sense, so e.g. \f(CW\*(C`ev_is_active\*(C'\fR might still return true. It is your |
555 | responsibility to either stop all watchers cleanly yoursef \fIbefore\fR |
571 | responsibility to either stop all watchers cleanly yoursef \fIbefore\fR |
556 | calling this function, or cope with the fact afterwards (which is usually |
572 | calling this function, or cope with the fact afterwards (which is usually |
557 | the easiest thing, youc na just ignore the watchers and/or \f(CW\*(C`free ()\*(C'\fR them |
573 | the easiest thing, you can just ignore the watchers and/or \f(CW\*(C`free ()\*(C'\fR them |
558 | for example). |
574 | for example). |
|
|
575 | .Sp |
|
|
576 | Note that certain global state, such as signal state, will not be freed by |
|
|
577 | this function, and related watchers (such as signal and child watchers) |
|
|
578 | would need to be stopped manually. |
|
|
579 | .Sp |
|
|
580 | In general it is not advisable to call this function except in the |
|
|
581 | rare occasion where you really need to free e.g. the signal handling |
|
|
582 | pipe fds. If you need dynamically allocated loops it is better to use |
|
|
583 | \&\f(CW\*(C`ev_loop_new\*(C'\fR and \f(CW\*(C`ev_loop_destroy\*(C'\fR). |
559 | .IP "ev_loop_destroy (loop)" 4 |
584 | .IP "ev_loop_destroy (loop)" 4 |
560 | .IX Item "ev_loop_destroy (loop)" |
585 | .IX Item "ev_loop_destroy (loop)" |
561 | Like \f(CW\*(C`ev_default_destroy\*(C'\fR, but destroys an event loop created by an |
586 | Like \f(CW\*(C`ev_default_destroy\*(C'\fR, but destroys an event loop created by an |
562 | earlier call to \f(CW\*(C`ev_loop_new\*(C'\fR. |
587 | earlier call to \f(CW\*(C`ev_loop_new\*(C'\fR. |
563 | .IP "ev_default_fork ()" 4 |
588 | .IP "ev_default_fork ()" 4 |
… | |
… | |
604 | .IX Item "ev_tstamp ev_now (loop)" |
629 | .IX Item "ev_tstamp ev_now (loop)" |
605 | Returns the current \*(L"event loop time\*(R", which is the time the event loop |
630 | Returns the current \*(L"event loop time\*(R", which is the time the event loop |
606 | received events and started processing them. This timestamp does not |
631 | received events and started processing them. This timestamp does not |
607 | change as long as callbacks are being processed, and this is also the base |
632 | change as long as callbacks are being processed, and this is also the base |
608 | time used for relative timers. You can treat it as the timestamp of the |
633 | time used for relative timers. You can treat it as the timestamp of the |
609 | event occuring (or more correctly, libev finding out about it). |
634 | event occurring (or more correctly, libev finding out about it). |
610 | .IP "ev_loop (loop, int flags)" 4 |
635 | .IP "ev_loop (loop, int flags)" 4 |
611 | .IX Item "ev_loop (loop, int flags)" |
636 | .IX Item "ev_loop (loop, int flags)" |
612 | Finally, this is it, the event handler. This function usually is called |
637 | Finally, this is it, the event handler. This function usually is called |
613 | after you initialised all your watchers and you want to start handling |
638 | after you initialised all your watchers and you want to start handling |
614 | events. |
639 | events. |
… | |
… | |
634 | libev watchers. However, a pair of \f(CW\*(C`ev_prepare\*(C'\fR/\f(CW\*(C`ev_check\*(C'\fR watchers is |
659 | libev watchers. However, a pair of \f(CW\*(C`ev_prepare\*(C'\fR/\f(CW\*(C`ev_check\*(C'\fR watchers is |
635 | usually a better approach for this kind of thing. |
660 | usually a better approach for this kind of thing. |
636 | .Sp |
661 | .Sp |
637 | Here are the gory details of what \f(CW\*(C`ev_loop\*(C'\fR does: |
662 | Here are the gory details of what \f(CW\*(C`ev_loop\*(C'\fR does: |
638 | .Sp |
663 | .Sp |
639 | .Vb 18 |
664 | .Vb 19 |
|
|
665 | \& - Before the first iteration, call any pending watchers. |
640 | \& * If there are no active watchers (reference count is zero), return. |
666 | \& * If there are no active watchers (reference count is zero), return. |
641 | \& - Queue prepare watchers and then call all outstanding watchers. |
667 | \& - Queue all prepare watchers and then call all outstanding watchers. |
642 | \& - If we have been forked, recreate the kernel state. |
668 | \& - If we have been forked, recreate the kernel state. |
643 | \& - Update the kernel state with all outstanding changes. |
669 | \& - Update the kernel state with all outstanding changes. |
644 | \& - Update the "event loop time". |
670 | \& - Update the "event loop time". |
645 | \& - Calculate for how long to block. |
671 | \& - Calculate for how long to block. |
646 | \& - Block the process, waiting for any events. |
672 | \& - Block the process, waiting for any events. |
… | |
… | |
703 | .Sp |
729 | .Sp |
704 | .Vb 2 |
730 | .Vb 2 |
705 | \& ev_ref (loop); |
731 | \& ev_ref (loop); |
706 | \& ev_signal_stop (loop, &exitsig); |
732 | \& ev_signal_stop (loop, &exitsig); |
707 | .Ve |
733 | .Ve |
|
|
734 | .IP "ev_set_io_collect_interval (ev_tstamp interval)" 4 |
|
|
735 | .IX Item "ev_set_io_collect_interval (ev_tstamp interval)" |
|
|
736 | .PD 0 |
|
|
737 | .IP "ev_set_timeout_collect_interval (ev_tstamp interval)" 4 |
|
|
738 | .IX Item "ev_set_timeout_collect_interval (ev_tstamp interval)" |
|
|
739 | .PD |
|
|
740 | These advanced functions influence the time that libev will spend waiting |
|
|
741 | for events. Both are by default \f(CW0\fR, meaning that libev will try to |
|
|
742 | invoke timer/periodic callbacks and I/O callbacks with minimum latency. |
|
|
743 | .Sp |
|
|
744 | Setting these to a higher value (the \f(CW\*(C`interval\*(C'\fR \fImust\fR be >= \f(CW0\fR) |
|
|
745 | allows libev to delay invocation of I/O and timer/periodic callbacks to |
|
|
746 | increase efficiency of loop iterations. |
|
|
747 | .Sp |
|
|
748 | The background is that sometimes your program runs just fast enough to |
|
|
749 | handle one (or very few) event(s) per loop iteration. While this makes |
|
|
750 | the program responsive, it also wastes a lot of \s-1CPU\s0 time to poll for new |
|
|
751 | events, especially with backends like \f(CW\*(C`select ()\*(C'\fR which have a high |
|
|
752 | overhead for the actual polling but can deliver many events at once. |
|
|
753 | .Sp |
|
|
754 | By setting a higher \fIio collect interval\fR you allow libev to spend more |
|
|
755 | time collecting I/O events, so you can handle more events per iteration, |
|
|
756 | at the cost of increasing latency. Timeouts (both \f(CW\*(C`ev_periodic\*(C'\fR and |
|
|
757 | \&\f(CW\*(C`ev_timer\*(C'\fR) will be not affected. |
|
|
758 | .Sp |
|
|
759 | Likewise, by setting a higher \fItimeout collect interval\fR you allow libev |
|
|
760 | to spend more time collecting timeouts, at the expense of increased |
|
|
761 | latency (the watcher callback will be called later). \f(CW\*(C`ev_io\*(C'\fR watchers |
|
|
762 | will not be affected. |
|
|
763 | .Sp |
|
|
764 | Many programs can usually benefit by setting the io collect interval to |
|
|
765 | a value near \f(CW0.1\fR or so, which is often enough for interactive servers |
|
|
766 | (of course not for games), likewise for timeouts. It usually doesn't make |
|
|
767 | much sense to set it to a lower value than \f(CW0.01\fR, as this approsaches |
|
|
768 | the timing granularity of most systems. |
708 | .SH "ANATOMY OF A WATCHER" |
769 | .SH "ANATOMY OF A WATCHER" |
709 | .IX Header "ANATOMY OF A WATCHER" |
770 | .IX Header "ANATOMY OF A WATCHER" |
710 | A watcher is a structure that you create and register to record your |
771 | A watcher is a structure that you create and register to record your |
711 | interest in some event. For instance, if you want to wait for \s-1STDIN\s0 to |
772 | interest in some event. For instance, if you want to wait for \s-1STDIN\s0 to |
712 | become readable, you would create an \f(CW\*(C`ev_io\*(C'\fR watcher for that: |
773 | become readable, you would create an \f(CW\*(C`ev_io\*(C'\fR watcher for that: |
… | |
… | |
889 | .IP "bool ev_is_pending (ev_TYPE *watcher)" 4 |
950 | .IP "bool ev_is_pending (ev_TYPE *watcher)" 4 |
890 | .IX Item "bool ev_is_pending (ev_TYPE *watcher)" |
951 | .IX Item "bool ev_is_pending (ev_TYPE *watcher)" |
891 | Returns a true value iff the watcher is pending, (i.e. it has outstanding |
952 | Returns a true value iff the watcher is pending, (i.e. it has outstanding |
892 | events but its callback has not yet been invoked). As long as a watcher |
953 | events but its callback has not yet been invoked). As long as a watcher |
893 | is pending (but not active) you must not call an init function on it (but |
954 | is pending (but not active) you must not call an init function on it (but |
894 | \&\f(CW\*(C`ev_TYPE_set\*(C'\fR is safe) and you must make sure the watcher is available to |
955 | \&\f(CW\*(C`ev_TYPE_set\*(C'\fR is safe), you must not change its priority, and you must |
895 | libev (e.g. you cnanot \f(CW\*(C`free ()\*(C'\fR it). |
956 | make sure the watcher is available to libev (e.g. you cannot \f(CW\*(C`free ()\*(C'\fR |
|
|
957 | it). |
896 | .IP "callback ev_cb (ev_TYPE *watcher)" 4 |
958 | .IP "callback ev_cb (ev_TYPE *watcher)" 4 |
897 | .IX Item "callback ev_cb (ev_TYPE *watcher)" |
959 | .IX Item "callback ev_cb (ev_TYPE *watcher)" |
898 | Returns the callback currently set on the watcher. |
960 | Returns the callback currently set on the watcher. |
899 | .IP "ev_cb_set (ev_TYPE *watcher, callback)" 4 |
961 | .IP "ev_cb_set (ev_TYPE *watcher, callback)" 4 |
900 | .IX Item "ev_cb_set (ev_TYPE *watcher, callback)" |
962 | .IX Item "ev_cb_set (ev_TYPE *watcher, callback)" |
… | |
… | |
918 | watchers on the same event and make sure one is called first. |
980 | watchers on the same event and make sure one is called first. |
919 | .Sp |
981 | .Sp |
920 | If you need to suppress invocation when higher priority events are pending |
982 | If you need to suppress invocation when higher priority events are pending |
921 | you need to look at \f(CW\*(C`ev_idle\*(C'\fR watchers, which provide this functionality. |
983 | you need to look at \f(CW\*(C`ev_idle\*(C'\fR watchers, which provide this functionality. |
922 | .Sp |
984 | .Sp |
|
|
985 | You \fImust not\fR change the priority of a watcher as long as it is active or |
|
|
986 | pending. |
|
|
987 | .Sp |
923 | The default priority used by watchers when no priority has been set is |
988 | The default priority used by watchers when no priority has been set is |
924 | always \f(CW0\fR, which is supposed to not be too high and not be too low :). |
989 | always \f(CW0\fR, which is supposed to not be too high and not be too low :). |
925 | .Sp |
990 | .Sp |
926 | Setting a priority outside the range of \f(CW\*(C`EV_MINPRI\*(C'\fR to \f(CW\*(C`EV_MAXPRI\*(C'\fR is |
991 | Setting a priority outside the range of \f(CW\*(C`EV_MINPRI\*(C'\fR to \f(CW\*(C`EV_MAXPRI\*(C'\fR is |
927 | fine, as long as you do not mind that the priority value you query might |
992 | fine, as long as you do not mind that the priority value you query might |
928 | or might not have been adjusted to be within valid range. |
993 | or might not have been adjusted to be within valid range. |
|
|
994 | .IP "ev_invoke (loop, ev_TYPE *watcher, int revents)" 4 |
|
|
995 | .IX Item "ev_invoke (loop, ev_TYPE *watcher, int revents)" |
|
|
996 | Invoke the \f(CW\*(C`watcher\*(C'\fR with the given \f(CW\*(C`loop\*(C'\fR and \f(CW\*(C`revents\*(C'\fR. Neither |
|
|
997 | \&\f(CW\*(C`loop\*(C'\fR nor \f(CW\*(C`revents\*(C'\fR need to be valid as long as the watcher callback |
|
|
998 | can deal with that fact. |
|
|
999 | .IP "int ev_clear_pending (loop, ev_TYPE *watcher)" 4 |
|
|
1000 | .IX Item "int ev_clear_pending (loop, ev_TYPE *watcher)" |
|
|
1001 | If the watcher is pending, this function returns clears its pending status |
|
|
1002 | and returns its \f(CW\*(C`revents\*(C'\fR bitset (as if its callback was invoked). If the |
|
|
1003 | watcher isn't pending it does nothing and returns \f(CW0\fR. |
929 | .Sh "\s-1ASSOCIATING\s0 \s-1CUSTOM\s0 \s-1DATA\s0 \s-1WITH\s0 A \s-1WATCHER\s0" |
1004 | .Sh "\s-1ASSOCIATING\s0 \s-1CUSTOM\s0 \s-1DATA\s0 \s-1WITH\s0 A \s-1WATCHER\s0" |
930 | .IX Subsection "ASSOCIATING CUSTOM DATA WITH A WATCHER" |
1005 | .IX Subsection "ASSOCIATING CUSTOM DATA WITH A WATCHER" |
931 | Each watcher has, by default, a member \f(CW\*(C`void *data\*(C'\fR that you can change |
1006 | Each watcher has, by default, a member \f(CW\*(C`void *data\*(C'\fR that you can change |
932 | and read at any time, libev will completely ignore it. This can be used |
1007 | and read at any time, libev will completely ignore it. This can be used |
933 | to associate arbitrary data with your watcher. If you need more data and |
1008 | to associate arbitrary data with your watcher. If you need more data and |
… | |
… | |
1047 | If you cannot run the fd in non-blocking mode (for example you should not |
1122 | If you cannot run the fd in non-blocking mode (for example you should not |
1048 | play around with an Xlib connection), then you have to seperately re-test |
1123 | play around with an Xlib connection), then you have to seperately re-test |
1049 | whether a file descriptor is really ready with a known-to-be good interface |
1124 | whether a file descriptor is really ready with a known-to-be good interface |
1050 | such as poll (fortunately in our Xlib example, Xlib already does this on |
1125 | such as poll (fortunately in our Xlib example, Xlib already does this on |
1051 | its own, so its quite safe to use). |
1126 | its own, so its quite safe to use). |
|
|
1127 | .PP |
|
|
1128 | \fIThe special problem of disappearing file descriptors\fR |
|
|
1129 | .IX Subsection "The special problem of disappearing file descriptors" |
|
|
1130 | .PP |
|
|
1131 | Some backends (e.g. kqueue, epoll) need to be told about closing a file |
|
|
1132 | descriptor (either by calling \f(CW\*(C`close\*(C'\fR explicitly or by any other means, |
|
|
1133 | such as \f(CW\*(C`dup\*(C'\fR). The reason is that you register interest in some file |
|
|
1134 | descriptor, but when it goes away, the operating system will silently drop |
|
|
1135 | this interest. If another file descriptor with the same number then is |
|
|
1136 | registered with libev, there is no efficient way to see that this is, in |
|
|
1137 | fact, a different file descriptor. |
|
|
1138 | .PP |
|
|
1139 | To avoid having to explicitly tell libev about such cases, libev follows |
|
|
1140 | the following policy: Each time \f(CW\*(C`ev_io_set\*(C'\fR is being called, libev |
|
|
1141 | will assume that this is potentially a new file descriptor, otherwise |
|
|
1142 | it is assumed that the file descriptor stays the same. That means that |
|
|
1143 | you \fIhave\fR to call \f(CW\*(C`ev_io_set\*(C'\fR (or \f(CW\*(C`ev_io_init\*(C'\fR) when you change the |
|
|
1144 | descriptor even if the file descriptor number itself did not change. |
|
|
1145 | .PP |
|
|
1146 | This is how one would do it normally anyway, the important point is that |
|
|
1147 | the libev application should not optimise around libev but should leave |
|
|
1148 | optimisations to libev. |
|
|
1149 | .PP |
|
|
1150 | \fIThe special problem of dup'ed file descriptors\fR |
|
|
1151 | .IX Subsection "The special problem of dup'ed file descriptors" |
|
|
1152 | .PP |
|
|
1153 | Some backends (e.g. epoll), cannot register events for file descriptors, |
|
|
1154 | but only events for the underlying file descriptions. That menas when you |
|
|
1155 | have \f(CW\*(C`dup ()\*(C'\fR'ed file descriptors and register events for them, only one |
|
|
1156 | file descriptor might actually receive events. |
|
|
1157 | .PP |
|
|
1158 | There is no workaorund possible except not registering events |
|
|
1159 | for potentially \f(CW\*(C`dup ()\*(C'\fR'ed file descriptors or to resort to |
|
|
1160 | \&\f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or \f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
|
|
1161 | .PP |
|
|
1162 | \fIThe special problem of fork\fR |
|
|
1163 | .IX Subsection "The special problem of fork" |
|
|
1164 | .PP |
|
|
1165 | Some backends (epoll, kqueue) do not support \f(CW\*(C`fork ()\*(C'\fR at all or exhibit |
|
|
1166 | useless behaviour. Libev fully supports fork, but needs to be told about |
|
|
1167 | it in the child. |
|
|
1168 | .PP |
|
|
1169 | To support fork in your programs, you either have to call |
|
|
1170 | \&\f(CW\*(C`ev_default_fork ()\*(C'\fR or \f(CW\*(C`ev_loop_fork ()\*(C'\fR after a fork in the child, |
|
|
1171 | enable \f(CW\*(C`EVFLAG_FORKCHECK\*(C'\fR, or resort to \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or |
|
|
1172 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
|
|
1173 | .PP |
|
|
1174 | \fIWatcher-Specific Functions\fR |
|
|
1175 | .IX Subsection "Watcher-Specific Functions" |
1052 | .IP "ev_io_init (ev_io *, callback, int fd, int events)" 4 |
1176 | .IP "ev_io_init (ev_io *, callback, int fd, int events)" 4 |
1053 | .IX Item "ev_io_init (ev_io *, callback, int fd, int events)" |
1177 | .IX Item "ev_io_init (ev_io *, callback, int fd, int events)" |
1054 | .PD 0 |
1178 | .PD 0 |
1055 | .IP "ev_io_set (ev_io *, int fd, int events)" 4 |
1179 | .IP "ev_io_set (ev_io *, int fd, int events)" 4 |
1056 | .IX Item "ev_io_set (ev_io *, int fd, int events)" |
1180 | .IX Item "ev_io_set (ev_io *, int fd, int events)" |
… | |
… | |
1109 | .Ve |
1233 | .Ve |
1110 | .PP |
1234 | .PP |
1111 | The callback is guarenteed to be invoked only when its timeout has passed, |
1235 | The callback is guarenteed to be invoked only when its timeout has passed, |
1112 | but if multiple timers become ready during the same loop iteration then |
1236 | but if multiple timers become ready during the same loop iteration then |
1113 | order of execution is undefined. |
1237 | order of execution is undefined. |
|
|
1238 | .PP |
|
|
1239 | \fIWatcher-Specific Functions and Data Members\fR |
|
|
1240 | .IX Subsection "Watcher-Specific Functions and Data Members" |
1114 | .IP "ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)" 4 |
1241 | .IP "ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)" 4 |
1115 | .IX Item "ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)" |
1242 | .IX Item "ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)" |
1116 | .PD 0 |
1243 | .PD 0 |
1117 | .IP "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" 4 |
1244 | .IP "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" 4 |
1118 | .IX Item "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" |
1245 | .IX Item "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" |
… | |
… | |
1220 | but on wallclock time (absolute time). You can tell a periodic watcher |
1347 | but on wallclock time (absolute time). You can tell a periodic watcher |
1221 | to trigger \*(L"at\*(R" some specific point in time. For example, if you tell a |
1348 | to trigger \*(L"at\*(R" some specific point in time. For example, if you tell a |
1222 | periodic watcher to trigger in 10 seconds (by specifiying e.g. \f(CW\*(C`ev_now () |
1349 | periodic watcher to trigger in 10 seconds (by specifiying e.g. \f(CW\*(C`ev_now () |
1223 | + 10.\*(C'\fR) and then reset your system clock to the last year, then it will |
1350 | + 10.\*(C'\fR) and then reset your system clock to the last year, then it will |
1224 | take a year to trigger the event (unlike an \f(CW\*(C`ev_timer\*(C'\fR, which would trigger |
1351 | take a year to trigger the event (unlike an \f(CW\*(C`ev_timer\*(C'\fR, which would trigger |
1225 | roughly 10 seconds later and of course not if you reset your system time |
1352 | roughly 10 seconds later). |
1226 | again). |
|
|
1227 | .PP |
1353 | .PP |
1228 | They can also be used to implement vastly more complex timers, such as |
1354 | They can also be used to implement vastly more complex timers, such as |
1229 | triggering an event on eahc midnight, local time. |
1355 | triggering an event on each midnight, local time or other, complicated, |
|
|
1356 | rules. |
1230 | .PP |
1357 | .PP |
1231 | As with timers, the callback is guarenteed to be invoked only when the |
1358 | As with timers, the callback is guarenteed to be invoked only when the |
1232 | time (\f(CW\*(C`at\*(C'\fR) has been passed, but if multiple periodic timers become ready |
1359 | time (\f(CW\*(C`at\*(C'\fR) has been passed, but if multiple periodic timers become ready |
1233 | during the same loop iteration then order of execution is undefined. |
1360 | during the same loop iteration then order of execution is undefined. |
|
|
1361 | .PP |
|
|
1362 | \fIWatcher-Specific Functions and Data Members\fR |
|
|
1363 | .IX Subsection "Watcher-Specific Functions and Data Members" |
1234 | .IP "ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)" 4 |
1364 | .IP "ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)" 4 |
1235 | .IX Item "ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)" |
1365 | .IX Item "ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)" |
1236 | .PD 0 |
1366 | .PD 0 |
1237 | .IP "ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)" 4 |
1367 | .IP "ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)" 4 |
1238 | .IX Item "ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)" |
1368 | .IX Item "ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)" |
1239 | .PD |
1369 | .PD |
1240 | Lots of arguments, lets sort it out... There are basically three modes of |
1370 | Lots of arguments, lets sort it out... There are basically three modes of |
1241 | operation, and we will explain them from simplest to complex: |
1371 | operation, and we will explain them from simplest to complex: |
1242 | .RS 4 |
1372 | .RS 4 |
1243 | .IP "* absolute timer (interval = reschedule_cb = 0)" 4 |
1373 | .IP "* absolute timer (at = time, interval = reschedule_cb = 0)" 4 |
1244 | .IX Item "absolute timer (interval = reschedule_cb = 0)" |
1374 | .IX Item "absolute timer (at = time, interval = reschedule_cb = 0)" |
1245 | In this configuration the watcher triggers an event at the wallclock time |
1375 | In this configuration the watcher triggers an event at the wallclock time |
1246 | \&\f(CW\*(C`at\*(C'\fR and doesn't repeat. It will not adjust when a time jump occurs, |
1376 | \&\f(CW\*(C`at\*(C'\fR and doesn't repeat. It will not adjust when a time jump occurs, |
1247 | that is, if it is to be run at January 1st 2011 then it will run when the |
1377 | that is, if it is to be run at January 1st 2011 then it will run when the |
1248 | system time reaches or surpasses this time. |
1378 | system time reaches or surpasses this time. |
1249 | .IP "* non-repeating interval timer (interval > 0, reschedule_cb = 0)" 4 |
1379 | .IP "* non-repeating interval timer (at = offset, interval > 0, reschedule_cb = 0)" 4 |
1250 | .IX Item "non-repeating interval timer (interval > 0, reschedule_cb = 0)" |
1380 | .IX Item "non-repeating interval timer (at = offset, interval > 0, reschedule_cb = 0)" |
1251 | In this mode the watcher will always be scheduled to time out at the next |
1381 | In this mode the watcher will always be scheduled to time out at the next |
1252 | \&\f(CW\*(C`at + N * interval\*(C'\fR time (for some integer N) and then repeat, regardless |
1382 | \&\f(CW\*(C`at + N * interval\*(C'\fR time (for some integer N, which can also be negative) |
1253 | of any time jumps. |
1383 | and then repeat, regardless of any time jumps. |
1254 | .Sp |
1384 | .Sp |
1255 | This can be used to create timers that do not drift with respect to system |
1385 | This can be used to create timers that do not drift with respect to system |
1256 | time: |
1386 | time: |
1257 | .Sp |
1387 | .Sp |
1258 | .Vb 1 |
1388 | .Vb 1 |
… | |
… | |
1265 | by 3600. |
1395 | by 3600. |
1266 | .Sp |
1396 | .Sp |
1267 | Another way to think about it (for the mathematically inclined) is that |
1397 | Another way to think about it (for the mathematically inclined) is that |
1268 | \&\f(CW\*(C`ev_periodic\*(C'\fR will try to run the callback in this mode at the next possible |
1398 | \&\f(CW\*(C`ev_periodic\*(C'\fR will try to run the callback in this mode at the next possible |
1269 | time where \f(CW\*(C`time = at (mod interval)\*(C'\fR, regardless of any time jumps. |
1399 | time where \f(CW\*(C`time = at (mod interval)\*(C'\fR, regardless of any time jumps. |
|
|
1400 | .Sp |
|
|
1401 | For numerical stability it is preferable that the \f(CW\*(C`at\*(C'\fR value is near |
|
|
1402 | \&\f(CW\*(C`ev_now ()\*(C'\fR (the current time), but there is no range requirement for |
|
|
1403 | this value. |
1270 | .IP "* manual reschedule mode (reschedule_cb = callback)" 4 |
1404 | .IP "* manual reschedule mode (at and interval ignored, reschedule_cb = callback)" 4 |
1271 | .IX Item "manual reschedule mode (reschedule_cb = callback)" |
1405 | .IX Item "manual reschedule mode (at and interval ignored, reschedule_cb = callback)" |
1272 | In this mode the values for \f(CW\*(C`interval\*(C'\fR and \f(CW\*(C`at\*(C'\fR are both being |
1406 | In this mode the values for \f(CW\*(C`interval\*(C'\fR and \f(CW\*(C`at\*(C'\fR are both being |
1273 | ignored. Instead, each time the periodic watcher gets scheduled, the |
1407 | ignored. Instead, each time the periodic watcher gets scheduled, the |
1274 | reschedule callback will be called with the watcher as first, and the |
1408 | reschedule callback will be called with the watcher as first, and the |
1275 | current time as second argument. |
1409 | current time as second argument. |
1276 | .Sp |
1410 | .Sp |
1277 | \&\s-1NOTE:\s0 \fIThis callback \s-1MUST\s0 \s-1NOT\s0 stop or destroy any periodic watcher, |
1411 | \&\s-1NOTE:\s0 \fIThis callback \s-1MUST\s0 \s-1NOT\s0 stop or destroy any periodic watcher, |
1278 | ever, or make any event loop modifications\fR. If you need to stop it, |
1412 | ever, or make any event loop modifications\fR. If you need to stop it, |
1279 | return \f(CW\*(C`now + 1e30\*(C'\fR (or so, fudge fudge) and stop it afterwards (e.g. by |
1413 | return \f(CW\*(C`now + 1e30\*(C'\fR (or so, fudge fudge) and stop it afterwards (e.g. by |
1280 | starting a prepare watcher). |
1414 | starting an \f(CW\*(C`ev_prepare\*(C'\fR watcher, which is legal). |
1281 | .Sp |
1415 | .Sp |
1282 | Its prototype is \f(CW\*(C`ev_tstamp (*reschedule_cb)(struct ev_periodic *w, |
1416 | Its prototype is \f(CW\*(C`ev_tstamp (*reschedule_cb)(struct ev_periodic *w, |
1283 | ev_tstamp now)\*(C'\fR, e.g.: |
1417 | ev_tstamp now)\*(C'\fR, e.g.: |
1284 | .Sp |
1418 | .Sp |
1285 | .Vb 4 |
1419 | .Vb 4 |
… | |
… | |
1309 | .IX Item "ev_periodic_again (loop, ev_periodic *)" |
1443 | .IX Item "ev_periodic_again (loop, ev_periodic *)" |
1310 | Simply stops and restarts the periodic watcher again. This is only useful |
1444 | Simply stops and restarts the periodic watcher again. This is only useful |
1311 | when you changed some parameters or the reschedule callback would return |
1445 | when you changed some parameters or the reschedule callback would return |
1312 | a different time than the last time it was called (e.g. in a crond like |
1446 | a different time than the last time it was called (e.g. in a crond like |
1313 | program when the crontabs have changed). |
1447 | program when the crontabs have changed). |
|
|
1448 | .IP "ev_tstamp offset [read\-write]" 4 |
|
|
1449 | .IX Item "ev_tstamp offset [read-write]" |
|
|
1450 | When repeating, this contains the offset value, otherwise this is the |
|
|
1451 | absolute point in time (the \f(CW\*(C`at\*(C'\fR value passed to \f(CW\*(C`ev_periodic_set\*(C'\fR). |
|
|
1452 | .Sp |
|
|
1453 | Can be modified any time, but changes only take effect when the periodic |
|
|
1454 | timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being called. |
1314 | .IP "ev_tstamp interval [read\-write]" 4 |
1455 | .IP "ev_tstamp interval [read\-write]" 4 |
1315 | .IX Item "ev_tstamp interval [read-write]" |
1456 | .IX Item "ev_tstamp interval [read-write]" |
1316 | The current interval value. Can be modified any time, but changes only |
1457 | The current interval value. Can be modified any time, but changes only |
1317 | take effect when the periodic timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being |
1458 | take effect when the periodic timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being |
1318 | called. |
1459 | called. |
1319 | .IP "ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read\-write]" 4 |
1460 | .IP "ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read\-write]" 4 |
1320 | .IX Item "ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read-write]" |
1461 | .IX Item "ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read-write]" |
1321 | The current reschedule callback, or \f(CW0\fR, if this functionality is |
1462 | The current reschedule callback, or \f(CW0\fR, if this functionality is |
1322 | switched off. Can be changed any time, but changes only take effect when |
1463 | switched off. Can be changed any time, but changes only take effect when |
1323 | the periodic timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being called. |
1464 | the periodic timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being called. |
|
|
1465 | .IP "ev_tstamp at [read\-only]" 4 |
|
|
1466 | .IX Item "ev_tstamp at [read-only]" |
|
|
1467 | When active, contains the absolute time that the watcher is supposed to |
|
|
1468 | trigger next. |
1324 | .PP |
1469 | .PP |
1325 | Example: Call a callback every hour, or, more precisely, whenever the |
1470 | Example: Call a callback every hour, or, more precisely, whenever the |
1326 | system clock is divisible by 3600. The callback invocation times have |
1471 | system clock is divisible by 3600. The callback invocation times have |
1327 | potentially a lot of jittering, but good long-term stability. |
1472 | potentially a lot of jittering, but good long-term stability. |
1328 | .PP |
1473 | .PP |
… | |
… | |
1378 | first watcher gets started will libev actually register a signal watcher |
1523 | first watcher gets started will libev actually register a signal watcher |
1379 | with the kernel (thus it coexists with your own signal handlers as long |
1524 | with the kernel (thus it coexists with your own signal handlers as long |
1380 | as you don't register any with libev). Similarly, when the last signal |
1525 | as you don't register any with libev). Similarly, when the last signal |
1381 | watcher for a signal is stopped libev will reset the signal handler to |
1526 | watcher for a signal is stopped libev will reset the signal handler to |
1382 | \&\s-1SIG_DFL\s0 (regardless of what it was set to before). |
1527 | \&\s-1SIG_DFL\s0 (regardless of what it was set to before). |
|
|
1528 | .PP |
|
|
1529 | \fIWatcher-Specific Functions and Data Members\fR |
|
|
1530 | .IX Subsection "Watcher-Specific Functions and Data Members" |
1383 | .IP "ev_signal_init (ev_signal *, callback, int signum)" 4 |
1531 | .IP "ev_signal_init (ev_signal *, callback, int signum)" 4 |
1384 | .IX Item "ev_signal_init (ev_signal *, callback, int signum)" |
1532 | .IX Item "ev_signal_init (ev_signal *, callback, int signum)" |
1385 | .PD 0 |
1533 | .PD 0 |
1386 | .IP "ev_signal_set (ev_signal *, int signum)" 4 |
1534 | .IP "ev_signal_set (ev_signal *, int signum)" 4 |
1387 | .IX Item "ev_signal_set (ev_signal *, int signum)" |
1535 | .IX Item "ev_signal_set (ev_signal *, int signum)" |
… | |
… | |
1394 | .ie n .Sh """ev_child"" \- watch out for process status changes" |
1542 | .ie n .Sh """ev_child"" \- watch out for process status changes" |
1395 | .el .Sh "\f(CWev_child\fP \- watch out for process status changes" |
1543 | .el .Sh "\f(CWev_child\fP \- watch out for process status changes" |
1396 | .IX Subsection "ev_child - watch out for process status changes" |
1544 | .IX Subsection "ev_child - watch out for process status changes" |
1397 | Child watchers trigger when your process receives a \s-1SIGCHLD\s0 in response to |
1545 | Child watchers trigger when your process receives a \s-1SIGCHLD\s0 in response to |
1398 | some child status changes (most typically when a child of yours dies). |
1546 | some child status changes (most typically when a child of yours dies). |
|
|
1547 | .PP |
|
|
1548 | \fIWatcher-Specific Functions and Data Members\fR |
|
|
1549 | .IX Subsection "Watcher-Specific Functions and Data Members" |
1399 | .IP "ev_child_init (ev_child *, callback, int pid)" 4 |
1550 | .IP "ev_child_init (ev_child *, callback, int pid)" 4 |
1400 | .IX Item "ev_child_init (ev_child *, callback, int pid)" |
1551 | .IX Item "ev_child_init (ev_child *, callback, int pid)" |
1401 | .PD 0 |
1552 | .PD 0 |
1402 | .IP "ev_child_set (ev_child *, int pid)" 4 |
1553 | .IP "ev_child_set (ev_child *, int pid)" 4 |
1403 | .IX Item "ev_child_set (ev_child *, int pid)" |
1554 | .IX Item "ev_child_set (ev_child *, int pid)" |
… | |
… | |
1468 | reader). Inotify will be used to give hints only and should not change the |
1619 | reader). Inotify will be used to give hints only and should not change the |
1469 | semantics of \f(CW\*(C`ev_stat\*(C'\fR watchers, which means that libev sometimes needs |
1620 | semantics of \f(CW\*(C`ev_stat\*(C'\fR watchers, which means that libev sometimes needs |
1470 | to fall back to regular polling again even with inotify, but changes are |
1621 | to fall back to regular polling again even with inotify, but changes are |
1471 | usually detected immediately, and if the file exists there will be no |
1622 | usually detected immediately, and if the file exists there will be no |
1472 | polling. |
1623 | polling. |
|
|
1624 | .PP |
|
|
1625 | \fIWatcher-Specific Functions and Data Members\fR |
|
|
1626 | .IX Subsection "Watcher-Specific Functions and Data Members" |
1473 | .IP "ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)" 4 |
1627 | .IP "ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)" 4 |
1474 | .IX Item "ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)" |
1628 | .IX Item "ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)" |
1475 | .PD 0 |
1629 | .PD 0 |
1476 | .IP "ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)" 4 |
1630 | .IP "ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)" 4 |
1477 | .IX Item "ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)" |
1631 | .IX Item "ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)" |
… | |
… | |
1556 | .PP |
1710 | .PP |
1557 | Apart from keeping your process non-blocking (which is a useful |
1711 | Apart from keeping your process non-blocking (which is a useful |
1558 | effect on its own sometimes), idle watchers are a good place to do |
1712 | effect on its own sometimes), idle watchers are a good place to do |
1559 | \&\*(L"pseudo\-background processing\*(R", or delay processing stuff to after the |
1713 | \&\*(L"pseudo\-background processing\*(R", or delay processing stuff to after the |
1560 | event loop has handled all outstanding events. |
1714 | event loop has handled all outstanding events. |
|
|
1715 | .PP |
|
|
1716 | \fIWatcher-Specific Functions and Data Members\fR |
|
|
1717 | .IX Subsection "Watcher-Specific Functions and Data Members" |
1561 | .IP "ev_idle_init (ev_signal *, callback)" 4 |
1718 | .IP "ev_idle_init (ev_signal *, callback)" 4 |
1562 | .IX Item "ev_idle_init (ev_signal *, callback)" |
1719 | .IX Item "ev_idle_init (ev_signal *, callback)" |
1563 | Initialises and configures the idle watcher \- it has no parameters of any |
1720 | Initialises and configures the idle watcher \- it has no parameters of any |
1564 | kind. There is a \f(CW\*(C`ev_idle_set\*(C'\fR macro, but using it is utterly pointless, |
1721 | kind. There is a \f(CW\*(C`ev_idle_set\*(C'\fR macro, but using it is utterly pointless, |
1565 | believe me. |
1722 | believe me. |
… | |
… | |
1620 | are ready to run (it's actually more complicated: it only runs coroutines |
1777 | are ready to run (it's actually more complicated: it only runs coroutines |
1621 | with priority higher than or equal to the event loop and one coroutine |
1778 | with priority higher than or equal to the event loop and one coroutine |
1622 | of lower priority, but only once, using idle watchers to keep the event |
1779 | of lower priority, but only once, using idle watchers to keep the event |
1623 | loop from blocking if lower-priority coroutines are active, thus mapping |
1780 | loop from blocking if lower-priority coroutines are active, thus mapping |
1624 | low-priority coroutines to idle/background tasks). |
1781 | low-priority coroutines to idle/background tasks). |
|
|
1782 | .PP |
|
|
1783 | It is recommended to give \f(CW\*(C`ev_check\*(C'\fR watchers highest (\f(CW\*(C`EV_MAXPRI\*(C'\fR) |
|
|
1784 | priority, to ensure that they are being run before any other watchers |
|
|
1785 | after the poll. Also, \f(CW\*(C`ev_check\*(C'\fR watchers (and \f(CW\*(C`ev_prepare\*(C'\fR watchers, |
|
|
1786 | too) should not activate (\*(L"feed\*(R") events into libev. While libev fully |
|
|
1787 | supports this, they will be called before other \f(CW\*(C`ev_check\*(C'\fR watchers did |
|
|
1788 | their job. As \f(CW\*(C`ev_check\*(C'\fR watchers are often used to embed other event |
|
|
1789 | loops those other event loops might be in an unusable state until their |
|
|
1790 | \&\f(CW\*(C`ev_check\*(C'\fR watcher ran (always remind yourself to coexist peacefully with |
|
|
1791 | others). |
|
|
1792 | .PP |
|
|
1793 | \fIWatcher-Specific Functions and Data Members\fR |
|
|
1794 | .IX Subsection "Watcher-Specific Functions and Data Members" |
1625 | .IP "ev_prepare_init (ev_prepare *, callback)" 4 |
1795 | .IP "ev_prepare_init (ev_prepare *, callback)" 4 |
1626 | .IX Item "ev_prepare_init (ev_prepare *, callback)" |
1796 | .IX Item "ev_prepare_init (ev_prepare *, callback)" |
1627 | .PD 0 |
1797 | .PD 0 |
1628 | .IP "ev_check_init (ev_check *, callback)" 4 |
1798 | .IP "ev_check_init (ev_check *, callback)" 4 |
1629 | .IX Item "ev_check_init (ev_check *, callback)" |
1799 | .IX Item "ev_check_init (ev_check *, callback)" |
1630 | .PD |
1800 | .PD |
1631 | Initialises and configures the prepare or check watcher \- they have no |
1801 | Initialises and configures the prepare or check watcher \- they have no |
1632 | parameters of any kind. There are \f(CW\*(C`ev_prepare_set\*(C'\fR and \f(CW\*(C`ev_check_set\*(C'\fR |
1802 | parameters of any kind. There are \f(CW\*(C`ev_prepare_set\*(C'\fR and \f(CW\*(C`ev_check_set\*(C'\fR |
1633 | macros, but using them is utterly, utterly and completely pointless. |
1803 | macros, but using them is utterly, utterly and completely pointless. |
1634 | .PP |
1804 | .PP |
1635 | Example: To include a library such as adns, you would add \s-1IO\s0 watchers |
1805 | There are a number of principal ways to embed other event loops or modules |
1636 | and a timeout watcher in a prepare handler, as required by libadns, and |
1806 | into libev. Here are some ideas on how to include libadns into libev |
|
|
1807 | (there is a Perl module named \f(CW\*(C`EV::ADNS\*(C'\fR that does this, which you could |
|
|
1808 | use for an actually working example. Another Perl module named \f(CW\*(C`EV::Glib\*(C'\fR |
|
|
1809 | embeds a Glib main context into libev, and finally, \f(CW\*(C`Glib::EV\*(C'\fR embeds \s-1EV\s0 |
|
|
1810 | into the Glib event loop). |
|
|
1811 | .PP |
|
|
1812 | Method 1: Add \s-1IO\s0 watchers and a timeout watcher in a prepare handler, |
1637 | in a check watcher, destroy them and call into libadns. What follows is |
1813 | and in a check watcher, destroy them and call into libadns. What follows |
1638 | pseudo-code only of course: |
1814 | is pseudo-code only of course. This requires you to either use a low |
|
|
1815 | priority for the check watcher or use \f(CW\*(C`ev_clear_pending\*(C'\fR explicitly, as |
|
|
1816 | the callbacks for the IO/timeout watchers might not have been called yet. |
1639 | .PP |
1817 | .PP |
1640 | .Vb 2 |
1818 | .Vb 2 |
1641 | \& static ev_io iow [nfd]; |
1819 | \& static ev_io iow [nfd]; |
1642 | \& static ev_timer tw; |
1820 | \& static ev_timer tw; |
1643 | .Ve |
1821 | .Ve |
1644 | .PP |
1822 | .PP |
1645 | .Vb 9 |
1823 | .Vb 4 |
1646 | \& static void |
1824 | \& static void |
1647 | \& io_cb (ev_loop *loop, ev_io *w, int revents) |
1825 | \& io_cb (ev_loop *loop, ev_io *w, int revents) |
1648 | \& { |
1826 | \& { |
1649 | \& // set the relevant poll flags |
|
|
1650 | \& // could also call adns_processreadable etc. here |
|
|
1651 | \& struct pollfd *fd = (struct pollfd *)w->data; |
|
|
1652 | \& if (revents & EV_READ ) fd->revents |= fd->events & POLLIN; |
|
|
1653 | \& if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT; |
|
|
1654 | \& } |
1827 | \& } |
1655 | .Ve |
1828 | .Ve |
1656 | .PP |
1829 | .PP |
1657 | .Vb 8 |
1830 | .Vb 8 |
1658 | \& // create io watchers for each fd and a timer before blocking |
1831 | \& // create io watchers for each fd and a timer before blocking |
… | |
… | |
1670 | \& ev_timer_init (&tw, 0, timeout * 1e-3); |
1843 | \& ev_timer_init (&tw, 0, timeout * 1e-3); |
1671 | \& ev_timer_start (loop, &tw); |
1844 | \& ev_timer_start (loop, &tw); |
1672 | .Ve |
1845 | .Ve |
1673 | .PP |
1846 | .PP |
1674 | .Vb 6 |
1847 | .Vb 6 |
1675 | \& // create on ev_io per pollfd |
1848 | \& // create one ev_io per pollfd |
1676 | \& for (int i = 0; i < nfd; ++i) |
1849 | \& for (int i = 0; i < nfd; ++i) |
1677 | \& { |
1850 | \& { |
1678 | \& ev_io_init (iow + i, io_cb, fds [i].fd, |
1851 | \& ev_io_init (iow + i, io_cb, fds [i].fd, |
1679 | \& ((fds [i].events & POLLIN ? EV_READ : 0) |
1852 | \& ((fds [i].events & POLLIN ? EV_READ : 0) |
1680 | \& | (fds [i].events & POLLOUT ? EV_WRITE : 0))); |
1853 | \& | (fds [i].events & POLLOUT ? EV_WRITE : 0))); |
1681 | .Ve |
1854 | .Ve |
1682 | .PP |
1855 | .PP |
1683 | .Vb 5 |
1856 | .Vb 4 |
1684 | \& fds [i].revents = 0; |
1857 | \& fds [i].revents = 0; |
1685 | \& iow [i].data = fds + i; |
|
|
1686 | \& ev_io_start (loop, iow + i); |
1858 | \& ev_io_start (loop, iow + i); |
1687 | \& } |
1859 | \& } |
1688 | \& } |
1860 | \& } |
1689 | .Ve |
1861 | .Ve |
1690 | .PP |
1862 | .PP |
… | |
… | |
1694 | \& adns_check_cb (ev_loop *loop, ev_check *w, int revents) |
1866 | \& adns_check_cb (ev_loop *loop, ev_check *w, int revents) |
1695 | \& { |
1867 | \& { |
1696 | \& ev_timer_stop (loop, &tw); |
1868 | \& ev_timer_stop (loop, &tw); |
1697 | .Ve |
1869 | .Ve |
1698 | .PP |
1870 | .PP |
1699 | .Vb 2 |
1871 | .Vb 8 |
1700 | \& for (int i = 0; i < nfd; ++i) |
1872 | \& for (int i = 0; i < nfd; ++i) |
|
|
1873 | \& { |
|
|
1874 | \& // set the relevant poll flags |
|
|
1875 | \& // could also call adns_processreadable etc. here |
|
|
1876 | \& struct pollfd *fd = fds + i; |
|
|
1877 | \& int revents = ev_clear_pending (iow + i); |
|
|
1878 | \& if (revents & EV_READ ) fd->revents |= fd->events & POLLIN; |
|
|
1879 | \& if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT; |
|
|
1880 | .Ve |
|
|
1881 | .PP |
|
|
1882 | .Vb 3 |
|
|
1883 | \& // now stop the watcher |
1701 | \& ev_io_stop (loop, iow + i); |
1884 | \& ev_io_stop (loop, iow + i); |
|
|
1885 | \& } |
1702 | .Ve |
1886 | .Ve |
1703 | .PP |
1887 | .PP |
1704 | .Vb 2 |
1888 | .Vb 2 |
1705 | \& adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop)); |
1889 | \& adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop)); |
|
|
1890 | \& } |
|
|
1891 | .Ve |
|
|
1892 | .PP |
|
|
1893 | Method 2: This would be just like method 1, but you run \f(CW\*(C`adns_afterpoll\*(C'\fR |
|
|
1894 | in the prepare watcher and would dispose of the check watcher. |
|
|
1895 | .PP |
|
|
1896 | Method 3: If the module to be embedded supports explicit event |
|
|
1897 | notification (adns does), you can also make use of the actual watcher |
|
|
1898 | callbacks, and only destroy/create the watchers in the prepare watcher. |
|
|
1899 | .PP |
|
|
1900 | .Vb 5 |
|
|
1901 | \& static void |
|
|
1902 | \& timer_cb (EV_P_ ev_timer *w, int revents) |
|
|
1903 | \& { |
|
|
1904 | \& adns_state ads = (adns_state)w->data; |
|
|
1905 | \& update_now (EV_A); |
|
|
1906 | .Ve |
|
|
1907 | .PP |
|
|
1908 | .Vb 2 |
|
|
1909 | \& adns_processtimeouts (ads, &tv_now); |
|
|
1910 | \& } |
|
|
1911 | .Ve |
|
|
1912 | .PP |
|
|
1913 | .Vb 5 |
|
|
1914 | \& static void |
|
|
1915 | \& io_cb (EV_P_ ev_io *w, int revents) |
|
|
1916 | \& { |
|
|
1917 | \& adns_state ads = (adns_state)w->data; |
|
|
1918 | \& update_now (EV_A); |
|
|
1919 | .Ve |
|
|
1920 | .PP |
|
|
1921 | .Vb 3 |
|
|
1922 | \& if (revents & EV_READ ) adns_processreadable (ads, w->fd, &tv_now); |
|
|
1923 | \& if (revents & EV_WRITE) adns_processwriteable (ads, w->fd, &tv_now); |
|
|
1924 | \& } |
|
|
1925 | .Ve |
|
|
1926 | .PP |
|
|
1927 | .Vb 1 |
|
|
1928 | \& // do not ever call adns_afterpoll |
|
|
1929 | .Ve |
|
|
1930 | .PP |
|
|
1931 | Method 4: Do not use a prepare or check watcher because the module you |
|
|
1932 | want to embed is too inflexible to support it. Instead, youc na override |
|
|
1933 | their poll function. The drawback with this solution is that the main |
|
|
1934 | loop is now no longer controllable by \s-1EV\s0. The \f(CW\*(C`Glib::EV\*(C'\fR module does |
|
|
1935 | this. |
|
|
1936 | .PP |
|
|
1937 | .Vb 4 |
|
|
1938 | \& static gint |
|
|
1939 | \& event_poll_func (GPollFD *fds, guint nfds, gint timeout) |
|
|
1940 | \& { |
|
|
1941 | \& int got_events = 0; |
|
|
1942 | .Ve |
|
|
1943 | .PP |
|
|
1944 | .Vb 2 |
|
|
1945 | \& for (n = 0; n < nfds; ++n) |
|
|
1946 | \& // create/start io watcher that sets the relevant bits in fds[n] and increment got_events |
|
|
1947 | .Ve |
|
|
1948 | .PP |
|
|
1949 | .Vb 2 |
|
|
1950 | \& if (timeout >= 0) |
|
|
1951 | \& // create/start timer |
|
|
1952 | .Ve |
|
|
1953 | .PP |
|
|
1954 | .Vb 2 |
|
|
1955 | \& // poll |
|
|
1956 | \& ev_loop (EV_A_ 0); |
|
|
1957 | .Ve |
|
|
1958 | .PP |
|
|
1959 | .Vb 3 |
|
|
1960 | \& // stop timer again |
|
|
1961 | \& if (timeout >= 0) |
|
|
1962 | \& ev_timer_stop (EV_A_ &to); |
|
|
1963 | .Ve |
|
|
1964 | .PP |
|
|
1965 | .Vb 3 |
|
|
1966 | \& // stop io watchers again - their callbacks should have set |
|
|
1967 | \& for (n = 0; n < nfds; ++n) |
|
|
1968 | \& ev_io_stop (EV_A_ iow [n]); |
|
|
1969 | .Ve |
|
|
1970 | .PP |
|
|
1971 | .Vb 2 |
|
|
1972 | \& return got_events; |
1706 | \& } |
1973 | \& } |
1707 | .Ve |
1974 | .Ve |
1708 | .ie n .Sh """ev_embed"" \- when one backend isn't enough..." |
1975 | .ie n .Sh """ev_embed"" \- when one backend isn't enough..." |
1709 | .el .Sh "\f(CWev_embed\fP \- when one backend isn't enough..." |
1976 | .el .Sh "\f(CWev_embed\fP \- when one backend isn't enough..." |
1710 | .IX Subsection "ev_embed - when one backend isn't enough..." |
1977 | .IX Subsection "ev_embed - when one backend isn't enough..." |
1711 | This is a rather advanced watcher type that lets you embed one event loop |
1978 | This is a rather advanced watcher type that lets you embed one event loop |
1712 | into another (currently only \f(CW\*(C`ev_io\*(C'\fR events are supported in the embedded |
1979 | into another (currently only \f(CW\*(C`ev_io\*(C'\fR events are supported in the embedded |
1713 | loop, other types of watchers might be handled in a delayed or incorrect |
1980 | loop, other types of watchers might be handled in a delayed or incorrect |
1714 | fashion and must not be used). |
1981 | fashion and must not be used). (See portability notes, below). |
1715 | .PP |
1982 | .PP |
1716 | There are primarily two reasons you would want that: work around bugs and |
1983 | There are primarily two reasons you would want that: work around bugs and |
1717 | prioritise I/O. |
1984 | prioritise I/O. |
1718 | .PP |
1985 | .PP |
1719 | As an example for a bug workaround, the kqueue backend might only support |
1986 | As an example for a bug workaround, the kqueue backend might only support |
… | |
… | |
1779 | \& ev_embed_start (loop_hi, &embed); |
2046 | \& ev_embed_start (loop_hi, &embed); |
1780 | \& } |
2047 | \& } |
1781 | \& else |
2048 | \& else |
1782 | \& loop_lo = loop_hi; |
2049 | \& loop_lo = loop_hi; |
1783 | .Ve |
2050 | .Ve |
|
|
2051 | .Sh "Portability notes" |
|
|
2052 | .IX Subsection "Portability notes" |
|
|
2053 | Kqueue is nominally embeddable, but this is broken on all BSDs that I |
|
|
2054 | tried, in various ways. Usually the embedded event loop will simply never |
|
|
2055 | receive events, sometimes it will only trigger a few times, sometimes in a |
|
|
2056 | loop. Epoll is also nominally embeddable, but many Linux kernel versions |
|
|
2057 | will always eport the epoll fd as ready, even when no events are pending. |
|
|
2058 | .PP |
|
|
2059 | While libev allows embedding these backends (they are contained in |
|
|
2060 | \&\f(CW\*(C`ev_embeddable_backends ()\*(C'\fR), take extreme care that it will actually |
|
|
2061 | work. |
|
|
2062 | .PP |
|
|
2063 | When in doubt, create a dynamic event loop forced to use sockets (this |
|
|
2064 | usually works) and possibly another thread and a pipe or so to report to |
|
|
2065 | your main event loop. |
|
|
2066 | .PP |
|
|
2067 | \fIWatcher-Specific Functions and Data Members\fR |
|
|
2068 | .IX Subsection "Watcher-Specific Functions and Data Members" |
1784 | .IP "ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)" 4 |
2069 | .IP "ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)" 4 |
1785 | .IX Item "ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)" |
2070 | .IX Item "ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)" |
1786 | .PD 0 |
2071 | .PD 0 |
1787 | .IP "ev_embed_set (ev_embed *, callback, struct ev_loop *embedded_loop)" 4 |
2072 | .IP "ev_embed_set (ev_embed *, callback, struct ev_loop *embedded_loop)" 4 |
1788 | .IX Item "ev_embed_set (ev_embed *, callback, struct ev_loop *embedded_loop)" |
2073 | .IX Item "ev_embed_set (ev_embed *, callback, struct ev_loop *embedded_loop)" |
… | |
… | |
1795 | .IP "ev_embed_sweep (loop, ev_embed *)" 4 |
2080 | .IP "ev_embed_sweep (loop, ev_embed *)" 4 |
1796 | .IX Item "ev_embed_sweep (loop, ev_embed *)" |
2081 | .IX Item "ev_embed_sweep (loop, ev_embed *)" |
1797 | Make a single, non-blocking sweep over the embedded loop. This works |
2082 | Make a single, non-blocking sweep over the embedded loop. This works |
1798 | similarly to \f(CW\*(C`ev_loop (embedded_loop, EVLOOP_NONBLOCK)\*(C'\fR, but in the most |
2083 | similarly to \f(CW\*(C`ev_loop (embedded_loop, EVLOOP_NONBLOCK)\*(C'\fR, but in the most |
1799 | apropriate way for embedded loops. |
2084 | apropriate way for embedded loops. |
1800 | .IP "struct ev_loop *loop [read\-only]" 4 |
2085 | .IP "struct ev_loop *other [read\-only]" 4 |
1801 | .IX Item "struct ev_loop *loop [read-only]" |
2086 | .IX Item "struct ev_loop *other [read-only]" |
1802 | The embedded event loop. |
2087 | The embedded event loop. |
1803 | .ie n .Sh """ev_fork"" \- the audacity to resume the event loop after a fork" |
2088 | .ie n .Sh """ev_fork"" \- the audacity to resume the event loop after a fork" |
1804 | .el .Sh "\f(CWev_fork\fP \- the audacity to resume the event loop after a fork" |
2089 | .el .Sh "\f(CWev_fork\fP \- the audacity to resume the event loop after a fork" |
1805 | .IX Subsection "ev_fork - the audacity to resume the event loop after a fork" |
2090 | .IX Subsection "ev_fork - the audacity to resume the event loop after a fork" |
1806 | Fork watchers are called when a \f(CW\*(C`fork ()\*(C'\fR was detected (usually because |
2091 | Fork watchers are called when a \f(CW\*(C`fork ()\*(C'\fR was detected (usually because |
… | |
… | |
1808 | \&\f(CW\*(C`ev_default_fork\*(C'\fR or \f(CW\*(C`ev_loop_fork\*(C'\fR). The invocation is done before the |
2093 | \&\f(CW\*(C`ev_default_fork\*(C'\fR or \f(CW\*(C`ev_loop_fork\*(C'\fR). The invocation is done before the |
1809 | event loop blocks next and before \f(CW\*(C`ev_check\*(C'\fR watchers are being called, |
2094 | event loop blocks next and before \f(CW\*(C`ev_check\*(C'\fR watchers are being called, |
1810 | and only in the child after the fork. If whoever good citizen calling |
2095 | and only in the child after the fork. If whoever good citizen calling |
1811 | \&\f(CW\*(C`ev_default_fork\*(C'\fR cheats and calls it in the wrong process, the fork |
2096 | \&\f(CW\*(C`ev_default_fork\*(C'\fR cheats and calls it in the wrong process, the fork |
1812 | handlers will be invoked, too, of course. |
2097 | handlers will be invoked, too, of course. |
|
|
2098 | .PP |
|
|
2099 | \fIWatcher-Specific Functions and Data Members\fR |
|
|
2100 | .IX Subsection "Watcher-Specific Functions and Data Members" |
1813 | .IP "ev_fork_init (ev_signal *, callback)" 4 |
2101 | .IP "ev_fork_init (ev_signal *, callback)" 4 |
1814 | .IX Item "ev_fork_init (ev_signal *, callback)" |
2102 | .IX Item "ev_fork_init (ev_signal *, callback)" |
1815 | Initialises and configures the fork watcher \- it has no parameters of any |
2103 | Initialises and configures the fork watcher \- it has no parameters of any |
1816 | kind. There is a \f(CW\*(C`ev_fork_set\*(C'\fR macro, but using it is utterly pointless, |
2104 | kind. There is a \f(CW\*(C`ev_fork_set\*(C'\fR macro, but using it is utterly pointless, |
1817 | believe me. |
2105 | believe me. |
… | |
… | |
1894 | .PP |
2182 | .PP |
1895 | .Vb 1 |
2183 | .Vb 1 |
1896 | \& #include <ev++.h> |
2184 | \& #include <ev++.h> |
1897 | .Ve |
2185 | .Ve |
1898 | .PP |
2186 | .PP |
1899 | (it is not installed by default). This automatically includes \fIev.h\fR |
2187 | This automatically includes \fIev.h\fR and puts all of its definitions (many |
1900 | and puts all of its definitions (many of them macros) into the global |
2188 | of them macros) into the global namespace. All \*(C+ specific things are |
1901 | namespace. All \*(C+ specific things are put into the \f(CW\*(C`ev\*(C'\fR namespace. |
2189 | put into the \f(CW\*(C`ev\*(C'\fR namespace. It should support all the same embedding |
|
|
2190 | options as \fIev.h\fR, most notably \f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. |
1902 | .PP |
2191 | .PP |
1903 | It should support all the same embedding options as \fIev.h\fR, most notably |
2192 | Care has been taken to keep the overhead low. The only data member the \*(C+ |
1904 | \&\f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. |
2193 | classes add (compared to plain C\-style watchers) is the event loop pointer |
|
|
2194 | that the watcher is associated with (or no additional members at all if |
|
|
2195 | you disable \f(CW\*(C`EV_MULTIPLICITY\*(C'\fR when embedding libev). |
|
|
2196 | .PP |
|
|
2197 | Currently, functions, and static and non-static member functions can be |
|
|
2198 | used as callbacks. Other types should be easy to add as long as they only |
|
|
2199 | need one additional pointer for context. If you need support for other |
|
|
2200 | types of functors please contact the author (preferably after implementing |
|
|
2201 | it). |
1905 | .PP |
2202 | .PP |
1906 | Here is a list of things available in the \f(CW\*(C`ev\*(C'\fR namespace: |
2203 | Here is a list of things available in the \f(CW\*(C`ev\*(C'\fR namespace: |
1907 | .ie n .IP """ev::READ""\fR, \f(CW""ev::WRITE"" etc." 4 |
2204 | .ie n .IP """ev::READ""\fR, \f(CW""ev::WRITE"" etc." 4 |
1908 | .el .IP "\f(CWev::READ\fR, \f(CWev::WRITE\fR etc." 4 |
2205 | .el .IP "\f(CWev::READ\fR, \f(CWev::WRITE\fR etc." 4 |
1909 | .IX Item "ev::READ, ev::WRITE etc." |
2206 | .IX Item "ev::READ, ev::WRITE etc." |
… | |
… | |
1921 | which is called \f(CW\*(C`ev::sig\*(C'\fR to avoid clashes with the \f(CW\*(C`signal\*(C'\fR macro |
2218 | which is called \f(CW\*(C`ev::sig\*(C'\fR to avoid clashes with the \f(CW\*(C`signal\*(C'\fR macro |
1922 | defines by many implementations. |
2219 | defines by many implementations. |
1923 | .Sp |
2220 | .Sp |
1924 | All of those classes have these methods: |
2221 | All of those classes have these methods: |
1925 | .RS 4 |
2222 | .RS 4 |
1926 | .IP "ev::TYPE::TYPE (object *, object::method *)" 4 |
2223 | .IP "ev::TYPE::TYPE ()" 4 |
1927 | .IX Item "ev::TYPE::TYPE (object *, object::method *)" |
2224 | .IX Item "ev::TYPE::TYPE ()" |
1928 | .PD 0 |
2225 | .PD 0 |
1929 | .IP "ev::TYPE::TYPE (object *, object::method *, struct ev_loop *)" 4 |
2226 | .IP "ev::TYPE::TYPE (struct ev_loop *)" 4 |
1930 | .IX Item "ev::TYPE::TYPE (object *, object::method *, struct ev_loop *)" |
2227 | .IX Item "ev::TYPE::TYPE (struct ev_loop *)" |
1931 | .IP "ev::TYPE::~TYPE" 4 |
2228 | .IP "ev::TYPE::~TYPE" 4 |
1932 | .IX Item "ev::TYPE::~TYPE" |
2229 | .IX Item "ev::TYPE::~TYPE" |
1933 | .PD |
2230 | .PD |
1934 | The constructor takes a pointer to an object and a method pointer to |
2231 | The constructor (optionally) takes an event loop to associate the watcher |
1935 | the event handler callback to call in this class. The constructor calls |
2232 | with. If it is omitted, it will use \f(CW\*(C`EV_DEFAULT\*(C'\fR. |
1936 | \&\f(CW\*(C`ev_init\*(C'\fR for you, which means you have to call the \f(CW\*(C`set\*(C'\fR method |
2233 | .Sp |
1937 | before starting it. If you do not specify a loop then the constructor |
2234 | The constructor calls \f(CW\*(C`ev_init\*(C'\fR for you, which means you have to call the |
1938 | automatically associates the default loop with this watcher. |
2235 | \&\f(CW\*(C`set\*(C'\fR method before starting it. |
|
|
2236 | .Sp |
|
|
2237 | It will not set a callback, however: You have to call the templated \f(CW\*(C`set\*(C'\fR |
|
|
2238 | method to set a callback before you can start the watcher. |
|
|
2239 | .Sp |
|
|
2240 | (The reason why you have to use a method is a limitation in \*(C+ which does |
|
|
2241 | not allow explicit template arguments for constructors). |
1939 | .Sp |
2242 | .Sp |
1940 | The destructor automatically stops the watcher if it is active. |
2243 | The destructor automatically stops the watcher if it is active. |
|
|
2244 | .IP "w\->set<class, &class::method> (object *)" 4 |
|
|
2245 | .IX Item "w->set<class, &class::method> (object *)" |
|
|
2246 | This method sets the callback method to call. The method has to have a |
|
|
2247 | signature of \f(CW\*(C`void (*)(ev_TYPE &, int)\*(C'\fR, it receives the watcher as |
|
|
2248 | first argument and the \f(CW\*(C`revents\*(C'\fR as second. The object must be given as |
|
|
2249 | parameter and is stored in the \f(CW\*(C`data\*(C'\fR member of the watcher. |
|
|
2250 | .Sp |
|
|
2251 | This method synthesizes efficient thunking code to call your method from |
|
|
2252 | the C callback that libev requires. If your compiler can inline your |
|
|
2253 | callback (i.e. it is visible to it at the place of the \f(CW\*(C`set\*(C'\fR call and |
|
|
2254 | your compiler is good :), then the method will be fully inlined into the |
|
|
2255 | thunking function, making it as fast as a direct C callback. |
|
|
2256 | .Sp |
|
|
2257 | Example: simple class declaration and watcher initialisation |
|
|
2258 | .Sp |
|
|
2259 | .Vb 4 |
|
|
2260 | \& struct myclass |
|
|
2261 | \& { |
|
|
2262 | \& void io_cb (ev::io &w, int revents) { } |
|
|
2263 | \& } |
|
|
2264 | .Ve |
|
|
2265 | .Sp |
|
|
2266 | .Vb 3 |
|
|
2267 | \& myclass obj; |
|
|
2268 | \& ev::io iow; |
|
|
2269 | \& iow.set <myclass, &myclass::io_cb> (&obj); |
|
|
2270 | .Ve |
|
|
2271 | .IP "w\->set<function> (void *data = 0)" 4 |
|
|
2272 | .IX Item "w->set<function> (void *data = 0)" |
|
|
2273 | Also sets a callback, but uses a static method or plain function as |
|
|
2274 | callback. The optional \f(CW\*(C`data\*(C'\fR argument will be stored in the watcher's |
|
|
2275 | \&\f(CW\*(C`data\*(C'\fR member and is free for you to use. |
|
|
2276 | .Sp |
|
|
2277 | The prototype of the \f(CW\*(C`function\*(C'\fR must be \f(CW\*(C`void (*)(ev::TYPE &w, int)\*(C'\fR. |
|
|
2278 | .Sp |
|
|
2279 | See the method\-\f(CW\*(C`set\*(C'\fR above for more details. |
|
|
2280 | .Sp |
|
|
2281 | Example: |
|
|
2282 | .Sp |
|
|
2283 | .Vb 2 |
|
|
2284 | \& static void io_cb (ev::io &w, int revents) { } |
|
|
2285 | \& iow.set <io_cb> (); |
|
|
2286 | .Ve |
1941 | .IP "w\->set (struct ev_loop *)" 4 |
2287 | .IP "w\->set (struct ev_loop *)" 4 |
1942 | .IX Item "w->set (struct ev_loop *)" |
2288 | .IX Item "w->set (struct ev_loop *)" |
1943 | Associates a different \f(CW\*(C`struct ev_loop\*(C'\fR with this watcher. You can only |
2289 | Associates a different \f(CW\*(C`struct ev_loop\*(C'\fR with this watcher. You can only |
1944 | do this when the watcher is inactive (and not pending either). |
2290 | do this when the watcher is inactive (and not pending either). |
1945 | .IP "w\->set ([args])" 4 |
2291 | .IP "w\->set ([args])" 4 |
1946 | .IX Item "w->set ([args])" |
2292 | .IX Item "w->set ([args])" |
1947 | Basically the same as \f(CW\*(C`ev_TYPE_set\*(C'\fR, with the same args. Must be |
2293 | Basically the same as \f(CW\*(C`ev_TYPE_set\*(C'\fR, with the same args. Must be |
1948 | called at least once. Unlike the C counterpart, an active watcher gets |
2294 | called at least once. Unlike the C counterpart, an active watcher gets |
1949 | automatically stopped and restarted. |
2295 | automatically stopped and restarted when reconfiguring it with this |
|
|
2296 | method. |
1950 | .IP "w\->start ()" 4 |
2297 | .IP "w\->start ()" 4 |
1951 | .IX Item "w->start ()" |
2298 | .IX Item "w->start ()" |
1952 | Starts the watcher. Note that there is no \f(CW\*(C`loop\*(C'\fR argument as the |
2299 | Starts the watcher. Note that there is no \f(CW\*(C`loop\*(C'\fR argument, as the |
1953 | constructor already takes the loop. |
2300 | constructor already stores the event loop. |
1954 | .IP "w\->stop ()" 4 |
2301 | .IP "w\->stop ()" 4 |
1955 | .IX Item "w->stop ()" |
2302 | .IX Item "w->stop ()" |
1956 | Stops the watcher if it is active. Again, no \f(CW\*(C`loop\*(C'\fR argument. |
2303 | Stops the watcher if it is active. Again, no \f(CW\*(C`loop\*(C'\fR argument. |
1957 | .ie n .IP "w\->again () ""ev::timer""\fR, \f(CW""ev::periodic"" only" 4 |
2304 | .ie n .IP "w\->again () (""ev::timer""\fR, \f(CW""ev::periodic"" only)" 4 |
1958 | .el .IP "w\->again () \f(CWev::timer\fR, \f(CWev::periodic\fR only" 4 |
2305 | .el .IP "w\->again () (\f(CWev::timer\fR, \f(CWev::periodic\fR only)" 4 |
1959 | .IX Item "w->again () ev::timer, ev::periodic only" |
2306 | .IX Item "w->again () (ev::timer, ev::periodic only)" |
1960 | For \f(CW\*(C`ev::timer\*(C'\fR and \f(CW\*(C`ev::periodic\*(C'\fR, this invokes the corresponding |
2307 | For \f(CW\*(C`ev::timer\*(C'\fR and \f(CW\*(C`ev::periodic\*(C'\fR, this invokes the corresponding |
1961 | \&\f(CW\*(C`ev_TYPE_again\*(C'\fR function. |
2308 | \&\f(CW\*(C`ev_TYPE_again\*(C'\fR function. |
1962 | .ie n .IP "w\->sweep () ""ev::embed"" only" 4 |
2309 | .ie n .IP "w\->sweep () (""ev::embed"" only)" 4 |
1963 | .el .IP "w\->sweep () \f(CWev::embed\fR only" 4 |
2310 | .el .IP "w\->sweep () (\f(CWev::embed\fR only)" 4 |
1964 | .IX Item "w->sweep () ev::embed only" |
2311 | .IX Item "w->sweep () (ev::embed only)" |
1965 | Invokes \f(CW\*(C`ev_embed_sweep\*(C'\fR. |
2312 | Invokes \f(CW\*(C`ev_embed_sweep\*(C'\fR. |
1966 | .ie n .IP "w\->update () ""ev::stat"" only" 4 |
2313 | .ie n .IP "w\->update () (""ev::stat"" only)" 4 |
1967 | .el .IP "w\->update () \f(CWev::stat\fR only" 4 |
2314 | .el .IP "w\->update () (\f(CWev::stat\fR only)" 4 |
1968 | .IX Item "w->update () ev::stat only" |
2315 | .IX Item "w->update () (ev::stat only)" |
1969 | Invokes \f(CW\*(C`ev_stat_stat\*(C'\fR. |
2316 | Invokes \f(CW\*(C`ev_stat_stat\*(C'\fR. |
1970 | .RE |
2317 | .RE |
1971 | .RS 4 |
2318 | .RS 4 |
1972 | .RE |
2319 | .RE |
1973 | .PP |
2320 | .PP |
… | |
… | |
1984 | .Vb 2 |
2331 | .Vb 2 |
1985 | \& myclass (); |
2332 | \& myclass (); |
1986 | \& } |
2333 | \& } |
1987 | .Ve |
2334 | .Ve |
1988 | .PP |
2335 | .PP |
1989 | .Vb 6 |
2336 | .Vb 4 |
1990 | \& myclass::myclass (int fd) |
2337 | \& myclass::myclass (int fd) |
1991 | \& : io (this, &myclass::io_cb), |
|
|
1992 | \& idle (this, &myclass::idle_cb) |
|
|
1993 | \& { |
2338 | \& { |
|
|
2339 | \& io .set <myclass, &myclass::io_cb > (this); |
|
|
2340 | \& idle.set <myclass, &myclass::idle_cb> (this); |
|
|
2341 | .Ve |
|
|
2342 | .PP |
|
|
2343 | .Vb 2 |
1994 | \& io.start (fd, ev::READ); |
2344 | \& io.start (fd, ev::READ); |
1995 | \& } |
2345 | \& } |
1996 | .Ve |
2346 | .Ve |
1997 | .SH "MACRO MAGIC" |
2347 | .SH "MACRO MAGIC" |
1998 | .IX Header "MACRO MAGIC" |
2348 | .IX Header "MACRO MAGIC" |
1999 | Libev can be compiled with a variety of options, the most fundemantal is |
2349 | Libev can be compiled with a variety of options, the most fundamantal |
2000 | \&\f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. This option determines whether (most) functions and |
2350 | of which is \f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. This option determines whether (most) |
2001 | callbacks have an initial \f(CW\*(C`struct ev_loop *\*(C'\fR argument. |
2351 | functions and callbacks have an initial \f(CW\*(C`struct ev_loop *\*(C'\fR argument. |
2002 | .PP |
2352 | .PP |
2003 | To make it easier to write programs that cope with either variant, the |
2353 | To make it easier to write programs that cope with either variant, the |
2004 | following macros are defined: |
2354 | following macros are defined: |
2005 | .ie n .IP """EV_A""\fR, \f(CW""EV_A_""" 4 |
2355 | .ie n .IP """EV_A""\fR, \f(CW""EV_A_""" 4 |
2006 | .el .IP "\f(CWEV_A\fR, \f(CWEV_A_\fR" 4 |
2356 | .el .IP "\f(CWEV_A\fR, \f(CWEV_A_\fR" 4 |
… | |
… | |
2065 | Libev can (and often is) directly embedded into host |
2415 | Libev can (and often is) directly embedded into host |
2066 | applications. Examples of applications that embed it include the Deliantra |
2416 | applications. Examples of applications that embed it include the Deliantra |
2067 | Game Server, the \s-1EV\s0 perl module, the \s-1GNU\s0 Virtual Private Ethernet (gvpe) |
2417 | Game Server, the \s-1EV\s0 perl module, the \s-1GNU\s0 Virtual Private Ethernet (gvpe) |
2068 | and rxvt\-unicode. |
2418 | and rxvt\-unicode. |
2069 | .PP |
2419 | .PP |
2070 | The goal is to enable you to just copy the neecssary files into your |
2420 | The goal is to enable you to just copy the necessary files into your |
2071 | source directory without having to change even a single line in them, so |
2421 | source directory without having to change even a single line in them, so |
2072 | you can easily upgrade by simply copying (or having a checked-out copy of |
2422 | you can easily upgrade by simply copying (or having a checked-out copy of |
2073 | libev somewhere in your source tree). |
2423 | libev somewhere in your source tree). |
2074 | .Sh "\s-1FILESETS\s0" |
2424 | .Sh "\s-1FILESETS\s0" |
2075 | .IX Subsection "FILESETS" |
2425 | .IX Subsection "FILESETS" |
… | |
… | |
2180 | .IX Item "EV_USE_MONOTONIC" |
2530 | .IX Item "EV_USE_MONOTONIC" |
2181 | If defined to be \f(CW1\fR, libev will try to detect the availability of the |
2531 | If defined to be \f(CW1\fR, libev will try to detect the availability of the |
2182 | monotonic clock option at both compiletime and runtime. Otherwise no use |
2532 | monotonic clock option at both compiletime and runtime. Otherwise no use |
2183 | of the monotonic clock option will be attempted. If you enable this, you |
2533 | of the monotonic clock option will be attempted. If you enable this, you |
2184 | usually have to link against librt or something similar. Enabling it when |
2534 | usually have to link against librt or something similar. Enabling it when |
2185 | the functionality isn't available is safe, though, althoguh you have |
2535 | the functionality isn't available is safe, though, although you have |
2186 | to make sure you link against any libraries where the \f(CW\*(C`clock_gettime\*(C'\fR |
2536 | to make sure you link against any libraries where the \f(CW\*(C`clock_gettime\*(C'\fR |
2187 | function is hiding in (often \fI\-lrt\fR). |
2537 | function is hiding in (often \fI\-lrt\fR). |
2188 | .IP "\s-1EV_USE_REALTIME\s0" 4 |
2538 | .IP "\s-1EV_USE_REALTIME\s0" 4 |
2189 | .IX Item "EV_USE_REALTIME" |
2539 | .IX Item "EV_USE_REALTIME" |
2190 | If defined to be \f(CW1\fR, libev will try to detect the availability of the |
2540 | If defined to be \f(CW1\fR, libev will try to detect the availability of the |
2191 | realtime clock option at compiletime (and assume its availability at |
2541 | realtime clock option at compiletime (and assume its availability at |
2192 | runtime if successful). Otherwise no use of the realtime clock option will |
2542 | runtime if successful). Otherwise no use of the realtime clock option will |
2193 | be attempted. This effectively replaces \f(CW\*(C`gettimeofday\*(C'\fR by \f(CW\*(C`clock_get |
2543 | be attempted. This effectively replaces \f(CW\*(C`gettimeofday\*(C'\fR by \f(CW\*(C`clock_get |
2194 | (CLOCK_REALTIME, ...)\*(C'\fR and will not normally affect correctness. See tzhe note about libraries |
2544 | (CLOCK_REALTIME, ...)\*(C'\fR and will not normally affect correctness. See the |
2195 | in the description of \f(CW\*(C`EV_USE_MONOTONIC\*(C'\fR, though. |
2545 | note about libraries in the description of \f(CW\*(C`EV_USE_MONOTONIC\*(C'\fR, though. |
|
|
2546 | .IP "\s-1EV_USE_NANOSLEEP\s0" 4 |
|
|
2547 | .IX Item "EV_USE_NANOSLEEP" |
|
|
2548 | If defined to be \f(CW1\fR, libev will assume that \f(CW\*(C`nanosleep ()\*(C'\fR is available |
|
|
2549 | and will use it for delays. Otherwise it will use \f(CW\*(C`select ()\*(C'\fR. |
2196 | .IP "\s-1EV_USE_SELECT\s0" 4 |
2550 | .IP "\s-1EV_USE_SELECT\s0" 4 |
2197 | .IX Item "EV_USE_SELECT" |
2551 | .IX Item "EV_USE_SELECT" |
2198 | If undefined or defined to be \f(CW1\fR, libev will compile in support for the |
2552 | If undefined or defined to be \f(CW1\fR, libev will compile in support for the |
2199 | \&\f(CW\*(C`select\*(C'\fR(2) backend. No attempt at autodetection will be done: if no |
2553 | \&\f(CW\*(C`select\*(C'\fR(2) backend. No attempt at autodetection will be done: if no |
2200 | other method takes over, select will be it. Otherwise the select backend |
2554 | other method takes over, select will be it. Otherwise the select backend |
… | |
… | |
2360 | .IP "ev_set_cb (ev, cb)" 4 |
2714 | .IP "ev_set_cb (ev, cb)" 4 |
2361 | .IX Item "ev_set_cb (ev, cb)" |
2715 | .IX Item "ev_set_cb (ev, cb)" |
2362 | .PD |
2716 | .PD |
2363 | Can be used to change the callback member declaration in each watcher, |
2717 | Can be used to change the callback member declaration in each watcher, |
2364 | and the way callbacks are invoked and set. Must expand to a struct member |
2718 | and the way callbacks are invoked and set. Must expand to a struct member |
2365 | definition and a statement, respectively. See the \fIev.v\fR header file for |
2719 | definition and a statement, respectively. See the \fIev.h\fR header file for |
2366 | their default definitions. One possible use for overriding these is to |
2720 | their default definitions. One possible use for overriding these is to |
2367 | avoid the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument in all cases, or to use |
2721 | avoid the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument in all cases, or to use |
2368 | method calls instead of plain function calls in \*(C+. |
2722 | method calls instead of plain function calls in \*(C+. |
|
|
2723 | .Sh "\s-1EXPORTED\s0 \s-1API\s0 \s-1SYMBOLS\s0" |
|
|
2724 | .IX Subsection "EXPORTED API SYMBOLS" |
|
|
2725 | If you need to re-export the \s-1API\s0 (e.g. via a dll) and you need a list of |
|
|
2726 | exported symbols, you can use the provided \fISymbol.*\fR files which list |
|
|
2727 | all public symbols, one per line: |
|
|
2728 | .Sp |
|
|
2729 | .Vb 2 |
|
|
2730 | \& Symbols.ev for libev proper |
|
|
2731 | \& Symbols.event for the libevent emulation |
|
|
2732 | .Ve |
|
|
2733 | .Sp |
|
|
2734 | This can also be used to rename all public symbols to avoid clashes with |
|
|
2735 | multiple versions of libev linked together (which is obviously bad in |
|
|
2736 | itself, but sometimes it is inconvinient to avoid this). |
|
|
2737 | .Sp |
|
|
2738 | A sed command like this will create wrapper \f(CW\*(C`#define\*(C'\fR's that you need to |
|
|
2739 | include before including \fIev.h\fR: |
|
|
2740 | .Sp |
|
|
2741 | .Vb 1 |
|
|
2742 | \& <Symbols.ev sed -e "s/.*/#define & myprefix_&/" >wrap.h |
|
|
2743 | .Ve |
|
|
2744 | .Sp |
|
|
2745 | This would create a file \fIwrap.h\fR which essentially looks like this: |
|
|
2746 | .Sp |
|
|
2747 | .Vb 4 |
|
|
2748 | \& #define ev_backend myprefix_ev_backend |
|
|
2749 | \& #define ev_check_start myprefix_ev_check_start |
|
|
2750 | \& #define ev_check_stop myprefix_ev_check_stop |
|
|
2751 | \& ... |
|
|
2752 | .Ve |
2369 | .Sh "\s-1EXAMPLES\s0" |
2753 | .Sh "\s-1EXAMPLES\s0" |
2370 | .IX Subsection "EXAMPLES" |
2754 | .IX Subsection "EXAMPLES" |
2371 | For a real-world example of a program the includes libev |
2755 | For a real-world example of a program the includes libev |
2372 | verbatim, you can have a look at the \s-1EV\s0 perl module |
2756 | verbatim, you can have a look at the \s-1EV\s0 perl module |
2373 | (<http://software.schmorp.de/pkg/EV.html>). It has the libev files in |
2757 | (<http://software.schmorp.de/pkg/EV.html>). It has the libev files in |
… | |
… | |
2404 | .SH "COMPLEXITIES" |
2788 | .SH "COMPLEXITIES" |
2405 | .IX Header "COMPLEXITIES" |
2789 | .IX Header "COMPLEXITIES" |
2406 | In this section the complexities of (many of) the algorithms used inside |
2790 | In this section the complexities of (many of) the algorithms used inside |
2407 | libev will be explained. For complexity discussions about backends see the |
2791 | libev will be explained. For complexity discussions about backends see the |
2408 | documentation for \f(CW\*(C`ev_default_init\*(C'\fR. |
2792 | documentation for \f(CW\*(C`ev_default_init\*(C'\fR. |
|
|
2793 | .Sp |
|
|
2794 | All of the following are about amortised time: If an array needs to be |
|
|
2795 | extended, libev needs to realloc and move the whole array, but this |
|
|
2796 | happens asymptotically never with higher number of elements, so O(1) might |
|
|
2797 | mean it might do a lengthy realloc operation in rare cases, but on average |
|
|
2798 | it is much faster and asymptotically approaches constant time. |
2409 | .RS 4 |
2799 | .RS 4 |
2410 | .IP "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" 4 |
2800 | .IP "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" 4 |
2411 | .IX Item "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" |
2801 | .IX Item "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" |
2412 | This means that, when you have a watcher that triggers in one hour and |
2802 | This means that, when you have a watcher that triggers in one hour and |
2413 | there are 100 watchers that would trigger before that then inserting will |
2803 | there are 100 watchers that would trigger before that then inserting will |
… | |
… | |
2416 | .IX Item "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)" |
2806 | .IX Item "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)" |
2417 | That means that for changing a timer costs less than removing/adding them |
2807 | That means that for changing a timer costs less than removing/adding them |
2418 | as only the relative motion in the event queue has to be paid for. |
2808 | as only the relative motion in the event queue has to be paid for. |
2419 | .IP "Starting io/check/prepare/idle/signal/child watchers: O(1)" 4 |
2809 | .IP "Starting io/check/prepare/idle/signal/child watchers: O(1)" 4 |
2420 | .IX Item "Starting io/check/prepare/idle/signal/child watchers: O(1)" |
2810 | .IX Item "Starting io/check/prepare/idle/signal/child watchers: O(1)" |
2421 | These just add the watcher into an array or at the head of a list. If |
2811 | These just add the watcher into an array or at the head of a list. |
2422 | the array needs to be extended libev needs to realloc and move the whole |
|
|
2423 | array, but this happen asymptotically less and less with more watchers, |
|
|
2424 | thus amortised O(1). |
|
|
2425 | .IP "Stopping check/prepare/idle watchers: O(1)" 4 |
|
|
2426 | .IX Item "Stopping check/prepare/idle watchers: O(1)" |
2812 | =item Stopping check/prepare/idle watchers: O(1) |
2427 | .PD 0 |
|
|
2428 | .IP "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % \s-1EV_PID_HASHSIZE\s0))" 4 |
2813 | .IP "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % \s-1EV_PID_HASHSIZE\s0))" 4 |
2429 | .IX Item "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))" |
2814 | .IX Item "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))" |
2430 | .PD |
|
|
2431 | These watchers are stored in lists then need to be walked to find the |
2815 | These watchers are stored in lists then need to be walked to find the |
2432 | correct watcher to remove. The lists are usually short (you don't usually |
2816 | correct watcher to remove. The lists are usually short (you don't usually |
2433 | have many watchers waiting for the same fd or signal). |
2817 | have many watchers waiting for the same fd or signal). |
2434 | .IP "Finding the next timer per loop iteration: O(1)" 4 |
2818 | .IP "Finding the next timer per loop iteration: O(1)" 4 |
2435 | .IX Item "Finding the next timer per loop iteration: O(1)" |
2819 | .IX Item "Finding the next timer per loop iteration: O(1)" |