1 | .\" Automatically generated by Pod::Man 2.22 (Pod::Simple 3.07) |
1 | .\" Automatically generated by Pod::Man 4.11 (Pod::Simple 3.35) |
2 | .\" |
2 | .\" |
3 | .\" Standard preamble: |
3 | .\" Standard preamble: |
4 | .\" ======================================================================== |
4 | .\" ======================================================================== |
5 | .de Sp \" Vertical space (when we can't use .PP) |
5 | .de Sp \" Vertical space (when we can't use .PP) |
6 | .if t .sp .5v |
6 | .if t .sp .5v |
… | |
… | |
36 | .el\{\ |
36 | .el\{\ |
37 | . ds -- \|\(em\| |
37 | . ds -- \|\(em\| |
38 | . ds PI \(*p |
38 | . ds PI \(*p |
39 | . ds L" `` |
39 | . ds L" `` |
40 | . ds R" '' |
40 | . ds R" '' |
|
|
41 | . ds C` |
|
|
42 | . ds C' |
41 | 'br\} |
43 | 'br\} |
42 | .\" |
44 | .\" |
43 | .\" Escape single quotes in literal strings from groff's Unicode transform. |
45 | .\" Escape single quotes in literal strings from groff's Unicode transform. |
44 | .ie \n(.g .ds Aq \(aq |
46 | .ie \n(.g .ds Aq \(aq |
45 | .el .ds Aq ' |
47 | .el .ds Aq ' |
46 | .\" |
48 | .\" |
47 | .\" If the F register is turned on, we'll generate index entries on stderr for |
49 | .\" If the F register is >0, we'll generate index entries on stderr for |
48 | .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index |
50 | .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index |
49 | .\" entries marked with X<> in POD. Of course, you'll have to process the |
51 | .\" entries marked with X<> in POD. Of course, you'll have to process the |
50 | .\" output yourself in some meaningful fashion. |
52 | .\" output yourself in some meaningful fashion. |
51 | .ie \nF \{\ |
53 | .\" |
|
|
54 | .\" Avoid warning from groff about undefined register 'F'. |
52 | . de IX |
55 | .de IX |
53 | . tm Index:\\$1\t\\n%\t"\\$2" |
|
|
54 | .. |
56 | .. |
55 | . nr % 0 |
57 | .nr rF 0 |
56 | . rr F |
58 | .if \n(.g .if rF .nr rF 1 |
|
|
59 | .if (\n(rF:(\n(.g==0)) \{\ |
|
|
60 | . if \nF \{\ |
|
|
61 | . de IX |
|
|
62 | . tm Index:\\$1\t\\n%\t"\\$2" |
|
|
63 | .. |
|
|
64 | . if !\nF==2 \{\ |
|
|
65 | . nr % 0 |
|
|
66 | . nr F 2 |
|
|
67 | . \} |
|
|
68 | . \} |
57 | .\} |
69 | .\} |
58 | .el \{\ |
70 | .rr rF |
59 | . de IX |
|
|
60 | .. |
|
|
61 | .\} |
|
|
62 | .\" |
71 | .\" |
63 | .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). |
72 | .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). |
64 | .\" Fear. Run. Save yourself. No user-serviceable parts. |
73 | .\" Fear. Run. Save yourself. No user-serviceable parts. |
65 | . \" fudge factors for nroff and troff |
74 | . \" fudge factors for nroff and troff |
66 | .if n \{\ |
75 | .if n \{\ |
… | |
… | |
122 | .\} |
131 | .\} |
123 | .rm #[ #] #H #V #F C |
132 | .rm #[ #] #H #V #F C |
124 | .\" ======================================================================== |
133 | .\" ======================================================================== |
125 | .\" |
134 | .\" |
126 | .IX Title "LIBEV 3" |
135 | .IX Title "LIBEV 3" |
127 | .TH LIBEV 3 "2011-02-16" "libev-4.04" "libev - high performance full featured event loop" |
136 | .TH LIBEV 3 "2021-01-11" "libev-4.33" "libev - high performance full featured event loop" |
128 | .\" For nroff, turn off justification. Always turn off hyphenation; it makes |
137 | .\" For nroff, turn off justification. Always turn off hyphenation; it makes |
129 | .\" way too many mistakes in technical documents. |
138 | .\" way too many mistakes in technical documents. |
130 | .if n .ad l |
139 | .if n .ad l |
131 | .nh |
140 | .nh |
132 | .SH "NAME" |
141 | .SH "NAME" |
… | |
… | |
134 | .SH "SYNOPSIS" |
143 | .SH "SYNOPSIS" |
135 | .IX Header "SYNOPSIS" |
144 | .IX Header "SYNOPSIS" |
136 | .Vb 1 |
145 | .Vb 1 |
137 | \& #include <ev.h> |
146 | \& #include <ev.h> |
138 | .Ve |
147 | .Ve |
139 | .SS "\s-1EXAMPLE\s0 \s-1PROGRAM\s0" |
148 | .SS "\s-1EXAMPLE PROGRAM\s0" |
140 | .IX Subsection "EXAMPLE PROGRAM" |
149 | .IX Subsection "EXAMPLE PROGRAM" |
141 | .Vb 2 |
150 | .Vb 2 |
142 | \& // a single header file is required |
151 | \& // a single header file is required |
143 | \& #include <ev.h> |
152 | \& #include <ev.h> |
144 | \& |
153 | \& |
… | |
… | |
212 | throughout this document. |
221 | throughout this document. |
213 | .SH "WHAT TO READ WHEN IN A HURRY" |
222 | .SH "WHAT TO READ WHEN IN A HURRY" |
214 | .IX Header "WHAT TO READ WHEN IN A HURRY" |
223 | .IX Header "WHAT TO READ WHEN IN A HURRY" |
215 | This manual tries to be very detailed, but unfortunately, this also makes |
224 | This manual tries to be very detailed, but unfortunately, this also makes |
216 | it very long. If you just want to know the basics of libev, I suggest |
225 | it very long. If you just want to know the basics of libev, I suggest |
217 | reading \*(L"\s-1ANATOMY\s0 \s-1OF\s0 A \s-1WATCHER\s0\*(R", then the \*(L"\s-1EXAMPLE\s0 \s-1PROGRAM\s0\*(R" above and |
226 | reading \*(L"\s-1ANATOMY OF A WATCHER\*(R"\s0, then the \*(L"\s-1EXAMPLE PROGRAM\*(R"\s0 above and |
218 | look up the missing functions in \*(L"\s-1GLOBAL\s0 \s-1FUNCTIONS\s0\*(R" and the \f(CW\*(C`ev_io\*(C'\fR and |
227 | look up the missing functions in \*(L"\s-1GLOBAL FUNCTIONS\*(R"\s0 and the \f(CW\*(C`ev_io\*(C'\fR and |
219 | \&\f(CW\*(C`ev_timer\*(C'\fR sections in \*(L"\s-1WATCHER\s0 \s-1TYPES\s0\*(R". |
228 | \&\f(CW\*(C`ev_timer\*(C'\fR sections in \*(L"\s-1WATCHER TYPES\*(R"\s0. |
220 | .SH "ABOUT LIBEV" |
229 | .SH "ABOUT LIBEV" |
221 | .IX Header "ABOUT LIBEV" |
230 | .IX Header "ABOUT LIBEV" |
222 | Libev is an event loop: you register interest in certain events (such as a |
231 | Libev is an event loop: you register interest in certain events (such as a |
223 | file descriptor being readable or a timeout occurring), and it will manage |
232 | file descriptor being readable or a timeout occurring), and it will manage |
224 | these event sources and provide your program with events. |
233 | these event sources and provide your program with events. |
… | |
… | |
231 | watchers\fR, which are relatively small C structures you initialise with the |
240 | watchers\fR, which are relatively small C structures you initialise with the |
232 | details of the event, and then hand it over to libev by \fIstarting\fR the |
241 | details of the event, and then hand it over to libev by \fIstarting\fR the |
233 | watcher. |
242 | watcher. |
234 | .SS "\s-1FEATURES\s0" |
243 | .SS "\s-1FEATURES\s0" |
235 | .IX Subsection "FEATURES" |
244 | .IX Subsection "FEATURES" |
236 | Libev supports \f(CW\*(C`select\*(C'\fR, \f(CW\*(C`poll\*(C'\fR, the Linux-specific \f(CW\*(C`epoll\*(C'\fR, the |
245 | Libev supports \f(CW\*(C`select\*(C'\fR, \f(CW\*(C`poll\*(C'\fR, the Linux-specific aio and \f(CW\*(C`epoll\*(C'\fR |
237 | BSD-specific \f(CW\*(C`kqueue\*(C'\fR and the Solaris-specific event port mechanisms |
246 | interfaces, the BSD-specific \f(CW\*(C`kqueue\*(C'\fR and the Solaris-specific event port |
238 | for file descriptor events (\f(CW\*(C`ev_io\*(C'\fR), the Linux \f(CW\*(C`inotify\*(C'\fR interface |
247 | mechanisms for file descriptor events (\f(CW\*(C`ev_io\*(C'\fR), the Linux \f(CW\*(C`inotify\*(C'\fR |
239 | (for \f(CW\*(C`ev_stat\*(C'\fR), Linux eventfd/signalfd (for faster and cleaner |
248 | interface (for \f(CW\*(C`ev_stat\*(C'\fR), Linux eventfd/signalfd (for faster and cleaner |
240 | inter-thread wakeup (\f(CW\*(C`ev_async\*(C'\fR)/signal handling (\f(CW\*(C`ev_signal\*(C'\fR)) relative |
249 | inter-thread wakeup (\f(CW\*(C`ev_async\*(C'\fR)/signal handling (\f(CW\*(C`ev_signal\*(C'\fR)) relative |
241 | timers (\f(CW\*(C`ev_timer\*(C'\fR), absolute timers with customised rescheduling |
250 | timers (\f(CW\*(C`ev_timer\*(C'\fR), absolute timers with customised rescheduling |
242 | (\f(CW\*(C`ev_periodic\*(C'\fR), synchronous signals (\f(CW\*(C`ev_signal\*(C'\fR), process status |
251 | (\f(CW\*(C`ev_periodic\*(C'\fR), synchronous signals (\f(CW\*(C`ev_signal\*(C'\fR), process status |
243 | change events (\f(CW\*(C`ev_child\*(C'\fR), and event watchers dealing with the event |
252 | change events (\f(CW\*(C`ev_child\*(C'\fR), and event watchers dealing with the event |
244 | loop mechanism itself (\f(CW\*(C`ev_idle\*(C'\fR, \f(CW\*(C`ev_embed\*(C'\fR, \f(CW\*(C`ev_prepare\*(C'\fR and |
253 | loop mechanism itself (\f(CW\*(C`ev_idle\*(C'\fR, \f(CW\*(C`ev_embed\*(C'\fR, \f(CW\*(C`ev_prepare\*(C'\fR and |
245 | \&\f(CW\*(C`ev_check\*(C'\fR watchers) as well as file watchers (\f(CW\*(C`ev_stat\*(C'\fR) and even |
254 | \&\f(CW\*(C`ev_check\*(C'\fR watchers) as well as file watchers (\f(CW\*(C`ev_stat\*(C'\fR) and even |
246 | limited support for fork events (\f(CW\*(C`ev_fork\*(C'\fR). |
255 | limited support for fork events (\f(CW\*(C`ev_fork\*(C'\fR). |
247 | .PP |
256 | .PP |
248 | It also is quite fast (see this |
257 | It also is quite fast (see this |
249 | <benchmark> comparing it to libevent |
258 | benchmark <http://libev.schmorp.de/bench.html> comparing it to libevent |
250 | for example). |
259 | for example). |
251 | .SS "\s-1CONVENTIONS\s0" |
260 | .SS "\s-1CONVENTIONS\s0" |
252 | .IX Subsection "CONVENTIONS" |
261 | .IX Subsection "CONVENTIONS" |
253 | Libev is very configurable. In this manual the default (and most common) |
262 | Libev is very configurable. In this manual the default (and most common) |
254 | configuration will be described, which supports multiple event loops. For |
263 | configuration will be described, which supports multiple event loops. For |
255 | more info about various configuration options please have a look at |
264 | more info about various configuration options please have a look at |
256 | \&\fB\s-1EMBED\s0\fR section in this manual. If libev was configured without support |
265 | \&\fB\s-1EMBED\s0\fR section in this manual. If libev was configured without support |
257 | for multiple event loops, then all functions taking an initial argument of |
266 | for multiple event loops, then all functions taking an initial argument of |
258 | name \f(CW\*(C`loop\*(C'\fR (which is always of type \f(CW\*(C`struct ev_loop *\*(C'\fR) will not have |
267 | name \f(CW\*(C`loop\*(C'\fR (which is always of type \f(CW\*(C`struct ev_loop *\*(C'\fR) will not have |
259 | this argument. |
268 | this argument. |
260 | .SS "\s-1TIME\s0 \s-1REPRESENTATION\s0" |
269 | .SS "\s-1TIME REPRESENTATION\s0" |
261 | .IX Subsection "TIME REPRESENTATION" |
270 | .IX Subsection "TIME REPRESENTATION" |
262 | Libev represents time as a single floating point number, representing |
271 | Libev represents time as a single floating point number, representing |
263 | the (fractional) number of seconds since the (\s-1POSIX\s0) epoch (in practice |
272 | the (fractional) number of seconds since the (\s-1POSIX\s0) epoch (in practice |
264 | somewhere near the beginning of 1970, details are complicated, don't |
273 | somewhere near the beginning of 1970, details are complicated, don't |
265 | ask). This type is called \f(CW\*(C`ev_tstamp\*(C'\fR, which is what you should use |
274 | ask). This type is called \f(CW\*(C`ev_tstamp\*(C'\fR, which is what you should use |
… | |
… | |
282 | When libev detects a usage error such as a negative timer interval, then |
291 | When libev detects a usage error such as a negative timer interval, then |
283 | it will print a diagnostic message and abort (via the \f(CW\*(C`assert\*(C'\fR mechanism, |
292 | it will print a diagnostic message and abort (via the \f(CW\*(C`assert\*(C'\fR mechanism, |
284 | so \f(CW\*(C`NDEBUG\*(C'\fR will disable this checking): these are programming errors in |
293 | so \f(CW\*(C`NDEBUG\*(C'\fR will disable this checking): these are programming errors in |
285 | the libev caller and need to be fixed there. |
294 | the libev caller and need to be fixed there. |
286 | .PP |
295 | .PP |
|
|
296 | Via the \f(CW\*(C`EV_FREQUENT\*(C'\fR macro you can compile in and/or enable extensive |
|
|
297 | consistency checking code inside libev that can be used to check for |
|
|
298 | internal inconsistencies, suually caused by application bugs. |
|
|
299 | .PP |
287 | Libev also has a few internal error-checking \f(CW\*(C`assert\*(C'\fRions, and also has |
300 | Libev also has a few internal error-checking \f(CW\*(C`assert\*(C'\fRions. These do not |
288 | extensive consistency checking code. These do not trigger under normal |
|
|
289 | circumstances, as they indicate either a bug in libev or worse. |
301 | trigger under normal circumstances, as they indicate either a bug in libev |
|
|
302 | or worse. |
290 | .SH "GLOBAL FUNCTIONS" |
303 | .SH "GLOBAL FUNCTIONS" |
291 | .IX Header "GLOBAL FUNCTIONS" |
304 | .IX Header "GLOBAL FUNCTIONS" |
292 | These functions can be called anytime, even before initialising the |
305 | These functions can be called anytime, even before initialising the |
293 | library in any way. |
306 | library in any way. |
294 | .IP "ev_tstamp ev_time ()" 4 |
307 | .IP "ev_tstamp ev_time ()" 4 |
295 | .IX Item "ev_tstamp ev_time ()" |
308 | .IX Item "ev_tstamp ev_time ()" |
296 | Returns the current time as libev would use it. Please note that the |
309 | Returns the current time as libev would use it. Please note that the |
297 | \&\f(CW\*(C`ev_now\*(C'\fR function is usually faster and also often returns the timestamp |
310 | \&\f(CW\*(C`ev_now\*(C'\fR function is usually faster and also often returns the timestamp |
298 | you actually want to know. Also interesting is the combination of |
311 | you actually want to know. Also interesting is the combination of |
299 | \&\f(CW\*(C`ev_update_now\*(C'\fR and \f(CW\*(C`ev_now\*(C'\fR. |
312 | \&\f(CW\*(C`ev_now_update\*(C'\fR and \f(CW\*(C`ev_now\*(C'\fR. |
300 | .IP "ev_sleep (ev_tstamp interval)" 4 |
313 | .IP "ev_sleep (ev_tstamp interval)" 4 |
301 | .IX Item "ev_sleep (ev_tstamp interval)" |
314 | .IX Item "ev_sleep (ev_tstamp interval)" |
302 | Sleep for the given interval: The current thread will be blocked until |
315 | Sleep for the given interval: The current thread will be blocked |
303 | either it is interrupted or the given time interval has passed. Basically |
316 | until either it is interrupted or the given time interval has |
|
|
317 | passed (approximately \- it might return a bit earlier even if not |
|
|
318 | interrupted). Returns immediately if \f(CW\*(C`interval <= 0\*(C'\fR. |
|
|
319 | .Sp |
304 | this is a sub-second-resolution \f(CW\*(C`sleep ()\*(C'\fR. |
320 | Basically this is a sub-second-resolution \f(CW\*(C`sleep ()\*(C'\fR. |
|
|
321 | .Sp |
|
|
322 | The range of the \f(CW\*(C`interval\*(C'\fR is limited \- libev only guarantees to work |
|
|
323 | with sleep times of up to one day (\f(CW\*(C`interval <= 86400\*(C'\fR). |
305 | .IP "int ev_version_major ()" 4 |
324 | .IP "int ev_version_major ()" 4 |
306 | .IX Item "int ev_version_major ()" |
325 | .IX Item "int ev_version_major ()" |
307 | .PD 0 |
326 | .PD 0 |
308 | .IP "int ev_version_minor ()" 4 |
327 | .IP "int ev_version_minor ()" 4 |
309 | .IX Item "int ev_version_minor ()" |
328 | .IX Item "int ev_version_minor ()" |
… | |
… | |
361 | current system. To find which embeddable backends might be supported on |
380 | current system. To find which embeddable backends might be supported on |
362 | the current system, you would need to look at \f(CW\*(C`ev_embeddable_backends () |
381 | the current system, you would need to look at \f(CW\*(C`ev_embeddable_backends () |
363 | & ev_supported_backends ()\*(C'\fR, likewise for recommended ones. |
382 | & ev_supported_backends ()\*(C'\fR, likewise for recommended ones. |
364 | .Sp |
383 | .Sp |
365 | See the description of \f(CW\*(C`ev_embed\*(C'\fR watchers for more info. |
384 | See the description of \f(CW\*(C`ev_embed\*(C'\fR watchers for more info. |
366 | .IP "ev_set_allocator (void *(*cb)(void *ptr, long size))" 4 |
385 | .IP "ev_set_allocator (void *(*cb)(void *ptr, long size) throw ())" 4 |
367 | .IX Item "ev_set_allocator (void *(*cb)(void *ptr, long size))" |
386 | .IX Item "ev_set_allocator (void *(*cb)(void *ptr, long size) throw ())" |
368 | Sets the allocation function to use (the prototype is similar \- the |
387 | Sets the allocation function to use (the prototype is similar \- the |
369 | semantics are identical to the \f(CW\*(C`realloc\*(C'\fR C89/SuS/POSIX function). It is |
388 | semantics are identical to the \f(CW\*(C`realloc\*(C'\fR C89/SuS/POSIX function). It is |
370 | used to allocate and free memory (no surprises here). If it returns zero |
389 | used to allocate and free memory (no surprises here). If it returns zero |
371 | when memory needs to be allocated (\f(CW\*(C`size != 0\*(C'\fR), the library might abort |
390 | when memory needs to be allocated (\f(CW\*(C`size != 0\*(C'\fR), the library might abort |
372 | or take some potentially destructive action. |
391 | or take some potentially destructive action. |
… | |
… | |
377 | .Sp |
396 | .Sp |
378 | You could override this function in high-availability programs to, say, |
397 | You could override this function in high-availability programs to, say, |
379 | free some memory if it cannot allocate memory, to use a special allocator, |
398 | free some memory if it cannot allocate memory, to use a special allocator, |
380 | or even to sleep a while and retry until some memory is available. |
399 | or even to sleep a while and retry until some memory is available. |
381 | .Sp |
400 | .Sp |
|
|
401 | Example: The following is the \f(CW\*(C`realloc\*(C'\fR function that libev itself uses |
|
|
402 | which should work with \f(CW\*(C`realloc\*(C'\fR and \f(CW\*(C`free\*(C'\fR functions of all kinds and |
|
|
403 | is probably a good basis for your own implementation. |
|
|
404 | .Sp |
|
|
405 | .Vb 5 |
|
|
406 | \& static void * |
|
|
407 | \& ev_realloc_emul (void *ptr, long size) EV_NOEXCEPT |
|
|
408 | \& { |
|
|
409 | \& if (size) |
|
|
410 | \& return realloc (ptr, size); |
|
|
411 | \& |
|
|
412 | \& free (ptr); |
|
|
413 | \& return 0; |
|
|
414 | \& } |
|
|
415 | .Ve |
|
|
416 | .Sp |
382 | Example: Replace the libev allocator with one that waits a bit and then |
417 | Example: Replace the libev allocator with one that waits a bit and then |
383 | retries (example requires a standards-compliant \f(CW\*(C`realloc\*(C'\fR). |
418 | retries. |
384 | .Sp |
419 | .Sp |
385 | .Vb 6 |
420 | .Vb 8 |
386 | \& static void * |
421 | \& static void * |
387 | \& persistent_realloc (void *ptr, size_t size) |
422 | \& persistent_realloc (void *ptr, size_t size) |
388 | \& { |
423 | \& { |
|
|
424 | \& if (!size) |
|
|
425 | \& { |
|
|
426 | \& free (ptr); |
|
|
427 | \& return 0; |
|
|
428 | \& } |
|
|
429 | \& |
389 | \& for (;;) |
430 | \& for (;;) |
390 | \& { |
431 | \& { |
391 | \& void *newptr = realloc (ptr, size); |
432 | \& void *newptr = realloc (ptr, size); |
392 | \& |
433 | \& |
393 | \& if (newptr) |
434 | \& if (newptr) |
… | |
… | |
398 | \& } |
439 | \& } |
399 | \& |
440 | \& |
400 | \& ... |
441 | \& ... |
401 | \& ev_set_allocator (persistent_realloc); |
442 | \& ev_set_allocator (persistent_realloc); |
402 | .Ve |
443 | .Ve |
403 | .IP "ev_set_syserr_cb (void (*cb)(const char *msg))" 4 |
444 | .IP "ev_set_syserr_cb (void (*cb)(const char *msg) throw ())" 4 |
404 | .IX Item "ev_set_syserr_cb (void (*cb)(const char *msg))" |
445 | .IX Item "ev_set_syserr_cb (void (*cb)(const char *msg) throw ())" |
405 | Set the callback function to call on a retryable system call error (such |
446 | Set the callback function to call on a retryable system call error (such |
406 | as failed select, poll, epoll_wait). The message is a printable string |
447 | as failed select, poll, epoll_wait). The message is a printable string |
407 | indicating the system call or subsystem causing the problem. If this |
448 | indicating the system call or subsystem causing the problem. If this |
408 | callback is set, then libev will expect it to remedy the situation, no |
449 | callback is set, then libev will expect it to remedy the situation, no |
409 | matter what, when it returns. That is, libev will generally retry the |
450 | matter what, when it returns. That is, libev will generally retry the |
… | |
… | |
508 | .IX Item "EVFLAG_NOENV" |
549 | .IX Item "EVFLAG_NOENV" |
509 | If this flag bit is or'ed into the flag value (or the program runs setuid |
550 | If this flag bit is or'ed into the flag value (or the program runs setuid |
510 | or setgid) then libev will \fInot\fR look at the environment variable |
551 | or setgid) then libev will \fInot\fR look at the environment variable |
511 | \&\f(CW\*(C`LIBEV_FLAGS\*(C'\fR. Otherwise (the default), this environment variable will |
552 | \&\f(CW\*(C`LIBEV_FLAGS\*(C'\fR. Otherwise (the default), this environment variable will |
512 | override the flags completely if it is found in the environment. This is |
553 | override the flags completely if it is found in the environment. This is |
513 | useful to try out specific backends to test their performance, or to work |
554 | useful to try out specific backends to test their performance, to work |
514 | around bugs. |
555 | around bugs, or to make libev threadsafe (accessing environment variables |
|
|
556 | cannot be done in a threadsafe way, but usually it works if no other |
|
|
557 | thread modifies them). |
515 | .ie n .IP """EVFLAG_FORKCHECK""" 4 |
558 | .ie n .IP """EVFLAG_FORKCHECK""" 4 |
516 | .el .IP "\f(CWEVFLAG_FORKCHECK\fR" 4 |
559 | .el .IP "\f(CWEVFLAG_FORKCHECK\fR" 4 |
517 | .IX Item "EVFLAG_FORKCHECK" |
560 | .IX Item "EVFLAG_FORKCHECK" |
518 | Instead of calling \f(CW\*(C`ev_loop_fork\*(C'\fR manually after a fork, you can also |
561 | Instead of calling \f(CW\*(C`ev_loop_fork\*(C'\fR manually after a fork, you can also |
519 | make libev check for a fork in each iteration by enabling this flag. |
562 | make libev check for a fork in each iteration by enabling this flag. |
520 | .Sp |
563 | .Sp |
521 | This works by calling \f(CW\*(C`getpid ()\*(C'\fR on every iteration of the loop, |
564 | This works by calling \f(CW\*(C`getpid ()\*(C'\fR on every iteration of the loop, |
522 | and thus this might slow down your event loop if you do a lot of loop |
565 | and thus this might slow down your event loop if you do a lot of loop |
523 | iterations and little real work, but is usually not noticeable (on my |
566 | iterations and little real work, but is usually not noticeable (on my |
524 | GNU/Linux system for example, \f(CW\*(C`getpid\*(C'\fR is actually a simple 5\-insn sequence |
567 | GNU/Linux system for example, \f(CW\*(C`getpid\*(C'\fR is actually a simple 5\-insn |
525 | without a system call and thus \fIvery\fR fast, but my GNU/Linux system also has |
568 | sequence without a system call and thus \fIvery\fR fast, but my GNU/Linux |
526 | \&\f(CW\*(C`pthread_atfork\*(C'\fR which is even faster). |
569 | system also has \f(CW\*(C`pthread_atfork\*(C'\fR which is even faster). (Update: glibc |
|
|
570 | versions 2.25 apparently removed the \f(CW\*(C`getpid\*(C'\fR optimisation again). |
527 | .Sp |
571 | .Sp |
528 | The big advantage of this flag is that you can forget about fork (and |
572 | The big advantage of this flag is that you can forget about fork (and |
529 | forget about forgetting to tell libev about forking) when you use this |
573 | forget about forgetting to tell libev about forking, although you still |
530 | flag. |
574 | have to ignore \f(CW\*(C`SIGPIPE\*(C'\fR) when you use this flag. |
531 | .Sp |
575 | .Sp |
532 | This flag setting cannot be overridden or specified in the \f(CW\*(C`LIBEV_FLAGS\*(C'\fR |
576 | This flag setting cannot be overridden or specified in the \f(CW\*(C`LIBEV_FLAGS\*(C'\fR |
533 | environment variable. |
577 | environment variable. |
534 | .ie n .IP """EVFLAG_NOINOTIFY""" 4 |
578 | .ie n .IP """EVFLAG_NOINOTIFY""" 4 |
535 | .el .IP "\f(CWEVFLAG_NOINOTIFY\fR" 4 |
579 | .el .IP "\f(CWEVFLAG_NOINOTIFY\fR" 4 |
… | |
… | |
553 | example) that can't properly initialise their signal masks. |
597 | example) that can't properly initialise their signal masks. |
554 | .ie n .IP """EVFLAG_NOSIGMASK""" 4 |
598 | .ie n .IP """EVFLAG_NOSIGMASK""" 4 |
555 | .el .IP "\f(CWEVFLAG_NOSIGMASK\fR" 4 |
599 | .el .IP "\f(CWEVFLAG_NOSIGMASK\fR" 4 |
556 | .IX Item "EVFLAG_NOSIGMASK" |
600 | .IX Item "EVFLAG_NOSIGMASK" |
557 | When this flag is specified, then libev will avoid to modify the signal |
601 | When this flag is specified, then libev will avoid to modify the signal |
558 | mask. Specifically, this means you ahve to make sure signals are unblocked |
602 | mask. Specifically, this means you have to make sure signals are unblocked |
559 | when you want to receive them. |
603 | when you want to receive them. |
560 | .Sp |
604 | .Sp |
561 | This behaviour is useful when you want to do your own signal handling, or |
605 | This behaviour is useful when you want to do your own signal handling, or |
562 | want to handle signals only in specific threads and want to avoid libev |
606 | want to handle signals only in specific threads and want to avoid libev |
563 | unblocking the signals. |
607 | unblocking the signals. |
564 | .Sp |
608 | .Sp |
565 | It's also required by \s-1POSIX\s0 in a threaded program, as libev calls |
609 | It's also required by \s-1POSIX\s0 in a threaded program, as libev calls |
566 | \&\f(CW\*(C`sigprocmask\*(C'\fR, whose behaviour is officially unspecified. |
610 | \&\f(CW\*(C`sigprocmask\*(C'\fR, whose behaviour is officially unspecified. |
|
|
611 | .ie n .IP """EVFLAG_NOTIMERFD""" 4 |
|
|
612 | .el .IP "\f(CWEVFLAG_NOTIMERFD\fR" 4 |
|
|
613 | .IX Item "EVFLAG_NOTIMERFD" |
|
|
614 | When this flag is specified, the libev will avoid using a \f(CW\*(C`timerfd\*(C'\fR to |
|
|
615 | detect time jumps. It will still be able to detect time jumps, but takes |
|
|
616 | longer and has a lower accuracy in doing so, but saves a file descriptor |
|
|
617 | per loop. |
567 | .Sp |
618 | .Sp |
568 | This flag's behaviour will become the default in future versions of libev. |
619 | The current implementation only tries to use a \f(CW\*(C`timerfd\*(C'\fR when the first |
|
|
620 | \&\f(CW\*(C`ev_periodic\*(C'\fR watcher is started and falls back on other methods if it |
|
|
621 | cannot be created, but this behaviour might change in the future. |
569 | .ie n .IP """EVBACKEND_SELECT"" (value 1, portable select backend)" 4 |
622 | .ie n .IP """EVBACKEND_SELECT"" (value 1, portable select backend)" 4 |
570 | .el .IP "\f(CWEVBACKEND_SELECT\fR (value 1, portable select backend)" 4 |
623 | .el .IP "\f(CWEVBACKEND_SELECT\fR (value 1, portable select backend)" 4 |
571 | .IX Item "EVBACKEND_SELECT (value 1, portable select backend)" |
624 | .IX Item "EVBACKEND_SELECT (value 1, portable select backend)" |
572 | This is your standard \fIselect\fR\|(2) backend. Not \fIcompletely\fR standard, as |
625 | This is your standard \fBselect\fR\|(2) backend. Not \fIcompletely\fR standard, as |
573 | libev tries to roll its own fd_set with no limits on the number of fds, |
626 | libev tries to roll its own fd_set with no limits on the number of fds, |
574 | but if that fails, expect a fairly low limit on the number of fds when |
627 | but if that fails, expect a fairly low limit on the number of fds when |
575 | using this backend. It doesn't scale too well (O(highest_fd)), but its |
628 | using this backend. It doesn't scale too well (O(highest_fd)), but its |
576 | usually the fastest backend for a low number of (low-numbered :) fds. |
629 | usually the fastest backend for a low number of (low-numbered :) fds. |
577 | .Sp |
630 | .Sp |
… | |
… | |
585 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR to the \f(CW\*(C`readfds\*(C'\fR set and \f(CW\*(C`EV_WRITE\*(C'\fR to the |
638 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR to the \f(CW\*(C`readfds\*(C'\fR set and \f(CW\*(C`EV_WRITE\*(C'\fR to the |
586 | \&\f(CW\*(C`writefds\*(C'\fR set (and to work around Microsoft Windows bugs, also onto the |
639 | \&\f(CW\*(C`writefds\*(C'\fR set (and to work around Microsoft Windows bugs, also onto the |
587 | \&\f(CW\*(C`exceptfds\*(C'\fR set on that platform). |
640 | \&\f(CW\*(C`exceptfds\*(C'\fR set on that platform). |
588 | .ie n .IP """EVBACKEND_POLL"" (value 2, poll backend, available everywhere except on windows)" 4 |
641 | .ie n .IP """EVBACKEND_POLL"" (value 2, poll backend, available everywhere except on windows)" 4 |
589 | .el .IP "\f(CWEVBACKEND_POLL\fR (value 2, poll backend, available everywhere except on windows)" 4 |
642 | .el .IP "\f(CWEVBACKEND_POLL\fR (value 2, poll backend, available everywhere except on windows)" 4 |
590 | .IX Item "EVBACKEND_POLL (value 2, poll backend, available everywhere except on windows)" |
643 | .IX Item "EVBACKEND_POLL (value 2, poll backend, available everywhere except on windows)" |
591 | And this is your standard \fIpoll\fR\|(2) backend. It's more complicated |
644 | And this is your standard \fBpoll\fR\|(2) backend. It's more complicated |
592 | than select, but handles sparse fds better and has no artificial |
645 | than select, but handles sparse fds better and has no artificial |
593 | limit on the number of fds you can use (except it will slow down |
646 | limit on the number of fds you can use (except it will slow down |
594 | considerably with a lot of inactive fds). It scales similarly to select, |
647 | considerably with a lot of inactive fds). It scales similarly to select, |
595 | i.e. O(total_fds). See the entry for \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR, above, for |
648 | i.e. O(total_fds). See the entry for \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR, above, for |
596 | performance tips. |
649 | performance tips. |
597 | .Sp |
650 | .Sp |
598 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR to \f(CW\*(C`POLLIN | POLLERR | POLLHUP\*(C'\fR, and |
651 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR to \f(CW\*(C`POLLIN | POLLERR | POLLHUP\*(C'\fR, and |
599 | \&\f(CW\*(C`EV_WRITE\*(C'\fR to \f(CW\*(C`POLLOUT | POLLERR | POLLHUP\*(C'\fR. |
652 | \&\f(CW\*(C`EV_WRITE\*(C'\fR to \f(CW\*(C`POLLOUT | POLLERR | POLLHUP\*(C'\fR. |
600 | .ie n .IP """EVBACKEND_EPOLL"" (value 4, Linux)" 4 |
653 | .ie n .IP """EVBACKEND_EPOLL"" (value 4, Linux)" 4 |
601 | .el .IP "\f(CWEVBACKEND_EPOLL\fR (value 4, Linux)" 4 |
654 | .el .IP "\f(CWEVBACKEND_EPOLL\fR (value 4, Linux)" 4 |
602 | .IX Item "EVBACKEND_EPOLL (value 4, Linux)" |
655 | .IX Item "EVBACKEND_EPOLL (value 4, Linux)" |
603 | Use the linux-specific \fIepoll\fR\|(7) interface (for both pre\- and post\-2.6.9 |
656 | Use the Linux-specific \fBepoll\fR\|(7) interface (for both pre\- and post\-2.6.9 |
604 | kernels). |
657 | kernels). |
605 | .Sp |
658 | .Sp |
606 | For few fds, this backend is a bit little slower than poll and select, |
659 | For few fds, this backend is a bit little slower than poll and select, but |
607 | but it scales phenomenally better. While poll and select usually scale |
660 | it scales phenomenally better. While poll and select usually scale like |
608 | like O(total_fds) where n is the total number of fds (or the highest fd), |
661 | O(total_fds) where total_fds is the total number of fds (or the highest |
609 | epoll scales either O(1) or O(active_fds). |
662 | fd), epoll scales either O(1) or O(active_fds). |
610 | .Sp |
663 | .Sp |
611 | The epoll mechanism deserves honorable mention as the most misdesigned |
664 | The epoll mechanism deserves honorable mention as the most misdesigned |
612 | of the more advanced event mechanisms: mere annoyances include silently |
665 | of the more advanced event mechanisms: mere annoyances include silently |
613 | dropping file descriptors, requiring a system call per change per file |
666 | dropping file descriptors, requiring a system call per change per file |
614 | descriptor (and unnecessary guessing of parameters), problems with dup, |
667 | descriptor (and unnecessary guessing of parameters), problems with dup, |
… | |
… | |
617 | 0.1ms) and so on. The biggest issue is fork races, however \- if a program |
670 | 0.1ms) and so on. The biggest issue is fork races, however \- if a program |
618 | forks then \fIboth\fR parent and child process have to recreate the epoll |
671 | forks then \fIboth\fR parent and child process have to recreate the epoll |
619 | set, which can take considerable time (one syscall per file descriptor) |
672 | set, which can take considerable time (one syscall per file descriptor) |
620 | and is of course hard to detect. |
673 | and is of course hard to detect. |
621 | .Sp |
674 | .Sp |
622 | Epoll is also notoriously buggy \- embedding epoll fds \fIshould\fR work, but |
675 | Epoll is also notoriously buggy \- embedding epoll fds \fIshould\fR work, |
623 | of course \fIdoesn't\fR, and epoll just loves to report events for totally |
676 | but of course \fIdoesn't\fR, and epoll just loves to report events for |
624 | \&\fIdifferent\fR file descriptors (even already closed ones, so one cannot |
677 | totally \fIdifferent\fR file descriptors (even already closed ones, so |
625 | even remove them from the set) than registered in the set (especially |
678 | one cannot even remove them from the set) than registered in the set |
626 | on \s-1SMP\s0 systems). Libev tries to counter these spurious notifications by |
679 | (especially on \s-1SMP\s0 systems). Libev tries to counter these spurious |
627 | employing an additional generation counter and comparing that against the |
680 | notifications by employing an additional generation counter and comparing |
628 | events to filter out spurious ones, recreating the set when required. Last |
681 | that against the events to filter out spurious ones, recreating the set |
|
|
682 | when required. Epoll also erroneously rounds down timeouts, but gives you |
|
|
683 | no way to know when and by how much, so sometimes you have to busy-wait |
|
|
684 | because epoll returns immediately despite a nonzero timeout. And last |
629 | not least, it also refuses to work with some file descriptors which work |
685 | not least, it also refuses to work with some file descriptors which work |
630 | perfectly fine with \f(CW\*(C`select\*(C'\fR (files, many character devices...). |
686 | perfectly fine with \f(CW\*(C`select\*(C'\fR (files, many character devices...). |
631 | .Sp |
687 | .Sp |
632 | Epoll is truly the train wreck analog among event poll mechanisms, |
688 | Epoll is truly the train wreck among event poll mechanisms, a frankenpoll, |
633 | a frankenpoll, cobbled together in a hurry, no thought to design or |
689 | cobbled together in a hurry, no thought to design or interaction with |
634 | interaction with others. |
690 | others. Oh, the pain, will it ever stop... |
635 | .Sp |
691 | .Sp |
636 | While stopping, setting and starting an I/O watcher in the same iteration |
692 | While stopping, setting and starting an I/O watcher in the same iteration |
637 | will result in some caching, there is still a system call per such |
693 | will result in some caching, there is still a system call per such |
638 | incident (because the same \fIfile descriptor\fR could point to a different |
694 | incident (because the same \fIfile descriptor\fR could point to a different |
639 | \&\fIfile description\fR now), so its best to avoid that. Also, \f(CW\*(C`dup ()\*(C'\fR'ed |
695 | \&\fIfile description\fR now), so its best to avoid that. Also, \f(CW\*(C`dup ()\*(C'\fR'ed |
… | |
… | |
651 | All this means that, in practice, \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR can be as fast or |
707 | All this means that, in practice, \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR can be as fast or |
652 | faster than epoll for maybe up to a hundred file descriptors, depending on |
708 | faster than epoll for maybe up to a hundred file descriptors, depending on |
653 | the usage. So sad. |
709 | the usage. So sad. |
654 | .Sp |
710 | .Sp |
655 | While nominally embeddable in other event loops, this feature is broken in |
711 | While nominally embeddable in other event loops, this feature is broken in |
656 | all kernel versions tested so far. |
712 | a lot of kernel revisions, but probably(!) works in current versions. |
|
|
713 | .Sp |
|
|
714 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR and \f(CW\*(C`EV_WRITE\*(C'\fR in the same way as |
|
|
715 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
|
|
716 | .ie n .IP """EVBACKEND_LINUXAIO"" (value 64, Linux)" 4 |
|
|
717 | .el .IP "\f(CWEVBACKEND_LINUXAIO\fR (value 64, Linux)" 4 |
|
|
718 | .IX Item "EVBACKEND_LINUXAIO (value 64, Linux)" |
|
|
719 | Use the Linux-specific Linux \s-1AIO\s0 (\fInot\fR \f(CWaio(7)\fR but \f(CWio_submit(2)\fR) event interface available in post\-4.18 kernels (but libev |
|
|
720 | only tries to use it in 4.19+). |
|
|
721 | .Sp |
|
|
722 | This is another Linux train wreck of an event interface. |
|
|
723 | .Sp |
|
|
724 | If this backend works for you (as of this writing, it was very |
|
|
725 | experimental), it is the best event interface available on Linux and might |
|
|
726 | be well worth enabling it \- if it isn't available in your kernel this will |
|
|
727 | be detected and this backend will be skipped. |
|
|
728 | .Sp |
|
|
729 | This backend can batch oneshot requests and supports a user-space ring |
|
|
730 | buffer to receive events. It also doesn't suffer from most of the design |
|
|
731 | problems of epoll (such as not being able to remove event sources from |
|
|
732 | the epoll set), and generally sounds too good to be true. Because, this |
|
|
733 | being the Linux kernel, of course it suffers from a whole new set of |
|
|
734 | limitations, forcing you to fall back to epoll, inheriting all its design |
|
|
735 | issues. |
|
|
736 | .Sp |
|
|
737 | For one, it is not easily embeddable (but probably could be done using |
|
|
738 | an event fd at some extra overhead). It also is subject to a system wide |
|
|
739 | limit that can be configured in \fI/proc/sys/fs/aio\-max\-nr\fR. If no \s-1AIO\s0 |
|
|
740 | requests are left, this backend will be skipped during initialisation, and |
|
|
741 | will switch to epoll when the loop is active. |
|
|
742 | .Sp |
|
|
743 | Most problematic in practice, however, is that not all file descriptors |
|
|
744 | work with it. For example, in Linux 5.1, \s-1TCP\s0 sockets, pipes, event fds, |
|
|
745 | files, \fI/dev/null\fR and many others are supported, but ttys do not work |
|
|
746 | properly (a known bug that the kernel developers don't care about, see |
|
|
747 | <https://lore.kernel.org/patchwork/patch/1047453/>), so this is not |
|
|
748 | (yet?) a generic event polling interface. |
|
|
749 | .Sp |
|
|
750 | Overall, it seems the Linux developers just don't want it to have a |
|
|
751 | generic event handling mechanism other than \f(CW\*(C`select\*(C'\fR or \f(CW\*(C`poll\*(C'\fR. |
|
|
752 | .Sp |
|
|
753 | To work around all these problem, the current version of libev uses its |
|
|
754 | epoll backend as a fallback for file descriptor types that do not work. Or |
|
|
755 | falls back completely to epoll if the kernel acts up. |
657 | .Sp |
756 | .Sp |
658 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR and \f(CW\*(C`EV_WRITE\*(C'\fR in the same way as |
757 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR and \f(CW\*(C`EV_WRITE\*(C'\fR in the same way as |
659 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
758 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
660 | .ie n .IP """EVBACKEND_KQUEUE"" (value 8, most \s-1BSD\s0 clones)" 4 |
759 | .ie n .IP """EVBACKEND_KQUEUE"" (value 8, most \s-1BSD\s0 clones)" 4 |
661 | .el .IP "\f(CWEVBACKEND_KQUEUE\fR (value 8, most \s-1BSD\s0 clones)" 4 |
760 | .el .IP "\f(CWEVBACKEND_KQUEUE\fR (value 8, most \s-1BSD\s0 clones)" 4 |
662 | .IX Item "EVBACKEND_KQUEUE (value 8, most BSD clones)" |
761 | .IX Item "EVBACKEND_KQUEUE (value 8, most BSD clones)" |
663 | Kqueue deserves special mention, as at the time of this writing, it |
762 | Kqueue deserves special mention, as at the time this backend was |
664 | was broken on all BSDs except NetBSD (usually it doesn't work reliably |
763 | implemented, it was broken on all BSDs except NetBSD (usually it doesn't |
665 | with anything but sockets and pipes, except on Darwin, where of course |
764 | work reliably with anything but sockets and pipes, except on Darwin, |
666 | it's completely useless). Unlike epoll, however, whose brokenness |
765 | where of course it's completely useless). Unlike epoll, however, whose |
667 | is by design, these kqueue bugs can (and eventually will) be fixed |
766 | brokenness is by design, these kqueue bugs can be (and mostly have been) |
668 | without \s-1API\s0 changes to existing programs. For this reason it's not being |
767 | fixed without \s-1API\s0 changes to existing programs. For this reason it's not |
669 | \&\*(L"auto-detected\*(R" unless you explicitly specify it in the flags (i.e. using |
768 | being \*(L"auto-detected\*(R" on all platforms unless you explicitly specify it |
670 | \&\f(CW\*(C`EVBACKEND_KQUEUE\*(C'\fR) or libev was compiled on a known-to-be-good (\-enough) |
769 | in the flags (i.e. using \f(CW\*(C`EVBACKEND_KQUEUE\*(C'\fR) or libev was compiled on a |
671 | system like NetBSD. |
770 | known-to-be-good (\-enough) system like NetBSD. |
672 | .Sp |
771 | .Sp |
673 | You still can embed kqueue into a normal poll or select backend and use it |
772 | You still can embed kqueue into a normal poll or select backend and use it |
674 | only for sockets (after having made sure that sockets work with kqueue on |
773 | only for sockets (after having made sure that sockets work with kqueue on |
675 | the target platform). See \f(CW\*(C`ev_embed\*(C'\fR watchers for more info. |
774 | the target platform). See \f(CW\*(C`ev_embed\*(C'\fR watchers for more info. |
676 | .Sp |
775 | .Sp |
677 | It scales in the same way as the epoll backend, but the interface to the |
776 | It scales in the same way as the epoll backend, but the interface to the |
678 | kernel is more efficient (which says nothing about its actual speed, of |
777 | kernel is more efficient (which says nothing about its actual speed, of |
679 | course). While stopping, setting and starting an I/O watcher does never |
778 | course). While stopping, setting and starting an I/O watcher does never |
680 | cause an extra system call as with \f(CW\*(C`EVBACKEND_EPOLL\*(C'\fR, it still adds up to |
779 | cause an extra system call as with \f(CW\*(C`EVBACKEND_EPOLL\*(C'\fR, it still adds up to |
681 | two event changes per incident. Support for \f(CW\*(C`fork ()\*(C'\fR is very bad (but |
780 | two event changes per incident. Support for \f(CW\*(C`fork ()\*(C'\fR is very bad (you |
682 | sane, unlike epoll) and it drops fds silently in similarly hard-to-detect |
781 | might have to leak fds on fork, but it's more sane than epoll) and it |
683 | cases |
782 | drops fds silently in similarly hard-to-detect cases. |
684 | .Sp |
783 | .Sp |
685 | This backend usually performs well under most conditions. |
784 | This backend usually performs well under most conditions. |
686 | .Sp |
785 | .Sp |
687 | While nominally embeddable in other event loops, this doesn't work |
786 | While nominally embeddable in other event loops, this doesn't work |
688 | everywhere, so you might need to test for this. And since it is broken |
787 | everywhere, so you might need to test for this. And since it is broken |
689 | almost everywhere, you should only use it when you have a lot of sockets |
788 | almost everywhere, you should only use it when you have a lot of sockets |
690 | (for which it usually works), by embedding it into another event loop |
789 | (for which it usually works), by embedding it into another event loop |
691 | (e.g. \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or \f(CW\*(C`EVBACKEND_POLL\*(C'\fR (but \f(CW\*(C`poll\*(C'\fR is of course |
790 | (e.g. \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or \f(CW\*(C`EVBACKEND_POLL\*(C'\fR (but \f(CW\*(C`poll\*(C'\fR is of course |
692 | also broken on \s-1OS\s0 X)) and, did I mention it, using it only for sockets. |
791 | also broken on \s-1OS X\s0)) and, did I mention it, using it only for sockets. |
693 | .Sp |
792 | .Sp |
694 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR into an \f(CW\*(C`EVFILT_READ\*(C'\fR kevent with |
793 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR into an \f(CW\*(C`EVFILT_READ\*(C'\fR kevent with |
695 | \&\f(CW\*(C`NOTE_EOF\*(C'\fR, and \f(CW\*(C`EV_WRITE\*(C'\fR into an \f(CW\*(C`EVFILT_WRITE\*(C'\fR kevent with |
794 | \&\f(CW\*(C`NOTE_EOF\*(C'\fR, and \f(CW\*(C`EV_WRITE\*(C'\fR into an \f(CW\*(C`EVFILT_WRITE\*(C'\fR kevent with |
696 | \&\f(CW\*(C`NOTE_EOF\*(C'\fR. |
795 | \&\f(CW\*(C`NOTE_EOF\*(C'\fR. |
697 | .ie n .IP """EVBACKEND_DEVPOLL"" (value 16, Solaris 8)" 4 |
796 | .ie n .IP """EVBACKEND_DEVPOLL"" (value 16, Solaris 8)" 4 |
… | |
… | |
701 | implementation). According to reports, \f(CW\*(C`/dev/poll\*(C'\fR only supports sockets |
800 | implementation). According to reports, \f(CW\*(C`/dev/poll\*(C'\fR only supports sockets |
702 | and is not embeddable, which would limit the usefulness of this backend |
801 | and is not embeddable, which would limit the usefulness of this backend |
703 | immensely. |
802 | immensely. |
704 | .ie n .IP """EVBACKEND_PORT"" (value 32, Solaris 10)" 4 |
803 | .ie n .IP """EVBACKEND_PORT"" (value 32, Solaris 10)" 4 |
705 | .el .IP "\f(CWEVBACKEND_PORT\fR (value 32, Solaris 10)" 4 |
804 | .el .IP "\f(CWEVBACKEND_PORT\fR (value 32, Solaris 10)" 4 |
706 | .IX Item "EVBACKEND_PORT (value 32, Solaris 10)" |
805 | .IX Item "EVBACKEND_PORT (value 32, Solaris 10)" |
707 | This uses the Solaris 10 event port mechanism. As with everything on Solaris, |
806 | This uses the Solaris 10 event port mechanism. As with everything on Solaris, |
708 | it's really slow, but it still scales very well (O(active_fds)). |
807 | it's really slow, but it still scales very well (O(active_fds)). |
709 | .Sp |
808 | .Sp |
710 | While this backend scales well, it requires one system call per active |
809 | While this backend scales well, it requires one system call per active |
711 | file descriptor per loop iteration. For small and medium numbers of file |
810 | file descriptor per loop iteration. For small and medium numbers of file |
… | |
… | |
717 | among the OS-specific backends (I vastly prefer correctness over speed |
816 | among the OS-specific backends (I vastly prefer correctness over speed |
718 | hacks). |
817 | hacks). |
719 | .Sp |
818 | .Sp |
720 | On the negative side, the interface is \fIbizarre\fR \- so bizarre that |
819 | On the negative side, the interface is \fIbizarre\fR \- so bizarre that |
721 | even sun itself gets it wrong in their code examples: The event polling |
820 | even sun itself gets it wrong in their code examples: The event polling |
722 | function sometimes returning events to the caller even though an error |
821 | function sometimes returns events to the caller even though an error |
723 | occurred, but with no indication whether it has done so or not (yes, it's |
822 | occurred, but with no indication whether it has done so or not (yes, it's |
724 | even documented that way) \- deadly for edge-triggered interfaces where |
823 | even documented that way) \- deadly for edge-triggered interfaces where you |
725 | you absolutely have to know whether an event occurred or not because you |
824 | absolutely have to know whether an event occurred or not because you have |
726 | have to re-arm the watcher. |
825 | to re-arm the watcher. |
727 | .Sp |
826 | .Sp |
728 | Fortunately libev seems to be able to work around these idiocies. |
827 | Fortunately libev seems to be able to work around these idiocies. |
729 | .Sp |
828 | .Sp |
730 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR and \f(CW\*(C`EV_WRITE\*(C'\fR in the same way as |
829 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR and \f(CW\*(C`EV_WRITE\*(C'\fR in the same way as |
731 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
830 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
… | |
… | |
765 | used if available. |
864 | used if available. |
766 | .Sp |
865 | .Sp |
767 | .Vb 1 |
866 | .Vb 1 |
768 | \& struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_KQUEUE); |
867 | \& struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_KQUEUE); |
769 | .Ve |
868 | .Ve |
|
|
869 | .Sp |
|
|
870 | Example: Similarly, on linux, you mgiht want to take advantage of the |
|
|
871 | linux aio backend if possible, but fall back to something else if that |
|
|
872 | isn't available. |
|
|
873 | .Sp |
|
|
874 | .Vb 1 |
|
|
875 | \& struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_LINUXAIO); |
|
|
876 | .Ve |
770 | .RE |
877 | .RE |
771 | .IP "ev_loop_destroy (loop)" 4 |
878 | .IP "ev_loop_destroy (loop)" 4 |
772 | .IX Item "ev_loop_destroy (loop)" |
879 | .IX Item "ev_loop_destroy (loop)" |
773 | Destroys an event loop object (frees all memory and kernel state |
880 | Destroys an event loop object (frees all memory and kernel state |
774 | etc.). None of the active event watchers will be stopped in the normal |
881 | etc.). None of the active event watchers will be stopped in the normal |
… | |
… | |
790 | except in the rare occasion where you really need to free its resources. |
897 | except in the rare occasion where you really need to free its resources. |
791 | If you need dynamically allocated loops it is better to use \f(CW\*(C`ev_loop_new\*(C'\fR |
898 | If you need dynamically allocated loops it is better to use \f(CW\*(C`ev_loop_new\*(C'\fR |
792 | and \f(CW\*(C`ev_loop_destroy\*(C'\fR. |
899 | and \f(CW\*(C`ev_loop_destroy\*(C'\fR. |
793 | .IP "ev_loop_fork (loop)" 4 |
900 | .IP "ev_loop_fork (loop)" 4 |
794 | .IX Item "ev_loop_fork (loop)" |
901 | .IX Item "ev_loop_fork (loop)" |
795 | This function sets a flag that causes subsequent \f(CW\*(C`ev_run\*(C'\fR iterations to |
902 | This function sets a flag that causes subsequent \f(CW\*(C`ev_run\*(C'\fR iterations |
796 | reinitialise the kernel state for backends that have one. Despite the |
903 | to reinitialise the kernel state for backends that have one. Despite |
797 | name, you can call it anytime, but it makes most sense after forking, in |
904 | the name, you can call it anytime you are allowed to start or stop |
798 | the child process. You \fImust\fR call it (or use \f(CW\*(C`EVFLAG_FORKCHECK\*(C'\fR) in the |
905 | watchers (except inside an \f(CW\*(C`ev_prepare\*(C'\fR callback), but it makes most |
799 | child before resuming or calling \f(CW\*(C`ev_run\*(C'\fR. |
906 | sense after forking, in the child process. You \fImust\fR call it (or use |
|
|
907 | \&\f(CW\*(C`EVFLAG_FORKCHECK\*(C'\fR) in the child before resuming or calling \f(CW\*(C`ev_run\*(C'\fR. |
800 | .Sp |
908 | .Sp |
|
|
909 | In addition, if you want to reuse a loop (via this function or |
|
|
910 | \&\f(CW\*(C`EVFLAG_FORKCHECK\*(C'\fR), you \fIalso\fR have to ignore \f(CW\*(C`SIGPIPE\*(C'\fR. |
|
|
911 | .Sp |
801 | Again, you \fIhave\fR to call it on \fIany\fR loop that you want to re-use after |
912 | Again, you \fIhave\fR to call it on \fIany\fR loop that you want to re-use after |
802 | a fork, \fIeven if you do not plan to use the loop in the parent\fR. This is |
913 | a fork, \fIeven if you do not plan to use the loop in the parent\fR. This is |
803 | because some kernel interfaces *cough* \fIkqueue\fR *cough* do funny things |
914 | because some kernel interfaces *cough* \fIkqueue\fR *cough* do funny things |
804 | during fork. |
915 | during fork. |
805 | .Sp |
916 | .Sp |
806 | On the other hand, you only need to call this function in the child |
917 | On the other hand, you only need to call this function in the child |
… | |
… | |
900 | given loop other than \f(CW\*(C`ev_resume\*(C'\fR, and you \fBmust not\fR call \f(CW\*(C`ev_resume\*(C'\fR |
1011 | given loop other than \f(CW\*(C`ev_resume\*(C'\fR, and you \fBmust not\fR call \f(CW\*(C`ev_resume\*(C'\fR |
901 | without a previous call to \f(CW\*(C`ev_suspend\*(C'\fR. |
1012 | without a previous call to \f(CW\*(C`ev_suspend\*(C'\fR. |
902 | .Sp |
1013 | .Sp |
903 | Calling \f(CW\*(C`ev_suspend\*(C'\fR/\f(CW\*(C`ev_resume\*(C'\fR has the side effect of updating the |
1014 | Calling \f(CW\*(C`ev_suspend\*(C'\fR/\f(CW\*(C`ev_resume\*(C'\fR has the side effect of updating the |
904 | event loop time (see \f(CW\*(C`ev_now_update\*(C'\fR). |
1015 | event loop time (see \f(CW\*(C`ev_now_update\*(C'\fR). |
905 | .IP "ev_run (loop, int flags)" 4 |
1016 | .IP "bool ev_run (loop, int flags)" 4 |
906 | .IX Item "ev_run (loop, int flags)" |
1017 | .IX Item "bool ev_run (loop, int flags)" |
907 | Finally, this is it, the event handler. This function usually is called |
1018 | Finally, this is it, the event handler. This function usually is called |
908 | after you have initialised all your watchers and you want to start |
1019 | after you have initialised all your watchers and you want to start |
909 | handling events. It will ask the operating system for any new events, call |
1020 | handling events. It will ask the operating system for any new events, call |
910 | the watcher callbacks, an then repeat the whole process indefinitely: This |
1021 | the watcher callbacks, and then repeat the whole process indefinitely: This |
911 | is why event loops are called \fIloops\fR. |
1022 | is why event loops are called \fIloops\fR. |
912 | .Sp |
1023 | .Sp |
913 | If the flags argument is specified as \f(CW0\fR, it will keep handling events |
1024 | If the flags argument is specified as \f(CW0\fR, it will keep handling events |
914 | until either no event watchers are active anymore or \f(CW\*(C`ev_break\*(C'\fR was |
1025 | until either no event watchers are active anymore or \f(CW\*(C`ev_break\*(C'\fR was |
915 | called. |
1026 | called. |
|
|
1027 | .Sp |
|
|
1028 | The return value is false if there are no more active watchers (which |
|
|
1029 | usually means \*(L"all jobs done\*(R" or \*(L"deadlock\*(R"), and true in all other cases |
|
|
1030 | (which usually means " you should call \f(CW\*(C`ev_run\*(C'\fR again"). |
916 | .Sp |
1031 | .Sp |
917 | Please note that an explicit \f(CW\*(C`ev_break\*(C'\fR is usually better than |
1032 | Please note that an explicit \f(CW\*(C`ev_break\*(C'\fR is usually better than |
918 | relying on all watchers to be stopped when deciding when a program has |
1033 | relying on all watchers to be stopped when deciding when a program has |
919 | finished (especially in interactive programs), but having a program |
1034 | finished (especially in interactive programs), but having a program |
920 | that automatically loops as long as it has to and no longer by virtue |
1035 | that automatically loops as long as it has to and no longer by virtue |
921 | of relying on its watchers stopping correctly, that is truly a thing of |
1036 | of relying on its watchers stopping correctly, that is truly a thing of |
922 | beauty. |
1037 | beauty. |
923 | .Sp |
1038 | .Sp |
924 | This function is also \fImostly\fR exception-safe \- you can break out of |
1039 | This function is \fImostly\fR exception-safe \- you can break out of a |
925 | a \f(CW\*(C`ev_run\*(C'\fR call by calling \f(CW\*(C`longjmp\*(C'\fR in a callback, throwing a \*(C+ |
1040 | \&\f(CW\*(C`ev_run\*(C'\fR call by calling \f(CW\*(C`longjmp\*(C'\fR in a callback, throwing a \*(C+ |
926 | exception and so on. This does not decrement the \f(CW\*(C`ev_depth\*(C'\fR value, nor |
1041 | exception and so on. This does not decrement the \f(CW\*(C`ev_depth\*(C'\fR value, nor |
927 | will it clear any outstanding \f(CW\*(C`EVBREAK_ONE\*(C'\fR breaks. |
1042 | will it clear any outstanding \f(CW\*(C`EVBREAK_ONE\*(C'\fR breaks. |
928 | .Sp |
1043 | .Sp |
929 | A flags value of \f(CW\*(C`EVRUN_NOWAIT\*(C'\fR will look for new events, will handle |
1044 | A flags value of \f(CW\*(C`EVRUN_NOWAIT\*(C'\fR will look for new events, will handle |
930 | those events and any already outstanding ones, but will not wait and |
1045 | those events and any already outstanding ones, but will not wait and |
… | |
… | |
942 | This is useful if you are waiting for some external event in conjunction |
1057 | This is useful if you are waiting for some external event in conjunction |
943 | with something not expressible using other libev watchers (i.e. "roll your |
1058 | with something not expressible using other libev watchers (i.e. "roll your |
944 | own \f(CW\*(C`ev_run\*(C'\fR"). However, a pair of \f(CW\*(C`ev_prepare\*(C'\fR/\f(CW\*(C`ev_check\*(C'\fR watchers is |
1059 | own \f(CW\*(C`ev_run\*(C'\fR"). However, a pair of \f(CW\*(C`ev_prepare\*(C'\fR/\f(CW\*(C`ev_check\*(C'\fR watchers is |
945 | usually a better approach for this kind of thing. |
1060 | usually a better approach for this kind of thing. |
946 | .Sp |
1061 | .Sp |
947 | Here are the gory details of what \f(CW\*(C`ev_run\*(C'\fR does: |
1062 | Here are the gory details of what \f(CW\*(C`ev_run\*(C'\fR does (this is for your |
|
|
1063 | understanding, not a guarantee that things will work exactly like this in |
|
|
1064 | future versions): |
948 | .Sp |
1065 | .Sp |
949 | .Vb 10 |
1066 | .Vb 10 |
950 | \& \- Increment loop depth. |
1067 | \& \- Increment loop depth. |
951 | \& \- Reset the ev_break status. |
1068 | \& \- Reset the ev_break status. |
952 | \& \- Before the first iteration, call any pending watchers. |
1069 | \& \- Before the first iteration, call any pending watchers. |
… | |
… | |
970 | \& \- Queue all expired timers. |
1087 | \& \- Queue all expired timers. |
971 | \& \- Queue all expired periodics. |
1088 | \& \- Queue all expired periodics. |
972 | \& \- Queue all idle watchers with priority higher than that of pending events. |
1089 | \& \- Queue all idle watchers with priority higher than that of pending events. |
973 | \& \- Queue all check watchers. |
1090 | \& \- Queue all check watchers. |
974 | \& \- Call all queued watchers in reverse order (i.e. check watchers first). |
1091 | \& \- Call all queued watchers in reverse order (i.e. check watchers first). |
975 | \& Signals and child watchers are implemented as I/O watchers, and will |
1092 | \& Signals, async and child watchers are implemented as I/O watchers, and |
976 | \& be handled here by queueing them when their watcher gets executed. |
1093 | \& will be handled here by queueing them when their watcher gets executed. |
977 | \& \- If ev_break has been called, or EVRUN_ONCE or EVRUN_NOWAIT |
1094 | \& \- If ev_break has been called, or EVRUN_ONCE or EVRUN_NOWAIT |
978 | \& were used, or there are no active watchers, goto FINISH, otherwise |
1095 | \& were used, or there are no active watchers, goto FINISH, otherwise |
979 | \& continue with step LOOP. |
1096 | \& continue with step LOOP. |
980 | \& FINISH: |
1097 | \& FINISH: |
981 | \& \- Reset the ev_break status iff it was EVBREAK_ONE. |
1098 | \& \- Reset the ev_break status iff it was EVBREAK_ONE. |
… | |
… | |
1067 | overhead for the actual polling but can deliver many events at once. |
1184 | overhead for the actual polling but can deliver many events at once. |
1068 | .Sp |
1185 | .Sp |
1069 | By setting a higher \fIio collect interval\fR you allow libev to spend more |
1186 | By setting a higher \fIio collect interval\fR you allow libev to spend more |
1070 | time collecting I/O events, so you can handle more events per iteration, |
1187 | time collecting I/O events, so you can handle more events per iteration, |
1071 | at the cost of increasing latency. Timeouts (both \f(CW\*(C`ev_periodic\*(C'\fR and |
1188 | at the cost of increasing latency. Timeouts (both \f(CW\*(C`ev_periodic\*(C'\fR and |
1072 | \&\f(CW\*(C`ev_timer\*(C'\fR) will be not affected. Setting this to a non-null value will |
1189 | \&\f(CW\*(C`ev_timer\*(C'\fR) will not be affected. Setting this to a non-null value will |
1073 | introduce an additional \f(CW\*(C`ev_sleep ()\*(C'\fR call into most loop iterations. The |
1190 | introduce an additional \f(CW\*(C`ev_sleep ()\*(C'\fR call into most loop iterations. The |
1074 | sleep time ensures that libev will not poll for I/O events more often then |
1191 | sleep time ensures that libev will not poll for I/O events more often then |
1075 | once per this interval, on average. |
1192 | once per this interval, on average (as long as the host time resolution is |
|
|
1193 | good enough). |
1076 | .Sp |
1194 | .Sp |
1077 | Likewise, by setting a higher \fItimeout collect interval\fR you allow libev |
1195 | Likewise, by setting a higher \fItimeout collect interval\fR you allow libev |
1078 | to spend more time collecting timeouts, at the expense of increased |
1196 | to spend more time collecting timeouts, at the expense of increased |
1079 | latency/jitter/inexactness (the watcher callback will be called |
1197 | latency/jitter/inexactness (the watcher callback will be called |
1080 | later). \f(CW\*(C`ev_io\*(C'\fR watchers will not be affected. Setting this to a non-null |
1198 | later). \f(CW\*(C`ev_io\*(C'\fR watchers will not be affected. Setting this to a non-null |
… | |
… | |
1124 | this callback instead. This is useful, for example, when you want to |
1242 | this callback instead. This is useful, for example, when you want to |
1125 | invoke the actual watchers inside another context (another thread etc.). |
1243 | invoke the actual watchers inside another context (another thread etc.). |
1126 | .Sp |
1244 | .Sp |
1127 | If you want to reset the callback, use \f(CW\*(C`ev_invoke_pending\*(C'\fR as new |
1245 | If you want to reset the callback, use \f(CW\*(C`ev_invoke_pending\*(C'\fR as new |
1128 | callback. |
1246 | callback. |
1129 | .IP "ev_set_loop_release_cb (loop, void (*release)(\s-1EV_P\s0), void (*acquire)(\s-1EV_P\s0))" 4 |
1247 | .IP "ev_set_loop_release_cb (loop, void (*release)(\s-1EV_P\s0) throw (), void (*acquire)(\s-1EV_P\s0) throw ())" 4 |
1130 | .IX Item "ev_set_loop_release_cb (loop, void (*release)(EV_P), void (*acquire)(EV_P))" |
1248 | .IX Item "ev_set_loop_release_cb (loop, void (*release)(EV_P) throw (), void (*acquire)(EV_P) throw ())" |
1131 | Sometimes you want to share the same loop between multiple threads. This |
1249 | Sometimes you want to share the same loop between multiple threads. This |
1132 | can be done relatively simply by putting mutex_lock/unlock calls around |
1250 | can be done relatively simply by putting mutex_lock/unlock calls around |
1133 | each call to a libev function. |
1251 | each call to a libev function. |
1134 | .Sp |
1252 | .Sp |
1135 | However, \f(CW\*(C`ev_run\*(C'\fR can run an indefinite time, so it is not feasible |
1253 | However, \f(CW\*(C`ev_run\*(C'\fR can run an indefinite time, so it is not feasible |
1136 | to wait for it to return. One way around this is to wake up the event |
1254 | to wait for it to return. One way around this is to wake up the event |
1137 | loop via \f(CW\*(C`ev_break\*(C'\fR and \f(CW\*(C`av_async_send\*(C'\fR, another way is to set these |
1255 | loop via \f(CW\*(C`ev_break\*(C'\fR and \f(CW\*(C`ev_async_send\*(C'\fR, another way is to set these |
1138 | \&\fIrelease\fR and \fIacquire\fR callbacks on the loop. |
1256 | \&\fIrelease\fR and \fIacquire\fR callbacks on the loop. |
1139 | .Sp |
1257 | .Sp |
1140 | When set, then \f(CW\*(C`release\*(C'\fR will be called just before the thread is |
1258 | When set, then \f(CW\*(C`release\*(C'\fR will be called just before the thread is |
1141 | suspended waiting for new events, and \f(CW\*(C`acquire\*(C'\fR is called just |
1259 | suspended waiting for new events, and \f(CW\*(C`acquire\*(C'\fR is called just |
1142 | afterwards. |
1260 | afterwards. |
… | |
… | |
1231 | with a watcher-specific start function (\f(CW\*(C`ev_TYPE_start (loop, watcher |
1349 | with a watcher-specific start function (\f(CW\*(C`ev_TYPE_start (loop, watcher |
1232 | *)\*(C'\fR), and you can stop watching for events at any time by calling the |
1350 | *)\*(C'\fR), and you can stop watching for events at any time by calling the |
1233 | corresponding stop function (\f(CW\*(C`ev_TYPE_stop (loop, watcher *)\*(C'\fR. |
1351 | corresponding stop function (\f(CW\*(C`ev_TYPE_stop (loop, watcher *)\*(C'\fR. |
1234 | .PP |
1352 | .PP |
1235 | As long as your watcher is active (has been started but not stopped) you |
1353 | As long as your watcher is active (has been started but not stopped) you |
1236 | must not touch the values stored in it. Most specifically you must never |
1354 | must not touch the values stored in it except when explicitly documented |
1237 | reinitialise it or call its \f(CW\*(C`ev_TYPE_set\*(C'\fR macro. |
1355 | otherwise. Most specifically you must never reinitialise it or call its |
|
|
1356 | \&\f(CW\*(C`ev_TYPE_set\*(C'\fR macro. |
1238 | .PP |
1357 | .PP |
1239 | Each and every callback receives the event loop pointer as first, the |
1358 | Each and every callback receives the event loop pointer as first, the |
1240 | registered watcher structure as second, and a bitset of received events as |
1359 | registered watcher structure as second, and a bitset of received events as |
1241 | third argument. |
1360 | third argument. |
1242 | .PP |
1361 | .PP |
… | |
… | |
1283 | .PD 0 |
1402 | .PD 0 |
1284 | .ie n .IP """EV_CHECK""" 4 |
1403 | .ie n .IP """EV_CHECK""" 4 |
1285 | .el .IP "\f(CWEV_CHECK\fR" 4 |
1404 | .el .IP "\f(CWEV_CHECK\fR" 4 |
1286 | .IX Item "EV_CHECK" |
1405 | .IX Item "EV_CHECK" |
1287 | .PD |
1406 | .PD |
1288 | All \f(CW\*(C`ev_prepare\*(C'\fR watchers are invoked just \fIbefore\fR \f(CW\*(C`ev_run\*(C'\fR starts |
1407 | All \f(CW\*(C`ev_prepare\*(C'\fR watchers are invoked just \fIbefore\fR \f(CW\*(C`ev_run\*(C'\fR starts to |
1289 | to gather new events, and all \f(CW\*(C`ev_check\*(C'\fR watchers are invoked just after |
1408 | gather new events, and all \f(CW\*(C`ev_check\*(C'\fR watchers are queued (not invoked) |
1290 | \&\f(CW\*(C`ev_run\*(C'\fR has gathered them, but before it invokes any callbacks for any |
1409 | just after \f(CW\*(C`ev_run\*(C'\fR has gathered them, but before it queues any callbacks |
|
|
1410 | for any received events. That means \f(CW\*(C`ev_prepare\*(C'\fR watchers are the last |
|
|
1411 | watchers invoked before the event loop sleeps or polls for new events, and |
|
|
1412 | \&\f(CW\*(C`ev_check\*(C'\fR watchers will be invoked before any other watchers of the same |
|
|
1413 | or lower priority within an event loop iteration. |
|
|
1414 | .Sp |
1291 | received events. Callbacks of both watcher types can start and stop as |
1415 | Callbacks of both watcher types can start and stop as many watchers as |
1292 | many watchers as they want, and all of them will be taken into account |
1416 | they want, and all of them will be taken into account (for example, a |
1293 | (for example, a \f(CW\*(C`ev_prepare\*(C'\fR watcher might start an idle watcher to keep |
1417 | \&\f(CW\*(C`ev_prepare\*(C'\fR watcher might start an idle watcher to keep \f(CW\*(C`ev_run\*(C'\fR from |
1294 | \&\f(CW\*(C`ev_run\*(C'\fR from blocking). |
1418 | blocking). |
1295 | .ie n .IP """EV_EMBED""" 4 |
1419 | .ie n .IP """EV_EMBED""" 4 |
1296 | .el .IP "\f(CWEV_EMBED\fR" 4 |
1420 | .el .IP "\f(CWEV_EMBED\fR" 4 |
1297 | .IX Item "EV_EMBED" |
1421 | .IX Item "EV_EMBED" |
1298 | The embedded event loop specified in the \f(CW\*(C`ev_embed\*(C'\fR watcher needs attention. |
1422 | The embedded event loop specified in the \f(CW\*(C`ev_embed\*(C'\fR watcher needs attention. |
1299 | .ie n .IP """EV_FORK""" 4 |
1423 | .ie n .IP """EV_FORK""" 4 |
… | |
… | |
1328 | bug in your program. |
1452 | bug in your program. |
1329 | .Sp |
1453 | .Sp |
1330 | Libev will usually signal a few \*(L"dummy\*(R" events together with an error, for |
1454 | Libev will usually signal a few \*(L"dummy\*(R" events together with an error, for |
1331 | example it might indicate that a fd is readable or writable, and if your |
1455 | example it might indicate that a fd is readable or writable, and if your |
1332 | callbacks is well-written it can just attempt the operation and cope with |
1456 | callbacks is well-written it can just attempt the operation and cope with |
1333 | the error from \fIread()\fR or \fIwrite()\fR. This will not work in multi-threaded |
1457 | the error from \fBread()\fR or \fBwrite()\fR. This will not work in multi-threaded |
1334 | programs, though, as the fd could already be closed and reused for another |
1458 | programs, though, as the fd could already be closed and reused for another |
1335 | thing, so beware. |
1459 | thing, so beware. |
1336 | .SS "\s-1GENERIC\s0 \s-1WATCHER\s0 \s-1FUNCTIONS\s0" |
1460 | .SS "\s-1GENERIC WATCHER FUNCTIONS\s0" |
1337 | .IX Subsection "GENERIC WATCHER FUNCTIONS" |
1461 | .IX Subsection "GENERIC WATCHER FUNCTIONS" |
1338 | .ie n .IP """ev_init"" (ev_TYPE *watcher, callback)" 4 |
1462 | .ie n .IP """ev_init"" (ev_TYPE *watcher, callback)" 4 |
1339 | .el .IP "\f(CWev_init\fR (ev_TYPE *watcher, callback)" 4 |
1463 | .el .IP "\f(CWev_init\fR (ev_TYPE *watcher, callback)" 4 |
1340 | .IX Item "ev_init (ev_TYPE *watcher, callback)" |
1464 | .IX Item "ev_init (ev_TYPE *watcher, callback)" |
1341 | This macro initialises the generic portion of a watcher. The contents |
1465 | This macro initialises the generic portion of a watcher. The contents |
… | |
… | |
1408 | therefore a good idea to always call its \f(CW\*(C`ev_TYPE_stop\*(C'\fR function. |
1532 | therefore a good idea to always call its \f(CW\*(C`ev_TYPE_stop\*(C'\fR function. |
1409 | .IP "bool ev_is_active (ev_TYPE *watcher)" 4 |
1533 | .IP "bool ev_is_active (ev_TYPE *watcher)" 4 |
1410 | .IX Item "bool ev_is_active (ev_TYPE *watcher)" |
1534 | .IX Item "bool ev_is_active (ev_TYPE *watcher)" |
1411 | Returns a true value iff the watcher is active (i.e. it has been started |
1535 | Returns a true value iff the watcher is active (i.e. it has been started |
1412 | and not yet been stopped). As long as a watcher is active you must not modify |
1536 | and not yet been stopped). As long as a watcher is active you must not modify |
1413 | it. |
1537 | it unless documented otherwise. |
1414 | .IP "bool ev_is_pending (ev_TYPE *watcher)" 4 |
1538 | .IP "bool ev_is_pending (ev_TYPE *watcher)" 4 |
1415 | .IX Item "bool ev_is_pending (ev_TYPE *watcher)" |
1539 | .IX Item "bool ev_is_pending (ev_TYPE *watcher)" |
1416 | Returns a true value iff the watcher is pending, (i.e. it has outstanding |
1540 | Returns a true value iff the watcher is pending, (i.e. it has outstanding |
1417 | events but its callback has not yet been invoked). As long as a watcher |
1541 | events but its callback has not yet been invoked). As long as a watcher |
1418 | is pending (but not active) you must not call an init function on it (but |
1542 | is pending (but not active) you must not call an init function on it (but |
… | |
… | |
1420 | make sure the watcher is available to libev (e.g. you cannot \f(CW\*(C`free ()\*(C'\fR |
1544 | make sure the watcher is available to libev (e.g. you cannot \f(CW\*(C`free ()\*(C'\fR |
1421 | it). |
1545 | it). |
1422 | .IP "callback ev_cb (ev_TYPE *watcher)" 4 |
1546 | .IP "callback ev_cb (ev_TYPE *watcher)" 4 |
1423 | .IX Item "callback ev_cb (ev_TYPE *watcher)" |
1547 | .IX Item "callback ev_cb (ev_TYPE *watcher)" |
1424 | Returns the callback currently set on the watcher. |
1548 | Returns the callback currently set on the watcher. |
1425 | .IP "ev_cb_set (ev_TYPE *watcher, callback)" 4 |
1549 | .IP "ev_set_cb (ev_TYPE *watcher, callback)" 4 |
1426 | .IX Item "ev_cb_set (ev_TYPE *watcher, callback)" |
1550 | .IX Item "ev_set_cb (ev_TYPE *watcher, callback)" |
1427 | Change the callback. You can change the callback at virtually any time |
1551 | Change the callback. You can change the callback at virtually any time |
1428 | (modulo threads). |
1552 | (modulo threads). |
1429 | .IP "ev_set_priority (ev_TYPE *watcher, int priority)" 4 |
1553 | .IP "ev_set_priority (ev_TYPE *watcher, int priority)" 4 |
1430 | .IX Item "ev_set_priority (ev_TYPE *watcher, int priority)" |
1554 | .IX Item "ev_set_priority (ev_TYPE *watcher, int priority)" |
1431 | .PD 0 |
1555 | .PD 0 |
… | |
… | |
1449 | or might not have been clamped to the valid range. |
1573 | or might not have been clamped to the valid range. |
1450 | .Sp |
1574 | .Sp |
1451 | The default priority used by watchers when no priority has been set is |
1575 | The default priority used by watchers when no priority has been set is |
1452 | always \f(CW0\fR, which is supposed to not be too high and not be too low :). |
1576 | always \f(CW0\fR, which is supposed to not be too high and not be too low :). |
1453 | .Sp |
1577 | .Sp |
1454 | See \*(L"\s-1WATCHER\s0 \s-1PRIORITY\s0 \s-1MODELS\s0\*(R", below, for a more thorough treatment of |
1578 | See \*(L"\s-1WATCHER PRIORITY MODELS\*(R"\s0, below, for a more thorough treatment of |
1455 | priorities. |
1579 | priorities. |
1456 | .IP "ev_invoke (loop, ev_TYPE *watcher, int revents)" 4 |
1580 | .IP "ev_invoke (loop, ev_TYPE *watcher, int revents)" 4 |
1457 | .IX Item "ev_invoke (loop, ev_TYPE *watcher, int revents)" |
1581 | .IX Item "ev_invoke (loop, ev_TYPE *watcher, int revents)" |
1458 | Invoke the \f(CW\*(C`watcher\*(C'\fR with the given \f(CW\*(C`loop\*(C'\fR and \f(CW\*(C`revents\*(C'\fR. Neither |
1582 | Invoke the \f(CW\*(C`watcher\*(C'\fR with the given \f(CW\*(C`loop\*(C'\fR and \f(CW\*(C`revents\*(C'\fR. Neither |
1459 | \&\f(CW\*(C`loop\*(C'\fR nor \f(CW\*(C`revents\*(C'\fR need to be valid as long as the watcher callback |
1583 | \&\f(CW\*(C`loop\*(C'\fR nor \f(CW\*(C`revents\*(C'\fR need to be valid as long as the watcher callback |
… | |
… | |
1479 | not started in the first place. |
1603 | not started in the first place. |
1480 | .Sp |
1604 | .Sp |
1481 | See also \f(CW\*(C`ev_feed_fd_event\*(C'\fR and \f(CW\*(C`ev_feed_signal_event\*(C'\fR for related |
1605 | See also \f(CW\*(C`ev_feed_fd_event\*(C'\fR and \f(CW\*(C`ev_feed_signal_event\*(C'\fR for related |
1482 | functions that do not need a watcher. |
1606 | functions that do not need a watcher. |
1483 | .PP |
1607 | .PP |
1484 | See also the \*(L"\s-1ASSOCIATING\s0 \s-1CUSTOM\s0 \s-1DATA\s0 \s-1WITH\s0 A \s-1WATCHER\s0\*(R" and \*(L"\s-1BUILDING\s0 \s-1YOUR\s0 |
1608 | See also the \*(L"\s-1ASSOCIATING CUSTOM DATA WITH A WATCHER\*(R"\s0 and \*(L"\s-1BUILDING YOUR |
1485 | \&\s-1OWN\s0 \s-1COMPOSITE\s0 \s-1WATCHERS\s0\*(R" idioms. |
1609 | OWN COMPOSITE WATCHERS\*(R"\s0 idioms. |
1486 | .SS "\s-1WATCHER\s0 \s-1STATES\s0" |
1610 | .SS "\s-1WATCHER STATES\s0" |
1487 | .IX Subsection "WATCHER STATES" |
1611 | .IX Subsection "WATCHER STATES" |
1488 | There are various watcher states mentioned throughout this manual \- |
1612 | There are various watcher states mentioned throughout this manual \- |
1489 | active, pending and so on. In this section these states and the rules to |
1613 | active, pending and so on. In this section these states and the rules to |
1490 | transition between them will be described in more detail \- and while these |
1614 | transition between them will be described in more detail \- and while these |
1491 | rules might look complicated, they usually do \*(L"the right thing\*(R". |
1615 | rules might look complicated, they usually do \*(L"the right thing\*(R". |
1492 | .IP "initialiased" 4 |
1616 | .IP "initialised" 4 |
1493 | .IX Item "initialiased" |
1617 | .IX Item "initialised" |
1494 | Before a watcher can be registered with the event looop it has to be |
1618 | Before a watcher can be registered with the event loop it has to be |
1495 | initialised. This can be done with a call to \f(CW\*(C`ev_TYPE_init\*(C'\fR, or calls to |
1619 | initialised. This can be done with a call to \f(CW\*(C`ev_TYPE_init\*(C'\fR, or calls to |
1496 | \&\f(CW\*(C`ev_init\*(C'\fR followed by the watcher-specific \f(CW\*(C`ev_TYPE_set\*(C'\fR function. |
1620 | \&\f(CW\*(C`ev_init\*(C'\fR followed by the watcher-specific \f(CW\*(C`ev_TYPE_set\*(C'\fR function. |
1497 | .Sp |
1621 | .Sp |
1498 | In this state it is simply some block of memory that is suitable for |
1622 | In this state it is simply some block of memory that is suitable for |
1499 | use in an event loop. It can be moved around, freed, reused etc. at |
1623 | use in an event loop. It can be moved around, freed, reused etc. at |
… | |
… | |
1534 | .Sp |
1658 | .Sp |
1535 | While stopped (and not pending) the watcher is essentially in the |
1659 | While stopped (and not pending) the watcher is essentially in the |
1536 | initialised state, that is, it can be reused, moved, modified in any way |
1660 | initialised state, that is, it can be reused, moved, modified in any way |
1537 | you wish (but when you trash the memory block, you need to \f(CW\*(C`ev_TYPE_init\*(C'\fR |
1661 | you wish (but when you trash the memory block, you need to \f(CW\*(C`ev_TYPE_init\*(C'\fR |
1538 | it again). |
1662 | it again). |
1539 | .SS "\s-1WATCHER\s0 \s-1PRIORITY\s0 \s-1MODELS\s0" |
1663 | .SS "\s-1WATCHER PRIORITY MODELS\s0" |
1540 | .IX Subsection "WATCHER PRIORITY MODELS" |
1664 | .IX Subsection "WATCHER PRIORITY MODELS" |
1541 | Many event loops support \fIwatcher priorities\fR, which are usually small |
1665 | Many event loops support \fIwatcher priorities\fR, which are usually small |
1542 | integers that influence the ordering of event callback invocation |
1666 | integers that influence the ordering of event callback invocation |
1543 | between watchers in some way, all else being equal. |
1667 | between watchers in some way, all else being equal. |
1544 | .PP |
1668 | .PP |
1545 | In libev, Watcher priorities can be set using \f(CW\*(C`ev_set_priority\*(C'\fR. See its |
1669 | In libev, watcher priorities can be set using \f(CW\*(C`ev_set_priority\*(C'\fR. See its |
1546 | description for the more technical details such as the actual priority |
1670 | description for the more technical details such as the actual priority |
1547 | range. |
1671 | range. |
1548 | .PP |
1672 | .PP |
1549 | There are two common ways how these these priorities are being interpreted |
1673 | There are two common ways how these these priorities are being interpreted |
1550 | by event loops: |
1674 | by event loops: |
… | |
… | |
1644 | .IX Header "WATCHER TYPES" |
1768 | .IX Header "WATCHER TYPES" |
1645 | This section describes each watcher in detail, but will not repeat |
1769 | This section describes each watcher in detail, but will not repeat |
1646 | information given in the last section. Any initialisation/set macros, |
1770 | information given in the last section. Any initialisation/set macros, |
1647 | functions and members specific to the watcher type are explained. |
1771 | functions and members specific to the watcher type are explained. |
1648 | .PP |
1772 | .PP |
1649 | Members are additionally marked with either \fI[read\-only]\fR, meaning that, |
1773 | Most members are additionally marked with either \fI[read\-only]\fR, meaning |
1650 | while the watcher is active, you can look at the member and expect some |
1774 | that, while the watcher is active, you can look at the member and expect |
1651 | sensible content, but you must not modify it (you can modify it while the |
1775 | some sensible content, but you must not modify it (you can modify it while |
1652 | watcher is stopped to your hearts content), or \fI[read\-write]\fR, which |
1776 | the watcher is stopped to your hearts content), or \fI[read\-write]\fR, which |
1653 | means you can expect it to have some sensible content while the watcher |
1777 | means you can expect it to have some sensible content while the watcher is |
1654 | is active, but you can also modify it. Modifying it may not do something |
1778 | active, but you can also modify it (within the same thread as the event |
|
|
1779 | loop, i.e. without creating data races). Modifying it may not do something |
1655 | sensible or take immediate effect (or do anything at all), but libev will |
1780 | sensible or take immediate effect (or do anything at all), but libev will |
1656 | not crash or malfunction in any way. |
1781 | not crash or malfunction in any way. |
|
|
1782 | .PP |
|
|
1783 | In any case, the documentation for each member will explain what the |
|
|
1784 | effects are, and if there are any additional access restrictions. |
1657 | .ie n .SS """ev_io"" \- is this file descriptor readable or writable?" |
1785 | .ie n .SS """ev_io"" \- is this file descriptor readable or writable?" |
1658 | .el .SS "\f(CWev_io\fP \- is this file descriptor readable or writable?" |
1786 | .el .SS "\f(CWev_io\fP \- is this file descriptor readable or writable?" |
1659 | .IX Subsection "ev_io - is this file descriptor readable or writable?" |
1787 | .IX Subsection "ev_io - is this file descriptor readable or writable?" |
1660 | I/O watchers check whether a file descriptor is readable or writable |
1788 | I/O watchers check whether a file descriptor is readable or writable |
1661 | in each iteration of the event loop, or, more precisely, when reading |
1789 | in each iteration of the event loop, or, more precisely, when reading |
… | |
… | |
1689 | But really, best use non-blocking mode. |
1817 | But really, best use non-blocking mode. |
1690 | .PP |
1818 | .PP |
1691 | \fIThe special problem of disappearing file descriptors\fR |
1819 | \fIThe special problem of disappearing file descriptors\fR |
1692 | .IX Subsection "The special problem of disappearing file descriptors" |
1820 | .IX Subsection "The special problem of disappearing file descriptors" |
1693 | .PP |
1821 | .PP |
1694 | Some backends (e.g. kqueue, epoll) need to be told about closing a file |
1822 | Some backends (e.g. kqueue, epoll, linuxaio) need to be told about closing |
1695 | descriptor (either due to calling \f(CW\*(C`close\*(C'\fR explicitly or any other means, |
1823 | a file descriptor (either due to calling \f(CW\*(C`close\*(C'\fR explicitly or any other |
1696 | such as \f(CW\*(C`dup2\*(C'\fR). The reason is that you register interest in some file |
1824 | means, such as \f(CW\*(C`dup2\*(C'\fR). The reason is that you register interest in some |
1697 | descriptor, but when it goes away, the operating system will silently drop |
1825 | file descriptor, but when it goes away, the operating system will silently |
1698 | this interest. If another file descriptor with the same number then is |
1826 | drop this interest. If another file descriptor with the same number then |
1699 | registered with libev, there is no efficient way to see that this is, in |
1827 | is registered with libev, there is no efficient way to see that this is, |
1700 | fact, a different file descriptor. |
1828 | in fact, a different file descriptor. |
1701 | .PP |
1829 | .PP |
1702 | To avoid having to explicitly tell libev about such cases, libev follows |
1830 | To avoid having to explicitly tell libev about such cases, libev follows |
1703 | the following policy: Each time \f(CW\*(C`ev_io_set\*(C'\fR is being called, libev |
1831 | the following policy: Each time \f(CW\*(C`ev_io_set\*(C'\fR is being called, libev |
1704 | will assume that this is potentially a new file descriptor, otherwise |
1832 | will assume that this is potentially a new file descriptor, otherwise |
1705 | it is assumed that the file descriptor stays the same. That means that |
1833 | it is assumed that the file descriptor stays the same. That means that |
… | |
… | |
1742 | wish to read \- you would first have to request some data. |
1870 | wish to read \- you would first have to request some data. |
1743 | .PP |
1871 | .PP |
1744 | Since files are typically not-so-well supported by advanced notification |
1872 | Since files are typically not-so-well supported by advanced notification |
1745 | mechanism, libev tries hard to emulate \s-1POSIX\s0 behaviour with respect |
1873 | mechanism, libev tries hard to emulate \s-1POSIX\s0 behaviour with respect |
1746 | to files, even though you should not use it. The reason for this is |
1874 | to files, even though you should not use it. The reason for this is |
1747 | convenience: sometimes you want to watch \s-1STDIN\s0 or \s-1STDOUT\s0, which is |
1875 | convenience: sometimes you want to watch \s-1STDIN\s0 or \s-1STDOUT,\s0 which is |
1748 | usually a tty, often a pipe, but also sometimes files or special devices |
1876 | usually a tty, often a pipe, but also sometimes files or special devices |
1749 | (for example, \f(CW\*(C`epoll\*(C'\fR on Linux works with \fI/dev/random\fR but not with |
1877 | (for example, \f(CW\*(C`epoll\*(C'\fR on Linux works with \fI/dev/random\fR but not with |
1750 | \&\fI/dev/urandom\fR), and even though the file might better be served with |
1878 | \&\fI/dev/urandom\fR), and even though the file might better be served with |
1751 | asynchronous I/O instead of with non-blocking I/O, it is still useful when |
1879 | asynchronous I/O instead of with non-blocking I/O, it is still useful when |
1752 | it \*(L"just works\*(R" instead of freezing. |
1880 | it \*(L"just works\*(R" instead of freezing. |
1753 | .PP |
1881 | .PP |
1754 | So avoid file descriptors pointing to files when you know it (e.g. use |
1882 | So avoid file descriptors pointing to files when you know it (e.g. use |
1755 | libeio), but use them when it is convenient, e.g. for \s-1STDIN/STDOUT\s0, or |
1883 | libeio), but use them when it is convenient, e.g. for \s-1STDIN/STDOUT,\s0 or |
1756 | when you rarely read from a file instead of from a socket, and want to |
1884 | when you rarely read from a file instead of from a socket, and want to |
1757 | reuse the same code path. |
1885 | reuse the same code path. |
1758 | .PP |
1886 | .PP |
1759 | \fIThe special problem of fork\fR |
1887 | \fIThe special problem of fork\fR |
1760 | .IX Subsection "The special problem of fork" |
1888 | .IX Subsection "The special problem of fork" |
1761 | .PP |
1889 | .PP |
1762 | Some backends (epoll, kqueue) do not support \f(CW\*(C`fork ()\*(C'\fR at all or exhibit |
1890 | Some backends (epoll, kqueue, linuxaio, iouring) do not support \f(CW\*(C`fork ()\*(C'\fR |
1763 | useless behaviour. Libev fully supports fork, but needs to be told about |
1891 | at all or exhibit useless behaviour. Libev fully supports fork, but needs |
1764 | it in the child if you want to continue to use it in the child. |
1892 | to be told about it in the child if you want to continue to use it in the |
|
|
1893 | child. |
1765 | .PP |
1894 | .PP |
1766 | To support fork in your child processes, you have to call \f(CW\*(C`ev_loop_fork |
1895 | To support fork in your child processes, you have to call \f(CW\*(C`ev_loop_fork |
1767 | ()\*(C'\fR after a fork in the child, enable \f(CW\*(C`EVFLAG_FORKCHECK\*(C'\fR, or resort to |
1896 | ()\*(C'\fR after a fork in the child, enable \f(CW\*(C`EVFLAG_FORKCHECK\*(C'\fR, or resort to |
1768 | \&\f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or \f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
1897 | \&\f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or \f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
1769 | .PP |
1898 | .PP |
1770 | \fIThe special problem of \s-1SIGPIPE\s0\fR |
1899 | \fIThe special problem of \s-1SIGPIPE\s0\fR |
1771 | .IX Subsection "The special problem of SIGPIPE" |
1900 | .IX Subsection "The special problem of SIGPIPE" |
1772 | .PP |
1901 | .PP |
1773 | While not really specific to libev, it is easy to forget about \f(CW\*(C`SIGPIPE\*(C'\fR: |
1902 | While not really specific to libev, it is easy to forget about \f(CW\*(C`SIGPIPE\*(C'\fR: |
1774 | when writing to a pipe whose other end has been closed, your program gets |
1903 | when writing to a pipe whose other end has been closed, your program gets |
1775 | sent a \s-1SIGPIPE\s0, which, by default, aborts your program. For most programs |
1904 | sent a \s-1SIGPIPE,\s0 which, by default, aborts your program. For most programs |
1776 | this is sensible behaviour, for daemons, this is usually undesirable. |
1905 | this is sensible behaviour, for daemons, this is usually undesirable. |
1777 | .PP |
1906 | .PP |
1778 | So when you encounter spurious, unexplained daemon exits, make sure you |
1907 | So when you encounter spurious, unexplained daemon exits, make sure you |
1779 | ignore \s-1SIGPIPE\s0 (and maybe make sure you log the exit status of your daemon |
1908 | ignore \s-1SIGPIPE\s0 (and maybe make sure you log the exit status of your daemon |
1780 | somewhere, as that would have given you a big clue). |
1909 | somewhere, as that would have given you a big clue). |
1781 | .PP |
1910 | .PP |
1782 | \fIThe special problem of \fIaccept()\fIing when you can't\fR |
1911 | \fIThe special problem of \f(BIaccept()\fIing when you can't\fR |
1783 | .IX Subsection "The special problem of accept()ing when you can't" |
1912 | .IX Subsection "The special problem of accept()ing when you can't" |
1784 | .PP |
1913 | .PP |
1785 | Many implementations of the \s-1POSIX\s0 \f(CW\*(C`accept\*(C'\fR function (for example, |
1914 | Many implementations of the \s-1POSIX\s0 \f(CW\*(C`accept\*(C'\fR function (for example, |
1786 | found in post\-2004 Linux) have the peculiar behaviour of not removing a |
1915 | found in post\-2004 Linux) have the peculiar behaviour of not removing a |
1787 | connection from the pending queue in all error cases. |
1916 | connection from the pending queue in all error cases. |
… | |
… | |
1826 | .PD 0 |
1955 | .PD 0 |
1827 | .IP "ev_io_set (ev_io *, int fd, int events)" 4 |
1956 | .IP "ev_io_set (ev_io *, int fd, int events)" 4 |
1828 | .IX Item "ev_io_set (ev_io *, int fd, int events)" |
1957 | .IX Item "ev_io_set (ev_io *, int fd, int events)" |
1829 | .PD |
1958 | .PD |
1830 | Configures an \f(CW\*(C`ev_io\*(C'\fR watcher. The \f(CW\*(C`fd\*(C'\fR is the file descriptor to |
1959 | Configures an \f(CW\*(C`ev_io\*(C'\fR watcher. The \f(CW\*(C`fd\*(C'\fR is the file descriptor to |
1831 | receive events for and \f(CW\*(C`events\*(C'\fR is either \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR or |
1960 | receive events for and \f(CW\*(C`events\*(C'\fR is either \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR, both |
1832 | \&\f(CW\*(C`EV_READ | EV_WRITE\*(C'\fR, to express the desire to receive the given events. |
1961 | \&\f(CW\*(C`EV_READ | EV_WRITE\*(C'\fR or \f(CW0\fR, to express the desire to receive the given |
|
|
1962 | events. |
|
|
1963 | .Sp |
|
|
1964 | Note that setting the \f(CW\*(C`events\*(C'\fR to \f(CW0\fR and starting the watcher is |
|
|
1965 | supported, but not specially optimized \- if your program sometimes happens |
|
|
1966 | to generate this combination this is fine, but if it is easy to avoid |
|
|
1967 | starting an io watcher watching for no events you should do so. |
|
|
1968 | .IP "ev_io_modify (ev_io *, int events)" 4 |
|
|
1969 | .IX Item "ev_io_modify (ev_io *, int events)" |
|
|
1970 | Similar to \f(CW\*(C`ev_io_set\*(C'\fR, but only changes the requested events. Using this |
|
|
1971 | might be faster with some backends, as libev can assume that the \f(CW\*(C`fd\*(C'\fR |
|
|
1972 | still refers to the same underlying file description, something it cannot |
|
|
1973 | do when using \f(CW\*(C`ev_io_set\*(C'\fR. |
1833 | .IP "int fd [read\-only]" 4 |
1974 | .IP "int fd [no\-modify]" 4 |
1834 | .IX Item "int fd [read-only]" |
1975 | .IX Item "int fd [no-modify]" |
1835 | The file descriptor being watched. |
1976 | The file descriptor being watched. While it can be read at any time, you |
|
|
1977 | must not modify this member even when the watcher is stopped \- always use |
|
|
1978 | \&\f(CW\*(C`ev_io_set\*(C'\fR for that. |
1836 | .IP "int events [read\-only]" 4 |
1979 | .IP "int events [no\-modify]" 4 |
1837 | .IX Item "int events [read-only]" |
1980 | .IX Item "int events [no-modify]" |
1838 | The events being watched. |
1981 | The set of events the fd is being watched for, among other flags. Remember |
|
|
1982 | that this is a bit set \- to test for \f(CW\*(C`EV_READ\*(C'\fR, use \f(CW\*(C`w\->events & |
|
|
1983 | EV_READ\*(C'\fR, and similarly for \f(CW\*(C`EV_WRITE\*(C'\fR. |
|
|
1984 | .Sp |
|
|
1985 | As with \f(CW\*(C`fd\*(C'\fR, you must not modify this member even when the watcher is |
|
|
1986 | stopped, always use \f(CW\*(C`ev_io_set\*(C'\fR or \f(CW\*(C`ev_io_modify\*(C'\fR for that. |
1839 | .PP |
1987 | .PP |
1840 | \fIExamples\fR |
1988 | \fIExamples\fR |
1841 | .IX Subsection "Examples" |
1989 | .IX Subsection "Examples" |
1842 | .PP |
1990 | .PP |
1843 | Example: Call \f(CW\*(C`stdin_readable_cb\*(C'\fR when \s-1STDIN_FILENO\s0 has become, well |
1991 | Example: Call \f(CW\*(C`stdin_readable_cb\*(C'\fR when \s-1STDIN_FILENO\s0 has become, well |
… | |
… | |
1871 | detecting time jumps is hard, and some inaccuracies are unavoidable (the |
2019 | detecting time jumps is hard, and some inaccuracies are unavoidable (the |
1872 | monotonic clock option helps a lot here). |
2020 | monotonic clock option helps a lot here). |
1873 | .PP |
2021 | .PP |
1874 | The callback is guaranteed to be invoked only \fIafter\fR its timeout has |
2022 | The callback is guaranteed to be invoked only \fIafter\fR its timeout has |
1875 | passed (not \fIat\fR, so on systems with very low-resolution clocks this |
2023 | passed (not \fIat\fR, so on systems with very low-resolution clocks this |
1876 | might introduce a small delay). If multiple timers become ready during the |
2024 | might introduce a small delay, see \*(L"the special problem of being too |
|
|
2025 | early\*(R", below). If multiple timers become ready during the same loop |
1877 | same loop iteration then the ones with earlier time-out values are invoked |
2026 | iteration then the ones with earlier time-out values are invoked before |
1878 | before ones of the same priority with later time-out values (but this is |
2027 | ones of the same priority with later time-out values (but this is no |
1879 | no longer true when a callback calls \f(CW\*(C`ev_run\*(C'\fR recursively). |
2028 | longer true when a callback calls \f(CW\*(C`ev_run\*(C'\fR recursively). |
1880 | .PP |
2029 | .PP |
1881 | \fIBe smart about timeouts\fR |
2030 | \fIBe smart about timeouts\fR |
1882 | .IX Subsection "Be smart about timeouts" |
2031 | .IX Subsection "Be smart about timeouts" |
1883 | .PP |
2032 | .PP |
1884 | Many real-world problems involve some kind of timeout, usually for error |
2033 | Many real-world problems involve some kind of timeout, usually for error |
… | |
… | |
1966 | .Sp |
2115 | .Sp |
1967 | In this case, it would be more efficient to leave the \f(CW\*(C`ev_timer\*(C'\fR alone, |
2116 | In this case, it would be more efficient to leave the \f(CW\*(C`ev_timer\*(C'\fR alone, |
1968 | but remember the time of last activity, and check for a real timeout only |
2117 | but remember the time of last activity, and check for a real timeout only |
1969 | within the callback: |
2118 | within the callback: |
1970 | .Sp |
2119 | .Sp |
1971 | .Vb 1 |
2120 | .Vb 3 |
|
|
2121 | \& ev_tstamp timeout = 60.; |
1972 | \& ev_tstamp last_activity; // time of last activity |
2122 | \& ev_tstamp last_activity; // time of last activity |
|
|
2123 | \& ev_timer timer; |
1973 | \& |
2124 | \& |
1974 | \& static void |
2125 | \& static void |
1975 | \& callback (EV_P_ ev_timer *w, int revents) |
2126 | \& callback (EV_P_ ev_timer *w, int revents) |
1976 | \& { |
2127 | \& { |
1977 | \& ev_tstamp now = ev_now (EV_A); |
2128 | \& // calculate when the timeout would happen |
1978 | \& ev_tstamp timeout = last_activity + 60.; |
2129 | \& ev_tstamp after = last_activity \- ev_now (EV_A) + timeout; |
1979 | \& |
2130 | \& |
1980 | \& // if last_activity + 60. is older than now, we did time out |
2131 | \& // if negative, it means we the timeout already occurred |
1981 | \& if (timeout < now) |
2132 | \& if (after < 0.) |
1982 | \& { |
2133 | \& { |
1983 | \& // timeout occurred, take action |
2134 | \& // timeout occurred, take action |
1984 | \& } |
2135 | \& } |
1985 | \& else |
2136 | \& else |
1986 | \& { |
2137 | \& { |
1987 | \& // callback was invoked, but there was some activity, re\-arm |
2138 | \& // callback was invoked, but there was some recent |
1988 | \& // the watcher to fire in last_activity + 60, which is |
2139 | \& // activity. simply restart the timer to time out |
1989 | \& // guaranteed to be in the future, so "again" is positive: |
2140 | \& // after "after" seconds, which is the earliest time |
1990 | \& w\->repeat = timeout \- now; |
2141 | \& // the timeout can occur. |
|
|
2142 | \& ev_timer_set (w, after, 0.); |
1991 | \& ev_timer_again (EV_A_ w); |
2143 | \& ev_timer_start (EV_A_ w); |
1992 | \& } |
2144 | \& } |
1993 | \& } |
2145 | \& } |
1994 | .Ve |
2146 | .Ve |
1995 | .Sp |
2147 | .Sp |
1996 | To summarise the callback: first calculate the real timeout (defined |
2148 | To summarise the callback: first calculate in how many seconds the |
1997 | as \*(L"60 seconds after the last activity\*(R"), then check if that time has |
2149 | timeout will occur (by calculating the absolute time when it would occur, |
1998 | been reached, which means something \fIdid\fR, in fact, time out. Otherwise |
2150 | \&\f(CW\*(C`last_activity + timeout\*(C'\fR, and subtracting the current time, \f(CW\*(C`ev_now |
1999 | the callback was invoked too early (\f(CW\*(C`timeout\*(C'\fR is in the future), so |
2151 | (EV_A)\*(C'\fR from that). |
2000 | re-schedule the timer to fire at that future time, to see if maybe we have |
|
|
2001 | a timeout then. |
|
|
2002 | .Sp |
2152 | .Sp |
2003 | Note how \f(CW\*(C`ev_timer_again\*(C'\fR is used, taking advantage of the |
2153 | If this value is negative, then we are already past the timeout, i.e. we |
2004 | \&\f(CW\*(C`ev_timer_again\*(C'\fR optimisation when the timer is already running. |
2154 | timed out, and need to do whatever is needed in this case. |
|
|
2155 | .Sp |
|
|
2156 | Otherwise, we now the earliest time at which the timeout would trigger, |
|
|
2157 | and simply start the timer with this timeout value. |
|
|
2158 | .Sp |
|
|
2159 | In other words, each time the callback is invoked it will check whether |
|
|
2160 | the timeout occurred. If not, it will simply reschedule itself to check |
|
|
2161 | again at the earliest time it could time out. Rinse. Repeat. |
2005 | .Sp |
2162 | .Sp |
2006 | This scheme causes more callback invocations (about one every 60 seconds |
2163 | This scheme causes more callback invocations (about one every 60 seconds |
2007 | minus half the average time between activity), but virtually no calls to |
2164 | minus half the average time between activity), but virtually no calls to |
2008 | libev to change the timeout. |
2165 | libev to change the timeout. |
2009 | .Sp |
2166 | .Sp |
2010 | To start the timer, simply initialise the watcher and set \f(CW\*(C`last_activity\*(C'\fR |
2167 | To start the machinery, simply initialise the watcher and set |
2011 | to the current time (meaning we just have some activity :), then call the |
2168 | \&\f(CW\*(C`last_activity\*(C'\fR to the current time (meaning there was some activity just |
2012 | callback, which will \*(L"do the right thing\*(R" and start the timer: |
2169 | now), then call the callback, which will \*(L"do the right thing\*(R" and start |
|
|
2170 | the timer: |
2013 | .Sp |
2171 | .Sp |
2014 | .Vb 3 |
2172 | .Vb 3 |
|
|
2173 | \& last_activity = ev_now (EV_A); |
2015 | \& ev_init (timer, callback); |
2174 | \& ev_init (&timer, callback); |
2016 | \& last_activity = ev_now (loop); |
2175 | \& callback (EV_A_ &timer, 0); |
2017 | \& callback (loop, timer, EV_TIMER); |
|
|
2018 | .Ve |
2176 | .Ve |
2019 | .Sp |
2177 | .Sp |
2020 | And when there is some activity, simply store the current time in |
2178 | When there is some activity, simply store the current time in |
2021 | \&\f(CW\*(C`last_activity\*(C'\fR, no libev calls at all: |
2179 | \&\f(CW\*(C`last_activity\*(C'\fR, no libev calls at all: |
2022 | .Sp |
2180 | .Sp |
2023 | .Vb 1 |
2181 | .Vb 2 |
|
|
2182 | \& if (activity detected) |
2024 | \& last_activity = ev_now (loop); |
2183 | \& last_activity = ev_now (EV_A); |
|
|
2184 | .Ve |
|
|
2185 | .Sp |
|
|
2186 | When your timeout value changes, then the timeout can be changed by simply |
|
|
2187 | providing a new value, stopping the timer and calling the callback, which |
|
|
2188 | will again do the right thing (for example, time out immediately :). |
|
|
2189 | .Sp |
|
|
2190 | .Vb 3 |
|
|
2191 | \& timeout = new_value; |
|
|
2192 | \& ev_timer_stop (EV_A_ &timer); |
|
|
2193 | \& callback (EV_A_ &timer, 0); |
2025 | .Ve |
2194 | .Ve |
2026 | .Sp |
2195 | .Sp |
2027 | This technique is slightly more complex, but in most cases where the |
2196 | This technique is slightly more complex, but in most cases where the |
2028 | time-out is unlikely to be triggered, much more efficient. |
2197 | time-out is unlikely to be triggered, much more efficient. |
2029 | .Sp |
|
|
2030 | Changing the timeout is trivial as well (if it isn't hard-coded in the |
|
|
2031 | callback :) \- just change the timeout and invoke the callback, which will |
|
|
2032 | fix things for you. |
|
|
2033 | .IP "4. Wee, just use a double-linked list for your timeouts." 4 |
2198 | .IP "4. Wee, just use a double-linked list for your timeouts." 4 |
2034 | .IX Item "4. Wee, just use a double-linked list for your timeouts." |
2199 | .IX Item "4. Wee, just use a double-linked list for your timeouts." |
2035 | If there is not one request, but many thousands (millions...), all |
2200 | If there is not one request, but many thousands (millions...), all |
2036 | employing some kind of timeout with the same timeout value, then one can |
2201 | employing some kind of timeout with the same timeout value, then one can |
2037 | do even better: |
2202 | do even better: |
… | |
… | |
2061 | Method #1 is almost always a bad idea, and buys you nothing. Method #4 is |
2226 | Method #1 is almost always a bad idea, and buys you nothing. Method #4 is |
2062 | rather complicated, but extremely efficient, something that really pays |
2227 | rather complicated, but extremely efficient, something that really pays |
2063 | off after the first million or so of active timers, i.e. it's usually |
2228 | off after the first million or so of active timers, i.e. it's usually |
2064 | overkill :) |
2229 | overkill :) |
2065 | .PP |
2230 | .PP |
|
|
2231 | \fIThe special problem of being too early\fR |
|
|
2232 | .IX Subsection "The special problem of being too early" |
|
|
2233 | .PP |
|
|
2234 | If you ask a timer to call your callback after three seconds, then |
|
|
2235 | you expect it to be invoked after three seconds \- but of course, this |
|
|
2236 | cannot be guaranteed to infinite precision. Less obviously, it cannot be |
|
|
2237 | guaranteed to any precision by libev \- imagine somebody suspending the |
|
|
2238 | process with a \s-1STOP\s0 signal for a few hours for example. |
|
|
2239 | .PP |
|
|
2240 | So, libev tries to invoke your callback as soon as possible \fIafter\fR the |
|
|
2241 | delay has occurred, but cannot guarantee this. |
|
|
2242 | .PP |
|
|
2243 | A less obvious failure mode is calling your callback too early: many event |
|
|
2244 | loops compare timestamps with a \*(L"elapsed delay >= requested delay\*(R", but |
|
|
2245 | this can cause your callback to be invoked much earlier than you would |
|
|
2246 | expect. |
|
|
2247 | .PP |
|
|
2248 | To see why, imagine a system with a clock that only offers full second |
|
|
2249 | resolution (think windows if you can't come up with a broken enough \s-1OS\s0 |
|
|
2250 | yourself). If you schedule a one-second timer at the time 500.9, then the |
|
|
2251 | event loop will schedule your timeout to elapse at a system time of 500 |
|
|
2252 | (500.9 truncated to the resolution) + 1, or 501. |
|
|
2253 | .PP |
|
|
2254 | If an event library looks at the timeout 0.1s later, it will see \*(L"501 >= |
|
|
2255 | 501\*(R" and invoke the callback 0.1s after it was started, even though a |
|
|
2256 | one-second delay was requested \- this is being \*(L"too early\*(R", despite best |
|
|
2257 | intentions. |
|
|
2258 | .PP |
|
|
2259 | This is the reason why libev will never invoke the callback if the elapsed |
|
|
2260 | delay equals the requested delay, but only when the elapsed delay is |
|
|
2261 | larger than the requested delay. In the example above, libev would only invoke |
|
|
2262 | the callback at system time 502, or 1.1s after the timer was started. |
|
|
2263 | .PP |
|
|
2264 | So, while libev cannot guarantee that your callback will be invoked |
|
|
2265 | exactly when requested, it \fIcan\fR and \fIdoes\fR guarantee that the requested |
|
|
2266 | delay has actually elapsed, or in other words, it always errs on the \*(L"too |
|
|
2267 | late\*(R" side of things. |
|
|
2268 | .PP |
2066 | \fIThe special problem of time updates\fR |
2269 | \fIThe special problem of time updates\fR |
2067 | .IX Subsection "The special problem of time updates" |
2270 | .IX Subsection "The special problem of time updates" |
2068 | .PP |
2271 | .PP |
2069 | Establishing the current time is a costly operation (it usually takes at |
2272 | Establishing the current time is a costly operation (it usually takes |
2070 | least two system calls): \s-1EV\s0 therefore updates its idea of the current |
2273 | at least one system call): \s-1EV\s0 therefore updates its idea of the current |
2071 | time only before and after \f(CW\*(C`ev_run\*(C'\fR collects new events, which causes a |
2274 | time only before and after \f(CW\*(C`ev_run\*(C'\fR collects new events, which causes a |
2072 | growing difference between \f(CW\*(C`ev_now ()\*(C'\fR and \f(CW\*(C`ev_time ()\*(C'\fR when handling |
2275 | growing difference between \f(CW\*(C`ev_now ()\*(C'\fR and \f(CW\*(C`ev_time ()\*(C'\fR when handling |
2073 | lots of events in one iteration. |
2276 | lots of events in one iteration. |
2074 | .PP |
2277 | .PP |
2075 | The relative timeouts are calculated relative to the \f(CW\*(C`ev_now ()\*(C'\fR |
2278 | The relative timeouts are calculated relative to the \f(CW\*(C`ev_now ()\*(C'\fR |
2076 | time. This is usually the right thing as this timestamp refers to the time |
2279 | time. This is usually the right thing as this timestamp refers to the time |
2077 | of the event triggering whatever timeout you are modifying/starting. If |
2280 | of the event triggering whatever timeout you are modifying/starting. If |
2078 | you suspect event processing to be delayed and you \fIneed\fR to base the |
2281 | you suspect event processing to be delayed and you \fIneed\fR to base the |
2079 | timeout on the current time, use something like this to adjust for this: |
2282 | timeout on the current time, use something like the following to adjust |
|
|
2283 | for it: |
2080 | .PP |
2284 | .PP |
2081 | .Vb 1 |
2285 | .Vb 1 |
2082 | \& ev_timer_set (&timer, after + ev_now () \- ev_time (), 0.); |
2286 | \& ev_timer_set (&timer, after + (ev_time () \- ev_now ()), 0.); |
2083 | .Ve |
2287 | .Ve |
2084 | .PP |
2288 | .PP |
2085 | If the event loop is suspended for a long time, you can also force an |
2289 | If the event loop is suspended for a long time, you can also force an |
2086 | update of the time returned by \f(CW\*(C`ev_now ()\*(C'\fR by calling \f(CW\*(C`ev_now_update |
2290 | update of the time returned by \f(CW\*(C`ev_now ()\*(C'\fR by calling \f(CW\*(C`ev_now_update |
2087 | ()\*(C'\fR. |
2291 | ()\*(C'\fR, although that will push the event time of all outstanding events |
|
|
2292 | further into the future. |
|
|
2293 | .PP |
|
|
2294 | \fIThe special problem of unsynchronised clocks\fR |
|
|
2295 | .IX Subsection "The special problem of unsynchronised clocks" |
|
|
2296 | .PP |
|
|
2297 | Modern systems have a variety of clocks \- libev itself uses the normal |
|
|
2298 | \&\*(L"wall clock\*(R" clock and, if available, the monotonic clock (to avoid time |
|
|
2299 | jumps). |
|
|
2300 | .PP |
|
|
2301 | Neither of these clocks is synchronised with each other or any other clock |
|
|
2302 | on the system, so \f(CW\*(C`ev_time ()\*(C'\fR might return a considerably different time |
|
|
2303 | than \f(CW\*(C`gettimeofday ()\*(C'\fR or \f(CW\*(C`time ()\*(C'\fR. On a GNU/Linux system, for example, |
|
|
2304 | a call to \f(CW\*(C`gettimeofday\*(C'\fR might return a second count that is one higher |
|
|
2305 | than a directly following call to \f(CW\*(C`time\*(C'\fR. |
|
|
2306 | .PP |
|
|
2307 | The moral of this is to only compare libev-related timestamps with |
|
|
2308 | \&\f(CW\*(C`ev_time ()\*(C'\fR and \f(CW\*(C`ev_now ()\*(C'\fR, at least if you want better precision than |
|
|
2309 | a second or so. |
|
|
2310 | .PP |
|
|
2311 | One more problem arises due to this lack of synchronisation: if libev uses |
|
|
2312 | the system monotonic clock and you compare timestamps from \f(CW\*(C`ev_time\*(C'\fR |
|
|
2313 | or \f(CW\*(C`ev_now\*(C'\fR from when you started your timer and when your callback is |
|
|
2314 | invoked, you will find that sometimes the callback is a bit \*(L"early\*(R". |
|
|
2315 | .PP |
|
|
2316 | This is because \f(CW\*(C`ev_timer\*(C'\fRs work in real time, not wall clock time, so |
|
|
2317 | libev makes sure your callback is not invoked before the delay happened, |
|
|
2318 | \&\fImeasured according to the real time\fR, not the system clock. |
|
|
2319 | .PP |
|
|
2320 | If your timeouts are based on a physical timescale (e.g. \*(L"time out this |
|
|
2321 | connection after 100 seconds\*(R") then this shouldn't bother you as it is |
|
|
2322 | exactly the right behaviour. |
|
|
2323 | .PP |
|
|
2324 | If you want to compare wall clock/system timestamps to your timers, then |
|
|
2325 | you need to use \f(CW\*(C`ev_periodic\*(C'\fRs, as these are based on the wall clock |
|
|
2326 | time, where your comparisons will always generate correct results. |
2088 | .PP |
2327 | .PP |
2089 | \fIThe special problems of suspended animation\fR |
2328 | \fIThe special problems of suspended animation\fR |
2090 | .IX Subsection "The special problems of suspended animation" |
2329 | .IX Subsection "The special problems of suspended animation" |
2091 | .PP |
2330 | .PP |
2092 | When you leave the server world it is quite customary to hit machines that |
2331 | When you leave the server world it is quite customary to hit machines that |
… | |
… | |
2123 | .IX Item "ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)" |
2362 | .IX Item "ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)" |
2124 | .PD 0 |
2363 | .PD 0 |
2125 | .IP "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" 4 |
2364 | .IP "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" 4 |
2126 | .IX Item "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" |
2365 | .IX Item "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" |
2127 | .PD |
2366 | .PD |
2128 | Configure the timer to trigger after \f(CW\*(C`after\*(C'\fR seconds. If \f(CW\*(C`repeat\*(C'\fR |
2367 | Configure the timer to trigger after \f(CW\*(C`after\*(C'\fR seconds (fractional and |
2129 | is \f(CW0.\fR, then it will automatically be stopped once the timeout is |
2368 | negative values are supported). If \f(CW\*(C`repeat\*(C'\fR is \f(CW0.\fR, then it will |
2130 | reached. If it is positive, then the timer will automatically be |
2369 | automatically be stopped once the timeout is reached. If it is positive, |
2131 | configured to trigger again \f(CW\*(C`repeat\*(C'\fR seconds later, again, and again, |
2370 | then the timer will automatically be configured to trigger again \f(CW\*(C`repeat\*(C'\fR |
2132 | until stopped manually. |
2371 | seconds later, again, and again, until stopped manually. |
2133 | .Sp |
2372 | .Sp |
2134 | The timer itself will do a best-effort at avoiding drift, that is, if |
2373 | The timer itself will do a best-effort at avoiding drift, that is, if |
2135 | you configure a timer to trigger every 10 seconds, then it will normally |
2374 | you configure a timer to trigger every 10 seconds, then it will normally |
2136 | trigger at exactly 10 second intervals. If, however, your program cannot |
2375 | trigger at exactly 10 second intervals. If, however, your program cannot |
2137 | keep up with the timer (because it takes longer than those 10 seconds to |
2376 | keep up with the timer (because it takes longer than those 10 seconds to |
2138 | do stuff) the timer will not fire more than once per event loop iteration. |
2377 | do stuff) the timer will not fire more than once per event loop iteration. |
2139 | .IP "ev_timer_again (loop, ev_timer *)" 4 |
2378 | .IP "ev_timer_again (loop, ev_timer *)" 4 |
2140 | .IX Item "ev_timer_again (loop, ev_timer *)" |
2379 | .IX Item "ev_timer_again (loop, ev_timer *)" |
2141 | This will act as if the timer timed out and restart it again if it is |
2380 | This will act as if the timer timed out, and restarts it again if it is |
2142 | repeating. The exact semantics are: |
2381 | repeating. It basically works like calling \f(CW\*(C`ev_timer_stop\*(C'\fR, updating the |
|
|
2382 | timeout to the \f(CW\*(C`repeat\*(C'\fR value and calling \f(CW\*(C`ev_timer_start\*(C'\fR. |
2143 | .Sp |
2383 | .Sp |
|
|
2384 | The exact semantics are as in the following rules, all of which will be |
|
|
2385 | applied to the watcher: |
|
|
2386 | .RS 4 |
2144 | If the timer is pending, its pending status is cleared. |
2387 | .IP "If the timer is pending, the pending status is always cleared." 4 |
2145 | .Sp |
2388 | .IX Item "If the timer is pending, the pending status is always cleared." |
|
|
2389 | .PD 0 |
2146 | If the timer is started but non-repeating, stop it (as if it timed out). |
2390 | .IP "If the timer is started but non-repeating, stop it (as if it timed out, without invoking it)." 4 |
2147 | .Sp |
2391 | .IX Item "If the timer is started but non-repeating, stop it (as if it timed out, without invoking it)." |
2148 | If the timer is repeating, either start it if necessary (with the |
2392 | .ie n .IP "If the timer is repeating, make the ""repeat"" value the new timeout and start the timer, if necessary." 4 |
2149 | \&\f(CW\*(C`repeat\*(C'\fR value), or reset the running timer to the \f(CW\*(C`repeat\*(C'\fR value. |
2393 | .el .IP "If the timer is repeating, make the \f(CWrepeat\fR value the new timeout and start the timer, if necessary." 4 |
|
|
2394 | .IX Item "If the timer is repeating, make the repeat value the new timeout and start the timer, if necessary." |
|
|
2395 | .RE |
|
|
2396 | .RS 4 |
|
|
2397 | .PD |
2150 | .Sp |
2398 | .Sp |
2151 | This sounds a bit complicated, see \*(L"Be smart about timeouts\*(R", above, for a |
2399 | This sounds a bit complicated, see \*(L"Be smart about timeouts\*(R", above, for a |
2152 | usage example. |
2400 | usage example. |
|
|
2401 | .RE |
2153 | .IP "ev_tstamp ev_timer_remaining (loop, ev_timer *)" 4 |
2402 | .IP "ev_tstamp ev_timer_remaining (loop, ev_timer *)" 4 |
2154 | .IX Item "ev_tstamp ev_timer_remaining (loop, ev_timer *)" |
2403 | .IX Item "ev_tstamp ev_timer_remaining (loop, ev_timer *)" |
2155 | Returns the remaining time until a timer fires. If the timer is active, |
2404 | Returns the remaining time until a timer fires. If the timer is active, |
2156 | then this time is relative to the current event loop time, otherwise it's |
2405 | then this time is relative to the current event loop time, otherwise it's |
2157 | the timeout value currently configured. |
2406 | the timeout value currently configured. |
… | |
… | |
2209 | Periodic watchers are also timers of a kind, but they are very versatile |
2458 | Periodic watchers are also timers of a kind, but they are very versatile |
2210 | (and unfortunately a bit complex). |
2459 | (and unfortunately a bit complex). |
2211 | .PP |
2460 | .PP |
2212 | Unlike \f(CW\*(C`ev_timer\*(C'\fR, periodic watchers are not based on real time (or |
2461 | Unlike \f(CW\*(C`ev_timer\*(C'\fR, periodic watchers are not based on real time (or |
2213 | relative time, the physical time that passes) but on wall clock time |
2462 | relative time, the physical time that passes) but on wall clock time |
2214 | (absolute time, the thing you can read on your calender or clock). The |
2463 | (absolute time, the thing you can read on your calendar or clock). The |
2215 | difference is that wall clock time can run faster or slower than real |
2464 | difference is that wall clock time can run faster or slower than real |
2216 | time, and time jumps are not uncommon (e.g. when you adjust your |
2465 | time, and time jumps are not uncommon (e.g. when you adjust your |
2217 | wrist-watch). |
2466 | wrist-watch). |
2218 | .PP |
2467 | .PP |
2219 | You can tell a periodic watcher to trigger after some specific point |
2468 | You can tell a periodic watcher to trigger after some specific point |
… | |
… | |
2224 | \&\f(CW\*(C`ev_timer\*(C'\fR, which would still trigger roughly 10 seconds after starting |
2473 | \&\f(CW\*(C`ev_timer\*(C'\fR, which would still trigger roughly 10 seconds after starting |
2225 | it, as it uses a relative timeout). |
2474 | it, as it uses a relative timeout). |
2226 | .PP |
2475 | .PP |
2227 | \&\f(CW\*(C`ev_periodic\*(C'\fR watchers can also be used to implement vastly more complex |
2476 | \&\f(CW\*(C`ev_periodic\*(C'\fR watchers can also be used to implement vastly more complex |
2228 | timers, such as triggering an event on each \*(L"midnight, local time\*(R", or |
2477 | timers, such as triggering an event on each \*(L"midnight, local time\*(R", or |
2229 | other complicated rules. This cannot be done with \f(CW\*(C`ev_timer\*(C'\fR watchers, as |
2478 | other complicated rules. This cannot easily be done with \f(CW\*(C`ev_timer\*(C'\fR |
2230 | those cannot react to time jumps. |
2479 | watchers, as those cannot react to time jumps. |
2231 | .PP |
2480 | .PP |
2232 | As with timers, the callback is guaranteed to be invoked only when the |
2481 | As with timers, the callback is guaranteed to be invoked only when the |
2233 | point in time where it is supposed to trigger has passed. If multiple |
2482 | point in time where it is supposed to trigger has passed. If multiple |
2234 | timers become ready during the same loop iteration then the ones with |
2483 | timers become ready during the same loop iteration then the ones with |
2235 | earlier time-out values are invoked before ones with later time-out values |
2484 | earlier time-out values are invoked before ones with later time-out values |
… | |
… | |
2277 | .Sp |
2526 | .Sp |
2278 | Another way to think about it (for the mathematically inclined) is that |
2527 | Another way to think about it (for the mathematically inclined) is that |
2279 | \&\f(CW\*(C`ev_periodic\*(C'\fR will try to run the callback in this mode at the next possible |
2528 | \&\f(CW\*(C`ev_periodic\*(C'\fR will try to run the callback in this mode at the next possible |
2280 | time where \f(CW\*(C`time = offset (mod interval)\*(C'\fR, regardless of any time jumps. |
2529 | time where \f(CW\*(C`time = offset (mod interval)\*(C'\fR, regardless of any time jumps. |
2281 | .Sp |
2530 | .Sp |
2282 | For numerical stability it is preferable that the \f(CW\*(C`offset\*(C'\fR value is near |
2531 | The \f(CW\*(C`interval\*(C'\fR \fI\s-1MUST\s0\fR be positive, and for numerical stability, the |
2283 | \&\f(CW\*(C`ev_now ()\*(C'\fR (the current time), but there is no range requirement for |
2532 | interval value should be higher than \f(CW\*(C`1/8192\*(C'\fR (which is around 100 |
2284 | this value, and in fact is often specified as zero. |
2533 | microseconds) and \f(CW\*(C`offset\*(C'\fR should be higher than \f(CW0\fR and should have |
|
|
2534 | at most a similar magnitude as the current time (say, within a factor of |
|
|
2535 | ten). Typical values for offset are, in fact, \f(CW0\fR or something between |
|
|
2536 | \&\f(CW0\fR and \f(CW\*(C`interval\*(C'\fR, which is also the recommended range. |
2285 | .Sp |
2537 | .Sp |
2286 | Note also that there is an upper limit to how often a timer can fire (\s-1CPU\s0 |
2538 | Note also that there is an upper limit to how often a timer can fire (\s-1CPU\s0 |
2287 | speed for example), so if \f(CW\*(C`interval\*(C'\fR is very small then timing stability |
2539 | speed for example), so if \f(CW\*(C`interval\*(C'\fR is very small then timing stability |
2288 | will of course deteriorate. Libev itself tries to be exact to be about one |
2540 | will of course deteriorate. Libev itself tries to be exact to be about one |
2289 | millisecond (if the \s-1OS\s0 supports it and the machine is fast enough). |
2541 | millisecond (if the \s-1OS\s0 supports it and the machine is fast enough). |
… | |
… | |
2293 | In this mode the values for \f(CW\*(C`interval\*(C'\fR and \f(CW\*(C`offset\*(C'\fR are both being |
2545 | In this mode the values for \f(CW\*(C`interval\*(C'\fR and \f(CW\*(C`offset\*(C'\fR are both being |
2294 | ignored. Instead, each time the periodic watcher gets scheduled, the |
2546 | ignored. Instead, each time the periodic watcher gets scheduled, the |
2295 | reschedule callback will be called with the watcher as first, and the |
2547 | reschedule callback will be called with the watcher as first, and the |
2296 | current time as second argument. |
2548 | current time as second argument. |
2297 | .Sp |
2549 | .Sp |
2298 | \&\s-1NOTE:\s0 \fIThis callback \s-1MUST\s0 \s-1NOT\s0 stop or destroy any periodic watcher, ever, |
2550 | \&\s-1NOTE:\s0 \fIThis callback \s-1MUST NOT\s0 stop or destroy any periodic watcher, ever, |
2299 | or make \s-1ANY\s0 other event loop modifications whatsoever, unless explicitly |
2551 | or make \s-1ANY\s0 other event loop modifications whatsoever, unless explicitly |
2300 | allowed by documentation here\fR. |
2552 | allowed by documentation here\fR. |
2301 | .Sp |
2553 | .Sp |
2302 | If you need to stop it, return \f(CW\*(C`now + 1e30\*(C'\fR (or so, fudge fudge) and stop |
2554 | If you need to stop it, return \f(CW\*(C`now + 1e30\*(C'\fR (or so, fudge fudge) and stop |
2303 | it afterwards (e.g. by starting an \f(CW\*(C`ev_prepare\*(C'\fR watcher, which is the |
2555 | it afterwards (e.g. by starting an \f(CW\*(C`ev_prepare\*(C'\fR watcher, which is the |
… | |
… | |
2321 | .Sp |
2573 | .Sp |
2322 | \&\s-1NOTE:\s0 \fIThis callback must always return a time that is higher than or |
2574 | \&\s-1NOTE:\s0 \fIThis callback must always return a time that is higher than or |
2323 | equal to the passed \f(CI\*(C`now\*(C'\fI value\fR. |
2575 | equal to the passed \f(CI\*(C`now\*(C'\fI value\fR. |
2324 | .Sp |
2576 | .Sp |
2325 | This can be used to create very complex timers, such as a timer that |
2577 | This can be used to create very complex timers, such as a timer that |
2326 | triggers on \*(L"next midnight, local time\*(R". To do this, you would calculate the |
2578 | triggers on \*(L"next midnight, local time\*(R". To do this, you would calculate |
2327 | next midnight after \f(CW\*(C`now\*(C'\fR and return the timestamp value for this. How |
2579 | the next midnight after \f(CW\*(C`now\*(C'\fR and return the timestamp value for |
2328 | you do this is, again, up to you (but it is not trivial, which is the main |
2580 | this. Here is a (completely untested, no error checking) example on how to |
2329 | reason I omitted it as an example). |
2581 | do this: |
|
|
2582 | .Sp |
|
|
2583 | .Vb 1 |
|
|
2584 | \& #include <time.h> |
|
|
2585 | \& |
|
|
2586 | \& static ev_tstamp |
|
|
2587 | \& my_rescheduler (ev_periodic *w, ev_tstamp now) |
|
|
2588 | \& { |
|
|
2589 | \& time_t tnow = (time_t)now; |
|
|
2590 | \& struct tm tm; |
|
|
2591 | \& localtime_r (&tnow, &tm); |
|
|
2592 | \& |
|
|
2593 | \& tm.tm_sec = tm.tm_min = tm.tm_hour = 0; // midnight current day |
|
|
2594 | \& ++tm.tm_mday; // midnight next day |
|
|
2595 | \& |
|
|
2596 | \& return mktime (&tm); |
|
|
2597 | \& } |
|
|
2598 | .Ve |
|
|
2599 | .Sp |
|
|
2600 | Note: this code might run into trouble on days that have more then two |
|
|
2601 | midnights (beginning and end). |
2330 | .RE |
2602 | .RE |
2331 | .RS 4 |
2603 | .RS 4 |
2332 | .RE |
2604 | .RE |
2333 | .IP "ev_periodic_again (loop, ev_periodic *)" 4 |
2605 | .IP "ev_periodic_again (loop, ev_periodic *)" 4 |
2334 | .IX Item "ev_periodic_again (loop, ev_periodic *)" |
2606 | .IX Item "ev_periodic_again (loop, ev_periodic *)" |
… | |
… | |
2419 | only within the same loop, i.e. you can watch for \f(CW\*(C`SIGINT\*(C'\fR in your |
2691 | only within the same loop, i.e. you can watch for \f(CW\*(C`SIGINT\*(C'\fR in your |
2420 | default loop and for \f(CW\*(C`SIGIO\*(C'\fR in another loop, but you cannot watch for |
2692 | default loop and for \f(CW\*(C`SIGIO\*(C'\fR in another loop, but you cannot watch for |
2421 | \&\f(CW\*(C`SIGINT\*(C'\fR in both the default loop and another loop at the same time. At |
2693 | \&\f(CW\*(C`SIGINT\*(C'\fR in both the default loop and another loop at the same time. At |
2422 | the moment, \f(CW\*(C`SIGCHLD\*(C'\fR is permanently tied to the default loop. |
2694 | the moment, \f(CW\*(C`SIGCHLD\*(C'\fR is permanently tied to the default loop. |
2423 | .PP |
2695 | .PP |
2424 | When the first watcher gets started will libev actually register something |
2696 | Only after the first watcher for a signal is started will libev actually |
2425 | with the kernel (thus it coexists with your own signal handlers as long as |
2697 | register something with the kernel. It thus coexists with your own signal |
2426 | you don't register any with libev for the same signal). |
2698 | handlers as long as you don't register any with libev for the same signal. |
2427 | .PP |
2699 | .PP |
2428 | If possible and supported, libev will install its handlers with |
2700 | If possible and supported, libev will install its handlers with |
2429 | \&\f(CW\*(C`SA_RESTART\*(C'\fR (or equivalent) behaviour enabled, so system calls should |
2701 | \&\f(CW\*(C`SA_RESTART\*(C'\fR (or equivalent) behaviour enabled, so system calls should |
2430 | not be unduly interrupted. If you have a problem with system calls getting |
2702 | not be unduly interrupted. If you have a problem with system calls getting |
2431 | interrupted by signals you can block all signals in an \f(CW\*(C`ev_check\*(C'\fR watcher |
2703 | interrupted by signals you can block all signals in an \f(CW\*(C`ev_check\*(C'\fR watcher |
… | |
… | |
2492 | The signal the watcher watches out for. |
2764 | The signal the watcher watches out for. |
2493 | .PP |
2765 | .PP |
2494 | \fIExamples\fR |
2766 | \fIExamples\fR |
2495 | .IX Subsection "Examples" |
2767 | .IX Subsection "Examples" |
2496 | .PP |
2768 | .PP |
2497 | Example: Try to exit cleanly on \s-1SIGINT\s0. |
2769 | Example: Try to exit cleanly on \s-1SIGINT.\s0 |
2498 | .PP |
2770 | .PP |
2499 | .Vb 5 |
2771 | .Vb 5 |
2500 | \& static void |
2772 | \& static void |
2501 | \& sigint_cb (struct ev_loop *loop, ev_signal *w, int revents) |
2773 | \& sigint_cb (struct ev_loop *loop, ev_signal *w, int revents) |
2502 | \& { |
2774 | \& { |
… | |
… | |
2617 | .ie n .SS """ev_stat"" \- did the file attributes just change?" |
2889 | .ie n .SS """ev_stat"" \- did the file attributes just change?" |
2618 | .el .SS "\f(CWev_stat\fP \- did the file attributes just change?" |
2890 | .el .SS "\f(CWev_stat\fP \- did the file attributes just change?" |
2619 | .IX Subsection "ev_stat - did the file attributes just change?" |
2891 | .IX Subsection "ev_stat - did the file attributes just change?" |
2620 | This watches a file system path for attribute changes. That is, it calls |
2892 | This watches a file system path for attribute changes. That is, it calls |
2621 | \&\f(CW\*(C`stat\*(C'\fR on that path in regular intervals (or when the \s-1OS\s0 says it changed) |
2893 | \&\f(CW\*(C`stat\*(C'\fR on that path in regular intervals (or when the \s-1OS\s0 says it changed) |
2622 | and sees if it changed compared to the last time, invoking the callback if |
2894 | and sees if it changed compared to the last time, invoking the callback |
2623 | it did. |
2895 | if it did. Starting the watcher \f(CW\*(C`stat\*(C'\fR's the file, so only changes that |
|
|
2896 | happen after the watcher has been started will be reported. |
2624 | .PP |
2897 | .PP |
2625 | The path does not need to exist: changing from \*(L"path exists\*(R" to \*(L"path does |
2898 | The path does not need to exist: changing from \*(L"path exists\*(R" to \*(L"path does |
2626 | not exist\*(R" is a status change like any other. The condition \*(L"path does not |
2899 | not exist\*(R" is a status change like any other. The condition \*(L"path does not |
2627 | exist\*(R" (or more correctly \*(L"path cannot be stat'ed\*(R") is signified by the |
2900 | exist\*(R" (or more correctly \*(L"path cannot be stat'ed\*(R") is signified by the |
2628 | \&\f(CW\*(C`st_nlink\*(C'\fR field being zero (which is otherwise always forced to be at |
2901 | \&\f(CW\*(C`st_nlink\*(C'\fR field being zero (which is otherwise always forced to be at |
… | |
… | |
2658 | compilation environment, which means that on systems with large file |
2931 | compilation environment, which means that on systems with large file |
2659 | support disabled by default, you get the 32 bit version of the stat |
2932 | support disabled by default, you get the 32 bit version of the stat |
2660 | structure. When using the library from programs that change the \s-1ABI\s0 to |
2933 | structure. When using the library from programs that change the \s-1ABI\s0 to |
2661 | use 64 bit file offsets the programs will fail. In that case you have to |
2934 | use 64 bit file offsets the programs will fail. In that case you have to |
2662 | compile libev with the same flags to get binary compatibility. This is |
2935 | compile libev with the same flags to get binary compatibility. This is |
2663 | obviously the case with any flags that change the \s-1ABI\s0, but the problem is |
2936 | obviously the case with any flags that change the \s-1ABI,\s0 but the problem is |
2664 | most noticeably displayed with ev_stat and large file support. |
2937 | most noticeably displayed with ev_stat and large file support. |
2665 | .PP |
2938 | .PP |
2666 | The solution for this is to lobby your distribution maker to make large |
2939 | The solution for this is to lobby your distribution maker to make large |
2667 | file interfaces available by default (as e.g. FreeBSD does) and not |
2940 | file interfaces available by default (as e.g. FreeBSD does) and not |
2668 | optional. Libev cannot simply switch on large file support because it has |
2941 | optional. Libev cannot simply switch on large file support because it has |
… | |
… | |
2859 | Apart from keeping your process non-blocking (which is a useful |
3132 | Apart from keeping your process non-blocking (which is a useful |
2860 | effect on its own sometimes), idle watchers are a good place to do |
3133 | effect on its own sometimes), idle watchers are a good place to do |
2861 | \&\*(L"pseudo-background processing\*(R", or delay processing stuff to after the |
3134 | \&\*(L"pseudo-background processing\*(R", or delay processing stuff to after the |
2862 | event loop has handled all outstanding events. |
3135 | event loop has handled all outstanding events. |
2863 | .PP |
3136 | .PP |
|
|
3137 | \fIAbusing an \f(CI\*(C`ev_idle\*(C'\fI watcher for its side-effect\fR |
|
|
3138 | .IX Subsection "Abusing an ev_idle watcher for its side-effect" |
|
|
3139 | .PP |
|
|
3140 | As long as there is at least one active idle watcher, libev will never |
|
|
3141 | sleep unnecessarily. Or in other words, it will loop as fast as possible. |
|
|
3142 | For this to work, the idle watcher doesn't need to be invoked at all \- the |
|
|
3143 | lowest priority will do. |
|
|
3144 | .PP |
|
|
3145 | This mode of operation can be useful together with an \f(CW\*(C`ev_check\*(C'\fR watcher, |
|
|
3146 | to do something on each event loop iteration \- for example to balance load |
|
|
3147 | between different connections. |
|
|
3148 | .PP |
|
|
3149 | See \*(L"Abusing an ev_check watcher for its side-effect\*(R" for a longer |
|
|
3150 | example. |
|
|
3151 | .PP |
2864 | \fIWatcher-Specific Functions and Data Members\fR |
3152 | \fIWatcher-Specific Functions and Data Members\fR |
2865 | .IX Subsection "Watcher-Specific Functions and Data Members" |
3153 | .IX Subsection "Watcher-Specific Functions and Data Members" |
2866 | .IP "ev_idle_init (ev_idle *, callback)" 4 |
3154 | .IP "ev_idle_init (ev_idle *, callback)" 4 |
2867 | .IX Item "ev_idle_init (ev_idle *, callback)" |
3155 | .IX Item "ev_idle_init (ev_idle *, callback)" |
2868 | Initialises and configures the idle watcher \- it has no parameters of any |
3156 | Initialises and configures the idle watcher \- it has no parameters of any |
… | |
… | |
2873 | .IX Subsection "Examples" |
3161 | .IX Subsection "Examples" |
2874 | .PP |
3162 | .PP |
2875 | Example: Dynamically allocate an \f(CW\*(C`ev_idle\*(C'\fR watcher, start it, and in the |
3163 | Example: Dynamically allocate an \f(CW\*(C`ev_idle\*(C'\fR watcher, start it, and in the |
2876 | callback, free it. Also, use no error checking, as usual. |
3164 | callback, free it. Also, use no error checking, as usual. |
2877 | .PP |
3165 | .PP |
2878 | .Vb 7 |
3166 | .Vb 5 |
2879 | \& static void |
3167 | \& static void |
2880 | \& idle_cb (struct ev_loop *loop, ev_idle *w, int revents) |
3168 | \& idle_cb (struct ev_loop *loop, ev_idle *w, int revents) |
2881 | \& { |
3169 | \& { |
|
|
3170 | \& // stop the watcher |
|
|
3171 | \& ev_idle_stop (loop, w); |
|
|
3172 | \& |
|
|
3173 | \& // now we can free it |
2882 | \& free (w); |
3174 | \& free (w); |
|
|
3175 | \& |
2883 | \& // now do something you wanted to do when the program has |
3176 | \& // now do something you wanted to do when the program has |
2884 | \& // no longer anything immediate to do. |
3177 | \& // no longer anything immediate to do. |
2885 | \& } |
3178 | \& } |
2886 | \& |
3179 | \& |
2887 | \& ev_idle *idle_watcher = malloc (sizeof (ev_idle)); |
3180 | \& ev_idle *idle_watcher = malloc (sizeof (ev_idle)); |
… | |
… | |
2889 | \& ev_idle_start (loop, idle_watcher); |
3182 | \& ev_idle_start (loop, idle_watcher); |
2890 | .Ve |
3183 | .Ve |
2891 | .ie n .SS """ev_prepare"" and ""ev_check"" \- customise your event loop!" |
3184 | .ie n .SS """ev_prepare"" and ""ev_check"" \- customise your event loop!" |
2892 | .el .SS "\f(CWev_prepare\fP and \f(CWev_check\fP \- customise your event loop!" |
3185 | .el .SS "\f(CWev_prepare\fP and \f(CWev_check\fP \- customise your event loop!" |
2893 | .IX Subsection "ev_prepare and ev_check - customise your event loop!" |
3186 | .IX Subsection "ev_prepare and ev_check - customise your event loop!" |
2894 | Prepare and check watchers are usually (but not always) used in pairs: |
3187 | Prepare and check watchers are often (but not always) used in pairs: |
2895 | prepare watchers get invoked before the process blocks and check watchers |
3188 | prepare watchers get invoked before the process blocks and check watchers |
2896 | afterwards. |
3189 | afterwards. |
2897 | .PP |
3190 | .PP |
2898 | You \fImust not\fR call \f(CW\*(C`ev_run\*(C'\fR or similar functions that enter |
3191 | You \fImust not\fR call \f(CW\*(C`ev_run\*(C'\fR (or similar functions that enter the |
2899 | the current event loop from either \f(CW\*(C`ev_prepare\*(C'\fR or \f(CW\*(C`ev_check\*(C'\fR |
3192 | current event loop) or \f(CW\*(C`ev_loop_fork\*(C'\fR from either \f(CW\*(C`ev_prepare\*(C'\fR or |
2900 | watchers. Other loops than the current one are fine, however. The |
3193 | \&\f(CW\*(C`ev_check\*(C'\fR watchers. Other loops than the current one are fine, |
2901 | rationale behind this is that you do not need to check for recursion in |
3194 | however. The rationale behind this is that you do not need to check |
2902 | those watchers, i.e. the sequence will always be \f(CW\*(C`ev_prepare\*(C'\fR, blocking, |
3195 | for recursion in those watchers, i.e. the sequence will always be |
2903 | \&\f(CW\*(C`ev_check\*(C'\fR so if you have one watcher of each kind they will always be |
3196 | \&\f(CW\*(C`ev_prepare\*(C'\fR, blocking, \f(CW\*(C`ev_check\*(C'\fR so if you have one watcher of each |
2904 | called in pairs bracketing the blocking call. |
3197 | kind they will always be called in pairs bracketing the blocking call. |
2905 | .PP |
3198 | .PP |
2906 | Their main purpose is to integrate other event mechanisms into libev and |
3199 | Their main purpose is to integrate other event mechanisms into libev and |
2907 | their use is somewhat advanced. They could be used, for example, to track |
3200 | their use is somewhat advanced. They could be used, for example, to track |
2908 | variable changes, implement your own watchers, integrate net-snmp or a |
3201 | variable changes, implement your own watchers, integrate net-snmp or a |
2909 | coroutine library and lots more. They are also occasionally useful if |
3202 | coroutine library and lots more. They are also occasionally useful if |
… | |
… | |
2927 | with priority higher than or equal to the event loop and one coroutine |
3220 | with priority higher than or equal to the event loop and one coroutine |
2928 | of lower priority, but only once, using idle watchers to keep the event |
3221 | of lower priority, but only once, using idle watchers to keep the event |
2929 | loop from blocking if lower-priority coroutines are active, thus mapping |
3222 | loop from blocking if lower-priority coroutines are active, thus mapping |
2930 | low-priority coroutines to idle/background tasks). |
3223 | low-priority coroutines to idle/background tasks). |
2931 | .PP |
3224 | .PP |
2932 | It is recommended to give \f(CW\*(C`ev_check\*(C'\fR watchers highest (\f(CW\*(C`EV_MAXPRI\*(C'\fR) |
3225 | When used for this purpose, it is recommended to give \f(CW\*(C`ev_check\*(C'\fR watchers |
2933 | priority, to ensure that they are being run before any other watchers |
3226 | highest (\f(CW\*(C`EV_MAXPRI\*(C'\fR) priority, to ensure that they are being run before |
2934 | after the poll (this doesn't matter for \f(CW\*(C`ev_prepare\*(C'\fR watchers). |
3227 | any other watchers after the poll (this doesn't matter for \f(CW\*(C`ev_prepare\*(C'\fR |
|
|
3228 | watchers). |
2935 | .PP |
3229 | .PP |
2936 | Also, \f(CW\*(C`ev_check\*(C'\fR watchers (and \f(CW\*(C`ev_prepare\*(C'\fR watchers, too) should not |
3230 | Also, \f(CW\*(C`ev_check\*(C'\fR watchers (and \f(CW\*(C`ev_prepare\*(C'\fR watchers, too) should not |
2937 | activate (\*(L"feed\*(R") events into libev. While libev fully supports this, they |
3231 | activate (\*(L"feed\*(R") events into libev. While libev fully supports this, they |
2938 | might get executed before other \f(CW\*(C`ev_check\*(C'\fR watchers did their job. As |
3232 | might get executed before other \f(CW\*(C`ev_check\*(C'\fR watchers did their job. As |
2939 | \&\f(CW\*(C`ev_check\*(C'\fR watchers are often used to embed other (non-libev) event |
3233 | \&\f(CW\*(C`ev_check\*(C'\fR watchers are often used to embed other (non-libev) event |
2940 | loops those other event loops might be in an unusable state until their |
3234 | loops those other event loops might be in an unusable state until their |
2941 | \&\f(CW\*(C`ev_check\*(C'\fR watcher ran (always remind yourself to coexist peacefully with |
3235 | \&\f(CW\*(C`ev_check\*(C'\fR watcher ran (always remind yourself to coexist peacefully with |
2942 | others). |
3236 | others). |
|
|
3237 | .PP |
|
|
3238 | \fIAbusing an \f(CI\*(C`ev_check\*(C'\fI watcher for its side-effect\fR |
|
|
3239 | .IX Subsection "Abusing an ev_check watcher for its side-effect" |
|
|
3240 | .PP |
|
|
3241 | \&\f(CW\*(C`ev_check\*(C'\fR (and less often also \f(CW\*(C`ev_prepare\*(C'\fR) watchers can also be |
|
|
3242 | useful because they are called once per event loop iteration. For |
|
|
3243 | example, if you want to handle a large number of connections fairly, you |
|
|
3244 | normally only do a bit of work for each active connection, and if there |
|
|
3245 | is more work to do, you wait for the next event loop iteration, so other |
|
|
3246 | connections have a chance of making progress. |
|
|
3247 | .PP |
|
|
3248 | Using an \f(CW\*(C`ev_check\*(C'\fR watcher is almost enough: it will be called on the |
|
|
3249 | next event loop iteration. However, that isn't as soon as possible \- |
|
|
3250 | without external events, your \f(CW\*(C`ev_check\*(C'\fR watcher will not be invoked. |
|
|
3251 | .PP |
|
|
3252 | This is where \f(CW\*(C`ev_idle\*(C'\fR watchers come in handy \- all you need is a |
|
|
3253 | single global idle watcher that is active as long as you have one active |
|
|
3254 | \&\f(CW\*(C`ev_check\*(C'\fR watcher. The \f(CW\*(C`ev_idle\*(C'\fR watcher makes sure the event loop |
|
|
3255 | will not sleep, and the \f(CW\*(C`ev_check\*(C'\fR watcher makes sure a callback gets |
|
|
3256 | invoked. Neither watcher alone can do that. |
2943 | .PP |
3257 | .PP |
2944 | \fIWatcher-Specific Functions and Data Members\fR |
3258 | \fIWatcher-Specific Functions and Data Members\fR |
2945 | .IX Subsection "Watcher-Specific Functions and Data Members" |
3259 | .IX Subsection "Watcher-Specific Functions and Data Members" |
2946 | .IP "ev_prepare_init (ev_prepare *, callback)" 4 |
3260 | .IP "ev_prepare_init (ev_prepare *, callback)" 4 |
2947 | .IX Item "ev_prepare_init (ev_prepare *, callback)" |
3261 | .IX Item "ev_prepare_init (ev_prepare *, callback)" |
… | |
… | |
3058 | .Ve |
3372 | .Ve |
3059 | .PP |
3373 | .PP |
3060 | Method 4: Do not use a prepare or check watcher because the module you |
3374 | Method 4: Do not use a prepare or check watcher because the module you |
3061 | want to embed is not flexible enough to support it. Instead, you can |
3375 | want to embed is not flexible enough to support it. Instead, you can |
3062 | override their poll function. The drawback with this solution is that the |
3376 | override their poll function. The drawback with this solution is that the |
3063 | main loop is now no longer controllable by \s-1EV\s0. The \f(CW\*(C`Glib::EV\*(C'\fR module uses |
3377 | main loop is now no longer controllable by \s-1EV.\s0 The \f(CW\*(C`Glib::EV\*(C'\fR module uses |
3064 | this approach, effectively embedding \s-1EV\s0 as a client into the horrible |
3378 | this approach, effectively embedding \s-1EV\s0 as a client into the horrible |
3065 | libglib event loop. |
3379 | libglib event loop. |
3066 | .PP |
3380 | .PP |
3067 | .Vb 4 |
3381 | .Vb 4 |
3068 | \& static gint |
3382 | \& static gint |
… | |
… | |
3152 | \fIWatcher-Specific Functions and Data Members\fR |
3466 | \fIWatcher-Specific Functions and Data Members\fR |
3153 | .IX Subsection "Watcher-Specific Functions and Data Members" |
3467 | .IX Subsection "Watcher-Specific Functions and Data Members" |
3154 | .IP "ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)" 4 |
3468 | .IP "ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)" 4 |
3155 | .IX Item "ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)" |
3469 | .IX Item "ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)" |
3156 | .PD 0 |
3470 | .PD 0 |
3157 | .IP "ev_embed_set (ev_embed *, callback, struct ev_loop *embedded_loop)" 4 |
3471 | .IP "ev_embed_set (ev_embed *, struct ev_loop *embedded_loop)" 4 |
3158 | .IX Item "ev_embed_set (ev_embed *, callback, struct ev_loop *embedded_loop)" |
3472 | .IX Item "ev_embed_set (ev_embed *, struct ev_loop *embedded_loop)" |
3159 | .PD |
3473 | .PD |
3160 | Configures the watcher to embed the given loop, which must be |
3474 | Configures the watcher to embed the given loop, which must be |
3161 | embeddable. If the callback is \f(CW0\fR, then \f(CW\*(C`ev_embed_sweep\*(C'\fR will be |
3475 | embeddable. If the callback is \f(CW0\fR, then \f(CW\*(C`ev_embed_sweep\*(C'\fR will be |
3162 | invoked automatically, otherwise it is the responsibility of the callback |
3476 | invoked automatically, otherwise it is the responsibility of the callback |
3163 | to invoke it (it will continue to be called until the sweep has been done, |
3477 | to invoke it (it will continue to be called until the sweep has been done, |
… | |
… | |
3182 | .PP |
3496 | .PP |
3183 | .Vb 3 |
3497 | .Vb 3 |
3184 | \& struct ev_loop *loop_hi = ev_default_init (0); |
3498 | \& struct ev_loop *loop_hi = ev_default_init (0); |
3185 | \& struct ev_loop *loop_lo = 0; |
3499 | \& struct ev_loop *loop_lo = 0; |
3186 | \& ev_embed embed; |
3500 | \& ev_embed embed; |
3187 | \& |
3501 | \& |
3188 | \& // see if there is a chance of getting one that works |
3502 | \& // see if there is a chance of getting one that works |
3189 | \& // (remember that a flags value of 0 means autodetection) |
3503 | \& // (remember that a flags value of 0 means autodetection) |
3190 | \& loop_lo = ev_embeddable_backends () & ev_recommended_backends () |
3504 | \& loop_lo = ev_embeddable_backends () & ev_recommended_backends () |
3191 | \& ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ()) |
3505 | \& ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ()) |
3192 | \& : 0; |
3506 | \& : 0; |
… | |
… | |
3208 | .PP |
3522 | .PP |
3209 | .Vb 3 |
3523 | .Vb 3 |
3210 | \& struct ev_loop *loop = ev_default_init (0); |
3524 | \& struct ev_loop *loop = ev_default_init (0); |
3211 | \& struct ev_loop *loop_socket = 0; |
3525 | \& struct ev_loop *loop_socket = 0; |
3212 | \& ev_embed embed; |
3526 | \& ev_embed embed; |
3213 | \& |
3527 | \& |
3214 | \& if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE) |
3528 | \& if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE) |
3215 | \& if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE)) |
3529 | \& if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE)) |
3216 | \& { |
3530 | \& { |
3217 | \& ev_embed_init (&embed, 0, loop_socket); |
3531 | \& ev_embed_init (&embed, 0, loop_socket); |
3218 | \& ev_embed_start (loop, &embed); |
3532 | \& ev_embed_start (loop, &embed); |
… | |
… | |
3226 | .ie n .SS """ev_fork"" \- the audacity to resume the event loop after a fork" |
3540 | .ie n .SS """ev_fork"" \- the audacity to resume the event loop after a fork" |
3227 | .el .SS "\f(CWev_fork\fP \- the audacity to resume the event loop after a fork" |
3541 | .el .SS "\f(CWev_fork\fP \- the audacity to resume the event loop after a fork" |
3228 | .IX Subsection "ev_fork - the audacity to resume the event loop after a fork" |
3542 | .IX Subsection "ev_fork - the audacity to resume the event loop after a fork" |
3229 | Fork watchers are called when a \f(CW\*(C`fork ()\*(C'\fR was detected (usually because |
3543 | Fork watchers are called when a \f(CW\*(C`fork ()\*(C'\fR was detected (usually because |
3230 | whoever is a good citizen cared to tell libev about it by calling |
3544 | whoever is a good citizen cared to tell libev about it by calling |
3231 | \&\f(CW\*(C`ev_default_fork\*(C'\fR or \f(CW\*(C`ev_loop_fork\*(C'\fR). The invocation is done before the |
3545 | \&\f(CW\*(C`ev_loop_fork\*(C'\fR). The invocation is done before the event loop blocks next |
3232 | event loop blocks next and before \f(CW\*(C`ev_check\*(C'\fR watchers are being called, |
3546 | and before \f(CW\*(C`ev_check\*(C'\fR watchers are being called, and only in the child |
3233 | and only in the child after the fork. If whoever good citizen calling |
3547 | after the fork. If whoever good citizen calling \f(CW\*(C`ev_default_fork\*(C'\fR cheats |
3234 | \&\f(CW\*(C`ev_default_fork\*(C'\fR cheats and calls it in the wrong process, the fork |
3548 | and calls it in the wrong process, the fork handlers will be invoked, too, |
3235 | handlers will be invoked, too, of course. |
3549 | of course. |
3236 | .PP |
3550 | .PP |
3237 | \fIThe special problem of life after fork \- how is it possible?\fR |
3551 | \fIThe special problem of life after fork \- how is it possible?\fR |
3238 | .IX Subsection "The special problem of life after fork - how is it possible?" |
3552 | .IX Subsection "The special problem of life after fork - how is it possible?" |
3239 | .PP |
3553 | .PP |
3240 | Most uses of \f(CW\*(C`fork()\*(C'\fR consist of forking, then some simple calls to set |
3554 | Most uses of \f(CW\*(C`fork ()\*(C'\fR consist of forking, then some simple calls to set |
3241 | up/change the process environment, followed by a call to \f(CW\*(C`exec()\*(C'\fR. This |
3555 | up/change the process environment, followed by a call to \f(CW\*(C`exec()\*(C'\fR. This |
3242 | sequence should be handled by libev without any problems. |
3556 | sequence should be handled by libev without any problems. |
3243 | .PP |
3557 | .PP |
3244 | This changes when the application actually wants to do event handling |
3558 | This changes when the application actually wants to do event handling |
3245 | in the child, or both parent in child, in effect \*(L"continuing\*(R" after the |
3559 | in the child, or both parent in child, in effect \*(L"continuing\*(R" after the |
… | |
… | |
3326 | it by calling \f(CW\*(C`ev_async_send\*(C'\fR, which is thread\- and signal safe. |
3640 | it by calling \f(CW\*(C`ev_async_send\*(C'\fR, which is thread\- and signal safe. |
3327 | .PP |
3641 | .PP |
3328 | This functionality is very similar to \f(CW\*(C`ev_signal\*(C'\fR watchers, as signals, |
3642 | This functionality is very similar to \f(CW\*(C`ev_signal\*(C'\fR watchers, as signals, |
3329 | too, are asynchronous in nature, and signals, too, will be compressed |
3643 | too, are asynchronous in nature, and signals, too, will be compressed |
3330 | (i.e. the number of callback invocations may be less than the number of |
3644 | (i.e. the number of callback invocations may be less than the number of |
3331 | \&\f(CW\*(C`ev_async_sent\*(C'\fR calls). In fact, you could use signal watchers as a kind |
3645 | \&\f(CW\*(C`ev_async_send\*(C'\fR calls). In fact, you could use signal watchers as a kind |
3332 | of \*(L"global async watchers\*(R" by using a watcher on an otherwise unused |
3646 | of \*(L"global async watchers\*(R" by using a watcher on an otherwise unused |
3333 | signal, and \f(CW\*(C`ev_feed_signal\*(C'\fR to signal this watcher from another thread, |
3647 | signal, and \f(CW\*(C`ev_feed_signal\*(C'\fR to signal this watcher from another thread, |
3334 | even without knowing which loop owns the signal. |
3648 | even without knowing which loop owns the signal. |
3335 | .PP |
|
|
3336 | Unlike \f(CW\*(C`ev_signal\*(C'\fR watchers, \f(CW\*(C`ev_async\*(C'\fR works with any event loop, not |
|
|
3337 | just the default loop. |
|
|
3338 | .PP |
3649 | .PP |
3339 | \fIQueueing\fR |
3650 | \fIQueueing\fR |
3340 | .IX Subsection "Queueing" |
3651 | .IX Subsection "Queueing" |
3341 | .PP |
3652 | .PP |
3342 | \&\f(CW\*(C`ev_async\*(C'\fR does not support queueing of data in any way. The reason |
3653 | \&\f(CW\*(C`ev_async\*(C'\fR does not support queueing of data in any way. The reason |
… | |
… | |
3437 | Unlike \f(CW\*(C`ev_feed_event\*(C'\fR, this call is safe to do from other threads, |
3748 | Unlike \f(CW\*(C`ev_feed_event\*(C'\fR, this call is safe to do from other threads, |
3438 | signal or similar contexts (see the discussion of \f(CW\*(C`EV_ATOMIC_T\*(C'\fR in the |
3749 | signal or similar contexts (see the discussion of \f(CW\*(C`EV_ATOMIC_T\*(C'\fR in the |
3439 | embedding section below on what exactly this means). |
3750 | embedding section below on what exactly this means). |
3440 | .Sp |
3751 | .Sp |
3441 | Note that, as with other watchers in libev, multiple events might get |
3752 | Note that, as with other watchers in libev, multiple events might get |
3442 | compressed into a single callback invocation (another way to look at this |
3753 | compressed into a single callback invocation (another way to look at |
3443 | is that \f(CW\*(C`ev_async\*(C'\fR watchers are level-triggered, set on \f(CW\*(C`ev_async_send\*(C'\fR, |
3754 | this is that \f(CW\*(C`ev_async\*(C'\fR watchers are level-triggered: they are set on |
3444 | reset when the event loop detects that). |
3755 | \&\f(CW\*(C`ev_async_send\*(C'\fR, reset when the event loop detects that). |
3445 | .Sp |
3756 | .Sp |
3446 | This call incurs the overhead of a system call only once per event loop |
3757 | This call incurs the overhead of at most one extra system call per event |
3447 | iteration, so while the overhead might be noticeable, it doesn't apply to |
3758 | loop iteration, if the event loop is blocked, and no syscall at all if |
3448 | repeated calls to \f(CW\*(C`ev_async_send\*(C'\fR for the same event loop. |
3759 | the event loop (or your program) is processing events. That means that |
|
|
3760 | repeated calls are basically free (there is no need to avoid calls for |
|
|
3761 | performance reasons) and that the overhead becomes smaller (typically |
|
|
3762 | zero) under load. |
3449 | .IP "bool = ev_async_pending (ev_async *)" 4 |
3763 | .IP "bool = ev_async_pending (ev_async *)" 4 |
3450 | .IX Item "bool = ev_async_pending (ev_async *)" |
3764 | .IX Item "bool = ev_async_pending (ev_async *)" |
3451 | Returns a non-zero value when \f(CW\*(C`ev_async_send\*(C'\fR has been called on the |
3765 | Returns a non-zero value when \f(CW\*(C`ev_async_send\*(C'\fR has been called on the |
3452 | watcher but the event has not yet been processed (or even noted) by the |
3766 | watcher but the event has not yet been processed (or even noted) by the |
3453 | event loop. |
3767 | event loop. |
… | |
… | |
3462 | is a time window between the event loop checking and resetting the async |
3776 | is a time window between the event loop checking and resetting the async |
3463 | notification, and the callback being invoked. |
3777 | notification, and the callback being invoked. |
3464 | .SH "OTHER FUNCTIONS" |
3778 | .SH "OTHER FUNCTIONS" |
3465 | .IX Header "OTHER FUNCTIONS" |
3779 | .IX Header "OTHER FUNCTIONS" |
3466 | There are some other functions of possible interest. Described. Here. Now. |
3780 | There are some other functions of possible interest. Described. Here. Now. |
3467 | .IP "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)" 4 |
3781 | .IP "ev_once (loop, int fd, int events, ev_tstamp timeout, callback, arg)" 4 |
3468 | .IX Item "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)" |
3782 | .IX Item "ev_once (loop, int fd, int events, ev_tstamp timeout, callback, arg)" |
3469 | This function combines a simple timer and an I/O watcher, calls your |
3783 | This function combines a simple timer and an I/O watcher, calls your |
3470 | callback on whichever event happens first and automatically stops both |
3784 | callback on whichever event happens first and automatically stops both |
3471 | watchers. This is useful if you want to wait for a single event on an fd |
3785 | watchers. This is useful if you want to wait for a single event on an fd |
3472 | or timeout without having to allocate/configure/start/stop/free one or |
3786 | or timeout without having to allocate/configure/start/stop/free one or |
3473 | more watchers yourself. |
3787 | more watchers yourself. |
… | |
… | |
3485 | \&\f(CW\*(C`EV_ERROR\*(C'\fR, \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR or \f(CW\*(C`EV_TIMER\*(C'\fR) and the \f(CW\*(C`arg\*(C'\fR |
3799 | \&\f(CW\*(C`EV_ERROR\*(C'\fR, \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR or \f(CW\*(C`EV_TIMER\*(C'\fR) and the \f(CW\*(C`arg\*(C'\fR |
3486 | value passed to \f(CW\*(C`ev_once\*(C'\fR. Note that it is possible to receive \fIboth\fR |
3800 | value passed to \f(CW\*(C`ev_once\*(C'\fR. Note that it is possible to receive \fIboth\fR |
3487 | a timeout and an io event at the same time \- you probably should give io |
3801 | a timeout and an io event at the same time \- you probably should give io |
3488 | events precedence. |
3802 | events precedence. |
3489 | .Sp |
3803 | .Sp |
3490 | Example: wait up to ten seconds for data to appear on \s-1STDIN_FILENO\s0. |
3804 | Example: wait up to ten seconds for data to appear on \s-1STDIN_FILENO.\s0 |
3491 | .Sp |
3805 | .Sp |
3492 | .Vb 7 |
3806 | .Vb 7 |
3493 | \& static void stdin_ready (int revents, void *arg) |
3807 | \& static void stdin_ready (int revents, void *arg) |
3494 | \& { |
3808 | \& { |
3495 | \& if (revents & EV_READ) |
3809 | \& if (revents & EV_READ) |
… | |
… | |
3501 | \& ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
3815 | \& ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
3502 | .Ve |
3816 | .Ve |
3503 | .IP "ev_feed_fd_event (loop, int fd, int revents)" 4 |
3817 | .IP "ev_feed_fd_event (loop, int fd, int revents)" 4 |
3504 | .IX Item "ev_feed_fd_event (loop, int fd, int revents)" |
3818 | .IX Item "ev_feed_fd_event (loop, int fd, int revents)" |
3505 | Feed an event on the given fd, as if a file descriptor backend detected |
3819 | Feed an event on the given fd, as if a file descriptor backend detected |
3506 | the given events it. |
3820 | the given events. |
3507 | .IP "ev_feed_signal_event (loop, int signum)" 4 |
3821 | .IP "ev_feed_signal_event (loop, int signum)" 4 |
3508 | .IX Item "ev_feed_signal_event (loop, int signum)" |
3822 | .IX Item "ev_feed_signal_event (loop, int signum)" |
3509 | Feed an event as if the given signal occurred. See also \f(CW\*(C`ev_feed_signal\*(C'\fR, |
3823 | Feed an event as if the given signal occurred. See also \f(CW\*(C`ev_feed_signal\*(C'\fR, |
3510 | which is async-safe. |
3824 | which is async-safe. |
3511 | .SH "COMMON OR USEFUL IDIOMS (OR BOTH)" |
3825 | .SH "COMMON OR USEFUL IDIOMS (OR BOTH)" |
3512 | .IX Header "COMMON OR USEFUL IDIOMS (OR BOTH)" |
3826 | .IX Header "COMMON OR USEFUL IDIOMS (OR BOTH)" |
3513 | This section explains some common idioms that are not immediately |
3827 | This section explains some common idioms that are not immediately |
3514 | obvious. Note that examples are sprinkled over the whole manual, and this |
3828 | obvious. Note that examples are sprinkled over the whole manual, and this |
3515 | section only contains stuff that wouldn't fit anywhere else. |
3829 | section only contains stuff that wouldn't fit anywhere else. |
3516 | .SS "\s-1ASSOCIATING\s0 \s-1CUSTOM\s0 \s-1DATA\s0 \s-1WITH\s0 A \s-1WATCHER\s0" |
3830 | .SS "\s-1ASSOCIATING CUSTOM DATA WITH A WATCHER\s0" |
3517 | .IX Subsection "ASSOCIATING CUSTOM DATA WITH A WATCHER" |
3831 | .IX Subsection "ASSOCIATING CUSTOM DATA WITH A WATCHER" |
3518 | Each watcher has, by default, a \f(CW\*(C`void *data\*(C'\fR member that you can read |
3832 | Each watcher has, by default, a \f(CW\*(C`void *data\*(C'\fR member that you can read |
3519 | or modify at any time: libev will completely ignore it. This can be used |
3833 | or modify at any time: libev will completely ignore it. This can be used |
3520 | to associate arbitrary data with your watcher. If you need more data and |
3834 | to associate arbitrary data with your watcher. If you need more data and |
3521 | don't want to allocate memory separately and store a pointer to it in that |
3835 | don't want to allocate memory separately and store a pointer to it in that |
… | |
… | |
3547 | \& } |
3861 | \& } |
3548 | .Ve |
3862 | .Ve |
3549 | .PP |
3863 | .PP |
3550 | More interesting and less C\-conformant ways of casting your callback |
3864 | More interesting and less C\-conformant ways of casting your callback |
3551 | function type instead have been omitted. |
3865 | function type instead have been omitted. |
3552 | .SS "\s-1BUILDING\s0 \s-1YOUR\s0 \s-1OWN\s0 \s-1COMPOSITE\s0 \s-1WATCHERS\s0" |
3866 | .SS "\s-1BUILDING YOUR OWN COMPOSITE WATCHERS\s0" |
3553 | .IX Subsection "BUILDING YOUR OWN COMPOSITE WATCHERS" |
3867 | .IX Subsection "BUILDING YOUR OWN COMPOSITE WATCHERS" |
3554 | Another common scenario is to use some data structure with multiple |
3868 | Another common scenario is to use some data structure with multiple |
3555 | embedded watchers, in effect creating your own watcher that combines |
3869 | embedded watchers, in effect creating your own watcher that combines |
3556 | multiple libev event sources into one \*(L"super-watcher\*(R": |
3870 | multiple libev event sources into one \*(L"super-watcher\*(R": |
3557 | .PP |
3871 | .PP |
… | |
… | |
3585 | \& { |
3899 | \& { |
3586 | \& struct my_biggy big = (struct my_biggy *) |
3900 | \& struct my_biggy big = (struct my_biggy *) |
3587 | \& (((char *)w) \- offsetof (struct my_biggy, t2)); |
3901 | \& (((char *)w) \- offsetof (struct my_biggy, t2)); |
3588 | \& } |
3902 | \& } |
3589 | .Ve |
3903 | .Ve |
3590 | .SS "\s-1MODEL/NESTED\s0 \s-1EVENT\s0 \s-1LOOP\s0 \s-1INVOCATIONS\s0 \s-1AND\s0 \s-1EXIT\s0 \s-1CONDITIONS\s0" |
3904 | .SS "\s-1AVOIDING FINISHING BEFORE RETURNING\s0" |
|
|
3905 | .IX Subsection "AVOIDING FINISHING BEFORE RETURNING" |
|
|
3906 | Often you have structures like this in event-based programs: |
|
|
3907 | .PP |
|
|
3908 | .Vb 4 |
|
|
3909 | \& callback () |
|
|
3910 | \& { |
|
|
3911 | \& free (request); |
|
|
3912 | \& } |
|
|
3913 | \& |
|
|
3914 | \& request = start_new_request (..., callback); |
|
|
3915 | .Ve |
|
|
3916 | .PP |
|
|
3917 | The intent is to start some \*(L"lengthy\*(R" operation. The \f(CW\*(C`request\*(C'\fR could be |
|
|
3918 | used to cancel the operation, or do other things with it. |
|
|
3919 | .PP |
|
|
3920 | It's not uncommon to have code paths in \f(CW\*(C`start_new_request\*(C'\fR that |
|
|
3921 | immediately invoke the callback, for example, to report errors. Or you add |
|
|
3922 | some caching layer that finds that it can skip the lengthy aspects of the |
|
|
3923 | operation and simply invoke the callback with the result. |
|
|
3924 | .PP |
|
|
3925 | The problem here is that this will happen \fIbefore\fR \f(CW\*(C`start_new_request\*(C'\fR |
|
|
3926 | has returned, so \f(CW\*(C`request\*(C'\fR is not set. |
|
|
3927 | .PP |
|
|
3928 | Even if you pass the request by some safer means to the callback, you |
|
|
3929 | might want to do something to the request after starting it, such as |
|
|
3930 | canceling it, which probably isn't working so well when the callback has |
|
|
3931 | already been invoked. |
|
|
3932 | .PP |
|
|
3933 | A common way around all these issues is to make sure that |
|
|
3934 | \&\f(CW\*(C`start_new_request\*(C'\fR \fIalways\fR returns before the callback is invoked. If |
|
|
3935 | \&\f(CW\*(C`start_new_request\*(C'\fR immediately knows the result, it can artificially |
|
|
3936 | delay invoking the callback by using a \f(CW\*(C`prepare\*(C'\fR or \f(CW\*(C`idle\*(C'\fR watcher for |
|
|
3937 | example, or more sneakily, by reusing an existing (stopped) watcher and |
|
|
3938 | pushing it into the pending queue: |
|
|
3939 | .PP |
|
|
3940 | .Vb 2 |
|
|
3941 | \& ev_set_cb (watcher, callback); |
|
|
3942 | \& ev_feed_event (EV_A_ watcher, 0); |
|
|
3943 | .Ve |
|
|
3944 | .PP |
|
|
3945 | This way, \f(CW\*(C`start_new_request\*(C'\fR can safely return before the callback is |
|
|
3946 | invoked, while not delaying callback invocation too much. |
|
|
3947 | .SS "\s-1MODEL/NESTED EVENT LOOP INVOCATIONS AND EXIT CONDITIONS\s0" |
3591 | .IX Subsection "MODEL/NESTED EVENT LOOP INVOCATIONS AND EXIT CONDITIONS" |
3948 | .IX Subsection "MODEL/NESTED EVENT LOOP INVOCATIONS AND EXIT CONDITIONS" |
3592 | Often (especially in \s-1GUI\s0 toolkits) there are places where you have |
3949 | Often (especially in \s-1GUI\s0 toolkits) there are places where you have |
3593 | \&\fImodal\fR interaction, which is most easily implemented by recursively |
3950 | \&\fImodal\fR interaction, which is most easily implemented by recursively |
3594 | invoking \f(CW\*(C`ev_run\*(C'\fR. |
3951 | invoking \f(CW\*(C`ev_run\*(C'\fR. |
3595 | .PP |
3952 | .PP |
3596 | This brings the problem of exiting \- a callback might want to finish the |
3953 | This brings the problem of exiting \- a callback might want to finish the |
3597 | main \f(CW\*(C`ev_run\*(C'\fR call, but not the nested one (e.g. user clicked \*(L"Quit\*(R", but |
3954 | main \f(CW\*(C`ev_run\*(C'\fR call, but not the nested one (e.g. user clicked \*(L"Quit\*(R", but |
3598 | a modal \*(L"Are you sure?\*(R" dialog is still waiting), or just the nested one |
3955 | a modal \*(L"Are you sure?\*(R" dialog is still waiting), or just the nested one |
3599 | and not the main one (e.g. user clocked \*(L"Ok\*(R" in a modal dialog), or some |
3956 | and not the main one (e.g. user clocked \*(L"Ok\*(R" in a modal dialog), or some |
3600 | other combination: In these cases, \f(CW\*(C`ev_break\*(C'\fR will not work alone. |
3957 | other combination: In these cases, a simple \f(CW\*(C`ev_break\*(C'\fR will not work. |
3601 | .PP |
3958 | .PP |
3602 | The solution is to maintain \*(L"break this loop\*(R" variable for each \f(CW\*(C`ev_run\*(C'\fR |
3959 | The solution is to maintain \*(L"break this loop\*(R" variable for each \f(CW\*(C`ev_run\*(C'\fR |
3603 | invocation, and use a loop around \f(CW\*(C`ev_run\*(C'\fR until the condition is |
3960 | invocation, and use a loop around \f(CW\*(C`ev_run\*(C'\fR until the condition is |
3604 | triggered, using \f(CW\*(C`EVRUN_ONCE\*(C'\fR: |
3961 | triggered, using \f(CW\*(C`EVRUN_ONCE\*(C'\fR: |
3605 | .PP |
3962 | .PP |
… | |
… | |
3608 | \& int exit_main_loop = 0; |
3965 | \& int exit_main_loop = 0; |
3609 | \& |
3966 | \& |
3610 | \& while (!exit_main_loop) |
3967 | \& while (!exit_main_loop) |
3611 | \& ev_run (EV_DEFAULT_ EVRUN_ONCE); |
3968 | \& ev_run (EV_DEFAULT_ EVRUN_ONCE); |
3612 | \& |
3969 | \& |
3613 | \& // in a model watcher |
3970 | \& // in a modal watcher |
3614 | \& int exit_nested_loop = 0; |
3971 | \& int exit_nested_loop = 0; |
3615 | \& |
3972 | \& |
3616 | \& while (!exit_nested_loop) |
3973 | \& while (!exit_nested_loop) |
3617 | \& ev_run (EV_A_ EVRUN_ONCE); |
3974 | \& ev_run (EV_A_ EVRUN_ONCE); |
3618 | .Ve |
3975 | .Ve |
… | |
… | |
3627 | \& exit_main_loop = 1; |
3984 | \& exit_main_loop = 1; |
3628 | \& |
3985 | \& |
3629 | \& // exit both |
3986 | \& // exit both |
3630 | \& exit_main_loop = exit_nested_loop = 1; |
3987 | \& exit_main_loop = exit_nested_loop = 1; |
3631 | .Ve |
3988 | .Ve |
3632 | .SS "\s-1THREAD\s0 \s-1LOCKING\s0 \s-1EXAMPLE\s0" |
3989 | .SS "\s-1THREAD LOCKING EXAMPLE\s0" |
3633 | .IX Subsection "THREAD LOCKING EXAMPLE" |
3990 | .IX Subsection "THREAD LOCKING EXAMPLE" |
3634 | Here is a fictitious example of how to run an event loop in a different |
3991 | Here is a fictitious example of how to run an event loop in a different |
3635 | thread from where callbacks are being invoked and watchers are |
3992 | thread from where callbacks are being invoked and watchers are |
3636 | created/added/removed. |
3993 | created/added/removed. |
3637 | .PP |
3994 | .PP |
… | |
… | |
3645 | .PP |
4002 | .PP |
3646 | First, you need to associate some data with the event loop: |
4003 | First, you need to associate some data with the event loop: |
3647 | .PP |
4004 | .PP |
3648 | .Vb 6 |
4005 | .Vb 6 |
3649 | \& typedef struct { |
4006 | \& typedef struct { |
3650 | \& mutex_t lock; /* global loop lock */ |
4007 | \& pthread_mutex_t lock; /* global loop lock */ |
|
|
4008 | \& pthread_t tid; |
|
|
4009 | \& pthread_cond_t invoke_cv; |
3651 | \& ev_async async_w; |
4010 | \& ev_async async_w; |
3652 | \& thread_t tid; |
|
|
3653 | \& cond_t invoke_cv; |
|
|
3654 | \& } userdata; |
4011 | \& } userdata; |
3655 | \& |
4012 | \& |
3656 | \& void prepare_loop (EV_P) |
4013 | \& void prepare_loop (EV_P) |
3657 | \& { |
4014 | \& { |
3658 | \& // for simplicity, we use a static userdata struct. |
4015 | \& // for simplicity, we use a static userdata struct. |
3659 | \& static userdata u; |
4016 | \& static userdata u; |
3660 | \& |
4017 | \& |
3661 | \& ev_async_init (&u\->async_w, async_cb); |
4018 | \& ev_async_init (&u.async_w, async_cb); |
3662 | \& ev_async_start (EV_A_ &u\->async_w); |
4019 | \& ev_async_start (EV_A_ &u.async_w); |
3663 | \& |
4020 | \& |
3664 | \& pthread_mutex_init (&u\->lock, 0); |
4021 | \& pthread_mutex_init (&u.lock, 0); |
3665 | \& pthread_cond_init (&u\->invoke_cv, 0); |
4022 | \& pthread_cond_init (&u.invoke_cv, 0); |
3666 | \& |
4023 | \& |
3667 | \& // now associate this with the loop |
4024 | \& // now associate this with the loop |
3668 | \& ev_set_userdata (EV_A_ u); |
4025 | \& ev_set_userdata (EV_A_ &u); |
3669 | \& ev_set_invoke_pending_cb (EV_A_ l_invoke); |
4026 | \& ev_set_invoke_pending_cb (EV_A_ l_invoke); |
3670 | \& ev_set_loop_release_cb (EV_A_ l_release, l_acquire); |
4027 | \& ev_set_loop_release_cb (EV_A_ l_release, l_acquire); |
3671 | \& |
4028 | \& |
3672 | \& // then create the thread running ev_run |
4029 | \& // then create the thread running ev_run |
3673 | \& pthread_create (&u\->tid, 0, l_run, EV_A); |
4030 | \& pthread_create (&u.tid, 0, l_run, EV_A); |
3674 | \& } |
4031 | \& } |
3675 | .Ve |
4032 | .Ve |
3676 | .PP |
4033 | .PP |
3677 | The callback for the \f(CW\*(C`ev_async\*(C'\fR watcher does nothing: the watcher is used |
4034 | The callback for the \f(CW\*(C`ev_async\*(C'\fR watcher does nothing: the watcher is used |
3678 | solely to wake up the event loop so it takes notice of any new watchers |
4035 | solely to wake up the event loop so it takes notice of any new watchers |
… | |
… | |
3778 | .PP |
4135 | .PP |
3779 | Note that sending the \f(CW\*(C`ev_async\*(C'\fR watcher is required because otherwise |
4136 | Note that sending the \f(CW\*(C`ev_async\*(C'\fR watcher is required because otherwise |
3780 | an event loop currently blocking in the kernel will have no knowledge |
4137 | an event loop currently blocking in the kernel will have no knowledge |
3781 | about the newly added timer. By waking up the loop it will pick up any new |
4138 | about the newly added timer. By waking up the loop it will pick up any new |
3782 | watchers in the next event loop iteration. |
4139 | watchers in the next event loop iteration. |
3783 | .SS "\s-1THREADS\s0, \s-1COROUTINES\s0, \s-1CONTINUATIONS\s0, \s-1QUEUES\s0... \s-1INSTEAD\s0 \s-1OF\s0 \s-1CALLBACKS\s0" |
4140 | .SS "\s-1THREADS, COROUTINES, CONTINUATIONS, QUEUES... INSTEAD OF CALLBACKS\s0" |
3784 | .IX Subsection "THREADS, COROUTINES, CONTINUATIONS, QUEUES... INSTEAD OF CALLBACKS" |
4141 | .IX Subsection "THREADS, COROUTINES, CONTINUATIONS, QUEUES... INSTEAD OF CALLBACKS" |
3785 | While the overhead of a callback that e.g. schedules a thread is small, it |
4142 | While the overhead of a callback that e.g. schedules a thread is small, it |
3786 | is still an overhead. If you embed libev, and your main usage is with some |
4143 | is still an overhead. If you embed libev, and your main usage is with some |
3787 | kind of threads or coroutines, you might want to customise libev so that |
4144 | kind of threads or coroutines, you might want to customise libev so that |
3788 | doesn't need callbacks anymore. |
4145 | doesn't need callbacks anymore. |
… | |
… | |
3810 | .PP |
4167 | .PP |
3811 | .Vb 6 |
4168 | .Vb 6 |
3812 | \& void |
4169 | \& void |
3813 | \& wait_for_event (ev_watcher *w) |
4170 | \& wait_for_event (ev_watcher *w) |
3814 | \& { |
4171 | \& { |
3815 | \& ev_cb_set (w) = current_coro; |
4172 | \& ev_set_cb (w, current_coro); |
3816 | \& switch_to (libev_coro); |
4173 | \& switch_to (libev_coro); |
3817 | \& } |
4174 | \& } |
3818 | .Ve |
4175 | .Ve |
3819 | .PP |
4176 | .PP |
3820 | That basically suspends the coroutine inside \f(CW\*(C`wait_for_event\*(C'\fR and |
4177 | That basically suspends the coroutine inside \f(CW\*(C`wait_for_event\*(C'\fR and |
3821 | continues the libev coroutine, which, when appropriate, switches back to |
4178 | continues the libev coroutine, which, when appropriate, switches back to |
3822 | this or any other coroutine. I am sure if you sue this your own :) |
4179 | this or any other coroutine. |
3823 | .PP |
4180 | .PP |
3824 | You can do similar tricks if you have, say, threads with an event queue \- |
4181 | You can do similar tricks if you have, say, threads with an event queue \- |
3825 | instead of storing a coroutine, you store the queue object and instead of |
4182 | instead of storing a coroutine, you store the queue object and instead of |
3826 | switching to a coroutine, you push the watcher onto the queue and notify |
4183 | switching to a coroutine, you push the watcher onto the queue and notify |
3827 | any waiters. |
4184 | any waiters. |
3828 | .PP |
4185 | .PP |
3829 | To embed libev, see \s-1EMBEDDING\s0, but in short, it's easiest to create two |
4186 | To embed libev, see \*(L"\s-1EMBEDDING\*(R"\s0, but in short, it's easiest to create two |
3830 | files, \fImy_ev.h\fR and \fImy_ev.c\fR that include the respective libev files: |
4187 | files, \fImy_ev.h\fR and \fImy_ev.c\fR that include the respective libev files: |
3831 | .PP |
4188 | .PP |
3832 | .Vb 4 |
4189 | .Vb 4 |
3833 | \& // my_ev.h |
4190 | \& // my_ev.h |
3834 | \& #define EV_CB_DECLARE(type) struct my_coro *cb; |
4191 | \& #define EV_CB_DECLARE(type) struct my_coro *cb; |
3835 | \& #define EV_CB_INVOKE(watcher) switch_to ((watcher)\->cb); |
4192 | \& #define EV_CB_INVOKE(watcher) switch_to ((watcher)\->cb) |
3836 | \& #include "../libev/ev.h" |
4193 | \& #include "../libev/ev.h" |
3837 | \& |
4194 | \& |
3838 | \& // my_ev.c |
4195 | \& // my_ev.c |
3839 | \& #define EV_H "my_ev.h" |
4196 | \& #define EV_H "my_ev.h" |
3840 | \& #include "../libev/ev.c" |
4197 | \& #include "../libev/ev.c" |
… | |
… | |
3873 | .IP "\(bu" 4 |
4230 | .IP "\(bu" 4 |
3874 | The libev emulation is \fInot\fR \s-1ABI\s0 compatible to libevent, you need |
4231 | The libev emulation is \fInot\fR \s-1ABI\s0 compatible to libevent, you need |
3875 | to use the libev header file and library. |
4232 | to use the libev header file and library. |
3876 | .SH "\*(C+ SUPPORT" |
4233 | .SH "\*(C+ SUPPORT" |
3877 | .IX Header " SUPPORT" |
4234 | .IX Header " SUPPORT" |
|
|
4235 | .SS "C \s-1API\s0" |
|
|
4236 | .IX Subsection "C API" |
|
|
4237 | The normal C \s-1API\s0 should work fine when used from \*(C+: both ev.h and the |
|
|
4238 | libev sources can be compiled as \*(C+. Therefore, code that uses the C \s-1API\s0 |
|
|
4239 | will work fine. |
|
|
4240 | .PP |
|
|
4241 | Proper exception specifications might have to be added to callbacks passed |
|
|
4242 | to libev: exceptions may be thrown only from watcher callbacks, all other |
|
|
4243 | callbacks (allocator, syserr, loop acquire/release and periodic reschedule |
|
|
4244 | callbacks) must not throw exceptions, and might need a \f(CW\*(C`noexcept\*(C'\fR |
|
|
4245 | specification. If you have code that needs to be compiled as both C and |
|
|
4246 | \&\*(C+ you can use the \f(CW\*(C`EV_NOEXCEPT\*(C'\fR macro for this: |
|
|
4247 | .PP |
|
|
4248 | .Vb 6 |
|
|
4249 | \& static void |
|
|
4250 | \& fatal_error (const char *msg) EV_NOEXCEPT |
|
|
4251 | \& { |
|
|
4252 | \& perror (msg); |
|
|
4253 | \& abort (); |
|
|
4254 | \& } |
|
|
4255 | \& |
|
|
4256 | \& ... |
|
|
4257 | \& ev_set_syserr_cb (fatal_error); |
|
|
4258 | .Ve |
|
|
4259 | .PP |
|
|
4260 | The only \s-1API\s0 functions that can currently throw exceptions are \f(CW\*(C`ev_run\*(C'\fR, |
|
|
4261 | \&\f(CW\*(C`ev_invoke\*(C'\fR, \f(CW\*(C`ev_invoke_pending\*(C'\fR and \f(CW\*(C`ev_loop_destroy\*(C'\fR (the latter |
|
|
4262 | because it runs cleanup watchers). |
|
|
4263 | .PP |
|
|
4264 | Throwing exceptions in watcher callbacks is only supported if libev itself |
|
|
4265 | is compiled with a \*(C+ compiler or your C and \*(C+ environments allow |
|
|
4266 | throwing exceptions through C libraries (most do). |
|
|
4267 | .SS "\*(C+ \s-1API\s0" |
|
|
4268 | .IX Subsection " API" |
3878 | Libev comes with some simplistic wrapper classes for \*(C+ that mainly allow |
4269 | Libev comes with some simplistic wrapper classes for \*(C+ that mainly allow |
3879 | you to use some convenience methods to start/stop watchers and also change |
4270 | you to use some convenience methods to start/stop watchers and also change |
3880 | the callback model to a model using method callbacks on objects. |
4271 | the callback model to a model using method callbacks on objects. |
3881 | .PP |
4272 | .PP |
3882 | To use it, |
4273 | To use it, |
… | |
… | |
3898 | Currently, functions, static and non-static member functions and classes |
4289 | Currently, functions, static and non-static member functions and classes |
3899 | with \f(CW\*(C`operator ()\*(C'\fR can be used as callbacks. Other types should be easy |
4290 | with \f(CW\*(C`operator ()\*(C'\fR can be used as callbacks. Other types should be easy |
3900 | to add as long as they only need one additional pointer for context. If |
4291 | to add as long as they only need one additional pointer for context. If |
3901 | you need support for other types of functors please contact the author |
4292 | you need support for other types of functors please contact the author |
3902 | (preferably after implementing it). |
4293 | (preferably after implementing it). |
|
|
4294 | .PP |
|
|
4295 | For all this to work, your \*(C+ compiler either has to use the same calling |
|
|
4296 | conventions as your C compiler (for static member functions), or you have |
|
|
4297 | to embed libev and compile libev itself as \*(C+. |
3903 | .PP |
4298 | .PP |
3904 | Here is a list of things available in the \f(CW\*(C`ev\*(C'\fR namespace: |
4299 | Here is a list of things available in the \f(CW\*(C`ev\*(C'\fR namespace: |
3905 | .ie n .IP """ev::READ"", ""ev::WRITE"" etc." 4 |
4300 | .ie n .IP """ev::READ"", ""ev::WRITE"" etc." 4 |
3906 | .el .IP "\f(CWev::READ\fR, \f(CWev::WRITE\fR etc." 4 |
4301 | .el .IP "\f(CWev::READ\fR, \f(CWev::WRITE\fR etc." 4 |
3907 | .IX Item "ev::READ, ev::WRITE etc." |
4302 | .IX Item "ev::READ, ev::WRITE etc." |
… | |
… | |
3915 | .el .IP "\f(CWev::io\fR, \f(CWev::timer\fR, \f(CWev::periodic\fR, \f(CWev::idle\fR, \f(CWev::sig\fR etc." 4 |
4310 | .el .IP "\f(CWev::io\fR, \f(CWev::timer\fR, \f(CWev::periodic\fR, \f(CWev::idle\fR, \f(CWev::sig\fR etc." 4 |
3916 | .IX Item "ev::io, ev::timer, ev::periodic, ev::idle, ev::sig etc." |
4311 | .IX Item "ev::io, ev::timer, ev::periodic, ev::idle, ev::sig etc." |
3917 | For each \f(CW\*(C`ev_TYPE\*(C'\fR watcher in \fIev.h\fR there is a corresponding class of |
4312 | For each \f(CW\*(C`ev_TYPE\*(C'\fR watcher in \fIev.h\fR there is a corresponding class of |
3918 | the same name in the \f(CW\*(C`ev\*(C'\fR namespace, with the exception of \f(CW\*(C`ev_signal\*(C'\fR |
4313 | the same name in the \f(CW\*(C`ev\*(C'\fR namespace, with the exception of \f(CW\*(C`ev_signal\*(C'\fR |
3919 | which is called \f(CW\*(C`ev::sig\*(C'\fR to avoid clashes with the \f(CW\*(C`signal\*(C'\fR macro |
4314 | which is called \f(CW\*(C`ev::sig\*(C'\fR to avoid clashes with the \f(CW\*(C`signal\*(C'\fR macro |
3920 | defines by many implementations. |
4315 | defined by many implementations. |
3921 | .Sp |
4316 | .Sp |
3922 | All of those classes have these methods: |
4317 | All of those classes have these methods: |
3923 | .RS 4 |
4318 | .RS 4 |
3924 | .IP "ev::TYPE::TYPE ()" 4 |
4319 | .IP "ev::TYPE::TYPE ()" 4 |
3925 | .IX Item "ev::TYPE::TYPE ()" |
4320 | .IX Item "ev::TYPE::TYPE ()" |
… | |
… | |
3988 | \& void operator() (ev::io &w, int revents) |
4383 | \& void operator() (ev::io &w, int revents) |
3989 | \& { |
4384 | \& { |
3990 | \& ... |
4385 | \& ... |
3991 | \& } |
4386 | \& } |
3992 | \& } |
4387 | \& } |
3993 | \& |
4388 | \& |
3994 | \& myfunctor f; |
4389 | \& myfunctor f; |
3995 | \& |
4390 | \& |
3996 | \& ev::io w; |
4391 | \& ev::io w; |
3997 | \& w.set (&f); |
4392 | \& w.set (&f); |
3998 | .Ve |
4393 | .Ve |
… | |
… | |
4016 | .IX Item "w->set (loop)" |
4411 | .IX Item "w->set (loop)" |
4017 | Associates a different \f(CW\*(C`struct ev_loop\*(C'\fR with this watcher. You can only |
4412 | Associates a different \f(CW\*(C`struct ev_loop\*(C'\fR with this watcher. You can only |
4018 | do this when the watcher is inactive (and not pending either). |
4413 | do this when the watcher is inactive (and not pending either). |
4019 | .IP "w\->set ([arguments])" 4 |
4414 | .IP "w\->set ([arguments])" 4 |
4020 | .IX Item "w->set ([arguments])" |
4415 | .IX Item "w->set ([arguments])" |
4021 | Basically the same as \f(CW\*(C`ev_TYPE_set\*(C'\fR, with the same arguments. Either this |
4416 | Basically the same as \f(CW\*(C`ev_TYPE_set\*(C'\fR (except for \f(CW\*(C`ev::embed\*(C'\fR watchers>), |
4022 | method or a suitable start method must be called at least once. Unlike the |
4417 | with the same arguments. Either this method or a suitable start method |
4023 | C counterpart, an active watcher gets automatically stopped and restarted |
4418 | must be called at least once. Unlike the C counterpart, an active watcher |
4024 | when reconfiguring it with this method. |
4419 | gets automatically stopped and restarted when reconfiguring it with this |
|
|
4420 | method. |
|
|
4421 | .Sp |
|
|
4422 | For \f(CW\*(C`ev::embed\*(C'\fR watchers this method is called \f(CW\*(C`set_embed\*(C'\fR, to avoid |
|
|
4423 | clashing with the \f(CW\*(C`set (loop)\*(C'\fR method. |
|
|
4424 | .Sp |
|
|
4425 | For \f(CW\*(C`ev::io\*(C'\fR watchers there is an additional \f(CW\*(C`set\*(C'\fR method that acepts a |
|
|
4426 | new event mask only, and internally calls \f(CW\*(C`ev_io_modfify\*(C'\fR. |
4025 | .IP "w\->start ()" 4 |
4427 | .IP "w\->start ()" 4 |
4026 | .IX Item "w->start ()" |
4428 | .IX Item "w->start ()" |
4027 | Starts the watcher. Note that there is no \f(CW\*(C`loop\*(C'\fR argument, as the |
4429 | Starts the watcher. Note that there is no \f(CW\*(C`loop\*(C'\fR argument, as the |
4028 | constructor already stores the event loop. |
4430 | constructor already stores the event loop. |
4029 | .IP "w\->start ([arguments])" 4 |
4431 | .IP "w\->start ([arguments])" 4 |
… | |
… | |
4056 | .PP |
4458 | .PP |
4057 | .Vb 5 |
4459 | .Vb 5 |
4058 | \& class myclass |
4460 | \& class myclass |
4059 | \& { |
4461 | \& { |
4060 | \& ev::io io ; void io_cb (ev::io &w, int revents); |
4462 | \& ev::io io ; void io_cb (ev::io &w, int revents); |
4061 | \& ev::io2 io2 ; void io2_cb (ev::io &w, int revents); |
4463 | \& ev::io io2 ; void io2_cb (ev::io &w, int revents); |
4062 | \& ev::idle idle; void idle_cb (ev::idle &w, int revents); |
4464 | \& ev::idle idle; void idle_cb (ev::idle &w, int revents); |
4063 | \& |
4465 | \& |
4064 | \& myclass (int fd) |
4466 | \& myclass (int fd) |
4065 | \& { |
4467 | \& { |
4066 | \& io .set <myclass, &myclass::io_cb > (this); |
4468 | \& io .set <myclass, &myclass::io_cb > (this); |
… | |
… | |
4087 | there are additional modules that implement libev-compatible interfaces |
4489 | there are additional modules that implement libev-compatible interfaces |
4088 | to \f(CW\*(C`libadns\*(C'\fR (\f(CW\*(C`EV::ADNS\*(C'\fR, but \f(CW\*(C`AnyEvent::DNS\*(C'\fR is preferred nowadays), |
4490 | to \f(CW\*(C`libadns\*(C'\fR (\f(CW\*(C`EV::ADNS\*(C'\fR, but \f(CW\*(C`AnyEvent::DNS\*(C'\fR is preferred nowadays), |
4089 | \&\f(CW\*(C`Net::SNMP\*(C'\fR (\f(CW\*(C`Net::SNMP::EV\*(C'\fR) and the \f(CW\*(C`libglib\*(C'\fR event core (\f(CW\*(C`Glib::EV\*(C'\fR |
4491 | \&\f(CW\*(C`Net::SNMP\*(C'\fR (\f(CW\*(C`Net::SNMP::EV\*(C'\fR) and the \f(CW\*(C`libglib\*(C'\fR event core (\f(CW\*(C`Glib::EV\*(C'\fR |
4090 | and \f(CW\*(C`EV::Glib\*(C'\fR). |
4492 | and \f(CW\*(C`EV::Glib\*(C'\fR). |
4091 | .Sp |
4493 | .Sp |
4092 | It can be found and installed via \s-1CPAN\s0, its homepage is at |
4494 | It can be found and installed via \s-1CPAN,\s0 its homepage is at |
4093 | <http://software.schmorp.de/pkg/EV>. |
4495 | <http://software.schmorp.de/pkg/EV>. |
4094 | .IP "Python" 4 |
4496 | .IP "Python" 4 |
4095 | .IX Item "Python" |
4497 | .IX Item "Python" |
4096 | Python bindings can be found at <http://code.google.com/p/pyev/>. It |
4498 | Python bindings can be found at <http://code.google.com/p/pyev/>. It |
4097 | seems to be quite complete and well-documented. |
4499 | seems to be quite complete and well-documented. |
… | |
… | |
4109 | A haskell binding to libev is available at |
4511 | A haskell binding to libev is available at |
4110 | <http://hackage.haskell.org/cgi\-bin/hackage\-scripts/package/hlibev>. |
4512 | <http://hackage.haskell.org/cgi\-bin/hackage\-scripts/package/hlibev>. |
4111 | .IP "D" 4 |
4513 | .IP "D" 4 |
4112 | .IX Item "D" |
4514 | .IX Item "D" |
4113 | Leandro Lucarella has written a D language binding (\fIev.d\fR) for libev, to |
4515 | Leandro Lucarella has written a D language binding (\fIev.d\fR) for libev, to |
4114 | be found at <http://proj.llucax.com.ar/wiki/evd>. |
4516 | be found at <http://www.llucax.com.ar/proj/ev.d/index.html>. |
4115 | .IP "Ocaml" 4 |
4517 | .IP "Ocaml" 4 |
4116 | .IX Item "Ocaml" |
4518 | .IX Item "Ocaml" |
4117 | Erkki Seppala has written Ocaml bindings for libev, to be found at |
4519 | Erkki Seppala has written Ocaml bindings for libev, to be found at |
4118 | <http://modeemi.cs.tut.fi/~flux/software/ocaml\-ev/>. |
4520 | <http://modeemi.cs.tut.fi/~flux/software/ocaml\-ev/>. |
4119 | .IP "Lua" 4 |
4521 | .IP "Lua" 4 |
4120 | .IX Item "Lua" |
4522 | .IX Item "Lua" |
4121 | Brian Maher has written a partial interface to libev for lua (at the |
4523 | Brian Maher has written a partial interface to libev for lua (at the |
4122 | time of this writing, only \f(CW\*(C`ev_io\*(C'\fR and \f(CW\*(C`ev_timer\*(C'\fR), to be found at |
4524 | time of this writing, only \f(CW\*(C`ev_io\*(C'\fR and \f(CW\*(C`ev_timer\*(C'\fR), to be found at |
4123 | <http://github.com/brimworks/lua\-ev>. |
4525 | <http://github.com/brimworks/lua\-ev>. |
|
|
4526 | .IP "Javascript" 4 |
|
|
4527 | .IX Item "Javascript" |
|
|
4528 | Node.js (<http://nodejs.org>) uses libev as the underlying event library. |
|
|
4529 | .IP "Others" 4 |
|
|
4530 | .IX Item "Others" |
|
|
4531 | There are others, and I stopped counting. |
4124 | .SH "MACRO MAGIC" |
4532 | .SH "MACRO MAGIC" |
4125 | .IX Header "MACRO MAGIC" |
4533 | .IX Header "MACRO MAGIC" |
4126 | Libev can be compiled with a variety of options, the most fundamental |
4534 | Libev can be compiled with a variety of options, the most fundamental |
4127 | of which is \f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. This option determines whether (most) |
4535 | of which is \f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. This option determines whether (most) |
4128 | functions and callbacks have an initial \f(CW\*(C`struct ev_loop *\*(C'\fR argument. |
4536 | functions and callbacks have an initial \f(CW\*(C`struct ev_loop *\*(C'\fR argument. |
… | |
… | |
4163 | suitable for use with \f(CW\*(C`EV_A\*(C'\fR. |
4571 | suitable for use with \f(CW\*(C`EV_A\*(C'\fR. |
4164 | .ie n .IP """EV_DEFAULT"", ""EV_DEFAULT_""" 4 |
4572 | .ie n .IP """EV_DEFAULT"", ""EV_DEFAULT_""" 4 |
4165 | .el .IP "\f(CWEV_DEFAULT\fR, \f(CWEV_DEFAULT_\fR" 4 |
4573 | .el .IP "\f(CWEV_DEFAULT\fR, \f(CWEV_DEFAULT_\fR" 4 |
4166 | .IX Item "EV_DEFAULT, EV_DEFAULT_" |
4574 | .IX Item "EV_DEFAULT, EV_DEFAULT_" |
4167 | Similar to the other two macros, this gives you the value of the default |
4575 | Similar to the other two macros, this gives you the value of the default |
4168 | loop, if multiple loops are supported (\*(L"ev loop default\*(R"). |
4576 | loop, if multiple loops are supported (\*(L"ev loop default\*(R"). The default loop |
|
|
4577 | will be initialised if it isn't already initialised. |
|
|
4578 | .Sp |
|
|
4579 | For non-multiplicity builds, these macros do nothing, so you always have |
|
|
4580 | to initialise the loop somewhere. |
4169 | .ie n .IP """EV_DEFAULT_UC"", ""EV_DEFAULT_UC_""" 4 |
4581 | .ie n .IP """EV_DEFAULT_UC"", ""EV_DEFAULT_UC_""" 4 |
4170 | .el .IP "\f(CWEV_DEFAULT_UC\fR, \f(CWEV_DEFAULT_UC_\fR" 4 |
4582 | .el .IP "\f(CWEV_DEFAULT_UC\fR, \f(CWEV_DEFAULT_UC_\fR" 4 |
4171 | .IX Item "EV_DEFAULT_UC, EV_DEFAULT_UC_" |
4583 | .IX Item "EV_DEFAULT_UC, EV_DEFAULT_UC_" |
4172 | Usage identical to \f(CW\*(C`EV_DEFAULT\*(C'\fR and \f(CW\*(C`EV_DEFAULT_\*(C'\fR, but requires that the |
4584 | Usage identical to \f(CW\*(C`EV_DEFAULT\*(C'\fR and \f(CW\*(C`EV_DEFAULT_\*(C'\fR, but requires that the |
4173 | default loop has been initialised (\f(CW\*(C`UC\*(C'\fR == unchecked). Their behaviour |
4585 | default loop has been initialised (\f(CW\*(C`UC\*(C'\fR == unchecked). Their behaviour |
… | |
… | |
4207 | .SS "\s-1FILESETS\s0" |
4619 | .SS "\s-1FILESETS\s0" |
4208 | .IX Subsection "FILESETS" |
4620 | .IX Subsection "FILESETS" |
4209 | Depending on what features you need you need to include one or more sets of files |
4621 | Depending on what features you need you need to include one or more sets of files |
4210 | in your application. |
4622 | in your application. |
4211 | .PP |
4623 | .PP |
4212 | \fI\s-1CORE\s0 \s-1EVENT\s0 \s-1LOOP\s0\fR |
4624 | \fI\s-1CORE EVENT LOOP\s0\fR |
4213 | .IX Subsection "CORE EVENT LOOP" |
4625 | .IX Subsection "CORE EVENT LOOP" |
4214 | .PP |
4626 | .PP |
4215 | To include only the libev core (all the \f(CW\*(C`ev_*\*(C'\fR functions), with manual |
4627 | To include only the libev core (all the \f(CW\*(C`ev_*\*(C'\fR functions), with manual |
4216 | configuration (no autoconf): |
4628 | configuration (no autoconf): |
4217 | .PP |
4629 | .PP |
… | |
… | |
4244 | \& ev_vars.h |
4656 | \& ev_vars.h |
4245 | \& ev_wrap.h |
4657 | \& ev_wrap.h |
4246 | \& |
4658 | \& |
4247 | \& ev_win32.c required on win32 platforms only |
4659 | \& ev_win32.c required on win32 platforms only |
4248 | \& |
4660 | \& |
4249 | \& ev_select.c only when select backend is enabled (which is enabled by default) |
4661 | \& ev_select.c only when select backend is enabled |
4250 | \& ev_poll.c only when poll backend is enabled (disabled by default) |
4662 | \& ev_poll.c only when poll backend is enabled |
4251 | \& ev_epoll.c only when the epoll backend is enabled (disabled by default) |
4663 | \& ev_epoll.c only when the epoll backend is enabled |
|
|
4664 | \& ev_linuxaio.c only when the linux aio backend is enabled |
|
|
4665 | \& ev_iouring.c only when the linux io_uring backend is enabled |
4252 | \& ev_kqueue.c only when the kqueue backend is enabled (disabled by default) |
4666 | \& ev_kqueue.c only when the kqueue backend is enabled |
4253 | \& ev_port.c only when the solaris port backend is enabled (disabled by default) |
4667 | \& ev_port.c only when the solaris port backend is enabled |
4254 | .Ve |
4668 | .Ve |
4255 | .PP |
4669 | .PP |
4256 | \&\fIev.c\fR includes the backend files directly when enabled, so you only need |
4670 | \&\fIev.c\fR includes the backend files directly when enabled, so you only need |
4257 | to compile this single file. |
4671 | to compile this single file. |
4258 | .PP |
4672 | .PP |
4259 | \fI\s-1LIBEVENT\s0 \s-1COMPATIBILITY\s0 \s-1API\s0\fR |
4673 | \fI\s-1LIBEVENT COMPATIBILITY API\s0\fR |
4260 | .IX Subsection "LIBEVENT COMPATIBILITY API" |
4674 | .IX Subsection "LIBEVENT COMPATIBILITY API" |
4261 | .PP |
4675 | .PP |
4262 | To include the libevent compatibility \s-1API\s0, also include: |
4676 | To include the libevent compatibility \s-1API,\s0 also include: |
4263 | .PP |
4677 | .PP |
4264 | .Vb 1 |
4678 | .Vb 1 |
4265 | \& #include "event.c" |
4679 | \& #include "event.c" |
4266 | .Ve |
4680 | .Ve |
4267 | .PP |
4681 | .PP |
… | |
… | |
4269 | .PP |
4683 | .PP |
4270 | .Vb 1 |
4684 | .Vb 1 |
4271 | \& #include "event.h" |
4685 | \& #include "event.h" |
4272 | .Ve |
4686 | .Ve |
4273 | .PP |
4687 | .PP |
4274 | in the files that want to use the libevent \s-1API\s0. This also includes \fIev.h\fR. |
4688 | in the files that want to use the libevent \s-1API.\s0 This also includes \fIev.h\fR. |
4275 | .PP |
4689 | .PP |
4276 | You need the following additional files for this: |
4690 | You need the following additional files for this: |
4277 | .PP |
4691 | .PP |
4278 | .Vb 2 |
4692 | .Vb 2 |
4279 | \& event.h |
4693 | \& event.h |
4280 | \& event.c |
4694 | \& event.c |
4281 | .Ve |
4695 | .Ve |
4282 | .PP |
4696 | .PP |
4283 | \fI\s-1AUTOCONF\s0 \s-1SUPPORT\s0\fR |
4697 | \fI\s-1AUTOCONF SUPPORT\s0\fR |
4284 | .IX Subsection "AUTOCONF SUPPORT" |
4698 | .IX Subsection "AUTOCONF SUPPORT" |
4285 | .PP |
4699 | .PP |
4286 | Instead of using \f(CW\*(C`EV_STANDALONE=1\*(C'\fR and providing your configuration in |
4700 | Instead of using \f(CW\*(C`EV_STANDALONE=1\*(C'\fR and providing your configuration in |
4287 | whatever way you want, you can also \f(CW\*(C`m4_include([libev.m4])\*(C'\fR in your |
4701 | whatever way you want, you can also \f(CW\*(C`m4_include([libev.m4])\*(C'\fR in your |
4288 | \&\fIconfigure.ac\fR and leave \f(CW\*(C`EV_STANDALONE\*(C'\fR undefined. \fIev.c\fR will then |
4702 | \&\fIconfigure.ac\fR and leave \f(CW\*(C`EV_STANDALONE\*(C'\fR undefined. \fIev.c\fR will then |
… | |
… | |
4291 | For this of course you need the m4 file: |
4705 | For this of course you need the m4 file: |
4292 | .PP |
4706 | .PP |
4293 | .Vb 1 |
4707 | .Vb 1 |
4294 | \& libev.m4 |
4708 | \& libev.m4 |
4295 | .Ve |
4709 | .Ve |
4296 | .SS "\s-1PREPROCESSOR\s0 \s-1SYMBOLS/MACROS\s0" |
4710 | .SS "\s-1PREPROCESSOR SYMBOLS/MACROS\s0" |
4297 | .IX Subsection "PREPROCESSOR SYMBOLS/MACROS" |
4711 | .IX Subsection "PREPROCESSOR SYMBOLS/MACROS" |
4298 | Libev can be configured via a variety of preprocessor symbols you have to |
4712 | Libev can be configured via a variety of preprocessor symbols you have to |
4299 | define before including (or compiling) any of its files. The default in |
4713 | define before including (or compiling) any of its files. The default in |
4300 | the absence of autoconf is documented for every option. |
4714 | the absence of autoconf is documented for every option. |
4301 | .PP |
4715 | .PP |
4302 | Symbols marked with \*(L"(h)\*(R" do not change the \s-1ABI\s0, and can have different |
4716 | Symbols marked with \*(L"(h)\*(R" do not change the \s-1ABI,\s0 and can have different |
4303 | values when compiling libev vs. including \fIev.h\fR, so it is permissible |
4717 | values when compiling libev vs. including \fIev.h\fR, so it is permissible |
4304 | to redefine them before including \fIev.h\fR without breaking compatibility |
4718 | to redefine them before including \fIev.h\fR without breaking compatibility |
4305 | to a compiled library. All other symbols change the \s-1ABI\s0, which means all |
4719 | to a compiled library. All other symbols change the \s-1ABI,\s0 which means all |
4306 | users of libev and the libev code itself must be compiled with compatible |
4720 | users of libev and the libev code itself must be compiled with compatible |
4307 | settings. |
4721 | settings. |
4308 | .IP "\s-1EV_COMPAT3\s0 (h)" 4 |
4722 | .IP "\s-1EV_COMPAT3\s0 (h)" 4 |
4309 | .IX Item "EV_COMPAT3 (h)" |
4723 | .IX Item "EV_COMPAT3 (h)" |
4310 | Backwards compatibility is a major concern for libev. This is why this |
4724 | Backwards compatibility is a major concern for libev. This is why this |
… | |
… | |
4328 | supported). It will also not define any of the structs usually found in |
4742 | supported). It will also not define any of the structs usually found in |
4329 | \&\fIevent.h\fR that are not directly supported by the libev core alone. |
4743 | \&\fIevent.h\fR that are not directly supported by the libev core alone. |
4330 | .Sp |
4744 | .Sp |
4331 | In standalone mode, libev will still try to automatically deduce the |
4745 | In standalone mode, libev will still try to automatically deduce the |
4332 | configuration, but has to be more conservative. |
4746 | configuration, but has to be more conservative. |
|
|
4747 | .IP "\s-1EV_USE_FLOOR\s0" 4 |
|
|
4748 | .IX Item "EV_USE_FLOOR" |
|
|
4749 | If defined to be \f(CW1\fR, libev will use the \f(CW\*(C`floor ()\*(C'\fR function for its |
|
|
4750 | periodic reschedule calculations, otherwise libev will fall back on a |
|
|
4751 | portable (slower) implementation. If you enable this, you usually have to |
|
|
4752 | link against libm or something equivalent. Enabling this when the \f(CW\*(C`floor\*(C'\fR |
|
|
4753 | function is not available will fail, so the safe default is to not enable |
|
|
4754 | this. |
4333 | .IP "\s-1EV_USE_MONOTONIC\s0" 4 |
4755 | .IP "\s-1EV_USE_MONOTONIC\s0" 4 |
4334 | .IX Item "EV_USE_MONOTONIC" |
4756 | .IX Item "EV_USE_MONOTONIC" |
4335 | If defined to be \f(CW1\fR, libev will try to detect the availability of the |
4757 | If defined to be \f(CW1\fR, libev will try to detect the availability of the |
4336 | monotonic clock option at both compile time and runtime. Otherwise no |
4758 | monotonic clock option at both compile time and runtime. Otherwise no |
4337 | use of the monotonic clock option will be attempted. If you enable this, |
4759 | use of the monotonic clock option will be attempted. If you enable this, |
… | |
… | |
4361 | higher, as it simplifies linking (no need for \f(CW\*(C`\-lrt\*(C'\fR). |
4783 | higher, as it simplifies linking (no need for \f(CW\*(C`\-lrt\*(C'\fR). |
4362 | .IP "\s-1EV_USE_NANOSLEEP\s0" 4 |
4784 | .IP "\s-1EV_USE_NANOSLEEP\s0" 4 |
4363 | .IX Item "EV_USE_NANOSLEEP" |
4785 | .IX Item "EV_USE_NANOSLEEP" |
4364 | If defined to be \f(CW1\fR, libev will assume that \f(CW\*(C`nanosleep ()\*(C'\fR is available |
4786 | If defined to be \f(CW1\fR, libev will assume that \f(CW\*(C`nanosleep ()\*(C'\fR is available |
4365 | and will use it for delays. Otherwise it will use \f(CW\*(C`select ()\*(C'\fR. |
4787 | and will use it for delays. Otherwise it will use \f(CW\*(C`select ()\*(C'\fR. |
|
|
4788 | .IP "\s-1EV_USE_EVENTFD\s0" 4 |
|
|
4789 | .IX Item "EV_USE_EVENTFD" |
|
|
4790 | If defined to be \f(CW1\fR, then libev will assume that \f(CW\*(C`eventfd ()\*(C'\fR is |
|
|
4791 | available and will probe for kernel support at runtime. This will improve |
|
|
4792 | \&\f(CW\*(C`ev_signal\*(C'\fR and \f(CW\*(C`ev_async\*(C'\fR performance and reduce resource consumption. |
|
|
4793 | If undefined, it will be enabled if the headers indicate GNU/Linux + Glibc |
|
|
4794 | 2.7 or newer, otherwise disabled. |
|
|
4795 | .IP "\s-1EV_USE_SIGNALFD\s0" 4 |
|
|
4796 | .IX Item "EV_USE_SIGNALFD" |
|
|
4797 | If defined to be \f(CW1\fR, then libev will assume that \f(CW\*(C`signalfd ()\*(C'\fR is |
|
|
4798 | available and will probe for kernel support at runtime. This enables |
|
|
4799 | the use of \s-1EVFLAG_SIGNALFD\s0 for faster and simpler signal handling. If |
|
|
4800 | undefined, it will be enabled if the headers indicate GNU/Linux + Glibc |
|
|
4801 | 2.7 or newer, otherwise disabled. |
|
|
4802 | .IP "\s-1EV_USE_TIMERFD\s0" 4 |
|
|
4803 | .IX Item "EV_USE_TIMERFD" |
|
|
4804 | If defined to be \f(CW1\fR, then libev will assume that \f(CW\*(C`timerfd ()\*(C'\fR is |
|
|
4805 | available and will probe for kernel support at runtime. This allows |
|
|
4806 | libev to detect time jumps accurately. If undefined, it will be enabled |
|
|
4807 | if the headers indicate GNU/Linux + Glibc 2.8 or newer and define |
|
|
4808 | \&\f(CW\*(C`TFD_TIMER_CANCEL_ON_SET\*(C'\fR, otherwise disabled. |
4366 | .IP "\s-1EV_USE_EVENTFD\s0" 4 |
4809 | .IP "\s-1EV_USE_EVENTFD\s0" 4 |
4367 | .IX Item "EV_USE_EVENTFD" |
4810 | .IX Item "EV_USE_EVENTFD" |
4368 | If defined to be \f(CW1\fR, then libev will assume that \f(CW\*(C`eventfd ()\*(C'\fR is |
4811 | If defined to be \f(CW1\fR, then libev will assume that \f(CW\*(C`eventfd ()\*(C'\fR is |
4369 | available and will probe for kernel support at runtime. This will improve |
4812 | available and will probe for kernel support at runtime. This will improve |
4370 | \&\f(CW\*(C`ev_signal\*(C'\fR and \f(CW\*(C`ev_async\*(C'\fR performance and reduce resource consumption. |
4813 | \&\f(CW\*(C`ev_signal\*(C'\fR and \f(CW\*(C`ev_async\*(C'\fR performance and reduce resource consumption. |
… | |
… | |
4411 | .IX Item "EV_WIN32_CLOSE_FD(fd)" |
4854 | .IX Item "EV_WIN32_CLOSE_FD(fd)" |
4412 | If programs implement their own fd to handle mapping on win32, then this |
4855 | If programs implement their own fd to handle mapping on win32, then this |
4413 | macro can be used to override the \f(CW\*(C`close\*(C'\fR function, useful to unregister |
4856 | macro can be used to override the \f(CW\*(C`close\*(C'\fR function, useful to unregister |
4414 | file descriptors again. Note that the replacement function has to close |
4857 | file descriptors again. Note that the replacement function has to close |
4415 | the underlying \s-1OS\s0 handle. |
4858 | the underlying \s-1OS\s0 handle. |
|
|
4859 | .IP "\s-1EV_USE_WSASOCKET\s0" 4 |
|
|
4860 | .IX Item "EV_USE_WSASOCKET" |
|
|
4861 | If defined to be \f(CW1\fR, libev will use \f(CW\*(C`WSASocket\*(C'\fR to create its internal |
|
|
4862 | communication socket, which works better in some environments. Otherwise, |
|
|
4863 | the normal \f(CW\*(C`socket\*(C'\fR function will be used, which works better in other |
|
|
4864 | environments. |
4416 | .IP "\s-1EV_USE_POLL\s0" 4 |
4865 | .IP "\s-1EV_USE_POLL\s0" 4 |
4417 | .IX Item "EV_USE_POLL" |
4866 | .IX Item "EV_USE_POLL" |
4418 | If defined to be \f(CW1\fR, libev will compile in support for the \f(CW\*(C`poll\*(C'\fR(2) |
4867 | If defined to be \f(CW1\fR, libev will compile in support for the \f(CW\*(C`poll\*(C'\fR(2) |
4419 | backend. Otherwise it will be enabled on non\-win32 platforms. It |
4868 | backend. Otherwise it will be enabled on non\-win32 platforms. It |
4420 | takes precedence over select. |
4869 | takes precedence over select. |
… | |
… | |
4423 | If defined to be \f(CW1\fR, libev will compile in support for the Linux |
4872 | If defined to be \f(CW1\fR, libev will compile in support for the Linux |
4424 | \&\f(CW\*(C`epoll\*(C'\fR(7) backend. Its availability will be detected at runtime, |
4873 | \&\f(CW\*(C`epoll\*(C'\fR(7) backend. Its availability will be detected at runtime, |
4425 | otherwise another method will be used as fallback. This is the preferred |
4874 | otherwise another method will be used as fallback. This is the preferred |
4426 | backend for GNU/Linux systems. If undefined, it will be enabled if the |
4875 | backend for GNU/Linux systems. If undefined, it will be enabled if the |
4427 | headers indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
4876 | headers indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
|
|
4877 | .IP "\s-1EV_USE_LINUXAIO\s0" 4 |
|
|
4878 | .IX Item "EV_USE_LINUXAIO" |
|
|
4879 | If defined to be \f(CW1\fR, libev will compile in support for the Linux aio |
|
|
4880 | backend (\f(CW\*(C`EV_USE_EPOLL\*(C'\fR must also be enabled). If undefined, it will be |
|
|
4881 | enabled on linux, otherwise disabled. |
|
|
4882 | .IP "\s-1EV_USE_IOURING\s0" 4 |
|
|
4883 | .IX Item "EV_USE_IOURING" |
|
|
4884 | If defined to be \f(CW1\fR, libev will compile in support for the Linux |
|
|
4885 | io_uring backend (\f(CW\*(C`EV_USE_EPOLL\*(C'\fR must also be enabled). Due to it's |
|
|
4886 | current limitations it has to be requested explicitly. If undefined, it |
|
|
4887 | will be enabled on linux, otherwise disabled. |
4428 | .IP "\s-1EV_USE_KQUEUE\s0" 4 |
4888 | .IP "\s-1EV_USE_KQUEUE\s0" 4 |
4429 | .IX Item "EV_USE_KQUEUE" |
4889 | .IX Item "EV_USE_KQUEUE" |
4430 | If defined to be \f(CW1\fR, libev will compile in support for the \s-1BSD\s0 style |
4890 | If defined to be \f(CW1\fR, libev will compile in support for the \s-1BSD\s0 style |
4431 | \&\f(CW\*(C`kqueue\*(C'\fR(2) backend. Its actual availability will be detected at runtime, |
4891 | \&\f(CW\*(C`kqueue\*(C'\fR(2) backend. Its actual availability will be detected at runtime, |
4432 | otherwise another method will be used as fallback. This is the preferred |
4892 | otherwise another method will be used as fallback. This is the preferred |
… | |
… | |
4449 | .IX Item "EV_USE_INOTIFY" |
4909 | .IX Item "EV_USE_INOTIFY" |
4450 | If defined to be \f(CW1\fR, libev will compile in support for the Linux inotify |
4910 | If defined to be \f(CW1\fR, libev will compile in support for the Linux inotify |
4451 | interface to speed up \f(CW\*(C`ev_stat\*(C'\fR watchers. Its actual availability will |
4911 | interface to speed up \f(CW\*(C`ev_stat\*(C'\fR watchers. Its actual availability will |
4452 | be detected at runtime. If undefined, it will be enabled if the headers |
4912 | be detected at runtime. If undefined, it will be enabled if the headers |
4453 | indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
4913 | indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
|
|
4914 | .IP "\s-1EV_NO_SMP\s0" 4 |
|
|
4915 | .IX Item "EV_NO_SMP" |
|
|
4916 | If defined to be \f(CW1\fR, libev will assume that memory is always coherent |
|
|
4917 | between threads, that is, threads can be used, but threads never run on |
|
|
4918 | different cpus (or different cpu cores). This reduces dependencies |
|
|
4919 | and makes libev faster. |
|
|
4920 | .IP "\s-1EV_NO_THREADS\s0" 4 |
|
|
4921 | .IX Item "EV_NO_THREADS" |
|
|
4922 | If defined to be \f(CW1\fR, libev will assume that it will never be called from |
|
|
4923 | different threads (that includes signal handlers), which is a stronger |
|
|
4924 | assumption than \f(CW\*(C`EV_NO_SMP\*(C'\fR, above. This reduces dependencies and makes |
|
|
4925 | libev faster. |
4454 | .IP "\s-1EV_ATOMIC_T\s0" 4 |
4926 | .IP "\s-1EV_ATOMIC_T\s0" 4 |
4455 | .IX Item "EV_ATOMIC_T" |
4927 | .IX Item "EV_ATOMIC_T" |
4456 | Libev requires an integer type (suitable for storing \f(CW0\fR or \f(CW1\fR) whose |
4928 | Libev requires an integer type (suitable for storing \f(CW0\fR or \f(CW1\fR) whose |
4457 | access is atomic with respect to other threads or signal contexts. No such |
4929 | access is atomic with respect to other threads or signal contexts. No |
4458 | type is easily found in the C language, so you can provide your own type |
4930 | such type is easily found in the C language, so you can provide your own |
4459 | that you know is safe for your purposes. It is used both for signal handler \*(L"locking\*(R" |
4931 | type that you know is safe for your purposes. It is used both for signal |
4460 | as well as for signal and thread safety in \f(CW\*(C`ev_async\*(C'\fR watchers. |
4932 | handler \*(L"locking\*(R" as well as for signal and thread safety in \f(CW\*(C`ev_async\*(C'\fR |
|
|
4933 | watchers. |
4461 | .Sp |
4934 | .Sp |
4462 | In the absence of this define, libev will use \f(CW\*(C`sig_atomic_t volatile\*(C'\fR |
4935 | In the absence of this define, libev will use \f(CW\*(C`sig_atomic_t volatile\*(C'\fR |
4463 | (from \fIsignal.h\fR), which is usually good enough on most platforms. |
4936 | (from \fIsignal.h\fR), which is usually good enough on most platforms. |
4464 | .IP "\s-1EV_H\s0 (h)" 4 |
4937 | .IP "\s-1EV_H\s0 (h)" 4 |
4465 | .IX Item "EV_H (h)" |
4938 | .IX Item "EV_H (h)" |
… | |
… | |
4486 | If undefined or defined to \f(CW1\fR, then all event-loop-specific functions |
4959 | If undefined or defined to \f(CW1\fR, then all event-loop-specific functions |
4487 | will have the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument, and you can create |
4960 | will have the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument, and you can create |
4488 | additional independent event loops. Otherwise there will be no support |
4961 | additional independent event loops. Otherwise there will be no support |
4489 | for multiple event loops and there is no first event loop pointer |
4962 | for multiple event loops and there is no first event loop pointer |
4490 | argument. Instead, all functions act on the single default loop. |
4963 | argument. Instead, all functions act on the single default loop. |
|
|
4964 | .Sp |
|
|
4965 | Note that \f(CW\*(C`EV_DEFAULT\*(C'\fR and \f(CW\*(C`EV_DEFAULT_\*(C'\fR will no longer provide a |
|
|
4966 | default loop when multiplicity is switched off \- you always have to |
|
|
4967 | initialise the loop manually in this case. |
4491 | .IP "\s-1EV_MINPRI\s0" 4 |
4968 | .IP "\s-1EV_MINPRI\s0" 4 |
4492 | .IX Item "EV_MINPRI" |
4969 | .IX Item "EV_MINPRI" |
4493 | .PD 0 |
4970 | .PD 0 |
4494 | .IP "\s-1EV_MAXPRI\s0" 4 |
4971 | .IP "\s-1EV_MAXPRI\s0" 4 |
4495 | .IX Item "EV_MAXPRI" |
4972 | .IX Item "EV_MAXPRI" |
… | |
… | |
4503 | all the priorities, so having many of them (hundreds) uses a lot of space |
4980 | all the priorities, so having many of them (hundreds) uses a lot of space |
4504 | and time, so using the defaults of five priorities (\-2 .. +2) is usually |
4981 | and time, so using the defaults of five priorities (\-2 .. +2) is usually |
4505 | fine. |
4982 | fine. |
4506 | .Sp |
4983 | .Sp |
4507 | If your embedding application does not need any priorities, defining these |
4984 | If your embedding application does not need any priorities, defining these |
4508 | both to \f(CW0\fR will save some memory and \s-1CPU\s0. |
4985 | both to \f(CW0\fR will save some memory and \s-1CPU.\s0 |
4509 | .IP "\s-1EV_PERIODIC_ENABLE\s0, \s-1EV_IDLE_ENABLE\s0, \s-1EV_EMBED_ENABLE\s0, \s-1EV_STAT_ENABLE\s0, \s-1EV_PREPARE_ENABLE\s0, \s-1EV_CHECK_ENABLE\s0, \s-1EV_FORK_ENABLE\s0, \s-1EV_SIGNAL_ENABLE\s0, \s-1EV_ASYNC_ENABLE\s0, \s-1EV_CHILD_ENABLE\s0." 4 |
4986 | .IP "\s-1EV_PERIODIC_ENABLE, EV_IDLE_ENABLE, EV_EMBED_ENABLE, EV_STAT_ENABLE, EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE, EV_ASYNC_ENABLE, EV_CHILD_ENABLE.\s0" 4 |
4510 | .IX Item "EV_PERIODIC_ENABLE, EV_IDLE_ENABLE, EV_EMBED_ENABLE, EV_STAT_ENABLE, EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE, EV_ASYNC_ENABLE, EV_CHILD_ENABLE." |
4987 | .IX Item "EV_PERIODIC_ENABLE, EV_IDLE_ENABLE, EV_EMBED_ENABLE, EV_STAT_ENABLE, EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE, EV_ASYNC_ENABLE, EV_CHILD_ENABLE." |
4511 | If undefined or defined to be \f(CW1\fR (and the platform supports it), then |
4988 | If undefined or defined to be \f(CW1\fR (and the platform supports it), then |
4512 | the respective watcher type is supported. If defined to be \f(CW0\fR, then it |
4989 | the respective watcher type is supported. If defined to be \f(CW0\fR, then it |
4513 | is not. Disabling watcher types mainly saves code size. |
4990 | is not. Disabling watcher types mainly saves code size. |
4514 | .IP "\s-1EV_FEATURES\s0" 4 |
4991 | .IP "\s-1EV_FEATURES\s0" 4 |
… | |
… | |
4531 | \& #define EV_CHILD_ENABLE 1 |
5008 | \& #define EV_CHILD_ENABLE 1 |
4532 | \& #define EV_ASYNC_ENABLE 1 |
5009 | \& #define EV_ASYNC_ENABLE 1 |
4533 | .Ve |
5010 | .Ve |
4534 | .Sp |
5011 | .Sp |
4535 | The actual value is a bitset, it can be a combination of the following |
5012 | The actual value is a bitset, it can be a combination of the following |
4536 | values: |
5013 | values (by default, all of these are enabled): |
4537 | .RS 4 |
5014 | .RS 4 |
4538 | .ie n .IP "1 \- faster/larger code" 4 |
5015 | .ie n .IP "1 \- faster/larger code" 4 |
4539 | .el .IP "\f(CW1\fR \- faster/larger code" 4 |
5016 | .el .IP "\f(CW1\fR \- faster/larger code" 4 |
4540 | .IX Item "1 - faster/larger code" |
5017 | .IX Item "1 - faster/larger code" |
4541 | Use larger code to speed up some operations. |
5018 | Use larger code to speed up some operations. |
… | |
… | |
4544 | code size by roughly 30% on amd64). |
5021 | code size by roughly 30% on amd64). |
4545 | .Sp |
5022 | .Sp |
4546 | When optimising for size, use of compiler flags such as \f(CW\*(C`\-Os\*(C'\fR with |
5023 | When optimising for size, use of compiler flags such as \f(CW\*(C`\-Os\*(C'\fR with |
4547 | gcc is recommended, as well as \f(CW\*(C`\-DNDEBUG\*(C'\fR, as libev contains a number of |
5024 | gcc is recommended, as well as \f(CW\*(C`\-DNDEBUG\*(C'\fR, as libev contains a number of |
4548 | assertions. |
5025 | assertions. |
|
|
5026 | .Sp |
|
|
5027 | The default is off when \f(CW\*(C`_\|_OPTIMIZE_SIZE_\|_\*(C'\fR is defined by your compiler |
|
|
5028 | (e.g. gcc with \f(CW\*(C`\-Os\*(C'\fR). |
4549 | .ie n .IP "2 \- faster/larger data structures" 4 |
5029 | .ie n .IP "2 \- faster/larger data structures" 4 |
4550 | .el .IP "\f(CW2\fR \- faster/larger data structures" 4 |
5030 | .el .IP "\f(CW2\fR \- faster/larger data structures" 4 |
4551 | .IX Item "2 - faster/larger data structures" |
5031 | .IX Item "2 - faster/larger data structures" |
4552 | Replaces the small 2\-heap for timer management by a faster 4\-heap, larger |
5032 | Replaces the small 2\-heap for timer management by a faster 4\-heap, larger |
4553 | hash table sizes and so on. This will usually further increase code size |
5033 | hash table sizes and so on. This will usually further increase code size |
4554 | and can additionally have an effect on the size of data structures at |
5034 | and can additionally have an effect on the size of data structures at |
4555 | runtime. |
5035 | runtime. |
|
|
5036 | .Sp |
|
|
5037 | The default is off when \f(CW\*(C`_\|_OPTIMIZE_SIZE_\|_\*(C'\fR is defined by your compiler |
|
|
5038 | (e.g. gcc with \f(CW\*(C`\-Os\*(C'\fR). |
4556 | .ie n .IP "4 \- full \s-1API\s0 configuration" 4 |
5039 | .ie n .IP "4 \- full \s-1API\s0 configuration" 4 |
4557 | .el .IP "\f(CW4\fR \- full \s-1API\s0 configuration" 4 |
5040 | .el .IP "\f(CW4\fR \- full \s-1API\s0 configuration" 4 |
4558 | .IX Item "4 - full API configuration" |
5041 | .IX Item "4 - full API configuration" |
4559 | This enables priorities (sets \f(CW\*(C`EV_MAXPRI\*(C'\fR=2 and \f(CW\*(C`EV_MINPRI\*(C'\fR=\-2), and |
5042 | This enables priorities (sets \f(CW\*(C`EV_MAXPRI\*(C'\fR=2 and \f(CW\*(C`EV_MINPRI\*(C'\fR=\-2), and |
4560 | enables multiplicity (\f(CW\*(C`EV_MULTIPLICITY\*(C'\fR=1). |
5043 | enables multiplicity (\f(CW\*(C`EV_MULTIPLICITY\*(C'\fR=1). |
… | |
… | |
4592 | With an intelligent-enough linker (gcc+binutils are intelligent enough |
5075 | With an intelligent-enough linker (gcc+binutils are intelligent enough |
4593 | when you use \f(CW\*(C`\-Wl,\-\-gc\-sections \-ffunction\-sections\*(C'\fR) functions unused by |
5076 | when you use \f(CW\*(C`\-Wl,\-\-gc\-sections \-ffunction\-sections\*(C'\fR) functions unused by |
4594 | your program might be left out as well \- a binary starting a timer and an |
5077 | your program might be left out as well \- a binary starting a timer and an |
4595 | I/O watcher then might come out at only 5Kb. |
5078 | I/O watcher then might come out at only 5Kb. |
4596 | .RE |
5079 | .RE |
|
|
5080 | .IP "\s-1EV_API_STATIC\s0" 4 |
|
|
5081 | .IX Item "EV_API_STATIC" |
|
|
5082 | If this symbol is defined (by default it is not), then all identifiers |
|
|
5083 | will have static linkage. This means that libev will not export any |
|
|
5084 | identifiers, and you cannot link against libev anymore. This can be useful |
|
|
5085 | when you embed libev, only want to use libev functions in a single file, |
|
|
5086 | and do not want its identifiers to be visible. |
|
|
5087 | .Sp |
|
|
5088 | To use this, define \f(CW\*(C`EV_API_STATIC\*(C'\fR and include \fIev.c\fR in the file that |
|
|
5089 | wants to use libev. |
|
|
5090 | .Sp |
|
|
5091 | This option only works when libev is compiled with a C compiler, as \*(C+ |
|
|
5092 | doesn't support the required declaration syntax. |
4597 | .IP "\s-1EV_AVOID_STDIO\s0" 4 |
5093 | .IP "\s-1EV_AVOID_STDIO\s0" 4 |
4598 | .IX Item "EV_AVOID_STDIO" |
5094 | .IX Item "EV_AVOID_STDIO" |
4599 | If this is set to \f(CW1\fR at compiletime, then libev will avoid using stdio |
5095 | If this is set to \f(CW1\fR at compiletime, then libev will avoid using stdio |
4600 | functions (printf, scanf, perror etc.). This will increase the code size |
5096 | functions (printf, scanf, perror etc.). This will increase the code size |
4601 | somewhat, but if your program doesn't otherwise depend on stdio and your |
5097 | somewhat, but if your program doesn't otherwise depend on stdio and your |
… | |
… | |
4653 | called. If set to \f(CW2\fR, then the internal verification code will be |
5149 | called. If set to \f(CW2\fR, then the internal verification code will be |
4654 | called once per loop, which can slow down libev. If set to \f(CW3\fR, then the |
5150 | called once per loop, which can slow down libev. If set to \f(CW3\fR, then the |
4655 | verification code will be called very frequently, which will slow down |
5151 | verification code will be called very frequently, which will slow down |
4656 | libev considerably. |
5152 | libev considerably. |
4657 | .Sp |
5153 | .Sp |
|
|
5154 | Verification errors are reported via C's \f(CW\*(C`assert\*(C'\fR mechanism, so if you |
|
|
5155 | disable that (e.g. by defining \f(CW\*(C`NDEBUG\*(C'\fR) then no errors will be reported. |
|
|
5156 | .Sp |
4658 | The default is \f(CW1\fR, unless \f(CW\*(C`EV_FEATURES\*(C'\fR overrides it, in which case it |
5157 | The default is \f(CW1\fR, unless \f(CW\*(C`EV_FEATURES\*(C'\fR overrides it, in which case it |
4659 | will be \f(CW0\fR. |
5158 | will be \f(CW0\fR. |
4660 | .IP "\s-1EV_COMMON\s0" 4 |
5159 | .IP "\s-1EV_COMMON\s0" 4 |
4661 | .IX Item "EV_COMMON" |
5160 | .IX Item "EV_COMMON" |
4662 | By default, all watchers have a \f(CW\*(C`void *data\*(C'\fR member. By redefining |
5161 | By default, all watchers have a \f(CW\*(C`void *data\*(C'\fR member. By redefining |
… | |
… | |
4683 | and the way callbacks are invoked and set. Must expand to a struct member |
5182 | and the way callbacks are invoked and set. Must expand to a struct member |
4684 | definition and a statement, respectively. See the \fIev.h\fR header file for |
5183 | definition and a statement, respectively. See the \fIev.h\fR header file for |
4685 | their default definitions. One possible use for overriding these is to |
5184 | their default definitions. One possible use for overriding these is to |
4686 | avoid the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument in all cases, or to use |
5185 | avoid the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument in all cases, or to use |
4687 | method calls instead of plain function calls in \*(C+. |
5186 | method calls instead of plain function calls in \*(C+. |
4688 | .SS "\s-1EXPORTED\s0 \s-1API\s0 \s-1SYMBOLS\s0" |
5187 | .SS "\s-1EXPORTED API SYMBOLS\s0" |
4689 | .IX Subsection "EXPORTED API SYMBOLS" |
5188 | .IX Subsection "EXPORTED API SYMBOLS" |
4690 | If you need to re-export the \s-1API\s0 (e.g. via a \s-1DLL\s0) and you need a list of |
5189 | If you need to re-export the \s-1API\s0 (e.g. via a \s-1DLL\s0) and you need a list of |
4691 | exported symbols, you can use the provided \fISymbol.*\fR files which list |
5190 | exported symbols, you can use the provided \fISymbol.*\fR files which list |
4692 | all public symbols, one per line: |
5191 | all public symbols, one per line: |
4693 | .PP |
5192 | .PP |
… | |
… | |
4747 | \& #include "ev_cpp.h" |
5246 | \& #include "ev_cpp.h" |
4748 | \& #include "ev.c" |
5247 | \& #include "ev.c" |
4749 | .Ve |
5248 | .Ve |
4750 | .SH "INTERACTION WITH OTHER PROGRAMS, LIBRARIES OR THE ENVIRONMENT" |
5249 | .SH "INTERACTION WITH OTHER PROGRAMS, LIBRARIES OR THE ENVIRONMENT" |
4751 | .IX Header "INTERACTION WITH OTHER PROGRAMS, LIBRARIES OR THE ENVIRONMENT" |
5250 | .IX Header "INTERACTION WITH OTHER PROGRAMS, LIBRARIES OR THE ENVIRONMENT" |
4752 | .SS "\s-1THREADS\s0 \s-1AND\s0 \s-1COROUTINES\s0" |
5251 | .SS "\s-1THREADS AND COROUTINES\s0" |
4753 | .IX Subsection "THREADS AND COROUTINES" |
5252 | .IX Subsection "THREADS AND COROUTINES" |
4754 | \fI\s-1THREADS\s0\fR |
5253 | \fI\s-1THREADS\s0\fR |
4755 | .IX Subsection "THREADS" |
5254 | .IX Subsection "THREADS" |
4756 | .PP |
5255 | .PP |
4757 | All libev functions are reentrant and thread-safe unless explicitly |
5256 | All libev functions are reentrant and thread-safe unless explicitly |
… | |
… | |
4803 | An example use would be to communicate signals or other events that only |
5302 | An example use would be to communicate signals or other events that only |
4804 | work in the default loop by registering the signal watcher with the |
5303 | work in the default loop by registering the signal watcher with the |
4805 | default loop and triggering an \f(CW\*(C`ev_async\*(C'\fR watcher from the default loop |
5304 | default loop and triggering an \f(CW\*(C`ev_async\*(C'\fR watcher from the default loop |
4806 | watcher callback into the event loop interested in the signal. |
5305 | watcher callback into the event loop interested in the signal. |
4807 | .PP |
5306 | .PP |
4808 | See also \*(L"\s-1THREAD\s0 \s-1LOCKING\s0 \s-1EXAMPLE\s0\*(R". |
5307 | See also \*(L"\s-1THREAD LOCKING EXAMPLE\*(R"\s0. |
4809 | .PP |
5308 | .PP |
4810 | \fI\s-1COROUTINES\s0\fR |
5309 | \fI\s-1COROUTINES\s0\fR |
4811 | .IX Subsection "COROUTINES" |
5310 | .IX Subsection "COROUTINES" |
4812 | .PP |
5311 | .PP |
4813 | Libev is very accommodating to coroutines (\*(L"cooperative threads\*(R"): |
5312 | Libev is very accommodating to coroutines (\*(L"cooperative threads\*(R"): |
… | |
… | |
4818 | that you must not do this from \f(CW\*(C`ev_periodic\*(C'\fR reschedule callbacks. |
5317 | that you must not do this from \f(CW\*(C`ev_periodic\*(C'\fR reschedule callbacks. |
4819 | .PP |
5318 | .PP |
4820 | Care has been taken to ensure that libev does not keep local state inside |
5319 | Care has been taken to ensure that libev does not keep local state inside |
4821 | \&\f(CW\*(C`ev_run\*(C'\fR, and other calls do not usually allow for coroutine switches as |
5320 | \&\f(CW\*(C`ev_run\*(C'\fR, and other calls do not usually allow for coroutine switches as |
4822 | they do not call any callbacks. |
5321 | they do not call any callbacks. |
4823 | .SS "\s-1COMPILER\s0 \s-1WARNINGS\s0" |
5322 | .SS "\s-1COMPILER WARNINGS\s0" |
4824 | .IX Subsection "COMPILER WARNINGS" |
5323 | .IX Subsection "COMPILER WARNINGS" |
4825 | Depending on your compiler and compiler settings, you might get no or a |
5324 | Depending on your compiler and compiler settings, you might get no or a |
4826 | lot of warnings when compiling libev code. Some people are apparently |
5325 | lot of warnings when compiling libev code. Some people are apparently |
4827 | scared by this. |
5326 | scared by this. |
4828 | .PP |
5327 | .PP |
… | |
… | |
4880 | .PP |
5379 | .PP |
4881 | If you need, for some reason, empty reports from valgrind for your project |
5380 | If you need, for some reason, empty reports from valgrind for your project |
4882 | I suggest using suppression lists. |
5381 | I suggest using suppression lists. |
4883 | .SH "PORTABILITY NOTES" |
5382 | .SH "PORTABILITY NOTES" |
4884 | .IX Header "PORTABILITY NOTES" |
5383 | .IX Header "PORTABILITY NOTES" |
4885 | .SS "\s-1GNU/LINUX\s0 32 \s-1BIT\s0 \s-1LIMITATIONS\s0" |
5384 | .SS "\s-1GNU/LINUX 32 BIT LIMITATIONS\s0" |
4886 | .IX Subsection "GNU/LINUX 32 BIT LIMITATIONS" |
5385 | .IX Subsection "GNU/LINUX 32 BIT LIMITATIONS" |
4887 | GNU/Linux is the only common platform that supports 64 bit file/large file |
5386 | GNU/Linux is the only common platform that supports 64 bit file/large file |
4888 | interfaces but \fIdisables\fR them by default. |
5387 | interfaces but \fIdisables\fR them by default. |
4889 | .PP |
5388 | .PP |
4890 | That means that libev compiled in the default environment doesn't support |
5389 | That means that libev compiled in the default environment doesn't support |
4891 | files larger than 2GiB or so, which mainly affects \f(CW\*(C`ev_stat\*(C'\fR watchers. |
5390 | files larger than 2GiB or so, which mainly affects \f(CW\*(C`ev_stat\*(C'\fR watchers. |
4892 | .PP |
5391 | .PP |
4893 | Unfortunately, many programs try to work around this GNU/Linux issue |
5392 | Unfortunately, many programs try to work around this GNU/Linux issue |
4894 | by enabling the large file \s-1API\s0, which makes them incompatible with the |
5393 | by enabling the large file \s-1API,\s0 which makes them incompatible with the |
4895 | standard libev compiled for their system. |
5394 | standard libev compiled for their system. |
4896 | .PP |
5395 | .PP |
4897 | Likewise, libev cannot enable the large file \s-1API\s0 itself as this would |
5396 | Likewise, libev cannot enable the large file \s-1API\s0 itself as this would |
4898 | suddenly make it incompatible to the default compile time environment, |
5397 | suddenly make it incompatible to the default compile time environment, |
4899 | i.e. all programs not using special compile switches. |
5398 | i.e. all programs not using special compile switches. |
4900 | .SS "\s-1OS/X\s0 \s-1AND\s0 \s-1DARWIN\s0 \s-1BUGS\s0" |
5399 | .SS "\s-1OS/X AND DARWIN BUGS\s0" |
4901 | .IX Subsection "OS/X AND DARWIN BUGS" |
5400 | .IX Subsection "OS/X AND DARWIN BUGS" |
4902 | The whole thing is a bug if you ask me \- basically any system interface |
5401 | The whole thing is a bug if you ask me \- basically any system interface |
4903 | you touch is broken, whether it is locales, poll, kqueue or even the |
5402 | you touch is broken, whether it is locales, poll, kqueue or even the |
4904 | OpenGL drivers. |
5403 | OpenGL drivers. |
4905 | .PP |
5404 | .PP |
… | |
… | |
4927 | .PP |
5426 | .PP |
4928 | \fI\f(CI\*(C`select\*(C'\fI is buggy\fR |
5427 | \fI\f(CI\*(C`select\*(C'\fI is buggy\fR |
4929 | .IX Subsection "select is buggy" |
5428 | .IX Subsection "select is buggy" |
4930 | .PP |
5429 | .PP |
4931 | All that's left is \f(CW\*(C`select\*(C'\fR, and of course Apple found a way to fuck this |
5430 | All that's left is \f(CW\*(C`select\*(C'\fR, and of course Apple found a way to fuck this |
4932 | one up as well: On \s-1OS/X\s0, \f(CW\*(C`select\*(C'\fR actively limits the number of file |
5431 | one up as well: On \s-1OS/X,\s0 \f(CW\*(C`select\*(C'\fR actively limits the number of file |
4933 | descriptors you can pass in to 1024 \- your program suddenly crashes when |
5432 | descriptors you can pass in to 1024 \- your program suddenly crashes when |
4934 | you use more. |
5433 | you use more. |
4935 | .PP |
5434 | .PP |
4936 | There is an undocumented \*(L"workaround\*(R" for this \- defining |
5435 | There is an undocumented \*(L"workaround\*(R" for this \- defining |
4937 | \&\f(CW\*(C`_DARWIN_UNLIMITED_SELECT\*(C'\fR, which libev tries to use, so select \fIshould\fR |
5436 | \&\f(CW\*(C`_DARWIN_UNLIMITED_SELECT\*(C'\fR, which libev tries to use, so select \fIshould\fR |
4938 | work on \s-1OS/X\s0. |
5437 | work on \s-1OS/X.\s0 |
4939 | .SS "\s-1SOLARIS\s0 \s-1PROBLEMS\s0 \s-1AND\s0 \s-1WORKAROUNDS\s0" |
5438 | .SS "\s-1SOLARIS PROBLEMS AND WORKAROUNDS\s0" |
4940 | .IX Subsection "SOLARIS PROBLEMS AND WORKAROUNDS" |
5439 | .IX Subsection "SOLARIS PROBLEMS AND WORKAROUNDS" |
4941 | \fI\f(CI\*(C`errno\*(C'\fI reentrancy\fR |
5440 | \fI\f(CI\*(C`errno\*(C'\fI reentrancy\fR |
4942 | .IX Subsection "errno reentrancy" |
5441 | .IX Subsection "errno reentrancy" |
4943 | .PP |
5442 | .PP |
4944 | The default compile environment on Solaris is unfortunately so |
5443 | The default compile environment on Solaris is unfortunately so |
… | |
… | |
4961 | great. |
5460 | great. |
4962 | .PP |
5461 | .PP |
4963 | If you can't get it to work, you can try running the program by setting |
5462 | If you can't get it to work, you can try running the program by setting |
4964 | the environment variable \f(CW\*(C`LIBEV_FLAGS=3\*(C'\fR to only allow \f(CW\*(C`poll\*(C'\fR and |
5463 | the environment variable \f(CW\*(C`LIBEV_FLAGS=3\*(C'\fR to only allow \f(CW\*(C`poll\*(C'\fR and |
4965 | \&\f(CW\*(C`select\*(C'\fR backends. |
5464 | \&\f(CW\*(C`select\*(C'\fR backends. |
4966 | .SS "\s-1AIX\s0 \s-1POLL\s0 \s-1BUG\s0" |
5465 | .SS "\s-1AIX POLL BUG\s0" |
4967 | .IX Subsection "AIX POLL BUG" |
5466 | .IX Subsection "AIX POLL BUG" |
4968 | \&\s-1AIX\s0 unfortunately has a broken \f(CW\*(C`poll.h\*(C'\fR header. Libev works around |
5467 | \&\s-1AIX\s0 unfortunately has a broken \f(CW\*(C`poll.h\*(C'\fR header. Libev works around |
4969 | this by trying to avoid the poll backend altogether (i.e. it's not even |
5468 | this by trying to avoid the poll backend altogether (i.e. it's not even |
4970 | compiled in), which normally isn't a big problem as \f(CW\*(C`select\*(C'\fR works fine |
5469 | compiled in), which normally isn't a big problem as \f(CW\*(C`select\*(C'\fR works fine |
4971 | with large bitsets on \s-1AIX\s0, and \s-1AIX\s0 is dead anyway. |
5470 | with large bitsets on \s-1AIX,\s0 and \s-1AIX\s0 is dead anyway. |
4972 | .SS "\s-1WIN32\s0 \s-1PLATFORM\s0 \s-1LIMITATIONS\s0 \s-1AND\s0 \s-1WORKAROUNDS\s0" |
5471 | .SS "\s-1WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS\s0" |
4973 | .IX Subsection "WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS" |
5472 | .IX Subsection "WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS" |
4974 | \fIGeneral issues\fR |
5473 | \fIGeneral issues\fR |
4975 | .IX Subsection "General issues" |
5474 | .IX Subsection "General issues" |
4976 | .PP |
5475 | .PP |
4977 | Win32 doesn't support any of the standards (e.g. \s-1POSIX\s0) that libev |
5476 | Win32 doesn't support any of the standards (e.g. \s-1POSIX\s0) that libev |
4978 | requires, and its I/O model is fundamentally incompatible with the \s-1POSIX\s0 |
5477 | requires, and its I/O model is fundamentally incompatible with the \s-1POSIX\s0 |
4979 | model. Libev still offers limited functionality on this platform in |
5478 | model. Libev still offers limited functionality on this platform in |
4980 | the form of the \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR backend, and only supports socket |
5479 | the form of the \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR backend, and only supports socket |
4981 | descriptors. This only applies when using Win32 natively, not when using |
5480 | descriptors. This only applies when using Win32 natively, not when using |
4982 | e.g. cygwin. Actually, it only applies to the microsofts own compilers, |
5481 | e.g. cygwin. Actually, it only applies to the microsofts own compilers, |
4983 | as every compielr comes with a slightly differently broken/incompatible |
5482 | as every compiler comes with a slightly differently broken/incompatible |
4984 | environment. |
5483 | environment. |
4985 | .PP |
5484 | .PP |
4986 | Lifting these limitations would basically require the full |
5485 | Lifting these limitations would basically require the full |
4987 | re-implementation of the I/O system. If you are into this kind of thing, |
5486 | re-implementation of the I/O system. If you are into this kind of thing, |
4988 | then note that glib does exactly that for you in a very portable way (note |
5487 | then note that glib does exactly that for you in a very portable way (note |
… | |
… | |
5046 | \& #define EV_USE_SELECT 1 |
5545 | \& #define EV_USE_SELECT 1 |
5047 | \& #define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */ |
5546 | \& #define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */ |
5048 | .Ve |
5547 | .Ve |
5049 | .PP |
5548 | .PP |
5050 | Note that winsockets handling of fd sets is O(n), so you can easily get a |
5549 | Note that winsockets handling of fd sets is O(n), so you can easily get a |
5051 | complexity in the O(nA\*^X) range when using win32. |
5550 | complexity in the O(nX) range when using win32. |
5052 | .PP |
5551 | .PP |
5053 | \fILimited number of file descriptors\fR |
5552 | \fILimited number of file descriptors\fR |
5054 | .IX Subsection "Limited number of file descriptors" |
5553 | .IX Subsection "Limited number of file descriptors" |
5055 | .PP |
5554 | .PP |
5056 | Windows has numerous arbitrary (and low) limits on things. |
5555 | Windows has numerous arbitrary (and low) limits on things. |
… | |
… | |
5072 | by calling \f(CW\*(C`_setmaxstdio\*(C'\fR, which can increase this limit to \f(CW2048\fR |
5571 | by calling \f(CW\*(C`_setmaxstdio\*(C'\fR, which can increase this limit to \f(CW2048\fR |
5073 | (another arbitrary limit), but is broken in many versions of the Microsoft |
5572 | (another arbitrary limit), but is broken in many versions of the Microsoft |
5074 | runtime libraries. This might get you to about \f(CW512\fR or \f(CW2048\fR sockets |
5573 | runtime libraries. This might get you to about \f(CW512\fR or \f(CW2048\fR sockets |
5075 | (depending on windows version and/or the phase of the moon). To get more, |
5574 | (depending on windows version and/or the phase of the moon). To get more, |
5076 | you need to wrap all I/O functions and provide your own fd management, but |
5575 | you need to wrap all I/O functions and provide your own fd management, but |
5077 | the cost of calling select (O(nA\*^X)) will likely make this unworkable. |
5576 | the cost of calling select (O(nX)) will likely make this unworkable. |
5078 | .SS "\s-1PORTABILITY\s0 \s-1REQUIREMENTS\s0" |
5577 | .SS "\s-1PORTABILITY REQUIREMENTS\s0" |
5079 | .IX Subsection "PORTABILITY REQUIREMENTS" |
5578 | .IX Subsection "PORTABILITY REQUIREMENTS" |
5080 | In addition to a working ISO-C implementation and of course the |
5579 | In addition to a working ISO-C implementation and of course the |
5081 | backend-specific APIs, libev relies on a few additional extensions: |
5580 | backend-specific APIs, libev relies on a few additional extensions: |
5082 | .ie n .IP """void (*)(ev_watcher_type *, int revents)"" must have compatible calling conventions regardless of ""ev_watcher_type *""." 4 |
5581 | .ie n .IP """void (*)(ev_watcher_type *, int revents)"" must have compatible calling conventions regardless of ""ev_watcher_type *""." 4 |
5083 | .el .IP "\f(CWvoid (*)(ev_watcher_type *, int revents)\fR must have compatible calling conventions regardless of \f(CWev_watcher_type *\fR." 4 |
5582 | .el .IP "\f(CWvoid (*)(ev_watcher_type *, int revents)\fR must have compatible calling conventions regardless of \f(CWev_watcher_type *\fR." 4 |
5084 | .IX Item "void (*)(ev_watcher_type *, int revents) must have compatible calling conventions regardless of ev_watcher_type *." |
5583 | .IX Item "void (*)(ev_watcher_type *, int revents) must have compatible calling conventions regardless of ev_watcher_type *." |
5085 | Libev assumes not only that all watcher pointers have the same internal |
5584 | Libev assumes not only that all watcher pointers have the same internal |
5086 | structure (guaranteed by \s-1POSIX\s0 but not by \s-1ISO\s0 C for example), but it also |
5585 | structure (guaranteed by \s-1POSIX\s0 but not by \s-1ISO C\s0 for example), but it also |
5087 | assumes that the same (machine) code can be used to call any watcher |
5586 | assumes that the same (machine) code can be used to call any watcher |
5088 | callback: The watcher callbacks have different type signatures, but libev |
5587 | callback: The watcher callbacks have different type signatures, but libev |
5089 | calls them using an \f(CW\*(C`ev_watcher *\*(C'\fR internally. |
5588 | calls them using an \f(CW\*(C`ev_watcher *\*(C'\fR internally. |
|
|
5589 | .IP "null pointers and integer zero are represented by 0 bytes" 4 |
|
|
5590 | .IX Item "null pointers and integer zero are represented by 0 bytes" |
|
|
5591 | Libev uses \f(CW\*(C`memset\*(C'\fR to initialise structs and arrays to \f(CW0\fR bytes, and |
|
|
5592 | relies on this setting pointers and integers to null. |
5090 | .IP "pointer accesses must be thread-atomic" 4 |
5593 | .IP "pointer accesses must be thread-atomic" 4 |
5091 | .IX Item "pointer accesses must be thread-atomic" |
5594 | .IX Item "pointer accesses must be thread-atomic" |
5092 | Accessing a pointer value must be atomic, it must both be readable and |
5595 | Accessing a pointer value must be atomic, it must both be readable and |
5093 | writable in one piece \- this is the case on all current architectures. |
5596 | writable in one piece \- this is the case on all current architectures. |
5094 | .ie n .IP """sig_atomic_t volatile"" must be thread-atomic as well" 4 |
5597 | .ie n .IP """sig_atomic_t volatile"" must be thread-atomic as well" 4 |
… | |
… | |
5107 | thread\*(R" or will block signals process-wide, both behaviours would |
5610 | thread\*(R" or will block signals process-wide, both behaviours would |
5108 | be compatible with libev. Interaction between \f(CW\*(C`sigprocmask\*(C'\fR and |
5611 | be compatible with libev. Interaction between \f(CW\*(C`sigprocmask\*(C'\fR and |
5109 | \&\f(CW\*(C`pthread_sigmask\*(C'\fR could complicate things, however. |
5612 | \&\f(CW\*(C`pthread_sigmask\*(C'\fR could complicate things, however. |
5110 | .Sp |
5613 | .Sp |
5111 | The most portable way to handle signals is to block signals in all threads |
5614 | The most portable way to handle signals is to block signals in all threads |
5112 | except the initial one, and run the default loop in the initial thread as |
5615 | except the initial one, and run the signal handling loop in the initial |
5113 | well. |
5616 | thread as well. |
5114 | .ie n .IP """long"" must be large enough for common memory allocation sizes" 4 |
5617 | .ie n .IP """long"" must be large enough for common memory allocation sizes" 4 |
5115 | .el .IP "\f(CWlong\fR must be large enough for common memory allocation sizes" 4 |
5618 | .el .IP "\f(CWlong\fR must be large enough for common memory allocation sizes" 4 |
5116 | .IX Item "long must be large enough for common memory allocation sizes" |
5619 | .IX Item "long must be large enough for common memory allocation sizes" |
5117 | To improve portability and simplify its \s-1API\s0, libev uses \f(CW\*(C`long\*(C'\fR internally |
5620 | To improve portability and simplify its \s-1API,\s0 libev uses \f(CW\*(C`long\*(C'\fR internally |
5118 | instead of \f(CW\*(C`size_t\*(C'\fR when allocating its data structures. On non-POSIX |
5621 | instead of \f(CW\*(C`size_t\*(C'\fR when allocating its data structures. On non-POSIX |
5119 | systems (Microsoft...) this might be unexpectedly low, but is still at |
5622 | systems (Microsoft...) this might be unexpectedly low, but is still at |
5120 | least 31 bits everywhere, which is enough for hundreds of millions of |
5623 | least 31 bits everywhere, which is enough for hundreds of millions of |
5121 | watchers. |
5624 | watchers. |
5122 | .ie n .IP """double"" must hold a time value in seconds with enough accuracy" 4 |
5625 | .ie n .IP """double"" must hold a time value in seconds with enough accuracy" 4 |
… | |
… | |
5124 | .IX Item "double must hold a time value in seconds with enough accuracy" |
5627 | .IX Item "double must hold a time value in seconds with enough accuracy" |
5125 | The type \f(CW\*(C`double\*(C'\fR is used to represent timestamps. It is required to |
5628 | The type \f(CW\*(C`double\*(C'\fR is used to represent timestamps. It is required to |
5126 | have at least 51 bits of mantissa (and 9 bits of exponent), which is |
5629 | have at least 51 bits of mantissa (and 9 bits of exponent), which is |
5127 | good enough for at least into the year 4000 with millisecond accuracy |
5630 | good enough for at least into the year 4000 with millisecond accuracy |
5128 | (the design goal for libev). This requirement is overfulfilled by |
5631 | (the design goal for libev). This requirement is overfulfilled by |
5129 | implementations using \s-1IEEE\s0 754, which is basically all existing ones. With |
5632 | implementations using \s-1IEEE 754,\s0 which is basically all existing ones. |
|
|
5633 | .Sp |
5130 | \&\s-1IEEE\s0 754 doubles, you get microsecond accuracy until at least 2200. |
5634 | With \s-1IEEE 754\s0 doubles, you get microsecond accuracy until at least the |
|
|
5635 | year 2255 (and millisecond accuracy till the year 287396 \- by then, libev |
|
|
5636 | is either obsolete or somebody patched it to use \f(CW\*(C`long double\*(C'\fR or |
|
|
5637 | something like that, just kidding). |
5131 | .PP |
5638 | .PP |
5132 | If you know of other additional requirements drop me a note. |
5639 | If you know of other additional requirements drop me a note. |
5133 | .SH "ALGORITHMIC COMPLEXITIES" |
5640 | .SH "ALGORITHMIC COMPLEXITIES" |
5134 | .IX Header "ALGORITHMIC COMPLEXITIES" |
5641 | .IX Header "ALGORITHMIC COMPLEXITIES" |
5135 | In this section the complexities of (many of) the algorithms used inside |
5642 | In this section the complexities of (many of) the algorithms used inside |
… | |
… | |
5189 | .IX Item "Processing ev_async_send: O(number_of_async_watchers)" |
5696 | .IX Item "Processing ev_async_send: O(number_of_async_watchers)" |
5190 | .IP "Processing signals: O(max_signal_number)" 4 |
5697 | .IP "Processing signals: O(max_signal_number)" 4 |
5191 | .IX Item "Processing signals: O(max_signal_number)" |
5698 | .IX Item "Processing signals: O(max_signal_number)" |
5192 | .PD |
5699 | .PD |
5193 | Sending involves a system call \fIiff\fR there were no other \f(CW\*(C`ev_async_send\*(C'\fR |
5700 | Sending involves a system call \fIiff\fR there were no other \f(CW\*(C`ev_async_send\*(C'\fR |
5194 | calls in the current loop iteration. Checking for async and signal events |
5701 | calls in the current loop iteration and the loop is currently |
|
|
5702 | blocked. Checking for async and signal events involves iterating over all |
5195 | involves iterating over all running async watchers or all signal numbers. |
5703 | running async watchers or all signal numbers. |
5196 | .SH "PORTING FROM LIBEV 3.X TO 4.X" |
5704 | .SH "PORTING FROM LIBEV 3.X TO 4.X" |
5197 | .IX Header "PORTING FROM LIBEV 3.X TO 4.X" |
5705 | .IX Header "PORTING FROM LIBEV 3.X TO 4.X" |
5198 | The major version 4 introduced some incompatible changes to the \s-1API\s0. |
5706 | The major version 4 introduced some incompatible changes to the \s-1API.\s0 |
5199 | .PP |
5707 | .PP |
5200 | At the moment, the \f(CW\*(C`ev.h\*(C'\fR header file provides compatibility definitions |
5708 | At the moment, the \f(CW\*(C`ev.h\*(C'\fR header file provides compatibility definitions |
5201 | for all changes, so most programs should still compile. The compatibility |
5709 | for all changes, so most programs should still compile. The compatibility |
5202 | layer might be removed in later versions of libev, so better update to the |
5710 | layer might be removed in later versions of libev, so better update to the |
5203 | new \s-1API\s0 early than late. |
5711 | new \s-1API\s0 early than late. |
5204 | .ie n .IP """EV_COMPAT3"" backwards compatibility mechanism" 4 |
5712 | .ie n .IP """EV_COMPAT3"" backwards compatibility mechanism" 4 |
5205 | .el .IP "\f(CWEV_COMPAT3\fR backwards compatibility mechanism" 4 |
5713 | .el .IP "\f(CWEV_COMPAT3\fR backwards compatibility mechanism" 4 |
5206 | .IX Item "EV_COMPAT3 backwards compatibility mechanism" |
5714 | .IX Item "EV_COMPAT3 backwards compatibility mechanism" |
5207 | The backward compatibility mechanism can be controlled by |
5715 | The backward compatibility mechanism can be controlled by |
5208 | \&\f(CW\*(C`EV_COMPAT3\*(C'\fR. See \*(L"\s-1MACROS\s0\*(R" in \s-1PREPROCESSOR\s0 \s-1SYMBOLS\s0 in the \s-1EMBEDDING\s0 |
5716 | \&\f(CW\*(C`EV_COMPAT3\*(C'\fR. See \*(L"\s-1PREPROCESSOR SYMBOLS/MACROS\*(R"\s0 in the \*(L"\s-1EMBEDDING\*(R"\s0 |
5209 | section. |
5717 | section. |
5210 | .ie n .IP """ev_default_destroy"" and ""ev_default_fork"" have been removed" 4 |
5718 | .ie n .IP """ev_default_destroy"" and ""ev_default_fork"" have been removed" 4 |
5211 | .el .IP "\f(CWev_default_destroy\fR and \f(CWev_default_fork\fR have been removed" 4 |
5719 | .el .IP "\f(CWev_default_destroy\fR and \f(CWev_default_fork\fR have been removed" 4 |
5212 | .IX Item "ev_default_destroy and ev_default_fork have been removed" |
5720 | .IX Item "ev_default_destroy and ev_default_fork have been removed" |
5213 | These calls can be replaced easily by their \f(CW\*(C`ev_loop_xxx\*(C'\fR counterparts: |
5721 | These calls can be replaced easily by their \f(CW\*(C`ev_loop_xxx\*(C'\fR counterparts: |
… | |
… | |
5253 | .SH "GLOSSARY" |
5761 | .SH "GLOSSARY" |
5254 | .IX Header "GLOSSARY" |
5762 | .IX Header "GLOSSARY" |
5255 | .IP "active" 4 |
5763 | .IP "active" 4 |
5256 | .IX Item "active" |
5764 | .IX Item "active" |
5257 | A watcher is active as long as it has been started and not yet stopped. |
5765 | A watcher is active as long as it has been started and not yet stopped. |
5258 | See \*(L"\s-1WATCHER\s0 \s-1STATES\s0\*(R" for details. |
5766 | See \*(L"\s-1WATCHER STATES\*(R"\s0 for details. |
5259 | .IP "application" 4 |
5767 | .IP "application" 4 |
5260 | .IX Item "application" |
5768 | .IX Item "application" |
5261 | In this document, an application is whatever is using libev. |
5769 | In this document, an application is whatever is using libev. |
5262 | .IP "backend" 4 |
5770 | .IP "backend" 4 |
5263 | .IX Item "backend" |
5771 | .IX Item "backend" |
… | |
… | |
5290 | The model used to describe how an event loop handles and processes |
5798 | The model used to describe how an event loop handles and processes |
5291 | watchers and events. |
5799 | watchers and events. |
5292 | .IP "pending" 4 |
5800 | .IP "pending" 4 |
5293 | .IX Item "pending" |
5801 | .IX Item "pending" |
5294 | A watcher is pending as soon as the corresponding event has been |
5802 | A watcher is pending as soon as the corresponding event has been |
5295 | detected. See \*(L"\s-1WATCHER\s0 \s-1STATES\s0\*(R" for details. |
5803 | detected. See \*(L"\s-1WATCHER STATES\*(R"\s0 for details. |
5296 | .IP "real time" 4 |
5804 | .IP "real time" 4 |
5297 | .IX Item "real time" |
5805 | .IX Item "real time" |
5298 | The physical time that is observed. It is apparently strictly monotonic :) |
5806 | The physical time that is observed. It is apparently strictly monotonic :) |
5299 | .IP "wall-clock time" 4 |
5807 | .IP "wall-clock time" 4 |
5300 | .IX Item "wall-clock time" |
5808 | .IX Item "wall-clock time" |