… | |
… | |
63 | details of the event, and then hand it over to libev by I<starting> the |
63 | details of the event, and then hand it over to libev by I<starting> the |
64 | watcher. |
64 | watcher. |
65 | |
65 | |
66 | =head1 FEATURES |
66 | =head1 FEATURES |
67 | |
67 | |
68 | Libev supports C<select>, C<poll>, the linux-specific C<epoll>, the |
68 | Libev supports C<select>, C<poll>, the Linux-specific C<epoll>, the |
69 | bsd-specific C<kqueue> and the solaris-specific event port mechanisms |
69 | BSD-specific C<kqueue> and the Solaris-specific event port mechanisms |
70 | for file descriptor events (C<ev_io>), relative timers (C<ev_timer>), |
70 | for file descriptor events (C<ev_io>), the Linux C<inotify> interface |
|
|
71 | (for C<ev_stat>), relative timers (C<ev_timer>), absolute timers |
71 | absolute timers with customised rescheduling (C<ev_periodic>), synchronous |
72 | with customised rescheduling (C<ev_periodic>), synchronous signals |
72 | signals (C<ev_signal>), process status change events (C<ev_child>), and |
73 | (C<ev_signal>), process status change events (C<ev_child>), and event |
73 | event watchers dealing with the event loop mechanism itself (C<ev_idle>, |
74 | watchers dealing with the event loop mechanism itself (C<ev_idle>, |
74 | C<ev_embed>, C<ev_prepare> and C<ev_check> watchers) as well as |
75 | C<ev_embed>, C<ev_prepare> and C<ev_check> watchers) as well as |
75 | file watchers (C<ev_stat>) and even limited support for fork events |
76 | file watchers (C<ev_stat>) and even limited support for fork events |
76 | (C<ev_fork>). |
77 | (C<ev_fork>). |
77 | |
78 | |
78 | It also is quite fast (see this |
79 | It also is quite fast (see this |
… | |
… | |
162 | C<ev_embeddable_backends () & ev_supported_backends ()>, likewise for |
163 | C<ev_embeddable_backends () & ev_supported_backends ()>, likewise for |
163 | recommended ones. |
164 | recommended ones. |
164 | |
165 | |
165 | See the description of C<ev_embed> watchers for more info. |
166 | See the description of C<ev_embed> watchers for more info. |
166 | |
167 | |
167 | =item ev_set_allocator (void *(*cb)(void *ptr, size_t size)) |
168 | =item ev_set_allocator (void *(*cb)(void *ptr, long size)) |
168 | |
169 | |
169 | Sets the allocation function to use (the prototype and semantics are |
170 | Sets the allocation function to use (the prototype is similar - the |
170 | identical to the realloc C function). It is used to allocate and free |
171 | semantics is identical - to the realloc C function). It is used to |
171 | memory (no surprises here). If it returns zero when memory needs to be |
172 | allocate and free memory (no surprises here). If it returns zero when |
172 | allocated, the library might abort or take some potentially destructive |
173 | memory needs to be allocated, the library might abort or take some |
173 | action. The default is your system realloc function. |
174 | potentially destructive action. The default is your system realloc |
|
|
175 | function. |
174 | |
176 | |
175 | You could override this function in high-availability programs to, say, |
177 | You could override this function in high-availability programs to, say, |
176 | free some memory if it cannot allocate memory, to use a special allocator, |
178 | free some memory if it cannot allocate memory, to use a special allocator, |
177 | or even to sleep a while and retry until some memory is available. |
179 | or even to sleep a while and retry until some memory is available. |
178 | |
180 | |
… | |
… | |
263 | or setgid) then libev will I<not> look at the environment variable |
265 | or setgid) then libev will I<not> look at the environment variable |
264 | C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will |
266 | C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will |
265 | override the flags completely if it is found in the environment. This is |
267 | override the flags completely if it is found in the environment. This is |
266 | useful to try out specific backends to test their performance, or to work |
268 | useful to try out specific backends to test their performance, or to work |
267 | around bugs. |
269 | around bugs. |
|
|
270 | |
|
|
271 | =item C<EVFLAG_FORKCHECK> |
|
|
272 | |
|
|
273 | Instead of calling C<ev_default_fork> or C<ev_loop_fork> manually after |
|
|
274 | a fork, you can also make libev check for a fork in each iteration by |
|
|
275 | enabling this flag. |
|
|
276 | |
|
|
277 | This works by calling C<getpid ()> on every iteration of the loop, |
|
|
278 | and thus this might slow down your event loop if you do a lot of loop |
|
|
279 | iterations and little real work, but is usually not noticable (on my |
|
|
280 | Linux system for example, C<getpid> is actually a simple 5-insn sequence |
|
|
281 | without a syscall and thus I<very> fast, but my Linux system also has |
|
|
282 | C<pthread_atfork> which is even faster). |
|
|
283 | |
|
|
284 | The big advantage of this flag is that you can forget about fork (and |
|
|
285 | forget about forgetting to tell libev about forking) when you use this |
|
|
286 | flag. |
|
|
287 | |
|
|
288 | This flag setting cannot be overriden or specified in the C<LIBEV_FLAGS> |
|
|
289 | environment variable. |
268 | |
290 | |
269 | =item C<EVBACKEND_SELECT> (value 1, portable select backend) |
291 | =item C<EVBACKEND_SELECT> (value 1, portable select backend) |
270 | |
292 | |
271 | This is your standard select(2) backend. Not I<completely> standard, as |
293 | This is your standard select(2) backend. Not I<completely> standard, as |
272 | libev tries to roll its own fd_set with no limits on the number of fds, |
294 | libev tries to roll its own fd_set with no limits on the number of fds, |
… | |
… | |
914 | =item ev_timer_again (loop) |
936 | =item ev_timer_again (loop) |
915 | |
937 | |
916 | This will act as if the timer timed out and restart it again if it is |
938 | This will act as if the timer timed out and restart it again if it is |
917 | repeating. The exact semantics are: |
939 | repeating. The exact semantics are: |
918 | |
940 | |
|
|
941 | If the timer is pending, its pending status is cleared. |
|
|
942 | |
919 | If the timer is started but nonrepeating, stop it. |
943 | If the timer is started but nonrepeating, stop it (as if it timed out). |
920 | |
944 | |
921 | If the timer is repeating, either start it if necessary (with the repeat |
945 | If the timer is repeating, either start it if necessary (with the |
922 | value), or reset the running timer to the repeat value. |
946 | C<repeat> value), or reset the running timer to the C<repeat> value. |
923 | |
947 | |
924 | This sounds a bit complicated, but here is a useful and typical |
948 | This sounds a bit complicated, but here is a useful and typical |
925 | example: Imagine you have a tcp connection and you want a so-called |
949 | example: Imagine you have a tcp connection and you want a so-called idle |
926 | idle timeout, that is, you want to be called when there have been, |
950 | timeout, that is, you want to be called when there have been, say, 60 |
927 | say, 60 seconds of inactivity on the socket. The easiest way to do |
951 | seconds of inactivity on the socket. The easiest way to do this is to |
928 | this is to configure an C<ev_timer> with C<after>=C<repeat>=C<60> and calling |
952 | configure an C<ev_timer> with a C<repeat> value of C<60> and then call |
929 | C<ev_timer_again> each time you successfully read or write some data. If |
953 | C<ev_timer_again> each time you successfully read or write some data. If |
930 | you go into an idle state where you do not expect data to travel on the |
954 | you go into an idle state where you do not expect data to travel on the |
931 | socket, you can stop the timer, and again will automatically restart it if |
955 | socket, you can C<ev_timer_stop> the timer, and C<ev_timer_again> will |
932 | need be. |
956 | automatically restart it if need be. |
933 | |
957 | |
934 | You can also ignore the C<after> value and C<ev_timer_start> altogether |
958 | That means you can ignore the C<after> value and C<ev_timer_start> |
935 | and only ever use the C<repeat> value: |
959 | altogether and only ever use the C<repeat> value and C<ev_timer_again>: |
936 | |
960 | |
937 | ev_timer_init (timer, callback, 0., 5.); |
961 | ev_timer_init (timer, callback, 0., 5.); |
938 | ev_timer_again (loop, timer); |
962 | ev_timer_again (loop, timer); |
939 | ... |
963 | ... |
940 | timer->again = 17.; |
964 | timer->again = 17.; |
941 | ev_timer_again (loop, timer); |
965 | ev_timer_again (loop, timer); |
942 | ... |
966 | ... |
943 | timer->again = 10.; |
967 | timer->again = 10.; |
944 | ev_timer_again (loop, timer); |
968 | ev_timer_again (loop, timer); |
945 | |
969 | |
946 | This is more efficient then stopping/starting the timer eahc time you want |
970 | This is more slightly efficient then stopping/starting the timer each time |
947 | to modify its timeout value. |
971 | you want to modify its timeout value. |
948 | |
972 | |
949 | =item ev_tstamp repeat [read-write] |
973 | =item ev_tstamp repeat [read-write] |
950 | |
974 | |
951 | The current C<repeat> value. Will be used each time the watcher times out |
975 | The current C<repeat> value. Will be used each time the watcher times out |
952 | or C<ev_timer_again> is called and determines the next timeout (if any), |
976 | or C<ev_timer_again> is called and determines the next timeout (if any), |
… | |
… | |
1221 | not exist" is a status change like any other. The condition "path does |
1245 | not exist" is a status change like any other. The condition "path does |
1222 | not exist" is signified by the C<st_nlink> field being zero (which is |
1246 | not exist" is signified by the C<st_nlink> field being zero (which is |
1223 | otherwise always forced to be at least one) and all the other fields of |
1247 | otherwise always forced to be at least one) and all the other fields of |
1224 | the stat buffer having unspecified contents. |
1248 | the stat buffer having unspecified contents. |
1225 | |
1249 | |
|
|
1250 | The path I<should> be absolute and I<must not> end in a slash. If it is |
|
|
1251 | relative and your working directory changes, the behaviour is undefined. |
|
|
1252 | |
1226 | Since there is no standard to do this, the portable implementation simply |
1253 | Since there is no standard to do this, the portable implementation simply |
1227 | calls C<stat (2)> regulalry on the path to see if it changed somehow. You |
1254 | calls C<stat (2)> regularly on the path to see if it changed somehow. You |
1228 | can specify a recommended polling interval for this case. If you specify |
1255 | can specify a recommended polling interval for this case. If you specify |
1229 | a polling interval of C<0> (highly recommended!) then a I<suitable, |
1256 | a polling interval of C<0> (highly recommended!) then a I<suitable, |
1230 | unspecified default> value will be used (which you can expect to be around |
1257 | unspecified default> value will be used (which you can expect to be around |
1231 | five seconds, although this might change dynamically). Libev will also |
1258 | five seconds, although this might change dynamically). Libev will also |
1232 | impose a minimum interval which is currently around C<0.1>, but thats |
1259 | impose a minimum interval which is currently around C<0.1>, but thats |
… | |
… | |
1234 | |
1261 | |
1235 | This watcher type is not meant for massive numbers of stat watchers, |
1262 | This watcher type is not meant for massive numbers of stat watchers, |
1236 | as even with OS-supported change notifications, this can be |
1263 | as even with OS-supported change notifications, this can be |
1237 | resource-intensive. |
1264 | resource-intensive. |
1238 | |
1265 | |
1239 | At the time of this writing, no specific OS backends are implemented, but |
1266 | At the time of this writing, only the Linux inotify interface is |
1240 | if demand increases, at least a kqueue and inotify backend will be added. |
1267 | implemented (implementing kqueue support is left as an exercise for the |
|
|
1268 | reader). Inotify will be used to give hints only and should not change the |
|
|
1269 | semantics of C<ev_stat> watchers, which means that libev sometimes needs |
|
|
1270 | to fall back to regular polling again even with inotify, but changes are |
|
|
1271 | usually detected immediately, and if the file exists there will be no |
|
|
1272 | polling. |
1241 | |
1273 | |
1242 | =over 4 |
1274 | =over 4 |
1243 | |
1275 | |
1244 | =item ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval) |
1276 | =item ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval) |
1245 | |
1277 | |
… | |
… | |
1816 | Similar to the other two macros, this gives you the value of the default |
1848 | Similar to the other two macros, this gives you the value of the default |
1817 | loop, if multiple loops are supported ("ev loop default"). |
1849 | loop, if multiple loops are supported ("ev loop default"). |
1818 | |
1850 | |
1819 | =back |
1851 | =back |
1820 | |
1852 | |
1821 | Example: Declare and initialise a check watcher, working regardless of |
1853 | Example: Declare and initialise a check watcher, utilising the above |
1822 | wether multiple loops are supported or not. |
1854 | macros so it will work regardless of wether multiple loops are supported |
|
|
1855 | or not. |
1823 | |
1856 | |
1824 | static void |
1857 | static void |
1825 | check_cb (EV_P_ ev_timer *w, int revents) |
1858 | check_cb (EV_P_ ev_timer *w, int revents) |
1826 | { |
1859 | { |
1827 | ev_check_stop (EV_A_ w); |
1860 | ev_check_stop (EV_A_ w); |
… | |
… | |
1829 | |
1862 | |
1830 | ev_check check; |
1863 | ev_check check; |
1831 | ev_check_init (&check, check_cb); |
1864 | ev_check_init (&check, check_cb); |
1832 | ev_check_start (EV_DEFAULT_ &check); |
1865 | ev_check_start (EV_DEFAULT_ &check); |
1833 | ev_loop (EV_DEFAULT_ 0); |
1866 | ev_loop (EV_DEFAULT_ 0); |
1834 | |
|
|
1835 | |
1867 | |
1836 | =head1 EMBEDDING |
1868 | =head1 EMBEDDING |
1837 | |
1869 | |
1838 | Libev can (and often is) directly embedded into host |
1870 | Libev can (and often is) directly embedded into host |
1839 | applications. Examples of applications that embed it include the Deliantra |
1871 | applications. Examples of applications that embed it include the Deliantra |
… | |
… | |
1879 | ev_vars.h |
1911 | ev_vars.h |
1880 | ev_wrap.h |
1912 | ev_wrap.h |
1881 | |
1913 | |
1882 | ev_win32.c required on win32 platforms only |
1914 | ev_win32.c required on win32 platforms only |
1883 | |
1915 | |
1884 | ev_select.c only when select backend is enabled (which is by default) |
1916 | ev_select.c only when select backend is enabled (which is enabled by default) |
1885 | ev_poll.c only when poll backend is enabled (disabled by default) |
1917 | ev_poll.c only when poll backend is enabled (disabled by default) |
1886 | ev_epoll.c only when the epoll backend is enabled (disabled by default) |
1918 | ev_epoll.c only when the epoll backend is enabled (disabled by default) |
1887 | ev_kqueue.c only when the kqueue backend is enabled (disabled by default) |
1919 | ev_kqueue.c only when the kqueue backend is enabled (disabled by default) |
1888 | ev_port.c only when the solaris port backend is enabled (disabled by default) |
1920 | ev_port.c only when the solaris port backend is enabled (disabled by default) |
1889 | |
1921 | |
… | |
… | |
2014 | |
2046 | |
2015 | =item EV_USE_DEVPOLL |
2047 | =item EV_USE_DEVPOLL |
2016 | |
2048 | |
2017 | reserved for future expansion, works like the USE symbols above. |
2049 | reserved for future expansion, works like the USE symbols above. |
2018 | |
2050 | |
|
|
2051 | =item EV_USE_INOTIFY |
|
|
2052 | |
|
|
2053 | If defined to be C<1>, libev will compile in support for the Linux inotify |
|
|
2054 | interface to speed up C<ev_stat> watchers. Its actual availability will |
|
|
2055 | be detected at runtime. |
|
|
2056 | |
2019 | =item EV_H |
2057 | =item EV_H |
2020 | |
2058 | |
2021 | The name of the F<ev.h> header file used to include it. The default if |
2059 | The name of the F<ev.h> header file used to include it. The default if |
2022 | undefined is C<< <ev.h> >> in F<event.h> and C<"ev.h"> in F<ev.c>. This |
2060 | undefined is C<< <ev.h> >> in F<event.h> and C<"ev.h"> in F<ev.c>. This |
2023 | can be used to virtually rename the F<ev.h> header file in case of conflicts. |
2061 | can be used to virtually rename the F<ev.h> header file in case of conflicts. |
… | |
… | |
2078 | =item EV_PID_HASHSIZE |
2116 | =item EV_PID_HASHSIZE |
2079 | |
2117 | |
2080 | C<ev_child> watchers use a small hash table to distribute workload by |
2118 | C<ev_child> watchers use a small hash table to distribute workload by |
2081 | pid. The default size is C<16> (or C<1> with C<EV_MINIMAL>), usually more |
2119 | pid. The default size is C<16> (or C<1> with C<EV_MINIMAL>), usually more |
2082 | than enough. If you need to manage thousands of children you might want to |
2120 | than enough. If you need to manage thousands of children you might want to |
2083 | increase this value. |
2121 | increase this value (I<must> be a power of two). |
|
|
2122 | |
|
|
2123 | =item EV_INOTIFY_HASHSIZE |
|
|
2124 | |
|
|
2125 | C<ev_staz> watchers use a small hash table to distribute workload by |
|
|
2126 | inotify watch id. The default size is C<16> (or C<1> with C<EV_MINIMAL>), |
|
|
2127 | usually more than enough. If you need to manage thousands of C<ev_stat> |
|
|
2128 | watchers you might want to increase this value (I<must> be a power of |
|
|
2129 | two). |
2084 | |
2130 | |
2085 | =item EV_COMMON |
2131 | =item EV_COMMON |
2086 | |
2132 | |
2087 | By default, all watchers have a C<void *data> member. By redefining |
2133 | By default, all watchers have a C<void *data> member. By redefining |
2088 | this macro to a something else you can include more and other types of |
2134 | this macro to a something else you can include more and other types of |
… | |
… | |
2117 | interface) and F<EV.xs> (implementation) files. Only the F<EV.xs> file |
2163 | interface) and F<EV.xs> (implementation) files. Only the F<EV.xs> file |
2118 | will be compiled. It is pretty complex because it provides its own header |
2164 | will be compiled. It is pretty complex because it provides its own header |
2119 | file. |
2165 | file. |
2120 | |
2166 | |
2121 | The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file |
2167 | The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file |
2122 | that everybody includes and which overrides some autoconf choices: |
2168 | that everybody includes and which overrides some configure choices: |
2123 | |
2169 | |
|
|
2170 | #define EV_MINIMAL 1 |
2124 | #define EV_USE_POLL 0 |
2171 | #define EV_USE_POLL 0 |
2125 | #define EV_MULTIPLICITY 0 |
2172 | #define EV_MULTIPLICITY 0 |
2126 | #define EV_PERIODICS 0 |
2173 | #define EV_PERIODIC_ENABLE 0 |
|
|
2174 | #define EV_STAT_ENABLE 0 |
|
|
2175 | #define EV_FORK_ENABLE 0 |
2127 | #define EV_CONFIG_H <config.h> |
2176 | #define EV_CONFIG_H <config.h> |
|
|
2177 | #define EV_MINPRI 0 |
|
|
2178 | #define EV_MAXPRI 0 |
2128 | |
2179 | |
2129 | #include "ev++.h" |
2180 | #include "ev++.h" |
2130 | |
2181 | |
2131 | And a F<ev_cpp.C> implementation file that contains libev proper and is compiled: |
2182 | And a F<ev_cpp.C> implementation file that contains libev proper and is compiled: |
2132 | |
2183 | |
… | |
… | |
2148 | |
2199 | |
2149 | =item Starting io/check/prepare/idle/signal/child watchers: O(1) |
2200 | =item Starting io/check/prepare/idle/signal/child watchers: O(1) |
2150 | |
2201 | |
2151 | =item Stopping check/prepare/idle watchers: O(1) |
2202 | =item Stopping check/prepare/idle watchers: O(1) |
2152 | |
2203 | |
2153 | =item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % 16)) |
2204 | =item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE)) |
2154 | |
2205 | |
2155 | =item Finding the next timer per loop iteration: O(1) |
2206 | =item Finding the next timer per loop iteration: O(1) |
2156 | |
2207 | |
2157 | =item Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd) |
2208 | =item Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd) |
2158 | |
2209 | |