… | |
… | |
39 | F<README.embed> in the libev distribution. If libev was configured without |
39 | F<README.embed> in the libev distribution. If libev was configured without |
40 | support for multiple event loops, then all functions taking an initial |
40 | support for multiple event loops, then all functions taking an initial |
41 | argument of name C<loop> (which is always of type C<struct ev_loop *>) |
41 | argument of name C<loop> (which is always of type C<struct ev_loop *>) |
42 | will not have this argument. |
42 | will not have this argument. |
43 | |
43 | |
44 | =head1 TIME AND OTHER GLOBAL FUNCTIONS |
44 | =head1 TIME REPRESENTATION |
45 | |
45 | |
46 | Libev represents time as a single floating point number, representing the |
46 | Libev represents time as a single floating point number, representing the |
47 | (fractional) number of seconds since the (POSIX) epoch (somewhere near |
47 | (fractional) number of seconds since the (POSIX) epoch (somewhere near |
48 | the beginning of 1970, details are complicated, don't ask). This type is |
48 | the beginning of 1970, details are complicated, don't ask). This type is |
49 | called C<ev_tstamp>, which is what you should use too. It usually aliases |
49 | called C<ev_tstamp>, which is what you should use too. It usually aliases |
50 | to the double type in C. |
50 | to the double type in C. |
51 | |
51 | |
|
|
52 | =head1 GLOBAL FUNCTIONS |
|
|
53 | |
|
|
54 | These functions can be called anytime, even before initialising the |
|
|
55 | library in any way. |
|
|
56 | |
52 | =over 4 |
57 | =over 4 |
53 | |
58 | |
54 | =item ev_tstamp ev_time () |
59 | =item ev_tstamp ev_time () |
55 | |
60 | |
56 | Returns the current time as libev would use it. |
61 | Returns the current time as libev would use it. |
… | |
… | |
63 | you linked against by calling the functions C<ev_version_major> and |
68 | you linked against by calling the functions C<ev_version_major> and |
64 | C<ev_version_minor>. If you want, you can compare against the global |
69 | C<ev_version_minor>. If you want, you can compare against the global |
65 | symbols C<EV_VERSION_MAJOR> and C<EV_VERSION_MINOR>, which specify the |
70 | symbols C<EV_VERSION_MAJOR> and C<EV_VERSION_MINOR>, which specify the |
66 | version of the library your program was compiled against. |
71 | version of the library your program was compiled against. |
67 | |
72 | |
68 | Usually, its a good idea to terminate if the major versions mismatch, |
73 | Usually, it's a good idea to terminate if the major versions mismatch, |
69 | as this indicates an incompatible change. Minor versions are usually |
74 | as this indicates an incompatible change. Minor versions are usually |
70 | compatible to older versions, so a larger minor version alone is usually |
75 | compatible to older versions, so a larger minor version alone is usually |
71 | not a problem. |
76 | not a problem. |
72 | |
77 | |
73 | =item ev_set_allocator (void *(*cb)(void *ptr, long size)) |
78 | =item ev_set_allocator (void *(*cb)(void *ptr, long size)) |
… | |
… | |
99 | An event loop is described by a C<struct ev_loop *>. The library knows two |
104 | An event loop is described by a C<struct ev_loop *>. The library knows two |
100 | types of such loops, the I<default> loop, which supports signals and child |
105 | types of such loops, the I<default> loop, which supports signals and child |
101 | events, and dynamically created loops which do not. |
106 | events, and dynamically created loops which do not. |
102 | |
107 | |
103 | If you use threads, a common model is to run the default event loop |
108 | If you use threads, a common model is to run the default event loop |
104 | in your main thread (or in a separate thrad) and for each thread you |
109 | in your main thread (or in a separate thread) and for each thread you |
105 | create, you also create another event loop. Libev itself does no locking |
110 | create, you also create another event loop. Libev itself does no locking |
106 | whatsoever, so if you mix calls to the same event loop in different |
111 | whatsoever, so if you mix calls to the same event loop in different |
107 | threads, make sure you lock (this is usually a bad idea, though, even if |
112 | threads, make sure you lock (this is usually a bad idea, though, even if |
108 | done correctly, because its hideous and inefficient). |
113 | done correctly, because it's hideous and inefficient). |
109 | |
114 | |
110 | =over 4 |
115 | =over 4 |
111 | |
116 | |
112 | =item struct ev_loop *ev_default_loop (unsigned int flags) |
117 | =item struct ev_loop *ev_default_loop (unsigned int flags) |
113 | |
118 | |
… | |
… | |
124 | |
129 | |
125 | It supports the following flags: |
130 | It supports the following flags: |
126 | |
131 | |
127 | =over 4 |
132 | =over 4 |
128 | |
133 | |
129 | =item EVFLAG_AUTO |
134 | =item C<EVFLAG_AUTO> |
130 | |
135 | |
131 | The default flags value. Use this if you have no clue (its the right |
136 | The default flags value. Use this if you have no clue (it's the right |
132 | thing, believe me). |
137 | thing, believe me). |
133 | |
138 | |
134 | =item EVFLAG_NOENV |
139 | =item C<EVFLAG_NOENV> |
135 | |
140 | |
136 | If this flag bit is ored into the flag value (or the program runs setuid |
141 | If this flag bit is ored into the flag value (or the program runs setuid |
137 | or setgid) then libev will I<not> look at the environment variable |
142 | or setgid) then libev will I<not> look at the environment variable |
138 | C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will |
143 | C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will |
139 | override the flags completely if it is found in the environment. This is |
144 | override the flags completely if it is found in the environment. This is |
140 | useful to try out specific backends to test their performance, or to work |
145 | useful to try out specific backends to test their performance, or to work |
141 | around bugs. |
146 | around bugs. |
142 | |
147 | |
143 | =item EVMETHOD_SELECT portable select backend |
148 | =item C<EVMETHOD_SELECT> (portable select backend) |
144 | |
149 | |
145 | =item EVMETHOD_POLL poll backend (everywhere except windows) |
150 | =item C<EVMETHOD_POLL> (poll backend, available everywhere except on windows) |
146 | |
151 | |
147 | =item EVMETHOD_EPOLL linux only |
152 | =item C<EVMETHOD_EPOLL> (linux only) |
148 | |
153 | |
149 | =item EVMETHOD_KQUEUE some bsds only |
154 | =item C<EVMETHOD_KQUEUE> (some bsds only) |
150 | |
155 | |
151 | =item EVMETHOD_DEVPOLL solaris 8 only |
156 | =item C<EVMETHOD_DEVPOLL> (solaris 8 only) |
152 | |
157 | |
153 | =item EVMETHOD_PORT solaris 10 only |
158 | =item C<EVMETHOD_PORT> (solaris 10 only) |
154 | |
159 | |
155 | If one or more of these are ored into the flags value, then only these |
160 | If one or more of these are ored into the flags value, then only these |
156 | backends will be tried (in the reverse order as given here). If one are |
161 | backends will be tried (in the reverse order as given here). If one are |
157 | specified, any backend will do. |
162 | specified, any backend will do. |
158 | |
163 | |
… | |
… | |
167 | |
172 | |
168 | =item ev_default_destroy () |
173 | =item ev_default_destroy () |
169 | |
174 | |
170 | Destroys the default loop again (frees all memory and kernel state |
175 | Destroys the default loop again (frees all memory and kernel state |
171 | etc.). This stops all registered event watchers (by not touching them in |
176 | etc.). This stops all registered event watchers (by not touching them in |
172 | any way whatsoever, although you cnanot rely on this :). |
177 | any way whatsoever, although you cannot rely on this :). |
173 | |
178 | |
174 | =item ev_loop_destroy (loop) |
179 | =item ev_loop_destroy (loop) |
175 | |
180 | |
176 | Like C<ev_default_destroy>, but destroys an event loop created by an |
181 | Like C<ev_default_destroy>, but destroys an event loop created by an |
177 | earlier call to C<ev_loop_new>. |
182 | earlier call to C<ev_loop_new>. |
… | |
… | |
185 | |
190 | |
186 | You I<must> call this function after forking if and only if you want to |
191 | You I<must> call this function after forking if and only if you want to |
187 | use the event library in both processes. If you just fork+exec, you don't |
192 | use the event library in both processes. If you just fork+exec, you don't |
188 | have to call it. |
193 | have to call it. |
189 | |
194 | |
190 | The function itself is quite fast and its usually not a problem to call |
195 | The function itself is quite fast and it's usually not a problem to call |
191 | it just in case after a fork. To make this easy, the function will fit in |
196 | it just in case after a fork. To make this easy, the function will fit in |
192 | quite nicely into a call to C<pthread_atfork>: |
197 | quite nicely into a call to C<pthread_atfork>: |
193 | |
198 | |
194 | pthread_atfork (0, 0, ev_default_fork); |
199 | pthread_atfork (0, 0, ev_default_fork); |
195 | |
200 | |
… | |
… | |
202 | =item unsigned int ev_method (loop) |
207 | =item unsigned int ev_method (loop) |
203 | |
208 | |
204 | Returns one of the C<EVMETHOD_*> flags indicating the event backend in |
209 | Returns one of the C<EVMETHOD_*> flags indicating the event backend in |
205 | use. |
210 | use. |
206 | |
211 | |
207 | =item ev_tstamp = ev_now (loop) |
212 | =item ev_tstamp ev_now (loop) |
208 | |
213 | |
209 | Returns the current "event loop time", which is the time the event loop |
214 | Returns the current "event loop time", which is the time the event loop |
210 | got events and started processing them. This timestamp does not change |
215 | got events and started processing them. This timestamp does not change |
211 | as long as callbacks are being processed, and this is also the base time |
216 | as long as callbacks are being processed, and this is also the base time |
212 | used for relative timers. You can treat it as the timestamp of the event |
217 | used for relative timers. You can treat it as the timestamp of the event |
… | |
… | |
221 | If the flags argument is specified as 0, it will not return until either |
226 | If the flags argument is specified as 0, it will not return until either |
222 | no event watchers are active anymore or C<ev_unloop> was called. |
227 | no event watchers are active anymore or C<ev_unloop> was called. |
223 | |
228 | |
224 | A flags value of C<EVLOOP_NONBLOCK> will look for new events, will handle |
229 | A flags value of C<EVLOOP_NONBLOCK> will look for new events, will handle |
225 | those events and any outstanding ones, but will not block your process in |
230 | those events and any outstanding ones, but will not block your process in |
226 | case there are no events. |
231 | case there are no events and will return after one iteration of the loop. |
227 | |
232 | |
228 | A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if |
233 | A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if |
229 | neccessary) and will handle those and any outstanding ones. It will block |
234 | neccessary) and will handle those and any outstanding ones. It will block |
230 | your process until at least one new event arrives. |
235 | your process until at least one new event arrives, and will return after |
|
|
236 | one iteration of the loop. |
231 | |
237 | |
232 | This flags value could be used to implement alternative looping |
238 | This flags value could be used to implement alternative looping |
233 | constructs, but the C<prepare> and C<check> watchers provide a better and |
239 | constructs, but the C<prepare> and C<check> watchers provide a better and |
234 | more generic mechanism. |
240 | more generic mechanism. |
235 | |
241 | |
236 | =item ev_unloop (loop, how) |
242 | =item ev_unloop (loop, how) |
237 | |
243 | |
238 | Can be used to make a call to C<ev_loop> return early. The C<how> argument |
244 | Can be used to make a call to C<ev_loop> return early (but only after it |
|
|
245 | has processed all outstanding events). The C<how> argument must be either |
239 | must be either C<EVUNLOOP_ONCE>, which will make the innermost C<ev_loop> |
246 | C<EVUNLOOP_ONCE>, which will make the innermost C<ev_loop> call return, or |
240 | call return, or C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> |
247 | C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return. |
241 | calls return. |
|
|
242 | |
248 | |
243 | =item ev_ref (loop) |
249 | =item ev_ref (loop) |
244 | |
250 | |
245 | =item ev_unref (loop) |
251 | =item ev_unref (loop) |
246 | |
252 | |
247 | Ref/unref can be used to add or remove a refcount on the event loop: Every |
253 | Ref/unref can be used to add or remove a reference count on the event |
248 | watcher keeps one reference. If you have a long-runing watcher you never |
254 | loop: Every watcher keeps one reference, and as long as the reference |
249 | unregister that should not keep ev_loop from running, ev_unref() after |
255 | count is nonzero, C<ev_loop> will not return on its own. If you have |
250 | starting, and ev_ref() before stopping it. Libev itself uses this for |
256 | a watcher you never unregister that should not keep C<ev_loop> from |
251 | example for its internal signal pipe: It is not visible to you as a user |
257 | returning, ev_unref() after starting, and ev_ref() before stopping it. For |
252 | and should not keep C<ev_loop> from exiting if the work is done. It is |
258 | example, libev itself uses this for its internal signal pipe: It is not |
253 | also an excellent way to do this for generic recurring timers or from |
259 | visible to the libev user and should not keep C<ev_loop> from exiting if |
254 | within third-party libraries. Just remember to unref after start and ref |
260 | no event watchers registered by it are active. It is also an excellent |
255 | before stop. |
261 | way to do this for generic recurring timers or from within third-party |
|
|
262 | libraries. Just remember to I<unref after start> and I<ref before stop>. |
256 | |
263 | |
257 | =back |
264 | =back |
258 | |
265 | |
259 | =head1 ANATOMY OF A WATCHER |
266 | =head1 ANATOMY OF A WATCHER |
260 | |
267 | |
261 | A watcher is a structure that you create and register to record your |
268 | A watcher is a structure that you create and register to record your |
262 | interest in some event. For instance, if you want to wait for STDIN to |
269 | interest in some event. For instance, if you want to wait for STDIN to |
263 | become readable, you would create an ev_io watcher for that: |
270 | become readable, you would create an C<ev_io> watcher for that: |
264 | |
271 | |
265 | static void my_cb (struct ev_loop *loop, struct ev_io *w, int revents) |
272 | static void my_cb (struct ev_loop *loop, struct ev_io *w, int revents) |
266 | { |
273 | { |
267 | ev_io_stop (w); |
274 | ev_io_stop (w); |
268 | ev_unloop (loop, EVUNLOOP_ALL); |
275 | ev_unloop (loop, EVUNLOOP_ALL); |
… | |
… | |
297 | |
304 | |
298 | As long as your watcher is active (has been started but not stopped) you |
305 | As long as your watcher is active (has been started but not stopped) you |
299 | must not touch the values stored in it. Most specifically you must never |
306 | must not touch the values stored in it. Most specifically you must never |
300 | reinitialise it or call its set method. |
307 | reinitialise it or call its set method. |
301 | |
308 | |
302 | You cna check whether an event is active by calling the C<ev_is_active |
309 | You can check whether an event is active by calling the C<ev_is_active |
303 | (watcher *)> macro. To see whether an event is outstanding (but the |
310 | (watcher *)> macro. To see whether an event is outstanding (but the |
304 | callback for it has not been called yet) you cna use the C<ev_is_pending |
311 | callback for it has not been called yet) you can use the C<ev_is_pending |
305 | (watcher *)> macro. |
312 | (watcher *)> macro. |
306 | |
313 | |
307 | Each and every callback receives the event loop pointer as first, the |
314 | Each and every callback receives the event loop pointer as first, the |
308 | registered watcher structure as second, and a bitset of received events as |
315 | registered watcher structure as second, and a bitset of received events as |
309 | third argument. |
316 | third argument. |
310 | |
317 | |
311 | The rceeived events usually include a single bit per event type received |
318 | The received events usually include a single bit per event type received |
312 | (you can receive multiple events at the same time). The possible bit masks |
319 | (you can receive multiple events at the same time). The possible bit masks |
313 | are: |
320 | are: |
314 | |
321 | |
315 | =over 4 |
322 | =over 4 |
316 | |
323 | |
317 | =item EV_READ |
324 | =item C<EV_READ> |
318 | |
325 | |
319 | =item EV_WRITE |
326 | =item C<EV_WRITE> |
320 | |
327 | |
321 | The file descriptor in the ev_io watcher has become readable and/or |
328 | The file descriptor in the C<ev_io> watcher has become readable and/or |
322 | writable. |
329 | writable. |
323 | |
330 | |
324 | =item EV_TIMEOUT |
331 | =item C<EV_TIMEOUT> |
325 | |
332 | |
326 | The ev_timer watcher has timed out. |
333 | The C<ev_timer> watcher has timed out. |
327 | |
334 | |
328 | =item EV_PERIODIC |
335 | =item C<EV_PERIODIC> |
329 | |
336 | |
330 | The ev_periodic watcher has timed out. |
337 | The C<ev_periodic> watcher has timed out. |
331 | |
338 | |
332 | =item EV_SIGNAL |
339 | =item C<EV_SIGNAL> |
333 | |
340 | |
334 | The signal specified in the ev_signal watcher has been received by a thread. |
341 | The signal specified in the C<ev_signal> watcher has been received by a thread. |
335 | |
342 | |
336 | =item EV_CHILD |
343 | =item C<EV_CHILD> |
337 | |
344 | |
338 | The pid specified in the ev_child watcher has received a status change. |
345 | The pid specified in the C<ev_child> watcher has received a status change. |
339 | |
346 | |
340 | =item EV_IDLE |
347 | =item C<EV_IDLE> |
341 | |
348 | |
342 | The ev_idle watcher has determined that you have nothing better to do. |
349 | The C<ev_idle> watcher has determined that you have nothing better to do. |
343 | |
350 | |
344 | =item EV_PREPARE |
351 | =item C<EV_PREPARE> |
345 | |
352 | |
346 | =item EV_CHECK |
353 | =item C<EV_CHECK> |
347 | |
354 | |
348 | All ev_prepare watchers are invoked just I<before> C<ev_loop> starts |
355 | All C<ev_prepare> watchers are invoked just I<before> C<ev_loop> starts |
349 | to gather new events, and all ev_check watchers are invoked just after |
356 | to gather new events, and all C<ev_check> watchers are invoked just after |
350 | C<ev_loop> has gathered them, but before it invokes any callbacks for any |
357 | C<ev_loop> has gathered them, but before it invokes any callbacks for any |
351 | received events. Callbacks of both watcher types can start and stop as |
358 | received events. Callbacks of both watcher types can start and stop as |
352 | many watchers as they want, and all of them will be taken into account |
359 | many watchers as they want, and all of them will be taken into account |
353 | (for example, a ev_prepare watcher might start an idle watcher to keep |
360 | (for example, a C<ev_prepare> watcher might start an idle watcher to keep |
354 | C<ev_loop> from blocking). |
361 | C<ev_loop> from blocking). |
355 | |
362 | |
356 | =item EV_ERROR |
363 | =item C<EV_ERROR> |
357 | |
364 | |
358 | An unspecified error has occured, the watcher has been stopped. This might |
365 | An unspecified error has occured, the watcher has been stopped. This might |
359 | happen because the watcher could not be properly started because libev |
366 | happen because the watcher could not be properly started because libev |
360 | ran out of memory, a file descriptor was found to be closed or any other |
367 | ran out of memory, a file descriptor was found to be closed or any other |
361 | problem. You best act on it by reporting the problem and somehow coping |
368 | problem. You best act on it by reporting the problem and somehow coping |
… | |
… | |
370 | =back |
377 | =back |
371 | |
378 | |
372 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
379 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
373 | |
380 | |
374 | Each watcher has, by default, a member C<void *data> that you can change |
381 | Each watcher has, by default, a member C<void *data> that you can change |
375 | and read at any time, libev will completely ignore it. This cna be used |
382 | and read at any time, libev will completely ignore it. This can be used |
376 | to associate arbitrary data with your watcher. If you need more data and |
383 | to associate arbitrary data with your watcher. If you need more data and |
377 | don't want to allocate memory and store a pointer to it in that data |
384 | don't want to allocate memory and store a pointer to it in that data |
378 | member, you can also "subclass" the watcher type and provide your own |
385 | member, you can also "subclass" the watcher type and provide your own |
379 | data: |
386 | data: |
380 | |
387 | |
… | |
… | |
402 | =head1 WATCHER TYPES |
409 | =head1 WATCHER TYPES |
403 | |
410 | |
404 | This section describes each watcher in detail, but will not repeat |
411 | This section describes each watcher in detail, but will not repeat |
405 | information given in the last section. |
412 | information given in the last section. |
406 | |
413 | |
407 | =head2 struct ev_io - is my file descriptor readable or writable |
414 | =head2 C<ev_io> - is this file descriptor readable or writable |
408 | |
415 | |
409 | I/O watchers check whether a file descriptor is readable or writable |
416 | I/O watchers check whether a file descriptor is readable or writable |
410 | in each iteration of the event loop (This behaviour is called |
417 | in each iteration of the event loop (This behaviour is called |
411 | level-triggering because you keep receiving events as long as the |
418 | level-triggering because you keep receiving events as long as the |
412 | condition persists. Remember you cna stop the watcher if you don't want to |
419 | condition persists. Remember you can stop the watcher if you don't want to |
413 | act on the event and neither want to receive future events). |
420 | act on the event and neither want to receive future events). |
414 | |
421 | |
415 | In general you can register as many read and/or write event watchers oer |
422 | In general you can register as many read and/or write event watchers per |
416 | fd as you want (as long as you don't confuse yourself). Setting all file |
423 | fd as you want (as long as you don't confuse yourself). Setting all file |
417 | descriptors to non-blocking mode is also usually a good idea (but not |
424 | descriptors to non-blocking mode is also usually a good idea (but not |
418 | required if you know what you are doing). |
425 | required if you know what you are doing). |
419 | |
426 | |
420 | You have to be careful with dup'ed file descriptors, though. Some backends |
427 | You have to be careful with dup'ed file descriptors, though. Some backends |
421 | (the linux epoll backend is a notable example) cannot handle dup'ed file |
428 | (the linux epoll backend is a notable example) cannot handle dup'ed file |
422 | descriptors correctly if you register interest in two or more fds pointing |
429 | descriptors correctly if you register interest in two or more fds pointing |
423 | to the same file/socket etc. description. |
430 | to the same file/socket etc. description (that is, they share the same |
|
|
431 | underlying "file open"). |
424 | |
432 | |
425 | If you must do this, then force the use of a known-to-be-good backend |
433 | If you must do this, then force the use of a known-to-be-good backend |
426 | (at the time of this writing, this includes only EVMETHOD_SELECT and |
434 | (at the time of this writing, this includes only EVMETHOD_SELECT and |
427 | EVMETHOD_POLL). |
435 | EVMETHOD_POLL). |
428 | |
436 | |
… | |
… | |
430 | |
438 | |
431 | =item ev_io_init (ev_io *, callback, int fd, int events) |
439 | =item ev_io_init (ev_io *, callback, int fd, int events) |
432 | |
440 | |
433 | =item ev_io_set (ev_io *, int fd, int events) |
441 | =item ev_io_set (ev_io *, int fd, int events) |
434 | |
442 | |
435 | Configures an ev_io watcher. The fd is the file descriptor to rceeive |
443 | Configures an C<ev_io> watcher. The fd is the file descriptor to rceeive |
436 | events for and events is either C<EV_READ>, C<EV_WRITE> or C<EV_READ | |
444 | events for and events is either C<EV_READ>, C<EV_WRITE> or C<EV_READ | |
437 | EV_WRITE> to receive the given events. |
445 | EV_WRITE> to receive the given events. |
438 | |
446 | |
439 | =back |
447 | =back |
440 | |
448 | |
441 | =head2 struct ev_timer - relative and optionally recurring timeouts |
449 | =head2 C<ev_timer> - relative and optionally recurring timeouts |
442 | |
450 | |
443 | Timer watchers are simple relative timers that generate an event after a |
451 | Timer watchers are simple relative timers that generate an event after a |
444 | given time, and optionally repeating in regular intervals after that. |
452 | given time, and optionally repeating in regular intervals after that. |
445 | |
453 | |
446 | The timers are based on real time, that is, if you register an event that |
454 | The timers are based on real time, that is, if you register an event that |
447 | times out after an hour and youreset your system clock to last years |
455 | times out after an hour and you reset your system clock to last years |
448 | time, it will still time out after (roughly) and hour. "Roughly" because |
456 | time, it will still time out after (roughly) and hour. "Roughly" because |
449 | detecting time jumps is hard, and soem inaccuracies are unavoidable (the |
457 | detecting time jumps is hard, and soem inaccuracies are unavoidable (the |
450 | monotonic clock option helps a lot here). |
458 | monotonic clock option helps a lot here). |
|
|
459 | |
|
|
460 | The relative timeouts are calculated relative to the C<ev_now ()> |
|
|
461 | time. This is usually the right thing as this timestamp refers to the time |
|
|
462 | of the event triggering whatever timeout you are modifying/starting. If |
|
|
463 | you suspect event processing to be delayed and you *need* to base the timeout |
|
|
464 | on the current time, use something like this to adjust for this: |
|
|
465 | |
|
|
466 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
451 | |
467 | |
452 | =over 4 |
468 | =over 4 |
453 | |
469 | |
454 | =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat) |
470 | =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat) |
455 | |
471 | |
… | |
… | |
461 | later, again, and again, until stopped manually. |
477 | later, again, and again, until stopped manually. |
462 | |
478 | |
463 | The timer itself will do a best-effort at avoiding drift, that is, if you |
479 | The timer itself will do a best-effort at avoiding drift, that is, if you |
464 | configure a timer to trigger every 10 seconds, then it will trigger at |
480 | configure a timer to trigger every 10 seconds, then it will trigger at |
465 | exactly 10 second intervals. If, however, your program cannot keep up with |
481 | exactly 10 second intervals. If, however, your program cannot keep up with |
466 | the timer (ecause it takes longer than those 10 seconds to do stuff) the |
482 | the timer (because it takes longer than those 10 seconds to do stuff) the |
467 | timer will not fire more than once per event loop iteration. |
483 | timer will not fire more than once per event loop iteration. |
468 | |
484 | |
469 | =item ev_timer_again (loop) |
485 | =item ev_timer_again (loop) |
470 | |
486 | |
471 | This will act as if the timer timed out and restart it again if it is |
487 | This will act as if the timer timed out and restart it again if it is |
… | |
… | |
478 | |
494 | |
479 | This sounds a bit complicated, but here is a useful and typical |
495 | This sounds a bit complicated, but here is a useful and typical |
480 | example: Imagine you have a tcp connection and you want a so-called idle |
496 | example: Imagine you have a tcp connection and you want a so-called idle |
481 | timeout, that is, you want to be called when there have been, say, 60 |
497 | timeout, that is, you want to be called when there have been, say, 60 |
482 | seconds of inactivity on the socket. The easiest way to do this is to |
498 | seconds of inactivity on the socket. The easiest way to do this is to |
483 | configure an ev_timer with after=repeat=60 and calling ev_timer_again each |
499 | configure an C<ev_timer> with after=repeat=60 and calling ev_timer_again each |
484 | time you successfully read or write some data. If you go into an idle |
500 | time you successfully read or write some data. If you go into an idle |
485 | state where you do not expect data to travel on the socket, you can stop |
501 | state where you do not expect data to travel on the socket, you can stop |
486 | the timer, and again will automatically restart it if need be. |
502 | the timer, and again will automatically restart it if need be. |
487 | |
503 | |
488 | =back |
504 | =back |
489 | |
505 | |
490 | =head2 ev_periodic - to cron or not to cron it |
506 | =head2 C<ev_periodic> - to cron or not to cron |
491 | |
507 | |
492 | Periodic watchers are also timers of a kind, but they are very versatile |
508 | Periodic watchers are also timers of a kind, but they are very versatile |
493 | (and unfortunately a bit complex). |
509 | (and unfortunately a bit complex). |
494 | |
510 | |
495 | Unlike ev_timer's, they are not based on real time (or relative time) |
511 | Unlike C<ev_timer>'s, they are not based on real time (or relative time) |
496 | but on wallclock time (absolute time). You can tell a periodic watcher |
512 | but on wallclock time (absolute time). You can tell a periodic watcher |
497 | to trigger "at" some specific point in time. For example, if you tell a |
513 | to trigger "at" some specific point in time. For example, if you tell a |
498 | periodic watcher to trigger in 10 seconds (by specifiying e.g. c<ev_now () |
514 | periodic watcher to trigger in 10 seconds (by specifiying e.g. c<ev_now () |
499 | + 10.>) and then reset your system clock to the last year, then it will |
515 | + 10.>) and then reset your system clock to the last year, then it will |
500 | take a year to trigger the event (unlike an ev_timer, which would trigger |
516 | take a year to trigger the event (unlike an C<ev_timer>, which would trigger |
501 | roughly 10 seconds later and of course not if you reset your system time |
517 | roughly 10 seconds later and of course not if you reset your system time |
502 | again). |
518 | again). |
503 | |
519 | |
504 | They can also be used to implement vastly more complex timers, such as |
520 | They can also be used to implement vastly more complex timers, such as |
505 | triggering an event on eahc midnight, local time. |
521 | triggering an event on eahc midnight, local time. |
… | |
… | |
534 | |
550 | |
535 | ev_periodic_set (&periodic, 0., 3600., 0); |
551 | ev_periodic_set (&periodic, 0., 3600., 0); |
536 | |
552 | |
537 | This doesn't mean there will always be 3600 seconds in between triggers, |
553 | This doesn't mean there will always be 3600 seconds in between triggers, |
538 | but only that the the callback will be called when the system time shows a |
554 | but only that the the callback will be called when the system time shows a |
539 | full hour (UTC), or more correct, when the system time is evenly divisible |
555 | full hour (UTC), or more correctly, when the system time is evenly divisible |
540 | by 3600. |
556 | by 3600. |
541 | |
557 | |
542 | Another way to think about it (for the mathematically inclined) is that |
558 | Another way to think about it (for the mathematically inclined) is that |
543 | ev_periodic will try to run the callback in this mode at the next possible |
559 | C<ev_periodic> will try to run the callback in this mode at the next possible |
544 | time where C<time = at (mod interval)>, regardless of any time jumps. |
560 | time where C<time = at (mod interval)>, regardless of any time jumps. |
545 | |
561 | |
546 | =item * manual reschedule mode (reschedule_cb = callback) |
562 | =item * manual reschedule mode (reschedule_cb = callback) |
547 | |
563 | |
548 | In this mode the values for C<interval> and C<at> are both being |
564 | In this mode the values for C<interval> and C<at> are both being |
549 | ignored. Instead, each time the periodic watcher gets scheduled, the |
565 | ignored. Instead, each time the periodic watcher gets scheduled, the |
550 | reschedule callback will be called with the watcher as first, and the |
566 | reschedule callback will be called with the watcher as first, and the |
551 | current time as second argument. |
567 | current time as second argument. |
552 | |
568 | |
553 | NOTE: I<This callback MUST NOT stop or destroy the periodic or any other |
569 | NOTE: I<This callback MUST NOT stop or destroy any periodic watcher, |
554 | periodic watcher, ever, or make any event loop modificstions>. If you need |
570 | ever, or make any event loop modifications>. If you need to stop it, |
555 | to stop it, return 1e30 (or so, fudge fudge) and stop it afterwards. |
571 | return C<now + 1e30> (or so, fudge fudge) and stop it afterwards (e.g. by |
|
|
572 | starting a prepare watcher). |
556 | |
573 | |
557 | Its prototype is c<ev_tstamp (*reschedule_cb)(struct ev_periodic *w, |
574 | Its prototype is C<ev_tstamp (*reschedule_cb)(struct ev_periodic *w, |
558 | ev_tstamp now)>, e.g.: |
575 | ev_tstamp now)>, e.g.: |
559 | |
576 | |
560 | static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) |
577 | static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) |
561 | { |
578 | { |
562 | return now + 60.; |
579 | return now + 60.; |
… | |
… | |
565 | It must return the next time to trigger, based on the passed time value |
582 | It must return the next time to trigger, based on the passed time value |
566 | (that is, the lowest time value larger than to the second argument). It |
583 | (that is, the lowest time value larger than to the second argument). It |
567 | will usually be called just before the callback will be triggered, but |
584 | will usually be called just before the callback will be triggered, but |
568 | might be called at other times, too. |
585 | might be called at other times, too. |
569 | |
586 | |
|
|
587 | NOTE: I<< This callback must always return a time that is later than the |
|
|
588 | passed C<now> value >>. Not even C<now> itself will do, it I<must> be larger. |
|
|
589 | |
570 | This can be used to create very complex timers, such as a timer that |
590 | This can be used to create very complex timers, such as a timer that |
571 | triggers on each midnight, local time. To do this, you would calculate the |
591 | triggers on each midnight, local time. To do this, you would calculate the |
572 | next midnight after C<now> and return the timestamp value for this. How you do this |
592 | next midnight after C<now> and return the timestamp value for this. How |
573 | is, again, up to you (but it is not trivial). |
593 | you do this is, again, up to you (but it is not trivial, which is the main |
|
|
594 | reason I omitted it as an example). |
574 | |
595 | |
575 | =back |
596 | =back |
576 | |
597 | |
577 | =item ev_periodic_again (loop, ev_periodic *) |
598 | =item ev_periodic_again (loop, ev_periodic *) |
578 | |
599 | |
… | |
… | |
581 | a different time than the last time it was called (e.g. in a crond like |
602 | a different time than the last time it was called (e.g. in a crond like |
582 | program when the crontabs have changed). |
603 | program when the crontabs have changed). |
583 | |
604 | |
584 | =back |
605 | =back |
585 | |
606 | |
586 | =head2 ev_signal - signal me when a signal gets signalled |
607 | =head2 C<ev_signal> - signal me when a signal gets signalled |
587 | |
608 | |
588 | Signal watchers will trigger an event when the process receives a specific |
609 | Signal watchers will trigger an event when the process receives a specific |
589 | signal one or more times. Even though signals are very asynchronous, libev |
610 | signal one or more times. Even though signals are very asynchronous, libev |
590 | will try its best to deliver signals synchronously, i.e. as part of the |
611 | will try it's best to deliver signals synchronously, i.e. as part of the |
591 | normal event processing, like any other event. |
612 | normal event processing, like any other event. |
592 | |
613 | |
593 | You cna configure as many watchers as you like per signal. Only when the |
614 | You can configure as many watchers as you like per signal. Only when the |
594 | first watcher gets started will libev actually register a signal watcher |
615 | first watcher gets started will libev actually register a signal watcher |
595 | with the kernel (thus it coexists with your own signal handlers as long |
616 | with the kernel (thus it coexists with your own signal handlers as long |
596 | as you don't register any with libev). Similarly, when the last signal |
617 | as you don't register any with libev). Similarly, when the last signal |
597 | watcher for a signal is stopped libev will reset the signal handler to |
618 | watcher for a signal is stopped libev will reset the signal handler to |
598 | SIG_DFL (regardless of what it was set to before). |
619 | SIG_DFL (regardless of what it was set to before). |
… | |
… | |
606 | Configures the watcher to trigger on the given signal number (usually one |
627 | Configures the watcher to trigger on the given signal number (usually one |
607 | of the C<SIGxxx> constants). |
628 | of the C<SIGxxx> constants). |
608 | |
629 | |
609 | =back |
630 | =back |
610 | |
631 | |
611 | =head2 ev_child - wait for pid status changes |
632 | =head2 C<ev_child> - wait for pid status changes |
612 | |
633 | |
613 | Child watchers trigger when your process receives a SIGCHLD in response to |
634 | Child watchers trigger when your process receives a SIGCHLD in response to |
614 | some child status changes (most typically when a child of yours dies). |
635 | some child status changes (most typically when a child of yours dies). |
615 | |
636 | |
616 | =over 4 |
637 | =over 4 |
… | |
… | |
620 | =item ev_child_set (ev_child *, int pid) |
641 | =item ev_child_set (ev_child *, int pid) |
621 | |
642 | |
622 | Configures the watcher to wait for status changes of process C<pid> (or |
643 | Configures the watcher to wait for status changes of process C<pid> (or |
623 | I<any> process if C<pid> is specified as C<0>). The callback can look |
644 | I<any> process if C<pid> is specified as C<0>). The callback can look |
624 | at the C<rstatus> member of the C<ev_child> watcher structure to see |
645 | at the C<rstatus> member of the C<ev_child> watcher structure to see |
625 | the status word (use the macros from C<sys/wait.h>). The C<rpid> member |
646 | the status word (use the macros from C<sys/wait.h> and see your systems |
626 | contains the pid of the process causing the status change. |
647 | C<waitpid> documentation). The C<rpid> member contains the pid of the |
|
|
648 | process causing the status change. |
627 | |
649 | |
628 | =back |
650 | =back |
629 | |
651 | |
630 | =head2 ev_idle - when you've got nothing better to do |
652 | =head2 C<ev_idle> - when you've got nothing better to do |
631 | |
653 | |
632 | Idle watchers trigger events when there are no other I/O or timer (or |
654 | Idle watchers trigger events when there are no other events are pending |
633 | periodic) events pending. That is, as long as your process is busy |
655 | (prepare, check and other idle watchers do not count). That is, as long |
634 | handling sockets or timeouts it will not be called. But when your process |
656 | as your process is busy handling sockets or timeouts (or even signals, |
635 | is idle all idle watchers are being called again and again - until |
657 | imagine) it will not be triggered. But when your process is idle all idle |
|
|
658 | watchers are being called again and again, once per event loop iteration - |
636 | stopped, that is, or your process receives more events. |
659 | until stopped, that is, or your process receives more events and becomes |
|
|
660 | busy. |
637 | |
661 | |
638 | The most noteworthy effect is that as long as any idle watchers are |
662 | The most noteworthy effect is that as long as any idle watchers are |
639 | active, the process will not block when waiting for new events. |
663 | active, the process will not block when waiting for new events. |
640 | |
664 | |
641 | Apart from keeping your process non-blocking (which is a useful |
665 | Apart from keeping your process non-blocking (which is a useful |
… | |
… | |
651 | kind. There is a C<ev_idle_set> macro, but using it is utterly pointless, |
675 | kind. There is a C<ev_idle_set> macro, but using it is utterly pointless, |
652 | believe me. |
676 | believe me. |
653 | |
677 | |
654 | =back |
678 | =back |
655 | |
679 | |
656 | =head2 prepare and check - your hooks into the event loop |
680 | =head2 C<ev_prepare> and C<ev_check> - customise your event loop |
657 | |
681 | |
658 | Prepare and check watchers usually (but not always) are used in |
682 | Prepare and check watchers are usually (but not always) used in tandem: |
659 | tandom. Prepare watchers get invoked before the process blocks and check |
683 | prepare watchers get invoked before the process blocks and check watchers |
660 | watchers afterwards. |
684 | afterwards. |
661 | |
685 | |
662 | Their main purpose is to integrate other event mechanisms into libev. This |
686 | Their main purpose is to integrate other event mechanisms into libev. This |
663 | could be used, for example, to track variable changes, implement your own |
687 | could be used, for example, to track variable changes, implement your own |
664 | watchers, integrate net-snmp or a coroutine library and lots more. |
688 | watchers, integrate net-snmp or a coroutine library and lots more. |
665 | |
689 | |
666 | This is done by examining in each prepare call which file descriptors need |
690 | This is done by examining in each prepare call which file descriptors need |
667 | to be watched by the other library, registering ev_io watchers for them |
691 | to be watched by the other library, registering C<ev_io> watchers for |
668 | and starting an ev_timer watcher for any timeouts (many libraries provide |
692 | them and starting an C<ev_timer> watcher for any timeouts (many libraries |
669 | just this functionality). Then, in the check watcher you check for any |
693 | provide just this functionality). Then, in the check watcher you check for |
670 | events that occured (by making your callbacks set soem flags for example) |
694 | any events that occured (by checking the pending status of all watchers |
671 | and call back into the library. |
695 | and stopping them) and call back into the library. The I/O and timer |
|
|
696 | callbacks will never actually be called (but must be valid nevertheless, |
|
|
697 | because you never know, you know?). |
672 | |
698 | |
673 | As another example, the perl Coro module uses these hooks to integrate |
699 | As another example, the Perl Coro module uses these hooks to integrate |
674 | coroutines into libev programs, by yielding to other active coroutines |
700 | coroutines into libev programs, by yielding to other active coroutines |
675 | during each prepare and only letting the process block if no coroutines |
701 | during each prepare and only letting the process block if no coroutines |
676 | are ready to run. |
702 | are ready to run (it's actually more complicated: it only runs coroutines |
|
|
703 | with priority higher than or equal to the event loop and one coroutine |
|
|
704 | of lower priority, but only once, using idle watchers to keep the event |
|
|
705 | loop from blocking if lower-priority coroutines are active, thus mapping |
|
|
706 | low-priority coroutines to idle/background tasks). |
677 | |
707 | |
678 | =over 4 |
708 | =over 4 |
679 | |
709 | |
680 | =item ev_prepare_init (ev_prepare *, callback) |
710 | =item ev_prepare_init (ev_prepare *, callback) |
681 | |
711 | |
682 | =item ev_check_init (ev_check *, callback) |
712 | =item ev_check_init (ev_check *, callback) |
683 | |
713 | |
684 | Initialises and configures the prepare or check watcher - they have no |
714 | Initialises and configures the prepare or check watcher - they have no |
685 | parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set> |
715 | parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set> |
686 | macros, but using them is utterly, utterly pointless. |
716 | macros, but using them is utterly, utterly and completely pointless. |
687 | |
717 | |
688 | =back |
718 | =back |
689 | |
719 | |
690 | =head1 OTHER FUNCTIONS |
720 | =head1 OTHER FUNCTIONS |
691 | |
721 | |
692 | There are some other fucntions of possible interest. Described. Here. Now. |
722 | There are some other functions of possible interest. Described. Here. Now. |
693 | |
723 | |
694 | =over 4 |
724 | =over 4 |
695 | |
725 | |
696 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
726 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
697 | |
727 | |
698 | This function combines a simple timer and an I/O watcher, calls your |
728 | This function combines a simple timer and an I/O watcher, calls your |
699 | callback on whichever event happens first and automatically stop both |
729 | callback on whichever event happens first and automatically stop both |
700 | watchers. This is useful if you want to wait for a single event on an fd |
730 | watchers. This is useful if you want to wait for a single event on an fd |
701 | or timeout without havign to allocate/configure/start/stop/free one or |
731 | or timeout without having to allocate/configure/start/stop/free one or |
702 | more watchers yourself. |
732 | more watchers yourself. |
703 | |
733 | |
704 | If C<fd> is less than 0, then no I/O watcher will be started and events is |
734 | If C<fd> is less than 0, then no I/O watcher will be started and events |
705 | ignored. Otherwise, an ev_io watcher for the given C<fd> and C<events> set |
735 | is being ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and |
706 | will be craeted and started. |
736 | C<events> set will be craeted and started. |
707 | |
737 | |
708 | If C<timeout> is less than 0, then no timeout watcher will be |
738 | If C<timeout> is less than 0, then no timeout watcher will be |
709 | started. Otherwise an ev_timer watcher with after = C<timeout> (and repeat |
739 | started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and |
710 | = 0) will be started. |
740 | repeat = 0) will be started. While C<0> is a valid timeout, it is of |
|
|
741 | dubious value. |
711 | |
742 | |
712 | The callback has the type C<void (*cb)(int revents, void *arg)> and |
743 | The callback has the type C<void (*cb)(int revents, void *arg)> and gets |
713 | gets passed an events set (normally a combination of EV_ERROR, EV_READ, |
744 | passed an C<revents> set like normal event callbacks (a combination of |
714 | EV_WRITE or EV_TIMEOUT) and the C<arg> value passed to C<ev_once>: |
745 | C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg> |
|
|
746 | value passed to C<ev_once>: |
715 | |
747 | |
716 | static void stdin_ready (int revents, void *arg) |
748 | static void stdin_ready (int revents, void *arg) |
717 | { |
749 | { |
718 | if (revents & EV_TIMEOUT) |
750 | if (revents & EV_TIMEOUT) |
719 | /* doh, nothing entered */ |
751 | /* doh, nothing entered */; |
720 | else if (revents & EV_READ) |
752 | else if (revents & EV_READ) |
721 | /* stdin might have data for us, joy! */ |
753 | /* stdin might have data for us, joy! */; |
722 | } |
754 | } |
723 | |
755 | |
724 | ev_once (STDIN_FILENO, EV_READm 10., stdin_ready, 0); |
756 | ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
725 | |
757 | |
726 | =item ev_feed_event (loop, watcher, int events) |
758 | =item ev_feed_event (loop, watcher, int events) |
727 | |
759 | |
728 | Feeds the given event set into the event loop, as if the specified event |
760 | Feeds the given event set into the event loop, as if the specified event |
729 | has happened for the specified watcher (which must be a pointer to an |
761 | had happened for the specified watcher (which must be a pointer to an |
730 | initialised but not necessarily active event watcher). |
762 | initialised but not necessarily started event watcher). |
731 | |
763 | |
732 | =item ev_feed_fd_event (loop, int fd, int revents) |
764 | =item ev_feed_fd_event (loop, int fd, int revents) |
733 | |
765 | |
734 | Feed an event on the given fd, as if a file descriptor backend detected it. |
766 | Feed an event on the given fd, as if a file descriptor backend detected |
|
|
767 | the given events it. |
735 | |
768 | |
736 | =item ev_feed_signal_event (loop, int signum) |
769 | =item ev_feed_signal_event (loop, int signum) |
737 | |
770 | |
738 | Feed an event as if the given signal occured (loop must be the default loop!). |
771 | Feed an event as if the given signal occured (loop must be the default loop!). |
739 | |
772 | |
740 | =back |
773 | =back |
741 | |
774 | |
|
|
775 | =head1 LIBEVENT EMULATION |
|
|
776 | |
|
|
777 | TBD. |
|
|
778 | |
|
|
779 | =head1 C++ SUPPORT |
|
|
780 | |
|
|
781 | TBD. |
|
|
782 | |
742 | =head1 AUTHOR |
783 | =head1 AUTHOR |
743 | |
784 | |
744 | Marc Lehmann <libev@schmorp.de>. |
785 | Marc Lehmann <libev@schmorp.de>. |
745 | |
786 | |