1 | .\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16) |
1 | .\" Automatically generated by Pod::Man 4.11 (Pod::Simple 3.35) |
2 | .\" |
2 | .\" |
3 | .\" Standard preamble: |
3 | .\" Standard preamble: |
4 | .\" ======================================================================== |
4 | .\" ======================================================================== |
5 | .de Sp \" Vertical space (when we can't use .PP) |
5 | .de Sp \" Vertical space (when we can't use .PP) |
6 | .if t .sp .5v |
6 | .if t .sp .5v |
… | |
… | |
36 | .el\{\ |
36 | .el\{\ |
37 | . ds -- \|\(em\| |
37 | . ds -- \|\(em\| |
38 | . ds PI \(*p |
38 | . ds PI \(*p |
39 | . ds L" `` |
39 | . ds L" `` |
40 | . ds R" '' |
40 | . ds R" '' |
|
|
41 | . ds C` |
|
|
42 | . ds C' |
41 | 'br\} |
43 | 'br\} |
42 | .\" |
44 | .\" |
43 | .\" Escape single quotes in literal strings from groff's Unicode transform. |
45 | .\" Escape single quotes in literal strings from groff's Unicode transform. |
44 | .ie \n(.g .ds Aq \(aq |
46 | .ie \n(.g .ds Aq \(aq |
45 | .el .ds Aq ' |
47 | .el .ds Aq ' |
46 | .\" |
48 | .\" |
47 | .\" If the F register is turned on, we'll generate index entries on stderr for |
49 | .\" If the F register is >0, we'll generate index entries on stderr for |
48 | .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index |
50 | .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index |
49 | .\" entries marked with X<> in POD. Of course, you'll have to process the |
51 | .\" entries marked with X<> in POD. Of course, you'll have to process the |
50 | .\" output yourself in some meaningful fashion. |
52 | .\" output yourself in some meaningful fashion. |
51 | .ie \nF \{\ |
53 | .\" |
|
|
54 | .\" Avoid warning from groff about undefined register 'F'. |
52 | . de IX |
55 | .de IX |
53 | . tm Index:\\$1\t\\n%\t"\\$2" |
|
|
54 | .. |
56 | .. |
55 | . nr % 0 |
57 | .nr rF 0 |
56 | . rr F |
58 | .if \n(.g .if rF .nr rF 1 |
|
|
59 | .if (\n(rF:(\n(.g==0)) \{\ |
|
|
60 | . if \nF \{\ |
|
|
61 | . de IX |
|
|
62 | . tm Index:\\$1\t\\n%\t"\\$2" |
|
|
63 | .. |
|
|
64 | . if !\nF==2 \{\ |
|
|
65 | . nr % 0 |
|
|
66 | . nr F 2 |
|
|
67 | . \} |
|
|
68 | . \} |
57 | .\} |
69 | .\} |
58 | .el \{\ |
70 | .rr rF |
59 | . de IX |
|
|
60 | .. |
|
|
61 | .\} |
|
|
62 | .\" |
71 | .\" |
63 | .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). |
72 | .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). |
64 | .\" Fear. Run. Save yourself. No user-serviceable parts. |
73 | .\" Fear. Run. Save yourself. No user-serviceable parts. |
65 | . \" fudge factors for nroff and troff |
74 | . \" fudge factors for nroff and troff |
66 | .if n \{\ |
75 | .if n \{\ |
… | |
… | |
122 | .\} |
131 | .\} |
123 | .rm #[ #] #H #V #F C |
132 | .rm #[ #] #H #V #F C |
124 | .\" ======================================================================== |
133 | .\" ======================================================================== |
125 | .\" |
134 | .\" |
126 | .IX Title "LIBEV 3" |
135 | .IX Title "LIBEV 3" |
127 | .TH LIBEV 3 "2012-05-26" "libev-4.11" "libev - high performance full featured event loop" |
136 | .TH LIBEV 3 "2021-01-11" "libev-4.33" "libev - high performance full featured event loop" |
128 | .\" For nroff, turn off justification. Always turn off hyphenation; it makes |
137 | .\" For nroff, turn off justification. Always turn off hyphenation; it makes |
129 | .\" way too many mistakes in technical documents. |
138 | .\" way too many mistakes in technical documents. |
130 | .if n .ad l |
139 | .if n .ad l |
131 | .nh |
140 | .nh |
132 | .SH "NAME" |
141 | .SH "NAME" |
… | |
… | |
134 | .SH "SYNOPSIS" |
143 | .SH "SYNOPSIS" |
135 | .IX Header "SYNOPSIS" |
144 | .IX Header "SYNOPSIS" |
136 | .Vb 1 |
145 | .Vb 1 |
137 | \& #include <ev.h> |
146 | \& #include <ev.h> |
138 | .Ve |
147 | .Ve |
139 | .SS "\s-1EXAMPLE\s0 \s-1PROGRAM\s0" |
148 | .SS "\s-1EXAMPLE PROGRAM\s0" |
140 | .IX Subsection "EXAMPLE PROGRAM" |
149 | .IX Subsection "EXAMPLE PROGRAM" |
141 | .Vb 2 |
150 | .Vb 2 |
142 | \& // a single header file is required |
151 | \& // a single header file is required |
143 | \& #include <ev.h> |
152 | \& #include <ev.h> |
144 | \& |
153 | \& |
… | |
… | |
212 | throughout this document. |
221 | throughout this document. |
213 | .SH "WHAT TO READ WHEN IN A HURRY" |
222 | .SH "WHAT TO READ WHEN IN A HURRY" |
214 | .IX Header "WHAT TO READ WHEN IN A HURRY" |
223 | .IX Header "WHAT TO READ WHEN IN A HURRY" |
215 | This manual tries to be very detailed, but unfortunately, this also makes |
224 | This manual tries to be very detailed, but unfortunately, this also makes |
216 | it very long. If you just want to know the basics of libev, I suggest |
225 | it very long. If you just want to know the basics of libev, I suggest |
217 | reading \*(L"\s-1ANATOMY\s0 \s-1OF\s0 A \s-1WATCHER\s0\*(R", then the \*(L"\s-1EXAMPLE\s0 \s-1PROGRAM\s0\*(R" above and |
226 | reading \*(L"\s-1ANATOMY OF A WATCHER\*(R"\s0, then the \*(L"\s-1EXAMPLE PROGRAM\*(R"\s0 above and |
218 | look up the missing functions in \*(L"\s-1GLOBAL\s0 \s-1FUNCTIONS\s0\*(R" and the \f(CW\*(C`ev_io\*(C'\fR and |
227 | look up the missing functions in \*(L"\s-1GLOBAL FUNCTIONS\*(R"\s0 and the \f(CW\*(C`ev_io\*(C'\fR and |
219 | \&\f(CW\*(C`ev_timer\*(C'\fR sections in \*(L"\s-1WATCHER\s0 \s-1TYPES\s0\*(R". |
228 | \&\f(CW\*(C`ev_timer\*(C'\fR sections in \*(L"\s-1WATCHER TYPES\*(R"\s0. |
220 | .SH "ABOUT LIBEV" |
229 | .SH "ABOUT LIBEV" |
221 | .IX Header "ABOUT LIBEV" |
230 | .IX Header "ABOUT LIBEV" |
222 | Libev is an event loop: you register interest in certain events (such as a |
231 | Libev is an event loop: you register interest in certain events (such as a |
223 | file descriptor being readable or a timeout occurring), and it will manage |
232 | file descriptor being readable or a timeout occurring), and it will manage |
224 | these event sources and provide your program with events. |
233 | these event sources and provide your program with events. |
… | |
… | |
231 | watchers\fR, which are relatively small C structures you initialise with the |
240 | watchers\fR, which are relatively small C structures you initialise with the |
232 | details of the event, and then hand it over to libev by \fIstarting\fR the |
241 | details of the event, and then hand it over to libev by \fIstarting\fR the |
233 | watcher. |
242 | watcher. |
234 | .SS "\s-1FEATURES\s0" |
243 | .SS "\s-1FEATURES\s0" |
235 | .IX Subsection "FEATURES" |
244 | .IX Subsection "FEATURES" |
236 | Libev supports \f(CW\*(C`select\*(C'\fR, \f(CW\*(C`poll\*(C'\fR, the Linux-specific \f(CW\*(C`epoll\*(C'\fR, the |
245 | Libev supports \f(CW\*(C`select\*(C'\fR, \f(CW\*(C`poll\*(C'\fR, the Linux-specific aio and \f(CW\*(C`epoll\*(C'\fR |
237 | BSD-specific \f(CW\*(C`kqueue\*(C'\fR and the Solaris-specific event port mechanisms |
246 | interfaces, the BSD-specific \f(CW\*(C`kqueue\*(C'\fR and the Solaris-specific event port |
238 | for file descriptor events (\f(CW\*(C`ev_io\*(C'\fR), the Linux \f(CW\*(C`inotify\*(C'\fR interface |
247 | mechanisms for file descriptor events (\f(CW\*(C`ev_io\*(C'\fR), the Linux \f(CW\*(C`inotify\*(C'\fR |
239 | (for \f(CW\*(C`ev_stat\*(C'\fR), Linux eventfd/signalfd (for faster and cleaner |
248 | interface (for \f(CW\*(C`ev_stat\*(C'\fR), Linux eventfd/signalfd (for faster and cleaner |
240 | inter-thread wakeup (\f(CW\*(C`ev_async\*(C'\fR)/signal handling (\f(CW\*(C`ev_signal\*(C'\fR)) relative |
249 | inter-thread wakeup (\f(CW\*(C`ev_async\*(C'\fR)/signal handling (\f(CW\*(C`ev_signal\*(C'\fR)) relative |
241 | timers (\f(CW\*(C`ev_timer\*(C'\fR), absolute timers with customised rescheduling |
250 | timers (\f(CW\*(C`ev_timer\*(C'\fR), absolute timers with customised rescheduling |
242 | (\f(CW\*(C`ev_periodic\*(C'\fR), synchronous signals (\f(CW\*(C`ev_signal\*(C'\fR), process status |
251 | (\f(CW\*(C`ev_periodic\*(C'\fR), synchronous signals (\f(CW\*(C`ev_signal\*(C'\fR), process status |
243 | change events (\f(CW\*(C`ev_child\*(C'\fR), and event watchers dealing with the event |
252 | change events (\f(CW\*(C`ev_child\*(C'\fR), and event watchers dealing with the event |
244 | loop mechanism itself (\f(CW\*(C`ev_idle\*(C'\fR, \f(CW\*(C`ev_embed\*(C'\fR, \f(CW\*(C`ev_prepare\*(C'\fR and |
253 | loop mechanism itself (\f(CW\*(C`ev_idle\*(C'\fR, \f(CW\*(C`ev_embed\*(C'\fR, \f(CW\*(C`ev_prepare\*(C'\fR and |
… | |
… | |
255 | more info about various configuration options please have a look at |
264 | more info about various configuration options please have a look at |
256 | \&\fB\s-1EMBED\s0\fR section in this manual. If libev was configured without support |
265 | \&\fB\s-1EMBED\s0\fR section in this manual. If libev was configured without support |
257 | for multiple event loops, then all functions taking an initial argument of |
266 | for multiple event loops, then all functions taking an initial argument of |
258 | name \f(CW\*(C`loop\*(C'\fR (which is always of type \f(CW\*(C`struct ev_loop *\*(C'\fR) will not have |
267 | name \f(CW\*(C`loop\*(C'\fR (which is always of type \f(CW\*(C`struct ev_loop *\*(C'\fR) will not have |
259 | this argument. |
268 | this argument. |
260 | .SS "\s-1TIME\s0 \s-1REPRESENTATION\s0" |
269 | .SS "\s-1TIME REPRESENTATION\s0" |
261 | .IX Subsection "TIME REPRESENTATION" |
270 | .IX Subsection "TIME REPRESENTATION" |
262 | Libev represents time as a single floating point number, representing |
271 | Libev represents time as a single floating point number, representing |
263 | the (fractional) number of seconds since the (\s-1POSIX\s0) epoch (in practice |
272 | the (fractional) number of seconds since the (\s-1POSIX\s0) epoch (in practice |
264 | somewhere near the beginning of 1970, details are complicated, don't |
273 | somewhere near the beginning of 1970, details are complicated, don't |
265 | ask). This type is called \f(CW\*(C`ev_tstamp\*(C'\fR, which is what you should use |
274 | ask). This type is called \f(CW\*(C`ev_tstamp\*(C'\fR, which is what you should use |
… | |
… | |
282 | When libev detects a usage error such as a negative timer interval, then |
291 | When libev detects a usage error such as a negative timer interval, then |
283 | it will print a diagnostic message and abort (via the \f(CW\*(C`assert\*(C'\fR mechanism, |
292 | it will print a diagnostic message and abort (via the \f(CW\*(C`assert\*(C'\fR mechanism, |
284 | so \f(CW\*(C`NDEBUG\*(C'\fR will disable this checking): these are programming errors in |
293 | so \f(CW\*(C`NDEBUG\*(C'\fR will disable this checking): these are programming errors in |
285 | the libev caller and need to be fixed there. |
294 | the libev caller and need to be fixed there. |
286 | .PP |
295 | .PP |
|
|
296 | Via the \f(CW\*(C`EV_FREQUENT\*(C'\fR macro you can compile in and/or enable extensive |
|
|
297 | consistency checking code inside libev that can be used to check for |
|
|
298 | internal inconsistencies, suually caused by application bugs. |
|
|
299 | .PP |
287 | Libev also has a few internal error-checking \f(CW\*(C`assert\*(C'\fRions, and also has |
300 | Libev also has a few internal error-checking \f(CW\*(C`assert\*(C'\fRions. These do not |
288 | extensive consistency checking code. These do not trigger under normal |
|
|
289 | circumstances, as they indicate either a bug in libev or worse. |
301 | trigger under normal circumstances, as they indicate either a bug in libev |
|
|
302 | or worse. |
290 | .SH "GLOBAL FUNCTIONS" |
303 | .SH "GLOBAL FUNCTIONS" |
291 | .IX Header "GLOBAL FUNCTIONS" |
304 | .IX Header "GLOBAL FUNCTIONS" |
292 | These functions can be called anytime, even before initialising the |
305 | These functions can be called anytime, even before initialising the |
293 | library in any way. |
306 | library in any way. |
294 | .IP "ev_tstamp ev_time ()" 4 |
307 | .IP "ev_tstamp ev_time ()" 4 |
… | |
… | |
383 | .Sp |
396 | .Sp |
384 | You could override this function in high-availability programs to, say, |
397 | You could override this function in high-availability programs to, say, |
385 | free some memory if it cannot allocate memory, to use a special allocator, |
398 | free some memory if it cannot allocate memory, to use a special allocator, |
386 | or even to sleep a while and retry until some memory is available. |
399 | or even to sleep a while and retry until some memory is available. |
387 | .Sp |
400 | .Sp |
|
|
401 | Example: The following is the \f(CW\*(C`realloc\*(C'\fR function that libev itself uses |
|
|
402 | which should work with \f(CW\*(C`realloc\*(C'\fR and \f(CW\*(C`free\*(C'\fR functions of all kinds and |
|
|
403 | is probably a good basis for your own implementation. |
|
|
404 | .Sp |
|
|
405 | .Vb 5 |
|
|
406 | \& static void * |
|
|
407 | \& ev_realloc_emul (void *ptr, long size) EV_NOEXCEPT |
|
|
408 | \& { |
|
|
409 | \& if (size) |
|
|
410 | \& return realloc (ptr, size); |
|
|
411 | \& |
|
|
412 | \& free (ptr); |
|
|
413 | \& return 0; |
|
|
414 | \& } |
|
|
415 | .Ve |
|
|
416 | .Sp |
388 | Example: Replace the libev allocator with one that waits a bit and then |
417 | Example: Replace the libev allocator with one that waits a bit and then |
389 | retries (example requires a standards-compliant \f(CW\*(C`realloc\*(C'\fR). |
418 | retries. |
390 | .Sp |
419 | .Sp |
391 | .Vb 6 |
420 | .Vb 8 |
392 | \& static void * |
421 | \& static void * |
393 | \& persistent_realloc (void *ptr, size_t size) |
422 | \& persistent_realloc (void *ptr, size_t size) |
394 | \& { |
423 | \& { |
|
|
424 | \& if (!size) |
|
|
425 | \& { |
|
|
426 | \& free (ptr); |
|
|
427 | \& return 0; |
|
|
428 | \& } |
|
|
429 | \& |
395 | \& for (;;) |
430 | \& for (;;) |
396 | \& { |
431 | \& { |
397 | \& void *newptr = realloc (ptr, size); |
432 | \& void *newptr = realloc (ptr, size); |
398 | \& |
433 | \& |
399 | \& if (newptr) |
434 | \& if (newptr) |
… | |
… | |
514 | .IX Item "EVFLAG_NOENV" |
549 | .IX Item "EVFLAG_NOENV" |
515 | If this flag bit is or'ed into the flag value (or the program runs setuid |
550 | If this flag bit is or'ed into the flag value (or the program runs setuid |
516 | or setgid) then libev will \fInot\fR look at the environment variable |
551 | or setgid) then libev will \fInot\fR look at the environment variable |
517 | \&\f(CW\*(C`LIBEV_FLAGS\*(C'\fR. Otherwise (the default), this environment variable will |
552 | \&\f(CW\*(C`LIBEV_FLAGS\*(C'\fR. Otherwise (the default), this environment variable will |
518 | override the flags completely if it is found in the environment. This is |
553 | override the flags completely if it is found in the environment. This is |
519 | useful to try out specific backends to test their performance, or to work |
554 | useful to try out specific backends to test their performance, to work |
520 | around bugs. |
555 | around bugs, or to make libev threadsafe (accessing environment variables |
|
|
556 | cannot be done in a threadsafe way, but usually it works if no other |
|
|
557 | thread modifies them). |
521 | .ie n .IP """EVFLAG_FORKCHECK""" 4 |
558 | .ie n .IP """EVFLAG_FORKCHECK""" 4 |
522 | .el .IP "\f(CWEVFLAG_FORKCHECK\fR" 4 |
559 | .el .IP "\f(CWEVFLAG_FORKCHECK\fR" 4 |
523 | .IX Item "EVFLAG_FORKCHECK" |
560 | .IX Item "EVFLAG_FORKCHECK" |
524 | Instead of calling \f(CW\*(C`ev_loop_fork\*(C'\fR manually after a fork, you can also |
561 | Instead of calling \f(CW\*(C`ev_loop_fork\*(C'\fR manually after a fork, you can also |
525 | make libev check for a fork in each iteration by enabling this flag. |
562 | make libev check for a fork in each iteration by enabling this flag. |
526 | .Sp |
563 | .Sp |
527 | This works by calling \f(CW\*(C`getpid ()\*(C'\fR on every iteration of the loop, |
564 | This works by calling \f(CW\*(C`getpid ()\*(C'\fR on every iteration of the loop, |
528 | and thus this might slow down your event loop if you do a lot of loop |
565 | and thus this might slow down your event loop if you do a lot of loop |
529 | iterations and little real work, but is usually not noticeable (on my |
566 | iterations and little real work, but is usually not noticeable (on my |
530 | GNU/Linux system for example, \f(CW\*(C`getpid\*(C'\fR is actually a simple 5\-insn sequence |
567 | GNU/Linux system for example, \f(CW\*(C`getpid\*(C'\fR is actually a simple 5\-insn |
531 | without a system call and thus \fIvery\fR fast, but my GNU/Linux system also has |
568 | sequence without a system call and thus \fIvery\fR fast, but my GNU/Linux |
532 | \&\f(CW\*(C`pthread_atfork\*(C'\fR which is even faster). |
569 | system also has \f(CW\*(C`pthread_atfork\*(C'\fR which is even faster). (Update: glibc |
|
|
570 | versions 2.25 apparently removed the \f(CW\*(C`getpid\*(C'\fR optimisation again). |
533 | .Sp |
571 | .Sp |
534 | The big advantage of this flag is that you can forget about fork (and |
572 | The big advantage of this flag is that you can forget about fork (and |
535 | forget about forgetting to tell libev about forking) when you use this |
573 | forget about forgetting to tell libev about forking, although you still |
536 | flag. |
574 | have to ignore \f(CW\*(C`SIGPIPE\*(C'\fR) when you use this flag. |
537 | .Sp |
575 | .Sp |
538 | This flag setting cannot be overridden or specified in the \f(CW\*(C`LIBEV_FLAGS\*(C'\fR |
576 | This flag setting cannot be overridden or specified in the \f(CW\*(C`LIBEV_FLAGS\*(C'\fR |
539 | environment variable. |
577 | environment variable. |
540 | .ie n .IP """EVFLAG_NOINOTIFY""" 4 |
578 | .ie n .IP """EVFLAG_NOINOTIFY""" 4 |
541 | .el .IP "\f(CWEVFLAG_NOINOTIFY\fR" 4 |
579 | .el .IP "\f(CWEVFLAG_NOINOTIFY\fR" 4 |
… | |
… | |
568 | want to handle signals only in specific threads and want to avoid libev |
606 | want to handle signals only in specific threads and want to avoid libev |
569 | unblocking the signals. |
607 | unblocking the signals. |
570 | .Sp |
608 | .Sp |
571 | It's also required by \s-1POSIX\s0 in a threaded program, as libev calls |
609 | It's also required by \s-1POSIX\s0 in a threaded program, as libev calls |
572 | \&\f(CW\*(C`sigprocmask\*(C'\fR, whose behaviour is officially unspecified. |
610 | \&\f(CW\*(C`sigprocmask\*(C'\fR, whose behaviour is officially unspecified. |
|
|
611 | .ie n .IP """EVFLAG_NOTIMERFD""" 4 |
|
|
612 | .el .IP "\f(CWEVFLAG_NOTIMERFD\fR" 4 |
|
|
613 | .IX Item "EVFLAG_NOTIMERFD" |
|
|
614 | When this flag is specified, the libev will avoid using a \f(CW\*(C`timerfd\*(C'\fR to |
|
|
615 | detect time jumps. It will still be able to detect time jumps, but takes |
|
|
616 | longer and has a lower accuracy in doing so, but saves a file descriptor |
|
|
617 | per loop. |
573 | .Sp |
618 | .Sp |
574 | This flag's behaviour will become the default in future versions of libev. |
619 | The current implementation only tries to use a \f(CW\*(C`timerfd\*(C'\fR when the first |
|
|
620 | \&\f(CW\*(C`ev_periodic\*(C'\fR watcher is started and falls back on other methods if it |
|
|
621 | cannot be created, but this behaviour might change in the future. |
575 | .ie n .IP """EVBACKEND_SELECT"" (value 1, portable select backend)" 4 |
622 | .ie n .IP """EVBACKEND_SELECT"" (value 1, portable select backend)" 4 |
576 | .el .IP "\f(CWEVBACKEND_SELECT\fR (value 1, portable select backend)" 4 |
623 | .el .IP "\f(CWEVBACKEND_SELECT\fR (value 1, portable select backend)" 4 |
577 | .IX Item "EVBACKEND_SELECT (value 1, portable select backend)" |
624 | .IX Item "EVBACKEND_SELECT (value 1, portable select backend)" |
578 | This is your standard \fIselect\fR\|(2) backend. Not \fIcompletely\fR standard, as |
625 | This is your standard \fBselect\fR\|(2) backend. Not \fIcompletely\fR standard, as |
579 | libev tries to roll its own fd_set with no limits on the number of fds, |
626 | libev tries to roll its own fd_set with no limits on the number of fds, |
580 | but if that fails, expect a fairly low limit on the number of fds when |
627 | but if that fails, expect a fairly low limit on the number of fds when |
581 | using this backend. It doesn't scale too well (O(highest_fd)), but its |
628 | using this backend. It doesn't scale too well (O(highest_fd)), but its |
582 | usually the fastest backend for a low number of (low-numbered :) fds. |
629 | usually the fastest backend for a low number of (low-numbered :) fds. |
583 | .Sp |
630 | .Sp |
… | |
… | |
591 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR to the \f(CW\*(C`readfds\*(C'\fR set and \f(CW\*(C`EV_WRITE\*(C'\fR to the |
638 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR to the \f(CW\*(C`readfds\*(C'\fR set and \f(CW\*(C`EV_WRITE\*(C'\fR to the |
592 | \&\f(CW\*(C`writefds\*(C'\fR set (and to work around Microsoft Windows bugs, also onto the |
639 | \&\f(CW\*(C`writefds\*(C'\fR set (and to work around Microsoft Windows bugs, also onto the |
593 | \&\f(CW\*(C`exceptfds\*(C'\fR set on that platform). |
640 | \&\f(CW\*(C`exceptfds\*(C'\fR set on that platform). |
594 | .ie n .IP """EVBACKEND_POLL"" (value 2, poll backend, available everywhere except on windows)" 4 |
641 | .ie n .IP """EVBACKEND_POLL"" (value 2, poll backend, available everywhere except on windows)" 4 |
595 | .el .IP "\f(CWEVBACKEND_POLL\fR (value 2, poll backend, available everywhere except on windows)" 4 |
642 | .el .IP "\f(CWEVBACKEND_POLL\fR (value 2, poll backend, available everywhere except on windows)" 4 |
596 | .IX Item "EVBACKEND_POLL (value 2, poll backend, available everywhere except on windows)" |
643 | .IX Item "EVBACKEND_POLL (value 2, poll backend, available everywhere except on windows)" |
597 | And this is your standard \fIpoll\fR\|(2) backend. It's more complicated |
644 | And this is your standard \fBpoll\fR\|(2) backend. It's more complicated |
598 | than select, but handles sparse fds better and has no artificial |
645 | than select, but handles sparse fds better and has no artificial |
599 | limit on the number of fds you can use (except it will slow down |
646 | limit on the number of fds you can use (except it will slow down |
600 | considerably with a lot of inactive fds). It scales similarly to select, |
647 | considerably with a lot of inactive fds). It scales similarly to select, |
601 | i.e. O(total_fds). See the entry for \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR, above, for |
648 | i.e. O(total_fds). See the entry for \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR, above, for |
602 | performance tips. |
649 | performance tips. |
603 | .Sp |
650 | .Sp |
604 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR to \f(CW\*(C`POLLIN | POLLERR | POLLHUP\*(C'\fR, and |
651 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR to \f(CW\*(C`POLLIN | POLLERR | POLLHUP\*(C'\fR, and |
605 | \&\f(CW\*(C`EV_WRITE\*(C'\fR to \f(CW\*(C`POLLOUT | POLLERR | POLLHUP\*(C'\fR. |
652 | \&\f(CW\*(C`EV_WRITE\*(C'\fR to \f(CW\*(C`POLLOUT | POLLERR | POLLHUP\*(C'\fR. |
606 | .ie n .IP """EVBACKEND_EPOLL"" (value 4, Linux)" 4 |
653 | .ie n .IP """EVBACKEND_EPOLL"" (value 4, Linux)" 4 |
607 | .el .IP "\f(CWEVBACKEND_EPOLL\fR (value 4, Linux)" 4 |
654 | .el .IP "\f(CWEVBACKEND_EPOLL\fR (value 4, Linux)" 4 |
608 | .IX Item "EVBACKEND_EPOLL (value 4, Linux)" |
655 | .IX Item "EVBACKEND_EPOLL (value 4, Linux)" |
609 | Use the linux-specific \fIepoll\fR\|(7) interface (for both pre\- and post\-2.6.9 |
656 | Use the Linux-specific \fBepoll\fR\|(7) interface (for both pre\- and post\-2.6.9 |
610 | kernels). |
657 | kernels). |
611 | .Sp |
658 | .Sp |
612 | For few fds, this backend is a bit little slower than poll and select, but |
659 | For few fds, this backend is a bit little slower than poll and select, but |
613 | it scales phenomenally better. While poll and select usually scale like |
660 | it scales phenomenally better. While poll and select usually scale like |
614 | O(total_fds) where total_fds is the total number of fds (or the highest |
661 | O(total_fds) where total_fds is the total number of fds (or the highest |
… | |
… | |
660 | All this means that, in practice, \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR can be as fast or |
707 | All this means that, in practice, \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR can be as fast or |
661 | faster than epoll for maybe up to a hundred file descriptors, depending on |
708 | faster than epoll for maybe up to a hundred file descriptors, depending on |
662 | the usage. So sad. |
709 | the usage. So sad. |
663 | .Sp |
710 | .Sp |
664 | While nominally embeddable in other event loops, this feature is broken in |
711 | While nominally embeddable in other event loops, this feature is broken in |
665 | all kernel versions tested so far. |
712 | a lot of kernel revisions, but probably(!) works in current versions. |
|
|
713 | .Sp |
|
|
714 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR and \f(CW\*(C`EV_WRITE\*(C'\fR in the same way as |
|
|
715 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
|
|
716 | .ie n .IP """EVBACKEND_LINUXAIO"" (value 64, Linux)" 4 |
|
|
717 | .el .IP "\f(CWEVBACKEND_LINUXAIO\fR (value 64, Linux)" 4 |
|
|
718 | .IX Item "EVBACKEND_LINUXAIO (value 64, Linux)" |
|
|
719 | Use the Linux-specific Linux \s-1AIO\s0 (\fInot\fR \f(CWaio(7)\fR but \f(CWio_submit(2)\fR) event interface available in post\-4.18 kernels (but libev |
|
|
720 | only tries to use it in 4.19+). |
|
|
721 | .Sp |
|
|
722 | This is another Linux train wreck of an event interface. |
|
|
723 | .Sp |
|
|
724 | If this backend works for you (as of this writing, it was very |
|
|
725 | experimental), it is the best event interface available on Linux and might |
|
|
726 | be well worth enabling it \- if it isn't available in your kernel this will |
|
|
727 | be detected and this backend will be skipped. |
|
|
728 | .Sp |
|
|
729 | This backend can batch oneshot requests and supports a user-space ring |
|
|
730 | buffer to receive events. It also doesn't suffer from most of the design |
|
|
731 | problems of epoll (such as not being able to remove event sources from |
|
|
732 | the epoll set), and generally sounds too good to be true. Because, this |
|
|
733 | being the Linux kernel, of course it suffers from a whole new set of |
|
|
734 | limitations, forcing you to fall back to epoll, inheriting all its design |
|
|
735 | issues. |
|
|
736 | .Sp |
|
|
737 | For one, it is not easily embeddable (but probably could be done using |
|
|
738 | an event fd at some extra overhead). It also is subject to a system wide |
|
|
739 | limit that can be configured in \fI/proc/sys/fs/aio\-max\-nr\fR. If no \s-1AIO\s0 |
|
|
740 | requests are left, this backend will be skipped during initialisation, and |
|
|
741 | will switch to epoll when the loop is active. |
|
|
742 | .Sp |
|
|
743 | Most problematic in practice, however, is that not all file descriptors |
|
|
744 | work with it. For example, in Linux 5.1, \s-1TCP\s0 sockets, pipes, event fds, |
|
|
745 | files, \fI/dev/null\fR and many others are supported, but ttys do not work |
|
|
746 | properly (a known bug that the kernel developers don't care about, see |
|
|
747 | <https://lore.kernel.org/patchwork/patch/1047453/>), so this is not |
|
|
748 | (yet?) a generic event polling interface. |
|
|
749 | .Sp |
|
|
750 | Overall, it seems the Linux developers just don't want it to have a |
|
|
751 | generic event handling mechanism other than \f(CW\*(C`select\*(C'\fR or \f(CW\*(C`poll\*(C'\fR. |
|
|
752 | .Sp |
|
|
753 | To work around all these problem, the current version of libev uses its |
|
|
754 | epoll backend as a fallback for file descriptor types that do not work. Or |
|
|
755 | falls back completely to epoll if the kernel acts up. |
666 | .Sp |
756 | .Sp |
667 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR and \f(CW\*(C`EV_WRITE\*(C'\fR in the same way as |
757 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR and \f(CW\*(C`EV_WRITE\*(C'\fR in the same way as |
668 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
758 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
669 | .ie n .IP """EVBACKEND_KQUEUE"" (value 8, most \s-1BSD\s0 clones)" 4 |
759 | .ie n .IP """EVBACKEND_KQUEUE"" (value 8, most \s-1BSD\s0 clones)" 4 |
670 | .el .IP "\f(CWEVBACKEND_KQUEUE\fR (value 8, most \s-1BSD\s0 clones)" 4 |
760 | .el .IP "\f(CWEVBACKEND_KQUEUE\fR (value 8, most \s-1BSD\s0 clones)" 4 |
671 | .IX Item "EVBACKEND_KQUEUE (value 8, most BSD clones)" |
761 | .IX Item "EVBACKEND_KQUEUE (value 8, most BSD clones)" |
672 | Kqueue deserves special mention, as at the time of this writing, it |
762 | Kqueue deserves special mention, as at the time this backend was |
673 | was broken on all BSDs except NetBSD (usually it doesn't work reliably |
763 | implemented, it was broken on all BSDs except NetBSD (usually it doesn't |
674 | with anything but sockets and pipes, except on Darwin, where of course |
764 | work reliably with anything but sockets and pipes, except on Darwin, |
675 | it's completely useless). Unlike epoll, however, whose brokenness |
765 | where of course it's completely useless). Unlike epoll, however, whose |
676 | is by design, these kqueue bugs can (and eventually will) be fixed |
766 | brokenness is by design, these kqueue bugs can be (and mostly have been) |
677 | without \s-1API\s0 changes to existing programs. For this reason it's not being |
767 | fixed without \s-1API\s0 changes to existing programs. For this reason it's not |
678 | \&\*(L"auto-detected\*(R" unless you explicitly specify it in the flags (i.e. using |
768 | being \*(L"auto-detected\*(R" on all platforms unless you explicitly specify it |
679 | \&\f(CW\*(C`EVBACKEND_KQUEUE\*(C'\fR) or libev was compiled on a known-to-be-good (\-enough) |
769 | in the flags (i.e. using \f(CW\*(C`EVBACKEND_KQUEUE\*(C'\fR) or libev was compiled on a |
680 | system like NetBSD. |
770 | known-to-be-good (\-enough) system like NetBSD. |
681 | .Sp |
771 | .Sp |
682 | You still can embed kqueue into a normal poll or select backend and use it |
772 | You still can embed kqueue into a normal poll or select backend and use it |
683 | only for sockets (after having made sure that sockets work with kqueue on |
773 | only for sockets (after having made sure that sockets work with kqueue on |
684 | the target platform). See \f(CW\*(C`ev_embed\*(C'\fR watchers for more info. |
774 | the target platform). See \f(CW\*(C`ev_embed\*(C'\fR watchers for more info. |
685 | .Sp |
775 | .Sp |
686 | It scales in the same way as the epoll backend, but the interface to the |
776 | It scales in the same way as the epoll backend, but the interface to the |
687 | kernel is more efficient (which says nothing about its actual speed, of |
777 | kernel is more efficient (which says nothing about its actual speed, of |
688 | course). While stopping, setting and starting an I/O watcher does never |
778 | course). While stopping, setting and starting an I/O watcher does never |
689 | cause an extra system call as with \f(CW\*(C`EVBACKEND_EPOLL\*(C'\fR, it still adds up to |
779 | cause an extra system call as with \f(CW\*(C`EVBACKEND_EPOLL\*(C'\fR, it still adds up to |
690 | two event changes per incident. Support for \f(CW\*(C`fork ()\*(C'\fR is very bad (you |
780 | two event changes per incident. Support for \f(CW\*(C`fork ()\*(C'\fR is very bad (you |
691 | might have to leak fd's on fork, but it's more sane than epoll) and it |
781 | might have to leak fds on fork, but it's more sane than epoll) and it |
692 | drops fds silently in similarly hard-to-detect cases |
782 | drops fds silently in similarly hard-to-detect cases. |
693 | .Sp |
783 | .Sp |
694 | This backend usually performs well under most conditions. |
784 | This backend usually performs well under most conditions. |
695 | .Sp |
785 | .Sp |
696 | While nominally embeddable in other event loops, this doesn't work |
786 | While nominally embeddable in other event loops, this doesn't work |
697 | everywhere, so you might need to test for this. And since it is broken |
787 | everywhere, so you might need to test for this. And since it is broken |
698 | almost everywhere, you should only use it when you have a lot of sockets |
788 | almost everywhere, you should only use it when you have a lot of sockets |
699 | (for which it usually works), by embedding it into another event loop |
789 | (for which it usually works), by embedding it into another event loop |
700 | (e.g. \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or \f(CW\*(C`EVBACKEND_POLL\*(C'\fR (but \f(CW\*(C`poll\*(C'\fR is of course |
790 | (e.g. \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or \f(CW\*(C`EVBACKEND_POLL\*(C'\fR (but \f(CW\*(C`poll\*(C'\fR is of course |
701 | also broken on \s-1OS\s0 X)) and, did I mention it, using it only for sockets. |
791 | also broken on \s-1OS X\s0)) and, did I mention it, using it only for sockets. |
702 | .Sp |
792 | .Sp |
703 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR into an \f(CW\*(C`EVFILT_READ\*(C'\fR kevent with |
793 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR into an \f(CW\*(C`EVFILT_READ\*(C'\fR kevent with |
704 | \&\f(CW\*(C`NOTE_EOF\*(C'\fR, and \f(CW\*(C`EV_WRITE\*(C'\fR into an \f(CW\*(C`EVFILT_WRITE\*(C'\fR kevent with |
794 | \&\f(CW\*(C`NOTE_EOF\*(C'\fR, and \f(CW\*(C`EV_WRITE\*(C'\fR into an \f(CW\*(C`EVFILT_WRITE\*(C'\fR kevent with |
705 | \&\f(CW\*(C`NOTE_EOF\*(C'\fR. |
795 | \&\f(CW\*(C`NOTE_EOF\*(C'\fR. |
706 | .ie n .IP """EVBACKEND_DEVPOLL"" (value 16, Solaris 8)" 4 |
796 | .ie n .IP """EVBACKEND_DEVPOLL"" (value 16, Solaris 8)" 4 |
… | |
… | |
710 | implementation). According to reports, \f(CW\*(C`/dev/poll\*(C'\fR only supports sockets |
800 | implementation). According to reports, \f(CW\*(C`/dev/poll\*(C'\fR only supports sockets |
711 | and is not embeddable, which would limit the usefulness of this backend |
801 | and is not embeddable, which would limit the usefulness of this backend |
712 | immensely. |
802 | immensely. |
713 | .ie n .IP """EVBACKEND_PORT"" (value 32, Solaris 10)" 4 |
803 | .ie n .IP """EVBACKEND_PORT"" (value 32, Solaris 10)" 4 |
714 | .el .IP "\f(CWEVBACKEND_PORT\fR (value 32, Solaris 10)" 4 |
804 | .el .IP "\f(CWEVBACKEND_PORT\fR (value 32, Solaris 10)" 4 |
715 | .IX Item "EVBACKEND_PORT (value 32, Solaris 10)" |
805 | .IX Item "EVBACKEND_PORT (value 32, Solaris 10)" |
716 | This uses the Solaris 10 event port mechanism. As with everything on Solaris, |
806 | This uses the Solaris 10 event port mechanism. As with everything on Solaris, |
717 | it's really slow, but it still scales very well (O(active_fds)). |
807 | it's really slow, but it still scales very well (O(active_fds)). |
718 | .Sp |
808 | .Sp |
719 | While this backend scales well, it requires one system call per active |
809 | While this backend scales well, it requires one system call per active |
720 | file descriptor per loop iteration. For small and medium numbers of file |
810 | file descriptor per loop iteration. For small and medium numbers of file |
… | |
… | |
774 | used if available. |
864 | used if available. |
775 | .Sp |
865 | .Sp |
776 | .Vb 1 |
866 | .Vb 1 |
777 | \& struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_KQUEUE); |
867 | \& struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_KQUEUE); |
778 | .Ve |
868 | .Ve |
|
|
869 | .Sp |
|
|
870 | Example: Similarly, on linux, you mgiht want to take advantage of the |
|
|
871 | linux aio backend if possible, but fall back to something else if that |
|
|
872 | isn't available. |
|
|
873 | .Sp |
|
|
874 | .Vb 1 |
|
|
875 | \& struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_LINUXAIO); |
|
|
876 | .Ve |
779 | .RE |
877 | .RE |
780 | .IP "ev_loop_destroy (loop)" 4 |
878 | .IP "ev_loop_destroy (loop)" 4 |
781 | .IX Item "ev_loop_destroy (loop)" |
879 | .IX Item "ev_loop_destroy (loop)" |
782 | Destroys an event loop object (frees all memory and kernel state |
880 | Destroys an event loop object (frees all memory and kernel state |
783 | etc.). None of the active event watchers will be stopped in the normal |
881 | etc.). None of the active event watchers will be stopped in the normal |
… | |
… | |
799 | except in the rare occasion where you really need to free its resources. |
897 | except in the rare occasion where you really need to free its resources. |
800 | If you need dynamically allocated loops it is better to use \f(CW\*(C`ev_loop_new\*(C'\fR |
898 | If you need dynamically allocated loops it is better to use \f(CW\*(C`ev_loop_new\*(C'\fR |
801 | and \f(CW\*(C`ev_loop_destroy\*(C'\fR. |
899 | and \f(CW\*(C`ev_loop_destroy\*(C'\fR. |
802 | .IP "ev_loop_fork (loop)" 4 |
900 | .IP "ev_loop_fork (loop)" 4 |
803 | .IX Item "ev_loop_fork (loop)" |
901 | .IX Item "ev_loop_fork (loop)" |
804 | This function sets a flag that causes subsequent \f(CW\*(C`ev_run\*(C'\fR iterations to |
902 | This function sets a flag that causes subsequent \f(CW\*(C`ev_run\*(C'\fR iterations |
805 | reinitialise the kernel state for backends that have one. Despite the |
903 | to reinitialise the kernel state for backends that have one. Despite |
806 | name, you can call it anytime, but it makes most sense after forking, in |
904 | the name, you can call it anytime you are allowed to start or stop |
807 | the child process. You \fImust\fR call it (or use \f(CW\*(C`EVFLAG_FORKCHECK\*(C'\fR) in the |
905 | watchers (except inside an \f(CW\*(C`ev_prepare\*(C'\fR callback), but it makes most |
808 | child before resuming or calling \f(CW\*(C`ev_run\*(C'\fR. |
906 | sense after forking, in the child process. You \fImust\fR call it (or use |
|
|
907 | \&\f(CW\*(C`EVFLAG_FORKCHECK\*(C'\fR) in the child before resuming or calling \f(CW\*(C`ev_run\*(C'\fR. |
809 | .Sp |
908 | .Sp |
|
|
909 | In addition, if you want to reuse a loop (via this function or |
|
|
910 | \&\f(CW\*(C`EVFLAG_FORKCHECK\*(C'\fR), you \fIalso\fR have to ignore \f(CW\*(C`SIGPIPE\*(C'\fR. |
|
|
911 | .Sp |
810 | Again, you \fIhave\fR to call it on \fIany\fR loop that you want to re-use after |
912 | Again, you \fIhave\fR to call it on \fIany\fR loop that you want to re-use after |
811 | a fork, \fIeven if you do not plan to use the loop in the parent\fR. This is |
913 | a fork, \fIeven if you do not plan to use the loop in the parent\fR. This is |
812 | because some kernel interfaces *cough* \fIkqueue\fR *cough* do funny things |
914 | because some kernel interfaces *cough* \fIkqueue\fR *cough* do funny things |
813 | during fork. |
915 | during fork. |
814 | .Sp |
916 | .Sp |
815 | On the other hand, you only need to call this function in the child |
917 | On the other hand, you only need to call this function in the child |
… | |
… | |
985 | \& \- Queue all expired timers. |
1087 | \& \- Queue all expired timers. |
986 | \& \- Queue all expired periodics. |
1088 | \& \- Queue all expired periodics. |
987 | \& \- Queue all idle watchers with priority higher than that of pending events. |
1089 | \& \- Queue all idle watchers with priority higher than that of pending events. |
988 | \& \- Queue all check watchers. |
1090 | \& \- Queue all check watchers. |
989 | \& \- Call all queued watchers in reverse order (i.e. check watchers first). |
1091 | \& \- Call all queued watchers in reverse order (i.e. check watchers first). |
990 | \& Signals and child watchers are implemented as I/O watchers, and will |
1092 | \& Signals, async and child watchers are implemented as I/O watchers, and |
991 | \& be handled here by queueing them when their watcher gets executed. |
1093 | \& will be handled here by queueing them when their watcher gets executed. |
992 | \& \- If ev_break has been called, or EVRUN_ONCE or EVRUN_NOWAIT |
1094 | \& \- If ev_break has been called, or EVRUN_ONCE or EVRUN_NOWAIT |
993 | \& were used, or there are no active watchers, goto FINISH, otherwise |
1095 | \& were used, or there are no active watchers, goto FINISH, otherwise |
994 | \& continue with step LOOP. |
1096 | \& continue with step LOOP. |
995 | \& FINISH: |
1097 | \& FINISH: |
996 | \& \- Reset the ev_break status iff it was EVBREAK_ONE. |
1098 | \& \- Reset the ev_break status iff it was EVBREAK_ONE. |
… | |
… | |
1247 | with a watcher-specific start function (\f(CW\*(C`ev_TYPE_start (loop, watcher |
1349 | with a watcher-specific start function (\f(CW\*(C`ev_TYPE_start (loop, watcher |
1248 | *)\*(C'\fR), and you can stop watching for events at any time by calling the |
1350 | *)\*(C'\fR), and you can stop watching for events at any time by calling the |
1249 | corresponding stop function (\f(CW\*(C`ev_TYPE_stop (loop, watcher *)\*(C'\fR. |
1351 | corresponding stop function (\f(CW\*(C`ev_TYPE_stop (loop, watcher *)\*(C'\fR. |
1250 | .PP |
1352 | .PP |
1251 | As long as your watcher is active (has been started but not stopped) you |
1353 | As long as your watcher is active (has been started but not stopped) you |
1252 | must not touch the values stored in it. Most specifically you must never |
1354 | must not touch the values stored in it except when explicitly documented |
1253 | reinitialise it or call its \f(CW\*(C`ev_TYPE_set\*(C'\fR macro. |
1355 | otherwise. Most specifically you must never reinitialise it or call its |
|
|
1356 | \&\f(CW\*(C`ev_TYPE_set\*(C'\fR macro. |
1254 | .PP |
1357 | .PP |
1255 | Each and every callback receives the event loop pointer as first, the |
1358 | Each and every callback receives the event loop pointer as first, the |
1256 | registered watcher structure as second, and a bitset of received events as |
1359 | registered watcher structure as second, and a bitset of received events as |
1257 | third argument. |
1360 | third argument. |
1258 | .PP |
1361 | .PP |
… | |
… | |
1349 | bug in your program. |
1452 | bug in your program. |
1350 | .Sp |
1453 | .Sp |
1351 | Libev will usually signal a few \*(L"dummy\*(R" events together with an error, for |
1454 | Libev will usually signal a few \*(L"dummy\*(R" events together with an error, for |
1352 | example it might indicate that a fd is readable or writable, and if your |
1455 | example it might indicate that a fd is readable or writable, and if your |
1353 | callbacks is well-written it can just attempt the operation and cope with |
1456 | callbacks is well-written it can just attempt the operation and cope with |
1354 | the error from \fIread()\fR or \fIwrite()\fR. This will not work in multi-threaded |
1457 | the error from \fBread()\fR or \fBwrite()\fR. This will not work in multi-threaded |
1355 | programs, though, as the fd could already be closed and reused for another |
1458 | programs, though, as the fd could already be closed and reused for another |
1356 | thing, so beware. |
1459 | thing, so beware. |
1357 | .SS "\s-1GENERIC\s0 \s-1WATCHER\s0 \s-1FUNCTIONS\s0" |
1460 | .SS "\s-1GENERIC WATCHER FUNCTIONS\s0" |
1358 | .IX Subsection "GENERIC WATCHER FUNCTIONS" |
1461 | .IX Subsection "GENERIC WATCHER FUNCTIONS" |
1359 | .ie n .IP """ev_init"" (ev_TYPE *watcher, callback)" 4 |
1462 | .ie n .IP """ev_init"" (ev_TYPE *watcher, callback)" 4 |
1360 | .el .IP "\f(CWev_init\fR (ev_TYPE *watcher, callback)" 4 |
1463 | .el .IP "\f(CWev_init\fR (ev_TYPE *watcher, callback)" 4 |
1361 | .IX Item "ev_init (ev_TYPE *watcher, callback)" |
1464 | .IX Item "ev_init (ev_TYPE *watcher, callback)" |
1362 | This macro initialises the generic portion of a watcher. The contents |
1465 | This macro initialises the generic portion of a watcher. The contents |
… | |
… | |
1429 | therefore a good idea to always call its \f(CW\*(C`ev_TYPE_stop\*(C'\fR function. |
1532 | therefore a good idea to always call its \f(CW\*(C`ev_TYPE_stop\*(C'\fR function. |
1430 | .IP "bool ev_is_active (ev_TYPE *watcher)" 4 |
1533 | .IP "bool ev_is_active (ev_TYPE *watcher)" 4 |
1431 | .IX Item "bool ev_is_active (ev_TYPE *watcher)" |
1534 | .IX Item "bool ev_is_active (ev_TYPE *watcher)" |
1432 | Returns a true value iff the watcher is active (i.e. it has been started |
1535 | Returns a true value iff the watcher is active (i.e. it has been started |
1433 | and not yet been stopped). As long as a watcher is active you must not modify |
1536 | and not yet been stopped). As long as a watcher is active you must not modify |
1434 | it. |
1537 | it unless documented otherwise. |
1435 | .IP "bool ev_is_pending (ev_TYPE *watcher)" 4 |
1538 | .IP "bool ev_is_pending (ev_TYPE *watcher)" 4 |
1436 | .IX Item "bool ev_is_pending (ev_TYPE *watcher)" |
1539 | .IX Item "bool ev_is_pending (ev_TYPE *watcher)" |
1437 | Returns a true value iff the watcher is pending, (i.e. it has outstanding |
1540 | Returns a true value iff the watcher is pending, (i.e. it has outstanding |
1438 | events but its callback has not yet been invoked). As long as a watcher |
1541 | events but its callback has not yet been invoked). As long as a watcher |
1439 | is pending (but not active) you must not call an init function on it (but |
1542 | is pending (but not active) you must not call an init function on it (but |
… | |
… | |
1470 | or might not have been clamped to the valid range. |
1573 | or might not have been clamped to the valid range. |
1471 | .Sp |
1574 | .Sp |
1472 | The default priority used by watchers when no priority has been set is |
1575 | The default priority used by watchers when no priority has been set is |
1473 | always \f(CW0\fR, which is supposed to not be too high and not be too low :). |
1576 | always \f(CW0\fR, which is supposed to not be too high and not be too low :). |
1474 | .Sp |
1577 | .Sp |
1475 | See \*(L"\s-1WATCHER\s0 \s-1PRIORITY\s0 \s-1MODELS\s0\*(R", below, for a more thorough treatment of |
1578 | See \*(L"\s-1WATCHER PRIORITY MODELS\*(R"\s0, below, for a more thorough treatment of |
1476 | priorities. |
1579 | priorities. |
1477 | .IP "ev_invoke (loop, ev_TYPE *watcher, int revents)" 4 |
1580 | .IP "ev_invoke (loop, ev_TYPE *watcher, int revents)" 4 |
1478 | .IX Item "ev_invoke (loop, ev_TYPE *watcher, int revents)" |
1581 | .IX Item "ev_invoke (loop, ev_TYPE *watcher, int revents)" |
1479 | Invoke the \f(CW\*(C`watcher\*(C'\fR with the given \f(CW\*(C`loop\*(C'\fR and \f(CW\*(C`revents\*(C'\fR. Neither |
1582 | Invoke the \f(CW\*(C`watcher\*(C'\fR with the given \f(CW\*(C`loop\*(C'\fR and \f(CW\*(C`revents\*(C'\fR. Neither |
1480 | \&\f(CW\*(C`loop\*(C'\fR nor \f(CW\*(C`revents\*(C'\fR need to be valid as long as the watcher callback |
1583 | \&\f(CW\*(C`loop\*(C'\fR nor \f(CW\*(C`revents\*(C'\fR need to be valid as long as the watcher callback |
… | |
… | |
1500 | not started in the first place. |
1603 | not started in the first place. |
1501 | .Sp |
1604 | .Sp |
1502 | See also \f(CW\*(C`ev_feed_fd_event\*(C'\fR and \f(CW\*(C`ev_feed_signal_event\*(C'\fR for related |
1605 | See also \f(CW\*(C`ev_feed_fd_event\*(C'\fR and \f(CW\*(C`ev_feed_signal_event\*(C'\fR for related |
1503 | functions that do not need a watcher. |
1606 | functions that do not need a watcher. |
1504 | .PP |
1607 | .PP |
1505 | See also the \*(L"\s-1ASSOCIATING\s0 \s-1CUSTOM\s0 \s-1DATA\s0 \s-1WITH\s0 A \s-1WATCHER\s0\*(R" and \*(L"\s-1BUILDING\s0 \s-1YOUR\s0 |
1608 | See also the \*(L"\s-1ASSOCIATING CUSTOM DATA WITH A WATCHER\*(R"\s0 and \*(L"\s-1BUILDING YOUR |
1506 | \&\s-1OWN\s0 \s-1COMPOSITE\s0 \s-1WATCHERS\s0\*(R" idioms. |
1609 | OWN COMPOSITE WATCHERS\*(R"\s0 idioms. |
1507 | .SS "\s-1WATCHER\s0 \s-1STATES\s0" |
1610 | .SS "\s-1WATCHER STATES\s0" |
1508 | .IX Subsection "WATCHER STATES" |
1611 | .IX Subsection "WATCHER STATES" |
1509 | There are various watcher states mentioned throughout this manual \- |
1612 | There are various watcher states mentioned throughout this manual \- |
1510 | active, pending and so on. In this section these states and the rules to |
1613 | active, pending and so on. In this section these states and the rules to |
1511 | transition between them will be described in more detail \- and while these |
1614 | transition between them will be described in more detail \- and while these |
1512 | rules might look complicated, they usually do \*(L"the right thing\*(R". |
1615 | rules might look complicated, they usually do \*(L"the right thing\*(R". |
1513 | .IP "initialiased" 4 |
1616 | .IP "initialised" 4 |
1514 | .IX Item "initialiased" |
1617 | .IX Item "initialised" |
1515 | Before a watcher can be registered with the event loop it has to be |
1618 | Before a watcher can be registered with the event loop it has to be |
1516 | initialised. This can be done with a call to \f(CW\*(C`ev_TYPE_init\*(C'\fR, or calls to |
1619 | initialised. This can be done with a call to \f(CW\*(C`ev_TYPE_init\*(C'\fR, or calls to |
1517 | \&\f(CW\*(C`ev_init\*(C'\fR followed by the watcher-specific \f(CW\*(C`ev_TYPE_set\*(C'\fR function. |
1620 | \&\f(CW\*(C`ev_init\*(C'\fR followed by the watcher-specific \f(CW\*(C`ev_TYPE_set\*(C'\fR function. |
1518 | .Sp |
1621 | .Sp |
1519 | In this state it is simply some block of memory that is suitable for |
1622 | In this state it is simply some block of memory that is suitable for |
… | |
… | |
1555 | .Sp |
1658 | .Sp |
1556 | While stopped (and not pending) the watcher is essentially in the |
1659 | While stopped (and not pending) the watcher is essentially in the |
1557 | initialised state, that is, it can be reused, moved, modified in any way |
1660 | initialised state, that is, it can be reused, moved, modified in any way |
1558 | you wish (but when you trash the memory block, you need to \f(CW\*(C`ev_TYPE_init\*(C'\fR |
1661 | you wish (but when you trash the memory block, you need to \f(CW\*(C`ev_TYPE_init\*(C'\fR |
1559 | it again). |
1662 | it again). |
1560 | .SS "\s-1WATCHER\s0 \s-1PRIORITY\s0 \s-1MODELS\s0" |
1663 | .SS "\s-1WATCHER PRIORITY MODELS\s0" |
1561 | .IX Subsection "WATCHER PRIORITY MODELS" |
1664 | .IX Subsection "WATCHER PRIORITY MODELS" |
1562 | Many event loops support \fIwatcher priorities\fR, which are usually small |
1665 | Many event loops support \fIwatcher priorities\fR, which are usually small |
1563 | integers that influence the ordering of event callback invocation |
1666 | integers that influence the ordering of event callback invocation |
1564 | between watchers in some way, all else being equal. |
1667 | between watchers in some way, all else being equal. |
1565 | .PP |
1668 | .PP |
1566 | In libev, Watcher priorities can be set using \f(CW\*(C`ev_set_priority\*(C'\fR. See its |
1669 | In libev, watcher priorities can be set using \f(CW\*(C`ev_set_priority\*(C'\fR. See its |
1567 | description for the more technical details such as the actual priority |
1670 | description for the more technical details such as the actual priority |
1568 | range. |
1671 | range. |
1569 | .PP |
1672 | .PP |
1570 | There are two common ways how these these priorities are being interpreted |
1673 | There are two common ways how these these priorities are being interpreted |
1571 | by event loops: |
1674 | by event loops: |
… | |
… | |
1665 | .IX Header "WATCHER TYPES" |
1768 | .IX Header "WATCHER TYPES" |
1666 | This section describes each watcher in detail, but will not repeat |
1769 | This section describes each watcher in detail, but will not repeat |
1667 | information given in the last section. Any initialisation/set macros, |
1770 | information given in the last section. Any initialisation/set macros, |
1668 | functions and members specific to the watcher type are explained. |
1771 | functions and members specific to the watcher type are explained. |
1669 | .PP |
1772 | .PP |
1670 | Members are additionally marked with either \fI[read\-only]\fR, meaning that, |
1773 | Most members are additionally marked with either \fI[read\-only]\fR, meaning |
1671 | while the watcher is active, you can look at the member and expect some |
1774 | that, while the watcher is active, you can look at the member and expect |
1672 | sensible content, but you must not modify it (you can modify it while the |
1775 | some sensible content, but you must not modify it (you can modify it while |
1673 | watcher is stopped to your hearts content), or \fI[read\-write]\fR, which |
1776 | the watcher is stopped to your hearts content), or \fI[read\-write]\fR, which |
1674 | means you can expect it to have some sensible content while the watcher |
1777 | means you can expect it to have some sensible content while the watcher is |
1675 | is active, but you can also modify it. Modifying it may not do something |
1778 | active, but you can also modify it (within the same thread as the event |
|
|
1779 | loop, i.e. without creating data races). Modifying it may not do something |
1676 | sensible or take immediate effect (or do anything at all), but libev will |
1780 | sensible or take immediate effect (or do anything at all), but libev will |
1677 | not crash or malfunction in any way. |
1781 | not crash or malfunction in any way. |
|
|
1782 | .PP |
|
|
1783 | In any case, the documentation for each member will explain what the |
|
|
1784 | effects are, and if there are any additional access restrictions. |
1678 | .ie n .SS """ev_io"" \- is this file descriptor readable or writable?" |
1785 | .ie n .SS """ev_io"" \- is this file descriptor readable or writable?" |
1679 | .el .SS "\f(CWev_io\fP \- is this file descriptor readable or writable?" |
1786 | .el .SS "\f(CWev_io\fP \- is this file descriptor readable or writable?" |
1680 | .IX Subsection "ev_io - is this file descriptor readable or writable?" |
1787 | .IX Subsection "ev_io - is this file descriptor readable or writable?" |
1681 | I/O watchers check whether a file descriptor is readable or writable |
1788 | I/O watchers check whether a file descriptor is readable or writable |
1682 | in each iteration of the event loop, or, more precisely, when reading |
1789 | in each iteration of the event loop, or, more precisely, when reading |
… | |
… | |
1710 | But really, best use non-blocking mode. |
1817 | But really, best use non-blocking mode. |
1711 | .PP |
1818 | .PP |
1712 | \fIThe special problem of disappearing file descriptors\fR |
1819 | \fIThe special problem of disappearing file descriptors\fR |
1713 | .IX Subsection "The special problem of disappearing file descriptors" |
1820 | .IX Subsection "The special problem of disappearing file descriptors" |
1714 | .PP |
1821 | .PP |
1715 | Some backends (e.g. kqueue, epoll) need to be told about closing a file |
1822 | Some backends (e.g. kqueue, epoll, linuxaio) need to be told about closing |
1716 | descriptor (either due to calling \f(CW\*(C`close\*(C'\fR explicitly or any other means, |
1823 | a file descriptor (either due to calling \f(CW\*(C`close\*(C'\fR explicitly or any other |
1717 | such as \f(CW\*(C`dup2\*(C'\fR). The reason is that you register interest in some file |
1824 | means, such as \f(CW\*(C`dup2\*(C'\fR). The reason is that you register interest in some |
1718 | descriptor, but when it goes away, the operating system will silently drop |
1825 | file descriptor, but when it goes away, the operating system will silently |
1719 | this interest. If another file descriptor with the same number then is |
1826 | drop this interest. If another file descriptor with the same number then |
1720 | registered with libev, there is no efficient way to see that this is, in |
1827 | is registered with libev, there is no efficient way to see that this is, |
1721 | fact, a different file descriptor. |
1828 | in fact, a different file descriptor. |
1722 | .PP |
1829 | .PP |
1723 | To avoid having to explicitly tell libev about such cases, libev follows |
1830 | To avoid having to explicitly tell libev about such cases, libev follows |
1724 | the following policy: Each time \f(CW\*(C`ev_io_set\*(C'\fR is being called, libev |
1831 | the following policy: Each time \f(CW\*(C`ev_io_set\*(C'\fR is being called, libev |
1725 | will assume that this is potentially a new file descriptor, otherwise |
1832 | will assume that this is potentially a new file descriptor, otherwise |
1726 | it is assumed that the file descriptor stays the same. That means that |
1833 | it is assumed that the file descriptor stays the same. That means that |
… | |
… | |
1763 | wish to read \- you would first have to request some data. |
1870 | wish to read \- you would first have to request some data. |
1764 | .PP |
1871 | .PP |
1765 | Since files are typically not-so-well supported by advanced notification |
1872 | Since files are typically not-so-well supported by advanced notification |
1766 | mechanism, libev tries hard to emulate \s-1POSIX\s0 behaviour with respect |
1873 | mechanism, libev tries hard to emulate \s-1POSIX\s0 behaviour with respect |
1767 | to files, even though you should not use it. The reason for this is |
1874 | to files, even though you should not use it. The reason for this is |
1768 | convenience: sometimes you want to watch \s-1STDIN\s0 or \s-1STDOUT\s0, which is |
1875 | convenience: sometimes you want to watch \s-1STDIN\s0 or \s-1STDOUT,\s0 which is |
1769 | usually a tty, often a pipe, but also sometimes files or special devices |
1876 | usually a tty, often a pipe, but also sometimes files or special devices |
1770 | (for example, \f(CW\*(C`epoll\*(C'\fR on Linux works with \fI/dev/random\fR but not with |
1877 | (for example, \f(CW\*(C`epoll\*(C'\fR on Linux works with \fI/dev/random\fR but not with |
1771 | \&\fI/dev/urandom\fR), and even though the file might better be served with |
1878 | \&\fI/dev/urandom\fR), and even though the file might better be served with |
1772 | asynchronous I/O instead of with non-blocking I/O, it is still useful when |
1879 | asynchronous I/O instead of with non-blocking I/O, it is still useful when |
1773 | it \*(L"just works\*(R" instead of freezing. |
1880 | it \*(L"just works\*(R" instead of freezing. |
1774 | .PP |
1881 | .PP |
1775 | So avoid file descriptors pointing to files when you know it (e.g. use |
1882 | So avoid file descriptors pointing to files when you know it (e.g. use |
1776 | libeio), but use them when it is convenient, e.g. for \s-1STDIN/STDOUT\s0, or |
1883 | libeio), but use them when it is convenient, e.g. for \s-1STDIN/STDOUT,\s0 or |
1777 | when you rarely read from a file instead of from a socket, and want to |
1884 | when you rarely read from a file instead of from a socket, and want to |
1778 | reuse the same code path. |
1885 | reuse the same code path. |
1779 | .PP |
1886 | .PP |
1780 | \fIThe special problem of fork\fR |
1887 | \fIThe special problem of fork\fR |
1781 | .IX Subsection "The special problem of fork" |
1888 | .IX Subsection "The special problem of fork" |
1782 | .PP |
1889 | .PP |
1783 | Some backends (epoll, kqueue) do not support \f(CW\*(C`fork ()\*(C'\fR at all or exhibit |
1890 | Some backends (epoll, kqueue, linuxaio, iouring) do not support \f(CW\*(C`fork ()\*(C'\fR |
1784 | useless behaviour. Libev fully supports fork, but needs to be told about |
1891 | at all or exhibit useless behaviour. Libev fully supports fork, but needs |
1785 | it in the child if you want to continue to use it in the child. |
1892 | to be told about it in the child if you want to continue to use it in the |
|
|
1893 | child. |
1786 | .PP |
1894 | .PP |
1787 | To support fork in your child processes, you have to call \f(CW\*(C`ev_loop_fork |
1895 | To support fork in your child processes, you have to call \f(CW\*(C`ev_loop_fork |
1788 | ()\*(C'\fR after a fork in the child, enable \f(CW\*(C`EVFLAG_FORKCHECK\*(C'\fR, or resort to |
1896 | ()\*(C'\fR after a fork in the child, enable \f(CW\*(C`EVFLAG_FORKCHECK\*(C'\fR, or resort to |
1789 | \&\f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or \f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
1897 | \&\f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or \f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
1790 | .PP |
1898 | .PP |
1791 | \fIThe special problem of \s-1SIGPIPE\s0\fR |
1899 | \fIThe special problem of \s-1SIGPIPE\s0\fR |
1792 | .IX Subsection "The special problem of SIGPIPE" |
1900 | .IX Subsection "The special problem of SIGPIPE" |
1793 | .PP |
1901 | .PP |
1794 | While not really specific to libev, it is easy to forget about \f(CW\*(C`SIGPIPE\*(C'\fR: |
1902 | While not really specific to libev, it is easy to forget about \f(CW\*(C`SIGPIPE\*(C'\fR: |
1795 | when writing to a pipe whose other end has been closed, your program gets |
1903 | when writing to a pipe whose other end has been closed, your program gets |
1796 | sent a \s-1SIGPIPE\s0, which, by default, aborts your program. For most programs |
1904 | sent a \s-1SIGPIPE,\s0 which, by default, aborts your program. For most programs |
1797 | this is sensible behaviour, for daemons, this is usually undesirable. |
1905 | this is sensible behaviour, for daemons, this is usually undesirable. |
1798 | .PP |
1906 | .PP |
1799 | So when you encounter spurious, unexplained daemon exits, make sure you |
1907 | So when you encounter spurious, unexplained daemon exits, make sure you |
1800 | ignore \s-1SIGPIPE\s0 (and maybe make sure you log the exit status of your daemon |
1908 | ignore \s-1SIGPIPE\s0 (and maybe make sure you log the exit status of your daemon |
1801 | somewhere, as that would have given you a big clue). |
1909 | somewhere, as that would have given you a big clue). |
1802 | .PP |
1910 | .PP |
1803 | \fIThe special problem of \fIaccept()\fIing when you can't\fR |
1911 | \fIThe special problem of \f(BIaccept()\fIing when you can't\fR |
1804 | .IX Subsection "The special problem of accept()ing when you can't" |
1912 | .IX Subsection "The special problem of accept()ing when you can't" |
1805 | .PP |
1913 | .PP |
1806 | Many implementations of the \s-1POSIX\s0 \f(CW\*(C`accept\*(C'\fR function (for example, |
1914 | Many implementations of the \s-1POSIX\s0 \f(CW\*(C`accept\*(C'\fR function (for example, |
1807 | found in post\-2004 Linux) have the peculiar behaviour of not removing a |
1915 | found in post\-2004 Linux) have the peculiar behaviour of not removing a |
1808 | connection from the pending queue in all error cases. |
1916 | connection from the pending queue in all error cases. |
… | |
… | |
1847 | .PD 0 |
1955 | .PD 0 |
1848 | .IP "ev_io_set (ev_io *, int fd, int events)" 4 |
1956 | .IP "ev_io_set (ev_io *, int fd, int events)" 4 |
1849 | .IX Item "ev_io_set (ev_io *, int fd, int events)" |
1957 | .IX Item "ev_io_set (ev_io *, int fd, int events)" |
1850 | .PD |
1958 | .PD |
1851 | Configures an \f(CW\*(C`ev_io\*(C'\fR watcher. The \f(CW\*(C`fd\*(C'\fR is the file descriptor to |
1959 | Configures an \f(CW\*(C`ev_io\*(C'\fR watcher. The \f(CW\*(C`fd\*(C'\fR is the file descriptor to |
1852 | receive events for and \f(CW\*(C`events\*(C'\fR is either \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR or |
1960 | receive events for and \f(CW\*(C`events\*(C'\fR is either \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR, both |
1853 | \&\f(CW\*(C`EV_READ | EV_WRITE\*(C'\fR, to express the desire to receive the given events. |
1961 | \&\f(CW\*(C`EV_READ | EV_WRITE\*(C'\fR or \f(CW0\fR, to express the desire to receive the given |
|
|
1962 | events. |
|
|
1963 | .Sp |
|
|
1964 | Note that setting the \f(CW\*(C`events\*(C'\fR to \f(CW0\fR and starting the watcher is |
|
|
1965 | supported, but not specially optimized \- if your program sometimes happens |
|
|
1966 | to generate this combination this is fine, but if it is easy to avoid |
|
|
1967 | starting an io watcher watching for no events you should do so. |
|
|
1968 | .IP "ev_io_modify (ev_io *, int events)" 4 |
|
|
1969 | .IX Item "ev_io_modify (ev_io *, int events)" |
|
|
1970 | Similar to \f(CW\*(C`ev_io_set\*(C'\fR, but only changes the requested events. Using this |
|
|
1971 | might be faster with some backends, as libev can assume that the \f(CW\*(C`fd\*(C'\fR |
|
|
1972 | still refers to the same underlying file description, something it cannot |
|
|
1973 | do when using \f(CW\*(C`ev_io_set\*(C'\fR. |
1854 | .IP "int fd [read\-only]" 4 |
1974 | .IP "int fd [no\-modify]" 4 |
1855 | .IX Item "int fd [read-only]" |
1975 | .IX Item "int fd [no-modify]" |
1856 | The file descriptor being watched. |
1976 | The file descriptor being watched. While it can be read at any time, you |
|
|
1977 | must not modify this member even when the watcher is stopped \- always use |
|
|
1978 | \&\f(CW\*(C`ev_io_set\*(C'\fR for that. |
1857 | .IP "int events [read\-only]" 4 |
1979 | .IP "int events [no\-modify]" 4 |
1858 | .IX Item "int events [read-only]" |
1980 | .IX Item "int events [no-modify]" |
1859 | The events being watched. |
1981 | The set of events the fd is being watched for, among other flags. Remember |
|
|
1982 | that this is a bit set \- to test for \f(CW\*(C`EV_READ\*(C'\fR, use \f(CW\*(C`w\->events & |
|
|
1983 | EV_READ\*(C'\fR, and similarly for \f(CW\*(C`EV_WRITE\*(C'\fR. |
|
|
1984 | .Sp |
|
|
1985 | As with \f(CW\*(C`fd\*(C'\fR, you must not modify this member even when the watcher is |
|
|
1986 | stopped, always use \f(CW\*(C`ev_io_set\*(C'\fR or \f(CW\*(C`ev_io_modify\*(C'\fR for that. |
1860 | .PP |
1987 | .PP |
1861 | \fIExamples\fR |
1988 | \fIExamples\fR |
1862 | .IX Subsection "Examples" |
1989 | .IX Subsection "Examples" |
1863 | .PP |
1990 | .PP |
1864 | Example: Call \f(CW\*(C`stdin_readable_cb\*(C'\fR when \s-1STDIN_FILENO\s0 has become, well |
1991 | Example: Call \f(CW\*(C`stdin_readable_cb\*(C'\fR when \s-1STDIN_FILENO\s0 has become, well |
… | |
… | |
2150 | .PP |
2277 | .PP |
2151 | The relative timeouts are calculated relative to the \f(CW\*(C`ev_now ()\*(C'\fR |
2278 | The relative timeouts are calculated relative to the \f(CW\*(C`ev_now ()\*(C'\fR |
2152 | time. This is usually the right thing as this timestamp refers to the time |
2279 | time. This is usually the right thing as this timestamp refers to the time |
2153 | of the event triggering whatever timeout you are modifying/starting. If |
2280 | of the event triggering whatever timeout you are modifying/starting. If |
2154 | you suspect event processing to be delayed and you \fIneed\fR to base the |
2281 | you suspect event processing to be delayed and you \fIneed\fR to base the |
2155 | timeout on the current time, use something like this to adjust for this: |
2282 | timeout on the current time, use something like the following to adjust |
|
|
2283 | for it: |
2156 | .PP |
2284 | .PP |
2157 | .Vb 1 |
2285 | .Vb 1 |
2158 | \& ev_timer_set (&timer, after + ev_now () \- ev_time (), 0.); |
2286 | \& ev_timer_set (&timer, after + (ev_time () \- ev_now ()), 0.); |
2159 | .Ve |
2287 | .Ve |
2160 | .PP |
2288 | .PP |
2161 | If the event loop is suspended for a long time, you can also force an |
2289 | If the event loop is suspended for a long time, you can also force an |
2162 | update of the time returned by \f(CW\*(C`ev_now ()\*(C'\fR by calling \f(CW\*(C`ev_now_update |
2290 | update of the time returned by \f(CW\*(C`ev_now ()\*(C'\fR by calling \f(CW\*(C`ev_now_update |
2163 | ()\*(C'\fR. |
2291 | ()\*(C'\fR, although that will push the event time of all outstanding events |
|
|
2292 | further into the future. |
2164 | .PP |
2293 | .PP |
2165 | \fIThe special problem of unsynchronised clocks\fR |
2294 | \fIThe special problem of unsynchronised clocks\fR |
2166 | .IX Subsection "The special problem of unsynchronised clocks" |
2295 | .IX Subsection "The special problem of unsynchronised clocks" |
2167 | .PP |
2296 | .PP |
2168 | Modern systems have a variety of clocks \- libev itself uses the normal |
2297 | Modern systems have a variety of clocks \- libev itself uses the normal |
… | |
… | |
2233 | .IX Item "ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)" |
2362 | .IX Item "ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)" |
2234 | .PD 0 |
2363 | .PD 0 |
2235 | .IP "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" 4 |
2364 | .IP "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" 4 |
2236 | .IX Item "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" |
2365 | .IX Item "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" |
2237 | .PD |
2366 | .PD |
2238 | Configure the timer to trigger after \f(CW\*(C`after\*(C'\fR seconds. If \f(CW\*(C`repeat\*(C'\fR |
2367 | Configure the timer to trigger after \f(CW\*(C`after\*(C'\fR seconds (fractional and |
2239 | is \f(CW0.\fR, then it will automatically be stopped once the timeout is |
2368 | negative values are supported). If \f(CW\*(C`repeat\*(C'\fR is \f(CW0.\fR, then it will |
2240 | reached. If it is positive, then the timer will automatically be |
2369 | automatically be stopped once the timeout is reached. If it is positive, |
2241 | configured to trigger again \f(CW\*(C`repeat\*(C'\fR seconds later, again, and again, |
2370 | then the timer will automatically be configured to trigger again \f(CW\*(C`repeat\*(C'\fR |
2242 | until stopped manually. |
2371 | seconds later, again, and again, until stopped manually. |
2243 | .Sp |
2372 | .Sp |
2244 | The timer itself will do a best-effort at avoiding drift, that is, if |
2373 | The timer itself will do a best-effort at avoiding drift, that is, if |
2245 | you configure a timer to trigger every 10 seconds, then it will normally |
2374 | you configure a timer to trigger every 10 seconds, then it will normally |
2246 | trigger at exactly 10 second intervals. If, however, your program cannot |
2375 | trigger at exactly 10 second intervals. If, however, your program cannot |
2247 | keep up with the timer (because it takes longer than those 10 seconds to |
2376 | keep up with the timer (because it takes longer than those 10 seconds to |
… | |
… | |
2329 | Periodic watchers are also timers of a kind, but they are very versatile |
2458 | Periodic watchers are also timers of a kind, but they are very versatile |
2330 | (and unfortunately a bit complex). |
2459 | (and unfortunately a bit complex). |
2331 | .PP |
2460 | .PP |
2332 | Unlike \f(CW\*(C`ev_timer\*(C'\fR, periodic watchers are not based on real time (or |
2461 | Unlike \f(CW\*(C`ev_timer\*(C'\fR, periodic watchers are not based on real time (or |
2333 | relative time, the physical time that passes) but on wall clock time |
2462 | relative time, the physical time that passes) but on wall clock time |
2334 | (absolute time, the thing you can read on your calender or clock). The |
2463 | (absolute time, the thing you can read on your calendar or clock). The |
2335 | difference is that wall clock time can run faster or slower than real |
2464 | difference is that wall clock time can run faster or slower than real |
2336 | time, and time jumps are not uncommon (e.g. when you adjust your |
2465 | time, and time jumps are not uncommon (e.g. when you adjust your |
2337 | wrist-watch). |
2466 | wrist-watch). |
2338 | .PP |
2467 | .PP |
2339 | You can tell a periodic watcher to trigger after some specific point |
2468 | You can tell a periodic watcher to trigger after some specific point |
… | |
… | |
2344 | \&\f(CW\*(C`ev_timer\*(C'\fR, which would still trigger roughly 10 seconds after starting |
2473 | \&\f(CW\*(C`ev_timer\*(C'\fR, which would still trigger roughly 10 seconds after starting |
2345 | it, as it uses a relative timeout). |
2474 | it, as it uses a relative timeout). |
2346 | .PP |
2475 | .PP |
2347 | \&\f(CW\*(C`ev_periodic\*(C'\fR watchers can also be used to implement vastly more complex |
2476 | \&\f(CW\*(C`ev_periodic\*(C'\fR watchers can also be used to implement vastly more complex |
2348 | timers, such as triggering an event on each \*(L"midnight, local time\*(R", or |
2477 | timers, such as triggering an event on each \*(L"midnight, local time\*(R", or |
2349 | other complicated rules. This cannot be done with \f(CW\*(C`ev_timer\*(C'\fR watchers, as |
2478 | other complicated rules. This cannot easily be done with \f(CW\*(C`ev_timer\*(C'\fR |
2350 | those cannot react to time jumps. |
2479 | watchers, as those cannot react to time jumps. |
2351 | .PP |
2480 | .PP |
2352 | As with timers, the callback is guaranteed to be invoked only when the |
2481 | As with timers, the callback is guaranteed to be invoked only when the |
2353 | point in time where it is supposed to trigger has passed. If multiple |
2482 | point in time where it is supposed to trigger has passed. If multiple |
2354 | timers become ready during the same loop iteration then the ones with |
2483 | timers become ready during the same loop iteration then the ones with |
2355 | earlier time-out values are invoked before ones with later time-out values |
2484 | earlier time-out values are invoked before ones with later time-out values |
… | |
… | |
2416 | In this mode the values for \f(CW\*(C`interval\*(C'\fR and \f(CW\*(C`offset\*(C'\fR are both being |
2545 | In this mode the values for \f(CW\*(C`interval\*(C'\fR and \f(CW\*(C`offset\*(C'\fR are both being |
2417 | ignored. Instead, each time the periodic watcher gets scheduled, the |
2546 | ignored. Instead, each time the periodic watcher gets scheduled, the |
2418 | reschedule callback will be called with the watcher as first, and the |
2547 | reschedule callback will be called with the watcher as first, and the |
2419 | current time as second argument. |
2548 | current time as second argument. |
2420 | .Sp |
2549 | .Sp |
2421 | \&\s-1NOTE:\s0 \fIThis callback \s-1MUST\s0 \s-1NOT\s0 stop or destroy any periodic watcher, ever, |
2550 | \&\s-1NOTE:\s0 \fIThis callback \s-1MUST NOT\s0 stop or destroy any periodic watcher, ever, |
2422 | or make \s-1ANY\s0 other event loop modifications whatsoever, unless explicitly |
2551 | or make \s-1ANY\s0 other event loop modifications whatsoever, unless explicitly |
2423 | allowed by documentation here\fR. |
2552 | allowed by documentation here\fR. |
2424 | .Sp |
2553 | .Sp |
2425 | If you need to stop it, return \f(CW\*(C`now + 1e30\*(C'\fR (or so, fudge fudge) and stop |
2554 | If you need to stop it, return \f(CW\*(C`now + 1e30\*(C'\fR (or so, fudge fudge) and stop |
2426 | it afterwards (e.g. by starting an \f(CW\*(C`ev_prepare\*(C'\fR watcher, which is the |
2555 | it afterwards (e.g. by starting an \f(CW\*(C`ev_prepare\*(C'\fR watcher, which is the |
… | |
… | |
2444 | .Sp |
2573 | .Sp |
2445 | \&\s-1NOTE:\s0 \fIThis callback must always return a time that is higher than or |
2574 | \&\s-1NOTE:\s0 \fIThis callback must always return a time that is higher than or |
2446 | equal to the passed \f(CI\*(C`now\*(C'\fI value\fR. |
2575 | equal to the passed \f(CI\*(C`now\*(C'\fI value\fR. |
2447 | .Sp |
2576 | .Sp |
2448 | This can be used to create very complex timers, such as a timer that |
2577 | This can be used to create very complex timers, such as a timer that |
2449 | triggers on \*(L"next midnight, local time\*(R". To do this, you would calculate the |
2578 | triggers on \*(L"next midnight, local time\*(R". To do this, you would calculate |
2450 | next midnight after \f(CW\*(C`now\*(C'\fR and return the timestamp value for this. How |
2579 | the next midnight after \f(CW\*(C`now\*(C'\fR and return the timestamp value for |
2451 | you do this is, again, up to you (but it is not trivial, which is the main |
2580 | this. Here is a (completely untested, no error checking) example on how to |
2452 | reason I omitted it as an example). |
2581 | do this: |
|
|
2582 | .Sp |
|
|
2583 | .Vb 1 |
|
|
2584 | \& #include <time.h> |
|
|
2585 | \& |
|
|
2586 | \& static ev_tstamp |
|
|
2587 | \& my_rescheduler (ev_periodic *w, ev_tstamp now) |
|
|
2588 | \& { |
|
|
2589 | \& time_t tnow = (time_t)now; |
|
|
2590 | \& struct tm tm; |
|
|
2591 | \& localtime_r (&tnow, &tm); |
|
|
2592 | \& |
|
|
2593 | \& tm.tm_sec = tm.tm_min = tm.tm_hour = 0; // midnight current day |
|
|
2594 | \& ++tm.tm_mday; // midnight next day |
|
|
2595 | \& |
|
|
2596 | \& return mktime (&tm); |
|
|
2597 | \& } |
|
|
2598 | .Ve |
|
|
2599 | .Sp |
|
|
2600 | Note: this code might run into trouble on days that have more then two |
|
|
2601 | midnights (beginning and end). |
2453 | .RE |
2602 | .RE |
2454 | .RS 4 |
2603 | .RS 4 |
2455 | .RE |
2604 | .RE |
2456 | .IP "ev_periodic_again (loop, ev_periodic *)" 4 |
2605 | .IP "ev_periodic_again (loop, ev_periodic *)" 4 |
2457 | .IX Item "ev_periodic_again (loop, ev_periodic *)" |
2606 | .IX Item "ev_periodic_again (loop, ev_periodic *)" |
… | |
… | |
2542 | only within the same loop, i.e. you can watch for \f(CW\*(C`SIGINT\*(C'\fR in your |
2691 | only within the same loop, i.e. you can watch for \f(CW\*(C`SIGINT\*(C'\fR in your |
2543 | default loop and for \f(CW\*(C`SIGIO\*(C'\fR in another loop, but you cannot watch for |
2692 | default loop and for \f(CW\*(C`SIGIO\*(C'\fR in another loop, but you cannot watch for |
2544 | \&\f(CW\*(C`SIGINT\*(C'\fR in both the default loop and another loop at the same time. At |
2693 | \&\f(CW\*(C`SIGINT\*(C'\fR in both the default loop and another loop at the same time. At |
2545 | the moment, \f(CW\*(C`SIGCHLD\*(C'\fR is permanently tied to the default loop. |
2694 | the moment, \f(CW\*(C`SIGCHLD\*(C'\fR is permanently tied to the default loop. |
2546 | .PP |
2695 | .PP |
2547 | When the first watcher gets started will libev actually register something |
2696 | Only after the first watcher for a signal is started will libev actually |
2548 | with the kernel (thus it coexists with your own signal handlers as long as |
2697 | register something with the kernel. It thus coexists with your own signal |
2549 | you don't register any with libev for the same signal). |
2698 | handlers as long as you don't register any with libev for the same signal. |
2550 | .PP |
2699 | .PP |
2551 | If possible and supported, libev will install its handlers with |
2700 | If possible and supported, libev will install its handlers with |
2552 | \&\f(CW\*(C`SA_RESTART\*(C'\fR (or equivalent) behaviour enabled, so system calls should |
2701 | \&\f(CW\*(C`SA_RESTART\*(C'\fR (or equivalent) behaviour enabled, so system calls should |
2553 | not be unduly interrupted. If you have a problem with system calls getting |
2702 | not be unduly interrupted. If you have a problem with system calls getting |
2554 | interrupted by signals you can block all signals in an \f(CW\*(C`ev_check\*(C'\fR watcher |
2703 | interrupted by signals you can block all signals in an \f(CW\*(C`ev_check\*(C'\fR watcher |
… | |
… | |
2615 | The signal the watcher watches out for. |
2764 | The signal the watcher watches out for. |
2616 | .PP |
2765 | .PP |
2617 | \fIExamples\fR |
2766 | \fIExamples\fR |
2618 | .IX Subsection "Examples" |
2767 | .IX Subsection "Examples" |
2619 | .PP |
2768 | .PP |
2620 | Example: Try to exit cleanly on \s-1SIGINT\s0. |
2769 | Example: Try to exit cleanly on \s-1SIGINT.\s0 |
2621 | .PP |
2770 | .PP |
2622 | .Vb 5 |
2771 | .Vb 5 |
2623 | \& static void |
2772 | \& static void |
2624 | \& sigint_cb (struct ev_loop *loop, ev_signal *w, int revents) |
2773 | \& sigint_cb (struct ev_loop *loop, ev_signal *w, int revents) |
2625 | \& { |
2774 | \& { |
… | |
… | |
2740 | .ie n .SS """ev_stat"" \- did the file attributes just change?" |
2889 | .ie n .SS """ev_stat"" \- did the file attributes just change?" |
2741 | .el .SS "\f(CWev_stat\fP \- did the file attributes just change?" |
2890 | .el .SS "\f(CWev_stat\fP \- did the file attributes just change?" |
2742 | .IX Subsection "ev_stat - did the file attributes just change?" |
2891 | .IX Subsection "ev_stat - did the file attributes just change?" |
2743 | This watches a file system path for attribute changes. That is, it calls |
2892 | This watches a file system path for attribute changes. That is, it calls |
2744 | \&\f(CW\*(C`stat\*(C'\fR on that path in regular intervals (or when the \s-1OS\s0 says it changed) |
2893 | \&\f(CW\*(C`stat\*(C'\fR on that path in regular intervals (or when the \s-1OS\s0 says it changed) |
2745 | and sees if it changed compared to the last time, invoking the callback if |
2894 | and sees if it changed compared to the last time, invoking the callback |
2746 | it did. |
2895 | if it did. Starting the watcher \f(CW\*(C`stat\*(C'\fR's the file, so only changes that |
|
|
2896 | happen after the watcher has been started will be reported. |
2747 | .PP |
2897 | .PP |
2748 | The path does not need to exist: changing from \*(L"path exists\*(R" to \*(L"path does |
2898 | The path does not need to exist: changing from \*(L"path exists\*(R" to \*(L"path does |
2749 | not exist\*(R" is a status change like any other. The condition \*(L"path does not |
2899 | not exist\*(R" is a status change like any other. The condition \*(L"path does not |
2750 | exist\*(R" (or more correctly \*(L"path cannot be stat'ed\*(R") is signified by the |
2900 | exist\*(R" (or more correctly \*(L"path cannot be stat'ed\*(R") is signified by the |
2751 | \&\f(CW\*(C`st_nlink\*(C'\fR field being zero (which is otherwise always forced to be at |
2901 | \&\f(CW\*(C`st_nlink\*(C'\fR field being zero (which is otherwise always forced to be at |
… | |
… | |
2781 | compilation environment, which means that on systems with large file |
2931 | compilation environment, which means that on systems with large file |
2782 | support disabled by default, you get the 32 bit version of the stat |
2932 | support disabled by default, you get the 32 bit version of the stat |
2783 | structure. When using the library from programs that change the \s-1ABI\s0 to |
2933 | structure. When using the library from programs that change the \s-1ABI\s0 to |
2784 | use 64 bit file offsets the programs will fail. In that case you have to |
2934 | use 64 bit file offsets the programs will fail. In that case you have to |
2785 | compile libev with the same flags to get binary compatibility. This is |
2935 | compile libev with the same flags to get binary compatibility. This is |
2786 | obviously the case with any flags that change the \s-1ABI\s0, but the problem is |
2936 | obviously the case with any flags that change the \s-1ABI,\s0 but the problem is |
2787 | most noticeably displayed with ev_stat and large file support. |
2937 | most noticeably displayed with ev_stat and large file support. |
2788 | .PP |
2938 | .PP |
2789 | The solution for this is to lobby your distribution maker to make large |
2939 | The solution for this is to lobby your distribution maker to make large |
2790 | file interfaces available by default (as e.g. FreeBSD does) and not |
2940 | file interfaces available by default (as e.g. FreeBSD does) and not |
2791 | optional. Libev cannot simply switch on large file support because it has |
2941 | optional. Libev cannot simply switch on large file support because it has |
… | |
… | |
3036 | .IX Subsection "ev_prepare and ev_check - customise your event loop!" |
3186 | .IX Subsection "ev_prepare and ev_check - customise your event loop!" |
3037 | Prepare and check watchers are often (but not always) used in pairs: |
3187 | Prepare and check watchers are often (but not always) used in pairs: |
3038 | prepare watchers get invoked before the process blocks and check watchers |
3188 | prepare watchers get invoked before the process blocks and check watchers |
3039 | afterwards. |
3189 | afterwards. |
3040 | .PP |
3190 | .PP |
3041 | You \fImust not\fR call \f(CW\*(C`ev_run\*(C'\fR or similar functions that enter |
3191 | You \fImust not\fR call \f(CW\*(C`ev_run\*(C'\fR (or similar functions that enter the |
3042 | the current event loop from either \f(CW\*(C`ev_prepare\*(C'\fR or \f(CW\*(C`ev_check\*(C'\fR |
3192 | current event loop) or \f(CW\*(C`ev_loop_fork\*(C'\fR from either \f(CW\*(C`ev_prepare\*(C'\fR or |
3043 | watchers. Other loops than the current one are fine, however. The |
3193 | \&\f(CW\*(C`ev_check\*(C'\fR watchers. Other loops than the current one are fine, |
3044 | rationale behind this is that you do not need to check for recursion in |
3194 | however. The rationale behind this is that you do not need to check |
3045 | those watchers, i.e. the sequence will always be \f(CW\*(C`ev_prepare\*(C'\fR, blocking, |
3195 | for recursion in those watchers, i.e. the sequence will always be |
3046 | \&\f(CW\*(C`ev_check\*(C'\fR so if you have one watcher of each kind they will always be |
3196 | \&\f(CW\*(C`ev_prepare\*(C'\fR, blocking, \f(CW\*(C`ev_check\*(C'\fR so if you have one watcher of each |
3047 | called in pairs bracketing the blocking call. |
3197 | kind they will always be called in pairs bracketing the blocking call. |
3048 | .PP |
3198 | .PP |
3049 | Their main purpose is to integrate other event mechanisms into libev and |
3199 | Their main purpose is to integrate other event mechanisms into libev and |
3050 | their use is somewhat advanced. They could be used, for example, to track |
3200 | their use is somewhat advanced. They could be used, for example, to track |
3051 | variable changes, implement your own watchers, integrate net-snmp or a |
3201 | variable changes, implement your own watchers, integrate net-snmp or a |
3052 | coroutine library and lots more. They are also occasionally useful if |
3202 | coroutine library and lots more. They are also occasionally useful if |
… | |
… | |
3222 | .Ve |
3372 | .Ve |
3223 | .PP |
3373 | .PP |
3224 | Method 4: Do not use a prepare or check watcher because the module you |
3374 | Method 4: Do not use a prepare or check watcher because the module you |
3225 | want to embed is not flexible enough to support it. Instead, you can |
3375 | want to embed is not flexible enough to support it. Instead, you can |
3226 | override their poll function. The drawback with this solution is that the |
3376 | override their poll function. The drawback with this solution is that the |
3227 | main loop is now no longer controllable by \s-1EV\s0. The \f(CW\*(C`Glib::EV\*(C'\fR module uses |
3377 | main loop is now no longer controllable by \s-1EV.\s0 The \f(CW\*(C`Glib::EV\*(C'\fR module uses |
3228 | this approach, effectively embedding \s-1EV\s0 as a client into the horrible |
3378 | this approach, effectively embedding \s-1EV\s0 as a client into the horrible |
3229 | libglib event loop. |
3379 | libglib event loop. |
3230 | .PP |
3380 | .PP |
3231 | .Vb 4 |
3381 | .Vb 4 |
3232 | \& static gint |
3382 | \& static gint |
… | |
… | |
3316 | \fIWatcher-Specific Functions and Data Members\fR |
3466 | \fIWatcher-Specific Functions and Data Members\fR |
3317 | .IX Subsection "Watcher-Specific Functions and Data Members" |
3467 | .IX Subsection "Watcher-Specific Functions and Data Members" |
3318 | .IP "ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)" 4 |
3468 | .IP "ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)" 4 |
3319 | .IX Item "ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)" |
3469 | .IX Item "ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)" |
3320 | .PD 0 |
3470 | .PD 0 |
3321 | .IP "ev_embed_set (ev_embed *, callback, struct ev_loop *embedded_loop)" 4 |
3471 | .IP "ev_embed_set (ev_embed *, struct ev_loop *embedded_loop)" 4 |
3322 | .IX Item "ev_embed_set (ev_embed *, callback, struct ev_loop *embedded_loop)" |
3472 | .IX Item "ev_embed_set (ev_embed *, struct ev_loop *embedded_loop)" |
3323 | .PD |
3473 | .PD |
3324 | Configures the watcher to embed the given loop, which must be |
3474 | Configures the watcher to embed the given loop, which must be |
3325 | embeddable. If the callback is \f(CW0\fR, then \f(CW\*(C`ev_embed_sweep\*(C'\fR will be |
3475 | embeddable. If the callback is \f(CW0\fR, then \f(CW\*(C`ev_embed_sweep\*(C'\fR will be |
3326 | invoked automatically, otherwise it is the responsibility of the callback |
3476 | invoked automatically, otherwise it is the responsibility of the callback |
3327 | to invoke it (it will continue to be called until the sweep has been done, |
3477 | to invoke it (it will continue to be called until the sweep has been done, |
… | |
… | |
3346 | .PP |
3496 | .PP |
3347 | .Vb 3 |
3497 | .Vb 3 |
3348 | \& struct ev_loop *loop_hi = ev_default_init (0); |
3498 | \& struct ev_loop *loop_hi = ev_default_init (0); |
3349 | \& struct ev_loop *loop_lo = 0; |
3499 | \& struct ev_loop *loop_lo = 0; |
3350 | \& ev_embed embed; |
3500 | \& ev_embed embed; |
3351 | \& |
3501 | \& |
3352 | \& // see if there is a chance of getting one that works |
3502 | \& // see if there is a chance of getting one that works |
3353 | \& // (remember that a flags value of 0 means autodetection) |
3503 | \& // (remember that a flags value of 0 means autodetection) |
3354 | \& loop_lo = ev_embeddable_backends () & ev_recommended_backends () |
3504 | \& loop_lo = ev_embeddable_backends () & ev_recommended_backends () |
3355 | \& ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ()) |
3505 | \& ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ()) |
3356 | \& : 0; |
3506 | \& : 0; |
… | |
… | |
3372 | .PP |
3522 | .PP |
3373 | .Vb 3 |
3523 | .Vb 3 |
3374 | \& struct ev_loop *loop = ev_default_init (0); |
3524 | \& struct ev_loop *loop = ev_default_init (0); |
3375 | \& struct ev_loop *loop_socket = 0; |
3525 | \& struct ev_loop *loop_socket = 0; |
3376 | \& ev_embed embed; |
3526 | \& ev_embed embed; |
3377 | \& |
3527 | \& |
3378 | \& if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE) |
3528 | \& if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE) |
3379 | \& if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE)) |
3529 | \& if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE)) |
3380 | \& { |
3530 | \& { |
3381 | \& ev_embed_init (&embed, 0, loop_socket); |
3531 | \& ev_embed_init (&embed, 0, loop_socket); |
3382 | \& ev_embed_start (loop, &embed); |
3532 | \& ev_embed_start (loop, &embed); |
… | |
… | |
3390 | .ie n .SS """ev_fork"" \- the audacity to resume the event loop after a fork" |
3540 | .ie n .SS """ev_fork"" \- the audacity to resume the event loop after a fork" |
3391 | .el .SS "\f(CWev_fork\fP \- the audacity to resume the event loop after a fork" |
3541 | .el .SS "\f(CWev_fork\fP \- the audacity to resume the event loop after a fork" |
3392 | .IX Subsection "ev_fork - the audacity to resume the event loop after a fork" |
3542 | .IX Subsection "ev_fork - the audacity to resume the event loop after a fork" |
3393 | Fork watchers are called when a \f(CW\*(C`fork ()\*(C'\fR was detected (usually because |
3543 | Fork watchers are called when a \f(CW\*(C`fork ()\*(C'\fR was detected (usually because |
3394 | whoever is a good citizen cared to tell libev about it by calling |
3544 | whoever is a good citizen cared to tell libev about it by calling |
3395 | \&\f(CW\*(C`ev_default_fork\*(C'\fR or \f(CW\*(C`ev_loop_fork\*(C'\fR). The invocation is done before the |
3545 | \&\f(CW\*(C`ev_loop_fork\*(C'\fR). The invocation is done before the event loop blocks next |
3396 | event loop blocks next and before \f(CW\*(C`ev_check\*(C'\fR watchers are being called, |
3546 | and before \f(CW\*(C`ev_check\*(C'\fR watchers are being called, and only in the child |
3397 | and only in the child after the fork. If whoever good citizen calling |
3547 | after the fork. If whoever good citizen calling \f(CW\*(C`ev_default_fork\*(C'\fR cheats |
3398 | \&\f(CW\*(C`ev_default_fork\*(C'\fR cheats and calls it in the wrong process, the fork |
3548 | and calls it in the wrong process, the fork handlers will be invoked, too, |
3399 | handlers will be invoked, too, of course. |
3549 | of course. |
3400 | .PP |
3550 | .PP |
3401 | \fIThe special problem of life after fork \- how is it possible?\fR |
3551 | \fIThe special problem of life after fork \- how is it possible?\fR |
3402 | .IX Subsection "The special problem of life after fork - how is it possible?" |
3552 | .IX Subsection "The special problem of life after fork - how is it possible?" |
3403 | .PP |
3553 | .PP |
3404 | Most uses of \f(CW\*(C`fork()\*(C'\fR consist of forking, then some simple calls to set |
3554 | Most uses of \f(CW\*(C`fork ()\*(C'\fR consist of forking, then some simple calls to set |
3405 | up/change the process environment, followed by a call to \f(CW\*(C`exec()\*(C'\fR. This |
3555 | up/change the process environment, followed by a call to \f(CW\*(C`exec()\*(C'\fR. This |
3406 | sequence should be handled by libev without any problems. |
3556 | sequence should be handled by libev without any problems. |
3407 | .PP |
3557 | .PP |
3408 | This changes when the application actually wants to do event handling |
3558 | This changes when the application actually wants to do event handling |
3409 | in the child, or both parent in child, in effect \*(L"continuing\*(R" after the |
3559 | in the child, or both parent in child, in effect \*(L"continuing\*(R" after the |
… | |
… | |
3626 | is a time window between the event loop checking and resetting the async |
3776 | is a time window between the event loop checking and resetting the async |
3627 | notification, and the callback being invoked. |
3777 | notification, and the callback being invoked. |
3628 | .SH "OTHER FUNCTIONS" |
3778 | .SH "OTHER FUNCTIONS" |
3629 | .IX Header "OTHER FUNCTIONS" |
3779 | .IX Header "OTHER FUNCTIONS" |
3630 | There are some other functions of possible interest. Described. Here. Now. |
3780 | There are some other functions of possible interest. Described. Here. Now. |
3631 | .IP "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)" 4 |
3781 | .IP "ev_once (loop, int fd, int events, ev_tstamp timeout, callback, arg)" 4 |
3632 | .IX Item "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)" |
3782 | .IX Item "ev_once (loop, int fd, int events, ev_tstamp timeout, callback, arg)" |
3633 | This function combines a simple timer and an I/O watcher, calls your |
3783 | This function combines a simple timer and an I/O watcher, calls your |
3634 | callback on whichever event happens first and automatically stops both |
3784 | callback on whichever event happens first and automatically stops both |
3635 | watchers. This is useful if you want to wait for a single event on an fd |
3785 | watchers. This is useful if you want to wait for a single event on an fd |
3636 | or timeout without having to allocate/configure/start/stop/free one or |
3786 | or timeout without having to allocate/configure/start/stop/free one or |
3637 | more watchers yourself. |
3787 | more watchers yourself. |
… | |
… | |
3649 | \&\f(CW\*(C`EV_ERROR\*(C'\fR, \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR or \f(CW\*(C`EV_TIMER\*(C'\fR) and the \f(CW\*(C`arg\*(C'\fR |
3799 | \&\f(CW\*(C`EV_ERROR\*(C'\fR, \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR or \f(CW\*(C`EV_TIMER\*(C'\fR) and the \f(CW\*(C`arg\*(C'\fR |
3650 | value passed to \f(CW\*(C`ev_once\*(C'\fR. Note that it is possible to receive \fIboth\fR |
3800 | value passed to \f(CW\*(C`ev_once\*(C'\fR. Note that it is possible to receive \fIboth\fR |
3651 | a timeout and an io event at the same time \- you probably should give io |
3801 | a timeout and an io event at the same time \- you probably should give io |
3652 | events precedence. |
3802 | events precedence. |
3653 | .Sp |
3803 | .Sp |
3654 | Example: wait up to ten seconds for data to appear on \s-1STDIN_FILENO\s0. |
3804 | Example: wait up to ten seconds for data to appear on \s-1STDIN_FILENO.\s0 |
3655 | .Sp |
3805 | .Sp |
3656 | .Vb 7 |
3806 | .Vb 7 |
3657 | \& static void stdin_ready (int revents, void *arg) |
3807 | \& static void stdin_ready (int revents, void *arg) |
3658 | \& { |
3808 | \& { |
3659 | \& if (revents & EV_READ) |
3809 | \& if (revents & EV_READ) |
… | |
… | |
3675 | .SH "COMMON OR USEFUL IDIOMS (OR BOTH)" |
3825 | .SH "COMMON OR USEFUL IDIOMS (OR BOTH)" |
3676 | .IX Header "COMMON OR USEFUL IDIOMS (OR BOTH)" |
3826 | .IX Header "COMMON OR USEFUL IDIOMS (OR BOTH)" |
3677 | This section explains some common idioms that are not immediately |
3827 | This section explains some common idioms that are not immediately |
3678 | obvious. Note that examples are sprinkled over the whole manual, and this |
3828 | obvious. Note that examples are sprinkled over the whole manual, and this |
3679 | section only contains stuff that wouldn't fit anywhere else. |
3829 | section only contains stuff that wouldn't fit anywhere else. |
3680 | .SS "\s-1ASSOCIATING\s0 \s-1CUSTOM\s0 \s-1DATA\s0 \s-1WITH\s0 A \s-1WATCHER\s0" |
3830 | .SS "\s-1ASSOCIATING CUSTOM DATA WITH A WATCHER\s0" |
3681 | .IX Subsection "ASSOCIATING CUSTOM DATA WITH A WATCHER" |
3831 | .IX Subsection "ASSOCIATING CUSTOM DATA WITH A WATCHER" |
3682 | Each watcher has, by default, a \f(CW\*(C`void *data\*(C'\fR member that you can read |
3832 | Each watcher has, by default, a \f(CW\*(C`void *data\*(C'\fR member that you can read |
3683 | or modify at any time: libev will completely ignore it. This can be used |
3833 | or modify at any time: libev will completely ignore it. This can be used |
3684 | to associate arbitrary data with your watcher. If you need more data and |
3834 | to associate arbitrary data with your watcher. If you need more data and |
3685 | don't want to allocate memory separately and store a pointer to it in that |
3835 | don't want to allocate memory separately and store a pointer to it in that |
… | |
… | |
3711 | \& } |
3861 | \& } |
3712 | .Ve |
3862 | .Ve |
3713 | .PP |
3863 | .PP |
3714 | More interesting and less C\-conformant ways of casting your callback |
3864 | More interesting and less C\-conformant ways of casting your callback |
3715 | function type instead have been omitted. |
3865 | function type instead have been omitted. |
3716 | .SS "\s-1BUILDING\s0 \s-1YOUR\s0 \s-1OWN\s0 \s-1COMPOSITE\s0 \s-1WATCHERS\s0" |
3866 | .SS "\s-1BUILDING YOUR OWN COMPOSITE WATCHERS\s0" |
3717 | .IX Subsection "BUILDING YOUR OWN COMPOSITE WATCHERS" |
3867 | .IX Subsection "BUILDING YOUR OWN COMPOSITE WATCHERS" |
3718 | Another common scenario is to use some data structure with multiple |
3868 | Another common scenario is to use some data structure with multiple |
3719 | embedded watchers, in effect creating your own watcher that combines |
3869 | embedded watchers, in effect creating your own watcher that combines |
3720 | multiple libev event sources into one \*(L"super-watcher\*(R": |
3870 | multiple libev event sources into one \*(L"super-watcher\*(R": |
3721 | .PP |
3871 | .PP |
… | |
… | |
3749 | \& { |
3899 | \& { |
3750 | \& struct my_biggy big = (struct my_biggy *) |
3900 | \& struct my_biggy big = (struct my_biggy *) |
3751 | \& (((char *)w) \- offsetof (struct my_biggy, t2)); |
3901 | \& (((char *)w) \- offsetof (struct my_biggy, t2)); |
3752 | \& } |
3902 | \& } |
3753 | .Ve |
3903 | .Ve |
3754 | .SS "\s-1AVOIDING\s0 \s-1FINISHING\s0 \s-1BEFORE\s0 \s-1RETURNING\s0" |
3904 | .SS "\s-1AVOIDING FINISHING BEFORE RETURNING\s0" |
3755 | .IX Subsection "AVOIDING FINISHING BEFORE RETURNING" |
3905 | .IX Subsection "AVOIDING FINISHING BEFORE RETURNING" |
3756 | Often you have structures like this in event-based programs: |
3906 | Often you have structures like this in event-based programs: |
3757 | .PP |
3907 | .PP |
3758 | .Vb 4 |
3908 | .Vb 4 |
3759 | \& callback () |
3909 | \& callback () |
… | |
… | |
3781 | already been invoked. |
3931 | already been invoked. |
3782 | .PP |
3932 | .PP |
3783 | A common way around all these issues is to make sure that |
3933 | A common way around all these issues is to make sure that |
3784 | \&\f(CW\*(C`start_new_request\*(C'\fR \fIalways\fR returns before the callback is invoked. If |
3934 | \&\f(CW\*(C`start_new_request\*(C'\fR \fIalways\fR returns before the callback is invoked. If |
3785 | \&\f(CW\*(C`start_new_request\*(C'\fR immediately knows the result, it can artificially |
3935 | \&\f(CW\*(C`start_new_request\*(C'\fR immediately knows the result, it can artificially |
3786 | delay invoking the callback by e.g. using a \f(CW\*(C`prepare\*(C'\fR or \f(CW\*(C`idle\*(C'\fR watcher |
3936 | delay invoking the callback by using a \f(CW\*(C`prepare\*(C'\fR or \f(CW\*(C`idle\*(C'\fR watcher for |
3787 | for example, or more sneakily, by reusing an existing (stopped) watcher |
3937 | example, or more sneakily, by reusing an existing (stopped) watcher and |
3788 | and pushing it into the pending queue: |
3938 | pushing it into the pending queue: |
3789 | .PP |
3939 | .PP |
3790 | .Vb 2 |
3940 | .Vb 2 |
3791 | \& ev_set_cb (watcher, callback); |
3941 | \& ev_set_cb (watcher, callback); |
3792 | \& ev_feed_event (EV_A_ watcher, 0); |
3942 | \& ev_feed_event (EV_A_ watcher, 0); |
3793 | .Ve |
3943 | .Ve |
3794 | .PP |
3944 | .PP |
3795 | This way, \f(CW\*(C`start_new_request\*(C'\fR can safely return before the callback is |
3945 | This way, \f(CW\*(C`start_new_request\*(C'\fR can safely return before the callback is |
3796 | invoked, while not delaying callback invocation too much. |
3946 | invoked, while not delaying callback invocation too much. |
3797 | .SS "\s-1MODEL/NESTED\s0 \s-1EVENT\s0 \s-1LOOP\s0 \s-1INVOCATIONS\s0 \s-1AND\s0 \s-1EXIT\s0 \s-1CONDITIONS\s0" |
3947 | .SS "\s-1MODEL/NESTED EVENT LOOP INVOCATIONS AND EXIT CONDITIONS\s0" |
3798 | .IX Subsection "MODEL/NESTED EVENT LOOP INVOCATIONS AND EXIT CONDITIONS" |
3948 | .IX Subsection "MODEL/NESTED EVENT LOOP INVOCATIONS AND EXIT CONDITIONS" |
3799 | Often (especially in \s-1GUI\s0 toolkits) there are places where you have |
3949 | Often (especially in \s-1GUI\s0 toolkits) there are places where you have |
3800 | \&\fImodal\fR interaction, which is most easily implemented by recursively |
3950 | \&\fImodal\fR interaction, which is most easily implemented by recursively |
3801 | invoking \f(CW\*(C`ev_run\*(C'\fR. |
3951 | invoking \f(CW\*(C`ev_run\*(C'\fR. |
3802 | .PP |
3952 | .PP |
3803 | This brings the problem of exiting \- a callback might want to finish the |
3953 | This brings the problem of exiting \- a callback might want to finish the |
3804 | main \f(CW\*(C`ev_run\*(C'\fR call, but not the nested one (e.g. user clicked \*(L"Quit\*(R", but |
3954 | main \f(CW\*(C`ev_run\*(C'\fR call, but not the nested one (e.g. user clicked \*(L"Quit\*(R", but |
3805 | a modal \*(L"Are you sure?\*(R" dialog is still waiting), or just the nested one |
3955 | a modal \*(L"Are you sure?\*(R" dialog is still waiting), or just the nested one |
3806 | and not the main one (e.g. user clocked \*(L"Ok\*(R" in a modal dialog), or some |
3956 | and not the main one (e.g. user clocked \*(L"Ok\*(R" in a modal dialog), or some |
3807 | other combination: In these cases, \f(CW\*(C`ev_break\*(C'\fR will not work alone. |
3957 | other combination: In these cases, a simple \f(CW\*(C`ev_break\*(C'\fR will not work. |
3808 | .PP |
3958 | .PP |
3809 | The solution is to maintain \*(L"break this loop\*(R" variable for each \f(CW\*(C`ev_run\*(C'\fR |
3959 | The solution is to maintain \*(L"break this loop\*(R" variable for each \f(CW\*(C`ev_run\*(C'\fR |
3810 | invocation, and use a loop around \f(CW\*(C`ev_run\*(C'\fR until the condition is |
3960 | invocation, and use a loop around \f(CW\*(C`ev_run\*(C'\fR until the condition is |
3811 | triggered, using \f(CW\*(C`EVRUN_ONCE\*(C'\fR: |
3961 | triggered, using \f(CW\*(C`EVRUN_ONCE\*(C'\fR: |
3812 | .PP |
3962 | .PP |
… | |
… | |
3834 | \& exit_main_loop = 1; |
3984 | \& exit_main_loop = 1; |
3835 | \& |
3985 | \& |
3836 | \& // exit both |
3986 | \& // exit both |
3837 | \& exit_main_loop = exit_nested_loop = 1; |
3987 | \& exit_main_loop = exit_nested_loop = 1; |
3838 | .Ve |
3988 | .Ve |
3839 | .SS "\s-1THREAD\s0 \s-1LOCKING\s0 \s-1EXAMPLE\s0" |
3989 | .SS "\s-1THREAD LOCKING EXAMPLE\s0" |
3840 | .IX Subsection "THREAD LOCKING EXAMPLE" |
3990 | .IX Subsection "THREAD LOCKING EXAMPLE" |
3841 | Here is a fictitious example of how to run an event loop in a different |
3991 | Here is a fictitious example of how to run an event loop in a different |
3842 | thread from where callbacks are being invoked and watchers are |
3992 | thread from where callbacks are being invoked and watchers are |
3843 | created/added/removed. |
3993 | created/added/removed. |
3844 | .PP |
3994 | .PP |
… | |
… | |
3852 | .PP |
4002 | .PP |
3853 | First, you need to associate some data with the event loop: |
4003 | First, you need to associate some data with the event loop: |
3854 | .PP |
4004 | .PP |
3855 | .Vb 6 |
4005 | .Vb 6 |
3856 | \& typedef struct { |
4006 | \& typedef struct { |
3857 | \& mutex_t lock; /* global loop lock */ |
4007 | \& pthread_mutex_t lock; /* global loop lock */ |
|
|
4008 | \& pthread_t tid; |
|
|
4009 | \& pthread_cond_t invoke_cv; |
3858 | \& ev_async async_w; |
4010 | \& ev_async async_w; |
3859 | \& thread_t tid; |
|
|
3860 | \& cond_t invoke_cv; |
|
|
3861 | \& } userdata; |
4011 | \& } userdata; |
3862 | \& |
4012 | \& |
3863 | \& void prepare_loop (EV_P) |
4013 | \& void prepare_loop (EV_P) |
3864 | \& { |
4014 | \& { |
3865 | \& // for simplicity, we use a static userdata struct. |
4015 | \& // for simplicity, we use a static userdata struct. |
3866 | \& static userdata u; |
4016 | \& static userdata u; |
3867 | \& |
4017 | \& |
3868 | \& ev_async_init (&u\->async_w, async_cb); |
4018 | \& ev_async_init (&u.async_w, async_cb); |
3869 | \& ev_async_start (EV_A_ &u\->async_w); |
4019 | \& ev_async_start (EV_A_ &u.async_w); |
3870 | \& |
4020 | \& |
3871 | \& pthread_mutex_init (&u\->lock, 0); |
4021 | \& pthread_mutex_init (&u.lock, 0); |
3872 | \& pthread_cond_init (&u\->invoke_cv, 0); |
4022 | \& pthread_cond_init (&u.invoke_cv, 0); |
3873 | \& |
4023 | \& |
3874 | \& // now associate this with the loop |
4024 | \& // now associate this with the loop |
3875 | \& ev_set_userdata (EV_A_ u); |
4025 | \& ev_set_userdata (EV_A_ &u); |
3876 | \& ev_set_invoke_pending_cb (EV_A_ l_invoke); |
4026 | \& ev_set_invoke_pending_cb (EV_A_ l_invoke); |
3877 | \& ev_set_loop_release_cb (EV_A_ l_release, l_acquire); |
4027 | \& ev_set_loop_release_cb (EV_A_ l_release, l_acquire); |
3878 | \& |
4028 | \& |
3879 | \& // then create the thread running ev_run |
4029 | \& // then create the thread running ev_run |
3880 | \& pthread_create (&u\->tid, 0, l_run, EV_A); |
4030 | \& pthread_create (&u.tid, 0, l_run, EV_A); |
3881 | \& } |
4031 | \& } |
3882 | .Ve |
4032 | .Ve |
3883 | .PP |
4033 | .PP |
3884 | The callback for the \f(CW\*(C`ev_async\*(C'\fR watcher does nothing: the watcher is used |
4034 | The callback for the \f(CW\*(C`ev_async\*(C'\fR watcher does nothing: the watcher is used |
3885 | solely to wake up the event loop so it takes notice of any new watchers |
4035 | solely to wake up the event loop so it takes notice of any new watchers |
… | |
… | |
3985 | .PP |
4135 | .PP |
3986 | Note that sending the \f(CW\*(C`ev_async\*(C'\fR watcher is required because otherwise |
4136 | Note that sending the \f(CW\*(C`ev_async\*(C'\fR watcher is required because otherwise |
3987 | an event loop currently blocking in the kernel will have no knowledge |
4137 | an event loop currently blocking in the kernel will have no knowledge |
3988 | about the newly added timer. By waking up the loop it will pick up any new |
4138 | about the newly added timer. By waking up the loop it will pick up any new |
3989 | watchers in the next event loop iteration. |
4139 | watchers in the next event loop iteration. |
3990 | .SS "\s-1THREADS\s0, \s-1COROUTINES\s0, \s-1CONTINUATIONS\s0, \s-1QUEUES\s0... \s-1INSTEAD\s0 \s-1OF\s0 \s-1CALLBACKS\s0" |
4140 | .SS "\s-1THREADS, COROUTINES, CONTINUATIONS, QUEUES... INSTEAD OF CALLBACKS\s0" |
3991 | .IX Subsection "THREADS, COROUTINES, CONTINUATIONS, QUEUES... INSTEAD OF CALLBACKS" |
4141 | .IX Subsection "THREADS, COROUTINES, CONTINUATIONS, QUEUES... INSTEAD OF CALLBACKS" |
3992 | While the overhead of a callback that e.g. schedules a thread is small, it |
4142 | While the overhead of a callback that e.g. schedules a thread is small, it |
3993 | is still an overhead. If you embed libev, and your main usage is with some |
4143 | is still an overhead. If you embed libev, and your main usage is with some |
3994 | kind of threads or coroutines, you might want to customise libev so that |
4144 | kind of threads or coroutines, you might want to customise libev so that |
3995 | doesn't need callbacks anymore. |
4145 | doesn't need callbacks anymore. |
… | |
… | |
4031 | You can do similar tricks if you have, say, threads with an event queue \- |
4181 | You can do similar tricks if you have, say, threads with an event queue \- |
4032 | instead of storing a coroutine, you store the queue object and instead of |
4182 | instead of storing a coroutine, you store the queue object and instead of |
4033 | switching to a coroutine, you push the watcher onto the queue and notify |
4183 | switching to a coroutine, you push the watcher onto the queue and notify |
4034 | any waiters. |
4184 | any waiters. |
4035 | .PP |
4185 | .PP |
4036 | To embed libev, see \*(L"\s-1EMBEDDING\s0\*(R", but in short, it's easiest to create two |
4186 | To embed libev, see \*(L"\s-1EMBEDDING\*(R"\s0, but in short, it's easiest to create two |
4037 | files, \fImy_ev.h\fR and \fImy_ev.c\fR that include the respective libev files: |
4187 | files, \fImy_ev.h\fR and \fImy_ev.c\fR that include the respective libev files: |
4038 | .PP |
4188 | .PP |
4039 | .Vb 4 |
4189 | .Vb 4 |
4040 | \& // my_ev.h |
4190 | \& // my_ev.h |
4041 | \& #define EV_CB_DECLARE(type) struct my_coro *cb; |
4191 | \& #define EV_CB_DECLARE(type) struct my_coro *cb; |
4042 | \& #define EV_CB_INVOKE(watcher) switch_to ((watcher)\->cb); |
4192 | \& #define EV_CB_INVOKE(watcher) switch_to ((watcher)\->cb) |
4043 | \& #include "../libev/ev.h" |
4193 | \& #include "../libev/ev.h" |
4044 | \& |
4194 | \& |
4045 | \& // my_ev.c |
4195 | \& // my_ev.c |
4046 | \& #define EV_H "my_ev.h" |
4196 | \& #define EV_H "my_ev.h" |
4047 | \& #include "../libev/ev.c" |
4197 | \& #include "../libev/ev.c" |
… | |
… | |
4087 | The normal C \s-1API\s0 should work fine when used from \*(C+: both ev.h and the |
4237 | The normal C \s-1API\s0 should work fine when used from \*(C+: both ev.h and the |
4088 | libev sources can be compiled as \*(C+. Therefore, code that uses the C \s-1API\s0 |
4238 | libev sources can be compiled as \*(C+. Therefore, code that uses the C \s-1API\s0 |
4089 | will work fine. |
4239 | will work fine. |
4090 | .PP |
4240 | .PP |
4091 | Proper exception specifications might have to be added to callbacks passed |
4241 | Proper exception specifications might have to be added to callbacks passed |
4092 | to libev: exceptions may be thrown only from watcher callbacks, all |
4242 | to libev: exceptions may be thrown only from watcher callbacks, all other |
4093 | other callbacks (allocator, syserr, loop acquire/release and periodic |
4243 | callbacks (allocator, syserr, loop acquire/release and periodic reschedule |
4094 | reschedule callbacks) must not throw exceptions, and might need a \f(CW\*(C`throw |
4244 | callbacks) must not throw exceptions, and might need a \f(CW\*(C`noexcept\*(C'\fR |
4095 | ()\*(C'\fR specification. If you have code that needs to be compiled as both C |
4245 | specification. If you have code that needs to be compiled as both C and |
4096 | and \*(C+ you can use the \f(CW\*(C`EV_THROW\*(C'\fR macro for this: |
4246 | \&\*(C+ you can use the \f(CW\*(C`EV_NOEXCEPT\*(C'\fR macro for this: |
4097 | .PP |
4247 | .PP |
4098 | .Vb 6 |
4248 | .Vb 6 |
4099 | \& static void |
4249 | \& static void |
4100 | \& fatal_error (const char *msg) EV_THROW |
4250 | \& fatal_error (const char *msg) EV_NOEXCEPT |
4101 | \& { |
4251 | \& { |
4102 | \& perror (msg); |
4252 | \& perror (msg); |
4103 | \& abort (); |
4253 | \& abort (); |
4104 | \& } |
4254 | \& } |
4105 | \& |
4255 | \& |
… | |
… | |
4233 | \& void operator() (ev::io &w, int revents) |
4383 | \& void operator() (ev::io &w, int revents) |
4234 | \& { |
4384 | \& { |
4235 | \& ... |
4385 | \& ... |
4236 | \& } |
4386 | \& } |
4237 | \& } |
4387 | \& } |
4238 | \& |
4388 | \& |
4239 | \& myfunctor f; |
4389 | \& myfunctor f; |
4240 | \& |
4390 | \& |
4241 | \& ev::io w; |
4391 | \& ev::io w; |
4242 | \& w.set (&f); |
4392 | \& w.set (&f); |
4243 | .Ve |
4393 | .Ve |
… | |
… | |
4261 | .IX Item "w->set (loop)" |
4411 | .IX Item "w->set (loop)" |
4262 | Associates a different \f(CW\*(C`struct ev_loop\*(C'\fR with this watcher. You can only |
4412 | Associates a different \f(CW\*(C`struct ev_loop\*(C'\fR with this watcher. You can only |
4263 | do this when the watcher is inactive (and not pending either). |
4413 | do this when the watcher is inactive (and not pending either). |
4264 | .IP "w\->set ([arguments])" 4 |
4414 | .IP "w\->set ([arguments])" 4 |
4265 | .IX Item "w->set ([arguments])" |
4415 | .IX Item "w->set ([arguments])" |
4266 | Basically the same as \f(CW\*(C`ev_TYPE_set\*(C'\fR, with the same arguments. Either this |
4416 | Basically the same as \f(CW\*(C`ev_TYPE_set\*(C'\fR (except for \f(CW\*(C`ev::embed\*(C'\fR watchers>), |
4267 | method or a suitable start method must be called at least once. Unlike the |
4417 | with the same arguments. Either this method or a suitable start method |
4268 | C counterpart, an active watcher gets automatically stopped and restarted |
4418 | must be called at least once. Unlike the C counterpart, an active watcher |
4269 | when reconfiguring it with this method. |
4419 | gets automatically stopped and restarted when reconfiguring it with this |
|
|
4420 | method. |
|
|
4421 | .Sp |
|
|
4422 | For \f(CW\*(C`ev::embed\*(C'\fR watchers this method is called \f(CW\*(C`set_embed\*(C'\fR, to avoid |
|
|
4423 | clashing with the \f(CW\*(C`set (loop)\*(C'\fR method. |
|
|
4424 | .Sp |
|
|
4425 | For \f(CW\*(C`ev::io\*(C'\fR watchers there is an additional \f(CW\*(C`set\*(C'\fR method that acepts a |
|
|
4426 | new event mask only, and internally calls \f(CW\*(C`ev_io_modfify\*(C'\fR. |
4270 | .IP "w\->start ()" 4 |
4427 | .IP "w\->start ()" 4 |
4271 | .IX Item "w->start ()" |
4428 | .IX Item "w->start ()" |
4272 | Starts the watcher. Note that there is no \f(CW\*(C`loop\*(C'\fR argument, as the |
4429 | Starts the watcher. Note that there is no \f(CW\*(C`loop\*(C'\fR argument, as the |
4273 | constructor already stores the event loop. |
4430 | constructor already stores the event loop. |
4274 | .IP "w\->start ([arguments])" 4 |
4431 | .IP "w\->start ([arguments])" 4 |
… | |
… | |
4332 | there are additional modules that implement libev-compatible interfaces |
4489 | there are additional modules that implement libev-compatible interfaces |
4333 | to \f(CW\*(C`libadns\*(C'\fR (\f(CW\*(C`EV::ADNS\*(C'\fR, but \f(CW\*(C`AnyEvent::DNS\*(C'\fR is preferred nowadays), |
4490 | to \f(CW\*(C`libadns\*(C'\fR (\f(CW\*(C`EV::ADNS\*(C'\fR, but \f(CW\*(C`AnyEvent::DNS\*(C'\fR is preferred nowadays), |
4334 | \&\f(CW\*(C`Net::SNMP\*(C'\fR (\f(CW\*(C`Net::SNMP::EV\*(C'\fR) and the \f(CW\*(C`libglib\*(C'\fR event core (\f(CW\*(C`Glib::EV\*(C'\fR |
4491 | \&\f(CW\*(C`Net::SNMP\*(C'\fR (\f(CW\*(C`Net::SNMP::EV\*(C'\fR) and the \f(CW\*(C`libglib\*(C'\fR event core (\f(CW\*(C`Glib::EV\*(C'\fR |
4335 | and \f(CW\*(C`EV::Glib\*(C'\fR). |
4492 | and \f(CW\*(C`EV::Glib\*(C'\fR). |
4336 | .Sp |
4493 | .Sp |
4337 | It can be found and installed via \s-1CPAN\s0, its homepage is at |
4494 | It can be found and installed via \s-1CPAN,\s0 its homepage is at |
4338 | <http://software.schmorp.de/pkg/EV>. |
4495 | <http://software.schmorp.de/pkg/EV>. |
4339 | .IP "Python" 4 |
4496 | .IP "Python" 4 |
4340 | .IX Item "Python" |
4497 | .IX Item "Python" |
4341 | Python bindings can be found at <http://code.google.com/p/pyev/>. It |
4498 | Python bindings can be found at <http://code.google.com/p/pyev/>. It |
4342 | seems to be quite complete and well-documented. |
4499 | seems to be quite complete and well-documented. |
… | |
… | |
4350 | Roger Pack reports that using the link order \f(CW\*(C`\-lws2_32 \-lmsvcrt\-ruby\-190\*(C'\fR |
4507 | Roger Pack reports that using the link order \f(CW\*(C`\-lws2_32 \-lmsvcrt\-ruby\-190\*(C'\fR |
4351 | makes rev work even on mingw. |
4508 | makes rev work even on mingw. |
4352 | .IP "Haskell" 4 |
4509 | .IP "Haskell" 4 |
4353 | .IX Item "Haskell" |
4510 | .IX Item "Haskell" |
4354 | A haskell binding to libev is available at |
4511 | A haskell binding to libev is available at |
4355 | http://hackage.haskell.org/cgi\-bin/hackage\-scripts/package/hlibev <http://hackage.haskell.org/cgi-bin/hackage-scripts/package/hlibev>. |
4512 | <http://hackage.haskell.org/cgi\-bin/hackage\-scripts/package/hlibev>. |
4356 | .IP "D" 4 |
4513 | .IP "D" 4 |
4357 | .IX Item "D" |
4514 | .IX Item "D" |
4358 | Leandro Lucarella has written a D language binding (\fIev.d\fR) for libev, to |
4515 | Leandro Lucarella has written a D language binding (\fIev.d\fR) for libev, to |
4359 | be found at <http://www.llucax.com.ar/proj/ev.d/index.html>. |
4516 | be found at <http://www.llucax.com.ar/proj/ev.d/index.html>. |
4360 | .IP "Ocaml" 4 |
4517 | .IP "Ocaml" 4 |
4361 | .IX Item "Ocaml" |
4518 | .IX Item "Ocaml" |
4362 | Erkki Seppala has written Ocaml bindings for libev, to be found at |
4519 | Erkki Seppala has written Ocaml bindings for libev, to be found at |
4363 | http://modeemi.cs.tut.fi/~flux/software/ocaml\-ev/ <http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>. |
4520 | <http://modeemi.cs.tut.fi/~flux/software/ocaml\-ev/>. |
4364 | .IP "Lua" 4 |
4521 | .IP "Lua" 4 |
4365 | .IX Item "Lua" |
4522 | .IX Item "Lua" |
4366 | Brian Maher has written a partial interface to libev for lua (at the |
4523 | Brian Maher has written a partial interface to libev for lua (at the |
4367 | time of this writing, only \f(CW\*(C`ev_io\*(C'\fR and \f(CW\*(C`ev_timer\*(C'\fR), to be found at |
4524 | time of this writing, only \f(CW\*(C`ev_io\*(C'\fR and \f(CW\*(C`ev_timer\*(C'\fR), to be found at |
4368 | http://github.com/brimworks/lua\-ev <http://github.com/brimworks/lua-ev>. |
4525 | <http://github.com/brimworks/lua\-ev>. |
4369 | .IP "Javascript" 4 |
4526 | .IP "Javascript" 4 |
4370 | .IX Item "Javascript" |
4527 | .IX Item "Javascript" |
4371 | Node.js (<http://nodejs.org>) uses libev as the underlying event library. |
4528 | Node.js (<http://nodejs.org>) uses libev as the underlying event library. |
4372 | .IP "Others" 4 |
4529 | .IP "Others" 4 |
4373 | .IX Item "Others" |
4530 | .IX Item "Others" |
… | |
… | |
4462 | .SS "\s-1FILESETS\s0" |
4619 | .SS "\s-1FILESETS\s0" |
4463 | .IX Subsection "FILESETS" |
4620 | .IX Subsection "FILESETS" |
4464 | Depending on what features you need you need to include one or more sets of files |
4621 | Depending on what features you need you need to include one or more sets of files |
4465 | in your application. |
4622 | in your application. |
4466 | .PP |
4623 | .PP |
4467 | \fI\s-1CORE\s0 \s-1EVENT\s0 \s-1LOOP\s0\fR |
4624 | \fI\s-1CORE EVENT LOOP\s0\fR |
4468 | .IX Subsection "CORE EVENT LOOP" |
4625 | .IX Subsection "CORE EVENT LOOP" |
4469 | .PP |
4626 | .PP |
4470 | To include only the libev core (all the \f(CW\*(C`ev_*\*(C'\fR functions), with manual |
4627 | To include only the libev core (all the \f(CW\*(C`ev_*\*(C'\fR functions), with manual |
4471 | configuration (no autoconf): |
4628 | configuration (no autoconf): |
4472 | .PP |
4629 | .PP |
… | |
… | |
4499 | \& ev_vars.h |
4656 | \& ev_vars.h |
4500 | \& ev_wrap.h |
4657 | \& ev_wrap.h |
4501 | \& |
4658 | \& |
4502 | \& ev_win32.c required on win32 platforms only |
4659 | \& ev_win32.c required on win32 platforms only |
4503 | \& |
4660 | \& |
4504 | \& ev_select.c only when select backend is enabled (which is enabled by default) |
4661 | \& ev_select.c only when select backend is enabled |
4505 | \& ev_poll.c only when poll backend is enabled (disabled by default) |
4662 | \& ev_poll.c only when poll backend is enabled |
4506 | \& ev_epoll.c only when the epoll backend is enabled (disabled by default) |
4663 | \& ev_epoll.c only when the epoll backend is enabled |
|
|
4664 | \& ev_linuxaio.c only when the linux aio backend is enabled |
|
|
4665 | \& ev_iouring.c only when the linux io_uring backend is enabled |
4507 | \& ev_kqueue.c only when the kqueue backend is enabled (disabled by default) |
4666 | \& ev_kqueue.c only when the kqueue backend is enabled |
4508 | \& ev_port.c only when the solaris port backend is enabled (disabled by default) |
4667 | \& ev_port.c only when the solaris port backend is enabled |
4509 | .Ve |
4668 | .Ve |
4510 | .PP |
4669 | .PP |
4511 | \&\fIev.c\fR includes the backend files directly when enabled, so you only need |
4670 | \&\fIev.c\fR includes the backend files directly when enabled, so you only need |
4512 | to compile this single file. |
4671 | to compile this single file. |
4513 | .PP |
4672 | .PP |
4514 | \fI\s-1LIBEVENT\s0 \s-1COMPATIBILITY\s0 \s-1API\s0\fR |
4673 | \fI\s-1LIBEVENT COMPATIBILITY API\s0\fR |
4515 | .IX Subsection "LIBEVENT COMPATIBILITY API" |
4674 | .IX Subsection "LIBEVENT COMPATIBILITY API" |
4516 | .PP |
4675 | .PP |
4517 | To include the libevent compatibility \s-1API\s0, also include: |
4676 | To include the libevent compatibility \s-1API,\s0 also include: |
4518 | .PP |
4677 | .PP |
4519 | .Vb 1 |
4678 | .Vb 1 |
4520 | \& #include "event.c" |
4679 | \& #include "event.c" |
4521 | .Ve |
4680 | .Ve |
4522 | .PP |
4681 | .PP |
… | |
… | |
4524 | .PP |
4683 | .PP |
4525 | .Vb 1 |
4684 | .Vb 1 |
4526 | \& #include "event.h" |
4685 | \& #include "event.h" |
4527 | .Ve |
4686 | .Ve |
4528 | .PP |
4687 | .PP |
4529 | in the files that want to use the libevent \s-1API\s0. This also includes \fIev.h\fR. |
4688 | in the files that want to use the libevent \s-1API.\s0 This also includes \fIev.h\fR. |
4530 | .PP |
4689 | .PP |
4531 | You need the following additional files for this: |
4690 | You need the following additional files for this: |
4532 | .PP |
4691 | .PP |
4533 | .Vb 2 |
4692 | .Vb 2 |
4534 | \& event.h |
4693 | \& event.h |
4535 | \& event.c |
4694 | \& event.c |
4536 | .Ve |
4695 | .Ve |
4537 | .PP |
4696 | .PP |
4538 | \fI\s-1AUTOCONF\s0 \s-1SUPPORT\s0\fR |
4697 | \fI\s-1AUTOCONF SUPPORT\s0\fR |
4539 | .IX Subsection "AUTOCONF SUPPORT" |
4698 | .IX Subsection "AUTOCONF SUPPORT" |
4540 | .PP |
4699 | .PP |
4541 | Instead of using \f(CW\*(C`EV_STANDALONE=1\*(C'\fR and providing your configuration in |
4700 | Instead of using \f(CW\*(C`EV_STANDALONE=1\*(C'\fR and providing your configuration in |
4542 | whatever way you want, you can also \f(CW\*(C`m4_include([libev.m4])\*(C'\fR in your |
4701 | whatever way you want, you can also \f(CW\*(C`m4_include([libev.m4])\*(C'\fR in your |
4543 | \&\fIconfigure.ac\fR and leave \f(CW\*(C`EV_STANDALONE\*(C'\fR undefined. \fIev.c\fR will then |
4702 | \&\fIconfigure.ac\fR and leave \f(CW\*(C`EV_STANDALONE\*(C'\fR undefined. \fIev.c\fR will then |
… | |
… | |
4546 | For this of course you need the m4 file: |
4705 | For this of course you need the m4 file: |
4547 | .PP |
4706 | .PP |
4548 | .Vb 1 |
4707 | .Vb 1 |
4549 | \& libev.m4 |
4708 | \& libev.m4 |
4550 | .Ve |
4709 | .Ve |
4551 | .SS "\s-1PREPROCESSOR\s0 \s-1SYMBOLS/MACROS\s0" |
4710 | .SS "\s-1PREPROCESSOR SYMBOLS/MACROS\s0" |
4552 | .IX Subsection "PREPROCESSOR SYMBOLS/MACROS" |
4711 | .IX Subsection "PREPROCESSOR SYMBOLS/MACROS" |
4553 | Libev can be configured via a variety of preprocessor symbols you have to |
4712 | Libev can be configured via a variety of preprocessor symbols you have to |
4554 | define before including (or compiling) any of its files. The default in |
4713 | define before including (or compiling) any of its files. The default in |
4555 | the absence of autoconf is documented for every option. |
4714 | the absence of autoconf is documented for every option. |
4556 | .PP |
4715 | .PP |
4557 | Symbols marked with \*(L"(h)\*(R" do not change the \s-1ABI\s0, and can have different |
4716 | Symbols marked with \*(L"(h)\*(R" do not change the \s-1ABI,\s0 and can have different |
4558 | values when compiling libev vs. including \fIev.h\fR, so it is permissible |
4717 | values when compiling libev vs. including \fIev.h\fR, so it is permissible |
4559 | to redefine them before including \fIev.h\fR without breaking compatibility |
4718 | to redefine them before including \fIev.h\fR without breaking compatibility |
4560 | to a compiled library. All other symbols change the \s-1ABI\s0, which means all |
4719 | to a compiled library. All other symbols change the \s-1ABI,\s0 which means all |
4561 | users of libev and the libev code itself must be compiled with compatible |
4720 | users of libev and the libev code itself must be compiled with compatible |
4562 | settings. |
4721 | settings. |
4563 | .IP "\s-1EV_COMPAT3\s0 (h)" 4 |
4722 | .IP "\s-1EV_COMPAT3\s0 (h)" 4 |
4564 | .IX Item "EV_COMPAT3 (h)" |
4723 | .IX Item "EV_COMPAT3 (h)" |
4565 | Backwards compatibility is a major concern for libev. This is why this |
4724 | Backwards compatibility is a major concern for libev. This is why this |
… | |
… | |
4624 | higher, as it simplifies linking (no need for \f(CW\*(C`\-lrt\*(C'\fR). |
4783 | higher, as it simplifies linking (no need for \f(CW\*(C`\-lrt\*(C'\fR). |
4625 | .IP "\s-1EV_USE_NANOSLEEP\s0" 4 |
4784 | .IP "\s-1EV_USE_NANOSLEEP\s0" 4 |
4626 | .IX Item "EV_USE_NANOSLEEP" |
4785 | .IX Item "EV_USE_NANOSLEEP" |
4627 | If defined to be \f(CW1\fR, libev will assume that \f(CW\*(C`nanosleep ()\*(C'\fR is available |
4786 | If defined to be \f(CW1\fR, libev will assume that \f(CW\*(C`nanosleep ()\*(C'\fR is available |
4628 | and will use it for delays. Otherwise it will use \f(CW\*(C`select ()\*(C'\fR. |
4787 | and will use it for delays. Otherwise it will use \f(CW\*(C`select ()\*(C'\fR. |
|
|
4788 | .IP "\s-1EV_USE_EVENTFD\s0" 4 |
|
|
4789 | .IX Item "EV_USE_EVENTFD" |
|
|
4790 | If defined to be \f(CW1\fR, then libev will assume that \f(CW\*(C`eventfd ()\*(C'\fR is |
|
|
4791 | available and will probe for kernel support at runtime. This will improve |
|
|
4792 | \&\f(CW\*(C`ev_signal\*(C'\fR and \f(CW\*(C`ev_async\*(C'\fR performance and reduce resource consumption. |
|
|
4793 | If undefined, it will be enabled if the headers indicate GNU/Linux + Glibc |
|
|
4794 | 2.7 or newer, otherwise disabled. |
|
|
4795 | .IP "\s-1EV_USE_SIGNALFD\s0" 4 |
|
|
4796 | .IX Item "EV_USE_SIGNALFD" |
|
|
4797 | If defined to be \f(CW1\fR, then libev will assume that \f(CW\*(C`signalfd ()\*(C'\fR is |
|
|
4798 | available and will probe for kernel support at runtime. This enables |
|
|
4799 | the use of \s-1EVFLAG_SIGNALFD\s0 for faster and simpler signal handling. If |
|
|
4800 | undefined, it will be enabled if the headers indicate GNU/Linux + Glibc |
|
|
4801 | 2.7 or newer, otherwise disabled. |
|
|
4802 | .IP "\s-1EV_USE_TIMERFD\s0" 4 |
|
|
4803 | .IX Item "EV_USE_TIMERFD" |
|
|
4804 | If defined to be \f(CW1\fR, then libev will assume that \f(CW\*(C`timerfd ()\*(C'\fR is |
|
|
4805 | available and will probe for kernel support at runtime. This allows |
|
|
4806 | libev to detect time jumps accurately. If undefined, it will be enabled |
|
|
4807 | if the headers indicate GNU/Linux + Glibc 2.8 or newer and define |
|
|
4808 | \&\f(CW\*(C`TFD_TIMER_CANCEL_ON_SET\*(C'\fR, otherwise disabled. |
4629 | .IP "\s-1EV_USE_EVENTFD\s0" 4 |
4809 | .IP "\s-1EV_USE_EVENTFD\s0" 4 |
4630 | .IX Item "EV_USE_EVENTFD" |
4810 | .IX Item "EV_USE_EVENTFD" |
4631 | If defined to be \f(CW1\fR, then libev will assume that \f(CW\*(C`eventfd ()\*(C'\fR is |
4811 | If defined to be \f(CW1\fR, then libev will assume that \f(CW\*(C`eventfd ()\*(C'\fR is |
4632 | available and will probe for kernel support at runtime. This will improve |
4812 | available and will probe for kernel support at runtime. This will improve |
4633 | \&\f(CW\*(C`ev_signal\*(C'\fR and \f(CW\*(C`ev_async\*(C'\fR performance and reduce resource consumption. |
4813 | \&\f(CW\*(C`ev_signal\*(C'\fR and \f(CW\*(C`ev_async\*(C'\fR performance and reduce resource consumption. |
… | |
… | |
4692 | If defined to be \f(CW1\fR, libev will compile in support for the Linux |
4872 | If defined to be \f(CW1\fR, libev will compile in support for the Linux |
4693 | \&\f(CW\*(C`epoll\*(C'\fR(7) backend. Its availability will be detected at runtime, |
4873 | \&\f(CW\*(C`epoll\*(C'\fR(7) backend. Its availability will be detected at runtime, |
4694 | otherwise another method will be used as fallback. This is the preferred |
4874 | otherwise another method will be used as fallback. This is the preferred |
4695 | backend for GNU/Linux systems. If undefined, it will be enabled if the |
4875 | backend for GNU/Linux systems. If undefined, it will be enabled if the |
4696 | headers indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
4876 | headers indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
|
|
4877 | .IP "\s-1EV_USE_LINUXAIO\s0" 4 |
|
|
4878 | .IX Item "EV_USE_LINUXAIO" |
|
|
4879 | If defined to be \f(CW1\fR, libev will compile in support for the Linux aio |
|
|
4880 | backend (\f(CW\*(C`EV_USE_EPOLL\*(C'\fR must also be enabled). If undefined, it will be |
|
|
4881 | enabled on linux, otherwise disabled. |
|
|
4882 | .IP "\s-1EV_USE_IOURING\s0" 4 |
|
|
4883 | .IX Item "EV_USE_IOURING" |
|
|
4884 | If defined to be \f(CW1\fR, libev will compile in support for the Linux |
|
|
4885 | io_uring backend (\f(CW\*(C`EV_USE_EPOLL\*(C'\fR must also be enabled). Due to it's |
|
|
4886 | current limitations it has to be requested explicitly. If undefined, it |
|
|
4887 | will be enabled on linux, otherwise disabled. |
4697 | .IP "\s-1EV_USE_KQUEUE\s0" 4 |
4888 | .IP "\s-1EV_USE_KQUEUE\s0" 4 |
4698 | .IX Item "EV_USE_KQUEUE" |
4889 | .IX Item "EV_USE_KQUEUE" |
4699 | If defined to be \f(CW1\fR, libev will compile in support for the \s-1BSD\s0 style |
4890 | If defined to be \f(CW1\fR, libev will compile in support for the \s-1BSD\s0 style |
4700 | \&\f(CW\*(C`kqueue\*(C'\fR(2) backend. Its actual availability will be detected at runtime, |
4891 | \&\f(CW\*(C`kqueue\*(C'\fR(2) backend. Its actual availability will be detected at runtime, |
4701 | otherwise another method will be used as fallback. This is the preferred |
4892 | otherwise another method will be used as fallback. This is the preferred |
… | |
… | |
4726 | between threads, that is, threads can be used, but threads never run on |
4917 | between threads, that is, threads can be used, but threads never run on |
4727 | different cpus (or different cpu cores). This reduces dependencies |
4918 | different cpus (or different cpu cores). This reduces dependencies |
4728 | and makes libev faster. |
4919 | and makes libev faster. |
4729 | .IP "\s-1EV_NO_THREADS\s0" 4 |
4920 | .IP "\s-1EV_NO_THREADS\s0" 4 |
4730 | .IX Item "EV_NO_THREADS" |
4921 | .IX Item "EV_NO_THREADS" |
4731 | If defined to be \f(CW1\fR, libev will assume that it will never be called |
4922 | If defined to be \f(CW1\fR, libev will assume that it will never be called from |
4732 | from different threads, which is a stronger assumption than \f(CW\*(C`EV_NO_SMP\*(C'\fR, |
4923 | different threads (that includes signal handlers), which is a stronger |
4733 | above. This reduces dependencies and makes libev faster. |
4924 | assumption than \f(CW\*(C`EV_NO_SMP\*(C'\fR, above. This reduces dependencies and makes |
|
|
4925 | libev faster. |
4734 | .IP "\s-1EV_ATOMIC_T\s0" 4 |
4926 | .IP "\s-1EV_ATOMIC_T\s0" 4 |
4735 | .IX Item "EV_ATOMIC_T" |
4927 | .IX Item "EV_ATOMIC_T" |
4736 | Libev requires an integer type (suitable for storing \f(CW0\fR or \f(CW1\fR) whose |
4928 | Libev requires an integer type (suitable for storing \f(CW0\fR or \f(CW1\fR) whose |
4737 | access is atomic and serialised with respect to other threads or signal |
4929 | access is atomic with respect to other threads or signal contexts. No |
4738 | contexts. No such type is easily found in the C language, so you can |
4930 | such type is easily found in the C language, so you can provide your own |
4739 | provide your own type that you know is safe for your purposes. It is used |
4931 | type that you know is safe for your purposes. It is used both for signal |
4740 | both for signal handler \*(L"locking\*(R" as well as for signal and thread safety |
4932 | handler \*(L"locking\*(R" as well as for signal and thread safety in \f(CW\*(C`ev_async\*(C'\fR |
4741 | in \f(CW\*(C`ev_async\*(C'\fR watchers. |
4933 | watchers. |
4742 | .Sp |
4934 | .Sp |
4743 | In the absence of this define, libev will use \f(CW\*(C`sig_atomic_t volatile\*(C'\fR |
4935 | In the absence of this define, libev will use \f(CW\*(C`sig_atomic_t volatile\*(C'\fR |
4744 | (from \fIsignal.h\fR), which is usually good enough on most platforms, |
4936 | (from \fIsignal.h\fR), which is usually good enough on most platforms. |
4745 | although strictly speaking using a type that also implies a memory fence |
|
|
4746 | is required. |
|
|
4747 | .IP "\s-1EV_H\s0 (h)" 4 |
4937 | .IP "\s-1EV_H\s0 (h)" 4 |
4748 | .IX Item "EV_H (h)" |
4938 | .IX Item "EV_H (h)" |
4749 | The name of the \fIev.h\fR header file used to include it. The default if |
4939 | The name of the \fIev.h\fR header file used to include it. The default if |
4750 | undefined is \f(CW"ev.h"\fR in \fIevent.h\fR, \fIev.c\fR and \fIev++.h\fR. This can be |
4940 | undefined is \f(CW"ev.h"\fR in \fIevent.h\fR, \fIev.c\fR and \fIev++.h\fR. This can be |
4751 | used to virtually rename the \fIev.h\fR header file in case of conflicts. |
4941 | used to virtually rename the \fIev.h\fR header file in case of conflicts. |
… | |
… | |
4790 | all the priorities, so having many of them (hundreds) uses a lot of space |
4980 | all the priorities, so having many of them (hundreds) uses a lot of space |
4791 | and time, so using the defaults of five priorities (\-2 .. +2) is usually |
4981 | and time, so using the defaults of five priorities (\-2 .. +2) is usually |
4792 | fine. |
4982 | fine. |
4793 | .Sp |
4983 | .Sp |
4794 | If your embedding application does not need any priorities, defining these |
4984 | If your embedding application does not need any priorities, defining these |
4795 | both to \f(CW0\fR will save some memory and \s-1CPU\s0. |
4985 | both to \f(CW0\fR will save some memory and \s-1CPU.\s0 |
4796 | .IP "\s-1EV_PERIODIC_ENABLE\s0, \s-1EV_IDLE_ENABLE\s0, \s-1EV_EMBED_ENABLE\s0, \s-1EV_STAT_ENABLE\s0, \s-1EV_PREPARE_ENABLE\s0, \s-1EV_CHECK_ENABLE\s0, \s-1EV_FORK_ENABLE\s0, \s-1EV_SIGNAL_ENABLE\s0, \s-1EV_ASYNC_ENABLE\s0, \s-1EV_CHILD_ENABLE\s0." 4 |
4986 | .IP "\s-1EV_PERIODIC_ENABLE, EV_IDLE_ENABLE, EV_EMBED_ENABLE, EV_STAT_ENABLE, EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE, EV_ASYNC_ENABLE, EV_CHILD_ENABLE.\s0" 4 |
4797 | .IX Item "EV_PERIODIC_ENABLE, EV_IDLE_ENABLE, EV_EMBED_ENABLE, EV_STAT_ENABLE, EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE, EV_ASYNC_ENABLE, EV_CHILD_ENABLE." |
4987 | .IX Item "EV_PERIODIC_ENABLE, EV_IDLE_ENABLE, EV_EMBED_ENABLE, EV_STAT_ENABLE, EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE, EV_ASYNC_ENABLE, EV_CHILD_ENABLE." |
4798 | If undefined or defined to be \f(CW1\fR (and the platform supports it), then |
4988 | If undefined or defined to be \f(CW1\fR (and the platform supports it), then |
4799 | the respective watcher type is supported. If defined to be \f(CW0\fR, then it |
4989 | the respective watcher type is supported. If defined to be \f(CW0\fR, then it |
4800 | is not. Disabling watcher types mainly saves code size. |
4990 | is not. Disabling watcher types mainly saves code size. |
4801 | .IP "\s-1EV_FEATURES\s0" 4 |
4991 | .IP "\s-1EV_FEATURES\s0" 4 |
… | |
… | |
4959 | called. If set to \f(CW2\fR, then the internal verification code will be |
5149 | called. If set to \f(CW2\fR, then the internal verification code will be |
4960 | called once per loop, which can slow down libev. If set to \f(CW3\fR, then the |
5150 | called once per loop, which can slow down libev. If set to \f(CW3\fR, then the |
4961 | verification code will be called very frequently, which will slow down |
5151 | verification code will be called very frequently, which will slow down |
4962 | libev considerably. |
5152 | libev considerably. |
4963 | .Sp |
5153 | .Sp |
|
|
5154 | Verification errors are reported via C's \f(CW\*(C`assert\*(C'\fR mechanism, so if you |
|
|
5155 | disable that (e.g. by defining \f(CW\*(C`NDEBUG\*(C'\fR) then no errors will be reported. |
|
|
5156 | .Sp |
4964 | The default is \f(CW1\fR, unless \f(CW\*(C`EV_FEATURES\*(C'\fR overrides it, in which case it |
5157 | The default is \f(CW1\fR, unless \f(CW\*(C`EV_FEATURES\*(C'\fR overrides it, in which case it |
4965 | will be \f(CW0\fR. |
5158 | will be \f(CW0\fR. |
4966 | .IP "\s-1EV_COMMON\s0" 4 |
5159 | .IP "\s-1EV_COMMON\s0" 4 |
4967 | .IX Item "EV_COMMON" |
5160 | .IX Item "EV_COMMON" |
4968 | By default, all watchers have a \f(CW\*(C`void *data\*(C'\fR member. By redefining |
5161 | By default, all watchers have a \f(CW\*(C`void *data\*(C'\fR member. By redefining |
… | |
… | |
4989 | and the way callbacks are invoked and set. Must expand to a struct member |
5182 | and the way callbacks are invoked and set. Must expand to a struct member |
4990 | definition and a statement, respectively. See the \fIev.h\fR header file for |
5183 | definition and a statement, respectively. See the \fIev.h\fR header file for |
4991 | their default definitions. One possible use for overriding these is to |
5184 | their default definitions. One possible use for overriding these is to |
4992 | avoid the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument in all cases, or to use |
5185 | avoid the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument in all cases, or to use |
4993 | method calls instead of plain function calls in \*(C+. |
5186 | method calls instead of plain function calls in \*(C+. |
4994 | .SS "\s-1EXPORTED\s0 \s-1API\s0 \s-1SYMBOLS\s0" |
5187 | .SS "\s-1EXPORTED API SYMBOLS\s0" |
4995 | .IX Subsection "EXPORTED API SYMBOLS" |
5188 | .IX Subsection "EXPORTED API SYMBOLS" |
4996 | If you need to re-export the \s-1API\s0 (e.g. via a \s-1DLL\s0) and you need a list of |
5189 | If you need to re-export the \s-1API\s0 (e.g. via a \s-1DLL\s0) and you need a list of |
4997 | exported symbols, you can use the provided \fISymbol.*\fR files which list |
5190 | exported symbols, you can use the provided \fISymbol.*\fR files which list |
4998 | all public symbols, one per line: |
5191 | all public symbols, one per line: |
4999 | .PP |
5192 | .PP |
… | |
… | |
5053 | \& #include "ev_cpp.h" |
5246 | \& #include "ev_cpp.h" |
5054 | \& #include "ev.c" |
5247 | \& #include "ev.c" |
5055 | .Ve |
5248 | .Ve |
5056 | .SH "INTERACTION WITH OTHER PROGRAMS, LIBRARIES OR THE ENVIRONMENT" |
5249 | .SH "INTERACTION WITH OTHER PROGRAMS, LIBRARIES OR THE ENVIRONMENT" |
5057 | .IX Header "INTERACTION WITH OTHER PROGRAMS, LIBRARIES OR THE ENVIRONMENT" |
5250 | .IX Header "INTERACTION WITH OTHER PROGRAMS, LIBRARIES OR THE ENVIRONMENT" |
5058 | .SS "\s-1THREADS\s0 \s-1AND\s0 \s-1COROUTINES\s0" |
5251 | .SS "\s-1THREADS AND COROUTINES\s0" |
5059 | .IX Subsection "THREADS AND COROUTINES" |
5252 | .IX Subsection "THREADS AND COROUTINES" |
5060 | \fI\s-1THREADS\s0\fR |
5253 | \fI\s-1THREADS\s0\fR |
5061 | .IX Subsection "THREADS" |
5254 | .IX Subsection "THREADS" |
5062 | .PP |
5255 | .PP |
5063 | All libev functions are reentrant and thread-safe unless explicitly |
5256 | All libev functions are reentrant and thread-safe unless explicitly |
… | |
… | |
5109 | An example use would be to communicate signals or other events that only |
5302 | An example use would be to communicate signals or other events that only |
5110 | work in the default loop by registering the signal watcher with the |
5303 | work in the default loop by registering the signal watcher with the |
5111 | default loop and triggering an \f(CW\*(C`ev_async\*(C'\fR watcher from the default loop |
5304 | default loop and triggering an \f(CW\*(C`ev_async\*(C'\fR watcher from the default loop |
5112 | watcher callback into the event loop interested in the signal. |
5305 | watcher callback into the event loop interested in the signal. |
5113 | .PP |
5306 | .PP |
5114 | See also \*(L"\s-1THREAD\s0 \s-1LOCKING\s0 \s-1EXAMPLE\s0\*(R". |
5307 | See also \*(L"\s-1THREAD LOCKING EXAMPLE\*(R"\s0. |
5115 | .PP |
5308 | .PP |
5116 | \fI\s-1COROUTINES\s0\fR |
5309 | \fI\s-1COROUTINES\s0\fR |
5117 | .IX Subsection "COROUTINES" |
5310 | .IX Subsection "COROUTINES" |
5118 | .PP |
5311 | .PP |
5119 | Libev is very accommodating to coroutines (\*(L"cooperative threads\*(R"): |
5312 | Libev is very accommodating to coroutines (\*(L"cooperative threads\*(R"): |
… | |
… | |
5124 | that you must not do this from \f(CW\*(C`ev_periodic\*(C'\fR reschedule callbacks. |
5317 | that you must not do this from \f(CW\*(C`ev_periodic\*(C'\fR reschedule callbacks. |
5125 | .PP |
5318 | .PP |
5126 | Care has been taken to ensure that libev does not keep local state inside |
5319 | Care has been taken to ensure that libev does not keep local state inside |
5127 | \&\f(CW\*(C`ev_run\*(C'\fR, and other calls do not usually allow for coroutine switches as |
5320 | \&\f(CW\*(C`ev_run\*(C'\fR, and other calls do not usually allow for coroutine switches as |
5128 | they do not call any callbacks. |
5321 | they do not call any callbacks. |
5129 | .SS "\s-1COMPILER\s0 \s-1WARNINGS\s0" |
5322 | .SS "\s-1COMPILER WARNINGS\s0" |
5130 | .IX Subsection "COMPILER WARNINGS" |
5323 | .IX Subsection "COMPILER WARNINGS" |
5131 | Depending on your compiler and compiler settings, you might get no or a |
5324 | Depending on your compiler and compiler settings, you might get no or a |
5132 | lot of warnings when compiling libev code. Some people are apparently |
5325 | lot of warnings when compiling libev code. Some people are apparently |
5133 | scared by this. |
5326 | scared by this. |
5134 | .PP |
5327 | .PP |
… | |
… | |
5186 | .PP |
5379 | .PP |
5187 | If you need, for some reason, empty reports from valgrind for your project |
5380 | If you need, for some reason, empty reports from valgrind for your project |
5188 | I suggest using suppression lists. |
5381 | I suggest using suppression lists. |
5189 | .SH "PORTABILITY NOTES" |
5382 | .SH "PORTABILITY NOTES" |
5190 | .IX Header "PORTABILITY NOTES" |
5383 | .IX Header "PORTABILITY NOTES" |
5191 | .SS "\s-1GNU/LINUX\s0 32 \s-1BIT\s0 \s-1LIMITATIONS\s0" |
5384 | .SS "\s-1GNU/LINUX 32 BIT LIMITATIONS\s0" |
5192 | .IX Subsection "GNU/LINUX 32 BIT LIMITATIONS" |
5385 | .IX Subsection "GNU/LINUX 32 BIT LIMITATIONS" |
5193 | GNU/Linux is the only common platform that supports 64 bit file/large file |
5386 | GNU/Linux is the only common platform that supports 64 bit file/large file |
5194 | interfaces but \fIdisables\fR them by default. |
5387 | interfaces but \fIdisables\fR them by default. |
5195 | .PP |
5388 | .PP |
5196 | That means that libev compiled in the default environment doesn't support |
5389 | That means that libev compiled in the default environment doesn't support |
5197 | files larger than 2GiB or so, which mainly affects \f(CW\*(C`ev_stat\*(C'\fR watchers. |
5390 | files larger than 2GiB or so, which mainly affects \f(CW\*(C`ev_stat\*(C'\fR watchers. |
5198 | .PP |
5391 | .PP |
5199 | Unfortunately, many programs try to work around this GNU/Linux issue |
5392 | Unfortunately, many programs try to work around this GNU/Linux issue |
5200 | by enabling the large file \s-1API\s0, which makes them incompatible with the |
5393 | by enabling the large file \s-1API,\s0 which makes them incompatible with the |
5201 | standard libev compiled for their system. |
5394 | standard libev compiled for their system. |
5202 | .PP |
5395 | .PP |
5203 | Likewise, libev cannot enable the large file \s-1API\s0 itself as this would |
5396 | Likewise, libev cannot enable the large file \s-1API\s0 itself as this would |
5204 | suddenly make it incompatible to the default compile time environment, |
5397 | suddenly make it incompatible to the default compile time environment, |
5205 | i.e. all programs not using special compile switches. |
5398 | i.e. all programs not using special compile switches. |
5206 | .SS "\s-1OS/X\s0 \s-1AND\s0 \s-1DARWIN\s0 \s-1BUGS\s0" |
5399 | .SS "\s-1OS/X AND DARWIN BUGS\s0" |
5207 | .IX Subsection "OS/X AND DARWIN BUGS" |
5400 | .IX Subsection "OS/X AND DARWIN BUGS" |
5208 | The whole thing is a bug if you ask me \- basically any system interface |
5401 | The whole thing is a bug if you ask me \- basically any system interface |
5209 | you touch is broken, whether it is locales, poll, kqueue or even the |
5402 | you touch is broken, whether it is locales, poll, kqueue or even the |
5210 | OpenGL drivers. |
5403 | OpenGL drivers. |
5211 | .PP |
5404 | .PP |
… | |
… | |
5233 | .PP |
5426 | .PP |
5234 | \fI\f(CI\*(C`select\*(C'\fI is buggy\fR |
5427 | \fI\f(CI\*(C`select\*(C'\fI is buggy\fR |
5235 | .IX Subsection "select is buggy" |
5428 | .IX Subsection "select is buggy" |
5236 | .PP |
5429 | .PP |
5237 | All that's left is \f(CW\*(C`select\*(C'\fR, and of course Apple found a way to fuck this |
5430 | All that's left is \f(CW\*(C`select\*(C'\fR, and of course Apple found a way to fuck this |
5238 | one up as well: On \s-1OS/X\s0, \f(CW\*(C`select\*(C'\fR actively limits the number of file |
5431 | one up as well: On \s-1OS/X,\s0 \f(CW\*(C`select\*(C'\fR actively limits the number of file |
5239 | descriptors you can pass in to 1024 \- your program suddenly crashes when |
5432 | descriptors you can pass in to 1024 \- your program suddenly crashes when |
5240 | you use more. |
5433 | you use more. |
5241 | .PP |
5434 | .PP |
5242 | There is an undocumented \*(L"workaround\*(R" for this \- defining |
5435 | There is an undocumented \*(L"workaround\*(R" for this \- defining |
5243 | \&\f(CW\*(C`_DARWIN_UNLIMITED_SELECT\*(C'\fR, which libev tries to use, so select \fIshould\fR |
5436 | \&\f(CW\*(C`_DARWIN_UNLIMITED_SELECT\*(C'\fR, which libev tries to use, so select \fIshould\fR |
5244 | work on \s-1OS/X\s0. |
5437 | work on \s-1OS/X.\s0 |
5245 | .SS "\s-1SOLARIS\s0 \s-1PROBLEMS\s0 \s-1AND\s0 \s-1WORKAROUNDS\s0" |
5438 | .SS "\s-1SOLARIS PROBLEMS AND WORKAROUNDS\s0" |
5246 | .IX Subsection "SOLARIS PROBLEMS AND WORKAROUNDS" |
5439 | .IX Subsection "SOLARIS PROBLEMS AND WORKAROUNDS" |
5247 | \fI\f(CI\*(C`errno\*(C'\fI reentrancy\fR |
5440 | \fI\f(CI\*(C`errno\*(C'\fI reentrancy\fR |
5248 | .IX Subsection "errno reentrancy" |
5441 | .IX Subsection "errno reentrancy" |
5249 | .PP |
5442 | .PP |
5250 | The default compile environment on Solaris is unfortunately so |
5443 | The default compile environment on Solaris is unfortunately so |
… | |
… | |
5267 | great. |
5460 | great. |
5268 | .PP |
5461 | .PP |
5269 | If you can't get it to work, you can try running the program by setting |
5462 | If you can't get it to work, you can try running the program by setting |
5270 | the environment variable \f(CW\*(C`LIBEV_FLAGS=3\*(C'\fR to only allow \f(CW\*(C`poll\*(C'\fR and |
5463 | the environment variable \f(CW\*(C`LIBEV_FLAGS=3\*(C'\fR to only allow \f(CW\*(C`poll\*(C'\fR and |
5271 | \&\f(CW\*(C`select\*(C'\fR backends. |
5464 | \&\f(CW\*(C`select\*(C'\fR backends. |
5272 | .SS "\s-1AIX\s0 \s-1POLL\s0 \s-1BUG\s0" |
5465 | .SS "\s-1AIX POLL BUG\s0" |
5273 | .IX Subsection "AIX POLL BUG" |
5466 | .IX Subsection "AIX POLL BUG" |
5274 | \&\s-1AIX\s0 unfortunately has a broken \f(CW\*(C`poll.h\*(C'\fR header. Libev works around |
5467 | \&\s-1AIX\s0 unfortunately has a broken \f(CW\*(C`poll.h\*(C'\fR header. Libev works around |
5275 | this by trying to avoid the poll backend altogether (i.e. it's not even |
5468 | this by trying to avoid the poll backend altogether (i.e. it's not even |
5276 | compiled in), which normally isn't a big problem as \f(CW\*(C`select\*(C'\fR works fine |
5469 | compiled in), which normally isn't a big problem as \f(CW\*(C`select\*(C'\fR works fine |
5277 | with large bitsets on \s-1AIX\s0, and \s-1AIX\s0 is dead anyway. |
5470 | with large bitsets on \s-1AIX,\s0 and \s-1AIX\s0 is dead anyway. |
5278 | .SS "\s-1WIN32\s0 \s-1PLATFORM\s0 \s-1LIMITATIONS\s0 \s-1AND\s0 \s-1WORKAROUNDS\s0" |
5471 | .SS "\s-1WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS\s0" |
5279 | .IX Subsection "WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS" |
5472 | .IX Subsection "WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS" |
5280 | \fIGeneral issues\fR |
5473 | \fIGeneral issues\fR |
5281 | .IX Subsection "General issues" |
5474 | .IX Subsection "General issues" |
5282 | .PP |
5475 | .PP |
5283 | Win32 doesn't support any of the standards (e.g. \s-1POSIX\s0) that libev |
5476 | Win32 doesn't support any of the standards (e.g. \s-1POSIX\s0) that libev |
… | |
… | |
5352 | \& #define EV_USE_SELECT 1 |
5545 | \& #define EV_USE_SELECT 1 |
5353 | \& #define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */ |
5546 | \& #define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */ |
5354 | .Ve |
5547 | .Ve |
5355 | .PP |
5548 | .PP |
5356 | Note that winsockets handling of fd sets is O(n), so you can easily get a |
5549 | Note that winsockets handling of fd sets is O(n), so you can easily get a |
5357 | complexity in the O(nA\*^X) range when using win32. |
5550 | complexity in the O(nX) range when using win32. |
5358 | .PP |
5551 | .PP |
5359 | \fILimited number of file descriptors\fR |
5552 | \fILimited number of file descriptors\fR |
5360 | .IX Subsection "Limited number of file descriptors" |
5553 | .IX Subsection "Limited number of file descriptors" |
5361 | .PP |
5554 | .PP |
5362 | Windows has numerous arbitrary (and low) limits on things. |
5555 | Windows has numerous arbitrary (and low) limits on things. |
… | |
… | |
5378 | by calling \f(CW\*(C`_setmaxstdio\*(C'\fR, which can increase this limit to \f(CW2048\fR |
5571 | by calling \f(CW\*(C`_setmaxstdio\*(C'\fR, which can increase this limit to \f(CW2048\fR |
5379 | (another arbitrary limit), but is broken in many versions of the Microsoft |
5572 | (another arbitrary limit), but is broken in many versions of the Microsoft |
5380 | runtime libraries. This might get you to about \f(CW512\fR or \f(CW2048\fR sockets |
5573 | runtime libraries. This might get you to about \f(CW512\fR or \f(CW2048\fR sockets |
5381 | (depending on windows version and/or the phase of the moon). To get more, |
5574 | (depending on windows version and/or the phase of the moon). To get more, |
5382 | you need to wrap all I/O functions and provide your own fd management, but |
5575 | you need to wrap all I/O functions and provide your own fd management, but |
5383 | the cost of calling select (O(nA\*^X)) will likely make this unworkable. |
5576 | the cost of calling select (O(nX)) will likely make this unworkable. |
5384 | .SS "\s-1PORTABILITY\s0 \s-1REQUIREMENTS\s0" |
5577 | .SS "\s-1PORTABILITY REQUIREMENTS\s0" |
5385 | .IX Subsection "PORTABILITY REQUIREMENTS" |
5578 | .IX Subsection "PORTABILITY REQUIREMENTS" |
5386 | In addition to a working ISO-C implementation and of course the |
5579 | In addition to a working ISO-C implementation and of course the |
5387 | backend-specific APIs, libev relies on a few additional extensions: |
5580 | backend-specific APIs, libev relies on a few additional extensions: |
5388 | .ie n .IP """void (*)(ev_watcher_type *, int revents)"" must have compatible calling conventions regardless of ""ev_watcher_type *""." 4 |
5581 | .ie n .IP """void (*)(ev_watcher_type *, int revents)"" must have compatible calling conventions regardless of ""ev_watcher_type *""." 4 |
5389 | .el .IP "\f(CWvoid (*)(ev_watcher_type *, int revents)\fR must have compatible calling conventions regardless of \f(CWev_watcher_type *\fR." 4 |
5582 | .el .IP "\f(CWvoid (*)(ev_watcher_type *, int revents)\fR must have compatible calling conventions regardless of \f(CWev_watcher_type *\fR." 4 |
5390 | .IX Item "void (*)(ev_watcher_type *, int revents) must have compatible calling conventions regardless of ev_watcher_type *." |
5583 | .IX Item "void (*)(ev_watcher_type *, int revents) must have compatible calling conventions regardless of ev_watcher_type *." |
5391 | Libev assumes not only that all watcher pointers have the same internal |
5584 | Libev assumes not only that all watcher pointers have the same internal |
5392 | structure (guaranteed by \s-1POSIX\s0 but not by \s-1ISO\s0 C for example), but it also |
5585 | structure (guaranteed by \s-1POSIX\s0 but not by \s-1ISO C\s0 for example), but it also |
5393 | assumes that the same (machine) code can be used to call any watcher |
5586 | assumes that the same (machine) code can be used to call any watcher |
5394 | callback: The watcher callbacks have different type signatures, but libev |
5587 | callback: The watcher callbacks have different type signatures, but libev |
5395 | calls them using an \f(CW\*(C`ev_watcher *\*(C'\fR internally. |
5588 | calls them using an \f(CW\*(C`ev_watcher *\*(C'\fR internally. |
|
|
5589 | .IP "null pointers and integer zero are represented by 0 bytes" 4 |
|
|
5590 | .IX Item "null pointers and integer zero are represented by 0 bytes" |
|
|
5591 | Libev uses \f(CW\*(C`memset\*(C'\fR to initialise structs and arrays to \f(CW0\fR bytes, and |
|
|
5592 | relies on this setting pointers and integers to null. |
5396 | .IP "pointer accesses must be thread-atomic" 4 |
5593 | .IP "pointer accesses must be thread-atomic" 4 |
5397 | .IX Item "pointer accesses must be thread-atomic" |
5594 | .IX Item "pointer accesses must be thread-atomic" |
5398 | Accessing a pointer value must be atomic, it must both be readable and |
5595 | Accessing a pointer value must be atomic, it must both be readable and |
5399 | writable in one piece \- this is the case on all current architectures. |
5596 | writable in one piece \- this is the case on all current architectures. |
5400 | .ie n .IP """sig_atomic_t volatile"" must be thread-atomic as well" 4 |
5597 | .ie n .IP """sig_atomic_t volatile"" must be thread-atomic as well" 4 |
… | |
… | |
5413 | thread\*(R" or will block signals process-wide, both behaviours would |
5610 | thread\*(R" or will block signals process-wide, both behaviours would |
5414 | be compatible with libev. Interaction between \f(CW\*(C`sigprocmask\*(C'\fR and |
5611 | be compatible with libev. Interaction between \f(CW\*(C`sigprocmask\*(C'\fR and |
5415 | \&\f(CW\*(C`pthread_sigmask\*(C'\fR could complicate things, however. |
5612 | \&\f(CW\*(C`pthread_sigmask\*(C'\fR could complicate things, however. |
5416 | .Sp |
5613 | .Sp |
5417 | The most portable way to handle signals is to block signals in all threads |
5614 | The most portable way to handle signals is to block signals in all threads |
5418 | except the initial one, and run the default loop in the initial thread as |
5615 | except the initial one, and run the signal handling loop in the initial |
5419 | well. |
5616 | thread as well. |
5420 | .ie n .IP """long"" must be large enough for common memory allocation sizes" 4 |
5617 | .ie n .IP """long"" must be large enough for common memory allocation sizes" 4 |
5421 | .el .IP "\f(CWlong\fR must be large enough for common memory allocation sizes" 4 |
5618 | .el .IP "\f(CWlong\fR must be large enough for common memory allocation sizes" 4 |
5422 | .IX Item "long must be large enough for common memory allocation sizes" |
5619 | .IX Item "long must be large enough for common memory allocation sizes" |
5423 | To improve portability and simplify its \s-1API\s0, libev uses \f(CW\*(C`long\*(C'\fR internally |
5620 | To improve portability and simplify its \s-1API,\s0 libev uses \f(CW\*(C`long\*(C'\fR internally |
5424 | instead of \f(CW\*(C`size_t\*(C'\fR when allocating its data structures. On non-POSIX |
5621 | instead of \f(CW\*(C`size_t\*(C'\fR when allocating its data structures. On non-POSIX |
5425 | systems (Microsoft...) this might be unexpectedly low, but is still at |
5622 | systems (Microsoft...) this might be unexpectedly low, but is still at |
5426 | least 31 bits everywhere, which is enough for hundreds of millions of |
5623 | least 31 bits everywhere, which is enough for hundreds of millions of |
5427 | watchers. |
5624 | watchers. |
5428 | .ie n .IP """double"" must hold a time value in seconds with enough accuracy" 4 |
5625 | .ie n .IP """double"" must hold a time value in seconds with enough accuracy" 4 |
… | |
… | |
5430 | .IX Item "double must hold a time value in seconds with enough accuracy" |
5627 | .IX Item "double must hold a time value in seconds with enough accuracy" |
5431 | The type \f(CW\*(C`double\*(C'\fR is used to represent timestamps. It is required to |
5628 | The type \f(CW\*(C`double\*(C'\fR is used to represent timestamps. It is required to |
5432 | have at least 51 bits of mantissa (and 9 bits of exponent), which is |
5629 | have at least 51 bits of mantissa (and 9 bits of exponent), which is |
5433 | good enough for at least into the year 4000 with millisecond accuracy |
5630 | good enough for at least into the year 4000 with millisecond accuracy |
5434 | (the design goal for libev). This requirement is overfulfilled by |
5631 | (the design goal for libev). This requirement is overfulfilled by |
5435 | implementations using \s-1IEEE\s0 754, which is basically all existing ones. |
5632 | implementations using \s-1IEEE 754,\s0 which is basically all existing ones. |
5436 | .Sp |
5633 | .Sp |
5437 | With \s-1IEEE\s0 754 doubles, you get microsecond accuracy until at least the |
5634 | With \s-1IEEE 754\s0 doubles, you get microsecond accuracy until at least the |
5438 | year 2255 (and millisecond accuracy till the year 287396 \- by then, libev |
5635 | year 2255 (and millisecond accuracy till the year 287396 \- by then, libev |
5439 | is either obsolete or somebody patched it to use \f(CW\*(C`long double\*(C'\fR or |
5636 | is either obsolete or somebody patched it to use \f(CW\*(C`long double\*(C'\fR or |
5440 | something like that, just kidding). |
5637 | something like that, just kidding). |
5441 | .PP |
5638 | .PP |
5442 | If you know of other additional requirements drop me a note. |
5639 | If you know of other additional requirements drop me a note. |
… | |
… | |
5504 | calls in the current loop iteration and the loop is currently |
5701 | calls in the current loop iteration and the loop is currently |
5505 | blocked. Checking for async and signal events involves iterating over all |
5702 | blocked. Checking for async and signal events involves iterating over all |
5506 | running async watchers or all signal numbers. |
5703 | running async watchers or all signal numbers. |
5507 | .SH "PORTING FROM LIBEV 3.X TO 4.X" |
5704 | .SH "PORTING FROM LIBEV 3.X TO 4.X" |
5508 | .IX Header "PORTING FROM LIBEV 3.X TO 4.X" |
5705 | .IX Header "PORTING FROM LIBEV 3.X TO 4.X" |
5509 | The major version 4 introduced some incompatible changes to the \s-1API\s0. |
5706 | The major version 4 introduced some incompatible changes to the \s-1API.\s0 |
5510 | .PP |
5707 | .PP |
5511 | At the moment, the \f(CW\*(C`ev.h\*(C'\fR header file provides compatibility definitions |
5708 | At the moment, the \f(CW\*(C`ev.h\*(C'\fR header file provides compatibility definitions |
5512 | for all changes, so most programs should still compile. The compatibility |
5709 | for all changes, so most programs should still compile. The compatibility |
5513 | layer might be removed in later versions of libev, so better update to the |
5710 | layer might be removed in later versions of libev, so better update to the |
5514 | new \s-1API\s0 early than late. |
5711 | new \s-1API\s0 early than late. |
5515 | .ie n .IP """EV_COMPAT3"" backwards compatibility mechanism" 4 |
5712 | .ie n .IP """EV_COMPAT3"" backwards compatibility mechanism" 4 |
5516 | .el .IP "\f(CWEV_COMPAT3\fR backwards compatibility mechanism" 4 |
5713 | .el .IP "\f(CWEV_COMPAT3\fR backwards compatibility mechanism" 4 |
5517 | .IX Item "EV_COMPAT3 backwards compatibility mechanism" |
5714 | .IX Item "EV_COMPAT3 backwards compatibility mechanism" |
5518 | The backward compatibility mechanism can be controlled by |
5715 | The backward compatibility mechanism can be controlled by |
5519 | \&\f(CW\*(C`EV_COMPAT3\*(C'\fR. See \*(L"\s-1PREPROCESSOR\s0 \s-1SYMBOLS/MACROS\s0\*(R" in the \*(L"\s-1EMBEDDING\s0\*(R" |
5716 | \&\f(CW\*(C`EV_COMPAT3\*(C'\fR. See \*(L"\s-1PREPROCESSOR SYMBOLS/MACROS\*(R"\s0 in the \*(L"\s-1EMBEDDING\*(R"\s0 |
5520 | section. |
5717 | section. |
5521 | .ie n .IP """ev_default_destroy"" and ""ev_default_fork"" have been removed" 4 |
5718 | .ie n .IP """ev_default_destroy"" and ""ev_default_fork"" have been removed" 4 |
5522 | .el .IP "\f(CWev_default_destroy\fR and \f(CWev_default_fork\fR have been removed" 4 |
5719 | .el .IP "\f(CWev_default_destroy\fR and \f(CWev_default_fork\fR have been removed" 4 |
5523 | .IX Item "ev_default_destroy and ev_default_fork have been removed" |
5720 | .IX Item "ev_default_destroy and ev_default_fork have been removed" |
5524 | These calls can be replaced easily by their \f(CW\*(C`ev_loop_xxx\*(C'\fR counterparts: |
5721 | These calls can be replaced easily by their \f(CW\*(C`ev_loop_xxx\*(C'\fR counterparts: |
… | |
… | |
5564 | .SH "GLOSSARY" |
5761 | .SH "GLOSSARY" |
5565 | .IX Header "GLOSSARY" |
5762 | .IX Header "GLOSSARY" |
5566 | .IP "active" 4 |
5763 | .IP "active" 4 |
5567 | .IX Item "active" |
5764 | .IX Item "active" |
5568 | A watcher is active as long as it has been started and not yet stopped. |
5765 | A watcher is active as long as it has been started and not yet stopped. |
5569 | See \*(L"\s-1WATCHER\s0 \s-1STATES\s0\*(R" for details. |
5766 | See \*(L"\s-1WATCHER STATES\*(R"\s0 for details. |
5570 | .IP "application" 4 |
5767 | .IP "application" 4 |
5571 | .IX Item "application" |
5768 | .IX Item "application" |
5572 | In this document, an application is whatever is using libev. |
5769 | In this document, an application is whatever is using libev. |
5573 | .IP "backend" 4 |
5770 | .IP "backend" 4 |
5574 | .IX Item "backend" |
5771 | .IX Item "backend" |
… | |
… | |
5601 | The model used to describe how an event loop handles and processes |
5798 | The model used to describe how an event loop handles and processes |
5602 | watchers and events. |
5799 | watchers and events. |
5603 | .IP "pending" 4 |
5800 | .IP "pending" 4 |
5604 | .IX Item "pending" |
5801 | .IX Item "pending" |
5605 | A watcher is pending as soon as the corresponding event has been |
5802 | A watcher is pending as soon as the corresponding event has been |
5606 | detected. See \*(L"\s-1WATCHER\s0 \s-1STATES\s0\*(R" for details. |
5803 | detected. See \*(L"\s-1WATCHER STATES\*(R"\s0 for details. |
5607 | .IP "real time" 4 |
5804 | .IP "real time" 4 |
5608 | .IX Item "real time" |
5805 | .IX Item "real time" |
5609 | The physical time that is observed. It is apparently strictly monotonic :) |
5806 | The physical time that is observed. It is apparently strictly monotonic :) |
5610 | .IP "wall-clock time" 4 |
5807 | .IP "wall-clock time" 4 |
5611 | .IX Item "wall-clock time" |
5808 | .IX Item "wall-clock time" |