… | |
… | |
105 | details of the event, and then hand it over to libev by I<starting> the |
105 | details of the event, and then hand it over to libev by I<starting> the |
106 | watcher. |
106 | watcher. |
107 | |
107 | |
108 | =head2 FEATURES |
108 | =head2 FEATURES |
109 | |
109 | |
110 | Libev supports C<select>, C<poll>, the Linux-specific C<epoll>, the |
110 | Libev supports C<select>, C<poll>, the Linux-specific aio and C<epoll> |
111 | BSD-specific C<kqueue> and the Solaris-specific event port mechanisms |
111 | interfaces, the BSD-specific C<kqueue> and the Solaris-specific event port |
112 | for file descriptor events (C<ev_io>), the Linux C<inotify> interface |
112 | mechanisms for file descriptor events (C<ev_io>), the Linux C<inotify> |
113 | (for C<ev_stat>), Linux eventfd/signalfd (for faster and cleaner |
113 | interface (for C<ev_stat>), Linux eventfd/signalfd (for faster and cleaner |
114 | inter-thread wakeup (C<ev_async>)/signal handling (C<ev_signal>)) relative |
114 | inter-thread wakeup (C<ev_async>)/signal handling (C<ev_signal>)) relative |
115 | timers (C<ev_timer>), absolute timers with customised rescheduling |
115 | timers (C<ev_timer>), absolute timers with customised rescheduling |
116 | (C<ev_periodic>), synchronous signals (C<ev_signal>), process status |
116 | (C<ev_periodic>), synchronous signals (C<ev_signal>), process status |
117 | change events (C<ev_child>), and event watchers dealing with the event |
117 | change events (C<ev_child>), and event watchers dealing with the event |
118 | loop mechanism itself (C<ev_idle>, C<ev_embed>, C<ev_prepare> and |
118 | loop mechanism itself (C<ev_idle>, C<ev_embed>, C<ev_prepare> and |
… | |
… | |
265 | |
265 | |
266 | You could override this function in high-availability programs to, say, |
266 | You could override this function in high-availability programs to, say, |
267 | free some memory if it cannot allocate memory, to use a special allocator, |
267 | free some memory if it cannot allocate memory, to use a special allocator, |
268 | or even to sleep a while and retry until some memory is available. |
268 | or even to sleep a while and retry until some memory is available. |
269 | |
269 | |
|
|
270 | Example: The following is the C<realloc> function that libev itself uses |
|
|
271 | which should work with C<realloc> and C<free> functions of all kinds and |
|
|
272 | is probably a good basis for your own implementation. |
|
|
273 | |
|
|
274 | static void * |
|
|
275 | ev_realloc_emul (void *ptr, long size) EV_NOEXCEPT |
|
|
276 | { |
|
|
277 | if (size) |
|
|
278 | return realloc (ptr, size); |
|
|
279 | |
|
|
280 | free (ptr); |
|
|
281 | return 0; |
|
|
282 | } |
|
|
283 | |
270 | Example: Replace the libev allocator with one that waits a bit and then |
284 | Example: Replace the libev allocator with one that waits a bit and then |
271 | retries (example requires a standards-compliant C<realloc>). |
285 | retries. |
272 | |
286 | |
273 | static void * |
287 | static void * |
274 | persistent_realloc (void *ptr, size_t size) |
288 | persistent_realloc (void *ptr, size_t size) |
275 | { |
289 | { |
|
|
290 | if (!size) |
|
|
291 | { |
|
|
292 | free (ptr); |
|
|
293 | return 0; |
|
|
294 | } |
|
|
295 | |
276 | for (;;) |
296 | for (;;) |
277 | { |
297 | { |
278 | void *newptr = realloc (ptr, size); |
298 | void *newptr = realloc (ptr, size); |
279 | |
299 | |
280 | if (newptr) |
300 | if (newptr) |
… | |
… | |
411 | make libev check for a fork in each iteration by enabling this flag. |
431 | make libev check for a fork in each iteration by enabling this flag. |
412 | |
432 | |
413 | This works by calling C<getpid ()> on every iteration of the loop, |
433 | This works by calling C<getpid ()> on every iteration of the loop, |
414 | and thus this might slow down your event loop if you do a lot of loop |
434 | and thus this might slow down your event loop if you do a lot of loop |
415 | iterations and little real work, but is usually not noticeable (on my |
435 | iterations and little real work, but is usually not noticeable (on my |
416 | GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence |
436 | GNU/Linux system for example, C<getpid> is actually a simple 5-insn |
417 | without a system call and thus I<very> fast, but my GNU/Linux system also has |
437 | sequence without a system call and thus I<very> fast, but my GNU/Linux |
418 | C<pthread_atfork> which is even faster). |
438 | system also has C<pthread_atfork> which is even faster). (Update: glibc |
|
|
439 | versions 2.25 apparently removed the C<getpid> optimisation again). |
419 | |
440 | |
420 | The big advantage of this flag is that you can forget about fork (and |
441 | The big advantage of this flag is that you can forget about fork (and |
421 | forget about forgetting to tell libev about forking, although you still |
442 | forget about forgetting to tell libev about forking, although you still |
422 | have to ignore C<SIGPIPE>) when you use this flag. |
443 | have to ignore C<SIGPIPE>) when you use this flag. |
423 | |
444 | |
… | |
… | |
546 | All this means that, in practice, C<EVBACKEND_SELECT> can be as fast or |
567 | All this means that, in practice, C<EVBACKEND_SELECT> can be as fast or |
547 | faster than epoll for maybe up to a hundred file descriptors, depending on |
568 | faster than epoll for maybe up to a hundred file descriptors, depending on |
548 | the usage. So sad. |
569 | the usage. So sad. |
549 | |
570 | |
550 | While nominally embeddable in other event loops, this feature is broken in |
571 | While nominally embeddable in other event loops, this feature is broken in |
551 | all kernel versions tested so far. |
572 | a lot of kernel revisions, but probably(!) works in current versions. |
|
|
573 | |
|
|
574 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
|
|
575 | C<EVBACKEND_POLL>. |
|
|
576 | |
|
|
577 | =item C<EVBACKEND_LINUXAIO> (value 64, Linux) |
|
|
578 | |
|
|
579 | Use the linux-specific linux aio (I<not> C<< aio(7) >> but C<< |
|
|
580 | io_submit(2) >>) event interface available in post-4.18 kernels (but libev |
|
|
581 | only tries to use it in 4.19+). |
|
|
582 | |
|
|
583 | This is another linux trainwreck of an event interface. |
|
|
584 | |
|
|
585 | If this backend works for you (as of this writing, it was very |
|
|
586 | experimental), it is the best event interface available on linux and might |
|
|
587 | be well worth enabling it - if it isn't available in your kernel this will |
|
|
588 | be detected and this backend will be skipped. |
|
|
589 | |
|
|
590 | This backend can batch oneshot requests and supports a user-space ring |
|
|
591 | buffer to receive events. It also doesn't suffer from most of the design |
|
|
592 | problems of epoll (such as not being able to remove event sources from |
|
|
593 | the epoll set), and generally sounds too good to be true. Because, this |
|
|
594 | being the linux kernel, of course it suffers from a whole new set of |
|
|
595 | limitations, forcing you to fall back to epoll, inheriting all its design |
|
|
596 | issues. |
|
|
597 | |
|
|
598 | For one, it is not easily embeddable (but probably could be done using |
|
|
599 | an event fd at some extra overhead). It also is subject to a system wide |
|
|
600 | limit that can be configured in F</proc/sys/fs/aio-max-nr>. If no aio |
|
|
601 | requests are left, this backend will be skipped during initialisation, and |
|
|
602 | will switch to epoll when the loop is active. |
|
|
603 | |
|
|
604 | Most problematic in practice, however, is that not all file descriptors |
|
|
605 | work with it. For example, in linux 5.1, tcp sockets, pipes, event fds, |
|
|
606 | files, F</dev/null> and a few others are supported, but ttys do not work |
|
|
607 | properly (a known bug that the kernel developers don't care about, see |
|
|
608 | L<https://lore.kernel.org/patchwork/patch/1047453/>), so this is not |
|
|
609 | (yet?) a generic event polling interface. |
|
|
610 | |
|
|
611 | Overall, it seems the linux developers just don't want it to have a |
|
|
612 | generic event handling mechanism other than C<select> or C<poll>. |
|
|
613 | |
|
|
614 | To work around all these problem, the current version of libev uses its |
|
|
615 | epoll backend as a fallback for file descriptor types that do not work. Or |
|
|
616 | falls back completely to epoll if the kernel acts up. |
552 | |
617 | |
553 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
618 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
554 | C<EVBACKEND_POLL>. |
619 | C<EVBACKEND_POLL>. |
555 | |
620 | |
556 | =item C<EVBACKEND_KQUEUE> (value 8, most BSD clones) |
621 | =item C<EVBACKEND_KQUEUE> (value 8, most BSD clones) |
… | |
… | |
657 | Example: Use whatever libev has to offer, but make sure that kqueue is |
722 | Example: Use whatever libev has to offer, but make sure that kqueue is |
658 | used if available. |
723 | used if available. |
659 | |
724 | |
660 | struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_KQUEUE); |
725 | struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_KQUEUE); |
661 | |
726 | |
|
|
727 | Example: Similarly, on linux, you mgiht want to take advantage of the |
|
|
728 | linux aio backend if possible, but fall back to something else if that |
|
|
729 | isn't available. |
|
|
730 | |
|
|
731 | struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_LINUXAIO); |
|
|
732 | |
662 | =item ev_loop_destroy (loop) |
733 | =item ev_loop_destroy (loop) |
663 | |
734 | |
664 | Destroys an event loop object (frees all memory and kernel state |
735 | Destroys an event loop object (frees all memory and kernel state |
665 | etc.). None of the active event watchers will be stopped in the normal |
736 | etc.). None of the active event watchers will be stopped in the normal |
666 | sense, so e.g. C<ev_is_active> might still return true. It is your |
737 | sense, so e.g. C<ev_is_active> might still return true. It is your |
… | |
… | |
689 | the name, you can call it anytime you are allowed to start or stop |
760 | the name, you can call it anytime you are allowed to start or stop |
690 | watchers (except inside an C<ev_prepare> callback), but it makes most |
761 | watchers (except inside an C<ev_prepare> callback), but it makes most |
691 | sense after forking, in the child process. You I<must> call it (or use |
762 | sense after forking, in the child process. You I<must> call it (or use |
692 | C<EVFLAG_FORKCHECK>) in the child before resuming or calling C<ev_run>. |
763 | C<EVFLAG_FORKCHECK>) in the child before resuming or calling C<ev_run>. |
693 | |
764 | |
694 | In addition, if you want to reuse a loop (via this function of |
765 | In addition, if you want to reuse a loop (via this function or |
695 | C<EVFLAG_FORKCHECK>), you I<also> have to ignore C<SIGPIPE>. |
766 | C<EVFLAG_FORKCHECK>), you I<also> have to ignore C<SIGPIPE>. |
696 | |
767 | |
697 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
768 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
698 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
769 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
699 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
770 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
… | |
… | |
1609 | |
1680 | |
1610 | But really, best use non-blocking mode. |
1681 | But really, best use non-blocking mode. |
1611 | |
1682 | |
1612 | =head3 The special problem of disappearing file descriptors |
1683 | =head3 The special problem of disappearing file descriptors |
1613 | |
1684 | |
1614 | Some backends (e.g. kqueue, epoll) need to be told about closing a file |
1685 | Some backends (e.g. kqueue, epoll, linuxaio) need to be told about closing |
1615 | descriptor (either due to calling C<close> explicitly or any other means, |
1686 | a file descriptor (either due to calling C<close> explicitly or any other |
1616 | such as C<dup2>). The reason is that you register interest in some file |
1687 | means, such as C<dup2>). The reason is that you register interest in some |
1617 | descriptor, but when it goes away, the operating system will silently drop |
1688 | file descriptor, but when it goes away, the operating system will silently |
1618 | this interest. If another file descriptor with the same number then is |
1689 | drop this interest. If another file descriptor with the same number then |
1619 | registered with libev, there is no efficient way to see that this is, in |
1690 | is registered with libev, there is no efficient way to see that this is, |
1620 | fact, a different file descriptor. |
1691 | in fact, a different file descriptor. |
1621 | |
1692 | |
1622 | To avoid having to explicitly tell libev about such cases, libev follows |
1693 | To avoid having to explicitly tell libev about such cases, libev follows |
1623 | the following policy: Each time C<ev_io_set> is being called, libev |
1694 | the following policy: Each time C<ev_io_set> is being called, libev |
1624 | will assume that this is potentially a new file descriptor, otherwise |
1695 | will assume that this is potentially a new file descriptor, otherwise |
1625 | it is assumed that the file descriptor stays the same. That means that |
1696 | it is assumed that the file descriptor stays the same. That means that |
… | |
… | |
1674 | when you rarely read from a file instead of from a socket, and want to |
1745 | when you rarely read from a file instead of from a socket, and want to |
1675 | reuse the same code path. |
1746 | reuse the same code path. |
1676 | |
1747 | |
1677 | =head3 The special problem of fork |
1748 | =head3 The special problem of fork |
1678 | |
1749 | |
1679 | Some backends (epoll, kqueue) do not support C<fork ()> at all or exhibit |
1750 | Some backends (epoll, kqueue, probably linuxaio) do not support C<fork ()> |
1680 | useless behaviour. Libev fully supports fork, but needs to be told about |
1751 | at all or exhibit useless behaviour. Libev fully supports fork, but needs |
1681 | it in the child if you want to continue to use it in the child. |
1752 | to be told about it in the child if you want to continue to use it in the |
|
|
1753 | child. |
1682 | |
1754 | |
1683 | To support fork in your child processes, you have to call C<ev_loop_fork |
1755 | To support fork in your child processes, you have to call C<ev_loop_fork |
1684 | ()> after a fork in the child, enable C<EVFLAG_FORKCHECK>, or resort to |
1756 | ()> after a fork in the child, enable C<EVFLAG_FORKCHECK>, or resort to |
1685 | C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>. |
1757 | C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>. |
1686 | |
1758 | |
… | |
… | |
2113 | |
2185 | |
2114 | =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat) |
2186 | =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat) |
2115 | |
2187 | |
2116 | =item ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat) |
2188 | =item ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat) |
2117 | |
2189 | |
2118 | Configure the timer to trigger after C<after> seconds. If C<repeat> |
2190 | Configure the timer to trigger after C<after> seconds (fractional and |
2119 | is C<0.>, then it will automatically be stopped once the timeout is |
2191 | negative values are supported). If C<repeat> is C<0.>, then it will |
2120 | reached. If it is positive, then the timer will automatically be |
2192 | automatically be stopped once the timeout is reached. If it is positive, |
2121 | configured to trigger again C<repeat> seconds later, again, and again, |
2193 | then the timer will automatically be configured to trigger again C<repeat> |
2122 | until stopped manually. |
2194 | seconds later, again, and again, until stopped manually. |
2123 | |
2195 | |
2124 | The timer itself will do a best-effort at avoiding drift, that is, if |
2196 | The timer itself will do a best-effort at avoiding drift, that is, if |
2125 | you configure a timer to trigger every 10 seconds, then it will normally |
2197 | you configure a timer to trigger every 10 seconds, then it will normally |
2126 | trigger at exactly 10 second intervals. If, however, your program cannot |
2198 | trigger at exactly 10 second intervals. If, however, your program cannot |
2127 | keep up with the timer (because it takes longer than those 10 seconds to |
2199 | keep up with the timer (because it takes longer than those 10 seconds to |
… | |
… | |
2209 | Periodic watchers are also timers of a kind, but they are very versatile |
2281 | Periodic watchers are also timers of a kind, but they are very versatile |
2210 | (and unfortunately a bit complex). |
2282 | (and unfortunately a bit complex). |
2211 | |
2283 | |
2212 | Unlike C<ev_timer>, periodic watchers are not based on real time (or |
2284 | Unlike C<ev_timer>, periodic watchers are not based on real time (or |
2213 | relative time, the physical time that passes) but on wall clock time |
2285 | relative time, the physical time that passes) but on wall clock time |
2214 | (absolute time, the thing you can read on your calender or clock). The |
2286 | (absolute time, the thing you can read on your calendar or clock). The |
2215 | difference is that wall clock time can run faster or slower than real |
2287 | difference is that wall clock time can run faster or slower than real |
2216 | time, and time jumps are not uncommon (e.g. when you adjust your |
2288 | time, and time jumps are not uncommon (e.g. when you adjust your |
2217 | wrist-watch). |
2289 | wrist-watch). |
2218 | |
2290 | |
2219 | You can tell a periodic watcher to trigger after some specific point |
2291 | You can tell a periodic watcher to trigger after some specific point |
… | |
… | |
2224 | C<ev_timer>, which would still trigger roughly 10 seconds after starting |
2296 | C<ev_timer>, which would still trigger roughly 10 seconds after starting |
2225 | it, as it uses a relative timeout). |
2297 | it, as it uses a relative timeout). |
2226 | |
2298 | |
2227 | C<ev_periodic> watchers can also be used to implement vastly more complex |
2299 | C<ev_periodic> watchers can also be used to implement vastly more complex |
2228 | timers, such as triggering an event on each "midnight, local time", or |
2300 | timers, such as triggering an event on each "midnight, local time", or |
2229 | other complicated rules. This cannot be done with C<ev_timer> watchers, as |
2301 | other complicated rules. This cannot easily be done with C<ev_timer> |
2230 | those cannot react to time jumps. |
2302 | watchers, as those cannot react to time jumps. |
2231 | |
2303 | |
2232 | As with timers, the callback is guaranteed to be invoked only when the |
2304 | As with timers, the callback is guaranteed to be invoked only when the |
2233 | point in time where it is supposed to trigger has passed. If multiple |
2305 | point in time where it is supposed to trigger has passed. If multiple |
2234 | timers become ready during the same loop iteration then the ones with |
2306 | timers become ready during the same loop iteration then the ones with |
2235 | earlier time-out values are invoked before ones with later time-out values |
2307 | earlier time-out values are invoked before ones with later time-out values |
… | |
… | |
2321 | |
2393 | |
2322 | NOTE: I<< This callback must always return a time that is higher than or |
2394 | NOTE: I<< This callback must always return a time that is higher than or |
2323 | equal to the passed C<now> value >>. |
2395 | equal to the passed C<now> value >>. |
2324 | |
2396 | |
2325 | This can be used to create very complex timers, such as a timer that |
2397 | This can be used to create very complex timers, such as a timer that |
2326 | triggers on "next midnight, local time". To do this, you would calculate the |
2398 | triggers on "next midnight, local time". To do this, you would calculate |
2327 | next midnight after C<now> and return the timestamp value for this. How |
2399 | the next midnight after C<now> and return the timestamp value for |
2328 | you do this is, again, up to you (but it is not trivial, which is the main |
2400 | this. Here is a (completely untested, no error checking) example on how to |
2329 | reason I omitted it as an example). |
2401 | do this: |
|
|
2402 | |
|
|
2403 | #include <time.h> |
|
|
2404 | |
|
|
2405 | static ev_tstamp |
|
|
2406 | my_rescheduler (ev_periodic *w, ev_tstamp now) |
|
|
2407 | { |
|
|
2408 | time_t tnow = (time_t)now; |
|
|
2409 | struct tm tm; |
|
|
2410 | localtime_r (&tnow, &tm); |
|
|
2411 | |
|
|
2412 | tm.tm_sec = tm.tm_min = tm.tm_hour = 0; // midnight current day |
|
|
2413 | ++tm.tm_mday; // midnight next day |
|
|
2414 | |
|
|
2415 | return mktime (&tm); |
|
|
2416 | } |
|
|
2417 | |
|
|
2418 | Note: this code might run into trouble on days that have more then two |
|
|
2419 | midnights (beginning and end). |
2330 | |
2420 | |
2331 | =back |
2421 | =back |
2332 | |
2422 | |
2333 | =item ev_periodic_again (loop, ev_periodic *) |
2423 | =item ev_periodic_again (loop, ev_periodic *) |
2334 | |
2424 | |
… | |
… | |
3517 | |
3607 | |
3518 | There are some other functions of possible interest. Described. Here. Now. |
3608 | There are some other functions of possible interest. Described. Here. Now. |
3519 | |
3609 | |
3520 | =over 4 |
3610 | =over 4 |
3521 | |
3611 | |
3522 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
3612 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback, arg) |
3523 | |
3613 | |
3524 | This function combines a simple timer and an I/O watcher, calls your |
3614 | This function combines a simple timer and an I/O watcher, calls your |
3525 | callback on whichever event happens first and automatically stops both |
3615 | callback on whichever event happens first and automatically stops both |
3526 | watchers. This is useful if you want to wait for a single event on an fd |
3616 | watchers. This is useful if you want to wait for a single event on an fd |
3527 | or timeout without having to allocate/configure/start/stop/free one or |
3617 | or timeout without having to allocate/configure/start/stop/free one or |
… | |
… | |
3959 | The normal C API should work fine when used from C++: both ev.h and the |
4049 | The normal C API should work fine when used from C++: both ev.h and the |
3960 | libev sources can be compiled as C++. Therefore, code that uses the C API |
4050 | libev sources can be compiled as C++. Therefore, code that uses the C API |
3961 | will work fine. |
4051 | will work fine. |
3962 | |
4052 | |
3963 | Proper exception specifications might have to be added to callbacks passed |
4053 | Proper exception specifications might have to be added to callbacks passed |
3964 | to libev: exceptions may be thrown only from watcher callbacks, all |
4054 | to libev: exceptions may be thrown only from watcher callbacks, all other |
3965 | other callbacks (allocator, syserr, loop acquire/release and periodic |
4055 | callbacks (allocator, syserr, loop acquire/release and periodic reschedule |
3966 | reschedule callbacks) must not throw exceptions, and might need a C<throw |
4056 | callbacks) must not throw exceptions, and might need a C<noexcept> |
3967 | ()> specification. If you have code that needs to be compiled as both C |
4057 | specification. If you have code that needs to be compiled as both C and |
3968 | and C++ you can use the C<EV_THROW> macro for this: |
4058 | C++ you can use the C<EV_NOEXCEPT> macro for this: |
3969 | |
4059 | |
3970 | static void |
4060 | static void |
3971 | fatal_error (const char *msg) EV_THROW |
4061 | fatal_error (const char *msg) EV_NOEXCEPT |
3972 | { |
4062 | { |
3973 | perror (msg); |
4063 | perror (msg); |
3974 | abort (); |
4064 | abort (); |
3975 | } |
4065 | } |
3976 | |
4066 | |
… | |
… | |
4386 | ev_vars.h |
4476 | ev_vars.h |
4387 | ev_wrap.h |
4477 | ev_wrap.h |
4388 | |
4478 | |
4389 | ev_win32.c required on win32 platforms only |
4479 | ev_win32.c required on win32 platforms only |
4390 | |
4480 | |
4391 | ev_select.c only when select backend is enabled (which is enabled by default) |
4481 | ev_select.c only when select backend is enabled |
4392 | ev_poll.c only when poll backend is enabled (disabled by default) |
4482 | ev_poll.c only when poll backend is enabled |
4393 | ev_epoll.c only when the epoll backend is enabled (disabled by default) |
4483 | ev_epoll.c only when the epoll backend is enabled |
|
|
4484 | ev_linuxaio.c only when the linux aio backend is enabled |
4394 | ev_kqueue.c only when the kqueue backend is enabled (disabled by default) |
4485 | ev_kqueue.c only when the kqueue backend is enabled |
4395 | ev_port.c only when the solaris port backend is enabled (disabled by default) |
4486 | ev_port.c only when the solaris port backend is enabled |
4396 | |
4487 | |
4397 | F<ev.c> includes the backend files directly when enabled, so you only need |
4488 | F<ev.c> includes the backend files directly when enabled, so you only need |
4398 | to compile this single file. |
4489 | to compile this single file. |
4399 | |
4490 | |
4400 | =head3 LIBEVENT COMPATIBILITY API |
4491 | =head3 LIBEVENT COMPATIBILITY API |
… | |
… | |
4588 | If defined to be C<1>, libev will compile in support for the Linux |
4679 | If defined to be C<1>, libev will compile in support for the Linux |
4589 | C<epoll>(7) backend. Its availability will be detected at runtime, |
4680 | C<epoll>(7) backend. Its availability will be detected at runtime, |
4590 | otherwise another method will be used as fallback. This is the preferred |
4681 | otherwise another method will be used as fallback. This is the preferred |
4591 | backend for GNU/Linux systems. If undefined, it will be enabled if the |
4682 | backend for GNU/Linux systems. If undefined, it will be enabled if the |
4592 | headers indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
4683 | headers indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
|
|
4684 | |
|
|
4685 | =item EV_USE_LINUXAIO |
|
|
4686 | |
|
|
4687 | If defined to be C<1>, libev will compile in support for the Linux |
|
|
4688 | aio backend. Due to it's currenbt limitations it has to be requested |
|
|
4689 | explicitly. If undefined, it will be enabled on linux, otherwise |
|
|
4690 | disabled. |
4593 | |
4691 | |
4594 | =item EV_USE_KQUEUE |
4692 | =item EV_USE_KQUEUE |
4595 | |
4693 | |
4596 | If defined to be C<1>, libev will compile in support for the BSD style |
4694 | If defined to be C<1>, libev will compile in support for the BSD style |
4597 | C<kqueue>(2) backend. Its actual availability will be detected at runtime, |
4695 | C<kqueue>(2) backend. Its actual availability will be detected at runtime, |
… | |
… | |
5300 | structure (guaranteed by POSIX but not by ISO C for example), but it also |
5398 | structure (guaranteed by POSIX but not by ISO C for example), but it also |
5301 | assumes that the same (machine) code can be used to call any watcher |
5399 | assumes that the same (machine) code can be used to call any watcher |
5302 | callback: The watcher callbacks have different type signatures, but libev |
5400 | callback: The watcher callbacks have different type signatures, but libev |
5303 | calls them using an C<ev_watcher *> internally. |
5401 | calls them using an C<ev_watcher *> internally. |
5304 | |
5402 | |
|
|
5403 | =item null pointers and integer zero are represented by 0 bytes |
|
|
5404 | |
|
|
5405 | Libev uses C<memset> to initialise structs and arrays to C<0> bytes, and |
|
|
5406 | relies on this setting pointers and integers to null. |
|
|
5407 | |
5305 | =item pointer accesses must be thread-atomic |
5408 | =item pointer accesses must be thread-atomic |
5306 | |
5409 | |
5307 | Accessing a pointer value must be atomic, it must both be readable and |
5410 | Accessing a pointer value must be atomic, it must both be readable and |
5308 | writable in one piece - this is the case on all current architectures. |
5411 | writable in one piece - this is the case on all current architectures. |
5309 | |
5412 | |