|
|
1 | =encoding utf-8 |
|
|
2 | |
1 | =head1 NAME |
3 | =head1 NAME |
2 | |
4 | |
3 | libev - a high performance full-featured event loop written in C |
5 | libev - a high performance full-featured event loop written in C |
4 | |
6 | |
5 | =head1 SYNOPSIS |
7 | =head1 SYNOPSIS |
… | |
… | |
103 | 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 |
104 | watcher. |
106 | watcher. |
105 | |
107 | |
106 | =head2 FEATURES |
108 | =head2 FEATURES |
107 | |
109 | |
108 | 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> |
109 | BSD-specific C<kqueue> and the Solaris-specific event port mechanisms |
111 | interfaces, the BSD-specific C<kqueue> and the Solaris-specific event port |
110 | 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> |
111 | (for C<ev_stat>), Linux eventfd/signalfd (for faster and cleaner |
113 | interface (for C<ev_stat>), Linux eventfd/signalfd (for faster and cleaner |
112 | 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 |
113 | timers (C<ev_timer>), absolute timers with customised rescheduling |
115 | timers (C<ev_timer>), absolute timers with customised rescheduling |
114 | (C<ev_periodic>), synchronous signals (C<ev_signal>), process status |
116 | (C<ev_periodic>), synchronous signals (C<ev_signal>), process status |
115 | 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 |
116 | 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 |
… | |
… | |
157 | When libev detects a usage error such as a negative timer interval, then |
159 | When libev detects a usage error such as a negative timer interval, then |
158 | it will print a diagnostic message and abort (via the C<assert> mechanism, |
160 | it will print a diagnostic message and abort (via the C<assert> mechanism, |
159 | so C<NDEBUG> will disable this checking): these are programming errors in |
161 | so C<NDEBUG> will disable this checking): these are programming errors in |
160 | the libev caller and need to be fixed there. |
162 | the libev caller and need to be fixed there. |
161 | |
163 | |
|
|
164 | Via the C<EV_FREQUENT> macro you can compile in and/or enable extensive |
|
|
165 | consistency checking code inside libev that can be used to check for |
|
|
166 | internal inconsistencies, suually caused by application bugs. |
|
|
167 | |
162 | Libev also has a few internal error-checking C<assert>ions, and also has |
168 | Libev also has a few internal error-checking C<assert>ions. These do not |
163 | extensive consistency checking code. These do not trigger under normal |
|
|
164 | circumstances, as they indicate either a bug in libev or worse. |
169 | trigger under normal circumstances, as they indicate either a bug in libev |
|
|
170 | or worse. |
165 | |
171 | |
166 | |
172 | |
167 | =head1 GLOBAL FUNCTIONS |
173 | =head1 GLOBAL FUNCTIONS |
168 | |
174 | |
169 | These functions can be called anytime, even before initialising the |
175 | These functions can be called anytime, even before initialising the |
… | |
… | |
263 | |
269 | |
264 | You could override this function in high-availability programs to, say, |
270 | You could override this function in high-availability programs to, say, |
265 | free some memory if it cannot allocate memory, to use a special allocator, |
271 | free some memory if it cannot allocate memory, to use a special allocator, |
266 | or even to sleep a while and retry until some memory is available. |
272 | or even to sleep a while and retry until some memory is available. |
267 | |
273 | |
|
|
274 | Example: The following is the C<realloc> function that libev itself uses |
|
|
275 | which should work with C<realloc> and C<free> functions of all kinds and |
|
|
276 | is probably a good basis for your own implementation. |
|
|
277 | |
|
|
278 | static void * |
|
|
279 | ev_realloc_emul (void *ptr, long size) EV_NOEXCEPT |
|
|
280 | { |
|
|
281 | if (size) |
|
|
282 | return realloc (ptr, size); |
|
|
283 | |
|
|
284 | free (ptr); |
|
|
285 | return 0; |
|
|
286 | } |
|
|
287 | |
268 | Example: Replace the libev allocator with one that waits a bit and then |
288 | Example: Replace the libev allocator with one that waits a bit and then |
269 | retries (example requires a standards-compliant C<realloc>). |
289 | retries. |
270 | |
290 | |
271 | static void * |
291 | static void * |
272 | persistent_realloc (void *ptr, size_t size) |
292 | persistent_realloc (void *ptr, size_t size) |
273 | { |
293 | { |
|
|
294 | if (!size) |
|
|
295 | { |
|
|
296 | free (ptr); |
|
|
297 | return 0; |
|
|
298 | } |
|
|
299 | |
274 | for (;;) |
300 | for (;;) |
275 | { |
301 | { |
276 | void *newptr = realloc (ptr, size); |
302 | void *newptr = realloc (ptr, size); |
277 | |
303 | |
278 | if (newptr) |
304 | if (newptr) |
… | |
… | |
396 | |
422 | |
397 | If this flag bit is or'ed into the flag value (or the program runs setuid |
423 | If this flag bit is or'ed into the flag value (or the program runs setuid |
398 | or setgid) then libev will I<not> look at the environment variable |
424 | or setgid) then libev will I<not> look at the environment variable |
399 | C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will |
425 | C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will |
400 | override the flags completely if it is found in the environment. This is |
426 | override the flags completely if it is found in the environment. This is |
401 | useful to try out specific backends to test their performance, or to work |
427 | useful to try out specific backends to test their performance, to work |
402 | around bugs. |
428 | around bugs, or to make libev threadsafe (accessing environment variables |
|
|
429 | cannot be done in a threadsafe way, but usually it works if no other |
|
|
430 | thread modifies them). |
403 | |
431 | |
404 | =item C<EVFLAG_FORKCHECK> |
432 | =item C<EVFLAG_FORKCHECK> |
405 | |
433 | |
406 | Instead of calling C<ev_loop_fork> manually after a fork, you can also |
434 | Instead of calling C<ev_loop_fork> manually after a fork, you can also |
407 | make libev check for a fork in each iteration by enabling this flag. |
435 | make libev check for a fork in each iteration by enabling this flag. |
408 | |
436 | |
409 | This works by calling C<getpid ()> on every iteration of the loop, |
437 | This works by calling C<getpid ()> on every iteration of the loop, |
410 | and thus this might slow down your event loop if you do a lot of loop |
438 | and thus this might slow down your event loop if you do a lot of loop |
411 | iterations and little real work, but is usually not noticeable (on my |
439 | iterations and little real work, but is usually not noticeable (on my |
412 | GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence |
440 | GNU/Linux system for example, C<getpid> is actually a simple 5-insn |
413 | without a system call and thus I<very> fast, but my GNU/Linux system also has |
441 | sequence without a system call and thus I<very> fast, but my GNU/Linux |
414 | C<pthread_atfork> which is even faster). |
442 | system also has C<pthread_atfork> which is even faster). (Update: glibc |
|
|
443 | versions 2.25 apparently removed the C<getpid> optimisation again). |
415 | |
444 | |
416 | The big advantage of this flag is that you can forget about fork (and |
445 | The big advantage of this flag is that you can forget about fork (and |
417 | forget about forgetting to tell libev about forking) when you use this |
446 | forget about forgetting to tell libev about forking, although you still |
418 | flag. |
447 | have to ignore C<SIGPIPE>) when you use this flag. |
419 | |
448 | |
420 | This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS> |
449 | This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS> |
421 | environment variable. |
450 | environment variable. |
422 | |
451 | |
423 | =item C<EVFLAG_NOINOTIFY> |
452 | =item C<EVFLAG_NOINOTIFY> |
… | |
… | |
486 | This backend maps C<EV_READ> to C<POLLIN | POLLERR | POLLHUP>, and |
515 | This backend maps C<EV_READ> to C<POLLIN | POLLERR | POLLHUP>, and |
487 | C<EV_WRITE> to C<POLLOUT | POLLERR | POLLHUP>. |
516 | C<EV_WRITE> to C<POLLOUT | POLLERR | POLLHUP>. |
488 | |
517 | |
489 | =item C<EVBACKEND_EPOLL> (value 4, Linux) |
518 | =item C<EVBACKEND_EPOLL> (value 4, Linux) |
490 | |
519 | |
491 | Use the linux-specific epoll(7) interface (for both pre- and post-2.6.9 |
520 | Use the Linux-specific epoll(7) interface (for both pre- and post-2.6.9 |
492 | kernels). |
521 | kernels). |
493 | |
522 | |
494 | For few fds, this backend is a bit little slower than poll and select, but |
523 | For few fds, this backend is a bit little slower than poll and select, but |
495 | it scales phenomenally better. While poll and select usually scale like |
524 | it scales phenomenally better. While poll and select usually scale like |
496 | O(total_fds) where total_fds is the total number of fds (or the highest |
525 | O(total_fds) where total_fds is the total number of fds (or the highest |
… | |
… | |
542 | All this means that, in practice, C<EVBACKEND_SELECT> can be as fast or |
571 | All this means that, in practice, C<EVBACKEND_SELECT> can be as fast or |
543 | faster than epoll for maybe up to a hundred file descriptors, depending on |
572 | faster than epoll for maybe up to a hundred file descriptors, depending on |
544 | the usage. So sad. |
573 | the usage. So sad. |
545 | |
574 | |
546 | While nominally embeddable in other event loops, this feature is broken in |
575 | While nominally embeddable in other event loops, this feature is broken in |
547 | all kernel versions tested so far. |
576 | a lot of kernel revisions, but probably(!) works in current versions. |
548 | |
577 | |
549 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
578 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
550 | C<EVBACKEND_POLL>. |
579 | C<EVBACKEND_POLL>. |
551 | |
580 | |
|
|
581 | =item C<EVBACKEND_LINUXAIO> (value 64, Linux) |
|
|
582 | |
|
|
583 | Use the Linux-specific Linux AIO (I<not> C<< aio(7) >> but C<< |
|
|
584 | io_submit(2) >>) event interface available in post-4.18 kernels (but libev |
|
|
585 | only tries to use it in 4.19+). |
|
|
586 | |
|
|
587 | This is another Linux train wreck of an event interface. |
|
|
588 | |
|
|
589 | If this backend works for you (as of this writing, it was very |
|
|
590 | experimental), it is the best event interface available on Linux and might |
|
|
591 | be well worth enabling it - if it isn't available in your kernel this will |
|
|
592 | be detected and this backend will be skipped. |
|
|
593 | |
|
|
594 | This backend can batch oneshot requests and supports a user-space ring |
|
|
595 | buffer to receive events. It also doesn't suffer from most of the design |
|
|
596 | problems of epoll (such as not being able to remove event sources from |
|
|
597 | the epoll set), and generally sounds too good to be true. Because, this |
|
|
598 | being the Linux kernel, of course it suffers from a whole new set of |
|
|
599 | limitations, forcing you to fall back to epoll, inheriting all its design |
|
|
600 | issues. |
|
|
601 | |
|
|
602 | For one, it is not easily embeddable (but probably could be done using |
|
|
603 | an event fd at some extra overhead). It also is subject to a system wide |
|
|
604 | limit that can be configured in F</proc/sys/fs/aio-max-nr>. If no AIO |
|
|
605 | requests are left, this backend will be skipped during initialisation, and |
|
|
606 | will switch to epoll when the loop is active. |
|
|
607 | |
|
|
608 | Most problematic in practice, however, is that not all file descriptors |
|
|
609 | work with it. For example, in Linux 5.1, TCP sockets, pipes, event fds, |
|
|
610 | files, F</dev/null> and many others are supported, but ttys do not work |
|
|
611 | properly (a known bug that the kernel developers don't care about, see |
|
|
612 | L<https://lore.kernel.org/patchwork/patch/1047453/>), so this is not |
|
|
613 | (yet?) a generic event polling interface. |
|
|
614 | |
|
|
615 | Overall, it seems the Linux developers just don't want it to have a |
|
|
616 | generic event handling mechanism other than C<select> or C<poll>. |
|
|
617 | |
|
|
618 | To work around all these problem, the current version of libev uses its |
|
|
619 | epoll backend as a fallback for file descriptor types that do not work. Or |
|
|
620 | falls back completely to epoll if the kernel acts up. |
|
|
621 | |
|
|
622 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
|
|
623 | C<EVBACKEND_POLL>. |
|
|
624 | |
552 | =item C<EVBACKEND_KQUEUE> (value 8, most BSD clones) |
625 | =item C<EVBACKEND_KQUEUE> (value 8, most BSD clones) |
553 | |
626 | |
554 | Kqueue deserves special mention, as at the time of this writing, it |
627 | Kqueue deserves special mention, as at the time this backend was |
555 | was broken on all BSDs except NetBSD (usually it doesn't work reliably |
628 | implemented, it was broken on all BSDs except NetBSD (usually it doesn't |
556 | with anything but sockets and pipes, except on Darwin, where of course |
629 | work reliably with anything but sockets and pipes, except on Darwin, |
557 | it's completely useless). Unlike epoll, however, whose brokenness |
630 | where of course it's completely useless). Unlike epoll, however, whose |
558 | is by design, these kqueue bugs can (and eventually will) be fixed |
631 | brokenness is by design, these kqueue bugs can be (and mostly have been) |
559 | without API changes to existing programs. For this reason it's not being |
632 | fixed without API changes to existing programs. For this reason it's not |
560 | "auto-detected" unless you explicitly specify it in the flags (i.e. using |
633 | being "auto-detected" on all platforms unless you explicitly specify it |
561 | C<EVBACKEND_KQUEUE>) or libev was compiled on a known-to-be-good (-enough) |
634 | in the flags (i.e. using C<EVBACKEND_KQUEUE>) or libev was compiled on a |
562 | system like NetBSD. |
635 | known-to-be-good (-enough) system like NetBSD. |
563 | |
636 | |
564 | You still can embed kqueue into a normal poll or select backend and use it |
637 | You still can embed kqueue into a normal poll or select backend and use it |
565 | only for sockets (after having made sure that sockets work with kqueue on |
638 | only for sockets (after having made sure that sockets work with kqueue on |
566 | the target platform). See C<ev_embed> watchers for more info. |
639 | the target platform). See C<ev_embed> watchers for more info. |
567 | |
640 | |
568 | It scales in the same way as the epoll backend, but the interface to the |
641 | It scales in the same way as the epoll backend, but the interface to the |
569 | kernel is more efficient (which says nothing about its actual speed, of |
642 | kernel is more efficient (which says nothing about its actual speed, of |
570 | course). While stopping, setting and starting an I/O watcher does never |
643 | course). While stopping, setting and starting an I/O watcher does never |
571 | cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to |
644 | cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to |
572 | two event changes per incident. Support for C<fork ()> is very bad (you |
645 | two event changes per incident. Support for C<fork ()> is very bad (you |
573 | might have to leak fd's on fork, but it's more sane than epoll) and it |
646 | might have to leak fds on fork, but it's more sane than epoll) and it |
574 | drops fds silently in similarly hard-to-detect cases. |
647 | drops fds silently in similarly hard-to-detect cases. |
575 | |
648 | |
576 | This backend usually performs well under most conditions. |
649 | This backend usually performs well under most conditions. |
577 | |
650 | |
578 | While nominally embeddable in other event loops, this doesn't work |
651 | While nominally embeddable in other event loops, this doesn't work |
… | |
… | |
653 | Example: Use whatever libev has to offer, but make sure that kqueue is |
726 | Example: Use whatever libev has to offer, but make sure that kqueue is |
654 | used if available. |
727 | used if available. |
655 | |
728 | |
656 | struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_KQUEUE); |
729 | struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_KQUEUE); |
657 | |
730 | |
|
|
731 | Example: Similarly, on linux, you mgiht want to take advantage of the |
|
|
732 | linux aio backend if possible, but fall back to something else if that |
|
|
733 | isn't available. |
|
|
734 | |
|
|
735 | struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_LINUXAIO); |
|
|
736 | |
658 | =item ev_loop_destroy (loop) |
737 | =item ev_loop_destroy (loop) |
659 | |
738 | |
660 | Destroys an event loop object (frees all memory and kernel state |
739 | Destroys an event loop object (frees all memory and kernel state |
661 | etc.). None of the active event watchers will be stopped in the normal |
740 | etc.). None of the active event watchers will be stopped in the normal |
662 | sense, so e.g. C<ev_is_active> might still return true. It is your |
741 | sense, so e.g. C<ev_is_active> might still return true. It is your |
… | |
… | |
678 | If you need dynamically allocated loops it is better to use C<ev_loop_new> |
757 | If you need dynamically allocated loops it is better to use C<ev_loop_new> |
679 | and C<ev_loop_destroy>. |
758 | and C<ev_loop_destroy>. |
680 | |
759 | |
681 | =item ev_loop_fork (loop) |
760 | =item ev_loop_fork (loop) |
682 | |
761 | |
683 | This function sets a flag that causes subsequent C<ev_run> iterations to |
762 | This function sets a flag that causes subsequent C<ev_run> iterations |
684 | reinitialise the kernel state for backends that have one. Despite the |
763 | to reinitialise the kernel state for backends that have one. Despite |
685 | name, you can call it anytime, but it makes most sense after forking, in |
764 | the name, you can call it anytime you are allowed to start or stop |
686 | the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the |
765 | watchers (except inside an C<ev_prepare> callback), but it makes most |
|
|
766 | sense after forking, in the child process. You I<must> call it (or use |
687 | child before resuming or calling C<ev_run>. |
767 | C<EVFLAG_FORKCHECK>) in the child before resuming or calling C<ev_run>. |
688 | |
768 | |
|
|
769 | In addition, if you want to reuse a loop (via this function or |
|
|
770 | C<EVFLAG_FORKCHECK>), you I<also> have to ignore C<SIGPIPE>. |
|
|
771 | |
689 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
772 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
690 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
773 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
691 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
774 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
692 | during fork. |
775 | during fork. |
693 | |
776 | |
694 | On the other hand, you only need to call this function in the child |
777 | On the other hand, you only need to call this function in the child |
… | |
… | |
1601 | |
1684 | |
1602 | But really, best use non-blocking mode. |
1685 | But really, best use non-blocking mode. |
1603 | |
1686 | |
1604 | =head3 The special problem of disappearing file descriptors |
1687 | =head3 The special problem of disappearing file descriptors |
1605 | |
1688 | |
1606 | Some backends (e.g. kqueue, epoll) need to be told about closing a file |
1689 | Some backends (e.g. kqueue, epoll, linuxaio) need to be told about closing |
1607 | descriptor (either due to calling C<close> explicitly or any other means, |
1690 | a file descriptor (either due to calling C<close> explicitly or any other |
1608 | such as C<dup2>). The reason is that you register interest in some file |
1691 | means, such as C<dup2>). The reason is that you register interest in some |
1609 | descriptor, but when it goes away, the operating system will silently drop |
1692 | file descriptor, but when it goes away, the operating system will silently |
1610 | this interest. If another file descriptor with the same number then is |
1693 | drop this interest. If another file descriptor with the same number then |
1611 | registered with libev, there is no efficient way to see that this is, in |
1694 | is registered with libev, there is no efficient way to see that this is, |
1612 | fact, a different file descriptor. |
1695 | in fact, a different file descriptor. |
1613 | |
1696 | |
1614 | To avoid having to explicitly tell libev about such cases, libev follows |
1697 | To avoid having to explicitly tell libev about such cases, libev follows |
1615 | the following policy: Each time C<ev_io_set> is being called, libev |
1698 | the following policy: Each time C<ev_io_set> is being called, libev |
1616 | will assume that this is potentially a new file descriptor, otherwise |
1699 | will assume that this is potentially a new file descriptor, otherwise |
1617 | it is assumed that the file descriptor stays the same. That means that |
1700 | it is assumed that the file descriptor stays the same. That means that |
… | |
… | |
1666 | when you rarely read from a file instead of from a socket, and want to |
1749 | when you rarely read from a file instead of from a socket, and want to |
1667 | reuse the same code path. |
1750 | reuse the same code path. |
1668 | |
1751 | |
1669 | =head3 The special problem of fork |
1752 | =head3 The special problem of fork |
1670 | |
1753 | |
1671 | Some backends (epoll, kqueue) do not support C<fork ()> at all or exhibit |
1754 | Some backends (epoll, kqueue, linuxaio, iouring) do not support C<fork ()> |
1672 | useless behaviour. Libev fully supports fork, but needs to be told about |
1755 | at all or exhibit useless behaviour. Libev fully supports fork, but needs |
1673 | it in the child if you want to continue to use it in the child. |
1756 | to be told about it in the child if you want to continue to use it in the |
|
|
1757 | child. |
1674 | |
1758 | |
1675 | To support fork in your child processes, you have to call C<ev_loop_fork |
1759 | To support fork in your child processes, you have to call C<ev_loop_fork |
1676 | ()> after a fork in the child, enable C<EVFLAG_FORKCHECK>, or resort to |
1760 | ()> after a fork in the child, enable C<EVFLAG_FORKCHECK>, or resort to |
1677 | C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>. |
1761 | C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>. |
1678 | |
1762 | |
… | |
… | |
2024 | |
2108 | |
2025 | The relative timeouts are calculated relative to the C<ev_now ()> |
2109 | The relative timeouts are calculated relative to the C<ev_now ()> |
2026 | time. This is usually the right thing as this timestamp refers to the time |
2110 | time. This is usually the right thing as this timestamp refers to the time |
2027 | of the event triggering whatever timeout you are modifying/starting. If |
2111 | of the event triggering whatever timeout you are modifying/starting. If |
2028 | you suspect event processing to be delayed and you I<need> to base the |
2112 | you suspect event processing to be delayed and you I<need> to base the |
2029 | timeout on the current time, use something like this to adjust for this: |
2113 | timeout on the current time, use something like the following to adjust |
|
|
2114 | for it: |
2030 | |
2115 | |
2031 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
2116 | ev_timer_set (&timer, after + (ev_time () - ev_now ()), 0.); |
2032 | |
2117 | |
2033 | If the event loop is suspended for a long time, you can also force an |
2118 | If the event loop is suspended for a long time, you can also force an |
2034 | update of the time returned by C<ev_now ()> by calling C<ev_now_update |
2119 | update of the time returned by C<ev_now ()> by calling C<ev_now_update |
2035 | ()>. |
2120 | ()>, although that will push the event time of all outstanding events |
|
|
2121 | further into the future. |
2036 | |
2122 | |
2037 | =head3 The special problem of unsynchronised clocks |
2123 | =head3 The special problem of unsynchronised clocks |
2038 | |
2124 | |
2039 | Modern systems have a variety of clocks - libev itself uses the normal |
2125 | Modern systems have a variety of clocks - libev itself uses the normal |
2040 | "wall clock" clock and, if available, the monotonic clock (to avoid time |
2126 | "wall clock" clock and, if available, the monotonic clock (to avoid time |
… | |
… | |
2103 | |
2189 | |
2104 | =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat) |
2190 | =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat) |
2105 | |
2191 | |
2106 | =item ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat) |
2192 | =item ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat) |
2107 | |
2193 | |
2108 | Configure the timer to trigger after C<after> seconds. If C<repeat> |
2194 | Configure the timer to trigger after C<after> seconds (fractional and |
2109 | is C<0.>, then it will automatically be stopped once the timeout is |
2195 | negative values are supported). If C<repeat> is C<0.>, then it will |
2110 | reached. If it is positive, then the timer will automatically be |
2196 | automatically be stopped once the timeout is reached. If it is positive, |
2111 | configured to trigger again C<repeat> seconds later, again, and again, |
2197 | then the timer will automatically be configured to trigger again C<repeat> |
2112 | until stopped manually. |
2198 | seconds later, again, and again, until stopped manually. |
2113 | |
2199 | |
2114 | The timer itself will do a best-effort at avoiding drift, that is, if |
2200 | The timer itself will do a best-effort at avoiding drift, that is, if |
2115 | you configure a timer to trigger every 10 seconds, then it will normally |
2201 | you configure a timer to trigger every 10 seconds, then it will normally |
2116 | trigger at exactly 10 second intervals. If, however, your program cannot |
2202 | trigger at exactly 10 second intervals. If, however, your program cannot |
2117 | keep up with the timer (because it takes longer than those 10 seconds to |
2203 | keep up with the timer (because it takes longer than those 10 seconds to |
… | |
… | |
2199 | Periodic watchers are also timers of a kind, but they are very versatile |
2285 | Periodic watchers are also timers of a kind, but they are very versatile |
2200 | (and unfortunately a bit complex). |
2286 | (and unfortunately a bit complex). |
2201 | |
2287 | |
2202 | Unlike C<ev_timer>, periodic watchers are not based on real time (or |
2288 | Unlike C<ev_timer>, periodic watchers are not based on real time (or |
2203 | relative time, the physical time that passes) but on wall clock time |
2289 | relative time, the physical time that passes) but on wall clock time |
2204 | (absolute time, the thing you can read on your calender or clock). The |
2290 | (absolute time, the thing you can read on your calendar or clock). The |
2205 | difference is that wall clock time can run faster or slower than real |
2291 | difference is that wall clock time can run faster or slower than real |
2206 | time, and time jumps are not uncommon (e.g. when you adjust your |
2292 | time, and time jumps are not uncommon (e.g. when you adjust your |
2207 | wrist-watch). |
2293 | wrist-watch). |
2208 | |
2294 | |
2209 | You can tell a periodic watcher to trigger after some specific point |
2295 | You can tell a periodic watcher to trigger after some specific point |
… | |
… | |
2214 | C<ev_timer>, which would still trigger roughly 10 seconds after starting |
2300 | C<ev_timer>, which would still trigger roughly 10 seconds after starting |
2215 | it, as it uses a relative timeout). |
2301 | it, as it uses a relative timeout). |
2216 | |
2302 | |
2217 | C<ev_periodic> watchers can also be used to implement vastly more complex |
2303 | C<ev_periodic> watchers can also be used to implement vastly more complex |
2218 | timers, such as triggering an event on each "midnight, local time", or |
2304 | timers, such as triggering an event on each "midnight, local time", or |
2219 | other complicated rules. This cannot be done with C<ev_timer> watchers, as |
2305 | other complicated rules. This cannot easily be done with C<ev_timer> |
2220 | those cannot react to time jumps. |
2306 | watchers, as those cannot react to time jumps. |
2221 | |
2307 | |
2222 | As with timers, the callback is guaranteed to be invoked only when the |
2308 | As with timers, the callback is guaranteed to be invoked only when the |
2223 | point in time where it is supposed to trigger has passed. If multiple |
2309 | point in time where it is supposed to trigger has passed. If multiple |
2224 | timers become ready during the same loop iteration then the ones with |
2310 | timers become ready during the same loop iteration then the ones with |
2225 | earlier time-out values are invoked before ones with later time-out values |
2311 | earlier time-out values are invoked before ones with later time-out values |
… | |
… | |
2311 | |
2397 | |
2312 | NOTE: I<< This callback must always return a time that is higher than or |
2398 | NOTE: I<< This callback must always return a time that is higher than or |
2313 | equal to the passed C<now> value >>. |
2399 | equal to the passed C<now> value >>. |
2314 | |
2400 | |
2315 | This can be used to create very complex timers, such as a timer that |
2401 | This can be used to create very complex timers, such as a timer that |
2316 | triggers on "next midnight, local time". To do this, you would calculate the |
2402 | triggers on "next midnight, local time". To do this, you would calculate |
2317 | next midnight after C<now> and return the timestamp value for this. How |
2403 | the next midnight after C<now> and return the timestamp value for |
2318 | you do this is, again, up to you (but it is not trivial, which is the main |
2404 | this. Here is a (completely untested, no error checking) example on how to |
2319 | reason I omitted it as an example). |
2405 | do this: |
|
|
2406 | |
|
|
2407 | #include <time.h> |
|
|
2408 | |
|
|
2409 | static ev_tstamp |
|
|
2410 | my_rescheduler (ev_periodic *w, ev_tstamp now) |
|
|
2411 | { |
|
|
2412 | time_t tnow = (time_t)now; |
|
|
2413 | struct tm tm; |
|
|
2414 | localtime_r (&tnow, &tm); |
|
|
2415 | |
|
|
2416 | tm.tm_sec = tm.tm_min = tm.tm_hour = 0; // midnight current day |
|
|
2417 | ++tm.tm_mday; // midnight next day |
|
|
2418 | |
|
|
2419 | return mktime (&tm); |
|
|
2420 | } |
|
|
2421 | |
|
|
2422 | Note: this code might run into trouble on days that have more then two |
|
|
2423 | midnights (beginning and end). |
2320 | |
2424 | |
2321 | =back |
2425 | =back |
2322 | |
2426 | |
2323 | =item ev_periodic_again (loop, ev_periodic *) |
2427 | =item ev_periodic_again (loop, ev_periodic *) |
2324 | |
2428 | |
… | |
… | |
2389 | |
2493 | |
2390 | ev_periodic hourly_tick; |
2494 | ev_periodic hourly_tick; |
2391 | ev_periodic_init (&hourly_tick, clock_cb, |
2495 | ev_periodic_init (&hourly_tick, clock_cb, |
2392 | fmod (ev_now (loop), 3600.), 3600., 0); |
2496 | fmod (ev_now (loop), 3600.), 3600., 0); |
2393 | ev_periodic_start (loop, &hourly_tick); |
2497 | ev_periodic_start (loop, &hourly_tick); |
2394 | |
2498 | |
2395 | |
2499 | |
2396 | =head2 C<ev_signal> - signal me when a signal gets signalled! |
2500 | =head2 C<ev_signal> - signal me when a signal gets signalled! |
2397 | |
2501 | |
2398 | Signal watchers will trigger an event when the process receives a specific |
2502 | Signal watchers will trigger an event when the process receives a specific |
2399 | signal one or more times. Even though signals are very asynchronous, libev |
2503 | signal one or more times. Even though signals are very asynchronous, libev |
… | |
… | |
2409 | only within the same loop, i.e. you can watch for C<SIGINT> in your |
2513 | only within the same loop, i.e. you can watch for C<SIGINT> in your |
2410 | default loop and for C<SIGIO> in another loop, but you cannot watch for |
2514 | default loop and for C<SIGIO> in another loop, but you cannot watch for |
2411 | C<SIGINT> in both the default loop and another loop at the same time. At |
2515 | C<SIGINT> in both the default loop and another loop at the same time. At |
2412 | the moment, C<SIGCHLD> is permanently tied to the default loop. |
2516 | the moment, C<SIGCHLD> is permanently tied to the default loop. |
2413 | |
2517 | |
2414 | When the first watcher gets started will libev actually register something |
2518 | Only after the first watcher for a signal is started will libev actually |
2415 | with the kernel (thus it coexists with your own signal handlers as long as |
2519 | register something with the kernel. It thus coexists with your own signal |
2416 | you don't register any with libev for the same signal). |
2520 | handlers as long as you don't register any with libev for the same signal. |
2417 | |
2521 | |
2418 | If possible and supported, libev will install its handlers with |
2522 | If possible and supported, libev will install its handlers with |
2419 | C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should |
2523 | C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should |
2420 | not be unduly interrupted. If you have a problem with system calls getting |
2524 | not be unduly interrupted. If you have a problem with system calls getting |
2421 | interrupted by signals you can block all signals in an C<ev_check> watcher |
2525 | interrupted by signals you can block all signals in an C<ev_check> watcher |
… | |
… | |
2903 | |
3007 | |
2904 | Prepare and check watchers are often (but not always) used in pairs: |
3008 | Prepare and check watchers are often (but not always) used in pairs: |
2905 | prepare watchers get invoked before the process blocks and check watchers |
3009 | prepare watchers get invoked before the process blocks and check watchers |
2906 | afterwards. |
3010 | afterwards. |
2907 | |
3011 | |
2908 | You I<must not> call C<ev_run> or similar functions that enter |
3012 | You I<must not> call C<ev_run> (or similar functions that enter the |
2909 | the current event loop from either C<ev_prepare> or C<ev_check> |
3013 | current event loop) or C<ev_loop_fork> from either C<ev_prepare> or |
2910 | watchers. Other loops than the current one are fine, however. The |
3014 | C<ev_check> watchers. Other loops than the current one are fine, |
2911 | rationale behind this is that you do not need to check for recursion in |
3015 | however. The rationale behind this is that you do not need to check |
2912 | those watchers, i.e. the sequence will always be C<ev_prepare>, blocking, |
3016 | for recursion in those watchers, i.e. the sequence will always be |
2913 | C<ev_check> so if you have one watcher of each kind they will always be |
3017 | C<ev_prepare>, blocking, C<ev_check> so if you have one watcher of each |
2914 | called in pairs bracketing the blocking call. |
3018 | kind they will always be called in pairs bracketing the blocking call. |
2915 | |
3019 | |
2916 | Their main purpose is to integrate other event mechanisms into libev and |
3020 | Their main purpose is to integrate other event mechanisms into libev and |
2917 | their use is somewhat advanced. They could be used, for example, to track |
3021 | their use is somewhat advanced. They could be used, for example, to track |
2918 | variable changes, implement your own watchers, integrate net-snmp or a |
3022 | variable changes, implement your own watchers, integrate net-snmp or a |
2919 | coroutine library and lots more. They are also occasionally useful if |
3023 | coroutine library and lots more. They are also occasionally useful if |
… | |
… | |
3209 | used). |
3313 | used). |
3210 | |
3314 | |
3211 | struct ev_loop *loop_hi = ev_default_init (0); |
3315 | struct ev_loop *loop_hi = ev_default_init (0); |
3212 | struct ev_loop *loop_lo = 0; |
3316 | struct ev_loop *loop_lo = 0; |
3213 | ev_embed embed; |
3317 | ev_embed embed; |
3214 | |
3318 | |
3215 | // see if there is a chance of getting one that works |
3319 | // see if there is a chance of getting one that works |
3216 | // (remember that a flags value of 0 means autodetection) |
3320 | // (remember that a flags value of 0 means autodetection) |
3217 | loop_lo = ev_embeddable_backends () & ev_recommended_backends () |
3321 | loop_lo = ev_embeddable_backends () & ev_recommended_backends () |
3218 | ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ()) |
3322 | ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ()) |
3219 | : 0; |
3323 | : 0; |
… | |
… | |
3233 | C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too). |
3337 | C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too). |
3234 | |
3338 | |
3235 | struct ev_loop *loop = ev_default_init (0); |
3339 | struct ev_loop *loop = ev_default_init (0); |
3236 | struct ev_loop *loop_socket = 0; |
3340 | struct ev_loop *loop_socket = 0; |
3237 | ev_embed embed; |
3341 | ev_embed embed; |
3238 | |
3342 | |
3239 | if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE) |
3343 | if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE) |
3240 | if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE)) |
3344 | if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE)) |
3241 | { |
3345 | { |
3242 | ev_embed_init (&embed, 0, loop_socket); |
3346 | ev_embed_init (&embed, 0, loop_socket); |
3243 | ev_embed_start (loop, &embed); |
3347 | ev_embed_start (loop, &embed); |
… | |
… | |
3259 | and calls it in the wrong process, the fork handlers will be invoked, too, |
3363 | and calls it in the wrong process, the fork handlers will be invoked, too, |
3260 | of course. |
3364 | of course. |
3261 | |
3365 | |
3262 | =head3 The special problem of life after fork - how is it possible? |
3366 | =head3 The special problem of life after fork - how is it possible? |
3263 | |
3367 | |
3264 | Most uses of C<fork()> consist of forking, then some simple calls to set |
3368 | Most uses of C<fork ()> consist of forking, then some simple calls to set |
3265 | up/change the process environment, followed by a call to C<exec()>. This |
3369 | up/change the process environment, followed by a call to C<exec()>. This |
3266 | sequence should be handled by libev without any problems. |
3370 | sequence should be handled by libev without any problems. |
3267 | |
3371 | |
3268 | This changes when the application actually wants to do event handling |
3372 | This changes when the application actually wants to do event handling |
3269 | in the child, or both parent in child, in effect "continuing" after the |
3373 | in the child, or both parent in child, in effect "continuing" after the |
… | |
… | |
3507 | |
3611 | |
3508 | There are some other functions of possible interest. Described. Here. Now. |
3612 | There are some other functions of possible interest. Described. Here. Now. |
3509 | |
3613 | |
3510 | =over 4 |
3614 | =over 4 |
3511 | |
3615 | |
3512 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
3616 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback, arg) |
3513 | |
3617 | |
3514 | This function combines a simple timer and an I/O watcher, calls your |
3618 | This function combines a simple timer and an I/O watcher, calls your |
3515 | callback on whichever event happens first and automatically stops both |
3619 | callback on whichever event happens first and automatically stops both |
3516 | watchers. This is useful if you want to wait for a single event on an fd |
3620 | watchers. This is useful if you want to wait for a single event on an fd |
3517 | or timeout without having to allocate/configure/start/stop/free one or |
3621 | or timeout without having to allocate/configure/start/stop/free one or |
… | |
… | |
3893 | To embed libev, see L</EMBEDDING>, but in short, it's easiest to create two |
3997 | To embed libev, see L</EMBEDDING>, but in short, it's easiest to create two |
3894 | files, F<my_ev.h> and F<my_ev.c> that include the respective libev files: |
3998 | files, F<my_ev.h> and F<my_ev.c> that include the respective libev files: |
3895 | |
3999 | |
3896 | // my_ev.h |
4000 | // my_ev.h |
3897 | #define EV_CB_DECLARE(type) struct my_coro *cb; |
4001 | #define EV_CB_DECLARE(type) struct my_coro *cb; |
3898 | #define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb); |
4002 | #define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb) |
3899 | #include "../libev/ev.h" |
4003 | #include "../libev/ev.h" |
3900 | |
4004 | |
3901 | // my_ev.c |
4005 | // my_ev.c |
3902 | #define EV_H "my_ev.h" |
4006 | #define EV_H "my_ev.h" |
3903 | #include "../libev/ev.c" |
4007 | #include "../libev/ev.c" |
… | |
… | |
3949 | The normal C API should work fine when used from C++: both ev.h and the |
4053 | The normal C API should work fine when used from C++: both ev.h and the |
3950 | libev sources can be compiled as C++. Therefore, code that uses the C API |
4054 | libev sources can be compiled as C++. Therefore, code that uses the C API |
3951 | will work fine. |
4055 | will work fine. |
3952 | |
4056 | |
3953 | Proper exception specifications might have to be added to callbacks passed |
4057 | Proper exception specifications might have to be added to callbacks passed |
3954 | to libev: exceptions may be thrown only from watcher callbacks, all |
4058 | to libev: exceptions may be thrown only from watcher callbacks, all other |
3955 | other callbacks (allocator, syserr, loop acquire/release and periodic |
4059 | callbacks (allocator, syserr, loop acquire/release and periodic reschedule |
3956 | reschedule callbacks) must not throw exceptions, and might need a C<throw |
4060 | callbacks) must not throw exceptions, and might need a C<noexcept> |
3957 | ()> specification. If you have code that needs to be compiled as both C |
4061 | specification. If you have code that needs to be compiled as both C and |
3958 | and C++ you can use the C<EV_THROW> macro for this: |
4062 | C++ you can use the C<EV_NOEXCEPT> macro for this: |
3959 | |
4063 | |
3960 | static void |
4064 | static void |
3961 | fatal_error (const char *msg) EV_THROW |
4065 | fatal_error (const char *msg) EV_NOEXCEPT |
3962 | { |
4066 | { |
3963 | perror (msg); |
4067 | perror (msg); |
3964 | abort (); |
4068 | abort (); |
3965 | } |
4069 | } |
3966 | |
4070 | |
… | |
… | |
3980 | Libev comes with some simplistic wrapper classes for C++ that mainly allow |
4084 | Libev comes with some simplistic wrapper classes for C++ that mainly allow |
3981 | you to use some convenience methods to start/stop watchers and also change |
4085 | you to use some convenience methods to start/stop watchers and also change |
3982 | the callback model to a model using method callbacks on objects. |
4086 | the callback model to a model using method callbacks on objects. |
3983 | |
4087 | |
3984 | To use it, |
4088 | To use it, |
3985 | |
4089 | |
3986 | #include <ev++.h> |
4090 | #include <ev++.h> |
3987 | |
4091 | |
3988 | This automatically includes F<ev.h> and puts all of its definitions (many |
4092 | This automatically includes F<ev.h> and puts all of its definitions (many |
3989 | of them macros) into the global namespace. All C++ specific things are |
4093 | of them macros) into the global namespace. All C++ specific things are |
3990 | put into the C<ev> namespace. It should support all the same embedding |
4094 | put into the C<ev> namespace. It should support all the same embedding |
… | |
… | |
4093 | void operator() (ev::io &w, int revents) |
4197 | void operator() (ev::io &w, int revents) |
4094 | { |
4198 | { |
4095 | ... |
4199 | ... |
4096 | } |
4200 | } |
4097 | } |
4201 | } |
4098 | |
4202 | |
4099 | myfunctor f; |
4203 | myfunctor f; |
4100 | |
4204 | |
4101 | ev::io w; |
4205 | ev::io w; |
4102 | w.set (&f); |
4206 | w.set (&f); |
4103 | |
4207 | |
… | |
… | |
4376 | ev_vars.h |
4480 | ev_vars.h |
4377 | ev_wrap.h |
4481 | ev_wrap.h |
4378 | |
4482 | |
4379 | ev_win32.c required on win32 platforms only |
4483 | ev_win32.c required on win32 platforms only |
4380 | |
4484 | |
4381 | ev_select.c only when select backend is enabled (which is enabled by default) |
4485 | ev_select.c only when select backend is enabled |
4382 | ev_poll.c only when poll backend is enabled (disabled by default) |
4486 | ev_poll.c only when poll backend is enabled |
4383 | ev_epoll.c only when the epoll backend is enabled (disabled by default) |
4487 | ev_epoll.c only when the epoll backend is enabled |
|
|
4488 | ev_linuxaio.c only when the linux aio backend is enabled |
|
|
4489 | ev_iouring.c only when the linux io_uring backend is enabled |
4384 | ev_kqueue.c only when the kqueue backend is enabled (disabled by default) |
4490 | ev_kqueue.c only when the kqueue backend is enabled |
4385 | ev_port.c only when the solaris port backend is enabled (disabled by default) |
4491 | ev_port.c only when the solaris port backend is enabled |
4386 | |
4492 | |
4387 | F<ev.c> includes the backend files directly when enabled, so you only need |
4493 | F<ev.c> includes the backend files directly when enabled, so you only need |
4388 | to compile this single file. |
4494 | to compile this single file. |
4389 | |
4495 | |
4390 | =head3 LIBEVENT COMPATIBILITY API |
4496 | =head3 LIBEVENT COMPATIBILITY API |
… | |
… | |
4578 | If defined to be C<1>, libev will compile in support for the Linux |
4684 | If defined to be C<1>, libev will compile in support for the Linux |
4579 | C<epoll>(7) backend. Its availability will be detected at runtime, |
4685 | C<epoll>(7) backend. Its availability will be detected at runtime, |
4580 | otherwise another method will be used as fallback. This is the preferred |
4686 | otherwise another method will be used as fallback. This is the preferred |
4581 | backend for GNU/Linux systems. If undefined, it will be enabled if the |
4687 | backend for GNU/Linux systems. If undefined, it will be enabled if the |
4582 | headers indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
4688 | headers indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
|
|
4689 | |
|
|
4690 | =item EV_USE_LINUXAIO |
|
|
4691 | |
|
|
4692 | If defined to be C<1>, libev will compile in support for the Linux aio |
|
|
4693 | backend (C<EV_USE_EPOLL> must also be enabled). If undefined, it will be |
|
|
4694 | enabled on linux, otherwise disabled. |
|
|
4695 | |
|
|
4696 | =item EV_USE_IOURING |
|
|
4697 | |
|
|
4698 | If defined to be C<1>, libev will compile in support for the Linux |
|
|
4699 | io_uring backend (C<EV_USE_EPOLL> must also be enabled). Due to it's |
|
|
4700 | current limitations it has to be requested explicitly. If undefined, it |
|
|
4701 | will be enabled on linux, otherwise disabled. |
4583 | |
4702 | |
4584 | =item EV_USE_KQUEUE |
4703 | =item EV_USE_KQUEUE |
4585 | |
4704 | |
4586 | If defined to be C<1>, libev will compile in support for the BSD style |
4705 | If defined to be C<1>, libev will compile in support for the BSD style |
4587 | C<kqueue>(2) backend. Its actual availability will be detected at runtime, |
4706 | C<kqueue>(2) backend. Its actual availability will be detected at runtime, |
… | |
… | |
4865 | called. If set to C<2>, then the internal verification code will be |
4984 | called. If set to C<2>, then the internal verification code will be |
4866 | called once per loop, which can slow down libev. If set to C<3>, then the |
4985 | called once per loop, which can slow down libev. If set to C<3>, then the |
4867 | verification code will be called very frequently, which will slow down |
4986 | verification code will be called very frequently, which will slow down |
4868 | libev considerably. |
4987 | libev considerably. |
4869 | |
4988 | |
|
|
4989 | Verification errors are reported via C's C<assert> mechanism, so if you |
|
|
4990 | disable that (e.g. by defining C<NDEBUG>) then no errors will be reported. |
|
|
4991 | |
4870 | The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it |
4992 | The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it |
4871 | will be C<0>. |
4993 | will be C<0>. |
4872 | |
4994 | |
4873 | =item EV_COMMON |
4995 | =item EV_COMMON |
4874 | |
4996 | |
… | |
… | |
5290 | structure (guaranteed by POSIX but not by ISO C for example), but it also |
5412 | structure (guaranteed by POSIX but not by ISO C for example), but it also |
5291 | assumes that the same (machine) code can be used to call any watcher |
5413 | assumes that the same (machine) code can be used to call any watcher |
5292 | callback: The watcher callbacks have different type signatures, but libev |
5414 | callback: The watcher callbacks have different type signatures, but libev |
5293 | calls them using an C<ev_watcher *> internally. |
5415 | calls them using an C<ev_watcher *> internally. |
5294 | |
5416 | |
|
|
5417 | =item null pointers and integer zero are represented by 0 bytes |
|
|
5418 | |
|
|
5419 | Libev uses C<memset> to initialise structs and arrays to C<0> bytes, and |
|
|
5420 | relies on this setting pointers and integers to null. |
|
|
5421 | |
5295 | =item pointer accesses must be thread-atomic |
5422 | =item pointer accesses must be thread-atomic |
5296 | |
5423 | |
5297 | Accessing a pointer value must be atomic, it must both be readable and |
5424 | Accessing a pointer value must be atomic, it must both be readable and |
5298 | writable in one piece - this is the case on all current architectures. |
5425 | writable in one piece - this is the case on all current architectures. |
5299 | |
5426 | |
… | |
… | |
5427 | =over 4 |
5554 | =over 4 |
5428 | |
5555 | |
5429 | =item C<EV_COMPAT3> backwards compatibility mechanism |
5556 | =item C<EV_COMPAT3> backwards compatibility mechanism |
5430 | |
5557 | |
5431 | The backward compatibility mechanism can be controlled by |
5558 | The backward compatibility mechanism can be controlled by |
5432 | C<EV_COMPAT3>. See L</PREPROCESSOR SYMBOLS/MACROS> in the L</EMBEDDING> |
5559 | C<EV_COMPAT3>. See L</"PREPROCESSOR SYMBOLS/MACROS"> in the L</EMBEDDING> |
5433 | section. |
5560 | section. |
5434 | |
5561 | |
5435 | =item C<ev_default_destroy> and C<ev_default_fork> have been removed |
5562 | =item C<ev_default_destroy> and C<ev_default_fork> have been removed |
5436 | |
5563 | |
5437 | These calls can be replaced easily by their C<ev_loop_xxx> counterparts: |
5564 | These calls can be replaced easily by their C<ev_loop_xxx> counterparts: |