… | |
… | |
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 ""<STANDARD INPUT>" 1" |
132 | .TH "<STANDARD INPUT>" 1 "2007-11-27" "perl v5.8.8" "User Contributed Perl Documentation" |
132 | .TH "<STANDARD INPUT>" 1 "2007-12-07" "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 |
… | |
… | |
196 | \& return 0; |
196 | \& return 0; |
197 | \& } |
197 | \& } |
198 | .Ve |
198 | .Ve |
199 | .SH "DESCRIPTION" |
199 | .SH "DESCRIPTION" |
200 | .IX Header "DESCRIPTION" |
200 | .IX Header "DESCRIPTION" |
|
|
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 |
|
|
203 | time: <http://cvs.schmorp.de/libev/ev.html>. |
|
|
204 | .PP |
201 | 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 |
202 | file descriptor being readable or a timeout occuring), and it will manage |
206 | file descriptor being readable or a timeout occuring), and it will manage |
203 | these event sources and provide your program with events. |
207 | these event sources and provide your program with events. |
204 | .PP |
208 | .PP |
205 | 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 | watchers\fR, which are relatively small C structures you initialise with the |
214 | watchers\fR, which are relatively small C structures you initialise with the |
211 | details of the event, and then hand it over to libev by \fIstarting\fR the |
215 | details of the event, and then hand it over to libev by \fIstarting\fR the |
212 | watcher. |
216 | watcher. |
213 | .SH "FEATURES" |
217 | .SH "FEATURES" |
214 | .IX Header "FEATURES" |
218 | .IX Header "FEATURES" |
215 | Libev supports \f(CW\*(C`select\*(C'\fR, \f(CW\*(C`poll\*(C'\fR, the linux-specific \f(CW\*(C`epoll\*(C'\fR, the |
219 | Libev supports \f(CW\*(C`select\*(C'\fR, \f(CW\*(C`poll\*(C'\fR, the Linux-specific \f(CW\*(C`epoll\*(C'\fR, the |
216 | bsd-specific \f(CW\*(C`kqueue\*(C'\fR and the solaris-specific event port mechanisms |
220 | BSD-specific \f(CW\*(C`kqueue\*(C'\fR and the Solaris-specific event port mechanisms |
217 | for file descriptor events (\f(CW\*(C`ev_io\*(C'\fR), relative timers (\f(CW\*(C`ev_timer\*(C'\fR), |
221 | for file descriptor events (\f(CW\*(C`ev_io\*(C'\fR), the Linux \f(CW\*(C`inotify\*(C'\fR interface |
|
|
222 | (for \f(CW\*(C`ev_stat\*(C'\fR), relative timers (\f(CW\*(C`ev_timer\*(C'\fR), absolute timers |
218 | absolute timers with customised rescheduling (\f(CW\*(C`ev_periodic\*(C'\fR), synchronous |
223 | with customised rescheduling (\f(CW\*(C`ev_periodic\*(C'\fR), synchronous signals |
219 | signals (\f(CW\*(C`ev_signal\*(C'\fR), process status change events (\f(CW\*(C`ev_child\*(C'\fR), and |
224 | (\f(CW\*(C`ev_signal\*(C'\fR), process status change events (\f(CW\*(C`ev_child\*(C'\fR), and event |
220 | event watchers dealing with the event loop mechanism itself (\f(CW\*(C`ev_idle\*(C'\fR, |
225 | watchers dealing with the event loop mechanism itself (\f(CW\*(C`ev_idle\*(C'\fR, |
221 | \&\f(CW\*(C`ev_embed\*(C'\fR, \f(CW\*(C`ev_prepare\*(C'\fR and \f(CW\*(C`ev_check\*(C'\fR watchers) as well as |
226 | \&\f(CW\*(C`ev_embed\*(C'\fR, \f(CW\*(C`ev_prepare\*(C'\fR and \f(CW\*(C`ev_check\*(C'\fR watchers) as well as |
222 | file watchers (\f(CW\*(C`ev_stat\*(C'\fR) and even limited support for fork events |
227 | file watchers (\f(CW\*(C`ev_stat\*(C'\fR) and even limited support for fork events |
223 | (\f(CW\*(C`ev_fork\*(C'\fR). |
228 | (\f(CW\*(C`ev_fork\*(C'\fR). |
224 | .PP |
229 | .PP |
225 | It also is quite fast (see this |
230 | It also is quite fast (see this |
… | |
… | |
304 | might be supported on the current system, you would need to look at |
309 | might be supported on the current system, you would need to look at |
305 | \&\f(CW\*(C`ev_embeddable_backends () & ev_supported_backends ()\*(C'\fR, likewise for |
310 | \&\f(CW\*(C`ev_embeddable_backends () & ev_supported_backends ()\*(C'\fR, likewise for |
306 | recommended ones. |
311 | recommended ones. |
307 | .Sp |
312 | .Sp |
308 | See the description of \f(CW\*(C`ev_embed\*(C'\fR watchers for more info. |
313 | See the description of \f(CW\*(C`ev_embed\*(C'\fR watchers for more info. |
309 | .IP "ev_set_allocator (void *(*cb)(void *ptr, size_t size))" 4 |
314 | .IP "ev_set_allocator (void *(*cb)(void *ptr, long size))" 4 |
310 | .IX Item "ev_set_allocator (void *(*cb)(void *ptr, size_t size))" |
315 | .IX Item "ev_set_allocator (void *(*cb)(void *ptr, long size))" |
311 | Sets the allocation function to use (the prototype and semantics are |
316 | Sets the allocation function to use (the prototype is similar \- the |
312 | identical to the realloc C function). It is used to allocate and free |
317 | semantics is identical \- to the realloc C function). It is used to |
313 | memory (no surprises here). If it returns zero when memory needs to be |
318 | allocate and free memory (no surprises here). If it returns zero when |
314 | allocated, the library might abort or take some potentially destructive |
319 | memory needs to be allocated, the library might abort or take some |
315 | action. The default is your system realloc function. |
320 | potentially destructive action. The default is your system realloc |
|
|
321 | function. |
316 | .Sp |
322 | .Sp |
317 | You could override this function in high-availability programs to, say, |
323 | You could override this function in high-availability programs to, say, |
318 | free some memory if it cannot allocate memory, to use a special allocator, |
324 | free some memory if it cannot allocate memory, to use a special allocator, |
319 | or even to sleep a while and retry until some memory is available. |
325 | or even to sleep a while and retry until some memory is available. |
320 | .Sp |
326 | .Sp |
… | |
… | |
409 | or setgid) then libev will \fInot\fR look at the environment variable |
415 | or setgid) then libev will \fInot\fR look at the environment variable |
410 | \&\f(CW\*(C`LIBEV_FLAGS\*(C'\fR. Otherwise (the default), this environment variable will |
416 | \&\f(CW\*(C`LIBEV_FLAGS\*(C'\fR. Otherwise (the default), this environment variable will |
411 | override the flags completely if it is found in the environment. This is |
417 | override the flags completely if it is found in the environment. This is |
412 | useful to try out specific backends to test their performance, or to work |
418 | useful to try out specific backends to test their performance, or to work |
413 | around bugs. |
419 | around bugs. |
|
|
420 | .ie n .IP """EVFLAG_FORKCHECK""" 4 |
|
|
421 | .el .IP "\f(CWEVFLAG_FORKCHECK\fR" 4 |
|
|
422 | .IX Item "EVFLAG_FORKCHECK" |
|
|
423 | Instead of calling \f(CW\*(C`ev_default_fork\*(C'\fR or \f(CW\*(C`ev_loop_fork\*(C'\fR manually after |
|
|
424 | a fork, you can also make libev check for a fork in each iteration by |
|
|
425 | enabling this flag. |
|
|
426 | .Sp |
|
|
427 | This works by calling \f(CW\*(C`getpid ()\*(C'\fR on every iteration of the loop, |
|
|
428 | and thus this might slow down your event loop if you do a lot of loop |
|
|
429 | iterations and little real work, but is usually not noticeable (on my |
|
|
430 | Linux system for example, \f(CW\*(C`getpid\*(C'\fR is actually a simple 5\-insn sequence |
|
|
431 | without a syscall and thus \fIvery\fR fast, but my Linux system also has |
|
|
432 | \&\f(CW\*(C`pthread_atfork\*(C'\fR which is even faster). |
|
|
433 | .Sp |
|
|
434 | The big advantage of this flag is that you can forget about fork (and |
|
|
435 | forget about forgetting to tell libev about forking) when you use this |
|
|
436 | flag. |
|
|
437 | .Sp |
|
|
438 | This flag setting cannot be overriden or specified in the \f(CW\*(C`LIBEV_FLAGS\*(C'\fR |
|
|
439 | environment variable. |
414 | .ie n .IP """EVBACKEND_SELECT"" (value 1, portable select backend)" 4 |
440 | .ie n .IP """EVBACKEND_SELECT"" (value 1, portable select backend)" 4 |
415 | .el .IP "\f(CWEVBACKEND_SELECT\fR (value 1, portable select backend)" 4 |
441 | .el .IP "\f(CWEVBACKEND_SELECT\fR (value 1, portable select backend)" 4 |
416 | .IX Item "EVBACKEND_SELECT (value 1, portable select backend)" |
442 | .IX Item "EVBACKEND_SELECT (value 1, portable select backend)" |
417 | This is your standard \fIselect\fR\|(2) backend. Not \fIcompletely\fR standard, as |
443 | This is your standard \fIselect\fR\|(2) backend. Not \fIcompletely\fR standard, as |
418 | libev tries to roll its own fd_set with no limits on the number of fds, |
444 | libev tries to roll its own fd_set with no limits on the number of fds, |
… | |
… | |
559 | .IP "ev_loop_fork (loop)" 4 |
585 | .IP "ev_loop_fork (loop)" 4 |
560 | .IX Item "ev_loop_fork (loop)" |
586 | .IX Item "ev_loop_fork (loop)" |
561 | Like \f(CW\*(C`ev_default_fork\*(C'\fR, but acts on an event loop created by |
587 | Like \f(CW\*(C`ev_default_fork\*(C'\fR, but acts on an event loop created by |
562 | \&\f(CW\*(C`ev_loop_new\*(C'\fR. Yes, you have to call this on every allocated event loop |
588 | \&\f(CW\*(C`ev_loop_new\*(C'\fR. Yes, you have to call this on every allocated event loop |
563 | after fork, and how you do this is entirely your own problem. |
589 | after fork, and how you do this is entirely your own problem. |
|
|
590 | .IP "unsigned int ev_loop_count (loop)" 4 |
|
|
591 | .IX Item "unsigned int ev_loop_count (loop)" |
|
|
592 | Returns the count of loop iterations for the loop, which is identical to |
|
|
593 | the number of times libev did poll for new events. It starts at \f(CW0\fR and |
|
|
594 | happily wraps around with enough iterations. |
|
|
595 | .Sp |
|
|
596 | This value can sometimes be useful as a generation counter of sorts (it |
|
|
597 | \&\*(L"ticks\*(R" the number of loop iterations), as it roughly corresponds with |
|
|
598 | \&\f(CW\*(C`ev_prepare\*(C'\fR and \f(CW\*(C`ev_check\*(C'\fR calls. |
564 | .IP "unsigned int ev_backend (loop)" 4 |
599 | .IP "unsigned int ev_backend (loop)" 4 |
565 | .IX Item "unsigned int ev_backend (loop)" |
600 | .IX Item "unsigned int ev_backend (loop)" |
566 | Returns one of the \f(CW\*(C`EVBACKEND_*\*(C'\fR flags indicating the event backend in |
601 | Returns one of the \f(CW\*(C`EVBACKEND_*\*(C'\fR flags indicating the event backend in |
567 | use. |
602 | use. |
568 | .IP "ev_tstamp ev_now (loop)" 4 |
603 | .IP "ev_tstamp ev_now (loop)" 4 |
… | |
… | |
856 | Returns a true value iff the watcher is pending, (i.e. it has outstanding |
891 | Returns a true value iff the watcher is pending, (i.e. it has outstanding |
857 | events but its callback has not yet been invoked). As long as a watcher |
892 | events but its callback has not yet been invoked). As long as a watcher |
858 | is pending (but not active) you must not call an init function on it (but |
893 | is pending (but not active) you must not call an init function on it (but |
859 | \&\f(CW\*(C`ev_TYPE_set\*(C'\fR is safe) and you must make sure the watcher is available to |
894 | \&\f(CW\*(C`ev_TYPE_set\*(C'\fR is safe) and you must make sure the watcher is available to |
860 | libev (e.g. you cnanot \f(CW\*(C`free ()\*(C'\fR it). |
895 | libev (e.g. you cnanot \f(CW\*(C`free ()\*(C'\fR it). |
861 | .IP "callback = ev_cb (ev_TYPE *watcher)" 4 |
896 | .IP "callback ev_cb (ev_TYPE *watcher)" 4 |
862 | .IX Item "callback = ev_cb (ev_TYPE *watcher)" |
897 | .IX Item "callback ev_cb (ev_TYPE *watcher)" |
863 | Returns the callback currently set on the watcher. |
898 | Returns the callback currently set on the watcher. |
864 | .IP "ev_cb_set (ev_TYPE *watcher, callback)" 4 |
899 | .IP "ev_cb_set (ev_TYPE *watcher, callback)" 4 |
865 | .IX Item "ev_cb_set (ev_TYPE *watcher, callback)" |
900 | .IX Item "ev_cb_set (ev_TYPE *watcher, callback)" |
866 | Change the callback. You can change the callback at virtually any time |
901 | Change the callback. You can change the callback at virtually any time |
867 | (modulo threads). |
902 | (modulo threads). |
|
|
903 | .IP "ev_set_priority (ev_TYPE *watcher, priority)" 4 |
|
|
904 | .IX Item "ev_set_priority (ev_TYPE *watcher, priority)" |
|
|
905 | .PD 0 |
|
|
906 | .IP "int ev_priority (ev_TYPE *watcher)" 4 |
|
|
907 | .IX Item "int ev_priority (ev_TYPE *watcher)" |
|
|
908 | .PD |
|
|
909 | Set and query the priority of the watcher. The priority is a small |
|
|
910 | integer between \f(CW\*(C`EV_MAXPRI\*(C'\fR (default: \f(CW2\fR) and \f(CW\*(C`EV_MINPRI\*(C'\fR |
|
|
911 | (default: \f(CW\*(C`\-2\*(C'\fR). Pending watchers with higher priority will be invoked |
|
|
912 | before watchers with lower priority, but priority will not keep watchers |
|
|
913 | from being executed (except for \f(CW\*(C`ev_idle\*(C'\fR watchers). |
|
|
914 | .Sp |
|
|
915 | This means that priorities are \fIonly\fR used for ordering callback |
|
|
916 | invocation after new events have been received. This is useful, for |
|
|
917 | example, to reduce latency after idling, or more often, to bind two |
|
|
918 | watchers on the same event and make sure one is called first. |
|
|
919 | .Sp |
|
|
920 | 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. |
|
|
922 | .Sp |
|
|
923 | 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 :). |
|
|
925 | .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 |
|
|
927 | 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. |
868 | .Sh "\s-1ASSOCIATING\s0 \s-1CUSTOM\s0 \s-1DATA\s0 \s-1WITH\s0 A \s-1WATCHER\s0" |
929 | .Sh "\s-1ASSOCIATING\s0 \s-1CUSTOM\s0 \s-1DATA\s0 \s-1WITH\s0 A \s-1WATCHER\s0" |
869 | .IX Subsection "ASSOCIATING CUSTOM DATA WITH A WATCHER" |
930 | .IX Subsection "ASSOCIATING CUSTOM DATA WITH A WATCHER" |
870 | Each watcher has, by default, a member \f(CW\*(C`void *data\*(C'\fR that you can change |
931 | Each watcher has, by default, a member \f(CW\*(C`void *data\*(C'\fR that you can change |
871 | and read at any time, libev will completely ignore it. This can be used |
932 | and read at any time, libev will completely ignore it. This can be used |
872 | to associate arbitrary data with your watcher. If you need more data and |
933 | to associate arbitrary data with your watcher. If you need more data and |
… | |
… | |
893 | \& struct my_io *w = (struct my_io *)w_; |
954 | \& struct my_io *w = (struct my_io *)w_; |
894 | \& ... |
955 | \& ... |
895 | \& } |
956 | \& } |
896 | .Ve |
957 | .Ve |
897 | .PP |
958 | .PP |
898 | More interesting and less C\-conformant ways of catsing your callback type |
959 | More interesting and less C\-conformant ways of casting your callback type |
899 | have been omitted.... |
960 | instead have been omitted. |
|
|
961 | .PP |
|
|
962 | Another common scenario is having some data structure with multiple |
|
|
963 | watchers: |
|
|
964 | .PP |
|
|
965 | .Vb 6 |
|
|
966 | \& struct my_biggy |
|
|
967 | \& { |
|
|
968 | \& int some_data; |
|
|
969 | \& ev_timer t1; |
|
|
970 | \& ev_timer t2; |
|
|
971 | \& } |
|
|
972 | .Ve |
|
|
973 | .PP |
|
|
974 | In this case getting the pointer to \f(CW\*(C`my_biggy\*(C'\fR is a bit more complicated, |
|
|
975 | you need to use \f(CW\*(C`offsetof\*(C'\fR: |
|
|
976 | .PP |
|
|
977 | .Vb 1 |
|
|
978 | \& #include <stddef.h> |
|
|
979 | .Ve |
|
|
980 | .PP |
|
|
981 | .Vb 6 |
|
|
982 | \& static void |
|
|
983 | \& t1_cb (EV_P_ struct ev_timer *w, int revents) |
|
|
984 | \& { |
|
|
985 | \& struct my_biggy big = (struct my_biggy * |
|
|
986 | \& (((char *)w) - offsetof (struct my_biggy, t1)); |
|
|
987 | \& } |
|
|
988 | .Ve |
|
|
989 | .PP |
|
|
990 | .Vb 6 |
|
|
991 | \& static void |
|
|
992 | \& t2_cb (EV_P_ struct ev_timer *w, int revents) |
|
|
993 | \& { |
|
|
994 | \& struct my_biggy big = (struct my_biggy * |
|
|
995 | \& (((char *)w) - offsetof (struct my_biggy, t2)); |
|
|
996 | \& } |
|
|
997 | .Ve |
900 | .SH "WATCHER TYPES" |
998 | .SH "WATCHER TYPES" |
901 | .IX Header "WATCHER TYPES" |
999 | .IX Header "WATCHER TYPES" |
902 | This section describes each watcher in detail, but will not repeat |
1000 | This section describes each watcher in detail, but will not repeat |
903 | information given in the last section. Any initialisation/set macros, |
1001 | information given in the last section. Any initialisation/set macros, |
904 | functions and members specific to the watcher type are explained. |
1002 | functions and members specific to the watcher type are explained. |
… | |
… | |
946 | it is best to always use non-blocking I/O: An extra \f(CW\*(C`read\*(C'\fR(2) returning |
1044 | it is best to always use non-blocking I/O: An extra \f(CW\*(C`read\*(C'\fR(2) returning |
947 | \&\f(CW\*(C`EAGAIN\*(C'\fR is far preferable to a program hanging until some data arrives. |
1045 | \&\f(CW\*(C`EAGAIN\*(C'\fR is far preferable to a program hanging until some data arrives. |
948 | .PP |
1046 | .PP |
949 | If you cannot run the fd in non-blocking mode (for example you should not |
1047 | If you cannot run the fd in non-blocking mode (for example you should not |
950 | play around with an Xlib connection), then you have to seperately re-test |
1048 | play around with an Xlib connection), then you have to seperately re-test |
951 | wether a file descriptor is really ready with a known-to-be good interface |
1049 | whether a file descriptor is really ready with a known-to-be good interface |
952 | such as poll (fortunately in our Xlib example, Xlib already does this on |
1050 | such as poll (fortunately in our Xlib example, Xlib already does this on |
953 | its own, so its quite safe to use). |
1051 | its own, so its quite safe to use). |
954 | .IP "ev_io_init (ev_io *, callback, int fd, int events)" 4 |
1052 | .IP "ev_io_init (ev_io *, callback, int fd, int events)" 4 |
955 | .IX Item "ev_io_init (ev_io *, callback, int fd, int events)" |
1053 | .IX Item "ev_io_init (ev_io *, callback, int fd, int events)" |
956 | .PD 0 |
1054 | .PD 0 |
… | |
… | |
1032 | .IP "ev_timer_again (loop)" 4 |
1130 | .IP "ev_timer_again (loop)" 4 |
1033 | .IX Item "ev_timer_again (loop)" |
1131 | .IX Item "ev_timer_again (loop)" |
1034 | This will act as if the timer timed out and restart it again if it is |
1132 | This will act as if the timer timed out and restart it again if it is |
1035 | repeating. The exact semantics are: |
1133 | repeating. The exact semantics are: |
1036 | .Sp |
1134 | .Sp |
|
|
1135 | If the timer is pending, its pending status is cleared. |
|
|
1136 | .Sp |
1037 | If the timer is started but nonrepeating, stop it. |
1137 | If the timer is started but nonrepeating, stop it (as if it timed out). |
1038 | .Sp |
1138 | .Sp |
1039 | If the timer is repeating, either start it if necessary (with the repeat |
1139 | If the timer is repeating, either start it if necessary (with the |
1040 | value), or reset the running timer to the repeat value. |
1140 | \&\f(CW\*(C`repeat\*(C'\fR value), or reset the running timer to the \f(CW\*(C`repeat\*(C'\fR value. |
1041 | .Sp |
1141 | .Sp |
1042 | This sounds a bit complicated, but here is a useful and typical |
1142 | This sounds a bit complicated, but here is a useful and typical |
1043 | example: Imagine you have a tcp connection and you want a so-called |
1143 | example: Imagine you have a tcp connection and you want a so-called idle |
1044 | idle timeout, that is, you want to be called when there have been, |
1144 | timeout, that is, you want to be called when there have been, say, 60 |
1045 | say, 60 seconds of inactivity on the socket. The easiest way to do |
1145 | seconds of inactivity on the socket. The easiest way to do this is to |
1046 | this is to configure an \f(CW\*(C`ev_timer\*(C'\fR with \f(CW\*(C`after\*(C'\fR=\f(CW\*(C`repeat\*(C'\fR=\f(CW60\fR and calling |
1146 | configure an \f(CW\*(C`ev_timer\*(C'\fR with a \f(CW\*(C`repeat\*(C'\fR value of \f(CW60\fR and then call |
1047 | \&\f(CW\*(C`ev_timer_again\*(C'\fR each time you successfully read or write some data. If |
1147 | \&\f(CW\*(C`ev_timer_again\*(C'\fR each time you successfully read or write some data. If |
1048 | you go into an idle state where you do not expect data to travel on the |
1148 | you go into an idle state where you do not expect data to travel on the |
1049 | socket, you can stop the timer, and again will automatically restart it if |
1149 | socket, you can \f(CW\*(C`ev_timer_stop\*(C'\fR the timer, and \f(CW\*(C`ev_timer_again\*(C'\fR will |
1050 | need be. |
1150 | automatically restart it if need be. |
1051 | .Sp |
1151 | .Sp |
1052 | You can also ignore the \f(CW\*(C`after\*(C'\fR value and \f(CW\*(C`ev_timer_start\*(C'\fR altogether |
1152 | That means you can ignore the \f(CW\*(C`after\*(C'\fR value and \f(CW\*(C`ev_timer_start\*(C'\fR |
1053 | and only ever use the \f(CW\*(C`repeat\*(C'\fR value: |
1153 | altogether and only ever use the \f(CW\*(C`repeat\*(C'\fR value and \f(CW\*(C`ev_timer_again\*(C'\fR: |
1054 | .Sp |
1154 | .Sp |
1055 | .Vb 8 |
1155 | .Vb 8 |
1056 | \& ev_timer_init (timer, callback, 0., 5.); |
1156 | \& ev_timer_init (timer, callback, 0., 5.); |
1057 | \& ev_timer_again (loop, timer); |
1157 | \& ev_timer_again (loop, timer); |
1058 | \& ... |
1158 | \& ... |
… | |
… | |
1061 | \& ... |
1161 | \& ... |
1062 | \& timer->again = 10.; |
1162 | \& timer->again = 10.; |
1063 | \& ev_timer_again (loop, timer); |
1163 | \& ev_timer_again (loop, timer); |
1064 | .Ve |
1164 | .Ve |
1065 | .Sp |
1165 | .Sp |
1066 | This is more efficient then stopping/starting the timer eahc time you want |
1166 | This is more slightly efficient then stopping/starting the timer each time |
1067 | to modify its timeout value. |
1167 | you want to modify its timeout value. |
1068 | .IP "ev_tstamp repeat [read\-write]" 4 |
1168 | .IP "ev_tstamp repeat [read\-write]" 4 |
1069 | .IX Item "ev_tstamp repeat [read-write]" |
1169 | .IX Item "ev_tstamp repeat [read-write]" |
1070 | The current \f(CW\*(C`repeat\*(C'\fR value. Will be used each time the watcher times out |
1170 | The current \f(CW\*(C`repeat\*(C'\fR value. Will be used each time the watcher times out |
1071 | or \f(CW\*(C`ev_timer_again\*(C'\fR is called and determines the next timeout (if any), |
1171 | or \f(CW\*(C`ev_timer_again\*(C'\fR is called and determines the next timeout (if any), |
1072 | which is also when any modifications are taken into account. |
1172 | which is also when any modifications are taken into account. |
… | |
… | |
1345 | not exist\*(R" is a status change like any other. The condition \*(L"path does |
1445 | not exist\*(R" is a status change like any other. The condition \*(L"path does |
1346 | not exist\*(R" is signified by the \f(CW\*(C`st_nlink\*(C'\fR field being zero (which is |
1446 | not exist\*(R" is signified by the \f(CW\*(C`st_nlink\*(C'\fR field being zero (which is |
1347 | otherwise always forced to be at least one) and all the other fields of |
1447 | otherwise always forced to be at least one) and all the other fields of |
1348 | the stat buffer having unspecified contents. |
1448 | the stat buffer having unspecified contents. |
1349 | .PP |
1449 | .PP |
|
|
1450 | The path \fIshould\fR be absolute and \fImust not\fR end in a slash. If it is |
|
|
1451 | relative and your working directory changes, the behaviour is undefined. |
|
|
1452 | .PP |
1350 | Since there is no standard to do this, the portable implementation simply |
1453 | Since there is no standard to do this, the portable implementation simply |
1351 | calls \f(CW\*(C`stat (2)\*(C'\fR regulalry on the path to see if it changed somehow. You |
1454 | calls \f(CW\*(C`stat (2)\*(C'\fR regularly on the path to see if it changed somehow. You |
1352 | can specify a recommended polling interval for this case. If you specify |
1455 | can specify a recommended polling interval for this case. If you specify |
1353 | a polling interval of \f(CW0\fR (highly recommended!) then a \fIsuitable, |
1456 | a polling interval of \f(CW0\fR (highly recommended!) then a \fIsuitable, |
1354 | unspecified default\fR value will be used (which you can expect to be around |
1457 | unspecified default\fR value will be used (which you can expect to be around |
1355 | five seconds, although this might change dynamically). Libev will also |
1458 | five seconds, although this might change dynamically). Libev will also |
1356 | impose a minimum interval which is currently around \f(CW0.1\fR, but thats |
1459 | impose a minimum interval which is currently around \f(CW0.1\fR, but thats |
… | |
… | |
1358 | .PP |
1461 | .PP |
1359 | This watcher type is not meant for massive numbers of stat watchers, |
1462 | This watcher type is not meant for massive numbers of stat watchers, |
1360 | as even with OS-supported change notifications, this can be |
1463 | as even with OS-supported change notifications, this can be |
1361 | resource\-intensive. |
1464 | resource\-intensive. |
1362 | .PP |
1465 | .PP |
1363 | At the time of this writing, no specific \s-1OS\s0 backends are implemented, but |
1466 | At the time of this writing, only the Linux inotify interface is |
1364 | if demand increases, at least a kqueue and inotify backend will be added. |
1467 | implemented (implementing kqueue support is left as an exercise for the |
|
|
1468 | 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 |
|
|
1470 | 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 |
|
|
1472 | polling. |
1365 | .IP "ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)" 4 |
1473 | .IP "ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)" 4 |
1366 | .IX Item "ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)" |
1474 | .IX Item "ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)" |
1367 | .PD 0 |
1475 | .PD 0 |
1368 | .IP "ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)" 4 |
1476 | .IP "ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)" 4 |
1369 | .IX Item "ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)" |
1477 | .IX Item "ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)" |
… | |
… | |
1430 | \& ev_stat_start (loop, &passwd); |
1538 | \& ev_stat_start (loop, &passwd); |
1431 | .Ve |
1539 | .Ve |
1432 | .ie n .Sh """ev_idle"" \- when you've got nothing better to do..." |
1540 | .ie n .Sh """ev_idle"" \- when you've got nothing better to do..." |
1433 | .el .Sh "\f(CWev_idle\fP \- when you've got nothing better to do..." |
1541 | .el .Sh "\f(CWev_idle\fP \- when you've got nothing better to do..." |
1434 | .IX Subsection "ev_idle - when you've got nothing better to do..." |
1542 | .IX Subsection "ev_idle - when you've got nothing better to do..." |
1435 | Idle watchers trigger events when there are no other events are pending |
1543 | Idle watchers trigger events when no other events of the same or higher |
1436 | (prepare, check and other idle watchers do not count). That is, as long |
1544 | priority are pending (prepare, check and other idle watchers do not |
1437 | as your process is busy handling sockets or timeouts (or even signals, |
1545 | count). |
1438 | imagine) it will not be triggered. But when your process is idle all idle |
1546 | .PP |
1439 | watchers are being called again and again, once per event loop iteration \- |
1547 | That is, as long as your process is busy handling sockets or timeouts |
|
|
1548 | (or even signals, imagine) of the same or higher priority it will not be |
|
|
1549 | triggered. But when your process is idle (or only lower-priority watchers |
|
|
1550 | are pending), the idle watchers are being called once per event loop |
1440 | until stopped, that is, or your process receives more events and becomes |
1551 | iteration \- until stopped, that is, or your process receives more events |
1441 | busy. |
1552 | and becomes busy again with higher priority stuff. |
1442 | .PP |
1553 | .PP |
1443 | The most noteworthy effect is that as long as any idle watchers are |
1554 | The most noteworthy effect is that as long as any idle watchers are |
1444 | active, the process will not block when waiting for new events. |
1555 | active, the process will not block when waiting for new events. |
1445 | .PP |
1556 | .PP |
1446 | Apart from keeping your process non-blocking (which is a useful |
1557 | Apart from keeping your process non-blocking (which is a useful |
… | |
… | |
1541 | \& if (revents & EV_READ ) fd->revents |= fd->events & POLLIN; |
1652 | \& if (revents & EV_READ ) fd->revents |= fd->events & POLLIN; |
1542 | \& if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT; |
1653 | \& if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT; |
1543 | \& } |
1654 | \& } |
1544 | .Ve |
1655 | .Ve |
1545 | .PP |
1656 | .PP |
1546 | .Vb 7 |
1657 | .Vb 8 |
1547 | \& // create io watchers for each fd and a timer before blocking |
1658 | \& // create io watchers for each fd and a timer before blocking |
1548 | \& static void |
1659 | \& static void |
1549 | \& adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) |
1660 | \& adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) |
1550 | \& { |
1661 | \& { |
1551 | \& int timeout = 3600000;truct pollfd fds [nfd]; |
1662 | \& int timeout = 3600000; |
|
|
1663 | \& struct pollfd fds [nfd]; |
1552 | \& // actual code will need to loop here and realloc etc. |
1664 | \& // actual code will need to loop here and realloc etc. |
1553 | \& adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ())); |
1665 | \& adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ())); |
1554 | .Ve |
1666 | .Ve |
1555 | .PP |
1667 | .PP |
1556 | .Vb 3 |
1668 | .Vb 3 |
… | |
… | |
1883 | \& } |
1995 | \& } |
1884 | .Ve |
1996 | .Ve |
1885 | .SH "MACRO MAGIC" |
1997 | .SH "MACRO MAGIC" |
1886 | .IX Header "MACRO MAGIC" |
1998 | .IX Header "MACRO MAGIC" |
1887 | Libev can be compiled with a variety of options, the most fundemantal is |
1999 | Libev can be compiled with a variety of options, the most fundemantal is |
1888 | \&\f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. This option determines wether (most) functions and |
2000 | \&\f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. This option determines whether (most) functions and |
1889 | callbacks have an initial \f(CW\*(C`struct ev_loop *\*(C'\fR argument. |
2001 | callbacks have an initial \f(CW\*(C`struct ev_loop *\*(C'\fR argument. |
1890 | .PP |
2002 | .PP |
1891 | To make it easier to write programs that cope with either variant, the |
2003 | To make it easier to write programs that cope with either variant, the |
1892 | following macros are defined: |
2004 | following macros are defined: |
1893 | .ie n .IP """EV_A""\fR, \f(CW""EV_A_""" 4 |
2005 | .ie n .IP """EV_A""\fR, \f(CW""EV_A_""" 4 |
… | |
… | |
1928 | .el .IP "\f(CWEV_DEFAULT\fR, \f(CWEV_DEFAULT_\fR" 4 |
2040 | .el .IP "\f(CWEV_DEFAULT\fR, \f(CWEV_DEFAULT_\fR" 4 |
1929 | .IX Item "EV_DEFAULT, EV_DEFAULT_" |
2041 | .IX Item "EV_DEFAULT, EV_DEFAULT_" |
1930 | Similar to the other two macros, this gives you the value of the default |
2042 | Similar to the other two macros, this gives you the value of the default |
1931 | loop, if multiple loops are supported (\*(L"ev loop default\*(R"). |
2043 | loop, if multiple loops are supported (\*(L"ev loop default\*(R"). |
1932 | .PP |
2044 | .PP |
1933 | Example: Declare and initialise a check watcher, working regardless of |
2045 | Example: Declare and initialise a check watcher, utilising the above |
1934 | wether multiple loops are supported or not. |
2046 | macros so it will work regardless of whether multiple loops are supported |
|
|
2047 | or not. |
1935 | .PP |
2048 | .PP |
1936 | .Vb 5 |
2049 | .Vb 5 |
1937 | \& static void |
2050 | \& static void |
1938 | \& check_cb (EV_P_ ev_timer *w, int revents) |
2051 | \& check_cb (EV_P_ ev_timer *w, int revents) |
1939 | \& { |
2052 | \& { |
… | |
… | |
2002 | .Vb 1 |
2115 | .Vb 1 |
2003 | \& ev_win32.c required on win32 platforms only |
2116 | \& ev_win32.c required on win32 platforms only |
2004 | .Ve |
2117 | .Ve |
2005 | .PP |
2118 | .PP |
2006 | .Vb 5 |
2119 | .Vb 5 |
2007 | \& ev_select.c only when select backend is enabled (which is by default) |
2120 | \& ev_select.c only when select backend is enabled (which is enabled by default) |
2008 | \& ev_poll.c only when poll backend is enabled (disabled by default) |
2121 | \& ev_poll.c only when poll backend is enabled (disabled by default) |
2009 | \& ev_epoll.c only when the epoll backend is enabled (disabled by default) |
2122 | \& ev_epoll.c only when the epoll backend is enabled (disabled by default) |
2010 | \& ev_kqueue.c only when the kqueue backend is enabled (disabled by default) |
2123 | \& ev_kqueue.c only when the kqueue backend is enabled (disabled by default) |
2011 | \& ev_port.c only when the solaris port backend is enabled (disabled by default) |
2124 | \& ev_port.c only when the solaris port backend is enabled (disabled by default) |
2012 | .Ve |
2125 | .Ve |
… | |
… | |
2133 | otherwise another method will be used as fallback. This is the preferred |
2246 | otherwise another method will be used as fallback. This is the preferred |
2134 | backend for Solaris 10 systems. |
2247 | backend for Solaris 10 systems. |
2135 | .IP "\s-1EV_USE_DEVPOLL\s0" 4 |
2248 | .IP "\s-1EV_USE_DEVPOLL\s0" 4 |
2136 | .IX Item "EV_USE_DEVPOLL" |
2249 | .IX Item "EV_USE_DEVPOLL" |
2137 | reserved for future expansion, works like the \s-1USE\s0 symbols above. |
2250 | reserved for future expansion, works like the \s-1USE\s0 symbols above. |
|
|
2251 | .IP "\s-1EV_USE_INOTIFY\s0" 4 |
|
|
2252 | .IX Item "EV_USE_INOTIFY" |
|
|
2253 | If defined to be \f(CW1\fR, libev will compile in support for the Linux inotify |
|
|
2254 | interface to speed up \f(CW\*(C`ev_stat\*(C'\fR watchers. Its actual availability will |
|
|
2255 | be detected at runtime. |
2138 | .IP "\s-1EV_H\s0" 4 |
2256 | .IP "\s-1EV_H\s0" 4 |
2139 | .IX Item "EV_H" |
2257 | .IX Item "EV_H" |
2140 | The name of the \fIev.h\fR header file used to include it. The default if |
2258 | The name of the \fIev.h\fR header file used to include it. The default if |
2141 | undefined is \f(CW\*(C`<ev.h>\*(C'\fR in \fIevent.h\fR and \f(CW"ev.h"\fR in \fIev.c\fR. This |
2259 | undefined is \f(CW\*(C`<ev.h>\*(C'\fR in \fIevent.h\fR and \f(CW"ev.h"\fR in \fIev.c\fR. This |
2142 | can be used to virtually rename the \fIev.h\fR header file in case of conflicts. |
2260 | can be used to virtually rename the \fIev.h\fR header file in case of conflicts. |
… | |
… | |
2160 | If undefined or defined to \f(CW1\fR, then all event-loop-specific functions |
2278 | If undefined or defined to \f(CW1\fR, then all event-loop-specific functions |
2161 | will have the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument, and you can create |
2279 | will have the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument, and you can create |
2162 | additional independent event loops. Otherwise there will be no support |
2280 | additional independent event loops. Otherwise there will be no support |
2163 | for multiple event loops and there is no first event loop pointer |
2281 | for multiple event loops and there is no first event loop pointer |
2164 | argument. Instead, all functions act on the single default loop. |
2282 | argument. Instead, all functions act on the single default loop. |
|
|
2283 | .IP "\s-1EV_MINPRI\s0" 4 |
|
|
2284 | .IX Item "EV_MINPRI" |
|
|
2285 | .PD 0 |
|
|
2286 | .IP "\s-1EV_MAXPRI\s0" 4 |
|
|
2287 | .IX Item "EV_MAXPRI" |
|
|
2288 | .PD |
|
|
2289 | The range of allowed priorities. \f(CW\*(C`EV_MINPRI\*(C'\fR must be smaller or equal to |
|
|
2290 | \&\f(CW\*(C`EV_MAXPRI\*(C'\fR, but otherwise there are no non-obvious limitations. You can |
|
|
2291 | provide for more priorities by overriding those symbols (usually defined |
|
|
2292 | to be \f(CW\*(C`\-2\*(C'\fR and \f(CW2\fR, respectively). |
|
|
2293 | .Sp |
|
|
2294 | When doing priority-based operations, libev usually has to linearly search |
|
|
2295 | all the priorities, so having many of them (hundreds) uses a lot of space |
|
|
2296 | and time, so using the defaults of five priorities (\-2 .. +2) is usually |
|
|
2297 | fine. |
|
|
2298 | .Sp |
|
|
2299 | If your embedding app does not need any priorities, defining these both to |
|
|
2300 | \&\f(CW0\fR will save some memory and cpu. |
2165 | .IP "\s-1EV_PERIODIC_ENABLE\s0" 4 |
2301 | .IP "\s-1EV_PERIODIC_ENABLE\s0" 4 |
2166 | .IX Item "EV_PERIODIC_ENABLE" |
2302 | .IX Item "EV_PERIODIC_ENABLE" |
2167 | If undefined or defined to be \f(CW1\fR, then periodic timers are supported. If |
2303 | If undefined or defined to be \f(CW1\fR, then periodic timers are supported. If |
|
|
2304 | defined to be \f(CW0\fR, then they are not. Disabling them saves a few kB of |
|
|
2305 | code. |
|
|
2306 | .IP "\s-1EV_IDLE_ENABLE\s0" 4 |
|
|
2307 | .IX Item "EV_IDLE_ENABLE" |
|
|
2308 | If undefined or defined to be \f(CW1\fR, then idle watchers are supported. If |
2168 | defined to be \f(CW0\fR, then they are not. Disabling them saves a few kB of |
2309 | defined to be \f(CW0\fR, then they are not. Disabling them saves a few kB of |
2169 | code. |
2310 | code. |
2170 | .IP "\s-1EV_EMBED_ENABLE\s0" 4 |
2311 | .IP "\s-1EV_EMBED_ENABLE\s0" 4 |
2171 | .IX Item "EV_EMBED_ENABLE" |
2312 | .IX Item "EV_EMBED_ENABLE" |
2172 | If undefined or defined to be \f(CW1\fR, then embed watchers are supported. If |
2313 | If undefined or defined to be \f(CW1\fR, then embed watchers are supported. If |
… | |
… | |
2187 | .IP "\s-1EV_PID_HASHSIZE\s0" 4 |
2328 | .IP "\s-1EV_PID_HASHSIZE\s0" 4 |
2188 | .IX Item "EV_PID_HASHSIZE" |
2329 | .IX Item "EV_PID_HASHSIZE" |
2189 | \&\f(CW\*(C`ev_child\*(C'\fR watchers use a small hash table to distribute workload by |
2330 | \&\f(CW\*(C`ev_child\*(C'\fR watchers use a small hash table to distribute workload by |
2190 | pid. The default size is \f(CW16\fR (or \f(CW1\fR with \f(CW\*(C`EV_MINIMAL\*(C'\fR), usually more |
2331 | pid. The default size is \f(CW16\fR (or \f(CW1\fR with \f(CW\*(C`EV_MINIMAL\*(C'\fR), usually more |
2191 | than enough. If you need to manage thousands of children you might want to |
2332 | than enough. If you need to manage thousands of children you might want to |
2192 | increase this value. |
2333 | increase this value (\fImust\fR be a power of two). |
|
|
2334 | .IP "\s-1EV_INOTIFY_HASHSIZE\s0" 4 |
|
|
2335 | .IX Item "EV_INOTIFY_HASHSIZE" |
|
|
2336 | \&\f(CW\*(C`ev_staz\*(C'\fR watchers use a small hash table to distribute workload by |
|
|
2337 | inotify watch id. The default size is \f(CW16\fR (or \f(CW1\fR with \f(CW\*(C`EV_MINIMAL\*(C'\fR), |
|
|
2338 | usually more than enough. If you need to manage thousands of \f(CW\*(C`ev_stat\*(C'\fR |
|
|
2339 | watchers you might want to increase this value (\fImust\fR be a power of |
|
|
2340 | two). |
2193 | .IP "\s-1EV_COMMON\s0" 4 |
2341 | .IP "\s-1EV_COMMON\s0" 4 |
2194 | .IX Item "EV_COMMON" |
2342 | .IX Item "EV_COMMON" |
2195 | By default, all watchers have a \f(CW\*(C`void *data\*(C'\fR member. By redefining |
2343 | By default, all watchers have a \f(CW\*(C`void *data\*(C'\fR member. By redefining |
2196 | this macro to a something else you can include more and other types of |
2344 | this macro to a something else you can include more and other types of |
2197 | members. You have to define it each time you include one of the files, |
2345 | members. You have to define it each time you include one of the files, |
… | |
… | |
2227 | interface) and \fI\s-1EV\s0.xs\fR (implementation) files. Only the \fI\s-1EV\s0.xs\fR file |
2375 | interface) and \fI\s-1EV\s0.xs\fR (implementation) files. Only the \fI\s-1EV\s0.xs\fR file |
2228 | will be compiled. It is pretty complex because it provides its own header |
2376 | will be compiled. It is pretty complex because it provides its own header |
2229 | file. |
2377 | file. |
2230 | .Sp |
2378 | .Sp |
2231 | The usage in rxvt-unicode is simpler. It has a \fIev_cpp.h\fR header file |
2379 | The usage in rxvt-unicode is simpler. It has a \fIev_cpp.h\fR header file |
2232 | that everybody includes and which overrides some autoconf choices: |
2380 | that everybody includes and which overrides some configure choices: |
2233 | .Sp |
2381 | .Sp |
2234 | .Vb 4 |
2382 | .Vb 9 |
|
|
2383 | \& #define EV_MINIMAL 1 |
2235 | \& #define EV_USE_POLL 0 |
2384 | \& #define EV_USE_POLL 0 |
2236 | \& #define EV_MULTIPLICITY 0 |
2385 | \& #define EV_MULTIPLICITY 0 |
2237 | \& #define EV_PERIODICS 0 |
2386 | \& #define EV_PERIODIC_ENABLE 0 |
|
|
2387 | \& #define EV_STAT_ENABLE 0 |
|
|
2388 | \& #define EV_FORK_ENABLE 0 |
2238 | \& #define EV_CONFIG_H <config.h> |
2389 | \& #define EV_CONFIG_H <config.h> |
|
|
2390 | \& #define EV_MINPRI 0 |
|
|
2391 | \& #define EV_MAXPRI 0 |
2239 | .Ve |
2392 | .Ve |
2240 | .Sp |
2393 | .Sp |
2241 | .Vb 1 |
2394 | .Vb 1 |
2242 | \& #include "ev++.h" |
2395 | \& #include "ev++.h" |
2243 | .Ve |
2396 | .Ve |
… | |
… | |
2254 | libev will be explained. For complexity discussions about backends see the |
2407 | libev will be explained. For complexity discussions about backends see the |
2255 | documentation for \f(CW\*(C`ev_default_init\*(C'\fR. |
2408 | documentation for \f(CW\*(C`ev_default_init\*(C'\fR. |
2256 | .RS 4 |
2409 | .RS 4 |
2257 | .IP "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" 4 |
2410 | .IP "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" 4 |
2258 | .IX Item "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" |
2411 | .IX Item "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" |
2259 | .PD 0 |
2412 | 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 |
|
|
2414 | have to skip those 100 watchers. |
2260 | .IP "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)" 4 |
2415 | .IP "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)" 4 |
2261 | .IX Item "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)" |
2416 | .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 |
|
|
2418 | as only the relative motion in the event queue has to be paid for. |
2262 | .IP "Starting io/check/prepare/idle/signal/child watchers: O(1)" 4 |
2419 | .IP "Starting io/check/prepare/idle/signal/child watchers: O(1)" 4 |
2263 | .IX Item "Starting io/check/prepare/idle/signal/child watchers: O(1)" |
2420 | .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 |
|
|
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). |
2264 | .IP "Stopping check/prepare/idle watchers: O(1)" 4 |
2425 | .IP "Stopping check/prepare/idle watchers: O(1)" 4 |
2265 | .IX Item "Stopping check/prepare/idle watchers: O(1)" |
2426 | .IX Item "Stopping check/prepare/idle watchers: O(1)" |
|
|
2427 | .PD 0 |
2266 | .IP "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % 16))" 4 |
2428 | .IP "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % \s-1EV_PID_HASHSIZE\s0))" 4 |
2267 | .IX Item "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % 16))" |
2429 | .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 |
|
|
2432 | correct watcher to remove. The lists are usually short (you don't usually |
|
|
2433 | have many watchers waiting for the same fd or signal). |
2268 | .IP "Finding the next timer per loop iteration: O(1)" 4 |
2434 | .IP "Finding the next timer per loop iteration: O(1)" 4 |
2269 | .IX Item "Finding the next timer per loop iteration: O(1)" |
2435 | .IX Item "Finding the next timer per loop iteration: O(1)" |
|
|
2436 | .PD 0 |
2270 | .IP "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)" 4 |
2437 | .IP "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)" 4 |
2271 | .IX Item "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)" |
2438 | .IX Item "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)" |
|
|
2439 | .PD |
|
|
2440 | A change means an I/O watcher gets started or stopped, which requires |
|
|
2441 | libev to recalculate its status (and possibly tell the kernel). |
2272 | .IP "Activating one watcher: O(1)" 4 |
2442 | .IP "Activating one watcher: O(1)" 4 |
2273 | .IX Item "Activating one watcher: O(1)" |
2443 | .IX Item "Activating one watcher: O(1)" |
|
|
2444 | .PD 0 |
|
|
2445 | .IP "Priority handling: O(number_of_priorities)" 4 |
|
|
2446 | .IX Item "Priority handling: O(number_of_priorities)" |
|
|
2447 | .PD |
|
|
2448 | Priorities are implemented by allocating some space for each |
|
|
2449 | priority. When doing priority-based operations, libev usually has to |
|
|
2450 | linearly search all the priorities. |
2274 | .RE |
2451 | .RE |
2275 | .RS 4 |
2452 | .RS 4 |
2276 | .PD |
|
|
2277 | .SH "AUTHOR" |
2453 | .SH "AUTHOR" |
2278 | .IX Header "AUTHOR" |
2454 | .IX Header "AUTHOR" |
2279 | Marc Lehmann <libev@schmorp.de>. |
2455 | Marc Lehmann <libev@schmorp.de>. |