… | |
… | |
130 | .\} |
130 | .\} |
131 | .rm #[ #] #H #V #F C |
131 | .rm #[ #] #H #V #F C |
132 | .\" ======================================================================== |
132 | .\" ======================================================================== |
133 | .\" |
133 | .\" |
134 | .IX Title "LIBEV 3" |
134 | .IX Title "LIBEV 3" |
135 | .TH LIBEV 3 "2008-05-09" "libev-1.1" "libev - high perfromance full featured event loop" |
135 | .TH LIBEV 3 "2008-10-21" "libev-3.45" "libev - high performance full featured event loop" |
136 | .\" For nroff, turn off justification. Always turn off hyphenation; it makes |
136 | .\" For nroff, turn off justification. Always turn off hyphenation; it makes |
137 | .\" way too many mistakes in technical documents. |
137 | .\" way too many mistakes in technical documents. |
138 | .if n .ad l |
138 | .if n .ad l |
139 | .nh |
139 | .nh |
140 | .SH "NAME" |
140 | .SH "NAME" |
141 | libev \- a high performance full\-featured event loop written in C |
141 | libev \- a high performance full\-featured event loop written in C |
142 | .SH "SYNOPSIS" |
142 | .SH "SYNOPSIS" |
143 | .IX Header "SYNOPSIS" |
143 | .IX Header "SYNOPSIS" |
144 | .Vb 1 |
144 | .Vb 1 |
145 | \& #include <ev.h> |
145 | \& #include <ev.h> |
146 | .Ve |
146 | .Ve |
147 | .Sh "\s-1EXAMPLE\s0 \s-1PROGRAM\s0" |
147 | .Sh "\s-1EXAMPLE\s0 \s-1PROGRAM\s0" |
148 | .IX Subsection "EXAMPLE PROGRAM" |
148 | .IX Subsection "EXAMPLE PROGRAM" |
149 | .Vb 2 |
149 | .Vb 2 |
150 | \& // a single header file is required |
150 | \& // a single header file is required |
151 | \& #include <ev.h> |
151 | \& #include <ev.h> |
152 | \& |
152 | \& |
153 | \& // every watcher type has its own typedef\*(Aqd struct |
153 | \& // every watcher type has its own typedef\*(Aqd struct |
154 | \& // with the name ev_<type> |
154 | \& // with the name ev_<type> |
155 | \& ev_io stdin_watcher; |
155 | \& ev_io stdin_watcher; |
156 | \& ev_timer timeout_watcher; |
156 | \& ev_timer timeout_watcher; |
157 | \& |
157 | \& |
158 | \& // all watcher callbacks have a similar signature |
158 | \& // all watcher callbacks have a similar signature |
159 | \& // this callback is called when data is readable on stdin |
159 | \& // this callback is called when data is readable on stdin |
160 | \& static void |
160 | \& static void |
161 | \& stdin_cb (EV_P_ struct ev_io *w, int revents) |
161 | \& stdin_cb (EV_P_ struct ev_io *w, int revents) |
162 | \& { |
162 | \& { |
163 | \& puts ("stdin ready"); |
163 | \& puts ("stdin ready"); |
164 | \& // for one\-shot events, one must manually stop the watcher |
164 | \& // for one\-shot events, one must manually stop the watcher |
165 | \& // with its corresponding stop function. |
165 | \& // with its corresponding stop function. |
166 | \& ev_io_stop (EV_A_ w); |
166 | \& ev_io_stop (EV_A_ w); |
167 | \& |
167 | \& |
168 | \& // this causes all nested ev_loop\*(Aqs to stop iterating |
168 | \& // this causes all nested ev_loop\*(Aqs to stop iterating |
169 | \& ev_unloop (EV_A_ EVUNLOOP_ALL); |
169 | \& ev_unloop (EV_A_ EVUNLOOP_ALL); |
170 | \& } |
170 | \& } |
171 | \& |
171 | \& |
172 | \& // another callback, this time for a time\-out |
172 | \& // another callback, this time for a time\-out |
173 | \& static void |
173 | \& static void |
174 | \& timeout_cb (EV_P_ struct ev_timer *w, int revents) |
174 | \& timeout_cb (EV_P_ struct ev_timer *w, int revents) |
175 | \& { |
175 | \& { |
176 | \& puts ("timeout"); |
176 | \& puts ("timeout"); |
177 | \& // this causes the innermost ev_loop to stop iterating |
177 | \& // this causes the innermost ev_loop to stop iterating |
178 | \& ev_unloop (EV_A_ EVUNLOOP_ONE); |
178 | \& ev_unloop (EV_A_ EVUNLOOP_ONE); |
179 | \& } |
179 | \& } |
180 | \& |
180 | \& |
181 | \& int |
181 | \& int |
182 | \& main (void) |
182 | \& main (void) |
183 | \& { |
183 | \& { |
184 | \& // use the default event loop unless you have special needs |
184 | \& // use the default event loop unless you have special needs |
185 | \& struct ev_loop *loop = ev_default_loop (0); |
185 | \& struct ev_loop *loop = ev_default_loop (0); |
186 | \& |
186 | \& |
187 | \& // initialise an io watcher, then start it |
187 | \& // initialise an io watcher, then start it |
188 | \& // this one will watch for stdin to become readable |
188 | \& // this one will watch for stdin to become readable |
189 | \& ev_io_init (&stdin_watcher, stdin_cb, /*STDIN_FILENO*/ 0, EV_READ); |
189 | \& ev_io_init (&stdin_watcher, stdin_cb, /*STDIN_FILENO*/ 0, EV_READ); |
190 | \& ev_io_start (loop, &stdin_watcher); |
190 | \& ev_io_start (loop, &stdin_watcher); |
191 | \& |
191 | \& |
192 | \& // initialise a timer watcher, then start it |
192 | \& // initialise a timer watcher, then start it |
193 | \& // simple non\-repeating 5.5 second timeout |
193 | \& // simple non\-repeating 5.5 second timeout |
194 | \& ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.); |
194 | \& ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.); |
195 | \& ev_timer_start (loop, &timeout_watcher); |
195 | \& ev_timer_start (loop, &timeout_watcher); |
196 | \& |
196 | \& |
197 | \& // now wait for events to arrive |
197 | \& // now wait for events to arrive |
198 | \& ev_loop (loop, 0); |
198 | \& ev_loop (loop, 0); |
199 | \& |
199 | \& |
200 | \& // unloop was called, so exit |
200 | \& // unloop was called, so exit |
201 | \& return 0; |
201 | \& return 0; |
202 | \& } |
202 | \& } |
203 | .Ve |
203 | .Ve |
204 | .SH "DESCRIPTION" |
204 | .SH "DESCRIPTION" |
205 | .IX Header "DESCRIPTION" |
205 | .IX Header "DESCRIPTION" |
206 | The newest version of this document is also available as an html-formatted |
206 | The newest version of this document is also available as an html-formatted |
207 | web page you might find easier to navigate when reading it for the first |
207 | web page you might find easier to navigate when reading it for the first |
208 | time: <http://cvs.schmorp.de/libev/ev.html>. |
208 | time: <http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod>. |
209 | .PP |
209 | .PP |
210 | Libev is an event loop: you register interest in certain events (such as a |
210 | Libev is an event loop: you register interest in certain events (such as a |
211 | file descriptor being readable or a timeout occurring), and it will manage |
211 | file descriptor being readable or a timeout occurring), and it will manage |
212 | these event sources and provide your program with events. |
212 | these event sources and provide your program with events. |
213 | .PP |
213 | .PP |
… | |
… | |
249 | Libev represents time as a single floating point number, representing the |
249 | Libev represents time as a single floating point number, representing the |
250 | (fractional) number of seconds since the (\s-1POSIX\s0) epoch (somewhere near |
250 | (fractional) number of seconds since the (\s-1POSIX\s0) epoch (somewhere near |
251 | the beginning of 1970, details are complicated, don't ask). This type is |
251 | the beginning of 1970, details are complicated, don't ask). This type is |
252 | called \f(CW\*(C`ev_tstamp\*(C'\fR, which is what you should use too. It usually aliases |
252 | called \f(CW\*(C`ev_tstamp\*(C'\fR, which is what you should use too. It usually aliases |
253 | to the \f(CW\*(C`double\*(C'\fR type in C, and when you need to do any calculations on |
253 | to the \f(CW\*(C`double\*(C'\fR type in C, and when you need to do any calculations on |
254 | it, you should treat it as some floatingpoint value. Unlike the name |
254 | it, you should treat it as some floating point value. Unlike the name |
255 | component \f(CW\*(C`stamp\*(C'\fR might indicate, it is also used for time differences |
255 | component \f(CW\*(C`stamp\*(C'\fR might indicate, it is also used for time differences |
256 | throughout libev. |
256 | throughout libev. |
|
|
257 | .SH "ERROR HANDLING" |
|
|
258 | .IX Header "ERROR HANDLING" |
|
|
259 | Libev knows three classes of errors: operating system errors, usage errors |
|
|
260 | and internal errors (bugs). |
|
|
261 | .PP |
|
|
262 | When libev catches an operating system error it cannot handle (for example |
|
|
263 | a system call indicating a condition libev cannot fix), it calls the callback |
|
|
264 | set via \f(CW\*(C`ev_set_syserr_cb\*(C'\fR, which is supposed to fix the problem or |
|
|
265 | abort. The default is to print a diagnostic message and to call \f(CW\*(C`abort |
|
|
266 | ()\*(C'\fR. |
|
|
267 | .PP |
|
|
268 | When libev detects a usage error such as a negative timer interval, then |
|
|
269 | it will print a diagnostic message and abort (via the \f(CW\*(C`assert\*(C'\fR mechanism, |
|
|
270 | so \f(CW\*(C`NDEBUG\*(C'\fR will disable this checking): these are programming errors in |
|
|
271 | the libev caller and need to be fixed there. |
|
|
272 | .PP |
|
|
273 | Libev also has a few internal error-checking \f(CW\*(C`assert\*(C'\fRions, and also has |
|
|
274 | extensive consistency checking code. These do not trigger under normal |
|
|
275 | circumstances, as they indicate either a bug in libev or worse. |
257 | .SH "GLOBAL FUNCTIONS" |
276 | .SH "GLOBAL FUNCTIONS" |
258 | .IX Header "GLOBAL FUNCTIONS" |
277 | .IX Header "GLOBAL FUNCTIONS" |
259 | These functions can be called anytime, even before initialising the |
278 | These functions can be called anytime, even before initialising the |
260 | library in any way. |
279 | library in any way. |
261 | .IP "ev_tstamp ev_time ()" 4 |
280 | .IP "ev_tstamp ev_time ()" 4 |
… | |
… | |
265 | you actually want to know. |
284 | you actually want to know. |
266 | .IP "ev_sleep (ev_tstamp interval)" 4 |
285 | .IP "ev_sleep (ev_tstamp interval)" 4 |
267 | .IX Item "ev_sleep (ev_tstamp interval)" |
286 | .IX Item "ev_sleep (ev_tstamp interval)" |
268 | Sleep for the given interval: The current thread will be blocked until |
287 | Sleep for the given interval: The current thread will be blocked until |
269 | either it is interrupted or the given time interval has passed. Basically |
288 | either it is interrupted or the given time interval has passed. Basically |
270 | this is a subsecond-resolution \f(CW\*(C`sleep ()\*(C'\fR. |
289 | this is a sub-second-resolution \f(CW\*(C`sleep ()\*(C'\fR. |
271 | .IP "int ev_version_major ()" 4 |
290 | .IP "int ev_version_major ()" 4 |
272 | .IX Item "int ev_version_major ()" |
291 | .IX Item "int ev_version_major ()" |
273 | .PD 0 |
292 | .PD 0 |
274 | .IP "int ev_version_minor ()" 4 |
293 | .IP "int ev_version_minor ()" 4 |
275 | .IX Item "int ev_version_minor ()" |
294 | .IX Item "int ev_version_minor ()" |
… | |
… | |
290 | .Sp |
309 | .Sp |
291 | Example: Make sure we haven't accidentally been linked against the wrong |
310 | Example: Make sure we haven't accidentally been linked against the wrong |
292 | version. |
311 | version. |
293 | .Sp |
312 | .Sp |
294 | .Vb 3 |
313 | .Vb 3 |
295 | \& assert (("libev version mismatch", |
314 | \& assert (("libev version mismatch", |
296 | \& ev_version_major () == EV_VERSION_MAJOR |
315 | \& ev_version_major () == EV_VERSION_MAJOR |
297 | \& && ev_version_minor () >= EV_VERSION_MINOR)); |
316 | \& && ev_version_minor () >= EV_VERSION_MINOR)); |
298 | .Ve |
317 | .Ve |
299 | .IP "unsigned int ev_supported_backends ()" 4 |
318 | .IP "unsigned int ev_supported_backends ()" 4 |
300 | .IX Item "unsigned int ev_supported_backends ()" |
319 | .IX Item "unsigned int ev_supported_backends ()" |
301 | Return the set of all backends (i.e. their corresponding \f(CW\*(C`EV_BACKEND_*\*(C'\fR |
320 | Return the set of all backends (i.e. their corresponding \f(CW\*(C`EV_BACKEND_*\*(C'\fR |
302 | value) compiled into this binary of libev (independent of their |
321 | value) compiled into this binary of libev (independent of their |
… | |
… | |
305 | .Sp |
324 | .Sp |
306 | Example: make sure we have the epoll method, because yeah this is cool and |
325 | Example: make sure we have the epoll method, because yeah this is cool and |
307 | a must have and can we have a torrent of it please!!!11 |
326 | a must have and can we have a torrent of it please!!!11 |
308 | .Sp |
327 | .Sp |
309 | .Vb 2 |
328 | .Vb 2 |
310 | \& assert (("sorry, no epoll, no sex", |
329 | \& assert (("sorry, no epoll, no sex", |
311 | \& ev_supported_backends () & EVBACKEND_EPOLL)); |
330 | \& ev_supported_backends () & EVBACKEND_EPOLL)); |
312 | .Ve |
331 | .Ve |
313 | .IP "unsigned int ev_recommended_backends ()" 4 |
332 | .IP "unsigned int ev_recommended_backends ()" 4 |
314 | .IX Item "unsigned int ev_recommended_backends ()" |
333 | .IX Item "unsigned int ev_recommended_backends ()" |
315 | Return the set of all backends compiled into this binary of libev and also |
334 | Return the set of all backends compiled into this binary of libev and also |
316 | recommended for this platform. This set is often smaller than the one |
335 | recommended for this platform. This set is often smaller than the one |
317 | returned by \f(CW\*(C`ev_supported_backends\*(C'\fR, as for example kqueue is broken on |
336 | returned by \f(CW\*(C`ev_supported_backends\*(C'\fR, as for example kqueue is broken on |
318 | most BSDs and will not be autodetected unless you explicitly request it |
337 | most BSDs and will not be auto-detected unless you explicitly request it |
319 | (assuming you know what you are doing). This is the set of backends that |
338 | (assuming you know what you are doing). This is the set of backends that |
320 | libev will probe for if you specify no backends explicitly. |
339 | libev will probe for if you specify no backends explicitly. |
321 | .IP "unsigned int ev_embeddable_backends ()" 4 |
340 | .IP "unsigned int ev_embeddable_backends ()" 4 |
322 | .IX Item "unsigned int ev_embeddable_backends ()" |
341 | .IX Item "unsigned int ev_embeddable_backends ()" |
323 | Returns the set of backends that are embeddable in other event loops. This |
342 | Returns the set of backends that are embeddable in other event loops. This |
… | |
… | |
325 | might be supported on the current system, you would need to look at |
344 | might be supported on the current system, you would need to look at |
326 | \&\f(CW\*(C`ev_embeddable_backends () & ev_supported_backends ()\*(C'\fR, likewise for |
345 | \&\f(CW\*(C`ev_embeddable_backends () & ev_supported_backends ()\*(C'\fR, likewise for |
327 | recommended ones. |
346 | recommended ones. |
328 | .Sp |
347 | .Sp |
329 | See the description of \f(CW\*(C`ev_embed\*(C'\fR watchers for more info. |
348 | See the description of \f(CW\*(C`ev_embed\*(C'\fR watchers for more info. |
330 | .IP "ev_set_allocator (void *(*cb)(void *ptr, long size))" 4 |
349 | .IP "ev_set_allocator (void *(*cb)(void *ptr, long size)) [\s-1NOT\s0 \s-1REENTRANT\s0]" 4 |
331 | .IX Item "ev_set_allocator (void *(*cb)(void *ptr, long size))" |
350 | .IX Item "ev_set_allocator (void *(*cb)(void *ptr, long size)) [NOT REENTRANT]" |
332 | Sets the allocation function to use (the prototype is similar \- the |
351 | Sets the allocation function to use (the prototype is similar \- the |
333 | semantics are identical to the \f(CW\*(C`realloc\*(C'\fR C89/SuS/POSIX function). It is |
352 | semantics are identical to the \f(CW\*(C`realloc\*(C'\fR C89/SuS/POSIX function). It is |
334 | used to allocate and free memory (no surprises here). If it returns zero |
353 | used to allocate and free memory (no surprises here). If it returns zero |
335 | when memory needs to be allocated (\f(CW\*(C`size != 0\*(C'\fR), the library might abort |
354 | when memory needs to be allocated (\f(CW\*(C`size != 0\*(C'\fR), the library might abort |
336 | or take some potentially destructive action. |
355 | or take some potentially destructive action. |
… | |
… | |
362 | \& } |
381 | \& } |
363 | \& |
382 | \& |
364 | \& ... |
383 | \& ... |
365 | \& ev_set_allocator (persistent_realloc); |
384 | \& ev_set_allocator (persistent_realloc); |
366 | .Ve |
385 | .Ve |
367 | .IP "ev_set_syserr_cb (void (*cb)(const char *msg));" 4 |
386 | .IP "ev_set_syserr_cb (void (*cb)(const char *msg)); [\s-1NOT\s0 \s-1REENTRANT\s0]" 4 |
368 | .IX Item "ev_set_syserr_cb (void (*cb)(const char *msg));" |
387 | .IX Item "ev_set_syserr_cb (void (*cb)(const char *msg)); [NOT REENTRANT]" |
369 | Set the callback function to call on a retryable syscall error (such |
388 | Set the callback function to call on a retryable system call error (such |
370 | as failed select, poll, epoll_wait). The message is a printable string |
389 | as failed select, poll, epoll_wait). The message is a printable string |
371 | indicating the system call or subsystem causing the problem. If this |
390 | indicating the system call or subsystem causing the problem. If this |
372 | callback is set, then libev will expect it to remedy the sitution, no |
391 | callback is set, then libev will expect it to remedy the situation, no |
373 | matter what, when it returns. That is, libev will generally retry the |
392 | matter what, when it returns. That is, libev will generally retry the |
374 | requested operation, or, if the condition doesn't go away, do bad stuff |
393 | requested operation, or, if the condition doesn't go away, do bad stuff |
375 | (such as abort). |
394 | (such as abort). |
376 | .Sp |
395 | .Sp |
377 | Example: This is basically the same thing that libev does internally, too. |
396 | Example: This is basically the same thing that libev does internally, too. |
… | |
… | |
406 | from multiple threads, you have to lock (note also that this is unlikely, |
425 | from multiple threads, you have to lock (note also that this is unlikely, |
407 | as loops cannot bes hared easily between threads anyway). |
426 | as loops cannot bes hared easily between threads anyway). |
408 | .Sp |
427 | .Sp |
409 | The default loop is the only loop that can handle \f(CW\*(C`ev_signal\*(C'\fR and |
428 | The default loop is the only loop that can handle \f(CW\*(C`ev_signal\*(C'\fR and |
410 | \&\f(CW\*(C`ev_child\*(C'\fR watchers, and to do this, it always registers a handler |
429 | \&\f(CW\*(C`ev_child\*(C'\fR watchers, and to do this, it always registers a handler |
411 | for \f(CW\*(C`SIGCHLD\*(C'\fR. If this is a problem for your app you can either |
430 | for \f(CW\*(C`SIGCHLD\*(C'\fR. If this is a problem for your application you can either |
412 | create a dynamic loop with \f(CW\*(C`ev_loop_new\*(C'\fR that doesn't do that, or you |
431 | create a dynamic loop with \f(CW\*(C`ev_loop_new\*(C'\fR that doesn't do that, or you |
413 | can simply overwrite the \f(CW\*(C`SIGCHLD\*(C'\fR signal handler \fIafter\fR calling |
432 | can simply overwrite the \f(CW\*(C`SIGCHLD\*(C'\fR signal handler \fIafter\fR calling |
414 | \&\f(CW\*(C`ev_default_init\*(C'\fR. |
433 | \&\f(CW\*(C`ev_default_init\*(C'\fR. |
415 | .Sp |
434 | .Sp |
416 | The flags argument can be used to specify special behaviour or specific |
435 | The flags argument can be used to specify special behaviour or specific |
… | |
… | |
424 | The default flags value. Use this if you have no clue (it's the right |
443 | The default flags value. Use this if you have no clue (it's the right |
425 | thing, believe me). |
444 | thing, believe me). |
426 | .ie n .IP """EVFLAG_NOENV""" 4 |
445 | .ie n .IP """EVFLAG_NOENV""" 4 |
427 | .el .IP "\f(CWEVFLAG_NOENV\fR" 4 |
446 | .el .IP "\f(CWEVFLAG_NOENV\fR" 4 |
428 | .IX Item "EVFLAG_NOENV" |
447 | .IX Item "EVFLAG_NOENV" |
429 | If this flag bit is ored into the flag value (or the program runs setuid |
448 | If this flag bit is or'ed into the flag value (or the program runs setuid |
430 | or setgid) then libev will \fInot\fR look at the environment variable |
449 | or setgid) then libev will \fInot\fR look at the environment variable |
431 | \&\f(CW\*(C`LIBEV_FLAGS\*(C'\fR. Otherwise (the default), this environment variable will |
450 | \&\f(CW\*(C`LIBEV_FLAGS\*(C'\fR. Otherwise (the default), this environment variable will |
432 | override the flags completely if it is found in the environment. This is |
451 | override the flags completely if it is found in the environment. This is |
433 | useful to try out specific backends to test their performance, or to work |
452 | useful to try out specific backends to test their performance, or to work |
434 | around bugs. |
453 | around bugs. |
… | |
… | |
441 | .Sp |
460 | .Sp |
442 | This works by calling \f(CW\*(C`getpid ()\*(C'\fR on every iteration of the loop, |
461 | This works by calling \f(CW\*(C`getpid ()\*(C'\fR on every iteration of the loop, |
443 | and thus this might slow down your event loop if you do a lot of loop |
462 | and thus this might slow down your event loop if you do a lot of loop |
444 | iterations and little real work, but is usually not noticeable (on my |
463 | iterations and little real work, but is usually not noticeable (on my |
445 | GNU/Linux system for example, \f(CW\*(C`getpid\*(C'\fR is actually a simple 5\-insn sequence |
464 | GNU/Linux system for example, \f(CW\*(C`getpid\*(C'\fR is actually a simple 5\-insn sequence |
446 | without a syscall and thus \fIvery\fR fast, but my GNU/Linux system also has |
465 | without a system call and thus \fIvery\fR fast, but my GNU/Linux system also has |
447 | \&\f(CW\*(C`pthread_atfork\*(C'\fR which is even faster). |
466 | \&\f(CW\*(C`pthread_atfork\*(C'\fR which is even faster). |
448 | .Sp |
467 | .Sp |
449 | The big advantage of this flag is that you can forget about fork (and |
468 | The big advantage of this flag is that you can forget about fork (and |
450 | forget about forgetting to tell libev about forking) when you use this |
469 | forget about forgetting to tell libev about forking) when you use this |
451 | flag. |
470 | flag. |
452 | .Sp |
471 | .Sp |
453 | This flag setting cannot be overriden or specified in the \f(CW\*(C`LIBEV_FLAGS\*(C'\fR |
472 | This flag setting cannot be overridden or specified in the \f(CW\*(C`LIBEV_FLAGS\*(C'\fR |
454 | environment variable. |
473 | environment variable. |
455 | .ie n .IP """EVBACKEND_SELECT"" (value 1, portable select backend)" 4 |
474 | .ie n .IP """EVBACKEND_SELECT"" (value 1, portable select backend)" 4 |
456 | .el .IP "\f(CWEVBACKEND_SELECT\fR (value 1, portable select backend)" 4 |
475 | .el .IP "\f(CWEVBACKEND_SELECT\fR (value 1, portable select backend)" 4 |
457 | .IX Item "EVBACKEND_SELECT (value 1, portable select backend)" |
476 | .IX Item "EVBACKEND_SELECT (value 1, portable select backend)" |
458 | This is your standard \fIselect\fR\|(2) backend. Not \fIcompletely\fR standard, as |
477 | This is your standard \fIselect\fR\|(2) backend. Not \fIcompletely\fR standard, as |
… | |
… | |
460 | but if that fails, expect a fairly low limit on the number of fds when |
479 | but if that fails, expect a fairly low limit on the number of fds when |
461 | using this backend. It doesn't scale too well (O(highest_fd)), but its |
480 | using this backend. It doesn't scale too well (O(highest_fd)), but its |
462 | usually the fastest backend for a low number of (low-numbered :) fds. |
481 | usually the fastest backend for a low number of (low-numbered :) fds. |
463 | .Sp |
482 | .Sp |
464 | To get good performance out of this backend you need a high amount of |
483 | To get good performance out of this backend you need a high amount of |
465 | parallelity (most of the file descriptors should be busy). If you are |
484 | parallelism (most of the file descriptors should be busy). If you are |
466 | writing a server, you should \f(CW\*(C`accept ()\*(C'\fR in a loop to accept as many |
485 | writing a server, you should \f(CW\*(C`accept ()\*(C'\fR in a loop to accept as many |
467 | connections as possible during one iteration. You might also want to have |
486 | connections as possible during one iteration. You might also want to have |
468 | a look at \f(CW\*(C`ev_set_io_collect_interval ()\*(C'\fR to increase the amount of |
487 | a look at \f(CW\*(C`ev_set_io_collect_interval ()\*(C'\fR to increase the amount of |
469 | readyness notifications you get per iteration. |
488 | readiness notifications you get per iteration. |
|
|
489 | .Sp |
|
|
490 | 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 |
|
|
491 | \&\f(CW\*(C`writefds\*(C'\fR set (and to work around Microsoft Windows bugs, also onto the |
|
|
492 | \&\f(CW\*(C`exceptfds\*(C'\fR set on that platform). |
470 | .ie n .IP """EVBACKEND_POLL"" (value 2, poll backend, available everywhere except on windows)" 4 |
493 | .ie n .IP """EVBACKEND_POLL"" (value 2, poll backend, available everywhere except on windows)" 4 |
471 | .el .IP "\f(CWEVBACKEND_POLL\fR (value 2, poll backend, available everywhere except on windows)" 4 |
494 | .el .IP "\f(CWEVBACKEND_POLL\fR (value 2, poll backend, available everywhere except on windows)" 4 |
472 | .IX Item "EVBACKEND_POLL (value 2, poll backend, available everywhere except on windows)" |
495 | .IX Item "EVBACKEND_POLL (value 2, poll backend, available everywhere except on windows)" |
473 | And this is your standard \fIpoll\fR\|(2) backend. It's more complicated |
496 | And this is your standard \fIpoll\fR\|(2) backend. It's more complicated |
474 | than select, but handles sparse fds better and has no artificial |
497 | than select, but handles sparse fds better and has no artificial |
475 | limit on the number of fds you can use (except it will slow down |
498 | limit on the number of fds you can use (except it will slow down |
476 | considerably with a lot of inactive fds). It scales similarly to select, |
499 | considerably with a lot of inactive fds). It scales similarly to select, |
477 | i.e. O(total_fds). See the entry for \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR, above, for |
500 | i.e. O(total_fds). See the entry for \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR, above, for |
478 | performance tips. |
501 | performance tips. |
|
|
502 | .Sp |
|
|
503 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR to \f(CW\*(C`POLLIN | POLLERR | POLLHUP\*(C'\fR, and |
|
|
504 | \&\f(CW\*(C`EV_WRITE\*(C'\fR to \f(CW\*(C`POLLOUT | POLLERR | POLLHUP\*(C'\fR. |
479 | .ie n .IP """EVBACKEND_EPOLL"" (value 4, Linux)" 4 |
505 | .ie n .IP """EVBACKEND_EPOLL"" (value 4, Linux)" 4 |
480 | .el .IP "\f(CWEVBACKEND_EPOLL\fR (value 4, Linux)" 4 |
506 | .el .IP "\f(CWEVBACKEND_EPOLL\fR (value 4, Linux)" 4 |
481 | .IX Item "EVBACKEND_EPOLL (value 4, Linux)" |
507 | .IX Item "EVBACKEND_EPOLL (value 4, Linux)" |
482 | For few fds, this backend is a bit little slower than poll and select, |
508 | For few fds, this backend is a bit little slower than poll and select, |
483 | but it scales phenomenally better. While poll and select usually scale |
509 | but it scales phenomenally better. While poll and select usually scale |
484 | like O(total_fds) where n is the total number of fds (or the highest fd), |
510 | like O(total_fds) where n is the total number of fds (or the highest fd), |
485 | epoll scales either O(1) or O(active_fds). The epoll design has a number |
511 | epoll scales either O(1) or O(active_fds). The epoll design has a number |
486 | of shortcomings, such as silently dropping events in some hard-to-detect |
512 | of shortcomings, such as silently dropping events in some hard-to-detect |
487 | cases and requiring a syscall per fd change, no fork support and bad |
513 | cases and requiring a system call per fd change, no fork support and bad |
488 | support for dup. |
514 | support for dup. |
489 | .Sp |
515 | .Sp |
490 | While stopping, setting and starting an I/O watcher in the same iteration |
516 | While stopping, setting and starting an I/O watcher in the same iteration |
491 | will result in some caching, there is still a syscall per such incident |
517 | will result in some caching, there is still a system call per such incident |
492 | (because the fd could point to a different file description now), so its |
518 | (because the fd could point to a different file description now), so its |
493 | best to avoid that. Also, \f(CW\*(C`dup ()\*(C'\fR'ed file descriptors might not work |
519 | best to avoid that. Also, \f(CW\*(C`dup ()\*(C'\fR'ed file descriptors might not work |
494 | very well if you register events for both fds. |
520 | very well if you register events for both fds. |
495 | .Sp |
521 | .Sp |
496 | Please note that epoll sometimes generates spurious notifications, so you |
522 | Please note that epoll sometimes generates spurious notifications, so you |
497 | need to use non-blocking I/O or other means to avoid blocking when no data |
523 | need to use non-blocking I/O or other means to avoid blocking when no data |
498 | (or space) is available. |
524 | (or space) is available. |
499 | .Sp |
525 | .Sp |
500 | Best performance from this backend is achieved by not unregistering all |
526 | Best performance from this backend is achieved by not unregistering all |
501 | watchers for a file descriptor until it has been closed, if possible, i.e. |
527 | watchers for a file descriptor until it has been closed, if possible, |
502 | keep at least one watcher active per fd at all times. |
528 | i.e. keep at least one watcher active per fd at all times. Stopping and |
|
|
529 | starting a watcher (without re-setting it) also usually doesn't cause |
|
|
530 | extra overhead. |
503 | .Sp |
531 | .Sp |
504 | While nominally embeddeble in other event loops, this feature is broken in |
532 | While nominally embeddable in other event loops, this feature is broken in |
505 | all kernel versions tested so far. |
533 | all kernel versions tested so far. |
|
|
534 | .Sp |
|
|
535 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR and \f(CW\*(C`EV_WRITE\*(C'\fR in the same way as |
|
|
536 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
506 | .ie n .IP """EVBACKEND_KQUEUE"" (value 8, most \s-1BSD\s0 clones)" 4 |
537 | .ie n .IP """EVBACKEND_KQUEUE"" (value 8, most \s-1BSD\s0 clones)" 4 |
507 | .el .IP "\f(CWEVBACKEND_KQUEUE\fR (value 8, most \s-1BSD\s0 clones)" 4 |
538 | .el .IP "\f(CWEVBACKEND_KQUEUE\fR (value 8, most \s-1BSD\s0 clones)" 4 |
508 | .IX Item "EVBACKEND_KQUEUE (value 8, most BSD clones)" |
539 | .IX Item "EVBACKEND_KQUEUE (value 8, most BSD clones)" |
509 | Kqueue deserves special mention, as at the time of this writing, it |
540 | Kqueue deserves special mention, as at the time of this writing, it was |
510 | was broken on all BSDs except NetBSD (usually it doesn't work reliably |
541 | broken on all BSDs except NetBSD (usually it doesn't work reliably with |
511 | with anything but sockets and pipes, except on Darwin, where of course |
542 | anything but sockets and pipes, except on Darwin, where of course it's |
512 | it's completely useless). For this reason it's not being \*(L"autodetected\*(R" |
543 | completely useless). For this reason it's not being \*(L"auto-detected\*(R" unless |
513 | unless you explicitly specify it explicitly in the flags (i.e. using |
544 | you explicitly specify it in the flags (i.e. using \f(CW\*(C`EVBACKEND_KQUEUE\*(C'\fR) or |
514 | \&\f(CW\*(C`EVBACKEND_KQUEUE\*(C'\fR) or libev was compiled on a known-to-be-good (\-enough) |
545 | libev was compiled on a known-to-be-good (\-enough) system like NetBSD. |
515 | system like NetBSD. |
|
|
516 | .Sp |
546 | .Sp |
517 | You still can embed kqueue into a normal poll or select backend and use it |
547 | You still can embed kqueue into a normal poll or select backend and use it |
518 | only for sockets (after having made sure that sockets work with kqueue on |
548 | only for sockets (after having made sure that sockets work with kqueue on |
519 | the target platform). See \f(CW\*(C`ev_embed\*(C'\fR watchers for more info. |
549 | the target platform). See \f(CW\*(C`ev_embed\*(C'\fR watchers for more info. |
520 | .Sp |
550 | .Sp |
521 | It scales in the same way as the epoll backend, but the interface to the |
551 | It scales in the same way as the epoll backend, but the interface to the |
522 | kernel is more efficient (which says nothing about its actual speed, of |
552 | kernel is more efficient (which says nothing about its actual speed, of |
523 | course). While stopping, setting and starting an I/O watcher does never |
553 | course). While stopping, setting and starting an I/O watcher does never |
524 | cause an extra syscall as with \f(CW\*(C`EVBACKEND_EPOLL\*(C'\fR, it still adds up to |
554 | cause an extra system call as with \f(CW\*(C`EVBACKEND_EPOLL\*(C'\fR, it still adds up to |
525 | two event changes per incident, support for \f(CW\*(C`fork ()\*(C'\fR is very bad and it |
555 | two event changes per incident. Support for \f(CW\*(C`fork ()\*(C'\fR is very bad and it |
526 | drops fds silently in similarly hard-to-detect cases. |
556 | drops fds silently in similarly hard-to-detect cases. |
527 | .Sp |
557 | .Sp |
528 | This backend usually performs well under most conditions. |
558 | This backend usually performs well under most conditions. |
529 | .Sp |
559 | .Sp |
530 | While nominally embeddable in other event loops, this doesn't work |
560 | While nominally embeddable in other event loops, this doesn't work |
531 | everywhere, so you might need to test for this. And since it is broken |
561 | everywhere, so you might need to test for this. And since it is broken |
532 | almost everywhere, you should only use it when you have a lot of sockets |
562 | almost everywhere, you should only use it when you have a lot of sockets |
533 | (for which it usually works), by embedding it into another event loop |
563 | (for which it usually works), by embedding it into another event loop |
534 | (e.g. \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or \f(CW\*(C`EVBACKEND_POLL\*(C'\fR) and using it only for |
564 | (e.g. \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or \f(CW\*(C`EVBACKEND_POLL\*(C'\fR) and, did I mention it, |
535 | sockets. |
565 | using it only for sockets. |
|
|
566 | .Sp |
|
|
567 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR into an \f(CW\*(C`EVFILT_READ\*(C'\fR kevent with |
|
|
568 | \&\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 |
|
|
569 | \&\f(CW\*(C`NOTE_EOF\*(C'\fR. |
536 | .ie n .IP """EVBACKEND_DEVPOLL"" (value 16, Solaris 8)" 4 |
570 | .ie n .IP """EVBACKEND_DEVPOLL"" (value 16, Solaris 8)" 4 |
537 | .el .IP "\f(CWEVBACKEND_DEVPOLL\fR (value 16, Solaris 8)" 4 |
571 | .el .IP "\f(CWEVBACKEND_DEVPOLL\fR (value 16, Solaris 8)" 4 |
538 | .IX Item "EVBACKEND_DEVPOLL (value 16, Solaris 8)" |
572 | .IX Item "EVBACKEND_DEVPOLL (value 16, Solaris 8)" |
539 | This is not implemented yet (and might never be, unless you send me an |
573 | This is not implemented yet (and might never be, unless you send me an |
540 | implementation). According to reports, \f(CW\*(C`/dev/poll\*(C'\fR only supports sockets |
574 | implementation). According to reports, \f(CW\*(C`/dev/poll\*(C'\fR only supports sockets |
… | |
… | |
544 | .el .IP "\f(CWEVBACKEND_PORT\fR (value 32, Solaris 10)" 4 |
578 | .el .IP "\f(CWEVBACKEND_PORT\fR (value 32, Solaris 10)" 4 |
545 | .IX Item "EVBACKEND_PORT (value 32, Solaris 10)" |
579 | .IX Item "EVBACKEND_PORT (value 32, Solaris 10)" |
546 | This uses the Solaris 10 event port mechanism. As with everything on Solaris, |
580 | This uses the Solaris 10 event port mechanism. As with everything on Solaris, |
547 | it's really slow, but it still scales very well (O(active_fds)). |
581 | it's really slow, but it still scales very well (O(active_fds)). |
548 | .Sp |
582 | .Sp |
549 | Please note that solaris event ports can deliver a lot of spurious |
583 | Please note that Solaris event ports can deliver a lot of spurious |
550 | notifications, so you need to use non-blocking I/O or other means to avoid |
584 | notifications, so you need to use non-blocking I/O or other means to avoid |
551 | blocking when no data (or space) is available. |
585 | blocking when no data (or space) is available. |
552 | .Sp |
586 | .Sp |
553 | While this backend scales well, it requires one system call per active |
587 | While this backend scales well, it requires one system call per active |
554 | file descriptor per loop iteration. For small and medium numbers of file |
588 | file descriptor per loop iteration. For small and medium numbers of file |
555 | descriptors a \*(L"slow\*(R" \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or \f(CW\*(C`EVBACKEND_POLL\*(C'\fR backend |
589 | descriptors a \*(L"slow\*(R" \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or \f(CW\*(C`EVBACKEND_POLL\*(C'\fR backend |
556 | might perform better. |
590 | might perform better. |
557 | .Sp |
591 | .Sp |
558 | On the positive side, ignoring the spurious readyness notifications, this |
592 | On the positive side, with the exception of the spurious readiness |
559 | backend actually performed to specification in all tests and is fully |
593 | notifications, this backend actually performed fully to specification |
560 | embeddable, which is a rare feat among the OS-specific backends. |
594 | in all tests and is fully embeddable, which is a rare feat among the |
|
|
595 | OS-specific backends. |
|
|
596 | .Sp |
|
|
597 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR and \f(CW\*(C`EV_WRITE\*(C'\fR in the same way as |
|
|
598 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
561 | .ie n .IP """EVBACKEND_ALL""" 4 |
599 | .ie n .IP """EVBACKEND_ALL""" 4 |
562 | .el .IP "\f(CWEVBACKEND_ALL\fR" 4 |
600 | .el .IP "\f(CWEVBACKEND_ALL\fR" 4 |
563 | .IX Item "EVBACKEND_ALL" |
601 | .IX Item "EVBACKEND_ALL" |
564 | Try all backends (even potentially broken ones that wouldn't be tried |
602 | Try all backends (even potentially broken ones that wouldn't be tried |
565 | with \f(CW\*(C`EVFLAG_AUTO\*(C'\fR). Since this is a mask, you can do stuff such as |
603 | with \f(CW\*(C`EVFLAG_AUTO\*(C'\fR). Since this is a mask, you can do stuff such as |
… | |
… | |
567 | .Sp |
605 | .Sp |
568 | It is definitely not recommended to use this flag. |
606 | It is definitely not recommended to use this flag. |
569 | .RE |
607 | .RE |
570 | .RS 4 |
608 | .RS 4 |
571 | .Sp |
609 | .Sp |
572 | If one or more of these are ored into the flags value, then only these |
610 | If one or more of these are or'ed into the flags value, then only these |
573 | backends will be tried (in the reverse order as listed here). If none are |
611 | backends will be tried (in the reverse order as listed here). If none are |
574 | specified, all backends in \f(CW\*(C`ev_recommended_backends ()\*(C'\fR will be tried. |
612 | specified, all backends in \f(CW\*(C`ev_recommended_backends ()\*(C'\fR will be tried. |
575 | .Sp |
613 | .Sp |
576 | The most typical usage is like this: |
614 | Example: This is the most typical usage. |
577 | .Sp |
615 | .Sp |
578 | .Vb 2 |
616 | .Vb 2 |
579 | \& if (!ev_default_loop (0)) |
617 | \& if (!ev_default_loop (0)) |
580 | \& fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?"); |
618 | \& fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?"); |
581 | .Ve |
619 | .Ve |
582 | .Sp |
620 | .Sp |
583 | Restrict libev to the select and poll backends, and do not allow |
621 | Example: Restrict libev to the select and poll backends, and do not allow |
584 | environment settings to be taken into account: |
622 | environment settings to be taken into account: |
585 | .Sp |
623 | .Sp |
586 | .Vb 1 |
624 | .Vb 1 |
587 | \& ev_default_loop (EVBACKEND_POLL | EVBACKEND_SELECT | EVFLAG_NOENV); |
625 | \& ev_default_loop (EVBACKEND_POLL | EVBACKEND_SELECT | EVFLAG_NOENV); |
588 | .Ve |
626 | .Ve |
589 | .Sp |
627 | .Sp |
590 | Use whatever libev has to offer, but make sure that kqueue is used if |
628 | Example: Use whatever libev has to offer, but make sure that kqueue is |
591 | available (warning, breaks stuff, best use only with your own private |
629 | used if available (warning, breaks stuff, best use only with your own |
592 | event loop and only if you know the \s-1OS\s0 supports your types of fds): |
630 | private event loop and only if you know the \s-1OS\s0 supports your types of |
|
|
631 | fds): |
593 | .Sp |
632 | .Sp |
594 | .Vb 1 |
633 | .Vb 1 |
595 | \& ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE); |
634 | \& ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE); |
596 | .Ve |
635 | .Ve |
597 | .RE |
636 | .RE |
598 | .IP "struct ev_loop *ev_loop_new (unsigned int flags)" 4 |
637 | .IP "struct ev_loop *ev_loop_new (unsigned int flags)" 4 |
599 | .IX Item "struct ev_loop *ev_loop_new (unsigned int flags)" |
638 | .IX Item "struct ev_loop *ev_loop_new (unsigned int flags)" |
600 | Similar to \f(CW\*(C`ev_default_loop\*(C'\fR, but always creates a new event loop that is |
639 | Similar to \f(CW\*(C`ev_default_loop\*(C'\fR, but always creates a new event loop that is |
… | |
… | |
607 | default loop in the \*(L"main\*(R" or \*(L"initial\*(R" thread. |
646 | default loop in the \*(L"main\*(R" or \*(L"initial\*(R" thread. |
608 | .Sp |
647 | .Sp |
609 | Example: Try to create a event loop that uses epoll and nothing else. |
648 | Example: Try to create a event loop that uses epoll and nothing else. |
610 | .Sp |
649 | .Sp |
611 | .Vb 3 |
650 | .Vb 3 |
612 | \& struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV); |
651 | \& struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV); |
613 | \& if (!epoller) |
652 | \& if (!epoller) |
614 | \& fatal ("no epoll found here, maybe it hides under your chair"); |
653 | \& fatal ("no epoll found here, maybe it hides under your chair"); |
615 | .Ve |
654 | .Ve |
616 | .IP "ev_default_destroy ()" 4 |
655 | .IP "ev_default_destroy ()" 4 |
617 | .IX Item "ev_default_destroy ()" |
656 | .IX Item "ev_default_destroy ()" |
618 | Destroys the default loop again (frees all memory and kernel state |
657 | Destroys the default loop again (frees all memory and kernel state |
619 | etc.). None of the active event watchers will be stopped in the normal |
658 | etc.). None of the active event watchers will be stopped in the normal |
620 | sense, so e.g. \f(CW\*(C`ev_is_active\*(C'\fR might still return true. It is your |
659 | sense, so e.g. \f(CW\*(C`ev_is_active\*(C'\fR might still return true. It is your |
621 | responsibility to either stop all watchers cleanly yoursef \fIbefore\fR |
660 | responsibility to either stop all watchers cleanly yourself \fIbefore\fR |
622 | calling this function, or cope with the fact afterwards (which is usually |
661 | calling this function, or cope with the fact afterwards (which is usually |
623 | the easiest thing, you can just ignore the watchers and/or \f(CW\*(C`free ()\*(C'\fR them |
662 | the easiest thing, you can just ignore the watchers and/or \f(CW\*(C`free ()\*(C'\fR them |
624 | for example). |
663 | for example). |
625 | .Sp |
664 | .Sp |
626 | Note that certain global state, such as signal state, will not be freed by |
665 | Note that certain global state, such as signal state, will not be freed by |
… | |
… | |
657 | .Ve |
696 | .Ve |
658 | .IP "ev_loop_fork (loop)" 4 |
697 | .IP "ev_loop_fork (loop)" 4 |
659 | .IX Item "ev_loop_fork (loop)" |
698 | .IX Item "ev_loop_fork (loop)" |
660 | Like \f(CW\*(C`ev_default_fork\*(C'\fR, but acts on an event loop created by |
699 | Like \f(CW\*(C`ev_default_fork\*(C'\fR, but acts on an event loop created by |
661 | \&\f(CW\*(C`ev_loop_new\*(C'\fR. Yes, you have to call this on every allocated event loop |
700 | \&\f(CW\*(C`ev_loop_new\*(C'\fR. Yes, you have to call this on every allocated event loop |
662 | after fork, and how you do this is entirely your own problem. |
701 | after fork that you want to re-use in the child, and how you do this is |
|
|
702 | entirely your own problem. |
663 | .IP "int ev_is_default_loop (loop)" 4 |
703 | .IP "int ev_is_default_loop (loop)" 4 |
664 | .IX Item "int ev_is_default_loop (loop)" |
704 | .IX Item "int ev_is_default_loop (loop)" |
665 | Returns true when the given loop actually is the default loop, false otherwise. |
705 | Returns true when the given loop is, in fact, the default loop, and false |
|
|
706 | otherwise. |
666 | .IP "unsigned int ev_loop_count (loop)" 4 |
707 | .IP "unsigned int ev_loop_count (loop)" 4 |
667 | .IX Item "unsigned int ev_loop_count (loop)" |
708 | .IX Item "unsigned int ev_loop_count (loop)" |
668 | Returns the count of loop iterations for the loop, which is identical to |
709 | Returns the count of loop iterations for the loop, which is identical to |
669 | the number of times libev did poll for new events. It starts at \f(CW0\fR and |
710 | the number of times libev did poll for new events. It starts at \f(CW0\fR and |
670 | happily wraps around with enough iterations. |
711 | happily wraps around with enough iterations. |
… | |
… | |
681 | Returns the current \*(L"event loop time\*(R", which is the time the event loop |
722 | Returns the current \*(L"event loop time\*(R", which is the time the event loop |
682 | received events and started processing them. This timestamp does not |
723 | received events and started processing them. This timestamp does not |
683 | change as long as callbacks are being processed, and this is also the base |
724 | change as long as callbacks are being processed, and this is also the base |
684 | time used for relative timers. You can treat it as the timestamp of the |
725 | time used for relative timers. You can treat it as the timestamp of the |
685 | event occurring (or more correctly, libev finding out about it). |
726 | event occurring (or more correctly, libev finding out about it). |
|
|
727 | .IP "ev_now_update (loop)" 4 |
|
|
728 | .IX Item "ev_now_update (loop)" |
|
|
729 | Establishes the current time by querying the kernel, updating the time |
|
|
730 | returned by \f(CW\*(C`ev_now ()\*(C'\fR in the progress. This is a costly operation and |
|
|
731 | is usually done automatically within \f(CW\*(C`ev_loop ()\*(C'\fR. |
|
|
732 | .Sp |
|
|
733 | This function is rarely useful, but when some event callback runs for a |
|
|
734 | very long time without entering the event loop, updating libev's idea of |
|
|
735 | the current time is a good idea. |
|
|
736 | .Sp |
|
|
737 | See also \*(L"The special problem of time updates\*(R" in the \f(CW\*(C`ev_timer\*(C'\fR section. |
686 | .IP "ev_loop (loop, int flags)" 4 |
738 | .IP "ev_loop (loop, int flags)" 4 |
687 | .IX Item "ev_loop (loop, int flags)" |
739 | .IX Item "ev_loop (loop, int flags)" |
688 | Finally, this is it, the event handler. This function usually is called |
740 | Finally, this is it, the event handler. This function usually is called |
689 | after you initialised all your watchers and you want to start handling |
741 | after you initialised all your watchers and you want to start handling |
690 | events. |
742 | events. |
… | |
… | |
692 | If the flags argument is specified as \f(CW0\fR, it will not return until |
744 | If the flags argument is specified as \f(CW0\fR, it will not return until |
693 | either no event watchers are active anymore or \f(CW\*(C`ev_unloop\*(C'\fR was called. |
745 | either no event watchers are active anymore or \f(CW\*(C`ev_unloop\*(C'\fR was called. |
694 | .Sp |
746 | .Sp |
695 | Please note that an explicit \f(CW\*(C`ev_unloop\*(C'\fR is usually better than |
747 | Please note that an explicit \f(CW\*(C`ev_unloop\*(C'\fR is usually better than |
696 | relying on all watchers to be stopped when deciding when a program has |
748 | relying on all watchers to be stopped when deciding when a program has |
697 | finished (especially in interactive programs), but having a program that |
749 | finished (especially in interactive programs), but having a program |
698 | automatically loops as long as it has to and no longer by virtue of |
750 | that automatically loops as long as it has to and no longer by virtue |
699 | relying on its watchers stopping correctly is a thing of beauty. |
751 | of relying on its watchers stopping correctly, that is truly a thing of |
|
|
752 | beauty. |
700 | .Sp |
753 | .Sp |
701 | A flags value of \f(CW\*(C`EVLOOP_NONBLOCK\*(C'\fR will look for new events, will handle |
754 | A flags value of \f(CW\*(C`EVLOOP_NONBLOCK\*(C'\fR will look for new events, will handle |
702 | those events and any outstanding ones, but will not block your process in |
755 | those events and any already outstanding ones, but will not block your |
703 | case there are no events and will return after one iteration of the loop. |
756 | process in case there are no events and will return after one iteration of |
|
|
757 | the loop. |
704 | .Sp |
758 | .Sp |
705 | A flags value of \f(CW\*(C`EVLOOP_ONESHOT\*(C'\fR will look for new events (waiting if |
759 | A flags value of \f(CW\*(C`EVLOOP_ONESHOT\*(C'\fR will look for new events (waiting if |
706 | neccessary) and will handle those and any outstanding ones. It will block |
760 | necessary) and will handle those and any already outstanding ones. It |
707 | your process until at least one new event arrives, and will return after |
761 | will block your process until at least one new event arrives (which could |
708 | one iteration of the loop. This is useful if you are waiting for some |
762 | be an event internal to libev itself, so there is no guarentee that a |
709 | external event in conjunction with something not expressible using other |
763 | user-registered callback will be called), and will return after one |
|
|
764 | iteration of the loop. |
|
|
765 | .Sp |
|
|
766 | This is useful if you are waiting for some external event in conjunction |
|
|
767 | with something not expressible using other libev watchers (i.e. "roll your |
710 | libev watchers. However, a pair of \f(CW\*(C`ev_prepare\*(C'\fR/\f(CW\*(C`ev_check\*(C'\fR watchers is |
768 | own \f(CW\*(C`ev_loop\*(C'\fR"). However, a pair of \f(CW\*(C`ev_prepare\*(C'\fR/\f(CW\*(C`ev_check\*(C'\fR watchers is |
711 | usually a better approach for this kind of thing. |
769 | usually a better approach for this kind of thing. |
712 | .Sp |
770 | .Sp |
713 | Here are the gory details of what \f(CW\*(C`ev_loop\*(C'\fR does: |
771 | Here are the gory details of what \f(CW\*(C`ev_loop\*(C'\fR does: |
714 | .Sp |
772 | .Sp |
715 | .Vb 10 |
773 | .Vb 10 |
716 | \& \- Before the first iteration, call any pending watchers. |
774 | \& \- Before the first iteration, call any pending watchers. |
717 | \& * If EVFLAG_FORKCHECK was used, check for a fork. |
775 | \& * If EVFLAG_FORKCHECK was used, check for a fork. |
718 | \& \- If a fork was detected, queue and call all fork watchers. |
776 | \& \- If a fork was detected (by any means), queue and call all fork watchers. |
719 | \& \- Queue and call all prepare watchers. |
777 | \& \- Queue and call all prepare watchers. |
720 | \& \- If we have been forked, recreate the kernel state. |
778 | \& \- If we have been forked, detach and recreate the kernel state |
|
|
779 | \& as to not disturb the other process. |
721 | \& \- Update the kernel state with all outstanding changes. |
780 | \& \- Update the kernel state with all outstanding changes. |
722 | \& \- Update the "event loop time". |
781 | \& \- Update the "event loop time" (ev_now ()). |
723 | \& \- Calculate for how long to sleep or block, if at all |
782 | \& \- Calculate for how long to sleep or block, if at all |
724 | \& (active idle watchers, EVLOOP_NONBLOCK or not having |
783 | \& (active idle watchers, EVLOOP_NONBLOCK or not having |
725 | \& any active watchers at all will result in not sleeping). |
784 | \& any active watchers at all will result in not sleeping). |
726 | \& \- Sleep if the I/O and timer collect interval say so. |
785 | \& \- Sleep if the I/O and timer collect interval say so. |
727 | \& \- Block the process, waiting for any events. |
786 | \& \- Block the process, waiting for any events. |
728 | \& \- Queue all outstanding I/O (fd) events. |
787 | \& \- Queue all outstanding I/O (fd) events. |
729 | \& \- Update the "event loop time" and do time jump handling. |
788 | \& \- Update the "event loop time" (ev_now ()), and do time jump adjustments. |
730 | \& \- Queue all outstanding timers. |
789 | \& \- Queue all expired timers. |
731 | \& \- Queue all outstanding periodics. |
790 | \& \- Queue all expired periodics. |
732 | \& \- If no events are pending now, queue all idle watchers. |
791 | \& \- Unless any events are pending now, queue all idle watchers. |
733 | \& \- Queue all check watchers. |
792 | \& \- Queue all check watchers. |
734 | \& \- Call all queued watchers in reverse order (i.e. check watchers first). |
793 | \& \- Call all queued watchers in reverse order (i.e. check watchers first). |
735 | \& Signals and child watchers are implemented as I/O watchers, and will |
794 | \& Signals and child watchers are implemented as I/O watchers, and will |
736 | \& be handled here by queueing them when their watcher gets executed. |
795 | \& be handled here by queueing them when their watcher gets executed. |
737 | \& \- If ev_unloop has been called, or EVLOOP_ONESHOT or EVLOOP_NONBLOCK |
796 | \& \- If ev_unloop has been called, or EVLOOP_ONESHOT or EVLOOP_NONBLOCK |
… | |
… | |
744 | .Sp |
803 | .Sp |
745 | .Vb 4 |
804 | .Vb 4 |
746 | \& ... queue jobs here, make sure they register event watchers as long |
805 | \& ... queue jobs here, make sure they register event watchers as long |
747 | \& ... as they still have work to do (even an idle watcher will do..) |
806 | \& ... as they still have work to do (even an idle watcher will do..) |
748 | \& ev_loop (my_loop, 0); |
807 | \& ev_loop (my_loop, 0); |
749 | \& ... jobs done. yeah! |
808 | \& ... jobs done or somebody called unloop. yeah! |
750 | .Ve |
809 | .Ve |
751 | .IP "ev_unloop (loop, how)" 4 |
810 | .IP "ev_unloop (loop, how)" 4 |
752 | .IX Item "ev_unloop (loop, how)" |
811 | .IX Item "ev_unloop (loop, how)" |
753 | Can be used to make a call to \f(CW\*(C`ev_loop\*(C'\fR return early (but only after it |
812 | Can be used to make a call to \f(CW\*(C`ev_loop\*(C'\fR return early (but only after it |
754 | has processed all outstanding events). The \f(CW\*(C`how\*(C'\fR argument must be either |
813 | has processed all outstanding events). The \f(CW\*(C`how\*(C'\fR argument must be either |
755 | \&\f(CW\*(C`EVUNLOOP_ONE\*(C'\fR, which will make the innermost \f(CW\*(C`ev_loop\*(C'\fR call return, or |
814 | \&\f(CW\*(C`EVUNLOOP_ONE\*(C'\fR, which will make the innermost \f(CW\*(C`ev_loop\*(C'\fR call return, or |
756 | \&\f(CW\*(C`EVUNLOOP_ALL\*(C'\fR, which will make all nested \f(CW\*(C`ev_loop\*(C'\fR calls return. |
815 | \&\f(CW\*(C`EVUNLOOP_ALL\*(C'\fR, which will make all nested \f(CW\*(C`ev_loop\*(C'\fR calls return. |
757 | .Sp |
816 | .Sp |
758 | This \*(L"unloop state\*(R" will be cleared when entering \f(CW\*(C`ev_loop\*(C'\fR again. |
817 | This \*(L"unloop state\*(R" will be cleared when entering \f(CW\*(C`ev_loop\*(C'\fR again. |
|
|
818 | .Sp |
|
|
819 | It is safe to call \f(CW\*(C`ev_unloop\*(C'\fR from otuside any \f(CW\*(C`ev_loop\*(C'\fR calls. |
759 | .IP "ev_ref (loop)" 4 |
820 | .IP "ev_ref (loop)" 4 |
760 | .IX Item "ev_ref (loop)" |
821 | .IX Item "ev_ref (loop)" |
761 | .PD 0 |
822 | .PD 0 |
762 | .IP "ev_unref (loop)" 4 |
823 | .IP "ev_unref (loop)" 4 |
763 | .IX Item "ev_unref (loop)" |
824 | .IX Item "ev_unref (loop)" |
764 | .PD |
825 | .PD |
765 | Ref/unref can be used to add or remove a reference count on the event |
826 | Ref/unref can be used to add or remove a reference count on the event |
766 | loop: Every watcher keeps one reference, and as long as the reference |
827 | loop: Every watcher keeps one reference, and as long as the reference |
767 | count is nonzero, \f(CW\*(C`ev_loop\*(C'\fR will not return on its own. If you have |
828 | count is nonzero, \f(CW\*(C`ev_loop\*(C'\fR will not return on its own. |
|
|
829 | .Sp |
768 | a watcher you never unregister that should not keep \f(CW\*(C`ev_loop\*(C'\fR from |
830 | If you have a watcher you never unregister that should not keep \f(CW\*(C`ev_loop\*(C'\fR |
769 | returning, \fIev_unref()\fR after starting, and \fIev_ref()\fR before stopping it. For |
831 | from returning, call \fIev_unref()\fR after starting, and \fIev_ref()\fR before |
|
|
832 | stopping it. |
|
|
833 | .Sp |
770 | example, libev itself uses this for its internal signal pipe: It is not |
834 | As an example, libev itself uses this for its internal signal pipe: It is |
771 | visible to the libev user and should not keep \f(CW\*(C`ev_loop\*(C'\fR from exiting if |
835 | not visible to the libev user and should not keep \f(CW\*(C`ev_loop\*(C'\fR from exiting |
772 | no event watchers registered by it are active. It is also an excellent |
836 | if no event watchers registered by it are active. It is also an excellent |
773 | way to do this for generic recurring timers or from within third-party |
837 | way to do this for generic recurring timers or from within third-party |
774 | libraries. Just remember to \fIunref after start\fR and \fIref before stop\fR |
838 | libraries. Just remember to \fIunref after start\fR and \fIref before stop\fR |
775 | (but only if the watcher wasn't active before, or was active before, |
839 | (but only if the watcher wasn't active before, or was active before, |
776 | respectively). |
840 | respectively). |
777 | .Sp |
841 | .Sp |
778 | Example: Create a signal watcher, but keep it from keeping \f(CW\*(C`ev_loop\*(C'\fR |
842 | Example: Create a signal watcher, but keep it from keeping \f(CW\*(C`ev_loop\*(C'\fR |
779 | running when nothing else is active. |
843 | running when nothing else is active. |
780 | .Sp |
844 | .Sp |
781 | .Vb 4 |
845 | .Vb 4 |
782 | \& struct ev_signal exitsig; |
846 | \& struct ev_signal exitsig; |
783 | \& ev_signal_init (&exitsig, sig_cb, SIGINT); |
847 | \& ev_signal_init (&exitsig, sig_cb, SIGINT); |
784 | \& ev_signal_start (loop, &exitsig); |
848 | \& ev_signal_start (loop, &exitsig); |
785 | \& evf_unref (loop); |
849 | \& evf_unref (loop); |
786 | .Ve |
850 | .Ve |
787 | .Sp |
851 | .Sp |
788 | Example: For some weird reason, unregister the above signal handler again. |
852 | Example: For some weird reason, unregister the above signal handler again. |
789 | .Sp |
853 | .Sp |
790 | .Vb 2 |
854 | .Vb 2 |
791 | \& ev_ref (loop); |
855 | \& ev_ref (loop); |
792 | \& ev_signal_stop (loop, &exitsig); |
856 | \& ev_signal_stop (loop, &exitsig); |
793 | .Ve |
857 | .Ve |
794 | .IP "ev_set_io_collect_interval (loop, ev_tstamp interval)" 4 |
858 | .IP "ev_set_io_collect_interval (loop, ev_tstamp interval)" 4 |
795 | .IX Item "ev_set_io_collect_interval (loop, ev_tstamp interval)" |
859 | .IX Item "ev_set_io_collect_interval (loop, ev_tstamp interval)" |
796 | .PD 0 |
860 | .PD 0 |
797 | .IP "ev_set_timeout_collect_interval (loop, ev_tstamp interval)" 4 |
861 | .IP "ev_set_timeout_collect_interval (loop, ev_tstamp interval)" 4 |
798 | .IX Item "ev_set_timeout_collect_interval (loop, ev_tstamp interval)" |
862 | .IX Item "ev_set_timeout_collect_interval (loop, ev_tstamp interval)" |
799 | .PD |
863 | .PD |
800 | These advanced functions influence the time that libev will spend waiting |
864 | These advanced functions influence the time that libev will spend waiting |
801 | for events. Both are by default \f(CW0\fR, meaning that libev will try to |
865 | for events. Both time intervals are by default \f(CW0\fR, meaning that libev |
802 | invoke timer/periodic callbacks and I/O callbacks with minimum latency. |
866 | will try to invoke timer/periodic callbacks and I/O callbacks with minimum |
|
|
867 | latency. |
803 | .Sp |
868 | .Sp |
804 | Setting these to a higher value (the \f(CW\*(C`interval\*(C'\fR \fImust\fR be >= \f(CW0\fR) |
869 | Setting these to a higher value (the \f(CW\*(C`interval\*(C'\fR \fImust\fR be >= \f(CW0\fR) |
805 | allows libev to delay invocation of I/O and timer/periodic callbacks to |
870 | allows libev to delay invocation of I/O and timer/periodic callbacks |
806 | increase efficiency of loop iterations. |
871 | to increase efficiency of loop iterations (or to increase power-saving |
|
|
872 | opportunities). |
807 | .Sp |
873 | .Sp |
808 | The background is that sometimes your program runs just fast enough to |
874 | The idea is that sometimes your program runs just fast enough to handle |
809 | handle one (or very few) event(s) per loop iteration. While this makes |
875 | one (or very few) event(s) per loop iteration. While this makes the |
810 | the program responsive, it also wastes a lot of \s-1CPU\s0 time to poll for new |
876 | program responsive, it also wastes a lot of \s-1CPU\s0 time to poll for new |
811 | events, especially with backends like \f(CW\*(C`select ()\*(C'\fR which have a high |
877 | events, especially with backends like \f(CW\*(C`select ()\*(C'\fR which have a high |
812 | overhead for the actual polling but can deliver many events at once. |
878 | overhead for the actual polling but can deliver many events at once. |
813 | .Sp |
879 | .Sp |
814 | By setting a higher \fIio collect interval\fR you allow libev to spend more |
880 | By setting a higher \fIio collect interval\fR you allow libev to spend more |
815 | time collecting I/O events, so you can handle more events per iteration, |
881 | time collecting I/O events, so you can handle more events per iteration, |
… | |
… | |
817 | \&\f(CW\*(C`ev_timer\*(C'\fR) will be not affected. Setting this to a non-null value will |
883 | \&\f(CW\*(C`ev_timer\*(C'\fR) will be not affected. Setting this to a non-null value will |
818 | introduce an additional \f(CW\*(C`ev_sleep ()\*(C'\fR call into most loop iterations. |
884 | introduce an additional \f(CW\*(C`ev_sleep ()\*(C'\fR call into most loop iterations. |
819 | .Sp |
885 | .Sp |
820 | Likewise, by setting a higher \fItimeout collect interval\fR you allow libev |
886 | Likewise, by setting a higher \fItimeout collect interval\fR you allow libev |
821 | to spend more time collecting timeouts, at the expense of increased |
887 | to spend more time collecting timeouts, at the expense of increased |
822 | latency (the watcher callback will be called later). \f(CW\*(C`ev_io\*(C'\fR watchers |
888 | latency/jitter/inexactness (the watcher callback will be called |
823 | will not be affected. Setting this to a non-null value will not introduce |
889 | later). \f(CW\*(C`ev_io\*(C'\fR watchers will not be affected. Setting this to a non-null |
824 | any overhead in libev. |
890 | value will not introduce any overhead in libev. |
825 | .Sp |
891 | .Sp |
826 | Many (busy) programs can usually benefit by setting the io collect |
892 | Many (busy) programs can usually benefit by setting the I/O collect |
827 | interval to a value near \f(CW0.1\fR or so, which is often enough for |
893 | interval to a value near \f(CW0.1\fR or so, which is often enough for |
828 | interactive servers (of course not for games), likewise for timeouts. It |
894 | interactive servers (of course not for games), likewise for timeouts. It |
829 | usually doesn't make much sense to set it to a lower value than \f(CW0.01\fR, |
895 | usually doesn't make much sense to set it to a lower value than \f(CW0.01\fR, |
830 | as this approsaches the timing granularity of most systems. |
896 | as this approaches the timing granularity of most systems. |
|
|
897 | .Sp |
|
|
898 | Setting the \fItimeout collect interval\fR can improve the opportunity for |
|
|
899 | saving power, as the program will \*(L"bundle\*(R" timer callback invocations that |
|
|
900 | are \*(L"near\*(R" in time together, by delaying some, thus reducing the number of |
|
|
901 | times the process sleeps and wakes up again. Another useful technique to |
|
|
902 | reduce iterations/wake\-ups is to use \f(CW\*(C`ev_periodic\*(C'\fR watchers and make sure |
|
|
903 | they fire on, say, one-second boundaries only. |
|
|
904 | .IP "ev_loop_verify (loop)" 4 |
|
|
905 | .IX Item "ev_loop_verify (loop)" |
|
|
906 | This function only does something when \f(CW\*(C`EV_VERIFY\*(C'\fR support has been |
|
|
907 | compiled in. which is the default for non-minimal builds. It tries to go |
|
|
908 | through all internal structures and checks them for validity. If anything |
|
|
909 | is found to be inconsistent, it will print an error message to standard |
|
|
910 | error and call \f(CW\*(C`abort ()\*(C'\fR. |
|
|
911 | .Sp |
|
|
912 | This can be used to catch bugs inside libev itself: under normal |
|
|
913 | circumstances, this function will never abort as of course libev keeps its |
|
|
914 | data structures consistent. |
831 | .SH "ANATOMY OF A WATCHER" |
915 | .SH "ANATOMY OF A WATCHER" |
832 | .IX Header "ANATOMY OF A WATCHER" |
916 | .IX Header "ANATOMY OF A WATCHER" |
833 | A watcher is a structure that you create and register to record your |
917 | A watcher is a structure that you create and register to record your |
834 | interest in some event. For instance, if you want to wait for \s-1STDIN\s0 to |
918 | interest in some event. For instance, if you want to wait for \s-1STDIN\s0 to |
835 | become readable, you would create an \f(CW\*(C`ev_io\*(C'\fR watcher for that: |
919 | become readable, you would create an \f(CW\*(C`ev_io\*(C'\fR watcher for that: |
836 | .PP |
920 | .PP |
837 | .Vb 5 |
921 | .Vb 5 |
838 | \& static void my_cb (struct ev_loop *loop, struct ev_io *w, int revents) |
922 | \& static void my_cb (struct ev_loop *loop, struct ev_io *w, int revents) |
839 | \& { |
923 | \& { |
840 | \& ev_io_stop (w); |
924 | \& ev_io_stop (w); |
841 | \& ev_unloop (loop, EVUNLOOP_ALL); |
925 | \& ev_unloop (loop, EVUNLOOP_ALL); |
842 | \& } |
926 | \& } |
843 | \& |
927 | \& |
844 | \& struct ev_loop *loop = ev_default_loop (0); |
928 | \& struct ev_loop *loop = ev_default_loop (0); |
845 | \& struct ev_io stdin_watcher; |
929 | \& struct ev_io stdin_watcher; |
846 | \& ev_init (&stdin_watcher, my_cb); |
930 | \& ev_init (&stdin_watcher, my_cb); |
847 | \& ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ); |
931 | \& ev_io_set (&stdin_watcher, STDIN_FILENO, EV_READ); |
848 | \& ev_io_start (loop, &stdin_watcher); |
932 | \& ev_io_start (loop, &stdin_watcher); |
849 | \& ev_loop (loop, 0); |
933 | \& ev_loop (loop, 0); |
850 | .Ve |
934 | .Ve |
851 | .PP |
935 | .PP |
852 | As you can see, you are responsible for allocating the memory for your |
936 | As you can see, you are responsible for allocating the memory for your |
853 | watcher structures (and it is usually a bad idea to do this on the stack, |
937 | watcher structures (and it is usually a bad idea to do this on the stack, |
854 | although this can sometimes be quite valid). |
938 | although this can sometimes be quite valid). |
855 | .PP |
939 | .PP |
856 | Each watcher structure must be initialised by a call to \f(CW\*(C`ev_init |
940 | Each watcher structure must be initialised by a call to \f(CW\*(C`ev_init |
857 | (watcher *, callback)\*(C'\fR, which expects a callback to be provided. This |
941 | (watcher *, callback)\*(C'\fR, which expects a callback to be provided. This |
858 | callback gets invoked each time the event occurs (or, in the case of io |
942 | callback gets invoked each time the event occurs (or, in the case of I/O |
859 | watchers, each time the event loop detects that the file descriptor given |
943 | watchers, each time the event loop detects that the file descriptor given |
860 | is readable and/or writable). |
944 | is readable and/or writable). |
861 | .PP |
945 | .PP |
862 | Each watcher type has its own \f(CW\*(C`ev_<type>_set (watcher *, ...)\*(C'\fR macro |
946 | Each watcher type has its own \f(CW\*(C`ev_<type>_set (watcher *, ...)\*(C'\fR macro |
863 | with arguments specific to this watcher type. There is also a macro |
947 | with arguments specific to this watcher type. There is also a macro |
… | |
… | |
943 | .IX Item "EV_ASYNC" |
1027 | .IX Item "EV_ASYNC" |
944 | The given async watcher has been asynchronously notified (see \f(CW\*(C`ev_async\*(C'\fR). |
1028 | The given async watcher has been asynchronously notified (see \f(CW\*(C`ev_async\*(C'\fR). |
945 | .ie n .IP """EV_ERROR""" 4 |
1029 | .ie n .IP """EV_ERROR""" 4 |
946 | .el .IP "\f(CWEV_ERROR\fR" 4 |
1030 | .el .IP "\f(CWEV_ERROR\fR" 4 |
947 | .IX Item "EV_ERROR" |
1031 | .IX Item "EV_ERROR" |
948 | An unspecified error has occured, the watcher has been stopped. This might |
1032 | An unspecified error has occurred, the watcher has been stopped. This might |
949 | happen because the watcher could not be properly started because libev |
1033 | happen because the watcher could not be properly started because libev |
950 | ran out of memory, a file descriptor was found to be closed or any other |
1034 | ran out of memory, a file descriptor was found to be closed or any other |
951 | problem. You best act on it by reporting the problem and somehow coping |
1035 | problem. You best act on it by reporting the problem and somehow coping |
952 | with the watcher being stopped. |
1036 | with the watcher being stopped. |
953 | .Sp |
1037 | .Sp |
954 | Libev will usually signal a few \*(L"dummy\*(R" events together with an error, |
1038 | Libev will usually signal a few \*(L"dummy\*(R" events together with an error, for |
955 | for example it might indicate that a fd is readable or writable, and if |
1039 | example it might indicate that a fd is readable or writable, and if your |
956 | your callbacks is well-written it can just attempt the operation and cope |
1040 | callbacks is well-written it can just attempt the operation and cope with |
957 | with the error from \fIread()\fR or \fIwrite()\fR. This will not work in multithreaded |
1041 | the error from \fIread()\fR or \fIwrite()\fR. This will not work in multi-threaded |
958 | programs, though, so beware. |
1042 | programs, though, as the fd could already be closed and reused for another |
|
|
1043 | thing, so beware. |
959 | .Sh "\s-1GENERIC\s0 \s-1WATCHER\s0 \s-1FUNCTIONS\s0" |
1044 | .Sh "\s-1GENERIC\s0 \s-1WATCHER\s0 \s-1FUNCTIONS\s0" |
960 | .IX Subsection "GENERIC WATCHER FUNCTIONS" |
1045 | .IX Subsection "GENERIC WATCHER FUNCTIONS" |
961 | In the following description, \f(CW\*(C`TYPE\*(C'\fR stands for the watcher type, |
1046 | In the following description, \f(CW\*(C`TYPE\*(C'\fR stands for the watcher type, |
962 | e.g. \f(CW\*(C`timer\*(C'\fR for \f(CW\*(C`ev_timer\*(C'\fR watchers and \f(CW\*(C`io\*(C'\fR for \f(CW\*(C`ev_io\*(C'\fR watchers. |
1047 | e.g. \f(CW\*(C`timer\*(C'\fR for \f(CW\*(C`ev_timer\*(C'\fR watchers and \f(CW\*(C`io\*(C'\fR for \f(CW\*(C`ev_io\*(C'\fR watchers. |
963 | .ie n .IP """ev_init"" (ev_TYPE *watcher, callback)" 4 |
1048 | .ie n .IP """ev_init"" (ev_TYPE *watcher, callback)" 4 |
… | |
… | |
973 | You can reinitialise a watcher at any time as long as it has been stopped |
1058 | You can reinitialise a watcher at any time as long as it has been stopped |
974 | (or never started) and there are no pending events outstanding. |
1059 | (or never started) and there are no pending events outstanding. |
975 | .Sp |
1060 | .Sp |
976 | The callback is always of type \f(CW\*(C`void (*)(ev_loop *loop, ev_TYPE *watcher, |
1061 | The callback is always of type \f(CW\*(C`void (*)(ev_loop *loop, ev_TYPE *watcher, |
977 | int revents)\*(C'\fR. |
1062 | int revents)\*(C'\fR. |
|
|
1063 | .Sp |
|
|
1064 | Example: Initialise an \f(CW\*(C`ev_io\*(C'\fR watcher in two steps. |
|
|
1065 | .Sp |
|
|
1066 | .Vb 3 |
|
|
1067 | \& ev_io w; |
|
|
1068 | \& ev_init (&w, my_cb); |
|
|
1069 | \& ev_io_set (&w, STDIN_FILENO, EV_READ); |
|
|
1070 | .Ve |
978 | .ie n .IP """ev_TYPE_set"" (ev_TYPE *, [args])" 4 |
1071 | .ie n .IP """ev_TYPE_set"" (ev_TYPE *, [args])" 4 |
979 | .el .IP "\f(CWev_TYPE_set\fR (ev_TYPE *, [args])" 4 |
1072 | .el .IP "\f(CWev_TYPE_set\fR (ev_TYPE *, [args])" 4 |
980 | .IX Item "ev_TYPE_set (ev_TYPE *, [args])" |
1073 | .IX Item "ev_TYPE_set (ev_TYPE *, [args])" |
981 | This macro initialises the type-specific parts of a watcher. You need to |
1074 | This macro initialises the type-specific parts of a watcher. You need to |
982 | call \f(CW\*(C`ev_init\*(C'\fR at least once before you call this macro, but you can |
1075 | call \f(CW\*(C`ev_init\*(C'\fR at least once before you call this macro, but you can |
… | |
… | |
984 | macro on a watcher that is active (it can be pending, however, which is a |
1077 | macro on a watcher that is active (it can be pending, however, which is a |
985 | difference to the \f(CW\*(C`ev_init\*(C'\fR macro). |
1078 | difference to the \f(CW\*(C`ev_init\*(C'\fR macro). |
986 | .Sp |
1079 | .Sp |
987 | Although some watcher types do not have type-specific arguments |
1080 | Although some watcher types do not have type-specific arguments |
988 | (e.g. \f(CW\*(C`ev_prepare\*(C'\fR) you still need to call its \f(CW\*(C`set\*(C'\fR macro. |
1081 | (e.g. \f(CW\*(C`ev_prepare\*(C'\fR) you still need to call its \f(CW\*(C`set\*(C'\fR macro. |
|
|
1082 | .Sp |
|
|
1083 | See \f(CW\*(C`ev_init\*(C'\fR, above, for an example. |
989 | .ie n .IP """ev_TYPE_init"" (ev_TYPE *watcher, callback, [args])" 4 |
1084 | .ie n .IP """ev_TYPE_init"" (ev_TYPE *watcher, callback, [args])" 4 |
990 | .el .IP "\f(CWev_TYPE_init\fR (ev_TYPE *watcher, callback, [args])" 4 |
1085 | .el .IP "\f(CWev_TYPE_init\fR (ev_TYPE *watcher, callback, [args])" 4 |
991 | .IX Item "ev_TYPE_init (ev_TYPE *watcher, callback, [args])" |
1086 | .IX Item "ev_TYPE_init (ev_TYPE *watcher, callback, [args])" |
992 | This convinience macro rolls both \f(CW\*(C`ev_init\*(C'\fR and \f(CW\*(C`ev_TYPE_set\*(C'\fR macro |
1087 | This convenience macro rolls both \f(CW\*(C`ev_init\*(C'\fR and \f(CW\*(C`ev_TYPE_set\*(C'\fR macro |
993 | calls into a single call. This is the most convinient method to initialise |
1088 | calls into a single call. This is the most convenient method to initialise |
994 | a watcher. The same limitations apply, of course. |
1089 | a watcher. The same limitations apply, of course. |
|
|
1090 | .Sp |
|
|
1091 | Example: Initialise and set an \f(CW\*(C`ev_io\*(C'\fR watcher in one step. |
|
|
1092 | .Sp |
|
|
1093 | .Vb 1 |
|
|
1094 | \& ev_io_init (&w, my_cb, STDIN_FILENO, EV_READ); |
|
|
1095 | .Ve |
995 | .ie n .IP """ev_TYPE_start"" (loop *, ev_TYPE *watcher)" 4 |
1096 | .ie n .IP """ev_TYPE_start"" (loop *, ev_TYPE *watcher)" 4 |
996 | .el .IP "\f(CWev_TYPE_start\fR (loop *, ev_TYPE *watcher)" 4 |
1097 | .el .IP "\f(CWev_TYPE_start\fR (loop *, ev_TYPE *watcher)" 4 |
997 | .IX Item "ev_TYPE_start (loop *, ev_TYPE *watcher)" |
1098 | .IX Item "ev_TYPE_start (loop *, ev_TYPE *watcher)" |
998 | Starts (activates) the given watcher. Only active watchers will receive |
1099 | Starts (activates) the given watcher. Only active watchers will receive |
999 | events. If the watcher is already active nothing will happen. |
1100 | events. If the watcher is already active nothing will happen. |
|
|
1101 | .Sp |
|
|
1102 | Example: Start the \f(CW\*(C`ev_io\*(C'\fR watcher that is being abused as example in this |
|
|
1103 | whole section. |
|
|
1104 | .Sp |
|
|
1105 | .Vb 1 |
|
|
1106 | \& ev_io_start (EV_DEFAULT_UC, &w); |
|
|
1107 | .Ve |
1000 | .ie n .IP """ev_TYPE_stop"" (loop *, ev_TYPE *watcher)" 4 |
1108 | .ie n .IP """ev_TYPE_stop"" (loop *, ev_TYPE *watcher)" 4 |
1001 | .el .IP "\f(CWev_TYPE_stop\fR (loop *, ev_TYPE *watcher)" 4 |
1109 | .el .IP "\f(CWev_TYPE_stop\fR (loop *, ev_TYPE *watcher)" 4 |
1002 | .IX Item "ev_TYPE_stop (loop *, ev_TYPE *watcher)" |
1110 | .IX Item "ev_TYPE_stop (loop *, ev_TYPE *watcher)" |
1003 | Stops the given watcher again (if active) and clears the pending |
1111 | Stops the given watcher if active, and clears the pending status (whether |
|
|
1112 | the watcher was active or not). |
|
|
1113 | .Sp |
1004 | status. It is possible that stopped watchers are pending (for example, |
1114 | It is possible that stopped watchers are pending \- for example, |
1005 | non-repeating timers are being stopped when they become pending), but |
1115 | non-repeating timers are being stopped when they become pending \- but |
1006 | \&\f(CW\*(C`ev_TYPE_stop\*(C'\fR ensures that the watcher is neither active nor pending. If |
1116 | calling \f(CW\*(C`ev_TYPE_stop\*(C'\fR ensures that the watcher is neither active nor |
1007 | you want to free or reuse the memory used by the watcher it is therefore a |
1117 | pending. If you want to free or reuse the memory used by the watcher it is |
1008 | good idea to always call its \f(CW\*(C`ev_TYPE_stop\*(C'\fR function. |
1118 | therefore a good idea to always call its \f(CW\*(C`ev_TYPE_stop\*(C'\fR function. |
1009 | .IP "bool ev_is_active (ev_TYPE *watcher)" 4 |
1119 | .IP "bool ev_is_active (ev_TYPE *watcher)" 4 |
1010 | .IX Item "bool ev_is_active (ev_TYPE *watcher)" |
1120 | .IX Item "bool ev_is_active (ev_TYPE *watcher)" |
1011 | Returns a true value iff the watcher is active (i.e. it has been started |
1121 | Returns a true value iff the watcher is active (i.e. it has been started |
1012 | and not yet been stopped). As long as a watcher is active you must not modify |
1122 | and not yet been stopped). As long as a watcher is active you must not modify |
1013 | it. |
1123 | it. |
… | |
… | |
1057 | or might not have been adjusted to be within valid range. |
1167 | or might not have been adjusted to be within valid range. |
1058 | .IP "ev_invoke (loop, ev_TYPE *watcher, int revents)" 4 |
1168 | .IP "ev_invoke (loop, ev_TYPE *watcher, int revents)" 4 |
1059 | .IX Item "ev_invoke (loop, ev_TYPE *watcher, int revents)" |
1169 | .IX Item "ev_invoke (loop, ev_TYPE *watcher, int revents)" |
1060 | 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 |
1170 | 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 |
1061 | \&\f(CW\*(C`loop\*(C'\fR nor \f(CW\*(C`revents\*(C'\fR need to be valid as long as the watcher callback |
1171 | \&\f(CW\*(C`loop\*(C'\fR nor \f(CW\*(C`revents\*(C'\fR need to be valid as long as the watcher callback |
1062 | can deal with that fact. |
1172 | can deal with that fact, as both are simply passed through to the |
|
|
1173 | callback. |
1063 | .IP "int ev_clear_pending (loop, ev_TYPE *watcher)" 4 |
1174 | .IP "int ev_clear_pending (loop, ev_TYPE *watcher)" 4 |
1064 | .IX Item "int ev_clear_pending (loop, ev_TYPE *watcher)" |
1175 | .IX Item "int ev_clear_pending (loop, ev_TYPE *watcher)" |
1065 | If the watcher is pending, this function returns clears its pending status |
1176 | If the watcher is pending, this function clears its pending status and |
1066 | and returns its \f(CW\*(C`revents\*(C'\fR bitset (as if its callback was invoked). If the |
1177 | returns its \f(CW\*(C`revents\*(C'\fR bitset (as if its callback was invoked). If the |
1067 | watcher isn't pending it does nothing and returns \f(CW0\fR. |
1178 | watcher isn't pending it does nothing and returns \f(CW0\fR. |
|
|
1179 | .Sp |
|
|
1180 | Sometimes it can be useful to \*(L"poll\*(R" a watcher instead of waiting for its |
|
|
1181 | callback to be invoked, which can be accomplished with this function. |
1068 | .Sh "\s-1ASSOCIATING\s0 \s-1CUSTOM\s0 \s-1DATA\s0 \s-1WITH\s0 A \s-1WATCHER\s0" |
1182 | .Sh "\s-1ASSOCIATING\s0 \s-1CUSTOM\s0 \s-1DATA\s0 \s-1WITH\s0 A \s-1WATCHER\s0" |
1069 | .IX Subsection "ASSOCIATING CUSTOM DATA WITH A WATCHER" |
1183 | .IX Subsection "ASSOCIATING CUSTOM DATA WITH A WATCHER" |
1070 | Each watcher has, by default, a member \f(CW\*(C`void *data\*(C'\fR that you can change |
1184 | Each watcher has, by default, a member \f(CW\*(C`void *data\*(C'\fR that you can change |
1071 | and read at any time, libev will completely ignore it. This can be used |
1185 | and read at any time: libev will completely ignore it. This can be used |
1072 | to associate arbitrary data with your watcher. If you need more data and |
1186 | to associate arbitrary data with your watcher. If you need more data and |
1073 | don't want to allocate memory and store a pointer to it in that data |
1187 | don't want to allocate memory and store a pointer to it in that data |
1074 | member, you can also \*(L"subclass\*(R" the watcher type and provide your own |
1188 | member, you can also \*(L"subclass\*(R" the watcher type and provide your own |
1075 | data: |
1189 | data: |
1076 | .PP |
1190 | .PP |
1077 | .Vb 7 |
1191 | .Vb 7 |
1078 | \& struct my_io |
1192 | \& struct my_io |
1079 | \& { |
1193 | \& { |
1080 | \& struct ev_io io; |
1194 | \& struct ev_io io; |
1081 | \& int otherfd; |
1195 | \& int otherfd; |
1082 | \& void *somedata; |
1196 | \& void *somedata; |
1083 | \& struct whatever *mostinteresting; |
1197 | \& struct whatever *mostinteresting; |
1084 | \& } |
1198 | \& }; |
|
|
1199 | \& |
|
|
1200 | \& ... |
|
|
1201 | \& struct my_io w; |
|
|
1202 | \& ev_io_init (&w.io, my_cb, fd, EV_READ); |
1085 | .Ve |
1203 | .Ve |
1086 | .PP |
1204 | .PP |
1087 | And since your callback will be called with a pointer to the watcher, you |
1205 | And since your callback will be called with a pointer to the watcher, you |
1088 | can cast it back to your own type: |
1206 | can cast it back to your own type: |
1089 | .PP |
1207 | .PP |
1090 | .Vb 5 |
1208 | .Vb 5 |
1091 | \& static void my_cb (struct ev_loop *loop, struct ev_io *w_, int revents) |
1209 | \& static void my_cb (struct ev_loop *loop, struct ev_io *w_, int revents) |
1092 | \& { |
1210 | \& { |
1093 | \& struct my_io *w = (struct my_io *)w_; |
1211 | \& struct my_io *w = (struct my_io *)w_; |
1094 | \& ... |
1212 | \& ... |
1095 | \& } |
1213 | \& } |
1096 | .Ve |
1214 | .Ve |
1097 | .PP |
1215 | .PP |
1098 | More interesting and less C\-conformant ways of casting your callback type |
1216 | More interesting and less C\-conformant ways of casting your callback type |
1099 | instead have been omitted. |
1217 | instead have been omitted. |
1100 | .PP |
1218 | .PP |
1101 | Another common scenario is having some data structure with multiple |
1219 | Another common scenario is to use some data structure with multiple |
1102 | watchers: |
1220 | embedded watchers: |
1103 | .PP |
1221 | .PP |
1104 | .Vb 6 |
1222 | .Vb 6 |
1105 | \& struct my_biggy |
1223 | \& struct my_biggy |
1106 | \& { |
1224 | \& { |
1107 | \& int some_data; |
1225 | \& int some_data; |
1108 | \& ev_timer t1; |
1226 | \& ev_timer t1; |
1109 | \& ev_timer t2; |
1227 | \& ev_timer t2; |
1110 | \& } |
1228 | \& } |
1111 | .Ve |
1229 | .Ve |
1112 | .PP |
1230 | .PP |
1113 | In this case getting the pointer to \f(CW\*(C`my_biggy\*(C'\fR is a bit more complicated, |
1231 | In this case getting the pointer to \f(CW\*(C`my_biggy\*(C'\fR is a bit more |
1114 | you need to use \f(CW\*(C`offsetof\*(C'\fR: |
1232 | complicated: Either you store the address of your \f(CW\*(C`my_biggy\*(C'\fR struct |
|
|
1233 | in the \f(CW\*(C`data\*(C'\fR member of the watcher (for woozies), or you need to use |
|
|
1234 | some pointer arithmetic using \f(CW\*(C`offsetof\*(C'\fR inside your watchers (for real |
|
|
1235 | programmers): |
1115 | .PP |
1236 | .PP |
1116 | .Vb 1 |
1237 | .Vb 1 |
1117 | \& #include <stddef.h> |
1238 | \& #include <stddef.h> |
1118 | \& |
1239 | \& |
1119 | \& static void |
1240 | \& static void |
1120 | \& t1_cb (EV_P_ struct ev_timer *w, int revents) |
1241 | \& t1_cb (EV_P_ struct ev_timer *w, int revents) |
1121 | \& { |
1242 | \& { |
1122 | \& struct my_biggy big = (struct my_biggy * |
1243 | \& struct my_biggy big = (struct my_biggy * |
1123 | \& (((char *)w) \- offsetof (struct my_biggy, t1)); |
1244 | \& (((char *)w) \- offsetof (struct my_biggy, t1)); |
1124 | \& } |
1245 | \& } |
1125 | \& |
1246 | \& |
1126 | \& static void |
1247 | \& static void |
1127 | \& t2_cb (EV_P_ struct ev_timer *w, int revents) |
1248 | \& t2_cb (EV_P_ struct ev_timer *w, int revents) |
1128 | \& { |
1249 | \& { |
1129 | \& struct my_biggy big = (struct my_biggy * |
1250 | \& struct my_biggy big = (struct my_biggy * |
1130 | \& (((char *)w) \- offsetof (struct my_biggy, t2)); |
1251 | \& (((char *)w) \- offsetof (struct my_biggy, t2)); |
1131 | \& } |
1252 | \& } |
1132 | .Ve |
1253 | .Ve |
1133 | .SH "WATCHER TYPES" |
1254 | .SH "WATCHER TYPES" |
1134 | .IX Header "WATCHER TYPES" |
1255 | .IX Header "WATCHER TYPES" |
1135 | This section describes each watcher in detail, but will not repeat |
1256 | This section describes each watcher in detail, but will not repeat |
1136 | information given in the last section. Any initialisation/set macros, |
1257 | information given in the last section. Any initialisation/set macros, |
… | |
… | |
1158 | In general you can register as many read and/or write event watchers per |
1279 | In general you can register as many read and/or write event watchers per |
1159 | fd as you want (as long as you don't confuse yourself). Setting all file |
1280 | fd as you want (as long as you don't confuse yourself). Setting all file |
1160 | descriptors to non-blocking mode is also usually a good idea (but not |
1281 | descriptors to non-blocking mode is also usually a good idea (but not |
1161 | required if you know what you are doing). |
1282 | required if you know what you are doing). |
1162 | .PP |
1283 | .PP |
1163 | If you must do this, then force the use of a known-to-be-good backend |
1284 | If you cannot use non-blocking mode, then force the use of a |
1164 | (at the time of this writing, this includes only \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR and |
1285 | known-to-be-good backend (at the time of this writing, this includes only |
1165 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR). |
1286 | \&\f(CW\*(C`EVBACKEND_SELECT\*(C'\fR and \f(CW\*(C`EVBACKEND_POLL\*(C'\fR). |
1166 | .PP |
1287 | .PP |
1167 | Another thing you have to watch out for is that it is quite easy to |
1288 | Another thing you have to watch out for is that it is quite easy to |
1168 | receive \*(L"spurious\*(R" readyness notifications, that is your callback might |
1289 | receive \*(L"spurious\*(R" readiness notifications, that is your callback might |
1169 | be called with \f(CW\*(C`EV_READ\*(C'\fR but a subsequent \f(CW\*(C`read\*(C'\fR(2) will actually block |
1290 | be called with \f(CW\*(C`EV_READ\*(C'\fR but a subsequent \f(CW\*(C`read\*(C'\fR(2) will actually block |
1170 | because there is no data. Not only are some backends known to create a |
1291 | because there is no data. Not only are some backends known to create a |
1171 | lot of those (for example solaris ports), it is very easy to get into |
1292 | lot of those (for example Solaris ports), it is very easy to get into |
1172 | this situation even with a relatively standard program structure. Thus |
1293 | this situation even with a relatively standard program structure. Thus |
1173 | it is best to always use non-blocking I/O: An extra \f(CW\*(C`read\*(C'\fR(2) returning |
1294 | it is best to always use non-blocking I/O: An extra \f(CW\*(C`read\*(C'\fR(2) returning |
1174 | \&\f(CW\*(C`EAGAIN\*(C'\fR is far preferable to a program hanging until some data arrives. |
1295 | \&\f(CW\*(C`EAGAIN\*(C'\fR is far preferable to a program hanging until some data arrives. |
1175 | .PP |
1296 | .PP |
1176 | If you cannot run the fd in non-blocking mode (for example you should not |
1297 | If you cannot run the fd in non-blocking mode (for example you should |
1177 | play around with an Xlib connection), then you have to seperately re-test |
1298 | not play around with an Xlib connection), then you have to separately |
1178 | whether a file descriptor is really ready with a known-to-be good interface |
1299 | re-test whether a file descriptor is really ready with a known-to-be good |
1179 | such as poll (fortunately in our Xlib example, Xlib already does this on |
1300 | interface such as poll (fortunately in our Xlib example, Xlib already |
1180 | its own, so its quite safe to use). |
1301 | does this on its own, so its quite safe to use). Some people additionally |
|
|
1302 | use \f(CW\*(C`SIGALRM\*(C'\fR and an interval timer, just to be sure you won't block |
|
|
1303 | indefinitely. |
|
|
1304 | .PP |
|
|
1305 | But really, best use non-blocking mode. |
1181 | .PP |
1306 | .PP |
1182 | \fIThe special problem of disappearing file descriptors\fR |
1307 | \fIThe special problem of disappearing file descriptors\fR |
1183 | .IX Subsection "The special problem of disappearing file descriptors" |
1308 | .IX Subsection "The special problem of disappearing file descriptors" |
1184 | .PP |
1309 | .PP |
1185 | Some backends (e.g. kqueue, epoll) need to be told about closing a file |
1310 | Some backends (e.g. kqueue, epoll) need to be told about closing a file |
1186 | descriptor (either by calling \f(CW\*(C`close\*(C'\fR explicitly or by any other means, |
1311 | descriptor (either due to calling \f(CW\*(C`close\*(C'\fR explicitly or any other means, |
1187 | such as \f(CW\*(C`dup\*(C'\fR). The reason is that you register interest in some file |
1312 | such as \f(CW\*(C`dup2\*(C'\fR). The reason is that you register interest in some file |
1188 | descriptor, but when it goes away, the operating system will silently drop |
1313 | descriptor, but when it goes away, the operating system will silently drop |
1189 | this interest. If another file descriptor with the same number then is |
1314 | this interest. If another file descriptor with the same number then is |
1190 | registered with libev, there is no efficient way to see that this is, in |
1315 | registered with libev, there is no efficient way to see that this is, in |
1191 | fact, a different file descriptor. |
1316 | fact, a different file descriptor. |
1192 | .PP |
1317 | .PP |
… | |
… | |
1226 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
1351 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
1227 | .PP |
1352 | .PP |
1228 | \fIThe special problem of \s-1SIGPIPE\s0\fR |
1353 | \fIThe special problem of \s-1SIGPIPE\s0\fR |
1229 | .IX Subsection "The special problem of SIGPIPE" |
1354 | .IX Subsection "The special problem of SIGPIPE" |
1230 | .PP |
1355 | .PP |
1231 | While not really specific to libev, it is easy to forget about \s-1SIGPIPE:\s0 |
1356 | While not really specific to libev, it is easy to forget about \f(CW\*(C`SIGPIPE\*(C'\fR: |
1232 | when reading from a pipe whose other end has been closed, your program |
1357 | when writing to a pipe whose other end has been closed, your program gets |
1233 | gets send a \s-1SIGPIPE\s0, which, by default, aborts your program. For most |
1358 | sent a \s-1SIGPIPE\s0, which, by default, aborts your program. For most programs |
1234 | programs this is sensible behaviour, for daemons, this is usually |
1359 | this is sensible behaviour, for daemons, this is usually undesirable. |
1235 | undesirable. |
|
|
1236 | .PP |
1360 | .PP |
1237 | So when you encounter spurious, unexplained daemon exits, make sure you |
1361 | So when you encounter spurious, unexplained daemon exits, make sure you |
1238 | ignore \s-1SIGPIPE\s0 (and maybe make sure you log the exit status of your daemon |
1362 | ignore \s-1SIGPIPE\s0 (and maybe make sure you log the exit status of your daemon |
1239 | somewhere, as that would have given you a big clue). |
1363 | somewhere, as that would have given you a big clue). |
1240 | .PP |
1364 | .PP |
… | |
… | |
1245 | .PD 0 |
1369 | .PD 0 |
1246 | .IP "ev_io_set (ev_io *, int fd, int events)" 4 |
1370 | .IP "ev_io_set (ev_io *, int fd, int events)" 4 |
1247 | .IX Item "ev_io_set (ev_io *, int fd, int events)" |
1371 | .IX Item "ev_io_set (ev_io *, int fd, int events)" |
1248 | .PD |
1372 | .PD |
1249 | Configures an \f(CW\*(C`ev_io\*(C'\fR watcher. The \f(CW\*(C`fd\*(C'\fR is the file descriptor to |
1373 | Configures an \f(CW\*(C`ev_io\*(C'\fR watcher. The \f(CW\*(C`fd\*(C'\fR is the file descriptor to |
1250 | rceeive events for and events is either \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR or |
1374 | 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 |
1251 | \&\f(CW\*(C`EV_READ | EV_WRITE\*(C'\fR to receive the given events. |
1375 | \&\f(CW\*(C`EV_READ | EV_WRITE\*(C'\fR, to express the desire to receive the given events. |
1252 | .IP "int fd [read\-only]" 4 |
1376 | .IP "int fd [read\-only]" 4 |
1253 | .IX Item "int fd [read-only]" |
1377 | .IX Item "int fd [read-only]" |
1254 | The file descriptor being watched. |
1378 | The file descriptor being watched. |
1255 | .IP "int events [read\-only]" 4 |
1379 | .IP "int events [read\-only]" 4 |
1256 | .IX Item "int events [read-only]" |
1380 | .IX Item "int events [read-only]" |
… | |
… | |
1262 | Example: Call \f(CW\*(C`stdin_readable_cb\*(C'\fR when \s-1STDIN_FILENO\s0 has become, well |
1386 | Example: Call \f(CW\*(C`stdin_readable_cb\*(C'\fR when \s-1STDIN_FILENO\s0 has become, well |
1263 | readable, but only once. Since it is likely line-buffered, you could |
1387 | readable, but only once. Since it is likely line-buffered, you could |
1264 | attempt to read a whole line in the callback. |
1388 | attempt to read a whole line in the callback. |
1265 | .PP |
1389 | .PP |
1266 | .Vb 6 |
1390 | .Vb 6 |
1267 | \& static void |
1391 | \& static void |
1268 | \& stdin_readable_cb (struct ev_loop *loop, struct ev_io *w, int revents) |
1392 | \& stdin_readable_cb (struct ev_loop *loop, struct ev_io *w, int revents) |
1269 | \& { |
1393 | \& { |
1270 | \& ev_io_stop (loop, w); |
1394 | \& ev_io_stop (loop, w); |
1271 | \& .. read from stdin here (or from w\->fd) and haqndle any I/O errors |
1395 | \& .. read from stdin here (or from w\->fd) and handle any I/O errors |
1272 | \& } |
1396 | \& } |
1273 | \& |
1397 | \& |
1274 | \& ... |
1398 | \& ... |
1275 | \& struct ev_loop *loop = ev_default_init (0); |
1399 | \& struct ev_loop *loop = ev_default_init (0); |
1276 | \& struct ev_io stdin_readable; |
1400 | \& struct ev_io stdin_readable; |
1277 | \& ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ); |
1401 | \& ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ); |
1278 | \& ev_io_start (loop, &stdin_readable); |
1402 | \& ev_io_start (loop, &stdin_readable); |
1279 | \& ev_loop (loop, 0); |
1403 | \& ev_loop (loop, 0); |
1280 | .Ve |
1404 | .Ve |
1281 | .ie n .Sh """ev_timer"" \- relative and optionally repeating timeouts" |
1405 | .ie n .Sh """ev_timer"" \- relative and optionally repeating timeouts" |
1282 | .el .Sh "\f(CWev_timer\fP \- relative and optionally repeating timeouts" |
1406 | .el .Sh "\f(CWev_timer\fP \- relative and optionally repeating timeouts" |
1283 | .IX Subsection "ev_timer - relative and optionally repeating timeouts" |
1407 | .IX Subsection "ev_timer - relative and optionally repeating timeouts" |
1284 | Timer watchers are simple relative timers that generate an event after a |
1408 | Timer watchers are simple relative timers that generate an event after a |
1285 | given time, and optionally repeating in regular intervals after that. |
1409 | given time, and optionally repeating in regular intervals after that. |
1286 | .PP |
1410 | .PP |
1287 | The timers are based on real time, that is, if you register an event that |
1411 | The timers are based on real time, that is, if you register an event that |
1288 | times out after an hour and you reset your system clock to last years |
1412 | times out after an hour and you reset your system clock to January last |
1289 | time, it will still time out after (roughly) and hour. \*(L"Roughly\*(R" because |
1413 | year, it will still time out after (roughly) one hour. \*(L"Roughly\*(R" because |
1290 | detecting time jumps is hard, and some inaccuracies are unavoidable (the |
1414 | detecting time jumps is hard, and some inaccuracies are unavoidable (the |
1291 | monotonic clock option helps a lot here). |
1415 | monotonic clock option helps a lot here). |
|
|
1416 | .PP |
|
|
1417 | The callback is guaranteed to be invoked only \fIafter\fR its timeout has |
|
|
1418 | passed, but if multiple timers become ready during the same loop iteration |
|
|
1419 | then order of execution is undefined. |
|
|
1420 | .PP |
|
|
1421 | \fIThe special problem of time updates\fR |
|
|
1422 | .IX Subsection "The special problem of time updates" |
|
|
1423 | .PP |
|
|
1424 | Establishing the current time is a costly operation (it usually takes at |
|
|
1425 | least two system calls): \s-1EV\s0 therefore updates its idea of the current |
|
|
1426 | time only before and after \f(CW\*(C`ev_loop\*(C'\fR collects new events, which causes a |
|
|
1427 | growing difference between \f(CW\*(C`ev_now ()\*(C'\fR and \f(CW\*(C`ev_time ()\*(C'\fR when handling |
|
|
1428 | lots of events in one iteration. |
1292 | .PP |
1429 | .PP |
1293 | The relative timeouts are calculated relative to the \f(CW\*(C`ev_now ()\*(C'\fR |
1430 | The relative timeouts are calculated relative to the \f(CW\*(C`ev_now ()\*(C'\fR |
1294 | time. This is usually the right thing as this timestamp refers to the time |
1431 | time. This is usually the right thing as this timestamp refers to the time |
1295 | of the event triggering whatever timeout you are modifying/starting. If |
1432 | of the event triggering whatever timeout you are modifying/starting. If |
1296 | you suspect event processing to be delayed and you \fIneed\fR to base the timeout |
1433 | you suspect event processing to be delayed and you \fIneed\fR to base the |
1297 | on the current time, use something like this to adjust for this: |
1434 | timeout on the current time, use something like this to adjust for this: |
1298 | .PP |
1435 | .PP |
1299 | .Vb 1 |
1436 | .Vb 1 |
1300 | \& ev_timer_set (&timer, after + ev_now () \- ev_time (), 0.); |
1437 | \& ev_timer_set (&timer, after + ev_now () \- ev_time (), 0.); |
1301 | .Ve |
1438 | .Ve |
1302 | .PP |
1439 | .PP |
1303 | The callback is guarenteed to be invoked only when its timeout has passed, |
1440 | If the event loop is suspended for a long time, you can also force an |
1304 | but if multiple timers become ready during the same loop iteration then |
1441 | update of the time returned by \f(CW\*(C`ev_now ()\*(C'\fR by calling \f(CW\*(C`ev_now_update |
1305 | order of execution is undefined. |
1442 | ()\*(C'\fR. |
1306 | .PP |
1443 | .PP |
1307 | \fIWatcher-Specific Functions and Data Members\fR |
1444 | \fIWatcher-Specific Functions and Data Members\fR |
1308 | .IX Subsection "Watcher-Specific Functions and Data Members" |
1445 | .IX Subsection "Watcher-Specific Functions and Data Members" |
1309 | .IP "ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)" 4 |
1446 | .IP "ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)" 4 |
1310 | .IX Item "ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)" |
1447 | .IX Item "ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)" |
1311 | .PD 0 |
1448 | .PD 0 |
1312 | .IP "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" 4 |
1449 | .IP "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" 4 |
1313 | .IX Item "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" |
1450 | .IX Item "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" |
1314 | .PD |
1451 | .PD |
1315 | Configure the timer to trigger after \f(CW\*(C`after\*(C'\fR seconds. If \f(CW\*(C`repeat\*(C'\fR is |
1452 | Configure the timer to trigger after \f(CW\*(C`after\*(C'\fR seconds. If \f(CW\*(C`repeat\*(C'\fR |
1316 | \&\f(CW0.\fR, then it will automatically be stopped. If it is positive, then the |
1453 | is \f(CW0.\fR, then it will automatically be stopped once the timeout is |
1317 | timer will automatically be configured to trigger again \f(CW\*(C`repeat\*(C'\fR seconds |
1454 | reached. If it is positive, then the timer will automatically be |
1318 | later, again, and again, until stopped manually. |
1455 | configured to trigger again \f(CW\*(C`repeat\*(C'\fR seconds later, again, and again, |
|
|
1456 | until stopped manually. |
1319 | .Sp |
1457 | .Sp |
1320 | The timer itself will do a best-effort at avoiding drift, that is, if you |
1458 | The timer itself will do a best-effort at avoiding drift, that is, if |
1321 | configure a timer to trigger every 10 seconds, then it will trigger at |
1459 | you configure a timer to trigger every 10 seconds, then it will normally |
1322 | exactly 10 second intervals. If, however, your program cannot keep up with |
1460 | trigger at exactly 10 second intervals. If, however, your program cannot |
1323 | the timer (because it takes longer than those 10 seconds to do stuff) the |
1461 | keep up with the timer (because it takes longer than those 10 seconds to |
1324 | timer will not fire more than once per event loop iteration. |
1462 | do stuff) the timer will not fire more than once per event loop iteration. |
1325 | .IP "ev_timer_again (loop, ev_timer *)" 4 |
1463 | .IP "ev_timer_again (loop, ev_timer *)" 4 |
1326 | .IX Item "ev_timer_again (loop, ev_timer *)" |
1464 | .IX Item "ev_timer_again (loop, ev_timer *)" |
1327 | This will act as if the timer timed out and restart it again if it is |
1465 | This will act as if the timer timed out and restart it again if it is |
1328 | repeating. The exact semantics are: |
1466 | repeating. The exact semantics are: |
1329 | .Sp |
1467 | .Sp |
1330 | If the timer is pending, its pending status is cleared. |
1468 | If the timer is pending, its pending status is cleared. |
1331 | .Sp |
1469 | .Sp |
1332 | If the timer is started but nonrepeating, stop it (as if it timed out). |
1470 | If the timer is started but non-repeating, stop it (as if it timed out). |
1333 | .Sp |
1471 | .Sp |
1334 | If the timer is repeating, either start it if necessary (with the |
1472 | If the timer is repeating, either start it if necessary (with the |
1335 | \&\f(CW\*(C`repeat\*(C'\fR value), or reset the running timer to the \f(CW\*(C`repeat\*(C'\fR value. |
1473 | \&\f(CW\*(C`repeat\*(C'\fR value), or reset the running timer to the \f(CW\*(C`repeat\*(C'\fR value. |
1336 | .Sp |
1474 | .Sp |
1337 | This sounds a bit complicated, but here is a useful and typical |
1475 | This sounds a bit complicated, but here is a useful and typical |
1338 | example: Imagine you have a tcp connection and you want a so-called idle |
1476 | example: Imagine you have a \s-1TCP\s0 connection and you want a so-called idle |
1339 | timeout, that is, you want to be called when there have been, say, 60 |
1477 | timeout, that is, you want to be called when there have been, say, 60 |
1340 | seconds of inactivity on the socket. The easiest way to do this is to |
1478 | seconds of inactivity on the socket. The easiest way to do this is to |
1341 | configure an \f(CW\*(C`ev_timer\*(C'\fR with a \f(CW\*(C`repeat\*(C'\fR value of \f(CW60\fR and then call |
1479 | configure an \f(CW\*(C`ev_timer\*(C'\fR with a \f(CW\*(C`repeat\*(C'\fR value of \f(CW60\fR and then call |
1342 | \&\f(CW\*(C`ev_timer_again\*(C'\fR each time you successfully read or write some data. If |
1480 | \&\f(CW\*(C`ev_timer_again\*(C'\fR each time you successfully read or write some data. If |
1343 | you go into an idle state where you do not expect data to travel on the |
1481 | you go into an idle state where you do not expect data to travel on the |
… | |
… | |
1358 | \& ev_timer_again (loop, timer); |
1496 | \& ev_timer_again (loop, timer); |
1359 | .Ve |
1497 | .Ve |
1360 | .Sp |
1498 | .Sp |
1361 | This is more slightly efficient then stopping/starting the timer each time |
1499 | This is more slightly efficient then stopping/starting the timer each time |
1362 | you want to modify its timeout value. |
1500 | you want to modify its timeout value. |
|
|
1501 | .Sp |
|
|
1502 | Note, however, that it is often even more efficient to remember the |
|
|
1503 | time of the last activity and let the timer time-out naturally. In the |
|
|
1504 | callback, you then check whether the time-out is real, or, if there was |
|
|
1505 | some activity, you reschedule the watcher to time-out in \*(L"last_activity + |
|
|
1506 | timeout \- ev_now ()\*(R" seconds. |
1363 | .IP "ev_tstamp repeat [read\-write]" 4 |
1507 | .IP "ev_tstamp repeat [read\-write]" 4 |
1364 | .IX Item "ev_tstamp repeat [read-write]" |
1508 | .IX Item "ev_tstamp repeat [read-write]" |
1365 | The current \f(CW\*(C`repeat\*(C'\fR value. Will be used each time the watcher times out |
1509 | The current \f(CW\*(C`repeat\*(C'\fR value. Will be used each time the watcher times out |
1366 | or \f(CW\*(C`ev_timer_again\*(C'\fR is called and determines the next timeout (if any), |
1510 | or \f(CW\*(C`ev_timer_again\*(C'\fR is called, and determines the next timeout (if any), |
1367 | which is also when any modifications are taken into account. |
1511 | which is also when any modifications are taken into account. |
1368 | .PP |
1512 | .PP |
1369 | \fIExamples\fR |
1513 | \fIExamples\fR |
1370 | .IX Subsection "Examples" |
1514 | .IX Subsection "Examples" |
1371 | .PP |
1515 | .PP |
1372 | Example: Create a timer that fires after 60 seconds. |
1516 | Example: Create a timer that fires after 60 seconds. |
1373 | .PP |
1517 | .PP |
1374 | .Vb 5 |
1518 | .Vb 5 |
1375 | \& static void |
1519 | \& static void |
1376 | \& one_minute_cb (struct ev_loop *loop, struct ev_timer *w, int revents) |
1520 | \& one_minute_cb (struct ev_loop *loop, struct ev_timer *w, int revents) |
1377 | \& { |
1521 | \& { |
1378 | \& .. one minute over, w is actually stopped right here |
1522 | \& .. one minute over, w is actually stopped right here |
1379 | \& } |
1523 | \& } |
1380 | \& |
1524 | \& |
1381 | \& struct ev_timer mytimer; |
1525 | \& struct ev_timer mytimer; |
1382 | \& ev_timer_init (&mytimer, one_minute_cb, 60., 0.); |
1526 | \& ev_timer_init (&mytimer, one_minute_cb, 60., 0.); |
1383 | \& ev_timer_start (loop, &mytimer); |
1527 | \& ev_timer_start (loop, &mytimer); |
1384 | .Ve |
1528 | .Ve |
1385 | .PP |
1529 | .PP |
1386 | Example: Create a timeout timer that times out after 10 seconds of |
1530 | Example: Create a timeout timer that times out after 10 seconds of |
1387 | inactivity. |
1531 | inactivity. |
1388 | .PP |
1532 | .PP |
1389 | .Vb 5 |
1533 | .Vb 5 |
1390 | \& static void |
1534 | \& static void |
1391 | \& timeout_cb (struct ev_loop *loop, struct ev_timer *w, int revents) |
1535 | \& timeout_cb (struct ev_loop *loop, struct ev_timer *w, int revents) |
1392 | \& { |
1536 | \& { |
1393 | \& .. ten seconds without any activity |
1537 | \& .. ten seconds without any activity |
1394 | \& } |
1538 | \& } |
1395 | \& |
1539 | \& |
1396 | \& struct ev_timer mytimer; |
1540 | \& struct ev_timer mytimer; |
1397 | \& ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */ |
1541 | \& ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */ |
1398 | \& ev_timer_again (&mytimer); /* start timer */ |
1542 | \& ev_timer_again (&mytimer); /* start timer */ |
1399 | \& ev_loop (loop, 0); |
1543 | \& ev_loop (loop, 0); |
1400 | \& |
1544 | \& |
1401 | \& // and in some piece of code that gets executed on any "activity": |
1545 | \& // and in some piece of code that gets executed on any "activity": |
1402 | \& // reset the timeout to start ticking again at 10 seconds |
1546 | \& // reset the timeout to start ticking again at 10 seconds |
1403 | \& ev_timer_again (&mytimer); |
1547 | \& ev_timer_again (&mytimer); |
1404 | .Ve |
1548 | .Ve |
1405 | .ie n .Sh """ev_periodic"" \- to cron or not to cron?" |
1549 | .ie n .Sh """ev_periodic"" \- to cron or not to cron?" |
1406 | .el .Sh "\f(CWev_periodic\fP \- to cron or not to cron?" |
1550 | .el .Sh "\f(CWev_periodic\fP \- to cron or not to cron?" |
1407 | .IX Subsection "ev_periodic - to cron or not to cron?" |
1551 | .IX Subsection "ev_periodic - to cron or not to cron?" |
1408 | Periodic watchers are also timers of a kind, but they are very versatile |
1552 | Periodic watchers are also timers of a kind, but they are very versatile |
1409 | (and unfortunately a bit complex). |
1553 | (and unfortunately a bit complex). |
1410 | .PP |
1554 | .PP |
1411 | Unlike \f(CW\*(C`ev_timer\*(C'\fR's, they are not based on real time (or relative time) |
1555 | Unlike \f(CW\*(C`ev_timer\*(C'\fR's, they are not based on real time (or relative time) |
1412 | but on wallclock time (absolute time). You can tell a periodic watcher |
1556 | but on wall clock time (absolute time). You can tell a periodic watcher |
1413 | to trigger \*(L"at\*(R" some specific point in time. For example, if you tell a |
1557 | to trigger after some specific point in time. For example, if you tell a |
1414 | periodic watcher to trigger in 10 seconds (by specifiying e.g. \f(CW\*(C`ev_now () |
1558 | periodic watcher to trigger in 10 seconds (by specifying e.g. \f(CW\*(C`ev_now () |
1415 | + 10.\*(C'\fR) and then reset your system clock to the last year, then it will |
1559 | + 10.\*(C'\fR, that is, an absolute time not a delay) and then reset your system |
|
|
1560 | clock to January of the previous year, then it will take more than year |
1416 | take a year to trigger the event (unlike an \f(CW\*(C`ev_timer\*(C'\fR, which would trigger |
1561 | to trigger the event (unlike an \f(CW\*(C`ev_timer\*(C'\fR, which would still trigger |
1417 | roughly 10 seconds later). |
1562 | roughly 10 seconds later as it uses a relative timeout). |
1418 | .PP |
1563 | .PP |
1419 | They can also be used to implement vastly more complex timers, such as |
1564 | \&\f(CW\*(C`ev_periodic\*(C'\fRs can also be used to implement vastly more complex timers, |
1420 | triggering an event on each midnight, local time or other, complicated, |
1565 | such as triggering an event on each \*(L"midnight, local time\*(R", or other |
1421 | rules. |
1566 | complicated rules. |
1422 | .PP |
1567 | .PP |
1423 | As with timers, the callback is guarenteed to be invoked only when the |
1568 | As with timers, the callback is guaranteed to be invoked only when the |
1424 | time (\f(CW\*(C`at\*(C'\fR) has been passed, but if multiple periodic timers become ready |
1569 | time (\f(CW\*(C`at\*(C'\fR) has passed, but if multiple periodic timers become ready |
1425 | during the same loop iteration then order of execution is undefined. |
1570 | during the same loop iteration, then order of execution is undefined. |
1426 | .PP |
1571 | .PP |
1427 | \fIWatcher-Specific Functions and Data Members\fR |
1572 | \fIWatcher-Specific Functions and Data Members\fR |
1428 | .IX Subsection "Watcher-Specific Functions and Data Members" |
1573 | .IX Subsection "Watcher-Specific Functions and Data Members" |
1429 | .IP "ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)" 4 |
1574 | .IP "ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)" 4 |
1430 | .IX Item "ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)" |
1575 | .IX Item "ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)" |
1431 | .PD 0 |
1576 | .PD 0 |
1432 | .IP "ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)" 4 |
1577 | .IP "ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)" 4 |
1433 | .IX Item "ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)" |
1578 | .IX Item "ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)" |
1434 | .PD |
1579 | .PD |
1435 | Lots of arguments, lets sort it out... There are basically three modes of |
1580 | Lots of arguments, lets sort it out... There are basically three modes of |
1436 | operation, and we will explain them from simplest to complex: |
1581 | operation, and we will explain them from simplest to most complex: |
1437 | .RS 4 |
1582 | .RS 4 |
1438 | .IP "\(bu" 4 |
1583 | .IP "\(bu" 4 |
1439 | absolute timer (at = time, interval = reschedule_cb = 0) |
1584 | absolute timer (at = time, interval = reschedule_cb = 0) |
1440 | .Sp |
1585 | .Sp |
1441 | In this configuration the watcher triggers an event at the wallclock time |
1586 | In this configuration the watcher triggers an event after the wall clock |
1442 | \&\f(CW\*(C`at\*(C'\fR and doesn't repeat. It will not adjust when a time jump occurs, |
1587 | time \f(CW\*(C`at\*(C'\fR has passed. It will not repeat and will not adjust when a time |
1443 | that is, if it is to be run at January 1st 2011 then it will run when the |
1588 | jump occurs, that is, if it is to be run at January 1st 2011 then it will |
1444 | system time reaches or surpasses this time. |
1589 | only run when the system clock reaches or surpasses this time. |
1445 | .IP "\(bu" 4 |
1590 | .IP "\(bu" 4 |
1446 | repeating interval timer (at = offset, interval > 0, reschedule_cb = 0) |
1591 | repeating interval timer (at = offset, interval > 0, reschedule_cb = 0) |
1447 | .Sp |
1592 | .Sp |
1448 | In this mode the watcher will always be scheduled to time out at the next |
1593 | In this mode the watcher will always be scheduled to time out at the next |
1449 | \&\f(CW\*(C`at + N * interval\*(C'\fR time (for some integer N, which can also be negative) |
1594 | \&\f(CW\*(C`at + N * interval\*(C'\fR time (for some integer N, which can also be negative) |
1450 | and then repeat, regardless of any time jumps. |
1595 | and then repeat, regardless of any time jumps. |
1451 | .Sp |
1596 | .Sp |
1452 | This can be used to create timers that do not drift with respect to system |
1597 | This can be used to create timers that do not drift with respect to the |
1453 | time: |
1598 | system clock, for example, here is a \f(CW\*(C`ev_periodic\*(C'\fR that triggers each |
|
|
1599 | hour, on the hour: |
1454 | .Sp |
1600 | .Sp |
1455 | .Vb 1 |
1601 | .Vb 1 |
1456 | \& ev_periodic_set (&periodic, 0., 3600., 0); |
1602 | \& ev_periodic_set (&periodic, 0., 3600., 0); |
1457 | .Ve |
1603 | .Ve |
1458 | .Sp |
1604 | .Sp |
1459 | This doesn't mean there will always be 3600 seconds in between triggers, |
1605 | This doesn't mean there will always be 3600 seconds in between triggers, |
1460 | but only that the the callback will be called when the system time shows a |
1606 | but only that the callback will be called when the system time shows a |
1461 | full hour (\s-1UTC\s0), or more correctly, when the system time is evenly divisible |
1607 | full hour (\s-1UTC\s0), or more correctly, when the system time is evenly divisible |
1462 | by 3600. |
1608 | by 3600. |
1463 | .Sp |
1609 | .Sp |
1464 | Another way to think about it (for the mathematically inclined) is that |
1610 | Another way to think about it (for the mathematically inclined) is that |
1465 | \&\f(CW\*(C`ev_periodic\*(C'\fR will try to run the callback in this mode at the next possible |
1611 | \&\f(CW\*(C`ev_periodic\*(C'\fR will try to run the callback in this mode at the next possible |
1466 | time where \f(CW\*(C`time = at (mod interval)\*(C'\fR, regardless of any time jumps. |
1612 | time where \f(CW\*(C`time = at (mod interval)\*(C'\fR, regardless of any time jumps. |
1467 | .Sp |
1613 | .Sp |
1468 | For numerical stability it is preferable that the \f(CW\*(C`at\*(C'\fR value is near |
1614 | For numerical stability it is preferable that the \f(CW\*(C`at\*(C'\fR value is near |
1469 | \&\f(CW\*(C`ev_now ()\*(C'\fR (the current time), but there is no range requirement for |
1615 | \&\f(CW\*(C`ev_now ()\*(C'\fR (the current time), but there is no range requirement for |
1470 | this value. |
1616 | this value, and in fact is often specified as zero. |
|
|
1617 | .Sp |
|
|
1618 | Note also that there is an upper limit to how often a timer can fire (\s-1CPU\s0 |
|
|
1619 | speed for example), so if \f(CW\*(C`interval\*(C'\fR is very small then timing stability |
|
|
1620 | will of course deteriorate. Libev itself tries to be exact to be about one |
|
|
1621 | millisecond (if the \s-1OS\s0 supports it and the machine is fast enough). |
1471 | .IP "\(bu" 4 |
1622 | .IP "\(bu" 4 |
1472 | manual reschedule mode (at and interval ignored, reschedule_cb = callback) |
1623 | manual reschedule mode (at and interval ignored, reschedule_cb = callback) |
1473 | .Sp |
1624 | .Sp |
1474 | In this mode the values for \f(CW\*(C`interval\*(C'\fR and \f(CW\*(C`at\*(C'\fR are both being |
1625 | In this mode the values for \f(CW\*(C`interval\*(C'\fR and \f(CW\*(C`at\*(C'\fR are both being |
1475 | ignored. Instead, each time the periodic watcher gets scheduled, the |
1626 | ignored. Instead, each time the periodic watcher gets scheduled, the |
1476 | reschedule callback will be called with the watcher as first, and the |
1627 | reschedule callback will be called with the watcher as first, and the |
1477 | current time as second argument. |
1628 | current time as second argument. |
1478 | .Sp |
1629 | .Sp |
1479 | \&\s-1NOTE:\s0 \fIThis callback \s-1MUST\s0 \s-1NOT\s0 stop or destroy any periodic watcher, |
1630 | \&\s-1NOTE:\s0 \fIThis callback \s-1MUST\s0 \s-1NOT\s0 stop or destroy any periodic watcher, |
1480 | ever, or make any event loop modifications\fR. If you need to stop it, |
1631 | ever, or make \s-1ANY\s0 event loop modifications whatsoever\fR. |
1481 | return \f(CW\*(C`now + 1e30\*(C'\fR (or so, fudge fudge) and stop it afterwards (e.g. by |
1632 | .Sp |
|
|
1633 | If you need to stop it, return \f(CW\*(C`now + 1e30\*(C'\fR (or so, fudge fudge) and stop |
1482 | starting an \f(CW\*(C`ev_prepare\*(C'\fR watcher, which is legal). |
1634 | it afterwards (e.g. by starting an \f(CW\*(C`ev_prepare\*(C'\fR watcher, which is the |
|
|
1635 | only event loop modification you are allowed to do). |
1483 | .Sp |
1636 | .Sp |
1484 | Its prototype is \f(CW\*(C`ev_tstamp (*reschedule_cb)(struct ev_periodic *w, |
1637 | The callback prototype is \f(CW\*(C`ev_tstamp (*reschedule_cb)(struct ev_periodic |
1485 | ev_tstamp now)\*(C'\fR, e.g.: |
1638 | *w, ev_tstamp now)\*(C'\fR, e.g.: |
1486 | .Sp |
1639 | .Sp |
1487 | .Vb 4 |
1640 | .Vb 4 |
1488 | \& static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) |
1641 | \& static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) |
1489 | \& { |
1642 | \& { |
1490 | \& return now + 60.; |
1643 | \& return now + 60.; |
… | |
… | |
1494 | It must return the next time to trigger, based on the passed time value |
1647 | It must return the next time to trigger, based on the passed time value |
1495 | (that is, the lowest time value larger than to the second argument). It |
1648 | (that is, the lowest time value larger than to the second argument). It |
1496 | will usually be called just before the callback will be triggered, but |
1649 | will usually be called just before the callback will be triggered, but |
1497 | might be called at other times, too. |
1650 | might be called at other times, too. |
1498 | .Sp |
1651 | .Sp |
1499 | \&\s-1NOTE:\s0 \fIThis callback must always return a time that is later than the |
1652 | \&\s-1NOTE:\s0 \fIThis callback must always return a time that is higher than or |
1500 | passed \f(CI\*(C`now\*(C'\fI value\fR. Not even \f(CW\*(C`now\*(C'\fR itself will do, it \fImust\fR be larger. |
1653 | equal to the passed \f(CI\*(C`now\*(C'\fI value\fR. |
1501 | .Sp |
1654 | .Sp |
1502 | This can be used to create very complex timers, such as a timer that |
1655 | This can be used to create very complex timers, such as a timer that |
1503 | triggers on each midnight, local time. To do this, you would calculate the |
1656 | triggers on \*(L"next midnight, local time\*(R". To do this, you would calculate the |
1504 | next midnight after \f(CW\*(C`now\*(C'\fR and return the timestamp value for this. How |
1657 | next midnight after \f(CW\*(C`now\*(C'\fR and return the timestamp value for this. How |
1505 | you do this is, again, up to you (but it is not trivial, which is the main |
1658 | you do this is, again, up to you (but it is not trivial, which is the main |
1506 | reason I omitted it as an example). |
1659 | reason I omitted it as an example). |
1507 | .RE |
1660 | .RE |
1508 | .RS 4 |
1661 | .RS 4 |
… | |
… | |
1537 | .PP |
1690 | .PP |
1538 | \fIExamples\fR |
1691 | \fIExamples\fR |
1539 | .IX Subsection "Examples" |
1692 | .IX Subsection "Examples" |
1540 | .PP |
1693 | .PP |
1541 | Example: Call a callback every hour, or, more precisely, whenever the |
1694 | Example: Call a callback every hour, or, more precisely, whenever the |
1542 | system clock is divisible by 3600. The callback invocation times have |
1695 | system time is divisible by 3600. The callback invocation times have |
1543 | potentially a lot of jittering, but good long-term stability. |
1696 | potentially a lot of jitter, but good long-term stability. |
1544 | .PP |
1697 | .PP |
1545 | .Vb 5 |
1698 | .Vb 5 |
1546 | \& static void |
1699 | \& static void |
1547 | \& clock_cb (struct ev_loop *loop, struct ev_io *w, int revents) |
1700 | \& clock_cb (struct ev_loop *loop, struct ev_io *w, int revents) |
1548 | \& { |
1701 | \& { |
1549 | \& ... its now a full hour (UTC, or TAI or whatever your clock follows) |
1702 | \& ... its now a full hour (UTC, or TAI or whatever your clock follows) |
1550 | \& } |
1703 | \& } |
1551 | \& |
1704 | \& |
1552 | \& struct ev_periodic hourly_tick; |
1705 | \& struct ev_periodic hourly_tick; |
1553 | \& ev_periodic_init (&hourly_tick, clock_cb, 0., 3600., 0); |
1706 | \& ev_periodic_init (&hourly_tick, clock_cb, 0., 3600., 0); |
1554 | \& ev_periodic_start (loop, &hourly_tick); |
1707 | \& ev_periodic_start (loop, &hourly_tick); |
1555 | .Ve |
1708 | .Ve |
1556 | .PP |
1709 | .PP |
1557 | Example: The same as above, but use a reschedule callback to do it: |
1710 | Example: The same as above, but use a reschedule callback to do it: |
1558 | .PP |
1711 | .PP |
1559 | .Vb 1 |
1712 | .Vb 1 |
1560 | \& #include <math.h> |
1713 | \& #include <math.h> |
1561 | \& |
1714 | \& |
1562 | \& static ev_tstamp |
1715 | \& static ev_tstamp |
1563 | \& my_scheduler_cb (struct ev_periodic *w, ev_tstamp now) |
1716 | \& my_scheduler_cb (struct ev_periodic *w, ev_tstamp now) |
1564 | \& { |
1717 | \& { |
1565 | \& return fmod (now, 3600.) + 3600.; |
1718 | \& return now + (3600. \- fmod (now, 3600.)); |
1566 | \& } |
1719 | \& } |
1567 | \& |
1720 | \& |
1568 | \& ev_periodic_init (&hourly_tick, clock_cb, 0., 0., my_scheduler_cb); |
1721 | \& ev_periodic_init (&hourly_tick, clock_cb, 0., 0., my_scheduler_cb); |
1569 | .Ve |
1722 | .Ve |
1570 | .PP |
1723 | .PP |
1571 | Example: Call a callback every hour, starting now: |
1724 | Example: Call a callback every hour, starting now: |
1572 | .PP |
1725 | .PP |
1573 | .Vb 4 |
1726 | .Vb 4 |
1574 | \& struct ev_periodic hourly_tick; |
1727 | \& struct ev_periodic hourly_tick; |
1575 | \& ev_periodic_init (&hourly_tick, clock_cb, |
1728 | \& ev_periodic_init (&hourly_tick, clock_cb, |
1576 | \& fmod (ev_now (loop), 3600.), 3600., 0); |
1729 | \& fmod (ev_now (loop), 3600.), 3600., 0); |
1577 | \& ev_periodic_start (loop, &hourly_tick); |
1730 | \& ev_periodic_start (loop, &hourly_tick); |
1578 | .Ve |
1731 | .Ve |
1579 | .ie n .Sh """ev_signal"" \- signal me when a signal gets signalled!" |
1732 | .ie n .Sh """ev_signal"" \- signal me when a signal gets signalled!" |
1580 | .el .Sh "\f(CWev_signal\fP \- signal me when a signal gets signalled!" |
1733 | .el .Sh "\f(CWev_signal\fP \- signal me when a signal gets signalled!" |
1581 | .IX Subsection "ev_signal - signal me when a signal gets signalled!" |
1734 | .IX Subsection "ev_signal - signal me when a signal gets signalled!" |
1582 | Signal watchers will trigger an event when the process receives a specific |
1735 | Signal watchers will trigger an event when the process receives a specific |
1583 | signal one or more times. Even though signals are very asynchronous, libev |
1736 | signal one or more times. Even though signals are very asynchronous, libev |
1584 | will try it's best to deliver signals synchronously, i.e. as part of the |
1737 | will try it's best to deliver signals synchronously, i.e. as part of the |
1585 | normal event processing, like any other event. |
1738 | normal event processing, like any other event. |
1586 | .PP |
1739 | .PP |
|
|
1740 | If you want signals asynchronously, just use \f(CW\*(C`sigaction\*(C'\fR as you would |
|
|
1741 | do without libev and forget about sharing the signal. You can even use |
|
|
1742 | \&\f(CW\*(C`ev_async\*(C'\fR from a signal handler to synchronously wake up an event loop. |
|
|
1743 | .PP |
1587 | You can configure as many watchers as you like per signal. Only when the |
1744 | You can configure as many watchers as you like per signal. Only when the |
1588 | first watcher gets started will libev actually register a signal watcher |
1745 | first watcher gets started will libev actually register a signal handler |
1589 | with the kernel (thus it coexists with your own signal handlers as long |
1746 | with the kernel (thus it coexists with your own signal handlers as long as |
1590 | as you don't register any with libev). Similarly, when the last signal |
1747 | you don't register any with libev for the same signal). Similarly, when |
1591 | watcher for a signal is stopped libev will reset the signal handler to |
1748 | the last signal watcher for a signal is stopped, libev will reset the |
1592 | \&\s-1SIG_DFL\s0 (regardless of what it was set to before). |
1749 | signal handler to \s-1SIG_DFL\s0 (regardless of what it was set to before). |
1593 | .PP |
1750 | .PP |
1594 | If possible and supported, libev will install its handlers with |
1751 | If possible and supported, libev will install its handlers with |
1595 | \&\f(CW\*(C`SA_RESTART\*(C'\fR behaviour enabled, so syscalls should not be unduly |
1752 | \&\f(CW\*(C`SA_RESTART\*(C'\fR behaviour enabled, so system calls should not be unduly |
1596 | interrupted. If you have a problem with syscalls getting interrupted by |
1753 | interrupted. If you have a problem with system calls getting interrupted by |
1597 | signals you can block all signals in an \f(CW\*(C`ev_check\*(C'\fR watcher and unblock |
1754 | signals you can block all signals in an \f(CW\*(C`ev_check\*(C'\fR watcher and unblock |
1598 | them in an \f(CW\*(C`ev_prepare\*(C'\fR watcher. |
1755 | them in an \f(CW\*(C`ev_prepare\*(C'\fR watcher. |
1599 | .PP |
1756 | .PP |
1600 | \fIWatcher-Specific Functions and Data Members\fR |
1757 | \fIWatcher-Specific Functions and Data Members\fR |
1601 | .IX Subsection "Watcher-Specific Functions and Data Members" |
1758 | .IX Subsection "Watcher-Specific Functions and Data Members" |
… | |
… | |
1612 | The signal the watcher watches out for. |
1769 | The signal the watcher watches out for. |
1613 | .PP |
1770 | .PP |
1614 | \fIExamples\fR |
1771 | \fIExamples\fR |
1615 | .IX Subsection "Examples" |
1772 | .IX Subsection "Examples" |
1616 | .PP |
1773 | .PP |
1617 | Example: Try to exit cleanly on \s-1SIGINT\s0 and \s-1SIGTERM\s0. |
1774 | Example: Try to exit cleanly on \s-1SIGINT\s0. |
1618 | .PP |
1775 | .PP |
1619 | .Vb 5 |
1776 | .Vb 5 |
1620 | \& static void |
1777 | \& static void |
1621 | \& sigint_cb (struct ev_loop *loop, struct ev_signal *w, int revents) |
1778 | \& sigint_cb (struct ev_loop *loop, struct ev_signal *w, int revents) |
1622 | \& { |
1779 | \& { |
1623 | \& ev_unloop (loop, EVUNLOOP_ALL); |
1780 | \& ev_unloop (loop, EVUNLOOP_ALL); |
1624 | \& } |
1781 | \& } |
1625 | \& |
1782 | \& |
1626 | \& struct ev_signal signal_watcher; |
1783 | \& struct ev_signal signal_watcher; |
1627 | \& ev_signal_init (&signal_watcher, sigint_cb, SIGINT); |
1784 | \& ev_signal_init (&signal_watcher, sigint_cb, SIGINT); |
1628 | \& ev_signal_start (loop, &sigint_cb); |
1785 | \& ev_signal_start (loop, &signal_watcher); |
1629 | .Ve |
1786 | .Ve |
1630 | .ie n .Sh """ev_child"" \- watch out for process status changes" |
1787 | .ie n .Sh """ev_child"" \- watch out for process status changes" |
1631 | .el .Sh "\f(CWev_child\fP \- watch out for process status changes" |
1788 | .el .Sh "\f(CWev_child\fP \- watch out for process status changes" |
1632 | .IX Subsection "ev_child - watch out for process status changes" |
1789 | .IX Subsection "ev_child - watch out for process status changes" |
1633 | Child watchers trigger when your process receives a \s-1SIGCHLD\s0 in response to |
1790 | Child watchers trigger when your process receives a \s-1SIGCHLD\s0 in response to |
1634 | some child status changes (most typically when a child of yours dies). It |
1791 | some child status changes (most typically when a child of yours dies or |
1635 | is permissible to install a child watcher \fIafter\fR the child has been |
1792 | exits). It is permissible to install a child watcher \fIafter\fR the child |
1636 | forked (which implies it might have already exited), as long as the event |
1793 | has been forked (which implies it might have already exited), as long |
1637 | loop isn't entered (or is continued from a watcher). |
1794 | as the event loop isn't entered (or is continued from a watcher), i.e., |
|
|
1795 | forking and then immediately registering a watcher for the child is fine, |
|
|
1796 | but forking and registering a watcher a few event loop iterations later is |
|
|
1797 | not. |
1638 | .PP |
1798 | .PP |
1639 | Only the default event loop is capable of handling signals, and therefore |
1799 | Only the default event loop is capable of handling signals, and therefore |
1640 | you can only rgeister child watchers in the default event loop. |
1800 | you can only register child watchers in the default event loop. |
1641 | .PP |
1801 | .PP |
1642 | \fIProcess Interaction\fR |
1802 | \fIProcess Interaction\fR |
1643 | .IX Subsection "Process Interaction" |
1803 | .IX Subsection "Process Interaction" |
1644 | .PP |
1804 | .PP |
1645 | Libev grabs \f(CW\*(C`SIGCHLD\*(C'\fR as soon as the default event loop is |
1805 | Libev grabs \f(CW\*(C`SIGCHLD\*(C'\fR as soon as the default event loop is |
1646 | initialised. This is necessary to guarantee proper behaviour even if |
1806 | initialised. This is necessary to guarantee proper behaviour even if |
1647 | the first child watcher is started after the child exits. The occurance |
1807 | the first child watcher is started after the child exits. The occurrence |
1648 | of \f(CW\*(C`SIGCHLD\*(C'\fR is recorded asynchronously, but child reaping is done |
1808 | of \f(CW\*(C`SIGCHLD\*(C'\fR is recorded asynchronously, but child reaping is done |
1649 | synchronously as part of the event loop processing. Libev always reaps all |
1809 | synchronously as part of the event loop processing. Libev always reaps all |
1650 | children, even ones not watched. |
1810 | children, even ones not watched. |
1651 | .PP |
1811 | .PP |
1652 | \fIOverriding the Built-In Processing\fR |
1812 | \fIOverriding the Built-In Processing\fR |
… | |
… | |
1657 | handler, you can override it easily by installing your own handler for |
1817 | handler, you can override it easily by installing your own handler for |
1658 | \&\f(CW\*(C`SIGCHLD\*(C'\fR after initialising the default loop, and making sure the |
1818 | \&\f(CW\*(C`SIGCHLD\*(C'\fR after initialising the default loop, and making sure the |
1659 | default loop never gets destroyed. You are encouraged, however, to use an |
1819 | default loop never gets destroyed. You are encouraged, however, to use an |
1660 | event-based approach to child reaping and thus use libev's support for |
1820 | event-based approach to child reaping and thus use libev's support for |
1661 | that, so other libev users can use \f(CW\*(C`ev_child\*(C'\fR watchers freely. |
1821 | that, so other libev users can use \f(CW\*(C`ev_child\*(C'\fR watchers freely. |
|
|
1822 | .PP |
|
|
1823 | \fIStopping the Child Watcher\fR |
|
|
1824 | .IX Subsection "Stopping the Child Watcher" |
|
|
1825 | .PP |
|
|
1826 | Currently, the child watcher never gets stopped, even when the |
|
|
1827 | child terminates, so normally one needs to stop the watcher in the |
|
|
1828 | callback. Future versions of libev might stop the watcher automatically |
|
|
1829 | when a child exit is detected. |
1662 | .PP |
1830 | .PP |
1663 | \fIWatcher-Specific Functions and Data Members\fR |
1831 | \fIWatcher-Specific Functions and Data Members\fR |
1664 | .IX Subsection "Watcher-Specific Functions and Data Members" |
1832 | .IX Subsection "Watcher-Specific Functions and Data Members" |
1665 | .IP "ev_child_init (ev_child *, callback, int pid, int trace)" 4 |
1833 | .IP "ev_child_init (ev_child *, callback, int pid, int trace)" 4 |
1666 | .IX Item "ev_child_init (ev_child *, callback, int pid, int trace)" |
1834 | .IX Item "ev_child_init (ev_child *, callback, int pid, int trace)" |
… | |
… | |
1692 | .PP |
1860 | .PP |
1693 | Example: \f(CW\*(C`fork()\*(C'\fR a new process and install a child handler to wait for |
1861 | Example: \f(CW\*(C`fork()\*(C'\fR a new process and install a child handler to wait for |
1694 | its completion. |
1862 | its completion. |
1695 | .PP |
1863 | .PP |
1696 | .Vb 1 |
1864 | .Vb 1 |
1697 | \& ev_child cw; |
1865 | \& ev_child cw; |
1698 | \& |
1866 | \& |
1699 | \& static void |
1867 | \& static void |
1700 | \& child_cb (EV_P_ struct ev_child *w, int revents) |
1868 | \& child_cb (EV_P_ struct ev_child *w, int revents) |
1701 | \& { |
1869 | \& { |
1702 | \& ev_child_stop (EV_A_ w); |
1870 | \& ev_child_stop (EV_A_ w); |
1703 | \& printf ("process %d exited with status %x\en", w\->rpid, w\->rstatus); |
1871 | \& printf ("process %d exited with status %x\en", w\->rpid, w\->rstatus); |
1704 | \& } |
1872 | \& } |
1705 | \& |
1873 | \& |
1706 | \& pid_t pid = fork (); |
1874 | \& pid_t pid = fork (); |
1707 | \& |
1875 | \& |
1708 | \& if (pid < 0) |
1876 | \& if (pid < 0) |
1709 | \& // error |
1877 | \& // error |
1710 | \& else if (pid == 0) |
1878 | \& else if (pid == 0) |
1711 | \& { |
1879 | \& { |
1712 | \& // the forked child executes here |
1880 | \& // the forked child executes here |
1713 | \& exit (1); |
1881 | \& exit (1); |
1714 | \& } |
1882 | \& } |
1715 | \& else |
1883 | \& else |
1716 | \& { |
1884 | \& { |
1717 | \& ev_child_init (&cw, child_cb, pid, 0); |
1885 | \& ev_child_init (&cw, child_cb, pid, 0); |
1718 | \& ev_child_start (EV_DEFAULT_ &cw); |
1886 | \& ev_child_start (EV_DEFAULT_ &cw); |
1719 | \& } |
1887 | \& } |
1720 | .Ve |
1888 | .Ve |
1721 | .ie n .Sh """ev_stat"" \- did the file attributes just change?" |
1889 | .ie n .Sh """ev_stat"" \- did the file attributes just change?" |
1722 | .el .Sh "\f(CWev_stat\fP \- did the file attributes just change?" |
1890 | .el .Sh "\f(CWev_stat\fP \- did the file attributes just change?" |
1723 | .IX Subsection "ev_stat - did the file attributes just change?" |
1891 | .IX Subsection "ev_stat - did the file attributes just change?" |
1724 | This watches a filesystem path for attribute changes. That is, it calls |
1892 | This watches a file system path for attribute changes. That is, it calls |
1725 | \&\f(CW\*(C`stat\*(C'\fR regularly (or when the \s-1OS\s0 says it changed) and sees if it changed |
1893 | \&\f(CW\*(C`stat\*(C'\fR regularly (or when the \s-1OS\s0 says it changed) and sees if it changed |
1726 | compared to the last time, invoking the callback if it did. |
1894 | compared to the last time, invoking the callback if it did. |
1727 | .PP |
1895 | .PP |
1728 | The path does not need to exist: changing from \*(L"path exists\*(R" to \*(L"path does |
1896 | The path does not need to exist: changing from \*(L"path exists\*(R" to \*(L"path does |
1729 | not exist\*(R" is a status change like any other. The condition \*(L"path does |
1897 | not exist\*(R" is a status change like any other. The condition \*(L"path does |
… | |
… | |
1732 | the stat buffer having unspecified contents. |
1900 | the stat buffer having unspecified contents. |
1733 | .PP |
1901 | .PP |
1734 | The path \fIshould\fR be absolute and \fImust not\fR end in a slash. If it is |
1902 | The path \fIshould\fR be absolute and \fImust not\fR end in a slash. If it is |
1735 | relative and your working directory changes, the behaviour is undefined. |
1903 | relative and your working directory changes, the behaviour is undefined. |
1736 | .PP |
1904 | .PP |
1737 | Since there is no standard to do this, the portable implementation simply |
1905 | Since there is no standard kernel interface to do this, the portable |
1738 | calls \f(CW\*(C`stat (2)\*(C'\fR regularly on the path to see if it changed somehow. You |
1906 | implementation simply calls \f(CW\*(C`stat (2)\*(C'\fR regularly on the path to see if |
1739 | can specify a recommended polling interval for this case. If you specify |
1907 | it changed somehow. You can specify a recommended polling interval for |
1740 | a polling interval of \f(CW0\fR (highly recommended!) then a \fIsuitable, |
1908 | this case. If you specify a polling interval of \f(CW0\fR (highly recommended!) |
1741 | unspecified default\fR value will be used (which you can expect to be around |
1909 | then a \fIsuitable, unspecified default\fR value will be used (which |
1742 | five seconds, although this might change dynamically). Libev will also |
1910 | you can expect to be around five seconds, although this might change |
1743 | impose a minimum interval which is currently around \f(CW0.1\fR, but thats |
1911 | dynamically). Libev will also impose a minimum interval which is currently |
1744 | usually overkill. |
1912 | around \f(CW0.1\fR, but thats usually overkill. |
1745 | .PP |
1913 | .PP |
1746 | This watcher type is not meant for massive numbers of stat watchers, |
1914 | This watcher type is not meant for massive numbers of stat watchers, |
1747 | as even with OS-supported change notifications, this can be |
1915 | as even with OS-supported change notifications, this can be |
1748 | resource-intensive. |
1916 | resource-intensive. |
1749 | .PP |
1917 | .PP |
1750 | At the time of this writing, only the Linux inotify interface is |
1918 | At the time of this writing, the only OS-specific interface implemented |
1751 | implemented (implementing kqueue support is left as an exercise for the |
1919 | is the Linux inotify interface (implementing kqueue support is left as |
1752 | reader, note, however, that the author sees no way of implementing ev_stat |
1920 | an exercise for the reader. Note, however, that the author sees no way |
1753 | semantics with kqueue). Inotify will be used to give hints only and should |
1921 | of implementing \f(CW\*(C`ev_stat\*(C'\fR semantics with kqueue). |
1754 | not change the semantics of \f(CW\*(C`ev_stat\*(C'\fR watchers, which means that libev |
|
|
1755 | sometimes needs to fall back to regular polling again even with inotify, |
|
|
1756 | but changes are usually detected immediately, and if the file exists there |
|
|
1757 | will be no polling. |
|
|
1758 | .PP |
1922 | .PP |
1759 | \fI\s-1ABI\s0 Issues (Largefile Support)\fR |
1923 | \fI\s-1ABI\s0 Issues (Largefile Support)\fR |
1760 | .IX Subsection "ABI Issues (Largefile Support)" |
1924 | .IX Subsection "ABI Issues (Largefile Support)" |
1761 | .PP |
1925 | .PP |
1762 | Libev by default (unless the user overrides this) uses the default |
1926 | Libev by default (unless the user overrides this) uses the default |
1763 | compilation environment, which means that on systems with optionally |
1927 | compilation environment, which means that on systems with large file |
1764 | disabled large file support, you get the 32 bit version of the stat |
1928 | support disabled by default, you get the 32 bit version of the stat |
1765 | structure. When using the library from programs that change the \s-1ABI\s0 to |
1929 | structure. When using the library from programs that change the \s-1ABI\s0 to |
1766 | use 64 bit file offsets the programs will fail. In that case you have to |
1930 | use 64 bit file offsets the programs will fail. In that case you have to |
1767 | compile libev with the same flags to get binary compatibility. This is |
1931 | compile libev with the same flags to get binary compatibility. This is |
1768 | obviously the case with any flags that change the \s-1ABI\s0, but the problem is |
1932 | obviously the case with any flags that change the \s-1ABI\s0, but the problem is |
1769 | most noticably with ev_stat and largefile support. |
1933 | most noticeably disabled with ev_stat and large file support. |
1770 | .PP |
1934 | .PP |
1771 | \fIInotify\fR |
1935 | The solution for this is to lobby your distribution maker to make large |
|
|
1936 | file interfaces available by default (as e.g. FreeBSD does) and not |
|
|
1937 | optional. Libev cannot simply switch on large file support because it has |
|
|
1938 | to exchange stat structures with application programs compiled using the |
|
|
1939 | default compilation environment. |
|
|
1940 | .PP |
|
|
1941 | \fIInotify and Kqueue\fR |
1772 | .IX Subsection "Inotify" |
1942 | .IX Subsection "Inotify and Kqueue" |
1773 | .PP |
1943 | .PP |
1774 | When \f(CW\*(C`inotify (7)\*(C'\fR support has been compiled into libev (generally only |
1944 | When \f(CW\*(C`inotify (7)\*(C'\fR support has been compiled into libev (generally |
|
|
1945 | only available with Linux 2.6.25 or above due to bugs in earlier |
1775 | available on Linux) and present at runtime, it will be used to speed up |
1946 | implementations) and present at runtime, it will be used to speed up |
1776 | change detection where possible. The inotify descriptor will be created lazily |
1947 | change detection where possible. The inotify descriptor will be created |
1777 | when the first \f(CW\*(C`ev_stat\*(C'\fR watcher is being started. |
1948 | lazily when the first \f(CW\*(C`ev_stat\*(C'\fR watcher is being started. |
1778 | .PP |
1949 | .PP |
1779 | Inotify presence does not change the semantics of \f(CW\*(C`ev_stat\*(C'\fR watchers |
1950 | Inotify presence does not change the semantics of \f(CW\*(C`ev_stat\*(C'\fR watchers |
1780 | except that changes might be detected earlier, and in some cases, to avoid |
1951 | except that changes might be detected earlier, and in some cases, to avoid |
1781 | making regular \f(CW\*(C`stat\*(C'\fR calls. Even in the presence of inotify support |
1952 | making regular \f(CW\*(C`stat\*(C'\fR calls. Even in the presence of inotify support |
1782 | there are many cases where libev has to resort to regular \f(CW\*(C`stat\*(C'\fR polling. |
1953 | there are many cases where libev has to resort to regular \f(CW\*(C`stat\*(C'\fR polling, |
|
|
1954 | but as long as the path exists, libev usually gets away without polling. |
1783 | .PP |
1955 | .PP |
1784 | (There is no support for kqueue, as apparently it cannot be used to |
1956 | There is no support for kqueue, as apparently it cannot be used to |
1785 | implement this functionality, due to the requirement of having a file |
1957 | implement this functionality, due to the requirement of having a file |
1786 | descriptor open on the object at all times). |
1958 | descriptor open on the object at all times, and detecting renames, unlinks |
|
|
1959 | etc. is difficult. |
1787 | .PP |
1960 | .PP |
1788 | \fIThe special problem of stat time resolution\fR |
1961 | \fIThe special problem of stat time resolution\fR |
1789 | .IX Subsection "The special problem of stat time resolution" |
1962 | .IX Subsection "The special problem of stat time resolution" |
1790 | .PP |
1963 | .PP |
1791 | The \f(CW\*(C`stat ()\*(C'\fR syscall only supports full-second resolution portably, and |
1964 | The \f(CW\*(C`stat ()\*(C'\fR system call only supports full-second resolution portably, and |
1792 | even on systems where the resolution is higher, many filesystems still |
1965 | even on systems where the resolution is higher, most file systems still |
1793 | only support whole seconds. |
1966 | only support whole seconds. |
1794 | .PP |
1967 | .PP |
1795 | That means that, if the time is the only thing that changes, you can |
1968 | That means that, if the time is the only thing that changes, you can |
1796 | easily miss updates: on the first update, \f(CW\*(C`ev_stat\*(C'\fR detects a change and |
1969 | easily miss updates: on the first update, \f(CW\*(C`ev_stat\*(C'\fR detects a change and |
1797 | calls your callback, which does something. When there is another update |
1970 | calls your callback, which does something. When there is another update |
1798 | within the same second, \f(CW\*(C`ev_stat\*(C'\fR will be unable to detect it as the stat |
1971 | within the same second, \f(CW\*(C`ev_stat\*(C'\fR will be unable to detect unless the |
1799 | data does not change. |
1972 | stat data does change in other ways (e.g. file size). |
1800 | .PP |
1973 | .PP |
1801 | The solution to this is to delay acting on a change for slightly more |
1974 | The solution to this is to delay acting on a change for slightly more |
1802 | than second (or till slightly after the next full second boundary), using |
1975 | than a second (or till slightly after the next full second boundary), using |
1803 | a roughly one-second-delay \f(CW\*(C`ev_timer\*(C'\fR (e.g. \f(CW\*(C`ev_timer_set (w, 0., 1.02); |
1976 | a roughly one-second-delay \f(CW\*(C`ev_timer\*(C'\fR (e.g. \f(CW\*(C`ev_timer_set (w, 0., 1.02); |
1804 | ev_timer_again (loop, w)\*(C'\fR). |
1977 | ev_timer_again (loop, w)\*(C'\fR). |
1805 | .PP |
1978 | .PP |
1806 | The \f(CW.02\fR offset is added to work around small timing inconsistencies |
1979 | The \f(CW.02\fR offset is added to work around small timing inconsistencies |
1807 | of some operating systems (where the second counter of the current time |
1980 | of some operating systems (where the second counter of the current time |
… | |
… | |
1824 | \&\f(CW\*(C`path\*(C'\fR. The \f(CW\*(C`interval\*(C'\fR is a hint on how quickly a change is expected to |
1997 | \&\f(CW\*(C`path\*(C'\fR. The \f(CW\*(C`interval\*(C'\fR is a hint on how quickly a change is expected to |
1825 | be detected and should normally be specified as \f(CW0\fR to let libev choose |
1998 | be detected and should normally be specified as \f(CW0\fR to let libev choose |
1826 | a suitable value. The memory pointed to by \f(CW\*(C`path\*(C'\fR must point to the same |
1999 | a suitable value. The memory pointed to by \f(CW\*(C`path\*(C'\fR must point to the same |
1827 | path for as long as the watcher is active. |
2000 | path for as long as the watcher is active. |
1828 | .Sp |
2001 | .Sp |
1829 | The callback will receive \f(CW\*(C`EV_STAT\*(C'\fR when a change was detected, relative |
2002 | The callback will receive an \f(CW\*(C`EV_STAT\*(C'\fR event when a change was detected, |
1830 | to the attributes at the time the watcher was started (or the last change |
2003 | relative to the attributes at the time the watcher was started (or the |
1831 | was detected). |
2004 | last change was detected). |
1832 | .IP "ev_stat_stat (loop, ev_stat *)" 4 |
2005 | .IP "ev_stat_stat (loop, ev_stat *)" 4 |
1833 | .IX Item "ev_stat_stat (loop, ev_stat *)" |
2006 | .IX Item "ev_stat_stat (loop, ev_stat *)" |
1834 | Updates the stat buffer immediately with new values. If you change the |
2007 | Updates the stat buffer immediately with new values. If you change the |
1835 | watched path in your callback, you could call this function to avoid |
2008 | watched path in your callback, you could call this function to avoid |
1836 | detecting this change (while introducing a race condition if you are not |
2009 | detecting this change (while introducing a race condition if you are not |
… | |
… | |
1852 | .IP "ev_tstamp interval [read\-only]" 4 |
2025 | .IP "ev_tstamp interval [read\-only]" 4 |
1853 | .IX Item "ev_tstamp interval [read-only]" |
2026 | .IX Item "ev_tstamp interval [read-only]" |
1854 | The specified interval. |
2027 | The specified interval. |
1855 | .IP "const char *path [read\-only]" 4 |
2028 | .IP "const char *path [read\-only]" 4 |
1856 | .IX Item "const char *path [read-only]" |
2029 | .IX Item "const char *path [read-only]" |
1857 | The filesystem path that is being watched. |
2030 | The file system path that is being watched. |
1858 | .PP |
2031 | .PP |
1859 | \fIExamples\fR |
2032 | \fIExamples\fR |
1860 | .IX Subsection "Examples" |
2033 | .IX Subsection "Examples" |
1861 | .PP |
2034 | .PP |
1862 | Example: Watch \f(CW\*(C`/etc/passwd\*(C'\fR for attribute changes. |
2035 | Example: Watch \f(CW\*(C`/etc/passwd\*(C'\fR for attribute changes. |
1863 | .PP |
2036 | .PP |
1864 | .Vb 10 |
2037 | .Vb 10 |
1865 | \& static void |
2038 | \& static void |
1866 | \& passwd_cb (struct ev_loop *loop, ev_stat *w, int revents) |
2039 | \& passwd_cb (struct ev_loop *loop, ev_stat *w, int revents) |
1867 | \& { |
2040 | \& { |
1868 | \& /* /etc/passwd changed in some way */ |
2041 | \& /* /etc/passwd changed in some way */ |
1869 | \& if (w\->attr.st_nlink) |
2042 | \& if (w\->attr.st_nlink) |
1870 | \& { |
2043 | \& { |
1871 | \& printf ("passwd current size %ld\en", (long)w\->attr.st_size); |
2044 | \& printf ("passwd current size %ld\en", (long)w\->attr.st_size); |
1872 | \& printf ("passwd current atime %ld\en", (long)w\->attr.st_mtime); |
2045 | \& printf ("passwd current atime %ld\en", (long)w\->attr.st_mtime); |
1873 | \& printf ("passwd current mtime %ld\en", (long)w\->attr.st_mtime); |
2046 | \& printf ("passwd current mtime %ld\en", (long)w\->attr.st_mtime); |
1874 | \& } |
2047 | \& } |
1875 | \& else |
2048 | \& else |
1876 | \& /* you shalt not abuse printf for puts */ |
2049 | \& /* you shalt not abuse printf for puts */ |
1877 | \& puts ("wow, /etc/passwd is not there, expect problems. " |
2050 | \& puts ("wow, /etc/passwd is not there, expect problems. " |
1878 | \& "if this is windows, they already arrived\en"); |
2051 | \& "if this is windows, they already arrived\en"); |
1879 | \& } |
2052 | \& } |
1880 | \& |
2053 | \& |
1881 | \& ... |
2054 | \& ... |
1882 | \& ev_stat passwd; |
2055 | \& ev_stat passwd; |
1883 | \& |
2056 | \& |
1884 | \& ev_stat_init (&passwd, passwd_cb, "/etc/passwd", 0.); |
2057 | \& ev_stat_init (&passwd, passwd_cb, "/etc/passwd", 0.); |
1885 | \& ev_stat_start (loop, &passwd); |
2058 | \& ev_stat_start (loop, &passwd); |
1886 | .Ve |
2059 | .Ve |
1887 | .PP |
2060 | .PP |
1888 | Example: Like above, but additionally use a one-second delay so we do not |
2061 | Example: Like above, but additionally use a one-second delay so we do not |
1889 | miss updates (however, frequent updates will delay processing, too, so |
2062 | miss updates (however, frequent updates will delay processing, too, so |
1890 | one might do the work both on \f(CW\*(C`ev_stat\*(C'\fR callback invocation \fIand\fR on |
2063 | one might do the work both on \f(CW\*(C`ev_stat\*(C'\fR callback invocation \fIand\fR on |
1891 | \&\f(CW\*(C`ev_timer\*(C'\fR callback invocation). |
2064 | \&\f(CW\*(C`ev_timer\*(C'\fR callback invocation). |
1892 | .PP |
2065 | .PP |
1893 | .Vb 2 |
2066 | .Vb 2 |
1894 | \& static ev_stat passwd; |
2067 | \& static ev_stat passwd; |
1895 | \& static ev_timer timer; |
2068 | \& static ev_timer timer; |
1896 | \& |
2069 | \& |
1897 | \& static void |
2070 | \& static void |
1898 | \& timer_cb (EV_P_ ev_timer *w, int revents) |
2071 | \& timer_cb (EV_P_ ev_timer *w, int revents) |
1899 | \& { |
2072 | \& { |
1900 | \& ev_timer_stop (EV_A_ w); |
2073 | \& ev_timer_stop (EV_A_ w); |
1901 | \& |
2074 | \& |
1902 | \& /* now it\*(Aqs one second after the most recent passwd change */ |
2075 | \& /* now it\*(Aqs one second after the most recent passwd change */ |
1903 | \& } |
2076 | \& } |
1904 | \& |
2077 | \& |
1905 | \& static void |
2078 | \& static void |
1906 | \& stat_cb (EV_P_ ev_stat *w, int revents) |
2079 | \& stat_cb (EV_P_ ev_stat *w, int revents) |
1907 | \& { |
2080 | \& { |
1908 | \& /* reset the one\-second timer */ |
2081 | \& /* reset the one\-second timer */ |
1909 | \& ev_timer_again (EV_A_ &timer); |
2082 | \& ev_timer_again (EV_A_ &timer); |
1910 | \& } |
2083 | \& } |
1911 | \& |
2084 | \& |
1912 | \& ... |
2085 | \& ... |
1913 | \& ev_stat_init (&passwd, stat_cb, "/etc/passwd", 0.); |
2086 | \& ev_stat_init (&passwd, stat_cb, "/etc/passwd", 0.); |
1914 | \& ev_stat_start (loop, &passwd); |
2087 | \& ev_stat_start (loop, &passwd); |
1915 | \& ev_timer_init (&timer, timer_cb, 0., 1.02); |
2088 | \& ev_timer_init (&timer, timer_cb, 0., 1.02); |
1916 | .Ve |
2089 | .Ve |
1917 | .ie n .Sh """ev_idle"" \- when you've got nothing better to do..." |
2090 | .ie n .Sh """ev_idle"" \- when you've got nothing better to do..." |
1918 | .el .Sh "\f(CWev_idle\fP \- when you've got nothing better to do..." |
2091 | .el .Sh "\f(CWev_idle\fP \- when you've got nothing better to do..." |
1919 | .IX Subsection "ev_idle - when you've got nothing better to do..." |
2092 | .IX Subsection "ev_idle - when you've got nothing better to do..." |
1920 | Idle watchers trigger events when no other events of the same or higher |
2093 | Idle watchers trigger events when no other events of the same or higher |
1921 | priority are pending (prepare, check and other idle watchers do not |
2094 | priority are pending (prepare, check and other idle watchers do not count |
1922 | count). |
2095 | as receiving \*(L"events\*(R"). |
1923 | .PP |
2096 | .PP |
1924 | That is, as long as your process is busy handling sockets or timeouts |
2097 | That is, as long as your process is busy handling sockets or timeouts |
1925 | (or even signals, imagine) of the same or higher priority it will not be |
2098 | (or even signals, imagine) of the same or higher priority it will not be |
1926 | triggered. But when your process is idle (or only lower-priority watchers |
2099 | triggered. But when your process is idle (or only lower-priority watchers |
1927 | are pending), the idle watchers are being called once per event loop |
2100 | are pending), the idle watchers are being called once per event loop |
… | |
… | |
1949 | .PP |
2122 | .PP |
1950 | Example: Dynamically allocate an \f(CW\*(C`ev_idle\*(C'\fR watcher, start it, and in the |
2123 | Example: Dynamically allocate an \f(CW\*(C`ev_idle\*(C'\fR watcher, start it, and in the |
1951 | callback, free it. Also, use no error checking, as usual. |
2124 | callback, free it. Also, use no error checking, as usual. |
1952 | .PP |
2125 | .PP |
1953 | .Vb 7 |
2126 | .Vb 7 |
1954 | \& static void |
2127 | \& static void |
1955 | \& idle_cb (struct ev_loop *loop, struct ev_idle *w, int revents) |
2128 | \& idle_cb (struct ev_loop *loop, struct ev_idle *w, int revents) |
1956 | \& { |
2129 | \& { |
1957 | \& free (w); |
2130 | \& free (w); |
1958 | \& // now do something you wanted to do when the program has |
2131 | \& // now do something you wanted to do when the program has |
1959 | \& // no longer anything immediate to do. |
2132 | \& // no longer anything immediate to do. |
1960 | \& } |
2133 | \& } |
1961 | \& |
2134 | \& |
1962 | \& struct ev_idle *idle_watcher = malloc (sizeof (struct ev_idle)); |
2135 | \& struct ev_idle *idle_watcher = malloc (sizeof (struct ev_idle)); |
1963 | \& ev_idle_init (idle_watcher, idle_cb); |
2136 | \& ev_idle_init (idle_watcher, idle_cb); |
1964 | \& ev_idle_start (loop, idle_cb); |
2137 | \& ev_idle_start (loop, idle_cb); |
1965 | .Ve |
2138 | .Ve |
1966 | .ie n .Sh """ev_prepare""\fP and \f(CW""ev_check"" \- customise your event loop!" |
2139 | .ie n .Sh """ev_prepare""\fP and \f(CW""ev_check"" \- customise your event loop!" |
1967 | .el .Sh "\f(CWev_prepare\fP and \f(CWev_check\fP \- customise your event loop!" |
2140 | .el .Sh "\f(CWev_prepare\fP and \f(CWev_check\fP \- customise your event loop!" |
1968 | .IX Subsection "ev_prepare and ev_check - customise your event loop!" |
2141 | .IX Subsection "ev_prepare and ev_check - customise your event loop!" |
1969 | Prepare and check watchers are usually (but not always) used in tandem: |
2142 | Prepare and check watchers are usually (but not always) used in pairs: |
1970 | prepare watchers get invoked before the process blocks and check watchers |
2143 | prepare watchers get invoked before the process blocks and check watchers |
1971 | afterwards. |
2144 | afterwards. |
1972 | .PP |
2145 | .PP |
1973 | You \fImust not\fR call \f(CW\*(C`ev_loop\*(C'\fR or similar functions that enter |
2146 | You \fImust not\fR call \f(CW\*(C`ev_loop\*(C'\fR or similar functions that enter |
1974 | the current event loop from either \f(CW\*(C`ev_prepare\*(C'\fR or \f(CW\*(C`ev_check\*(C'\fR |
2147 | the current event loop from either \f(CW\*(C`ev_prepare\*(C'\fR or \f(CW\*(C`ev_check\*(C'\fR |
… | |
… | |
1977 | those watchers, i.e. the sequence will always be \f(CW\*(C`ev_prepare\*(C'\fR, blocking, |
2150 | those watchers, i.e. the sequence will always be \f(CW\*(C`ev_prepare\*(C'\fR, blocking, |
1978 | \&\f(CW\*(C`ev_check\*(C'\fR so if you have one watcher of each kind they will always be |
2151 | \&\f(CW\*(C`ev_check\*(C'\fR so if you have one watcher of each kind they will always be |
1979 | called in pairs bracketing the blocking call. |
2152 | called in pairs bracketing the blocking call. |
1980 | .PP |
2153 | .PP |
1981 | Their main purpose is to integrate other event mechanisms into libev and |
2154 | Their main purpose is to integrate other event mechanisms into libev and |
1982 | their use is somewhat advanced. This could be used, for example, to track |
2155 | their use is somewhat advanced. They could be used, for example, to track |
1983 | variable changes, implement your own watchers, integrate net-snmp or a |
2156 | variable changes, implement your own watchers, integrate net-snmp or a |
1984 | coroutine library and lots more. They are also occasionally useful if |
2157 | coroutine library and lots more. They are also occasionally useful if |
1985 | you cache some data and want to flush it before blocking (for example, |
2158 | you cache some data and want to flush it before blocking (for example, |
1986 | in X programs you might want to do an \f(CW\*(C`XFlush ()\*(C'\fR in an \f(CW\*(C`ev_prepare\*(C'\fR |
2159 | in X programs you might want to do an \f(CW\*(C`XFlush ()\*(C'\fR in an \f(CW\*(C`ev_prepare\*(C'\fR |
1987 | watcher). |
2160 | watcher). |
1988 | .PP |
2161 | .PP |
1989 | This is done by examining in each prepare call which file descriptors need |
2162 | This is done by examining in each prepare call which file descriptors |
1990 | to be watched by the other library, registering \f(CW\*(C`ev_io\*(C'\fR watchers for |
2163 | need to be watched by the other library, registering \f(CW\*(C`ev_io\*(C'\fR watchers |
1991 | them and starting an \f(CW\*(C`ev_timer\*(C'\fR watcher for any timeouts (many libraries |
2164 | for them and starting an \f(CW\*(C`ev_timer\*(C'\fR watcher for any timeouts (many |
1992 | provide just this functionality). Then, in the check watcher you check for |
2165 | libraries provide exactly this functionality). Then, in the check watcher, |
1993 | any events that occured (by checking the pending status of all watchers |
2166 | you check for any events that occurred (by checking the pending status |
1994 | and stopping them) and call back into the library. The I/O and timer |
2167 | of all watchers and stopping them) and call back into the library. The |
1995 | callbacks will never actually be called (but must be valid nevertheless, |
2168 | I/O and timer callbacks will never actually be called (but must be valid |
1996 | because you never know, you know?). |
2169 | nevertheless, because you never know, you know?). |
1997 | .PP |
2170 | .PP |
1998 | As another example, the Perl Coro module uses these hooks to integrate |
2171 | As another example, the Perl Coro module uses these hooks to integrate |
1999 | coroutines into libev programs, by yielding to other active coroutines |
2172 | coroutines into libev programs, by yielding to other active coroutines |
2000 | during each prepare and only letting the process block if no coroutines |
2173 | during each prepare and only letting the process block if no coroutines |
2001 | are ready to run (it's actually more complicated: it only runs coroutines |
2174 | are ready to run (it's actually more complicated: it only runs coroutines |
… | |
… | |
2004 | loop from blocking if lower-priority coroutines are active, thus mapping |
2177 | loop from blocking if lower-priority coroutines are active, thus mapping |
2005 | low-priority coroutines to idle/background tasks). |
2178 | low-priority coroutines to idle/background tasks). |
2006 | .PP |
2179 | .PP |
2007 | It is recommended to give \f(CW\*(C`ev_check\*(C'\fR watchers highest (\f(CW\*(C`EV_MAXPRI\*(C'\fR) |
2180 | It is recommended to give \f(CW\*(C`ev_check\*(C'\fR watchers highest (\f(CW\*(C`EV_MAXPRI\*(C'\fR) |
2008 | priority, to ensure that they are being run before any other watchers |
2181 | priority, to ensure that they are being run before any other watchers |
|
|
2182 | after the poll (this doesn't matter for \f(CW\*(C`ev_prepare\*(C'\fR watchers). |
|
|
2183 | .PP |
2009 | after the poll. Also, \f(CW\*(C`ev_check\*(C'\fR watchers (and \f(CW\*(C`ev_prepare\*(C'\fR watchers, |
2184 | Also, \f(CW\*(C`ev_check\*(C'\fR watchers (and \f(CW\*(C`ev_prepare\*(C'\fR watchers, too) should not |
2010 | too) should not activate (\*(L"feed\*(R") events into libev. While libev fully |
2185 | activate (\*(L"feed\*(R") events into libev. While libev fully supports this, they |
2011 | supports this, they might get executed before other \f(CW\*(C`ev_check\*(C'\fR watchers |
2186 | might get executed before other \f(CW\*(C`ev_check\*(C'\fR watchers did their job. As |
2012 | did their job. As \f(CW\*(C`ev_check\*(C'\fR watchers are often used to embed other |
2187 | \&\f(CW\*(C`ev_check\*(C'\fR watchers are often used to embed other (non-libev) event |
2013 | (non-libev) event loops those other event loops might be in an unusable |
2188 | loops those other event loops might be in an unusable state until their |
2014 | state until their \f(CW\*(C`ev_check\*(C'\fR watcher ran (always remind yourself to |
2189 | \&\f(CW\*(C`ev_check\*(C'\fR watcher ran (always remind yourself to coexist peacefully with |
2015 | coexist peacefully with others). |
2190 | others). |
2016 | .PP |
2191 | .PP |
2017 | \fIWatcher-Specific Functions and Data Members\fR |
2192 | \fIWatcher-Specific Functions and Data Members\fR |
2018 | .IX Subsection "Watcher-Specific Functions and Data Members" |
2193 | .IX Subsection "Watcher-Specific Functions and Data Members" |
2019 | .IP "ev_prepare_init (ev_prepare *, callback)" 4 |
2194 | .IP "ev_prepare_init (ev_prepare *, callback)" 4 |
2020 | .IX Item "ev_prepare_init (ev_prepare *, callback)" |
2195 | .IX Item "ev_prepare_init (ev_prepare *, callback)" |
… | |
… | |
2022 | .IP "ev_check_init (ev_check *, callback)" 4 |
2197 | .IP "ev_check_init (ev_check *, callback)" 4 |
2023 | .IX Item "ev_check_init (ev_check *, callback)" |
2198 | .IX Item "ev_check_init (ev_check *, callback)" |
2024 | .PD |
2199 | .PD |
2025 | Initialises and configures the prepare or check watcher \- they have no |
2200 | Initialises and configures the prepare or check watcher \- they have no |
2026 | parameters of any kind. There are \f(CW\*(C`ev_prepare_set\*(C'\fR and \f(CW\*(C`ev_check_set\*(C'\fR |
2201 | parameters of any kind. There are \f(CW\*(C`ev_prepare_set\*(C'\fR and \f(CW\*(C`ev_check_set\*(C'\fR |
2027 | macros, but using them is utterly, utterly and completely pointless. |
2202 | macros, but using them is utterly, utterly, utterly and completely |
|
|
2203 | pointless. |
2028 | .PP |
2204 | .PP |
2029 | \fIExamples\fR |
2205 | \fIExamples\fR |
2030 | .IX Subsection "Examples" |
2206 | .IX Subsection "Examples" |
2031 | .PP |
2207 | .PP |
2032 | There are a number of principal ways to embed other event loops or modules |
2208 | There are a number of principal ways to embed other event loops or modules |
… | |
… | |
2041 | is pseudo-code only of course. This requires you to either use a low |
2217 | is pseudo-code only of course. This requires you to either use a low |
2042 | priority for the check watcher or use \f(CW\*(C`ev_clear_pending\*(C'\fR explicitly, as |
2218 | priority for the check watcher or use \f(CW\*(C`ev_clear_pending\*(C'\fR explicitly, as |
2043 | the callbacks for the IO/timeout watchers might not have been called yet. |
2219 | the callbacks for the IO/timeout watchers might not have been called yet. |
2044 | .PP |
2220 | .PP |
2045 | .Vb 2 |
2221 | .Vb 2 |
2046 | \& static ev_io iow [nfd]; |
2222 | \& static ev_io iow [nfd]; |
2047 | \& static ev_timer tw; |
2223 | \& static ev_timer tw; |
2048 | \& |
2224 | \& |
2049 | \& static void |
2225 | \& static void |
2050 | \& io_cb (ev_loop *loop, ev_io *w, int revents) |
2226 | \& io_cb (ev_loop *loop, ev_io *w, int revents) |
2051 | \& { |
2227 | \& { |
2052 | \& } |
2228 | \& } |
2053 | \& |
2229 | \& |
2054 | \& // create io watchers for each fd and a timer before blocking |
2230 | \& // create io watchers for each fd and a timer before blocking |
2055 | \& static void |
2231 | \& static void |
2056 | \& adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) |
2232 | \& adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) |
2057 | \& { |
2233 | \& { |
2058 | \& int timeout = 3600000; |
2234 | \& int timeout = 3600000; |
2059 | \& struct pollfd fds [nfd]; |
2235 | \& struct pollfd fds [nfd]; |
2060 | \& // actual code will need to loop here and realloc etc. |
2236 | \& // actual code will need to loop here and realloc etc. |
2061 | \& adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ())); |
2237 | \& adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ())); |
2062 | \& |
2238 | \& |
2063 | \& /* the callback is illegal, but won\*(Aqt be called as we stop during check */ |
2239 | \& /* the callback is illegal, but won\*(Aqt be called as we stop during check */ |
2064 | \& ev_timer_init (&tw, 0, timeout * 1e\-3); |
2240 | \& ev_timer_init (&tw, 0, timeout * 1e\-3); |
2065 | \& ev_timer_start (loop, &tw); |
2241 | \& ev_timer_start (loop, &tw); |
2066 | \& |
2242 | \& |
2067 | \& // create one ev_io per pollfd |
2243 | \& // create one ev_io per pollfd |
2068 | \& for (int i = 0; i < nfd; ++i) |
2244 | \& for (int i = 0; i < nfd; ++i) |
2069 | \& { |
2245 | \& { |
2070 | \& ev_io_init (iow + i, io_cb, fds [i].fd, |
2246 | \& ev_io_init (iow + i, io_cb, fds [i].fd, |
2071 | \& ((fds [i].events & POLLIN ? EV_READ : 0) |
2247 | \& ((fds [i].events & POLLIN ? EV_READ : 0) |
2072 | \& | (fds [i].events & POLLOUT ? EV_WRITE : 0))); |
2248 | \& | (fds [i].events & POLLOUT ? EV_WRITE : 0))); |
2073 | \& |
2249 | \& |
2074 | \& fds [i].revents = 0; |
2250 | \& fds [i].revents = 0; |
2075 | \& ev_io_start (loop, iow + i); |
2251 | \& ev_io_start (loop, iow + i); |
2076 | \& } |
2252 | \& } |
2077 | \& } |
2253 | \& } |
2078 | \& |
2254 | \& |
2079 | \& // stop all watchers after blocking |
2255 | \& // stop all watchers after blocking |
2080 | \& static void |
2256 | \& static void |
2081 | \& adns_check_cb (ev_loop *loop, ev_check *w, int revents) |
2257 | \& adns_check_cb (ev_loop *loop, ev_check *w, int revents) |
2082 | \& { |
2258 | \& { |
2083 | \& ev_timer_stop (loop, &tw); |
2259 | \& ev_timer_stop (loop, &tw); |
2084 | \& |
2260 | \& |
2085 | \& for (int i = 0; i < nfd; ++i) |
2261 | \& for (int i = 0; i < nfd; ++i) |
2086 | \& { |
2262 | \& { |
2087 | \& // set the relevant poll flags |
2263 | \& // set the relevant poll flags |
2088 | \& // could also call adns_processreadable etc. here |
2264 | \& // could also call adns_processreadable etc. here |
2089 | \& struct pollfd *fd = fds + i; |
2265 | \& struct pollfd *fd = fds + i; |
2090 | \& int revents = ev_clear_pending (iow + i); |
2266 | \& int revents = ev_clear_pending (iow + i); |
2091 | \& if (revents & EV_READ ) fd\->revents |= fd\->events & POLLIN; |
2267 | \& if (revents & EV_READ ) fd\->revents |= fd\->events & POLLIN; |
2092 | \& if (revents & EV_WRITE) fd\->revents |= fd\->events & POLLOUT; |
2268 | \& if (revents & EV_WRITE) fd\->revents |= fd\->events & POLLOUT; |
2093 | \& |
2269 | \& |
2094 | \& // now stop the watcher |
2270 | \& // now stop the watcher |
2095 | \& ev_io_stop (loop, iow + i); |
2271 | \& ev_io_stop (loop, iow + i); |
2096 | \& } |
2272 | \& } |
2097 | \& |
2273 | \& |
2098 | \& adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop)); |
2274 | \& adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop)); |
2099 | \& } |
2275 | \& } |
2100 | .Ve |
2276 | .Ve |
2101 | .PP |
2277 | .PP |
2102 | Method 2: This would be just like method 1, but you run \f(CW\*(C`adns_afterpoll\*(C'\fR |
2278 | Method 2: This would be just like method 1, but you run \f(CW\*(C`adns_afterpoll\*(C'\fR |
2103 | in the prepare watcher and would dispose of the check watcher. |
2279 | in the prepare watcher and would dispose of the check watcher. |
2104 | .PP |
2280 | .PP |
2105 | Method 3: If the module to be embedded supports explicit event |
2281 | Method 3: If the module to be embedded supports explicit event |
2106 | notification (adns does), you can also make use of the actual watcher |
2282 | notification (libadns does), you can also make use of the actual watcher |
2107 | callbacks, and only destroy/create the watchers in the prepare watcher. |
2283 | callbacks, and only destroy/create the watchers in the prepare watcher. |
2108 | .PP |
2284 | .PP |
2109 | .Vb 5 |
2285 | .Vb 5 |
2110 | \& static void |
2286 | \& static void |
2111 | \& timer_cb (EV_P_ ev_timer *w, int revents) |
2287 | \& timer_cb (EV_P_ ev_timer *w, int revents) |
2112 | \& { |
2288 | \& { |
2113 | \& adns_state ads = (adns_state)w\->data; |
2289 | \& adns_state ads = (adns_state)w\->data; |
2114 | \& update_now (EV_A); |
2290 | \& update_now (EV_A); |
2115 | \& |
2291 | \& |
2116 | \& adns_processtimeouts (ads, &tv_now); |
2292 | \& adns_processtimeouts (ads, &tv_now); |
2117 | \& } |
2293 | \& } |
2118 | \& |
2294 | \& |
2119 | \& static void |
2295 | \& static void |
2120 | \& io_cb (EV_P_ ev_io *w, int revents) |
2296 | \& io_cb (EV_P_ ev_io *w, int revents) |
2121 | \& { |
2297 | \& { |
2122 | \& adns_state ads = (adns_state)w\->data; |
2298 | \& adns_state ads = (adns_state)w\->data; |
2123 | \& update_now (EV_A); |
2299 | \& update_now (EV_A); |
2124 | \& |
2300 | \& |
2125 | \& if (revents & EV_READ ) adns_processreadable (ads, w\->fd, &tv_now); |
2301 | \& if (revents & EV_READ ) adns_processreadable (ads, w\->fd, &tv_now); |
2126 | \& if (revents & EV_WRITE) adns_processwriteable (ads, w\->fd, &tv_now); |
2302 | \& if (revents & EV_WRITE) adns_processwriteable (ads, w\->fd, &tv_now); |
2127 | \& } |
2303 | \& } |
2128 | \& |
2304 | \& |
2129 | \& // do not ever call adns_afterpoll |
2305 | \& // do not ever call adns_afterpoll |
2130 | .Ve |
2306 | .Ve |
2131 | .PP |
2307 | .PP |
2132 | Method 4: Do not use a prepare or check watcher because the module you |
2308 | Method 4: Do not use a prepare or check watcher because the module you |
2133 | want to embed is too inflexible to support it. Instead, youc na override |
2309 | want to embed is not flexible enough to support it. Instead, you can |
2134 | their poll function. The drawback with this solution is that the main |
2310 | override their poll function. The drawback with this solution is that the |
2135 | loop is now no longer controllable by \s-1EV\s0. The \f(CW\*(C`Glib::EV\*(C'\fR module does |
2311 | main loop is now no longer controllable by \s-1EV\s0. The \f(CW\*(C`Glib::EV\*(C'\fR module uses |
2136 | this. |
2312 | this approach, effectively embedding \s-1EV\s0 as a client into the horrible |
|
|
2313 | libglib event loop. |
2137 | .PP |
2314 | .PP |
2138 | .Vb 4 |
2315 | .Vb 4 |
2139 | \& static gint |
2316 | \& static gint |
2140 | \& event_poll_func (GPollFD *fds, guint nfds, gint timeout) |
2317 | \& event_poll_func (GPollFD *fds, guint nfds, gint timeout) |
2141 | \& { |
2318 | \& { |
2142 | \& int got_events = 0; |
2319 | \& int got_events = 0; |
2143 | \& |
2320 | \& |
2144 | \& for (n = 0; n < nfds; ++n) |
2321 | \& for (n = 0; n < nfds; ++n) |
2145 | \& // create/start io watcher that sets the relevant bits in fds[n] and increment got_events |
2322 | \& // create/start io watcher that sets the relevant bits in fds[n] and increment got_events |
2146 | \& |
2323 | \& |
2147 | \& if (timeout >= 0) |
2324 | \& if (timeout >= 0) |
2148 | \& // create/start timer |
2325 | \& // create/start timer |
2149 | \& |
2326 | \& |
2150 | \& // poll |
2327 | \& // poll |
2151 | \& ev_loop (EV_A_ 0); |
2328 | \& ev_loop (EV_A_ 0); |
2152 | \& |
2329 | \& |
2153 | \& // stop timer again |
2330 | \& // stop timer again |
2154 | \& if (timeout >= 0) |
2331 | \& if (timeout >= 0) |
2155 | \& ev_timer_stop (EV_A_ &to); |
2332 | \& ev_timer_stop (EV_A_ &to); |
2156 | \& |
2333 | \& |
2157 | \& // stop io watchers again \- their callbacks should have set |
2334 | \& // stop io watchers again \- their callbacks should have set |
2158 | \& for (n = 0; n < nfds; ++n) |
2335 | \& for (n = 0; n < nfds; ++n) |
2159 | \& ev_io_stop (EV_A_ iow [n]); |
2336 | \& ev_io_stop (EV_A_ iow [n]); |
2160 | \& |
2337 | \& |
2161 | \& return got_events; |
2338 | \& return got_events; |
2162 | \& } |
2339 | \& } |
2163 | .Ve |
2340 | .Ve |
2164 | .ie n .Sh """ev_embed"" \- when one backend isn't enough..." |
2341 | .ie n .Sh """ev_embed"" \- when one backend isn't enough..." |
2165 | .el .Sh "\f(CWev_embed\fP \- when one backend isn't enough..." |
2342 | .el .Sh "\f(CWev_embed\fP \- when one backend isn't enough..." |
2166 | .IX Subsection "ev_embed - when one backend isn't enough..." |
2343 | .IX Subsection "ev_embed - when one backend isn't enough..." |
2167 | This is a rather advanced watcher type that lets you embed one event loop |
2344 | This is a rather advanced watcher type that lets you embed one event loop |
… | |
… | |
2173 | prioritise I/O. |
2350 | prioritise I/O. |
2174 | .PP |
2351 | .PP |
2175 | As an example for a bug workaround, the kqueue backend might only support |
2352 | As an example for a bug workaround, the kqueue backend might only support |
2176 | sockets on some platform, so it is unusable as generic backend, but you |
2353 | sockets on some platform, so it is unusable as generic backend, but you |
2177 | still want to make use of it because you have many sockets and it scales |
2354 | still want to make use of it because you have many sockets and it scales |
2178 | so nicely. In this case, you would create a kqueue-based loop and embed it |
2355 | so nicely. In this case, you would create a kqueue-based loop and embed |
2179 | into your default loop (which might use e.g. poll). Overall operation will |
2356 | it into your default loop (which might use e.g. poll). Overall operation |
2180 | be a bit slower because first libev has to poll and then call kevent, but |
2357 | will be a bit slower because first libev has to call \f(CW\*(C`poll\*(C'\fR and then |
2181 | at least you can use both at what they are best. |
2358 | \&\f(CW\*(C`kevent\*(C'\fR, but at least you can use both mechanisms for what they are |
|
|
2359 | best: \f(CW\*(C`kqueue\*(C'\fR for scalable sockets and \f(CW\*(C`poll\*(C'\fR if you want it to work :) |
2182 | .PP |
2360 | .PP |
2183 | As for prioritising I/O: rarely you have the case where some fds have |
2361 | As for prioritising I/O: under rare circumstances you have the case where |
2184 | to be watched and handled very quickly (with low latency), and even |
2362 | some fds have to be watched and handled very quickly (with low latency), |
2185 | priorities and idle watchers might have too much overhead. In this case |
2363 | and even priorities and idle watchers might have too much overhead. In |
2186 | you would put all the high priority stuff in one loop and all the rest in |
2364 | this case you would put all the high priority stuff in one loop and all |
2187 | a second one, and embed the second one in the first. |
2365 | the rest in a second one, and embed the second one in the first. |
2188 | .PP |
2366 | .PP |
2189 | As long as the watcher is active, the callback will be invoked every time |
2367 | As long as the watcher is active, the callback will be invoked every time |
2190 | there might be events pending in the embedded loop. The callback must then |
2368 | there might be events pending in the embedded loop. The callback must then |
2191 | call \f(CW\*(C`ev_embed_sweep (mainloop, watcher)\*(C'\fR to make a single sweep and invoke |
2369 | call \f(CW\*(C`ev_embed_sweep (mainloop, watcher)\*(C'\fR to make a single sweep and invoke |
2192 | their callbacks (you could also start an idle watcher to give the embedded |
2370 | their callbacks (you could also start an idle watcher to give the embedded |
… | |
… | |
2200 | interested in that. |
2378 | interested in that. |
2201 | .PP |
2379 | .PP |
2202 | Also, there have not currently been made special provisions for forking: |
2380 | Also, there have not currently been made special provisions for forking: |
2203 | when you fork, you not only have to call \f(CW\*(C`ev_loop_fork\*(C'\fR on both loops, |
2381 | when you fork, you not only have to call \f(CW\*(C`ev_loop_fork\*(C'\fR on both loops, |
2204 | but you will also have to stop and restart any \f(CW\*(C`ev_embed\*(C'\fR watchers |
2382 | but you will also have to stop and restart any \f(CW\*(C`ev_embed\*(C'\fR watchers |
2205 | yourself. |
2383 | yourself \- but you can use a fork watcher to handle this automatically, |
|
|
2384 | and future versions of libev might do just that. |
2206 | .PP |
2385 | .PP |
2207 | Unfortunately, not all backends are embeddable, only the ones returned by |
2386 | Unfortunately, not all backends are embeddable: only the ones returned by |
2208 | \&\f(CW\*(C`ev_embeddable_backends\*(C'\fR are, which, unfortunately, does not include any |
2387 | \&\f(CW\*(C`ev_embeddable_backends\*(C'\fR are, which, unfortunately, does not include any |
2209 | portable one. |
2388 | portable one. |
2210 | .PP |
2389 | .PP |
2211 | So when you want to use this feature you will always have to be prepared |
2390 | So when you want to use this feature you will always have to be prepared |
2212 | that you cannot get an embeddable loop. The recommended way to get around |
2391 | that you cannot get an embeddable loop. The recommended way to get around |
2213 | this is to have a separate variables for your embeddable loop, try to |
2392 | this is to have a separate variables for your embeddable loop, try to |
2214 | create it, and if that fails, use the normal loop for everything. |
2393 | create it, and if that fails, use the normal loop for everything. |
|
|
2394 | .PP |
|
|
2395 | \fI\f(CI\*(C`ev_embed\*(C'\fI and fork\fR |
|
|
2396 | .IX Subsection "ev_embed and fork" |
|
|
2397 | .PP |
|
|
2398 | While the \f(CW\*(C`ev_embed\*(C'\fR watcher is running, forks in the embedding loop will |
|
|
2399 | automatically be applied to the embedded loop as well, so no special |
|
|
2400 | fork handling is required in that case. When the watcher is not running, |
|
|
2401 | however, it is still the task of the libev user to call \f(CW\*(C`ev_loop_fork ()\*(C'\fR |
|
|
2402 | as applicable. |
2215 | .PP |
2403 | .PP |
2216 | \fIWatcher-Specific Functions and Data Members\fR |
2404 | \fIWatcher-Specific Functions and Data Members\fR |
2217 | .IX Subsection "Watcher-Specific Functions and Data Members" |
2405 | .IX Subsection "Watcher-Specific Functions and Data Members" |
2218 | .IP "ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)" 4 |
2406 | .IP "ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)" 4 |
2219 | .IX Item "ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)" |
2407 | .IX Item "ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)" |
… | |
… | |
2223 | .PD |
2411 | .PD |
2224 | Configures the watcher to embed the given loop, which must be |
2412 | Configures the watcher to embed the given loop, which must be |
2225 | embeddable. If the callback is \f(CW0\fR, then \f(CW\*(C`ev_embed_sweep\*(C'\fR will be |
2413 | embeddable. If the callback is \f(CW0\fR, then \f(CW\*(C`ev_embed_sweep\*(C'\fR will be |
2226 | invoked automatically, otherwise it is the responsibility of the callback |
2414 | invoked automatically, otherwise it is the responsibility of the callback |
2227 | to invoke it (it will continue to be called until the sweep has been done, |
2415 | to invoke it (it will continue to be called until the sweep has been done, |
2228 | if you do not want thta, you need to temporarily stop the embed watcher). |
2416 | if you do not want that, you need to temporarily stop the embed watcher). |
2229 | .IP "ev_embed_sweep (loop, ev_embed *)" 4 |
2417 | .IP "ev_embed_sweep (loop, ev_embed *)" 4 |
2230 | .IX Item "ev_embed_sweep (loop, ev_embed *)" |
2418 | .IX Item "ev_embed_sweep (loop, ev_embed *)" |
2231 | Make a single, non-blocking sweep over the embedded loop. This works |
2419 | Make a single, non-blocking sweep over the embedded loop. This works |
2232 | similarly to \f(CW\*(C`ev_loop (embedded_loop, EVLOOP_NONBLOCK)\*(C'\fR, but in the most |
2420 | similarly to \f(CW\*(C`ev_loop (embedded_loop, EVLOOP_NONBLOCK)\*(C'\fR, but in the most |
2233 | apropriate way for embedded loops. |
2421 | appropriate way for embedded loops. |
2234 | .IP "struct ev_loop *other [read\-only]" 4 |
2422 | .IP "struct ev_loop *other [read\-only]" 4 |
2235 | .IX Item "struct ev_loop *other [read-only]" |
2423 | .IX Item "struct ev_loop *other [read-only]" |
2236 | The embedded event loop. |
2424 | The embedded event loop. |
2237 | .PP |
2425 | .PP |
2238 | \fIExamples\fR |
2426 | \fIExamples\fR |
2239 | .IX Subsection "Examples" |
2427 | .IX Subsection "Examples" |
2240 | .PP |
2428 | .PP |
2241 | Example: Try to get an embeddable event loop and embed it into the default |
2429 | Example: Try to get an embeddable event loop and embed it into the default |
2242 | event loop. If that is not possible, use the default loop. The default |
2430 | event loop. If that is not possible, use the default loop. The default |
2243 | loop is stored in \f(CW\*(C`loop_hi\*(C'\fR, while the mebeddable loop is stored in |
2431 | loop is stored in \f(CW\*(C`loop_hi\*(C'\fR, while the embeddable loop is stored in |
2244 | \&\f(CW\*(C`loop_lo\*(C'\fR (which is \f(CW\*(C`loop_hi\*(C'\fR in the acse no embeddable loop can be |
2432 | \&\f(CW\*(C`loop_lo\*(C'\fR (which is \f(CW\*(C`loop_hi\*(C'\fR in the case no embeddable loop can be |
2245 | used). |
2433 | used). |
2246 | .PP |
2434 | .PP |
2247 | .Vb 3 |
2435 | .Vb 3 |
2248 | \& struct ev_loop *loop_hi = ev_default_init (0); |
2436 | \& struct ev_loop *loop_hi = ev_default_init (0); |
2249 | \& struct ev_loop *loop_lo = 0; |
2437 | \& struct ev_loop *loop_lo = 0; |
2250 | \& struct ev_embed embed; |
2438 | \& struct ev_embed embed; |
2251 | \& |
2439 | \& |
2252 | \& // see if there is a chance of getting one that works |
2440 | \& // see if there is a chance of getting one that works |
2253 | \& // (remember that a flags value of 0 means autodetection) |
2441 | \& // (remember that a flags value of 0 means autodetection) |
2254 | \& loop_lo = ev_embeddable_backends () & ev_recommended_backends () |
2442 | \& loop_lo = ev_embeddable_backends () & ev_recommended_backends () |
2255 | \& ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ()) |
2443 | \& ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ()) |
2256 | \& : 0; |
2444 | \& : 0; |
2257 | \& |
2445 | \& |
2258 | \& // if we got one, then embed it, otherwise default to loop_hi |
2446 | \& // if we got one, then embed it, otherwise default to loop_hi |
2259 | \& if (loop_lo) |
2447 | \& if (loop_lo) |
2260 | \& { |
2448 | \& { |
2261 | \& ev_embed_init (&embed, 0, loop_lo); |
2449 | \& ev_embed_init (&embed, 0, loop_lo); |
2262 | \& ev_embed_start (loop_hi, &embed); |
2450 | \& ev_embed_start (loop_hi, &embed); |
2263 | \& } |
2451 | \& } |
2264 | \& else |
2452 | \& else |
2265 | \& loop_lo = loop_hi; |
2453 | \& loop_lo = loop_hi; |
2266 | .Ve |
2454 | .Ve |
2267 | .PP |
2455 | .PP |
2268 | Example: Check if kqueue is available but not recommended and create |
2456 | Example: Check if kqueue is available but not recommended and create |
2269 | a kqueue backend for use with sockets (which usually work with any |
2457 | a kqueue backend for use with sockets (which usually work with any |
2270 | kqueue implementation). Store the kqueue/socket\-only event loop in |
2458 | kqueue implementation). Store the kqueue/socket\-only event loop in |
2271 | \&\f(CW\*(C`loop_socket\*(C'\fR. (One might optionally use \f(CW\*(C`EVFLAG_NOENV\*(C'\fR, too). |
2459 | \&\f(CW\*(C`loop_socket\*(C'\fR. (One might optionally use \f(CW\*(C`EVFLAG_NOENV\*(C'\fR, too). |
2272 | .PP |
2460 | .PP |
2273 | .Vb 3 |
2461 | .Vb 3 |
2274 | \& struct ev_loop *loop = ev_default_init (0); |
2462 | \& struct ev_loop *loop = ev_default_init (0); |
2275 | \& struct ev_loop *loop_socket = 0; |
2463 | \& struct ev_loop *loop_socket = 0; |
2276 | \& struct ev_embed embed; |
2464 | \& struct ev_embed embed; |
2277 | \& |
2465 | \& |
2278 | \& if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE) |
2466 | \& if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE) |
2279 | \& if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE)) |
2467 | \& if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE)) |
2280 | \& { |
2468 | \& { |
2281 | \& ev_embed_init (&embed, 0, loop_socket); |
2469 | \& ev_embed_init (&embed, 0, loop_socket); |
2282 | \& ev_embed_start (loop, &embed); |
2470 | \& ev_embed_start (loop, &embed); |
2283 | \& } |
2471 | \& } |
2284 | \& |
2472 | \& |
2285 | \& if (!loop_socket) |
2473 | \& if (!loop_socket) |
2286 | \& loop_socket = loop; |
2474 | \& loop_socket = loop; |
2287 | \& |
2475 | \& |
2288 | \& // now use loop_socket for all sockets, and loop for everything else |
2476 | \& // now use loop_socket for all sockets, and loop for everything else |
2289 | .Ve |
2477 | .Ve |
2290 | .ie n .Sh """ev_fork"" \- the audacity to resume the event loop after a fork" |
2478 | .ie n .Sh """ev_fork"" \- the audacity to resume the event loop after a fork" |
2291 | .el .Sh "\f(CWev_fork\fP \- the audacity to resume the event loop after a fork" |
2479 | .el .Sh "\f(CWev_fork\fP \- the audacity to resume the event loop after a fork" |
2292 | .IX Subsection "ev_fork - the audacity to resume the event loop after a fork" |
2480 | .IX Subsection "ev_fork - the audacity to resume the event loop after a fork" |
2293 | Fork watchers are called when a \f(CW\*(C`fork ()\*(C'\fR was detected (usually because |
2481 | Fork watchers are called when a \f(CW\*(C`fork ()\*(C'\fR was detected (usually because |
… | |
… | |
2333 | is that the author does not know of a simple (or any) algorithm for a |
2521 | is that the author does not know of a simple (or any) algorithm for a |
2334 | multiple-writer-single-reader queue that works in all cases and doesn't |
2522 | multiple-writer-single-reader queue that works in all cases and doesn't |
2335 | need elaborate support such as pthreads. |
2523 | need elaborate support such as pthreads. |
2336 | .PP |
2524 | .PP |
2337 | That means that if you want to queue data, you have to provide your own |
2525 | That means that if you want to queue data, you have to provide your own |
2338 | queue. But at least I can tell you would implement locking around your |
2526 | queue. But at least I can tell you how to implement locking around your |
2339 | queue: |
2527 | queue: |
2340 | .IP "queueing from a signal handler context" 4 |
2528 | .IP "queueing from a signal handler context" 4 |
2341 | .IX Item "queueing from a signal handler context" |
2529 | .IX Item "queueing from a signal handler context" |
2342 | To implement race-free queueing, you simply add to the queue in the signal |
2530 | To implement race-free queueing, you simply add to the queue in the signal |
2343 | handler but you block the signal handler in the watcher callback. Here is an example that does that for |
2531 | handler but you block the signal handler in the watcher callback. Here is |
2344 | some fictitiuous \s-1SIGUSR1\s0 handler: |
2532 | an example that does that for some fictitious \s-1SIGUSR1\s0 handler: |
2345 | .Sp |
2533 | .Sp |
2346 | .Vb 1 |
2534 | .Vb 1 |
2347 | \& static ev_async mysig; |
2535 | \& static ev_async mysig; |
2348 | \& |
2536 | \& |
2349 | \& static void |
2537 | \& static void |
… | |
… | |
2414 | .IX Subsection "Watcher-Specific Functions and Data Members" |
2602 | .IX Subsection "Watcher-Specific Functions and Data Members" |
2415 | .IP "ev_async_init (ev_async *, callback)" 4 |
2603 | .IP "ev_async_init (ev_async *, callback)" 4 |
2416 | .IX Item "ev_async_init (ev_async *, callback)" |
2604 | .IX Item "ev_async_init (ev_async *, callback)" |
2417 | Initialises and configures the async watcher \- it has no parameters of any |
2605 | Initialises and configures the async watcher \- it has no parameters of any |
2418 | kind. There is a \f(CW\*(C`ev_asynd_set\*(C'\fR macro, but using it is utterly pointless, |
2606 | kind. There is a \f(CW\*(C`ev_asynd_set\*(C'\fR macro, but using it is utterly pointless, |
2419 | believe me. |
2607 | trust me. |
2420 | .IP "ev_async_send (loop, ev_async *)" 4 |
2608 | .IP "ev_async_send (loop, ev_async *)" 4 |
2421 | .IX Item "ev_async_send (loop, ev_async *)" |
2609 | .IX Item "ev_async_send (loop, ev_async *)" |
2422 | Sends/signals/activates the given \f(CW\*(C`ev_async\*(C'\fR watcher, that is, feeds |
2610 | Sends/signals/activates the given \f(CW\*(C`ev_async\*(C'\fR watcher, that is, feeds |
2423 | an \f(CW\*(C`EV_ASYNC\*(C'\fR event on the watcher into the event loop. Unlike |
2611 | an \f(CW\*(C`EV_ASYNC\*(C'\fR event on the watcher into the event loop. Unlike |
2424 | \&\f(CW\*(C`ev_feed_event\*(C'\fR, this call is safe to do in other threads, signal or |
2612 | \&\f(CW\*(C`ev_feed_event\*(C'\fR, this call is safe to do from other threads, signal or |
2425 | similar contexts (see the dicusssion of \f(CW\*(C`EV_ATOMIC_T\*(C'\fR in the embedding |
2613 | similar contexts (see the discussion of \f(CW\*(C`EV_ATOMIC_T\*(C'\fR in the embedding |
2426 | section below on what exactly this means). |
2614 | section below on what exactly this means). |
2427 | .Sp |
2615 | .Sp |
2428 | This call incurs the overhead of a syscall only once per loop iteration, |
2616 | This call incurs the overhead of a system call only once per loop iteration, |
2429 | so while the overhead might be noticable, it doesn't apply to repeated |
2617 | so while the overhead might be noticeable, it doesn't apply to repeated |
2430 | calls to \f(CW\*(C`ev_async_send\*(C'\fR. |
2618 | calls to \f(CW\*(C`ev_async_send\*(C'\fR. |
2431 | .IP "bool = ev_async_pending (ev_async *)" 4 |
2619 | .IP "bool = ev_async_pending (ev_async *)" 4 |
2432 | .IX Item "bool = ev_async_pending (ev_async *)" |
2620 | .IX Item "bool = ev_async_pending (ev_async *)" |
2433 | Returns a non-zero value when \f(CW\*(C`ev_async_send\*(C'\fR has been called on the |
2621 | Returns a non-zero value when \f(CW\*(C`ev_async_send\*(C'\fR has been called on the |
2434 | watcher but the event has not yet been processed (or even noted) by the |
2622 | watcher but the event has not yet been processed (or even noted) by the |
2435 | event loop. |
2623 | event loop. |
2436 | .Sp |
2624 | .Sp |
2437 | \&\f(CW\*(C`ev_async_send\*(C'\fR sets a flag in the watcher and wakes up the loop. When |
2625 | \&\f(CW\*(C`ev_async_send\*(C'\fR sets a flag in the watcher and wakes up the loop. When |
2438 | the loop iterates next and checks for the watcher to have become active, |
2626 | the loop iterates next and checks for the watcher to have become active, |
2439 | it will reset the flag again. \f(CW\*(C`ev_async_pending\*(C'\fR can be used to very |
2627 | it will reset the flag again. \f(CW\*(C`ev_async_pending\*(C'\fR can be used to very |
2440 | quickly check wether invoking the loop might be a good idea. |
2628 | quickly check whether invoking the loop might be a good idea. |
2441 | .Sp |
2629 | .Sp |
2442 | Not that this does \fInot\fR check wether the watcher itself is pending, only |
2630 | Not that this does \fInot\fR check whether the watcher itself is pending, only |
2443 | wether it has been requested to make this watcher pending. |
2631 | whether it has been requested to make this watcher pending. |
2444 | .SH "OTHER FUNCTIONS" |
2632 | .SH "OTHER FUNCTIONS" |
2445 | .IX Header "OTHER FUNCTIONS" |
2633 | .IX Header "OTHER FUNCTIONS" |
2446 | There are some other functions of possible interest. Described. Here. Now. |
2634 | There are some other functions of possible interest. Described. Here. Now. |
2447 | .IP "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)" 4 |
2635 | .IP "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)" 4 |
2448 | .IX Item "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)" |
2636 | .IX Item "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)" |
2449 | This function combines a simple timer and an I/O watcher, calls your |
2637 | This function combines a simple timer and an I/O watcher, calls your |
2450 | callback on whichever event happens first and automatically stop both |
2638 | callback on whichever event happens first and automatically stops both |
2451 | watchers. This is useful if you want to wait for a single event on an fd |
2639 | watchers. This is useful if you want to wait for a single event on an fd |
2452 | or timeout without having to allocate/configure/start/stop/free one or |
2640 | or timeout without having to allocate/configure/start/stop/free one or |
2453 | more watchers yourself. |
2641 | more watchers yourself. |
2454 | .Sp |
2642 | .Sp |
2455 | If \f(CW\*(C`fd\*(C'\fR is less than 0, then no I/O watcher will be started and events |
2643 | If \f(CW\*(C`fd\*(C'\fR is less than 0, then no I/O watcher will be started and the |
2456 | is being ignored. Otherwise, an \f(CW\*(C`ev_io\*(C'\fR watcher for the given \f(CW\*(C`fd\*(C'\fR and |
2644 | \&\f(CW\*(C`events\*(C'\fR argument is being ignored. Otherwise, an \f(CW\*(C`ev_io\*(C'\fR watcher for |
2457 | \&\f(CW\*(C`events\*(C'\fR set will be craeted and started. |
2645 | the given \f(CW\*(C`fd\*(C'\fR and \f(CW\*(C`events\*(C'\fR set will be created and started. |
2458 | .Sp |
2646 | .Sp |
2459 | If \f(CW\*(C`timeout\*(C'\fR is less than 0, then no timeout watcher will be |
2647 | If \f(CW\*(C`timeout\*(C'\fR is less than 0, then no timeout watcher will be |
2460 | started. Otherwise an \f(CW\*(C`ev_timer\*(C'\fR watcher with after = \f(CW\*(C`timeout\*(C'\fR (and |
2648 | started. Otherwise an \f(CW\*(C`ev_timer\*(C'\fR watcher with after = \f(CW\*(C`timeout\*(C'\fR (and |
2461 | repeat = 0) will be started. While \f(CW0\fR is a valid timeout, it is of |
2649 | repeat = 0) will be started. \f(CW0\fR is a valid timeout. |
2462 | dubious value. |
|
|
2463 | .Sp |
2650 | .Sp |
2464 | The callback has the type \f(CW\*(C`void (*cb)(int revents, void *arg)\*(C'\fR and gets |
2651 | The callback has the type \f(CW\*(C`void (*cb)(int revents, void *arg)\*(C'\fR and gets |
2465 | passed an \f(CW\*(C`revents\*(C'\fR set like normal event callbacks (a combination of |
2652 | passed an \f(CW\*(C`revents\*(C'\fR set like normal event callbacks (a combination of |
2466 | \&\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_TIMEOUT\*(C'\fR) and the \f(CW\*(C`arg\*(C'\fR |
2653 | \&\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_TIMEOUT\*(C'\fR) and the \f(CW\*(C`arg\*(C'\fR |
2467 | value passed to \f(CW\*(C`ev_once\*(C'\fR: |
2654 | value passed to \f(CW\*(C`ev_once\*(C'\fR. Note that it is possible to receive \fIboth\fR |
|
|
2655 | a timeout and an io event at the same time \- you probably should give io |
|
|
2656 | events precedence. |
|
|
2657 | .Sp |
|
|
2658 | Example: wait up to ten seconds for data to appear on \s-1STDIN_FILENO\s0. |
2468 | .Sp |
2659 | .Sp |
2469 | .Vb 7 |
2660 | .Vb 7 |
2470 | \& static void stdin_ready (int revents, void *arg) |
2661 | \& static void stdin_ready (int revents, void *arg) |
2471 | \& { |
2662 | \& { |
2472 | \& if (revents & EV_TIMEOUT) |
|
|
2473 | \& /* doh, nothing entered */; |
|
|
2474 | \& else if (revents & EV_READ) |
2663 | \& if (revents & EV_READ) |
2475 | \& /* stdin might have data for us, joy! */; |
2664 | \& /* stdin might have data for us, joy! */; |
|
|
2665 | \& else if (revents & EV_TIMEOUT) |
|
|
2666 | \& /* doh, nothing entered */; |
2476 | \& } |
2667 | \& } |
2477 | \& |
2668 | \& |
2478 | \& ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
2669 | \& ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
2479 | .Ve |
2670 | .Ve |
2480 | .IP "ev_feed_event (ev_loop *, watcher *, int revents)" 4 |
2671 | .IP "ev_feed_event (ev_loop *, watcher *, int revents)" 4 |
2481 | .IX Item "ev_feed_event (ev_loop *, watcher *, int revents)" |
2672 | .IX Item "ev_feed_event (ev_loop *, watcher *, int revents)" |
2482 | Feeds the given event set into the event loop, as if the specified event |
2673 | Feeds the given event set into the event loop, as if the specified event |
2483 | had happened for the specified watcher (which must be a pointer to an |
2674 | had happened for the specified watcher (which must be a pointer to an |
… | |
… | |
2486 | .IX Item "ev_feed_fd_event (ev_loop *, int fd, int revents)" |
2677 | .IX Item "ev_feed_fd_event (ev_loop *, int fd, int revents)" |
2487 | Feed an event on the given fd, as if a file descriptor backend detected |
2678 | Feed an event on the given fd, as if a file descriptor backend detected |
2488 | the given events it. |
2679 | the given events it. |
2489 | .IP "ev_feed_signal_event (ev_loop *loop, int signum)" 4 |
2680 | .IP "ev_feed_signal_event (ev_loop *loop, int signum)" 4 |
2490 | .IX Item "ev_feed_signal_event (ev_loop *loop, int signum)" |
2681 | .IX Item "ev_feed_signal_event (ev_loop *loop, int signum)" |
2491 | Feed an event as if the given signal occured (\f(CW\*(C`loop\*(C'\fR must be the default |
2682 | Feed an event as if the given signal occurred (\f(CW\*(C`loop\*(C'\fR must be the default |
2492 | loop!). |
2683 | loop!). |
2493 | .SH "LIBEVENT EMULATION" |
2684 | .SH "LIBEVENT EMULATION" |
2494 | .IX Header "LIBEVENT EMULATION" |
2685 | .IX Header "LIBEVENT EMULATION" |
2495 | Libev offers a compatibility emulation layer for libevent. It cannot |
2686 | Libev offers a compatibility emulation layer for libevent. It cannot |
2496 | emulate the internals of libevent, so here are some usage hints: |
2687 | emulate the internals of libevent, so here are some usage hints: |
… | |
… | |
2516 | The libev emulation is \fInot\fR \s-1ABI\s0 compatible to libevent, you need |
2707 | The libev emulation is \fInot\fR \s-1ABI\s0 compatible to libevent, you need |
2517 | to use the libev header file and library. |
2708 | to use the libev header file and library. |
2518 | .SH "\*(C+ SUPPORT" |
2709 | .SH "\*(C+ SUPPORT" |
2519 | .IX Header " SUPPORT" |
2710 | .IX Header " SUPPORT" |
2520 | Libev comes with some simplistic wrapper classes for \*(C+ that mainly allow |
2711 | Libev comes with some simplistic wrapper classes for \*(C+ that mainly allow |
2521 | you to use some convinience methods to start/stop watchers and also change |
2712 | you to use some convenience methods to start/stop watchers and also change |
2522 | the callback model to a model using method callbacks on objects. |
2713 | the callback model to a model using method callbacks on objects. |
2523 | .PP |
2714 | .PP |
2524 | To use it, |
2715 | To use it, |
2525 | .PP |
2716 | .PP |
2526 | .Vb 1 |
2717 | .Vb 1 |
2527 | \& #include <ev++.h> |
2718 | \& #include <ev++.h> |
2528 | .Ve |
2719 | .Ve |
2529 | .PP |
2720 | .PP |
2530 | This automatically includes \fIev.h\fR and puts all of its definitions (many |
2721 | This automatically includes \fIev.h\fR and puts all of its definitions (many |
2531 | of them macros) into the global namespace. All \*(C+ specific things are |
2722 | of them macros) into the global namespace. All \*(C+ specific things are |
2532 | put into the \f(CW\*(C`ev\*(C'\fR namespace. It should support all the same embedding |
2723 | put into the \f(CW\*(C`ev\*(C'\fR namespace. It should support all the same embedding |
… | |
… | |
2598 | thunking function, making it as fast as a direct C callback. |
2789 | thunking function, making it as fast as a direct C callback. |
2599 | .Sp |
2790 | .Sp |
2600 | Example: simple class declaration and watcher initialisation |
2791 | Example: simple class declaration and watcher initialisation |
2601 | .Sp |
2792 | .Sp |
2602 | .Vb 4 |
2793 | .Vb 4 |
2603 | \& struct myclass |
2794 | \& struct myclass |
2604 | \& { |
2795 | \& { |
2605 | \& void io_cb (ev::io &w, int revents) { } |
2796 | \& void io_cb (ev::io &w, int revents) { } |
2606 | \& } |
2797 | \& } |
2607 | \& |
2798 | \& |
2608 | \& myclass obj; |
2799 | \& myclass obj; |
2609 | \& ev::io iow; |
2800 | \& ev::io iow; |
2610 | \& iow.set <myclass, &myclass::io_cb> (&obj); |
2801 | \& iow.set <myclass, &myclass::io_cb> (&obj); |
2611 | .Ve |
2802 | .Ve |
2612 | .IP "w\->set<function> (void *data = 0)" 4 |
2803 | .IP "w\->set<function> (void *data = 0)" 4 |
2613 | .IX Item "w->set<function> (void *data = 0)" |
2804 | .IX Item "w->set<function> (void *data = 0)" |
2614 | Also sets a callback, but uses a static method or plain function as |
2805 | Also sets a callback, but uses a static method or plain function as |
2615 | callback. The optional \f(CW\*(C`data\*(C'\fR argument will be stored in the watcher's |
2806 | callback. The optional \f(CW\*(C`data\*(C'\fR argument will be stored in the watcher's |
… | |
… | |
2617 | .Sp |
2808 | .Sp |
2618 | The prototype of the \f(CW\*(C`function\*(C'\fR must be \f(CW\*(C`void (*)(ev::TYPE &w, int)\*(C'\fR. |
2809 | The prototype of the \f(CW\*(C`function\*(C'\fR must be \f(CW\*(C`void (*)(ev::TYPE &w, int)\*(C'\fR. |
2619 | .Sp |
2810 | .Sp |
2620 | See the method\-\f(CW\*(C`set\*(C'\fR above for more details. |
2811 | See the method\-\f(CW\*(C`set\*(C'\fR above for more details. |
2621 | .Sp |
2812 | .Sp |
2622 | Example: |
2813 | Example: Use a plain function as callback. |
2623 | .Sp |
2814 | .Sp |
2624 | .Vb 2 |
2815 | .Vb 2 |
2625 | \& static void io_cb (ev::io &w, int revents) { } |
2816 | \& static void io_cb (ev::io &w, int revents) { } |
2626 | \& iow.set <io_cb> (); |
2817 | \& iow.set <io_cb> (); |
2627 | .Ve |
2818 | .Ve |
2628 | .IP "w\->set (struct ev_loop *)" 4 |
2819 | .IP "w\->set (struct ev_loop *)" 4 |
2629 | .IX Item "w->set (struct ev_loop *)" |
2820 | .IX Item "w->set (struct ev_loop *)" |
2630 | Associates a different \f(CW\*(C`struct ev_loop\*(C'\fR with this watcher. You can only |
2821 | Associates a different \f(CW\*(C`struct ev_loop\*(C'\fR with this watcher. You can only |
2631 | do this when the watcher is inactive (and not pending either). |
2822 | do this when the watcher is inactive (and not pending either). |
2632 | .IP "w\->set ([args])" 4 |
2823 | .IP "w\->set ([arguments])" 4 |
2633 | .IX Item "w->set ([args])" |
2824 | .IX Item "w->set ([arguments])" |
2634 | Basically the same as \f(CW\*(C`ev_TYPE_set\*(C'\fR, with the same args. Must be |
2825 | Basically the same as \f(CW\*(C`ev_TYPE_set\*(C'\fR, with the same arguments. Must be |
2635 | called at least once. Unlike the C counterpart, an active watcher gets |
2826 | called at least once. Unlike the C counterpart, an active watcher gets |
2636 | automatically stopped and restarted when reconfiguring it with this |
2827 | automatically stopped and restarted when reconfiguring it with this |
2637 | method. |
2828 | method. |
2638 | .IP "w\->start ()" 4 |
2829 | .IP "w\->start ()" 4 |
2639 | .IX Item "w->start ()" |
2830 | .IX Item "w->start ()" |
… | |
… | |
2661 | .PP |
2852 | .PP |
2662 | Example: Define a class with an \s-1IO\s0 and idle watcher, start one of them in |
2853 | Example: Define a class with an \s-1IO\s0 and idle watcher, start one of them in |
2663 | the constructor. |
2854 | the constructor. |
2664 | .PP |
2855 | .PP |
2665 | .Vb 4 |
2856 | .Vb 4 |
2666 | \& class myclass |
2857 | \& class myclass |
2667 | \& { |
2858 | \& { |
2668 | \& ev::io io; void io_cb (ev::io &w, int revents); |
2859 | \& ev::io io ; void io_cb (ev::io &w, int revents); |
2669 | \& ev:idle idle void idle_cb (ev::idle &w, int revents); |
2860 | \& ev::idle idle; void idle_cb (ev::idle &w, int revents); |
2670 | \& |
2861 | \& |
2671 | \& myclass (int fd) |
2862 | \& myclass (int fd) |
2672 | \& { |
2863 | \& { |
2673 | \& io .set <myclass, &myclass::io_cb > (this); |
2864 | \& io .set <myclass, &myclass::io_cb > (this); |
2674 | \& idle.set <myclass, &myclass::idle_cb> (this); |
2865 | \& idle.set <myclass, &myclass::idle_cb> (this); |
2675 | \& |
2866 | \& |
2676 | \& io.start (fd, ev::READ); |
2867 | \& io.start (fd, ev::READ); |
2677 | \& } |
2868 | \& } |
2678 | \& }; |
2869 | \& }; |
2679 | .Ve |
2870 | .Ve |
2680 | .SH "OTHER LANGUAGE BINDINGS" |
2871 | .SH "OTHER LANGUAGE BINDINGS" |
2681 | .IX Header "OTHER LANGUAGE BINDINGS" |
2872 | .IX Header "OTHER LANGUAGE BINDINGS" |
2682 | Libev does not offer other language bindings itself, but bindings for a |
2873 | Libev does not offer other language bindings itself, but bindings for a |
2683 | numbe rof languages exist in the form of third-party packages. If you know |
2874 | number of languages exist in the form of third-party packages. If you know |
2684 | any interesting language binding in addition to the ones listed here, drop |
2875 | any interesting language binding in addition to the ones listed here, drop |
2685 | me a note. |
2876 | me a note. |
2686 | .IP "Perl" 4 |
2877 | .IP "Perl" 4 |
2687 | .IX Item "Perl" |
2878 | .IX Item "Perl" |
2688 | The \s-1EV\s0 module implements the full libev \s-1API\s0 and is actually used to test |
2879 | The \s-1EV\s0 module implements the full libev \s-1API\s0 and is actually used to test |
2689 | libev. \s-1EV\s0 is developed together with libev. Apart from the \s-1EV\s0 core module, |
2880 | libev. \s-1EV\s0 is developed together with libev. Apart from the \s-1EV\s0 core module, |
2690 | there are additional modules that implement libev-compatible interfaces |
2881 | there are additional modules that implement libev-compatible interfaces |
2691 | to \f(CW\*(C`libadns\*(C'\fR (\f(CW\*(C`EV::ADNS\*(C'\fR), \f(CW\*(C`Net::SNMP\*(C'\fR (\f(CW\*(C`Net::SNMP::EV\*(C'\fR) and the |
2882 | 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), |
2692 | \&\f(CW\*(C`libglib\*(C'\fR event core (\f(CW\*(C`Glib::EV\*(C'\fR and \f(CW\*(C`EV::Glib\*(C'\fR). |
2883 | \&\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 |
|
|
2884 | and \f(CW\*(C`EV::Glib\*(C'\fR). |
2693 | .Sp |
2885 | .Sp |
2694 | It can be found and installed via \s-1CPAN\s0, its homepage is found at |
2886 | It can be found and installed via \s-1CPAN\s0, its homepage is at |
2695 | <http://software.schmorp.de/pkg/EV>. |
2887 | <http://software.schmorp.de/pkg/EV>. |
|
|
2888 | .IP "Python" 4 |
|
|
2889 | .IX Item "Python" |
|
|
2890 | Python bindings can be found at <http://code.google.com/p/pyev/>. It |
|
|
2891 | seems to be quite complete and well-documented. Note, however, that the |
|
|
2892 | patch they require for libev is outright dangerous as it breaks the \s-1ABI\s0 |
|
|
2893 | for everybody else, and therefore, should never be applied in an installed |
|
|
2894 | libev (if python requires an incompatible \s-1ABI\s0 then it needs to embed |
|
|
2895 | libev). |
2696 | .IP "Ruby" 4 |
2896 | .IP "Ruby" 4 |
2697 | .IX Item "Ruby" |
2897 | .IX Item "Ruby" |
2698 | Tony Arcieri has written a ruby extension that offers access to a subset |
2898 | Tony Arcieri has written a ruby extension that offers access to a subset |
2699 | of the libev \s-1API\s0 and adds filehandle abstractions, asynchronous \s-1DNS\s0 and |
2899 | of the libev \s-1API\s0 and adds file handle abstractions, asynchronous \s-1DNS\s0 and |
2700 | more on top of it. It can be found via gem servers. Its homepage is at |
2900 | more on top of it. It can be found via gem servers. Its homepage is at |
2701 | <http://rev.rubyforge.org/>. |
2901 | <http://rev.rubyforge.org/>. |
2702 | .IP "D" 4 |
2902 | .IP "D" 4 |
2703 | .IX Item "D" |
2903 | .IX Item "D" |
2704 | Leandro Lucarella has written a D language binding (\fIev.d\fR) for libev, to |
2904 | Leandro Lucarella has written a D language binding (\fIev.d\fR) for libev, to |
2705 | be found at <http://git.llucax.com.ar/?p=software/ev.d.git;a=summary>. |
2905 | be found at <http://proj.llucax.com.ar/wiki/evd>. |
2706 | .SH "MACRO MAGIC" |
2906 | .SH "MACRO MAGIC" |
2707 | .IX Header "MACRO MAGIC" |
2907 | .IX Header "MACRO MAGIC" |
2708 | Libev can be compiled with a variety of options, the most fundamantal |
2908 | Libev can be compiled with a variety of options, the most fundamental |
2709 | of which is \f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. This option determines whether (most) |
2909 | of which is \f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. This option determines whether (most) |
2710 | functions and callbacks have an initial \f(CW\*(C`struct ev_loop *\*(C'\fR argument. |
2910 | functions and callbacks have an initial \f(CW\*(C`struct ev_loop *\*(C'\fR argument. |
2711 | .PP |
2911 | .PP |
2712 | To make it easier to write programs that cope with either variant, the |
2912 | To make it easier to write programs that cope with either variant, the |
2713 | following macros are defined: |
2913 | following macros are defined: |
… | |
… | |
2717 | This provides the loop \fIargument\fR for functions, if one is required (\*(L"ev |
2917 | This provides the loop \fIargument\fR for functions, if one is required (\*(L"ev |
2718 | loop argument\*(R"). The \f(CW\*(C`EV_A\*(C'\fR form is used when this is the sole argument, |
2918 | loop argument\*(R"). The \f(CW\*(C`EV_A\*(C'\fR form is used when this is the sole argument, |
2719 | \&\f(CW\*(C`EV_A_\*(C'\fR is used when other arguments are following. Example: |
2919 | \&\f(CW\*(C`EV_A_\*(C'\fR is used when other arguments are following. Example: |
2720 | .Sp |
2920 | .Sp |
2721 | .Vb 3 |
2921 | .Vb 3 |
2722 | \& ev_unref (EV_A); |
2922 | \& ev_unref (EV_A); |
2723 | \& ev_timer_add (EV_A_ watcher); |
2923 | \& ev_timer_add (EV_A_ watcher); |
2724 | \& ev_loop (EV_A_ 0); |
2924 | \& ev_loop (EV_A_ 0); |
2725 | .Ve |
2925 | .Ve |
2726 | .Sp |
2926 | .Sp |
2727 | It assumes the variable \f(CW\*(C`loop\*(C'\fR of type \f(CW\*(C`struct ev_loop *\*(C'\fR is in scope, |
2927 | It assumes the variable \f(CW\*(C`loop\*(C'\fR of type \f(CW\*(C`struct ev_loop *\*(C'\fR is in scope, |
2728 | which is often provided by the following macro. |
2928 | which is often provided by the following macro. |
2729 | .ie n .IP """EV_P""\fR, \f(CW""EV_P_""" 4 |
2929 | .ie n .IP """EV_P""\fR, \f(CW""EV_P_""" 4 |
… | |
… | |
2732 | This provides the loop \fIparameter\fR for functions, if one is required (\*(L"ev |
2932 | This provides the loop \fIparameter\fR for functions, if one is required (\*(L"ev |
2733 | loop parameter\*(R"). The \f(CW\*(C`EV_P\*(C'\fR form is used when this is the sole parameter, |
2933 | loop parameter\*(R"). The \f(CW\*(C`EV_P\*(C'\fR form is used when this is the sole parameter, |
2734 | \&\f(CW\*(C`EV_P_\*(C'\fR is used when other parameters are following. Example: |
2934 | \&\f(CW\*(C`EV_P_\*(C'\fR is used when other parameters are following. Example: |
2735 | .Sp |
2935 | .Sp |
2736 | .Vb 2 |
2936 | .Vb 2 |
2737 | \& // this is how ev_unref is being declared |
2937 | \& // this is how ev_unref is being declared |
2738 | \& static void ev_unref (EV_P); |
2938 | \& static void ev_unref (EV_P); |
2739 | \& |
2939 | \& |
2740 | \& // this is how you can declare your typical callback |
2940 | \& // this is how you can declare your typical callback |
2741 | \& static void cb (EV_P_ ev_timer *w, int revents) |
2941 | \& static void cb (EV_P_ ev_timer *w, int revents) |
2742 | .Ve |
2942 | .Ve |
2743 | .Sp |
2943 | .Sp |
2744 | It declares a parameter \f(CW\*(C`loop\*(C'\fR of type \f(CW\*(C`struct ev_loop *\*(C'\fR, quite |
2944 | It declares a parameter \f(CW\*(C`loop\*(C'\fR of type \f(CW\*(C`struct ev_loop *\*(C'\fR, quite |
2745 | suitable for use with \f(CW\*(C`EV_A\*(C'\fR. |
2945 | suitable for use with \f(CW\*(C`EV_A\*(C'\fR. |
2746 | .ie n .IP """EV_DEFAULT""\fR, \f(CW""EV_DEFAULT_""" 4 |
2946 | .ie n .IP """EV_DEFAULT""\fR, \f(CW""EV_DEFAULT_""" 4 |
… | |
… | |
2762 | Example: Declare and initialise a check watcher, utilising the above |
2962 | Example: Declare and initialise a check watcher, utilising the above |
2763 | macros so it will work regardless of whether multiple loops are supported |
2963 | macros so it will work regardless of whether multiple loops are supported |
2764 | or not. |
2964 | or not. |
2765 | .PP |
2965 | .PP |
2766 | .Vb 5 |
2966 | .Vb 5 |
2767 | \& static void |
2967 | \& static void |
2768 | \& check_cb (EV_P_ ev_timer *w, int revents) |
2968 | \& check_cb (EV_P_ ev_timer *w, int revents) |
2769 | \& { |
2969 | \& { |
2770 | \& ev_check_stop (EV_A_ w); |
2970 | \& ev_check_stop (EV_A_ w); |
2771 | \& } |
2971 | \& } |
2772 | \& |
2972 | \& |
2773 | \& ev_check check; |
2973 | \& ev_check check; |
2774 | \& ev_check_init (&check, check_cb); |
2974 | \& ev_check_init (&check, check_cb); |
2775 | \& ev_check_start (EV_DEFAULT_ &check); |
2975 | \& ev_check_start (EV_DEFAULT_ &check); |
2776 | \& ev_loop (EV_DEFAULT_ 0); |
2976 | \& ev_loop (EV_DEFAULT_ 0); |
2777 | .Ve |
2977 | .Ve |
2778 | .SH "EMBEDDING" |
2978 | .SH "EMBEDDING" |
2779 | .IX Header "EMBEDDING" |
2979 | .IX Header "EMBEDDING" |
2780 | Libev can (and often is) directly embedded into host |
2980 | Libev can (and often is) directly embedded into host |
2781 | applications. Examples of applications that embed it include the Deliantra |
2981 | applications. Examples of applications that embed it include the Deliantra |
… | |
… | |
2787 | you can easily upgrade by simply copying (or having a checked-out copy of |
2987 | you can easily upgrade by simply copying (or having a checked-out copy of |
2788 | libev somewhere in your source tree). |
2988 | libev somewhere in your source tree). |
2789 | .Sh "\s-1FILESETS\s0" |
2989 | .Sh "\s-1FILESETS\s0" |
2790 | .IX Subsection "FILESETS" |
2990 | .IX Subsection "FILESETS" |
2791 | Depending on what features you need you need to include one or more sets of files |
2991 | Depending on what features you need you need to include one or more sets of files |
2792 | in your app. |
2992 | in your application. |
2793 | .PP |
2993 | .PP |
2794 | \fI\s-1CORE\s0 \s-1EVENT\s0 \s-1LOOP\s0\fR |
2994 | \fI\s-1CORE\s0 \s-1EVENT\s0 \s-1LOOP\s0\fR |
2795 | .IX Subsection "CORE EVENT LOOP" |
2995 | .IX Subsection "CORE EVENT LOOP" |
2796 | .PP |
2996 | .PP |
2797 | To include only the libev core (all the \f(CW\*(C`ev_*\*(C'\fR functions), with manual |
2997 | To include only the libev core (all the \f(CW\*(C`ev_*\*(C'\fR functions), with manual |
2798 | configuration (no autoconf): |
2998 | configuration (no autoconf): |
2799 | .PP |
2999 | .PP |
2800 | .Vb 2 |
3000 | .Vb 2 |
2801 | \& #define EV_STANDALONE 1 |
3001 | \& #define EV_STANDALONE 1 |
2802 | \& #include "ev.c" |
3002 | \& #include "ev.c" |
2803 | .Ve |
3003 | .Ve |
2804 | .PP |
3004 | .PP |
2805 | This will automatically include \fIev.h\fR, too, and should be done in a |
3005 | This will automatically include \fIev.h\fR, too, and should be done in a |
2806 | single C source file only to provide the function implementations. To use |
3006 | single C source file only to provide the function implementations. To use |
2807 | it, do the same for \fIev.h\fR in all files wishing to use this \s-1API\s0 (best |
3007 | it, do the same for \fIev.h\fR in all files wishing to use this \s-1API\s0 (best |
2808 | done by writing a wrapper around \fIev.h\fR that you can include instead and |
3008 | done by writing a wrapper around \fIev.h\fR that you can include instead and |
2809 | where you can put other configuration options): |
3009 | where you can put other configuration options): |
2810 | .PP |
3010 | .PP |
2811 | .Vb 2 |
3011 | .Vb 2 |
2812 | \& #define EV_STANDALONE 1 |
3012 | \& #define EV_STANDALONE 1 |
2813 | \& #include "ev.h" |
3013 | \& #include "ev.h" |
2814 | .Ve |
3014 | .Ve |
2815 | .PP |
3015 | .PP |
2816 | Both header files and implementation files can be compiled with a \*(C+ |
3016 | Both header files and implementation files can be compiled with a \*(C+ |
2817 | compiler (at least, thats a stated goal, and breakage will be treated |
3017 | compiler (at least, thats a stated goal, and breakage will be treated |
2818 | as a bug). |
3018 | as a bug). |
2819 | .PP |
3019 | .PP |
2820 | You need the following files in your source tree, or in a directory |
3020 | You need the following files in your source tree, or in a directory |
2821 | in your include path (e.g. in libev/ when using \-Ilibev): |
3021 | in your include path (e.g. in libev/ when using \-Ilibev): |
2822 | .PP |
3022 | .PP |
2823 | .Vb 4 |
3023 | .Vb 4 |
2824 | \& ev.h |
3024 | \& ev.h |
2825 | \& ev.c |
3025 | \& ev.c |
2826 | \& ev_vars.h |
3026 | \& ev_vars.h |
2827 | \& ev_wrap.h |
3027 | \& ev_wrap.h |
2828 | \& |
3028 | \& |
2829 | \& ev_win32.c required on win32 platforms only |
3029 | \& ev_win32.c required on win32 platforms only |
2830 | \& |
3030 | \& |
2831 | \& ev_select.c only when select backend is enabled (which is enabled by default) |
3031 | \& ev_select.c only when select backend is enabled (which is enabled by default) |
2832 | \& ev_poll.c only when poll backend is enabled (disabled by default) |
3032 | \& ev_poll.c only when poll backend is enabled (disabled by default) |
2833 | \& ev_epoll.c only when the epoll backend is enabled (disabled by default) |
3033 | \& ev_epoll.c only when the epoll backend is enabled (disabled by default) |
2834 | \& ev_kqueue.c only when the kqueue backend is enabled (disabled by default) |
3034 | \& ev_kqueue.c only when the kqueue backend is enabled (disabled by default) |
2835 | \& ev_port.c only when the solaris port backend is enabled (disabled by default) |
3035 | \& ev_port.c only when the solaris port backend is enabled (disabled by default) |
2836 | .Ve |
3036 | .Ve |
2837 | .PP |
3037 | .PP |
2838 | \&\fIev.c\fR includes the backend files directly when enabled, so you only need |
3038 | \&\fIev.c\fR includes the backend files directly when enabled, so you only need |
2839 | to compile this single file. |
3039 | to compile this single file. |
2840 | .PP |
3040 | .PP |
… | |
… | |
2842 | .IX Subsection "LIBEVENT COMPATIBILITY API" |
3042 | .IX Subsection "LIBEVENT COMPATIBILITY API" |
2843 | .PP |
3043 | .PP |
2844 | To include the libevent compatibility \s-1API\s0, also include: |
3044 | To include the libevent compatibility \s-1API\s0, also include: |
2845 | .PP |
3045 | .PP |
2846 | .Vb 1 |
3046 | .Vb 1 |
2847 | \& #include "event.c" |
3047 | \& #include "event.c" |
2848 | .Ve |
3048 | .Ve |
2849 | .PP |
3049 | .PP |
2850 | in the file including \fIev.c\fR, and: |
3050 | in the file including \fIev.c\fR, and: |
2851 | .PP |
3051 | .PP |
2852 | .Vb 1 |
3052 | .Vb 1 |
2853 | \& #include "event.h" |
3053 | \& #include "event.h" |
2854 | .Ve |
3054 | .Ve |
2855 | .PP |
3055 | .PP |
2856 | in the files that want to use the libevent \s-1API\s0. This also includes \fIev.h\fR. |
3056 | in the files that want to use the libevent \s-1API\s0. This also includes \fIev.h\fR. |
2857 | .PP |
3057 | .PP |
2858 | You need the following additional files for this: |
3058 | You need the following additional files for this: |
2859 | .PP |
3059 | .PP |
2860 | .Vb 2 |
3060 | .Vb 2 |
2861 | \& event.h |
3061 | \& event.h |
2862 | \& event.c |
3062 | \& event.c |
2863 | .Ve |
3063 | .Ve |
2864 | .PP |
3064 | .PP |
2865 | \fI\s-1AUTOCONF\s0 \s-1SUPPORT\s0\fR |
3065 | \fI\s-1AUTOCONF\s0 \s-1SUPPORT\s0\fR |
2866 | .IX Subsection "AUTOCONF SUPPORT" |
3066 | .IX Subsection "AUTOCONF SUPPORT" |
2867 | .PP |
3067 | .PP |
2868 | Instead of using \f(CW\*(C`EV_STANDALONE=1\*(C'\fR and providing your config in |
3068 | Instead of using \f(CW\*(C`EV_STANDALONE=1\*(C'\fR and providing your configuration in |
2869 | whatever way you want, you can also \f(CW\*(C`m4_include([libev.m4])\*(C'\fR in your |
3069 | whatever way you want, you can also \f(CW\*(C`m4_include([libev.m4])\*(C'\fR in your |
2870 | \&\fIconfigure.ac\fR and leave \f(CW\*(C`EV_STANDALONE\*(C'\fR undefined. \fIev.c\fR will then |
3070 | \&\fIconfigure.ac\fR and leave \f(CW\*(C`EV_STANDALONE\*(C'\fR undefined. \fIev.c\fR will then |
2871 | include \fIconfig.h\fR and configure itself accordingly. |
3071 | include \fIconfig.h\fR and configure itself accordingly. |
2872 | .PP |
3072 | .PP |
2873 | For this of course you need the m4 file: |
3073 | For this of course you need the m4 file: |
2874 | .PP |
3074 | .PP |
2875 | .Vb 1 |
3075 | .Vb 1 |
2876 | \& libev.m4 |
3076 | \& libev.m4 |
2877 | .Ve |
3077 | .Ve |
2878 | .Sh "\s-1PREPROCESSOR\s0 \s-1SYMBOLS/MACROS\s0" |
3078 | .Sh "\s-1PREPROCESSOR\s0 \s-1SYMBOLS/MACROS\s0" |
2879 | .IX Subsection "PREPROCESSOR SYMBOLS/MACROS" |
3079 | .IX Subsection "PREPROCESSOR SYMBOLS/MACROS" |
2880 | Libev can be configured via a variety of preprocessor symbols you have to |
3080 | Libev can be configured via a variety of preprocessor symbols you have to |
2881 | define before including any of its files. The default in the absense of |
3081 | define before including any of its files. The default in the absence of |
2882 | autoconf is noted for every option. |
3082 | autoconf is documented for every option. |
2883 | .IP "\s-1EV_STANDALONE\s0" 4 |
3083 | .IP "\s-1EV_STANDALONE\s0" 4 |
2884 | .IX Item "EV_STANDALONE" |
3084 | .IX Item "EV_STANDALONE" |
2885 | Must always be \f(CW1\fR if you do not use autoconf configuration, which |
3085 | Must always be \f(CW1\fR if you do not use autoconf configuration, which |
2886 | keeps libev from including \fIconfig.h\fR, and it also defines dummy |
3086 | keeps libev from including \fIconfig.h\fR, and it also defines dummy |
2887 | implementations for some libevent functions (such as logging, which is not |
3087 | implementations for some libevent functions (such as logging, which is not |
2888 | supported). It will also not define any of the structs usually found in |
3088 | supported). It will also not define any of the structs usually found in |
2889 | \&\fIevent.h\fR that are not directly supported by the libev core alone. |
3089 | \&\fIevent.h\fR that are not directly supported by the libev core alone. |
2890 | .IP "\s-1EV_USE_MONOTONIC\s0" 4 |
3090 | .IP "\s-1EV_USE_MONOTONIC\s0" 4 |
2891 | .IX Item "EV_USE_MONOTONIC" |
3091 | .IX Item "EV_USE_MONOTONIC" |
2892 | If defined to be \f(CW1\fR, libev will try to detect the availability of the |
3092 | If defined to be \f(CW1\fR, libev will try to detect the availability of the |
2893 | monotonic clock option at both compiletime and runtime. Otherwise no use |
3093 | monotonic clock option at both compile time and runtime. Otherwise no use |
2894 | of the monotonic clock option will be attempted. If you enable this, you |
3094 | of the monotonic clock option will be attempted. If you enable this, you |
2895 | usually have to link against librt or something similar. Enabling it when |
3095 | usually have to link against librt or something similar. Enabling it when |
2896 | the functionality isn't available is safe, though, although you have |
3096 | the functionality isn't available is safe, though, although you have |
2897 | to make sure you link against any libraries where the \f(CW\*(C`clock_gettime\*(C'\fR |
3097 | to make sure you link against any libraries where the \f(CW\*(C`clock_gettime\*(C'\fR |
2898 | function is hiding in (often \fI\-lrt\fR). |
3098 | function is hiding in (often \fI\-lrt\fR). |
2899 | .IP "\s-1EV_USE_REALTIME\s0" 4 |
3099 | .IP "\s-1EV_USE_REALTIME\s0" 4 |
2900 | .IX Item "EV_USE_REALTIME" |
3100 | .IX Item "EV_USE_REALTIME" |
2901 | If defined to be \f(CW1\fR, libev will try to detect the availability of the |
3101 | If defined to be \f(CW1\fR, libev will try to detect the availability of the |
2902 | realtime clock option at compiletime (and assume its availability at |
3102 | real-time clock option at compile time (and assume its availability at |
2903 | runtime if successful). Otherwise no use of the realtime clock option will |
3103 | runtime if successful). Otherwise no use of the real-time clock option will |
2904 | be attempted. This effectively replaces \f(CW\*(C`gettimeofday\*(C'\fR by \f(CW\*(C`clock_get |
3104 | be attempted. This effectively replaces \f(CW\*(C`gettimeofday\*(C'\fR by \f(CW\*(C`clock_get |
2905 | (CLOCK_REALTIME, ...)\*(C'\fR and will not normally affect correctness. See the |
3105 | (CLOCK_REALTIME, ...)\*(C'\fR and will not normally affect correctness. See the |
2906 | note about libraries in the description of \f(CW\*(C`EV_USE_MONOTONIC\*(C'\fR, though. |
3106 | note about libraries in the description of \f(CW\*(C`EV_USE_MONOTONIC\*(C'\fR, though. |
2907 | .IP "\s-1EV_USE_NANOSLEEP\s0" 4 |
3107 | .IP "\s-1EV_USE_NANOSLEEP\s0" 4 |
2908 | .IX Item "EV_USE_NANOSLEEP" |
3108 | .IX Item "EV_USE_NANOSLEEP" |
… | |
… | |
2916 | If undefined, it will be enabled if the headers indicate GNU/Linux + Glibc |
3116 | If undefined, it will be enabled if the headers indicate GNU/Linux + Glibc |
2917 | 2.7 or newer, otherwise disabled. |
3117 | 2.7 or newer, otherwise disabled. |
2918 | .IP "\s-1EV_USE_SELECT\s0" 4 |
3118 | .IP "\s-1EV_USE_SELECT\s0" 4 |
2919 | .IX Item "EV_USE_SELECT" |
3119 | .IX Item "EV_USE_SELECT" |
2920 | If undefined or defined to be \f(CW1\fR, libev will compile in support for the |
3120 | If undefined or defined to be \f(CW1\fR, libev will compile in support for the |
2921 | \&\f(CW\*(C`select\*(C'\fR(2) backend. No attempt at autodetection will be done: if no |
3121 | \&\f(CW\*(C`select\*(C'\fR(2) backend. No attempt at auto-detection will be done: if no |
2922 | other method takes over, select will be it. Otherwise the select backend |
3122 | other method takes over, select will be it. Otherwise the select backend |
2923 | will not be compiled in. |
3123 | will not be compiled in. |
2924 | .IP "\s-1EV_SELECT_USE_FD_SET\s0" 4 |
3124 | .IP "\s-1EV_SELECT_USE_FD_SET\s0" 4 |
2925 | .IX Item "EV_SELECT_USE_FD_SET" |
3125 | .IX Item "EV_SELECT_USE_FD_SET" |
2926 | If defined to \f(CW1\fR, then the select backend will use the system \f(CW\*(C`fd_set\*(C'\fR |
3126 | If defined to \f(CW1\fR, then the select backend will use the system \f(CW\*(C`fd_set\*(C'\fR |
2927 | structure. This is useful if libev doesn't compile due to a missing |
3127 | structure. This is useful if libev doesn't compile due to a missing |
2928 | \&\f(CW\*(C`NFDBITS\*(C'\fR or \f(CW\*(C`fd_mask\*(C'\fR definition or it misguesses the bitset layout on |
3128 | \&\f(CW\*(C`NFDBITS\*(C'\fR or \f(CW\*(C`fd_mask\*(C'\fR definition or it mis-guesses the bitset layout on |
2929 | exotic systems. This usually limits the range of file descriptors to some |
3129 | exotic systems. This usually limits the range of file descriptors to some |
2930 | low limit such as 1024 or might have other limitations (winsocket only |
3130 | low limit such as 1024 or might have other limitations (winsocket only |
2931 | allows 64 sockets). The \f(CW\*(C`FD_SETSIZE\*(C'\fR macro, set before compilation, might |
3131 | allows 64 sockets). The \f(CW\*(C`FD_SETSIZE\*(C'\fR macro, set before compilation, might |
2932 | influence the size of the \f(CW\*(C`fd_set\*(C'\fR used. |
3132 | influence the size of the \f(CW\*(C`fd_set\*(C'\fR used. |
2933 | .IP "\s-1EV_SELECT_IS_WINSOCKET\s0" 4 |
3133 | .IP "\s-1EV_SELECT_IS_WINSOCKET\s0" 4 |
… | |
… | |
2975 | 10 port style backend. Its availability will be detected at runtime, |
3175 | 10 port style backend. Its availability will be detected at runtime, |
2976 | otherwise another method will be used as fallback. This is the preferred |
3176 | otherwise another method will be used as fallback. This is the preferred |
2977 | backend for Solaris 10 systems. |
3177 | backend for Solaris 10 systems. |
2978 | .IP "\s-1EV_USE_DEVPOLL\s0" 4 |
3178 | .IP "\s-1EV_USE_DEVPOLL\s0" 4 |
2979 | .IX Item "EV_USE_DEVPOLL" |
3179 | .IX Item "EV_USE_DEVPOLL" |
2980 | reserved for future expansion, works like the \s-1USE\s0 symbols above. |
3180 | Reserved for future expansion, works like the \s-1USE\s0 symbols above. |
2981 | .IP "\s-1EV_USE_INOTIFY\s0" 4 |
3181 | .IP "\s-1EV_USE_INOTIFY\s0" 4 |
2982 | .IX Item "EV_USE_INOTIFY" |
3182 | .IX Item "EV_USE_INOTIFY" |
2983 | If defined to be \f(CW1\fR, libev will compile in support for the Linux inotify |
3183 | If defined to be \f(CW1\fR, libev will compile in support for the Linux inotify |
2984 | interface to speed up \f(CW\*(C`ev_stat\*(C'\fR watchers. Its actual availability will |
3184 | interface to speed up \f(CW\*(C`ev_stat\*(C'\fR watchers. Its actual availability will |
2985 | be detected at runtime. If undefined, it will be enabled if the headers |
3185 | be detected at runtime. If undefined, it will be enabled if the headers |
… | |
… | |
2990 | access is atomic with respect to other threads or signal contexts. No such |
3190 | access is atomic with respect to other threads or signal contexts. No such |
2991 | type is easily found in the C language, so you can provide your own type |
3191 | type is easily found in the C language, so you can provide your own type |
2992 | that you know is safe for your purposes. It is used both for signal handler \*(L"locking\*(R" |
3192 | that you know is safe for your purposes. It is used both for signal handler \*(L"locking\*(R" |
2993 | as well as for signal and thread safety in \f(CW\*(C`ev_async\*(C'\fR watchers. |
3193 | as well as for signal and thread safety in \f(CW\*(C`ev_async\*(C'\fR watchers. |
2994 | .Sp |
3194 | .Sp |
2995 | In the absense of this define, libev will use \f(CW\*(C`sig_atomic_t volatile\*(C'\fR |
3195 | In the absence of this define, libev will use \f(CW\*(C`sig_atomic_t volatile\*(C'\fR |
2996 | (from \fIsignal.h\fR), which is usually good enough on most platforms. |
3196 | (from \fIsignal.h\fR), which is usually good enough on most platforms. |
2997 | .IP "\s-1EV_H\s0" 4 |
3197 | .IP "\s-1EV_H\s0" 4 |
2998 | .IX Item "EV_H" |
3198 | .IX Item "EV_H" |
2999 | The name of the \fIev.h\fR header file used to include it. The default if |
3199 | The name of the \fIev.h\fR header file used to include it. The default if |
3000 | undefined is \f(CW"ev.h"\fR in \fIevent.h\fR, \fIev.c\fR and \fIev++.h\fR. This can be |
3200 | undefined is \f(CW"ev.h"\fR in \fIevent.h\fR, \fIev.c\fR and \fIev++.h\fR. This can be |
… | |
… | |
3035 | When doing priority-based operations, libev usually has to linearly search |
3235 | When doing priority-based operations, libev usually has to linearly search |
3036 | all the priorities, so having many of them (hundreds) uses a lot of space |
3236 | all the priorities, so having many of them (hundreds) uses a lot of space |
3037 | and time, so using the defaults of five priorities (\-2 .. +2) is usually |
3237 | and time, so using the defaults of five priorities (\-2 .. +2) is usually |
3038 | fine. |
3238 | fine. |
3039 | .Sp |
3239 | .Sp |
3040 | If your embedding app does not need any priorities, defining these both to |
3240 | If your embedding application does not need any priorities, defining these |
3041 | \&\f(CW0\fR will save some memory and cpu. |
3241 | both to \f(CW0\fR will save some memory and \s-1CPU\s0. |
3042 | .IP "\s-1EV_PERIODIC_ENABLE\s0" 4 |
3242 | .IP "\s-1EV_PERIODIC_ENABLE\s0" 4 |
3043 | .IX Item "EV_PERIODIC_ENABLE" |
3243 | .IX Item "EV_PERIODIC_ENABLE" |
3044 | If undefined or defined to be \f(CW1\fR, then periodic timers are supported. If |
3244 | If undefined or defined to be \f(CW1\fR, then periodic timers are supported. If |
3045 | defined to be \f(CW0\fR, then they are not. Disabling them saves a few kB of |
3245 | defined to be \f(CW0\fR, then they are not. Disabling them saves a few kB of |
3046 | code. |
3246 | code. |
… | |
… | |
3050 | defined to be \f(CW0\fR, then they are not. Disabling them saves a few kB of |
3250 | defined to be \f(CW0\fR, then they are not. Disabling them saves a few kB of |
3051 | code. |
3251 | code. |
3052 | .IP "\s-1EV_EMBED_ENABLE\s0" 4 |
3252 | .IP "\s-1EV_EMBED_ENABLE\s0" 4 |
3053 | .IX Item "EV_EMBED_ENABLE" |
3253 | .IX Item "EV_EMBED_ENABLE" |
3054 | If undefined or defined to be \f(CW1\fR, then embed watchers are supported. If |
3254 | If undefined or defined to be \f(CW1\fR, then embed watchers are supported. If |
3055 | defined to be \f(CW0\fR, then they are not. |
3255 | defined to be \f(CW0\fR, then they are not. Embed watchers rely on most other |
|
|
3256 | watcher types, which therefore must not be disabled. |
3056 | .IP "\s-1EV_STAT_ENABLE\s0" 4 |
3257 | .IP "\s-1EV_STAT_ENABLE\s0" 4 |
3057 | .IX Item "EV_STAT_ENABLE" |
3258 | .IX Item "EV_STAT_ENABLE" |
3058 | If undefined or defined to be \f(CW1\fR, then stat watchers are supported. If |
3259 | If undefined or defined to be \f(CW1\fR, then stat watchers are supported. If |
3059 | defined to be \f(CW0\fR, then they are not. |
3260 | defined to be \f(CW0\fR, then they are not. |
3060 | .IP "\s-1EV_FORK_ENABLE\s0" 4 |
3261 | .IP "\s-1EV_FORK_ENABLE\s0" 4 |
… | |
… | |
3067 | defined to be \f(CW0\fR, then they are not. |
3268 | defined to be \f(CW0\fR, then they are not. |
3068 | .IP "\s-1EV_MINIMAL\s0" 4 |
3269 | .IP "\s-1EV_MINIMAL\s0" 4 |
3069 | .IX Item "EV_MINIMAL" |
3270 | .IX Item "EV_MINIMAL" |
3070 | If you need to shave off some kilobytes of code at the expense of some |
3271 | If you need to shave off some kilobytes of code at the expense of some |
3071 | speed, define this symbol to \f(CW1\fR. Currently this is used to override some |
3272 | speed, define this symbol to \f(CW1\fR. Currently this is used to override some |
3072 | inlining decisions, saves roughly 30% codesize of amd64. It also selects a |
3273 | inlining decisions, saves roughly 30% code size on amd64. It also selects a |
3073 | much smaller 2\-heap for timer management over the default 4\-heap. |
3274 | much smaller 2\-heap for timer management over the default 4\-heap. |
3074 | .IP "\s-1EV_PID_HASHSIZE\s0" 4 |
3275 | .IP "\s-1EV_PID_HASHSIZE\s0" 4 |
3075 | .IX Item "EV_PID_HASHSIZE" |
3276 | .IX Item "EV_PID_HASHSIZE" |
3076 | \&\f(CW\*(C`ev_child\*(C'\fR watchers use a small hash table to distribute workload by |
3277 | \&\f(CW\*(C`ev_child\*(C'\fR watchers use a small hash table to distribute workload by |
3077 | pid. The default size is \f(CW16\fR (or \f(CW1\fR with \f(CW\*(C`EV_MINIMAL\*(C'\fR), usually more |
3278 | pid. The default size is \f(CW16\fR (or \f(CW1\fR with \f(CW\*(C`EV_MINIMAL\*(C'\fR), usually more |
… | |
… | |
3085 | watchers you might want to increase this value (\fImust\fR be a power of |
3286 | watchers you might want to increase this value (\fImust\fR be a power of |
3086 | two). |
3287 | two). |
3087 | .IP "\s-1EV_USE_4HEAP\s0" 4 |
3288 | .IP "\s-1EV_USE_4HEAP\s0" 4 |
3088 | .IX Item "EV_USE_4HEAP" |
3289 | .IX Item "EV_USE_4HEAP" |
3089 | Heaps are not very cache-efficient. To improve the cache-efficiency of the |
3290 | Heaps are not very cache-efficient. To improve the cache-efficiency of the |
3090 | timer and periodics heap, libev uses a 4\-heap when this symbol is defined |
3291 | timer and periodics heaps, libev uses a 4\-heap when this symbol is defined |
3091 | to \f(CW1\fR. The 4\-heap uses more complicated (longer) code but has a |
3292 | to \f(CW1\fR. The 4\-heap uses more complicated (longer) code but has noticeably |
3092 | noticable after performance with many (thousands) of watchers. |
3293 | faster performance with many (thousands) of watchers. |
3093 | .Sp |
3294 | .Sp |
3094 | The default is \f(CW1\fR unless \f(CW\*(C`EV_MINIMAL\*(C'\fR is set in which case it is \f(CW0\fR |
3295 | The default is \f(CW1\fR unless \f(CW\*(C`EV_MINIMAL\*(C'\fR is set in which case it is \f(CW0\fR |
3095 | (disabled). |
3296 | (disabled). |
3096 | .IP "\s-1EV_HEAP_CACHE_AT\s0" 4 |
3297 | .IP "\s-1EV_HEAP_CACHE_AT\s0" 4 |
3097 | .IX Item "EV_HEAP_CACHE_AT" |
3298 | .IX Item "EV_HEAP_CACHE_AT" |
3098 | Heaps are not very cache-efficient. To improve the cache-efficiency of the |
3299 | Heaps are not very cache-efficient. To improve the cache-efficiency of the |
3099 | timer and periodics heap, libev can cache the timestamp (\fIat\fR) within |
3300 | timer and periodics heaps, libev can cache the timestamp (\fIat\fR) within |
3100 | the heap structure (selected by defining \f(CW\*(C`EV_HEAP_CACHE_AT\*(C'\fR to \f(CW1\fR), |
3301 | the heap structure (selected by defining \f(CW\*(C`EV_HEAP_CACHE_AT\*(C'\fR to \f(CW1\fR), |
3101 | which uses 8\-12 bytes more per watcher and a few hundred bytes more code, |
3302 | which uses 8\-12 bytes more per watcher and a few hundred bytes more code, |
3102 | but avoids random read accesses on heap changes. This noticably improves |
3303 | but avoids random read accesses on heap changes. This improves performance |
3103 | performance noticably with with many (hundreds) of watchers. |
3304 | noticeably with many (hundreds) of watchers. |
3104 | .Sp |
3305 | .Sp |
3105 | The default is \f(CW1\fR unless \f(CW\*(C`EV_MINIMAL\*(C'\fR is set in which case it is \f(CW0\fR |
3306 | The default is \f(CW1\fR unless \f(CW\*(C`EV_MINIMAL\*(C'\fR is set in which case it is \f(CW0\fR |
3106 | (disabled). |
3307 | (disabled). |
|
|
3308 | .IP "\s-1EV_VERIFY\s0" 4 |
|
|
3309 | .IX Item "EV_VERIFY" |
|
|
3310 | Controls how much internal verification (see \f(CW\*(C`ev_loop_verify ()\*(C'\fR) will |
|
|
3311 | be done: If set to \f(CW0\fR, no internal verification code will be compiled |
|
|
3312 | in. If set to \f(CW1\fR, then verification code will be compiled in, but not |
|
|
3313 | called. If set to \f(CW2\fR, then the internal verification code will be |
|
|
3314 | called once per loop, which can slow down libev. If set to \f(CW3\fR, then the |
|
|
3315 | verification code will be called very frequently, which will slow down |
|
|
3316 | libev considerably. |
|
|
3317 | .Sp |
|
|
3318 | The default is \f(CW1\fR, unless \f(CW\*(C`EV_MINIMAL\*(C'\fR is set, in which case it will be |
|
|
3319 | \&\f(CW0\fR. |
3107 | .IP "\s-1EV_COMMON\s0" 4 |
3320 | .IP "\s-1EV_COMMON\s0" 4 |
3108 | .IX Item "EV_COMMON" |
3321 | .IX Item "EV_COMMON" |
3109 | By default, all watchers have a \f(CW\*(C`void *data\*(C'\fR member. By redefining |
3322 | By default, all watchers have a \f(CW\*(C`void *data\*(C'\fR member. By redefining |
3110 | this macro to a something else you can include more and other types of |
3323 | this macro to a something else you can include more and other types of |
3111 | members. You have to define it each time you include one of the files, |
3324 | members. You have to define it each time you include one of the files, |
3112 | though, and it must be identical each time. |
3325 | though, and it must be identical each time. |
3113 | .Sp |
3326 | .Sp |
3114 | For example, the perl \s-1EV\s0 module uses something like this: |
3327 | For example, the perl \s-1EV\s0 module uses something like this: |
3115 | .Sp |
3328 | .Sp |
3116 | .Vb 3 |
3329 | .Vb 3 |
3117 | \& #define EV_COMMON \e |
3330 | \& #define EV_COMMON \e |
3118 | \& SV *self; /* contains this struct */ \e |
3331 | \& SV *self; /* contains this struct */ \e |
3119 | \& SV *cb_sv, *fh /* note no trailing ";" */ |
3332 | \& SV *cb_sv, *fh /* note no trailing ";" */ |
3120 | .Ve |
3333 | .Ve |
3121 | .IP "\s-1EV_CB_DECLARE\s0 (type)" 4 |
3334 | .IP "\s-1EV_CB_DECLARE\s0 (type)" 4 |
3122 | .IX Item "EV_CB_DECLARE (type)" |
3335 | .IX Item "EV_CB_DECLARE (type)" |
3123 | .PD 0 |
3336 | .PD 0 |
3124 | .IP "\s-1EV_CB_INVOKE\s0 (watcher, revents)" 4 |
3337 | .IP "\s-1EV_CB_INVOKE\s0 (watcher, revents)" 4 |
… | |
… | |
3132 | their default definitions. One possible use for overriding these is to |
3345 | their default definitions. One possible use for overriding these is to |
3133 | avoid the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument in all cases, or to use |
3346 | avoid the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument in all cases, or to use |
3134 | method calls instead of plain function calls in \*(C+. |
3347 | method calls instead of plain function calls in \*(C+. |
3135 | .Sh "\s-1EXPORTED\s0 \s-1API\s0 \s-1SYMBOLS\s0" |
3348 | .Sh "\s-1EXPORTED\s0 \s-1API\s0 \s-1SYMBOLS\s0" |
3136 | .IX Subsection "EXPORTED API SYMBOLS" |
3349 | .IX Subsection "EXPORTED API SYMBOLS" |
3137 | If you need to re-export the \s-1API\s0 (e.g. via a dll) and you need a list of |
3350 | If you need to re-export the \s-1API\s0 (e.g. via a \s-1DLL\s0) and you need a list of |
3138 | exported symbols, you can use the provided \fISymbol.*\fR files which list |
3351 | exported symbols, you can use the provided \fISymbol.*\fR files which list |
3139 | all public symbols, one per line: |
3352 | all public symbols, one per line: |
3140 | .PP |
3353 | .PP |
3141 | .Vb 2 |
3354 | .Vb 2 |
3142 | \& Symbols.ev for libev proper |
3355 | \& Symbols.ev for libev proper |
3143 | \& Symbols.event for the libevent emulation |
3356 | \& Symbols.event for the libevent emulation |
3144 | .Ve |
3357 | .Ve |
3145 | .PP |
3358 | .PP |
3146 | This can also be used to rename all public symbols to avoid clashes with |
3359 | This can also be used to rename all public symbols to avoid clashes with |
3147 | multiple versions of libev linked together (which is obviously bad in |
3360 | multiple versions of libev linked together (which is obviously bad in |
3148 | itself, but sometimes it is inconvinient to avoid this). |
3361 | itself, but sometimes it is inconvenient to avoid this). |
3149 | .PP |
3362 | .PP |
3150 | A sed command like this will create wrapper \f(CW\*(C`#define\*(C'\fR's that you need to |
3363 | A sed command like this will create wrapper \f(CW\*(C`#define\*(C'\fR's that you need to |
3151 | include before including \fIev.h\fR: |
3364 | include before including \fIev.h\fR: |
3152 | .PP |
3365 | .PP |
3153 | .Vb 1 |
3366 | .Vb 1 |
… | |
… | |
3174 | .PP |
3387 | .PP |
3175 | The usage in rxvt-unicode is simpler. It has a \fIev_cpp.h\fR header file |
3388 | The usage in rxvt-unicode is simpler. It has a \fIev_cpp.h\fR header file |
3176 | that everybody includes and which overrides some configure choices: |
3389 | that everybody includes and which overrides some configure choices: |
3177 | .PP |
3390 | .PP |
3178 | .Vb 9 |
3391 | .Vb 9 |
3179 | \& #define EV_MINIMAL 1 |
3392 | \& #define EV_MINIMAL 1 |
3180 | \& #define EV_USE_POLL 0 |
3393 | \& #define EV_USE_POLL 0 |
3181 | \& #define EV_MULTIPLICITY 0 |
3394 | \& #define EV_MULTIPLICITY 0 |
3182 | \& #define EV_PERIODIC_ENABLE 0 |
3395 | \& #define EV_PERIODIC_ENABLE 0 |
3183 | \& #define EV_STAT_ENABLE 0 |
3396 | \& #define EV_STAT_ENABLE 0 |
3184 | \& #define EV_FORK_ENABLE 0 |
3397 | \& #define EV_FORK_ENABLE 0 |
3185 | \& #define EV_CONFIG_H <config.h> |
3398 | \& #define EV_CONFIG_H <config.h> |
3186 | \& #define EV_MINPRI 0 |
3399 | \& #define EV_MINPRI 0 |
3187 | \& #define EV_MAXPRI 0 |
3400 | \& #define EV_MAXPRI 0 |
3188 | \& |
3401 | \& |
3189 | \& #include "ev++.h" |
3402 | \& #include "ev++.h" |
3190 | .Ve |
3403 | .Ve |
3191 | .PP |
3404 | .PP |
3192 | And a \fIev_cpp.C\fR implementation file that contains libev proper and is compiled: |
3405 | And a \fIev_cpp.C\fR implementation file that contains libev proper and is compiled: |
3193 | .PP |
3406 | .PP |
3194 | .Vb 2 |
3407 | .Vb 2 |
3195 | \& #include "ev_cpp.h" |
3408 | \& #include "ev_cpp.h" |
3196 | \& #include "ev.c" |
3409 | \& #include "ev.c" |
3197 | .Ve |
3410 | .Ve |
3198 | .SH "THREADS AND COROUTINES" |
3411 | .SH "INTERACTION WITH OTHER PROGRAMS OR LIBRARIES" |
|
|
3412 | .IX Header "INTERACTION WITH OTHER PROGRAMS OR LIBRARIES" |
|
|
3413 | .Sh "\s-1THREADS\s0 \s-1AND\s0 \s-1COROUTINES\s0" |
3199 | .IX Header "THREADS AND COROUTINES" |
3414 | .IX Subsection "THREADS AND COROUTINES" |
3200 | .Sh "\s-1THREADS\s0" |
3415 | \fI\s-1THREADS\s0\fR |
3201 | .IX Subsection "THREADS" |
3416 | .IX Subsection "THREADS" |
3202 | Libev itself is completely threadsafe, but it uses no locking. This |
3417 | .PP |
|
|
3418 | All libev functions are reentrant and thread-safe unless explicitly |
|
|
3419 | documented otherwise, but libev implements no locking itself. This means |
3203 | means that you can use as many loops as you want in parallel, as long as |
3420 | that you can use as many loops as you want in parallel, as long as there |
3204 | only one thread ever calls into one libev function with the same loop |
3421 | are no concurrent calls into any libev function with the same loop |
3205 | parameter. |
3422 | parameter (\f(CW\*(C`ev_default_*\*(C'\fR calls have an implicit default loop parameter, |
|
|
3423 | of course): libev guarantees that different event loops share no data |
|
|
3424 | structures that need any locking. |
3206 | .PP |
3425 | .PP |
3207 | Or put differently: calls with different loop parameters can be done in |
3426 | Or to put it differently: calls with different loop parameters can be done |
3208 | parallel from multiple threads, calls with the same loop parameter must be |
3427 | concurrently from multiple threads, calls with the same loop parameter |
3209 | done serially (but can be done from different threads, as long as only one |
3428 | must be done serially (but can be done from different threads, as long as |
3210 | thread ever is inside a call at any point in time, e.g. by using a mutex |
3429 | only one thread ever is inside a call at any point in time, e.g. by using |
3211 | per loop). |
3430 | a mutex per loop). |
3212 | .PP |
3431 | .PP |
3213 | If you want to know which design is best for your problem, then I cannot |
3432 | Specifically to support threads (and signal handlers), libev implements |
|
|
3433 | so-called \f(CW\*(C`ev_async\*(C'\fR watchers, which allow some limited form of |
|
|
3434 | concurrency on the same event loop, namely waking it up \*(L"from the |
|
|
3435 | outside\*(R". |
|
|
3436 | .PP |
|
|
3437 | If you want to know which design (one loop, locking, or multiple loops |
|
|
3438 | without or something else still) is best for your problem, then I cannot |
3214 | help you but by giving some generic advice: |
3439 | help you, but here is some generic advice: |
3215 | .IP "\(bu" 4 |
3440 | .IP "\(bu" 4 |
3216 | most applications have a main thread: use the default libev loop |
3441 | most applications have a main thread: use the default libev loop |
3217 | in that thread, or create a seperate thread running only the default loop. |
3442 | in that thread, or create a separate thread running only the default loop. |
3218 | .Sp |
3443 | .Sp |
3219 | This helps integrating other libraries or software modules that use libev |
3444 | This helps integrating other libraries or software modules that use libev |
3220 | themselves and don't care/know about threading. |
3445 | themselves and don't care/know about threading. |
3221 | .IP "\(bu" 4 |
3446 | .IP "\(bu" 4 |
3222 | one loop per thread is usually a good model. |
3447 | one loop per thread is usually a good model. |
3223 | .Sp |
3448 | .Sp |
3224 | Doing this is almost never wrong, sometimes a better-performance model |
3449 | Doing this is almost never wrong, sometimes a better-performance model |
3225 | exists, but it is always a good start. |
3450 | exists, but it is always a good start. |
3226 | .IP "\(bu" 4 |
3451 | .IP "\(bu" 4 |
3227 | other models exist, such as the leader/follower pattern, where one |
3452 | other models exist, such as the leader/follower pattern, where one |
3228 | loop is handed through multiple threads in a kind of round-robbin fashion. |
3453 | loop is handed through multiple threads in a kind of round-robin fashion. |
3229 | .Sp |
3454 | .Sp |
3230 | Chosing a model is hard \- look around, learn, know that usually you cna do |
3455 | Choosing a model is hard \- look around, learn, know that usually you can do |
3231 | better than you currently do :\-) |
3456 | better than you currently do :\-) |
3232 | .IP "\(bu" 4 |
3457 | .IP "\(bu" 4 |
3233 | often you need to talk to some other thread which blocks in the |
3458 | often you need to talk to some other thread which blocks in the |
|
|
3459 | event loop. |
|
|
3460 | .Sp |
3234 | event loop \- \f(CW\*(C`ev_async\*(C'\fR watchers can be used to wake them up from other |
3461 | \&\f(CW\*(C`ev_async\*(C'\fR watchers can be used to wake them up from other threads safely |
3235 | threads safely (or from signal contexts...). |
3462 | (or from signal contexts...). |
3236 | .Sh "\s-1COROUTINES\s0" |
3463 | .Sp |
|
|
3464 | An example use would be to communicate signals or other events that only |
|
|
3465 | work in the default loop by registering the signal watcher with the |
|
|
3466 | default loop and triggering an \f(CW\*(C`ev_async\*(C'\fR watcher from the default loop |
|
|
3467 | watcher callback into the event loop interested in the signal. |
|
|
3468 | .PP |
|
|
3469 | \fI\s-1COROUTINES\s0\fR |
3237 | .IX Subsection "COROUTINES" |
3470 | .IX Subsection "COROUTINES" |
|
|
3471 | .PP |
3238 | Libev is much more accomodating to coroutines (\*(L"cooperative threads\*(R"): |
3472 | Libev is very accommodating to coroutines (\*(L"cooperative threads\*(R"): |
3239 | libev fully supports nesting calls to it's functions from different |
3473 | libev fully supports nesting calls to its functions from different |
3240 | coroutines (e.g. you can call \f(CW\*(C`ev_loop\*(C'\fR on the same loop from two |
3474 | coroutines (e.g. you can call \f(CW\*(C`ev_loop\*(C'\fR on the same loop from two |
3241 | different coroutines and switch freely between both coroutines running the |
3475 | different coroutines, and switch freely between both coroutines running the |
3242 | loop, as long as you don't confuse yourself). The only exception is that |
3476 | loop, as long as you don't confuse yourself). The only exception is that |
3243 | you must not do this from \f(CW\*(C`ev_periodic\*(C'\fR reschedule callbacks. |
3477 | you must not do this from \f(CW\*(C`ev_periodic\*(C'\fR reschedule callbacks. |
3244 | .PP |
3478 | .PP |
3245 | Care has been invested into making sure that libev does not keep local |
3479 | Care has been taken to ensure that libev does not keep local state inside |
3246 | state inside \f(CW\*(C`ev_loop\*(C'\fR, and other calls do not usually allow coroutine |
3480 | \&\f(CW\*(C`ev_loop\*(C'\fR, and other calls do not usually allow for coroutine switches as |
3247 | switches. |
3481 | they do not clal any callbacks. |
3248 | .SH "COMPLEXITIES" |
3482 | .Sh "\s-1COMPILER\s0 \s-1WARNINGS\s0" |
3249 | .IX Header "COMPLEXITIES" |
3483 | .IX Subsection "COMPILER WARNINGS" |
3250 | In this section the complexities of (many of) the algorithms used inside |
3484 | Depending on your compiler and compiler settings, you might get no or a |
3251 | libev will be explained. For complexity discussions about backends see the |
3485 | lot of warnings when compiling libev code. Some people are apparently |
3252 | documentation for \f(CW\*(C`ev_default_init\*(C'\fR. |
3486 | scared by this. |
3253 | .PP |
3487 | .PP |
3254 | All of the following are about amortised time: If an array needs to be |
3488 | However, these are unavoidable for many reasons. For one, each compiler |
3255 | extended, libev needs to realloc and move the whole array, but this |
3489 | has different warnings, and each user has different tastes regarding |
3256 | happens asymptotically never with higher number of elements, so O(1) might |
3490 | warning options. \*(L"Warn-free\*(R" code therefore cannot be a goal except when |
3257 | mean it might do a lengthy realloc operation in rare cases, but on average |
3491 | targeting a specific compiler and compiler-version. |
3258 | it is much faster and asymptotically approaches constant time. |
3492 | .PP |
3259 | .IP "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" 4 |
3493 | Another reason is that some compiler warnings require elaborate |
3260 | .IX Item "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" |
3494 | workarounds, or other changes to the code that make it less clear and less |
3261 | This means that, when you have a watcher that triggers in one hour and |
3495 | maintainable. |
3262 | there are 100 watchers that would trigger before that then inserting will |
3496 | .PP |
3263 | have to skip roughly seven (\f(CW\*(C`ld 100\*(C'\fR) of these watchers. |
3497 | And of course, some compiler warnings are just plain stupid, or simply |
3264 | .IP "Changing timer/periodic watchers (by autorepeat or calling again): O(log skipped_other_timers)" 4 |
3498 | wrong (because they don't actually warn about the condition their message |
3265 | .IX Item "Changing timer/periodic watchers (by autorepeat or calling again): O(log skipped_other_timers)" |
3499 | seems to warn about). For example, certain older gcc versions had some |
3266 | That means that changing a timer costs less than removing/adding them |
3500 | warnings that resulted an extreme number of false positives. These have |
3267 | as only the relative motion in the event queue has to be paid for. |
3501 | been fixed, but some people still insist on making code warn-free with |
3268 | .IP "Starting io/check/prepare/idle/signal/child/fork/async watchers: O(1)" 4 |
3502 | such buggy versions. |
3269 | .IX Item "Starting io/check/prepare/idle/signal/child/fork/async watchers: O(1)" |
3503 | .PP |
3270 | These just add the watcher into an array or at the head of a list. |
3504 | While libev is written to generate as few warnings as possible, |
3271 | .IP "Stopping check/prepare/idle/fork/async watchers: O(1)" 4 |
3505 | \&\*(L"warn-free\*(R" code is not a goal, and it is recommended not to build libev |
3272 | .IX Item "Stopping check/prepare/idle/fork/async watchers: O(1)" |
3506 | with any compiler warnings enabled unless you are prepared to cope with |
3273 | .PD 0 |
3507 | them (e.g. by ignoring them). Remember that warnings are just that: |
3274 | .IP "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % \s-1EV_PID_HASHSIZE\s0))" 4 |
3508 | warnings, not errors, or proof of bugs. |
3275 | .IX Item "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))" |
3509 | .Sh "\s-1VALGRIND\s0" |
3276 | .PD |
3510 | .IX Subsection "VALGRIND" |
3277 | These watchers are stored in lists then need to be walked to find the |
3511 | Valgrind has a special section here because it is a popular tool that is |
3278 | correct watcher to remove. The lists are usually short (you don't usually |
3512 | highly useful. Unfortunately, valgrind reports are very hard to interpret. |
3279 | have many watchers waiting for the same fd or signal). |
3513 | .PP |
3280 | .IP "Finding the next timer in each loop iteration: O(1)" 4 |
3514 | If you think you found a bug (memory leak, uninitialised data access etc.) |
3281 | .IX Item "Finding the next timer in each loop iteration: O(1)" |
3515 | in libev, then check twice: If valgrind reports something like: |
3282 | By virtue of using a binary or 4\-heap, the next timer is always found at a |
3516 | .PP |
3283 | fixed position in the storage array. |
3517 | .Vb 3 |
3284 | .IP "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)" 4 |
3518 | \& ==2274== definitely lost: 0 bytes in 0 blocks. |
3285 | .IX Item "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)" |
3519 | \& ==2274== possibly lost: 0 bytes in 0 blocks. |
3286 | A change means an I/O watcher gets started or stopped, which requires |
3520 | \& ==2274== still reachable: 256 bytes in 1 blocks. |
3287 | libev to recalculate its status (and possibly tell the kernel, depending |
3521 | .Ve |
3288 | on backend and wether \f(CW\*(C`ev_io_set\*(C'\fR was used). |
3522 | .PP |
3289 | .IP "Activating one watcher (putting it into the pending state): O(1)" 4 |
3523 | Then there is no memory leak, just as memory accounted to global variables |
3290 | .IX Item "Activating one watcher (putting it into the pending state): O(1)" |
3524 | is not a memleak \- the memory is still being refernced, and didn't leak. |
3291 | .PD 0 |
3525 | .PP |
3292 | .IP "Priority handling: O(number_of_priorities)" 4 |
3526 | Similarly, under some circumstances, valgrind might report kernel bugs |
3293 | .IX Item "Priority handling: O(number_of_priorities)" |
3527 | as if it were a bug in libev (e.g. in realloc or in the poll backend, |
3294 | .PD |
3528 | although an acceptable workaround has been found here), or it might be |
3295 | Priorities are implemented by allocating some space for each |
3529 | confused. |
3296 | priority. When doing priority-based operations, libev usually has to |
3530 | .PP |
3297 | linearly search all the priorities, but starting/stopping and activating |
3531 | Keep in mind that valgrind is a very good tool, but only a tool. Don't |
3298 | watchers becomes O(1) w.r.t. priority handling. |
3532 | make it into some kind of religion. |
3299 | .IP "Sending an ev_async: O(1)" 4 |
3533 | .PP |
3300 | .IX Item "Sending an ev_async: O(1)" |
3534 | If you are unsure about something, feel free to contact the mailing list |
3301 | .PD 0 |
3535 | with the full valgrind report and an explanation on why you think this |
3302 | .IP "Processing ev_async_send: O(number_of_async_watchers)" 4 |
3536 | is a bug in libev (best check the archives, too :). However, don't be |
3303 | .IX Item "Processing ev_async_send: O(number_of_async_watchers)" |
3537 | annoyed when you get a brisk \*(L"this is no bug\*(R" answer and take the chance |
3304 | .IP "Processing signals: O(max_signal_number)" 4 |
3538 | of learning how to interpret valgrind properly. |
3305 | .IX Item "Processing signals: O(max_signal_number)" |
3539 | .PP |
3306 | .PD |
3540 | If you need, for some reason, empty reports from valgrind for your project |
3307 | Sending involves a syscall \fIiff\fR there were no other \f(CW\*(C`ev_async_send\*(C'\fR |
3541 | I suggest using suppression lists. |
3308 | calls in the current loop iteration. Checking for async and signal events |
3542 | .SH "PORTABILITY NOTES" |
3309 | involves iterating over all running async watchers or all signal numbers. |
3543 | .IX Header "PORTABILITY NOTES" |
3310 | .SH "Win32 platform limitations and workarounds" |
3544 | .Sh "\s-1WIN32\s0 \s-1PLATFORM\s0 \s-1LIMITATIONS\s0 \s-1AND\s0 \s-1WORKAROUNDS\s0" |
3311 | .IX Header "Win32 platform limitations and workarounds" |
3545 | .IX Subsection "WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS" |
3312 | Win32 doesn't support any of the standards (e.g. \s-1POSIX\s0) that libev |
3546 | Win32 doesn't support any of the standards (e.g. \s-1POSIX\s0) that libev |
3313 | requires, and its I/O model is fundamentally incompatible with the \s-1POSIX\s0 |
3547 | requires, and its I/O model is fundamentally incompatible with the \s-1POSIX\s0 |
3314 | model. Libev still offers limited functionality on this platform in |
3548 | model. Libev still offers limited functionality on this platform in |
3315 | the form of the \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR backend, and only supports socket |
3549 | the form of the \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR backend, and only supports socket |
3316 | descriptors. This only applies when using Win32 natively, not when using |
3550 | descriptors. This only applies when using Win32 natively, not when using |
… | |
… | |
3322 | way (note also that glib is the slowest event library known to man). |
3556 | way (note also that glib is the slowest event library known to man). |
3323 | .PP |
3557 | .PP |
3324 | There is no supported compilation method available on windows except |
3558 | There is no supported compilation method available on windows except |
3325 | embedding it into other applications. |
3559 | embedding it into other applications. |
3326 | .PP |
3560 | .PP |
|
|
3561 | Not a libev limitation but worth mentioning: windows apparently doesn't |
|
|
3562 | accept large writes: instead of resulting in a partial write, windows will |
|
|
3563 | either accept everything or return \f(CW\*(C`ENOBUFS\*(C'\fR if the buffer is too large, |
|
|
3564 | so make sure you only write small amounts into your sockets (less than a |
|
|
3565 | megabyte seems safe, but this apparently depends on the amount of memory |
|
|
3566 | available). |
|
|
3567 | .PP |
3327 | Due to the many, low, and arbitrary limits on the win32 platform and |
3568 | Due to the many, low, and arbitrary limits on the win32 platform and |
3328 | the abysmal performance of winsockets, using a large number of sockets |
3569 | the abysmal performance of winsockets, using a large number of sockets |
3329 | is not recommended (and not reasonable). If your program needs to use |
3570 | is not recommended (and not reasonable). If your program needs to use |
3330 | more than a hundred or so sockets, then likely it needs to use a totally |
3571 | more than a hundred or so sockets, then likely it needs to use a totally |
3331 | different implementation for windows, as libev offers the \s-1POSIX\s0 readyness |
3572 | different implementation for windows, as libev offers the \s-1POSIX\s0 readiness |
3332 | notification model, which cannot be implemented efficiently on windows |
3573 | notification model, which cannot be implemented efficiently on windows |
3333 | (microsoft monopoly games). |
3574 | (Microsoft monopoly games). |
|
|
3575 | .PP |
|
|
3576 | A typical way to use libev under windows is to embed it (see the embedding |
|
|
3577 | section for details) and use the following \fIevwrap.h\fR header file instead |
|
|
3578 | of \fIev.h\fR: |
|
|
3579 | .PP |
|
|
3580 | .Vb 2 |
|
|
3581 | \& #define EV_STANDALONE /* keeps ev from requiring config.h */ |
|
|
3582 | \& #define EV_SELECT_IS_WINSOCKET 1 /* configure libev for windows select */ |
|
|
3583 | \& |
|
|
3584 | \& #include "ev.h" |
|
|
3585 | .Ve |
|
|
3586 | .PP |
|
|
3587 | And compile the following \fIevwrap.c\fR file into your project (make sure |
|
|
3588 | you do \fInot\fR compile the \fIev.c\fR or any other embedded source files!): |
|
|
3589 | .PP |
|
|
3590 | .Vb 2 |
|
|
3591 | \& #include "evwrap.h" |
|
|
3592 | \& #include "ev.c" |
|
|
3593 | .Ve |
3334 | .IP "The winsocket select function" 4 |
3594 | .IP "The winsocket select function" 4 |
3335 | .IX Item "The winsocket select function" |
3595 | .IX Item "The winsocket select function" |
3336 | The winsocket \f(CW\*(C`select\*(C'\fR function doesn't follow \s-1POSIX\s0 in that it requires |
3596 | The winsocket \f(CW\*(C`select\*(C'\fR function doesn't follow \s-1POSIX\s0 in that it |
3337 | socket \fIhandles\fR and not socket \fIfile descriptors\fR. This makes select |
3597 | requires socket \fIhandles\fR and not socket \fIfile descriptors\fR (it is |
3338 | very inefficient, and also requires a mapping from file descriptors |
3598 | also extremely buggy). This makes select very inefficient, and also |
3339 | to socket handles. See the discussion of the \f(CW\*(C`EV_SELECT_USE_FD_SET\*(C'\fR, |
3599 | requires a mapping from file descriptors to socket handles (the Microsoft |
3340 | \&\f(CW\*(C`EV_SELECT_IS_WINSOCKET\*(C'\fR and \f(CW\*(C`EV_FD_TO_WIN32_HANDLE\*(C'\fR preprocessor |
3600 | C runtime provides the function \f(CW\*(C`_open_osfhandle\*(C'\fR for this). See the |
3341 | symbols for more info. |
3601 | discussion of the \f(CW\*(C`EV_SELECT_USE_FD_SET\*(C'\fR, \f(CW\*(C`EV_SELECT_IS_WINSOCKET\*(C'\fR and |
|
|
3602 | \&\f(CW\*(C`EV_FD_TO_WIN32_HANDLE\*(C'\fR preprocessor symbols for more info. |
3342 | .Sp |
3603 | .Sp |
3343 | The configuration for a \*(L"naked\*(R" win32 using the microsoft runtime |
3604 | The configuration for a \*(L"naked\*(R" win32 using the Microsoft runtime |
3344 | libraries and raw winsocket select is: |
3605 | libraries and raw winsocket select is: |
3345 | .Sp |
3606 | .Sp |
3346 | .Vb 2 |
3607 | .Vb 2 |
3347 | \& #define EV_USE_SELECT 1 |
3608 | \& #define EV_USE_SELECT 1 |
3348 | \& #define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */ |
3609 | \& #define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */ |
3349 | .Ve |
3610 | .Ve |
3350 | .Sp |
3611 | .Sp |
3351 | Note that winsockets handling of fd sets is O(n), so you can easily get a |
3612 | Note that winsockets handling of fd sets is O(n), so you can easily get a |
3352 | complexity in the O(nA\*^X) range when using win32. |
3613 | complexity in the O(nA\*^X) range when using win32. |
3353 | .IP "Limited number of file descriptors" 4 |
3614 | .IP "Limited number of file descriptors" 4 |
3354 | .IX Item "Limited number of file descriptors" |
3615 | .IX Item "Limited number of file descriptors" |
3355 | Windows has numerous arbitrary (and low) limits on things. |
3616 | Windows has numerous arbitrary (and low) limits on things. |
3356 | .Sp |
3617 | .Sp |
3357 | Early versions of winsocket's select only supported waiting for a maximum |
3618 | Early versions of winsocket's select only supported waiting for a maximum |
3358 | of \f(CW64\fR handles (probably owning to the fact that all windows kernels |
3619 | of \f(CW64\fR handles (probably owning to the fact that all windows kernels |
3359 | can only wait for \f(CW64\fR things at the same time internally; microsoft |
3620 | can only wait for \f(CW64\fR things at the same time internally; Microsoft |
3360 | recommends spawning a chain of threads and wait for 63 handles and the |
3621 | recommends spawning a chain of threads and wait for 63 handles and the |
3361 | previous thread in each. Great). |
3622 | previous thread in each. Great). |
3362 | .Sp |
3623 | .Sp |
3363 | Newer versions support more handles, but you need to define \f(CW\*(C`FD_SETSIZE\*(C'\fR |
3624 | Newer versions support more handles, but you need to define \f(CW\*(C`FD_SETSIZE\*(C'\fR |
3364 | to some high number (e.g. \f(CW2048\fR) before compiling the winsocket select |
3625 | to some high number (e.g. \f(CW2048\fR) before compiling the winsocket select |
3365 | call (which might be in libev or elsewhere, for example, perl does its own |
3626 | call (which might be in libev or elsewhere, for example, perl does its own |
3366 | select emulation on windows). |
3627 | select emulation on windows). |
3367 | .Sp |
3628 | .Sp |
3368 | Another limit is the number of file descriptors in the microsoft runtime |
3629 | Another limit is the number of file descriptors in the Microsoft runtime |
3369 | libraries, which by default is \f(CW64\fR (there must be a hidden \fI64\fR fetish |
3630 | libraries, which by default is \f(CW64\fR (there must be a hidden \fI64\fR fetish |
3370 | or something like this inside microsoft). You can increase this by calling |
3631 | or something like this inside Microsoft). You can increase this by calling |
3371 | \&\f(CW\*(C`_setmaxstdio\*(C'\fR, which can increase this limit to \f(CW2048\fR (another |
3632 | \&\f(CW\*(C`_setmaxstdio\*(C'\fR, which can increase this limit to \f(CW2048\fR (another |
3372 | arbitrary limit), but is broken in many versions of the microsoft runtime |
3633 | arbitrary limit), but is broken in many versions of the Microsoft runtime |
3373 | libraries. |
3634 | libraries. |
3374 | .Sp |
3635 | .Sp |
3375 | This might get you to about \f(CW512\fR or \f(CW2048\fR sockets (depending on |
3636 | This might get you to about \f(CW512\fR or \f(CW2048\fR sockets (depending on |
3376 | windows version and/or the phase of the moon). To get more, you need to |
3637 | windows version and/or the phase of the moon). To get more, you need to |
3377 | wrap all I/O functions and provide your own fd management, but the cost of |
3638 | wrap all I/O functions and provide your own fd management, but the cost of |
3378 | calling select (O(nA\*^X)) will likely make this unworkable. |
3639 | calling select (O(nA\*^X)) will likely make this unworkable. |
3379 | .SH "PORTABILITY REQUIREMENTS" |
3640 | .Sh "\s-1PORTABILITY\s0 \s-1REQUIREMENTS\s0" |
3380 | .IX Header "PORTABILITY REQUIREMENTS" |
3641 | .IX Subsection "PORTABILITY REQUIREMENTS" |
3381 | In addition to a working ISO-C implementation, libev relies on a few |
3642 | In addition to a working ISO-C implementation and of course the |
3382 | additional extensions: |
3643 | backend-specific APIs, libev relies on a few additional extensions: |
|
|
3644 | .ie n .IP """void (*)(ev_watcher_type *, int revents)""\fR must have compatible calling conventions regardless of \f(CW""ev_watcher_type *""." 4 |
|
|
3645 | .el .IP "\f(CWvoid (*)(ev_watcher_type *, int revents)\fR must have compatible calling conventions regardless of \f(CWev_watcher_type *\fR." 4 |
|
|
3646 | .IX Item "void (*)(ev_watcher_type *, int revents) must have compatible calling conventions regardless of ev_watcher_type *." |
|
|
3647 | Libev assumes not only that all watcher pointers have the same internal |
|
|
3648 | structure (guaranteed by \s-1POSIX\s0 but not by \s-1ISO\s0 C for example), but it also |
|
|
3649 | assumes that the same (machine) code can be used to call any watcher |
|
|
3650 | callback: The watcher callbacks have different type signatures, but libev |
|
|
3651 | calls them using an \f(CW\*(C`ev_watcher *\*(C'\fR internally. |
3383 | .ie n .IP """sig_atomic_t volatile"" must be thread-atomic as well" 4 |
3652 | .ie n .IP """sig_atomic_t volatile"" must be thread-atomic as well" 4 |
3384 | .el .IP "\f(CWsig_atomic_t volatile\fR must be thread-atomic as well" 4 |
3653 | .el .IP "\f(CWsig_atomic_t volatile\fR must be thread-atomic as well" 4 |
3385 | .IX Item "sig_atomic_t volatile must be thread-atomic as well" |
3654 | .IX Item "sig_atomic_t volatile must be thread-atomic as well" |
3386 | The type \f(CW\*(C`sig_atomic_t volatile\*(C'\fR (or whatever is defined as |
3655 | The type \f(CW\*(C`sig_atomic_t volatile\*(C'\fR (or whatever is defined as |
3387 | \&\f(CW\*(C`EV_ATOMIC_T\*(C'\fR) must be atomic w.r.t. accesses from different |
3656 | \&\f(CW\*(C`EV_ATOMIC_T\*(C'\fR) must be atomic with respect to accesses from different |
3388 | threads. This is not part of the specification for \f(CW\*(C`sig_atomic_t\*(C'\fR, but is |
3657 | threads. This is not part of the specification for \f(CW\*(C`sig_atomic_t\*(C'\fR, but is |
3389 | believed to be sufficiently portable. |
3658 | believed to be sufficiently portable. |
3390 | .ie n .IP """sigprocmask"" must work in a threaded environment" 4 |
3659 | .ie n .IP """sigprocmask"" must work in a threaded environment" 4 |
3391 | .el .IP "\f(CWsigprocmask\fR must work in a threaded environment" 4 |
3660 | .el .IP "\f(CWsigprocmask\fR must work in a threaded environment" 4 |
3392 | .IX Item "sigprocmask must work in a threaded environment" |
3661 | .IX Item "sigprocmask must work in a threaded environment" |
… | |
… | |
3401 | except the initial one, and run the default loop in the initial thread as |
3670 | except the initial one, and run the default loop in the initial thread as |
3402 | well. |
3671 | well. |
3403 | .ie n .IP """long"" must be large enough for common memory allocation sizes" 4 |
3672 | .ie n .IP """long"" must be large enough for common memory allocation sizes" 4 |
3404 | .el .IP "\f(CWlong\fR must be large enough for common memory allocation sizes" 4 |
3673 | .el .IP "\f(CWlong\fR must be large enough for common memory allocation sizes" 4 |
3405 | .IX Item "long must be large enough for common memory allocation sizes" |
3674 | .IX Item "long must be large enough for common memory allocation sizes" |
3406 | To improve portability and simplify using libev, libev uses \f(CW\*(C`long\*(C'\fR |
3675 | To improve portability and simplify its \s-1API\s0, libev uses \f(CW\*(C`long\*(C'\fR internally |
3407 | internally instead of \f(CW\*(C`size_t\*(C'\fR when allocating its data structures. On |
3676 | instead of \f(CW\*(C`size_t\*(C'\fR when allocating its data structures. On non-POSIX |
3408 | non-POSIX systems (Microsoft...) this might be unexpectedly low, but |
3677 | systems (Microsoft...) this might be unexpectedly low, but is still at |
3409 | is still at least 31 bits everywhere, which is enough for hundreds of |
3678 | least 31 bits everywhere, which is enough for hundreds of millions of |
3410 | millions of watchers. |
3679 | watchers. |
3411 | .ie n .IP """double"" must hold a time value in seconds with enough accuracy" 4 |
3680 | .ie n .IP """double"" must hold a time value in seconds with enough accuracy" 4 |
3412 | .el .IP "\f(CWdouble\fR must hold a time value in seconds with enough accuracy" 4 |
3681 | .el .IP "\f(CWdouble\fR must hold a time value in seconds with enough accuracy" 4 |
3413 | .IX Item "double must hold a time value in seconds with enough accuracy" |
3682 | .IX Item "double must hold a time value in seconds with enough accuracy" |
3414 | The type \f(CW\*(C`double\*(C'\fR is used to represent timestamps. It is required to |
3683 | The type \f(CW\*(C`double\*(C'\fR is used to represent timestamps. It is required to |
3415 | have at least 51 bits of mantissa (and 9 bits of exponent), which is good |
3684 | have at least 51 bits of mantissa (and 9 bits of exponent), which is good |
3416 | enough for at least into the year 4000. This requirement is fulfilled by |
3685 | enough for at least into the year 4000. This requirement is fulfilled by |
3417 | implementations implementing \s-1IEEE\s0 754 (basically all existing ones). |
3686 | implementations implementing \s-1IEEE\s0 754 (basically all existing ones). |
3418 | .PP |
3687 | .PP |
3419 | If you know of other additional requirements drop me a note. |
3688 | If you know of other additional requirements drop me a note. |
|
|
3689 | .SH "ALGORITHMIC COMPLEXITIES" |
|
|
3690 | .IX Header "ALGORITHMIC COMPLEXITIES" |
|
|
3691 | In this section the complexities of (many of) the algorithms used inside |
|
|
3692 | libev will be documented. For complexity discussions about backends see |
|
|
3693 | the documentation for \f(CW\*(C`ev_default_init\*(C'\fR. |
|
|
3694 | .PP |
|
|
3695 | All of the following are about amortised time: If an array needs to be |
|
|
3696 | extended, libev needs to realloc and move the whole array, but this |
|
|
3697 | happens asymptotically rarer with higher number of elements, so O(1) might |
|
|
3698 | mean that libev does a lengthy realloc operation in rare cases, but on |
|
|
3699 | average it is much faster and asymptotically approaches constant time. |
|
|
3700 | .IP "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" 4 |
|
|
3701 | .IX Item "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" |
|
|
3702 | This means that, when you have a watcher that triggers in one hour and |
|
|
3703 | there are 100 watchers that would trigger before that, then inserting will |
|
|
3704 | have to skip roughly seven (\f(CW\*(C`ld 100\*(C'\fR) of these watchers. |
|
|
3705 | .IP "Changing timer/periodic watchers (by autorepeat or calling again): O(log skipped_other_timers)" 4 |
|
|
3706 | .IX Item "Changing timer/periodic watchers (by autorepeat or calling again): O(log skipped_other_timers)" |
|
|
3707 | That means that changing a timer costs less than removing/adding them, |
|
|
3708 | as only the relative motion in the event queue has to be paid for. |
|
|
3709 | .IP "Starting io/check/prepare/idle/signal/child/fork/async watchers: O(1)" 4 |
|
|
3710 | .IX Item "Starting io/check/prepare/idle/signal/child/fork/async watchers: O(1)" |
|
|
3711 | These just add the watcher into an array or at the head of a list. |
|
|
3712 | .IP "Stopping check/prepare/idle/fork/async watchers: O(1)" 4 |
|
|
3713 | .IX Item "Stopping check/prepare/idle/fork/async watchers: O(1)" |
|
|
3714 | .PD 0 |
|
|
3715 | .IP "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % \s-1EV_PID_HASHSIZE\s0))" 4 |
|
|
3716 | .IX Item "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))" |
|
|
3717 | .PD |
|
|
3718 | These watchers are stored in lists, so they need to be walked to find the |
|
|
3719 | correct watcher to remove. The lists are usually short (you don't usually |
|
|
3720 | have many watchers waiting for the same fd or signal: one is typical, two |
|
|
3721 | is rare). |
|
|
3722 | .IP "Finding the next timer in each loop iteration: O(1)" 4 |
|
|
3723 | .IX Item "Finding the next timer in each loop iteration: O(1)" |
|
|
3724 | By virtue of using a binary or 4\-heap, the next timer is always found at a |
|
|
3725 | fixed position in the storage array. |
|
|
3726 | .IP "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)" 4 |
|
|
3727 | .IX Item "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)" |
|
|
3728 | A change means an I/O watcher gets started or stopped, which requires |
|
|
3729 | libev to recalculate its status (and possibly tell the kernel, depending |
|
|
3730 | on backend and whether \f(CW\*(C`ev_io_set\*(C'\fR was used). |
|
|
3731 | .IP "Activating one watcher (putting it into the pending state): O(1)" 4 |
|
|
3732 | .IX Item "Activating one watcher (putting it into the pending state): O(1)" |
|
|
3733 | .PD 0 |
|
|
3734 | .IP "Priority handling: O(number_of_priorities)" 4 |
|
|
3735 | .IX Item "Priority handling: O(number_of_priorities)" |
|
|
3736 | .PD |
|
|
3737 | Priorities are implemented by allocating some space for each |
|
|
3738 | priority. When doing priority-based operations, libev usually has to |
|
|
3739 | linearly search all the priorities, but starting/stopping and activating |
|
|
3740 | watchers becomes O(1) with respect to priority handling. |
|
|
3741 | .IP "Sending an ev_async: O(1)" 4 |
|
|
3742 | .IX Item "Sending an ev_async: O(1)" |
|
|
3743 | .PD 0 |
|
|
3744 | .IP "Processing ev_async_send: O(number_of_async_watchers)" 4 |
|
|
3745 | .IX Item "Processing ev_async_send: O(number_of_async_watchers)" |
|
|
3746 | .IP "Processing signals: O(max_signal_number)" 4 |
|
|
3747 | .IX Item "Processing signals: O(max_signal_number)" |
|
|
3748 | .PD |
|
|
3749 | Sending involves a system call \fIiff\fR there were no other \f(CW\*(C`ev_async_send\*(C'\fR |
|
|
3750 | calls in the current loop iteration. Checking for async and signal events |
|
|
3751 | involves iterating over all running async watchers or all signal numbers. |
3420 | .SH "AUTHOR" |
3752 | .SH "AUTHOR" |
3421 | .IX Header "AUTHOR" |
3753 | .IX Header "AUTHOR" |
3422 | Marc Lehmann <libev@schmorp.de>. |
3754 | Marc Lehmann <libev@schmorp.de>. |
3423 | .SH "POD ERRORS" |
|
|
3424 | .IX Header "POD ERRORS" |
|
|
3425 | Hey! \fBThe above document had some coding errors, which are explained below:\fR |
|
|
3426 | .IP "Around line 3052:" 4 |
|
|
3427 | .IX Item "Around line 3052:" |
|
|
3428 | You forgot a '=back' before '=head2' |
|
|