… | |
… | |
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-12" "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 ()" |
… | |
… | |
457 | 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). |
458 | .ie n .IP """EVBACKEND_EPOLL"" (value 4, Linux)" 4 |
465 | .ie n .IP """EVBACKEND_EPOLL"" (value 4, Linux)" 4 |
459 | .el .IP "\f(CWEVBACKEND_EPOLL\fR (value 4, Linux)" 4 |
466 | .el .IP "\f(CWEVBACKEND_EPOLL\fR (value 4, Linux)" 4 |
460 | .IX Item "EVBACKEND_EPOLL (value 4, Linux)" |
467 | .IX Item "EVBACKEND_EPOLL (value 4, Linux)" |
461 | 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, |
462 | but it scales phenomenally better. While poll and select usually scale like |
469 | but it scales phenomenally better. While poll and select usually scale |
463 | 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), |
464 | 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: |
465 | .Sp |
475 | .Sp |
466 | 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 |
467 | 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 |
468 | (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 |
469 | 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 |
470 | well if you register events for both fds. |
480 | very well if you register events for both fds. |
471 | .Sp |
481 | .Sp |
472 | Please note that epoll sometimes generates spurious notifications, so you |
482 | Please note that epoll sometimes generates spurious notifications, so you |
473 | 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 |
474 | (or space) is available. |
484 | (or space) is available. |
475 | .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 |
476 | .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 |
477 | .IX Item "EVBACKEND_KQUEUE (value 8, most BSD clones)" |
487 | .IX Item "EVBACKEND_KQUEUE (value 8, most BSD clones)" |
478 | 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 |
479 | 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 |
480 | 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 |
481 | 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" |
482 | 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 |
483 | \&\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. |
484 | .Sp |
496 | .Sp |
485 | 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 |
486 | kernel is more efficient (which says nothing about its actual speed, of |
498 | kernel is more efficient (which says nothing about its actual speed, |
487 | 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 |
488 | 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 |
489 | 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. |
490 | .ie n .IP """EVBACKEND_DEVPOLL"" (value 16, Solaris 8)" 4 |
503 | .ie n .IP """EVBACKEND_DEVPOLL"" (value 16, Solaris 8)" 4 |
491 | .el .IP "\f(CWEVBACKEND_DEVPOLL\fR (value 16, Solaris 8)" 4 |
504 | .el .IP "\f(CWEVBACKEND_DEVPOLL\fR (value 16, Solaris 8)" 4 |
492 | .IX Item "EVBACKEND_DEVPOLL (value 16, Solaris 8)" |
505 | .IX Item "EVBACKEND_DEVPOLL (value 16, Solaris 8)" |
493 | This is not implemented yet (and might never be). |
506 | This is not implemented yet (and might never be). |
494 | .ie n .IP """EVBACKEND_PORT"" (value 32, Solaris 10)" 4 |
507 | .ie n .IP """EVBACKEND_PORT"" (value 32, Solaris 10)" 4 |
495 | .el .IP "\f(CWEVBACKEND_PORT\fR (value 32, Solaris 10)" 4 |
508 | .el .IP "\f(CWEVBACKEND_PORT\fR (value 32, Solaris 10)" 4 |
496 | .IX Item "EVBACKEND_PORT (value 32, Solaris 10)" |
509 | .IX Item "EVBACKEND_PORT (value 32, Solaris 10)" |
497 | 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, |
498 | 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)). |
499 | .Sp |
512 | .Sp |
500 | 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 |
501 | 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 |
502 | blocking when no data (or space) is available. |
515 | blocking when no data (or space) is available. |
503 | .ie n .IP """EVBACKEND_ALL""" 4 |
516 | .ie n .IP """EVBACKEND_ALL""" 4 |
504 | .el .IP "\f(CWEVBACKEND_ALL\fR" 4 |
517 | .el .IP "\f(CWEVBACKEND_ALL\fR" 4 |
505 | .IX Item "EVBACKEND_ALL" |
518 | .IX Item "EVBACKEND_ALL" |
… | |
… | |
555 | Destroys the default loop again (frees all memory and kernel state |
568 | Destroys the default loop again (frees all memory and kernel state |
556 | 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 |
557 | 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 |
558 | responsibility to either stop all watchers cleanly yoursef \fIbefore\fR |
571 | responsibility to either stop all watchers cleanly yoursef \fIbefore\fR |
559 | 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 |
560 | 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 |
561 | 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). |
562 | .IP "ev_loop_destroy (loop)" 4 |
584 | .IP "ev_loop_destroy (loop)" 4 |
563 | .IX Item "ev_loop_destroy (loop)" |
585 | .IX Item "ev_loop_destroy (loop)" |
564 | 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 |
565 | earlier call to \f(CW\*(C`ev_loop_new\*(C'\fR. |
587 | earlier call to \f(CW\*(C`ev_loop_new\*(C'\fR. |
566 | .IP "ev_default_fork ()" 4 |
588 | .IP "ev_default_fork ()" 4 |
… | |
… | |
607 | .IX Item "ev_tstamp ev_now (loop)" |
629 | .IX Item "ev_tstamp ev_now (loop)" |
608 | 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 |
609 | received events and started processing them. This timestamp does not |
631 | received events and started processing them. This timestamp does not |
610 | 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 |
611 | 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 |
612 | event occuring (or more correctly, libev finding out about it). |
634 | event occurring (or more correctly, libev finding out about it). |
613 | .IP "ev_loop (loop, int flags)" 4 |
635 | .IP "ev_loop (loop, int flags)" 4 |
614 | .IX Item "ev_loop (loop, int flags)" |
636 | .IX Item "ev_loop (loop, int flags)" |
615 | 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 |
616 | 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 |
617 | events. |
639 | events. |
… | |
… | |
707 | .Sp |
729 | .Sp |
708 | .Vb 2 |
730 | .Vb 2 |
709 | \& ev_ref (loop); |
731 | \& ev_ref (loop); |
710 | \& ev_signal_stop (loop, &exitsig); |
732 | \& ev_signal_stop (loop, &exitsig); |
711 | .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. |
712 | .SH "ANATOMY OF A WATCHER" |
769 | .SH "ANATOMY OF A WATCHER" |
713 | .IX Header "ANATOMY OF A WATCHER" |
770 | .IX Header "ANATOMY OF A WATCHER" |
714 | 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 |
715 | 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 |
716 | 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: |
… | |
… | |
1069 | its own, so its quite safe to use). |
1126 | its own, so its quite safe to use). |
1070 | .PP |
1127 | .PP |
1071 | \fIThe special problem of disappearing file descriptors\fR |
1128 | \fIThe special problem of disappearing file descriptors\fR |
1072 | .IX Subsection "The special problem of disappearing file descriptors" |
1129 | .IX Subsection "The special problem of disappearing file descriptors" |
1073 | .PP |
1130 | .PP |
1074 | Some backends (e.g kqueue, epoll) need to be told about closing a file |
1131 | Some backends (e.g. kqueue, epoll) need to be told about closing a file |
1075 | descriptor (either by calling \f(CW\*(C`close\*(C'\fR explicitly or by any other means, |
1132 | descriptor (either by calling \f(CW\*(C`close\*(C'\fR explicitly or by any other means, |
1076 | such as \f(CW\*(C`dup\*(C'\fR). The reason is that you register interest in some file |
1133 | such as \f(CW\*(C`dup\*(C'\fR). The reason is that you register interest in some file |
1077 | descriptor, but when it goes away, the operating system will silently drop |
1134 | descriptor, but when it goes away, the operating system will silently drop |
1078 | this interest. If another file descriptor with the same number then is |
1135 | this interest. If another file descriptor with the same number then is |
1079 | registered with libev, there is no efficient way to see that this is, in |
1136 | registered with libev, there is no efficient way to see that this is, in |
… | |
… | |
1087 | descriptor even if the file descriptor number itself did not change. |
1144 | descriptor even if the file descriptor number itself did not change. |
1088 | .PP |
1145 | .PP |
1089 | This is how one would do it normally anyway, the important point is that |
1146 | This is how one would do it normally anyway, the important point is that |
1090 | the libev application should not optimise around libev but should leave |
1147 | the libev application should not optimise around libev but should leave |
1091 | optimisations to libev. |
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" |
1092 | .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 |
1093 | .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)" |
1094 | .PD 0 |
1178 | .PD 0 |
1095 | .IP "ev_io_set (ev_io *, int fd, int events)" 4 |
1179 | .IP "ev_io_set (ev_io *, int fd, int events)" 4 |
1096 | .IX Item "ev_io_set (ev_io *, int fd, int events)" |
1180 | .IX Item "ev_io_set (ev_io *, int fd, int events)" |
… | |
… | |
1149 | .Ve |
1233 | .Ve |
1150 | .PP |
1234 | .PP |
1151 | 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, |
1152 | 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 |
1153 | 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" |
1154 | .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 |
1155 | .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)" |
1156 | .PD 0 |
1243 | .PD 0 |
1157 | .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 |
1158 | .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)" |
… | |
… | |
1269 | rules. |
1356 | rules. |
1270 | .PP |
1357 | .PP |
1271 | 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 |
1272 | 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 |
1273 | 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" |
1274 | .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 |
1275 | .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)" |
1276 | .PD 0 |
1366 | .PD 0 |
1277 | .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 |
1278 | .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)" |
… | |
… | |
1370 | .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 |
1371 | .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]" |
1372 | 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 |
1373 | 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 |
1374 | 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. |
1375 | .PP |
1469 | .PP |
1376 | Example: Call a callback every hour, or, more precisely, whenever the |
1470 | Example: Call a callback every hour, or, more precisely, whenever the |
1377 | system clock is divisible by 3600. The callback invocation times have |
1471 | system clock is divisible by 3600. The callback invocation times have |
1378 | potentially a lot of jittering, but good long-term stability. |
1472 | potentially a lot of jittering, but good long-term stability. |
1379 | .PP |
1473 | .PP |
… | |
… | |
1429 | first watcher gets started will libev actually register a signal watcher |
1523 | first watcher gets started will libev actually register a signal watcher |
1430 | 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 |
1431 | 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 |
1432 | 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 |
1433 | \&\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" |
1434 | .IP "ev_signal_init (ev_signal *, callback, int signum)" 4 |
1531 | .IP "ev_signal_init (ev_signal *, callback, int signum)" 4 |
1435 | .IX Item "ev_signal_init (ev_signal *, callback, int signum)" |
1532 | .IX Item "ev_signal_init (ev_signal *, callback, int signum)" |
1436 | .PD 0 |
1533 | .PD 0 |
1437 | .IP "ev_signal_set (ev_signal *, int signum)" 4 |
1534 | .IP "ev_signal_set (ev_signal *, int signum)" 4 |
1438 | .IX Item "ev_signal_set (ev_signal *, int signum)" |
1535 | .IX Item "ev_signal_set (ev_signal *, int signum)" |
… | |
… | |
1445 | .ie n .Sh """ev_child"" \- watch out for process status changes" |
1542 | .ie n .Sh """ev_child"" \- watch out for process status changes" |
1446 | .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" |
1447 | .IX Subsection "ev_child - watch out for process status changes" |
1544 | .IX Subsection "ev_child - watch out for process status changes" |
1448 | 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 |
1449 | 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" |
1450 | .IP "ev_child_init (ev_child *, callback, int pid)" 4 |
1550 | .IP "ev_child_init (ev_child *, callback, int pid)" 4 |
1451 | .IX Item "ev_child_init (ev_child *, callback, int pid)" |
1551 | .IX Item "ev_child_init (ev_child *, callback, int pid)" |
1452 | .PD 0 |
1552 | .PD 0 |
1453 | .IP "ev_child_set (ev_child *, int pid)" 4 |
1553 | .IP "ev_child_set (ev_child *, int pid)" 4 |
1454 | .IX Item "ev_child_set (ev_child *, int pid)" |
1554 | .IX Item "ev_child_set (ev_child *, int pid)" |
… | |
… | |
1519 | 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 |
1520 | 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 |
1521 | 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 |
1522 | 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 |
1523 | polling. |
1623 | polling. |
|
|
1624 | .PP |
|
|
1625 | \fIWatcher-Specific Functions and Data Members\fR |
|
|
1626 | .IX Subsection "Watcher-Specific Functions and Data Members" |
1524 | .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 |
1525 | .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)" |
1526 | .PD 0 |
1629 | .PD 0 |
1527 | .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 |
1528 | .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)" |
… | |
… | |
1607 | .PP |
1710 | .PP |
1608 | Apart from keeping your process non-blocking (which is a useful |
1711 | Apart from keeping your process non-blocking (which is a useful |
1609 | 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 |
1610 | \&\*(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 |
1611 | 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" |
1612 | .IP "ev_idle_init (ev_signal *, callback)" 4 |
1718 | .IP "ev_idle_init (ev_signal *, callback)" 4 |
1613 | .IX Item "ev_idle_init (ev_signal *, callback)" |
1719 | .IX Item "ev_idle_init (ev_signal *, callback)" |
1614 | 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 |
1615 | 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, |
1616 | believe me. |
1722 | believe me. |
… | |
… | |
1681 | supports this, they will be called before other \f(CW\*(C`ev_check\*(C'\fR watchers did |
1787 | supports this, they will be called before other \f(CW\*(C`ev_check\*(C'\fR watchers did |
1682 | their job. As \f(CW\*(C`ev_check\*(C'\fR watchers are often used to embed other event |
1788 | their job. As \f(CW\*(C`ev_check\*(C'\fR watchers are often used to embed other event |
1683 | loops those other event loops might be in an unusable state until their |
1789 | loops those other event loops might be in an unusable state until their |
1684 | \&\f(CW\*(C`ev_check\*(C'\fR watcher ran (always remind yourself to coexist peacefully with |
1790 | \&\f(CW\*(C`ev_check\*(C'\fR watcher ran (always remind yourself to coexist peacefully with |
1685 | others). |
1791 | others). |
|
|
1792 | .PP |
|
|
1793 | \fIWatcher-Specific Functions and Data Members\fR |
|
|
1794 | .IX Subsection "Watcher-Specific Functions and Data Members" |
1686 | .IP "ev_prepare_init (ev_prepare *, callback)" 4 |
1795 | .IP "ev_prepare_init (ev_prepare *, callback)" 4 |
1687 | .IX Item "ev_prepare_init (ev_prepare *, callback)" |
1796 | .IX Item "ev_prepare_init (ev_prepare *, callback)" |
1688 | .PD 0 |
1797 | .PD 0 |
1689 | .IP "ev_check_init (ev_check *, callback)" 4 |
1798 | .IP "ev_check_init (ev_check *, callback)" 4 |
1690 | .IX Item "ev_check_init (ev_check *, callback)" |
1799 | .IX Item "ev_check_init (ev_check *, callback)" |
… | |
… | |
1867 | .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..." |
1868 | .IX Subsection "ev_embed - when one backend isn't enough..." |
1977 | .IX Subsection "ev_embed - when one backend isn't enough..." |
1869 | 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 |
1870 | 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 |
1871 | 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 |
1872 | fashion and must not be used). |
1981 | fashion and must not be used). (See portability notes, below). |
1873 | .PP |
1982 | .PP |
1874 | 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 |
1875 | prioritise I/O. |
1984 | prioritise I/O. |
1876 | .PP |
1985 | .PP |
1877 | 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 |
… | |
… | |
1937 | \& ev_embed_start (loop_hi, &embed); |
2046 | \& ev_embed_start (loop_hi, &embed); |
1938 | \& } |
2047 | \& } |
1939 | \& else |
2048 | \& else |
1940 | \& loop_lo = loop_hi; |
2049 | \& loop_lo = loop_hi; |
1941 | .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" |
1942 | .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 |
1943 | .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)" |
1944 | .PD 0 |
2071 | .PD 0 |
1945 | .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 |
1946 | .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)" |
… | |
… | |
1953 | .IP "ev_embed_sweep (loop, ev_embed *)" 4 |
2080 | .IP "ev_embed_sweep (loop, ev_embed *)" 4 |
1954 | .IX Item "ev_embed_sweep (loop, ev_embed *)" |
2081 | .IX Item "ev_embed_sweep (loop, ev_embed *)" |
1955 | 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 |
1956 | 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 |
1957 | apropriate way for embedded loops. |
2084 | apropriate way for embedded loops. |
1958 | .IP "struct ev_loop *loop [read\-only]" 4 |
2085 | .IP "struct ev_loop *other [read\-only]" 4 |
1959 | .IX Item "struct ev_loop *loop [read-only]" |
2086 | .IX Item "struct ev_loop *other [read-only]" |
1960 | The embedded event loop. |
2087 | The embedded event loop. |
1961 | .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" |
1962 | .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" |
1963 | .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" |
1964 | 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 |
… | |
… | |
1966 | \&\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 |
1967 | 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, |
1968 | 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 |
1969 | \&\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 |
1970 | 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" |
1971 | .IP "ev_fork_init (ev_signal *, callback)" 4 |
2101 | .IP "ev_fork_init (ev_signal *, callback)" 4 |
1972 | .IX Item "ev_fork_init (ev_signal *, callback)" |
2102 | .IX Item "ev_fork_init (ev_signal *, callback)" |
1973 | 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 |
1974 | 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, |
1975 | believe me. |
2105 | believe me. |
… | |
… | |
2169 | 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 |
2170 | constructor already stores the event loop. |
2300 | constructor already stores the event loop. |
2171 | .IP "w\->stop ()" 4 |
2301 | .IP "w\->stop ()" 4 |
2172 | .IX Item "w->stop ()" |
2302 | .IX Item "w->stop ()" |
2173 | 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. |
2174 | .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 |
2175 | .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 |
2176 | .IX Item "w->again () ev::timer, ev::periodic only" |
2306 | .IX Item "w->again () (ev::timer, ev::periodic only)" |
2177 | 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 |
2178 | \&\f(CW\*(C`ev_TYPE_again\*(C'\fR function. |
2308 | \&\f(CW\*(C`ev_TYPE_again\*(C'\fR function. |
2179 | .ie n .IP "w\->sweep () ""ev::embed"" only" 4 |
2309 | .ie n .IP "w\->sweep () (""ev::embed"" only)" 4 |
2180 | .el .IP "w\->sweep () \f(CWev::embed\fR only" 4 |
2310 | .el .IP "w\->sweep () (\f(CWev::embed\fR only)" 4 |
2181 | .IX Item "w->sweep () ev::embed only" |
2311 | .IX Item "w->sweep () (ev::embed only)" |
2182 | Invokes \f(CW\*(C`ev_embed_sweep\*(C'\fR. |
2312 | Invokes \f(CW\*(C`ev_embed_sweep\*(C'\fR. |
2183 | .ie n .IP "w\->update () ""ev::stat"" only" 4 |
2313 | .ie n .IP "w\->update () (""ev::stat"" only)" 4 |
2184 | .el .IP "w\->update () \f(CWev::stat\fR only" 4 |
2314 | .el .IP "w\->update () (\f(CWev::stat\fR only)" 4 |
2185 | .IX Item "w->update () ev::stat only" |
2315 | .IX Item "w->update () (ev::stat only)" |
2186 | Invokes \f(CW\*(C`ev_stat_stat\*(C'\fR. |
2316 | Invokes \f(CW\*(C`ev_stat_stat\*(C'\fR. |
2187 | .RE |
2317 | .RE |
2188 | .RS 4 |
2318 | .RS 4 |
2189 | .RE |
2319 | .RE |
2190 | .PP |
2320 | .PP |
… | |
… | |
2214 | \& io.start (fd, ev::READ); |
2344 | \& io.start (fd, ev::READ); |
2215 | \& } |
2345 | \& } |
2216 | .Ve |
2346 | .Ve |
2217 | .SH "MACRO MAGIC" |
2347 | .SH "MACRO MAGIC" |
2218 | .IX Header "MACRO MAGIC" |
2348 | .IX Header "MACRO MAGIC" |
2219 | 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 |
2220 | \&\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) |
2221 | 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. |
2222 | .PP |
2352 | .PP |
2223 | 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 |
2224 | following macros are defined: |
2354 | following macros are defined: |
2225 | .ie n .IP """EV_A""\fR, \f(CW""EV_A_""" 4 |
2355 | .ie n .IP """EV_A""\fR, \f(CW""EV_A_""" 4 |
2226 | .el .IP "\f(CWEV_A\fR, \f(CWEV_A_\fR" 4 |
2356 | .el .IP "\f(CWEV_A\fR, \f(CWEV_A_\fR" 4 |
… | |
… | |
2285 | Libev can (and often is) directly embedded into host |
2415 | Libev can (and often is) directly embedded into host |
2286 | applications. Examples of applications that embed it include the Deliantra |
2416 | applications. Examples of applications that embed it include the Deliantra |
2287 | 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) |
2288 | and rxvt\-unicode. |
2418 | and rxvt\-unicode. |
2289 | .PP |
2419 | .PP |
2290 | 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 |
2291 | 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 |
2292 | 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 |
2293 | libev somewhere in your source tree). |
2423 | libev somewhere in your source tree). |
2294 | .Sh "\s-1FILESETS\s0" |
2424 | .Sh "\s-1FILESETS\s0" |
2295 | .IX Subsection "FILESETS" |
2425 | .IX Subsection "FILESETS" |
… | |
… | |
2400 | .IX Item "EV_USE_MONOTONIC" |
2530 | .IX Item "EV_USE_MONOTONIC" |
2401 | 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 |
2402 | monotonic clock option at both compiletime and runtime. Otherwise no use |
2532 | monotonic clock option at both compiletime and runtime. Otherwise no use |
2403 | 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 |
2404 | 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 |
2405 | the functionality isn't available is safe, though, althoguh you have |
2535 | the functionality isn't available is safe, though, although you have |
2406 | 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 |
2407 | function is hiding in (often \fI\-lrt\fR). |
2537 | function is hiding in (often \fI\-lrt\fR). |
2408 | .IP "\s-1EV_USE_REALTIME\s0" 4 |
2538 | .IP "\s-1EV_USE_REALTIME\s0" 4 |
2409 | .IX Item "EV_USE_REALTIME" |
2539 | .IX Item "EV_USE_REALTIME" |
2410 | 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 |
2411 | realtime clock option at compiletime (and assume its availability at |
2541 | realtime clock option at compiletime (and assume its availability at |
2412 | 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 |
2413 | 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 |
2414 | (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 |
2415 | 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. |
2416 | .IP "\s-1EV_USE_SELECT\s0" 4 |
2550 | .IP "\s-1EV_USE_SELECT\s0" 4 |
2417 | .IX Item "EV_USE_SELECT" |
2551 | .IX Item "EV_USE_SELECT" |
2418 | 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 |
2419 | \&\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 |
2420 | 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 |
… | |
… | |
2580 | .IP "ev_set_cb (ev, cb)" 4 |
2714 | .IP "ev_set_cb (ev, cb)" 4 |
2581 | .IX Item "ev_set_cb (ev, cb)" |
2715 | .IX Item "ev_set_cb (ev, cb)" |
2582 | .PD |
2716 | .PD |
2583 | 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, |
2584 | 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 |
2585 | 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 |
2586 | their default definitions. One possible use for overriding these is to |
2720 | their default definitions. One possible use for overriding these is to |
2587 | 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 |
2588 | 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 |
2589 | .Sh "\s-1EXAMPLES\s0" |
2753 | .Sh "\s-1EXAMPLES\s0" |
2590 | .IX Subsection "EXAMPLES" |
2754 | .IX Subsection "EXAMPLES" |
2591 | For a real-world example of a program the includes libev |
2755 | For a real-world example of a program the includes libev |
2592 | 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 |
2593 | (<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 |