… | |
… | |
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 |
… | |
… | |
1222 | not exist" is signified by the C<st_nlink> field being zero (which is |
1223 | 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 |
1224 | otherwise always forced to be at least one) and all the other fields of |
1224 | the stat buffer having unspecified contents. |
1225 | the stat buffer having unspecified contents. |
1225 | |
1226 | |
1226 | Since there is no standard to do this, the portable implementation simply |
1227 | 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 |
1228 | 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 |
1229 | 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, |
1230 | 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 |
1231 | unspecified default> value will be used (which you can expect to be around |
1231 | five seconds, although this might change dynamically). Libev will also |
1232 | five seconds, although this might change dynamically). Libev will also |
1232 | impose a minimum interval which is currently around C<0.1>, but thats |
1233 | impose a minimum interval which is currently around C<0.1>, but thats |
… | |
… | |
1234 | |
1235 | |
1235 | This watcher type is not meant for massive numbers of stat watchers, |
1236 | This watcher type is not meant for massive numbers of stat watchers, |
1236 | as even with OS-supported change notifications, this can be |
1237 | as even with OS-supported change notifications, this can be |
1237 | resource-intensive. |
1238 | resource-intensive. |
1238 | |
1239 | |
1239 | At the time of this writing, no specific OS backends are implemented, but |
1240 | 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. |
1241 | implemented (implementing kqueue support is left as an exercise for the |
|
|
1242 | reader). Inotify will be used to give hints only and should not change the |
|
|
1243 | semantics of C<ev_stat> watchers, which means that libev sometimes needs |
|
|
1244 | to fall back to regular polling again even with inotify, but changes are |
|
|
1245 | usually detected immediately, and if the file exists there will be no |
|
|
1246 | polling. |
1241 | |
1247 | |
1242 | =over 4 |
1248 | =over 4 |
1243 | |
1249 | |
1244 | =item ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval) |
1250 | =item ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval) |
1245 | |
1251 | |
… | |
… | |
2014 | |
2020 | |
2015 | =item EV_USE_DEVPOLL |
2021 | =item EV_USE_DEVPOLL |
2016 | |
2022 | |
2017 | reserved for future expansion, works like the USE symbols above. |
2023 | reserved for future expansion, works like the USE symbols above. |
2018 | |
2024 | |
|
|
2025 | =item EV_USE_INOTIFY |
|
|
2026 | |
|
|
2027 | If defined to be C<1>, libev will compile in support for the Linux inotify |
|
|
2028 | interface to speed up C<ev_stat> watchers. Its actual availability will |
|
|
2029 | be detected at runtime. |
|
|
2030 | |
2019 | =item EV_H |
2031 | =item EV_H |
2020 | |
2032 | |
2021 | The name of the F<ev.h> header file used to include it. The default if |
2033 | 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 |
2034 | 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. |
2035 | can be used to virtually rename the F<ev.h> header file in case of conflicts. |
… | |
… | |
2078 | =item EV_PID_HASHSIZE |
2090 | =item EV_PID_HASHSIZE |
2079 | |
2091 | |
2080 | C<ev_child> watchers use a small hash table to distribute workload by |
2092 | 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 |
2093 | 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 |
2094 | than enough. If you need to manage thousands of children you might want to |
2083 | increase this value. |
2095 | increase this value (I<must> be a power of two). |
|
|
2096 | |
|
|
2097 | =item EV_INOTIFY_HASHSIZE |
|
|
2098 | |
|
|
2099 | C<ev_staz> watchers use a small hash table to distribute workload by |
|
|
2100 | inotify watch id. The default size is C<16> (or C<1> with C<EV_MINIMAL>), |
|
|
2101 | usually more than enough. If you need to manage thousands of C<ev_stat> |
|
|
2102 | watchers you might want to increase this value (I<must> be a power of |
|
|
2103 | two). |
2084 | |
2104 | |
2085 | =item EV_COMMON |
2105 | =item EV_COMMON |
2086 | |
2106 | |
2087 | By default, all watchers have a C<void *data> member. By redefining |
2107 | 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 |
2108 | this macro to a something else you can include more and other types of |
… | |
… | |
2148 | |
2168 | |
2149 | =item Starting io/check/prepare/idle/signal/child watchers: O(1) |
2169 | =item Starting io/check/prepare/idle/signal/child watchers: O(1) |
2150 | |
2170 | |
2151 | =item Stopping check/prepare/idle watchers: O(1) |
2171 | =item Stopping check/prepare/idle watchers: O(1) |
2152 | |
2172 | |
2153 | =item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % 16)) |
2173 | =item Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE)) |
2154 | |
2174 | |
2155 | =item Finding the next timer per loop iteration: O(1) |
2175 | =item Finding the next timer per loop iteration: O(1) |
2156 | |
2176 | |
2157 | =item Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd) |
2177 | =item Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd) |
2158 | |
2178 | |