… | |
… | |
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 |
… | |
… | |
159 | 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 |
160 | 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, |
161 | 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 |
162 | the libev caller and need to be fixed there. |
162 | the libev caller and need to be fixed there. |
163 | |
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 | |
164 | 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 |
165 | extensive consistency checking code. These do not trigger under normal |
|
|
166 | 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. |
167 | |
171 | |
168 | |
172 | |
169 | =head1 GLOBAL FUNCTIONS |
173 | =head1 GLOBAL FUNCTIONS |
170 | |
174 | |
171 | These functions can be called anytime, even before initialising the |
175 | These functions can be called anytime, even before initialising the |
… | |
… | |
265 | |
269 | |
266 | You could override this function in high-availability programs to, say, |
270 | 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, |
271 | 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. |
272 | or even to sleep a while and retry until some memory is available. |
269 | |
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 | |
270 | 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 |
271 | retries (example requires a standards-compliant C<realloc>). |
289 | retries. |
272 | |
290 | |
273 | static void * |
291 | static void * |
274 | persistent_realloc (void *ptr, size_t size) |
292 | persistent_realloc (void *ptr, size_t size) |
275 | { |
293 | { |
|
|
294 | if (!size) |
|
|
295 | { |
|
|
296 | free (ptr); |
|
|
297 | return 0; |
|
|
298 | } |
|
|
299 | |
276 | for (;;) |
300 | for (;;) |
277 | { |
301 | { |
278 | void *newptr = realloc (ptr, size); |
302 | void *newptr = realloc (ptr, size); |
279 | |
303 | |
280 | if (newptr) |
304 | if (newptr) |
… | |
… | |
411 | 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. |
412 | |
436 | |
413 | 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, |
414 | 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 |
415 | 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 |
416 | 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 |
417 | 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 |
418 | 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). |
419 | |
444 | |
420 | 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 |
421 | forget about forgetting to tell libev about forking) when you use this |
446 | forget about forgetting to tell libev about forking, although you still |
422 | flag. |
447 | have to ignore C<SIGPIPE>) when you use this flag. |
423 | |
448 | |
424 | 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> |
425 | environment variable. |
450 | environment variable. |
426 | |
451 | |
427 | =item C<EVFLAG_NOINOTIFY> |
452 | =item C<EVFLAG_NOINOTIFY> |
… | |
… | |
455 | unblocking the signals. |
480 | unblocking the signals. |
456 | |
481 | |
457 | It's also required by POSIX in a threaded program, as libev calls |
482 | It's also required by POSIX in a threaded program, as libev calls |
458 | C<sigprocmask>, whose behaviour is officially unspecified. |
483 | C<sigprocmask>, whose behaviour is officially unspecified. |
459 | |
484 | |
460 | This flag's behaviour will become the default in future versions of libev. |
485 | =item C<EVFLAG_NOTIMERFD> |
|
|
486 | |
|
|
487 | When this flag is specified, the libev will avoid using a C<timerfd> to |
|
|
488 | detect time jumps. It will still be able to detect time jumps, but takes |
|
|
489 | longer and has a lower accuracy in doing so, but saves a file descriptor |
|
|
490 | per loop. |
|
|
491 | |
|
|
492 | The current implementation only tries to use a C<timerfd> when the first |
|
|
493 | C<ev_periodic> watcher is started and falls back on other methods if it |
|
|
494 | cannot be created, but this behaviour might change in the future. |
461 | |
495 | |
462 | =item C<EVBACKEND_SELECT> (value 1, portable select backend) |
496 | =item C<EVBACKEND_SELECT> (value 1, portable select backend) |
463 | |
497 | |
464 | This is your standard select(2) backend. Not I<completely> standard, as |
498 | This is your standard select(2) backend. Not I<completely> standard, as |
465 | libev tries to roll its own fd_set with no limits on the number of fds, |
499 | libev tries to roll its own fd_set with no limits on the number of fds, |
… | |
… | |
490 | This backend maps C<EV_READ> to C<POLLIN | POLLERR | POLLHUP>, and |
524 | This backend maps C<EV_READ> to C<POLLIN | POLLERR | POLLHUP>, and |
491 | C<EV_WRITE> to C<POLLOUT | POLLERR | POLLHUP>. |
525 | C<EV_WRITE> to C<POLLOUT | POLLERR | POLLHUP>. |
492 | |
526 | |
493 | =item C<EVBACKEND_EPOLL> (value 4, Linux) |
527 | =item C<EVBACKEND_EPOLL> (value 4, Linux) |
494 | |
528 | |
495 | Use the linux-specific epoll(7) interface (for both pre- and post-2.6.9 |
529 | Use the Linux-specific epoll(7) interface (for both pre- and post-2.6.9 |
496 | kernels). |
530 | kernels). |
497 | |
531 | |
498 | For few fds, this backend is a bit little slower than poll and select, but |
532 | For few fds, this backend is a bit little slower than poll and select, but |
499 | it scales phenomenally better. While poll and select usually scale like |
533 | it scales phenomenally better. While poll and select usually scale like |
500 | O(total_fds) where total_fds is the total number of fds (or the highest |
534 | O(total_fds) where total_fds is the total number of fds (or the highest |
… | |
… | |
546 | All this means that, in practice, C<EVBACKEND_SELECT> can be as fast or |
580 | 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 |
581 | faster than epoll for maybe up to a hundred file descriptors, depending on |
548 | the usage. So sad. |
582 | the usage. So sad. |
549 | |
583 | |
550 | While nominally embeddable in other event loops, this feature is broken in |
584 | While nominally embeddable in other event loops, this feature is broken in |
551 | all kernel versions tested so far. |
585 | a lot of kernel revisions, but probably(!) works in current versions. |
552 | |
586 | |
553 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
587 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
554 | C<EVBACKEND_POLL>. |
588 | C<EVBACKEND_POLL>. |
555 | |
589 | |
|
|
590 | =item C<EVBACKEND_LINUXAIO> (value 64, Linux) |
|
|
591 | |
|
|
592 | Use the Linux-specific Linux AIO (I<not> C<< aio(7) >> but C<< |
|
|
593 | io_submit(2) >>) event interface available in post-4.18 kernels (but libev |
|
|
594 | only tries to use it in 4.19+). |
|
|
595 | |
|
|
596 | This is another Linux train wreck of an event interface. |
|
|
597 | |
|
|
598 | If this backend works for you (as of this writing, it was very |
|
|
599 | experimental), it is the best event interface available on Linux and might |
|
|
600 | be well worth enabling it - if it isn't available in your kernel this will |
|
|
601 | be detected and this backend will be skipped. |
|
|
602 | |
|
|
603 | This backend can batch oneshot requests and supports a user-space ring |
|
|
604 | buffer to receive events. It also doesn't suffer from most of the design |
|
|
605 | problems of epoll (such as not being able to remove event sources from |
|
|
606 | the epoll set), and generally sounds too good to be true. Because, this |
|
|
607 | being the Linux kernel, of course it suffers from a whole new set of |
|
|
608 | limitations, forcing you to fall back to epoll, inheriting all its design |
|
|
609 | issues. |
|
|
610 | |
|
|
611 | For one, it is not easily embeddable (but probably could be done using |
|
|
612 | an event fd at some extra overhead). It also is subject to a system wide |
|
|
613 | limit that can be configured in F</proc/sys/fs/aio-max-nr>. If no AIO |
|
|
614 | requests are left, this backend will be skipped during initialisation, and |
|
|
615 | will switch to epoll when the loop is active. |
|
|
616 | |
|
|
617 | Most problematic in practice, however, is that not all file descriptors |
|
|
618 | work with it. For example, in Linux 5.1, TCP sockets, pipes, event fds, |
|
|
619 | files, F</dev/null> and many others are supported, but ttys do not work |
|
|
620 | properly (a known bug that the kernel developers don't care about, see |
|
|
621 | L<https://lore.kernel.org/patchwork/patch/1047453/>), so this is not |
|
|
622 | (yet?) a generic event polling interface. |
|
|
623 | |
|
|
624 | Overall, it seems the Linux developers just don't want it to have a |
|
|
625 | generic event handling mechanism other than C<select> or C<poll>. |
|
|
626 | |
|
|
627 | To work around all these problem, the current version of libev uses its |
|
|
628 | epoll backend as a fallback for file descriptor types that do not work. Or |
|
|
629 | falls back completely to epoll if the kernel acts up. |
|
|
630 | |
|
|
631 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
|
|
632 | C<EVBACKEND_POLL>. |
|
|
633 | |
556 | =item C<EVBACKEND_KQUEUE> (value 8, most BSD clones) |
634 | =item C<EVBACKEND_KQUEUE> (value 8, most BSD clones) |
557 | |
635 | |
558 | Kqueue deserves special mention, as at the time of this writing, it |
636 | Kqueue deserves special mention, as at the time this backend was |
559 | was broken on all BSDs except NetBSD (usually it doesn't work reliably |
637 | implemented, it was broken on all BSDs except NetBSD (usually it doesn't |
560 | with anything but sockets and pipes, except on Darwin, where of course |
638 | work reliably with anything but sockets and pipes, except on Darwin, |
561 | it's completely useless). Unlike epoll, however, whose brokenness |
639 | where of course it's completely useless). Unlike epoll, however, whose |
562 | is by design, these kqueue bugs can (and eventually will) be fixed |
640 | brokenness is by design, these kqueue bugs can be (and mostly have been) |
563 | without API changes to existing programs. For this reason it's not being |
641 | fixed without API changes to existing programs. For this reason it's not |
564 | "auto-detected" unless you explicitly specify it in the flags (i.e. using |
642 | being "auto-detected" on all platforms unless you explicitly specify it |
565 | C<EVBACKEND_KQUEUE>) or libev was compiled on a known-to-be-good (-enough) |
643 | in the flags (i.e. using C<EVBACKEND_KQUEUE>) or libev was compiled on a |
566 | system like NetBSD. |
644 | known-to-be-good (-enough) system like NetBSD. |
567 | |
645 | |
568 | You still can embed kqueue into a normal poll or select backend and use it |
646 | You still can embed kqueue into a normal poll or select backend and use it |
569 | only for sockets (after having made sure that sockets work with kqueue on |
647 | only for sockets (after having made sure that sockets work with kqueue on |
570 | the target platform). See C<ev_embed> watchers for more info. |
648 | the target platform). See C<ev_embed> watchers for more info. |
571 | |
649 | |
572 | It scales in the same way as the epoll backend, but the interface to the |
650 | It scales in the same way as the epoll backend, but the interface to the |
573 | kernel is more efficient (which says nothing about its actual speed, of |
651 | kernel is more efficient (which says nothing about its actual speed, of |
574 | course). While stopping, setting and starting an I/O watcher does never |
652 | course). While stopping, setting and starting an I/O watcher does never |
575 | cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to |
653 | cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to |
576 | two event changes per incident. Support for C<fork ()> is very bad (you |
654 | two event changes per incident. Support for C<fork ()> is very bad (you |
577 | might have to leak fd's on fork, but it's more sane than epoll) and it |
655 | might have to leak fds on fork, but it's more sane than epoll) and it |
578 | drops fds silently in similarly hard-to-detect cases. |
656 | drops fds silently in similarly hard-to-detect cases. |
579 | |
657 | |
580 | This backend usually performs well under most conditions. |
658 | This backend usually performs well under most conditions. |
581 | |
659 | |
582 | While nominally embeddable in other event loops, this doesn't work |
660 | While nominally embeddable in other event loops, this doesn't work |
… | |
… | |
657 | Example: Use whatever libev has to offer, but make sure that kqueue is |
735 | Example: Use whatever libev has to offer, but make sure that kqueue is |
658 | used if available. |
736 | used if available. |
659 | |
737 | |
660 | struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_KQUEUE); |
738 | struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_KQUEUE); |
661 | |
739 | |
|
|
740 | Example: Similarly, on linux, you mgiht want to take advantage of the |
|
|
741 | linux aio backend if possible, but fall back to something else if that |
|
|
742 | isn't available. |
|
|
743 | |
|
|
744 | struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_LINUXAIO); |
|
|
745 | |
662 | =item ev_loop_destroy (loop) |
746 | =item ev_loop_destroy (loop) |
663 | |
747 | |
664 | Destroys an event loop object (frees all memory and kernel state |
748 | 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 |
749 | 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 |
750 | sense, so e.g. C<ev_is_active> might still return true. It is your |
… | |
… | |
682 | If you need dynamically allocated loops it is better to use C<ev_loop_new> |
766 | If you need dynamically allocated loops it is better to use C<ev_loop_new> |
683 | and C<ev_loop_destroy>. |
767 | and C<ev_loop_destroy>. |
684 | |
768 | |
685 | =item ev_loop_fork (loop) |
769 | =item ev_loop_fork (loop) |
686 | |
770 | |
687 | This function sets a flag that causes subsequent C<ev_run> iterations to |
771 | This function sets a flag that causes subsequent C<ev_run> iterations |
688 | reinitialise the kernel state for backends that have one. Despite the |
772 | to reinitialise the kernel state for backends that have one. Despite |
689 | name, you can call it anytime, but it makes most sense after forking, in |
773 | the name, you can call it anytime you are allowed to start or stop |
690 | the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the |
774 | watchers (except inside an C<ev_prepare> callback), but it makes most |
|
|
775 | sense after forking, in the child process. You I<must> call it (or use |
691 | child before resuming or calling C<ev_run>. |
776 | C<EVFLAG_FORKCHECK>) in the child before resuming or calling C<ev_run>. |
|
|
777 | |
|
|
778 | In addition, if you want to reuse a loop (via this function or |
|
|
779 | C<EVFLAG_FORKCHECK>), you I<also> have to ignore C<SIGPIPE>. |
692 | |
780 | |
693 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
781 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
694 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
782 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
695 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
783 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
696 | during fork. |
784 | during fork. |
… | |
… | |
1130 | with a watcher-specific start function (C<< ev_TYPE_start (loop, watcher |
1218 | with a watcher-specific start function (C<< ev_TYPE_start (loop, watcher |
1131 | *) >>), and you can stop watching for events at any time by calling the |
1219 | *) >>), and you can stop watching for events at any time by calling the |
1132 | corresponding stop function (C<< ev_TYPE_stop (loop, watcher *) >>. |
1220 | corresponding stop function (C<< ev_TYPE_stop (loop, watcher *) >>. |
1133 | |
1221 | |
1134 | As long as your watcher is active (has been started but not stopped) you |
1222 | As long as your watcher is active (has been started but not stopped) you |
1135 | must not touch the values stored in it. Most specifically you must never |
1223 | must not touch the values stored in it except when explicitly documented |
1136 | reinitialise it or call its C<ev_TYPE_set> macro. |
1224 | otherwise. Most specifically you must never reinitialise it or call its |
|
|
1225 | C<ev_TYPE_set> macro. |
1137 | |
1226 | |
1138 | Each and every callback receives the event loop pointer as first, the |
1227 | Each and every callback receives the event loop pointer as first, the |
1139 | registered watcher structure as second, and a bitset of received events as |
1228 | registered watcher structure as second, and a bitset of received events as |
1140 | third argument. |
1229 | third argument. |
1141 | |
1230 | |
… | |
… | |
1456 | |
1545 | |
1457 | Many event loops support I<watcher priorities>, which are usually small |
1546 | Many event loops support I<watcher priorities>, which are usually small |
1458 | integers that influence the ordering of event callback invocation |
1547 | integers that influence the ordering of event callback invocation |
1459 | between watchers in some way, all else being equal. |
1548 | between watchers in some way, all else being equal. |
1460 | |
1549 | |
1461 | In libev, Watcher priorities can be set using C<ev_set_priority>. See its |
1550 | In libev, watcher priorities can be set using C<ev_set_priority>. See its |
1462 | description for the more technical details such as the actual priority |
1551 | description for the more technical details such as the actual priority |
1463 | range. |
1552 | range. |
1464 | |
1553 | |
1465 | There are two common ways how these these priorities are being interpreted |
1554 | There are two common ways how these these priorities are being interpreted |
1466 | by event loops: |
1555 | by event loops: |
… | |
… | |
1560 | |
1649 | |
1561 | This section describes each watcher in detail, but will not repeat |
1650 | This section describes each watcher in detail, but will not repeat |
1562 | information given in the last section. Any initialisation/set macros, |
1651 | information given in the last section. Any initialisation/set macros, |
1563 | functions and members specific to the watcher type are explained. |
1652 | functions and members specific to the watcher type are explained. |
1564 | |
1653 | |
1565 | Members are additionally marked with either I<[read-only]>, meaning that, |
1654 | Most members are additionally marked with either I<[read-only]>, meaning |
1566 | while the watcher is active, you can look at the member and expect some |
1655 | that, while the watcher is active, you can look at the member and expect |
1567 | sensible content, but you must not modify it (you can modify it while the |
1656 | some sensible content, but you must not modify it (you can modify it while |
1568 | watcher is stopped to your hearts content), or I<[read-write]>, which |
1657 | the watcher is stopped to your hearts content), or I<[read-write]>, which |
1569 | means you can expect it to have some sensible content while the watcher |
1658 | means you can expect it to have some sensible content while the watcher |
1570 | is active, but you can also modify it. Modifying it may not do something |
1659 | is active, but you can also modify it. Modifying it may not do something |
1571 | sensible or take immediate effect (or do anything at all), but libev will |
1660 | sensible or take immediate effect (or do anything at all), but libev will |
1572 | not crash or malfunction in any way. |
1661 | not crash or malfunction in any way. |
1573 | |
1662 | |
|
|
1663 | In any case, the documentation for each member will explain what the |
|
|
1664 | effects are, and if there are any additional access restrictions. |
1574 | |
1665 | |
1575 | =head2 C<ev_io> - is this file descriptor readable or writable? |
1666 | =head2 C<ev_io> - is this file descriptor readable or writable? |
1576 | |
1667 | |
1577 | I/O watchers check whether a file descriptor is readable or writable |
1668 | I/O watchers check whether a file descriptor is readable or writable |
1578 | in each iteration of the event loop, or, more precisely, when reading |
1669 | in each iteration of the event loop, or, more precisely, when reading |
… | |
… | |
1605 | |
1696 | |
1606 | But really, best use non-blocking mode. |
1697 | But really, best use non-blocking mode. |
1607 | |
1698 | |
1608 | =head3 The special problem of disappearing file descriptors |
1699 | =head3 The special problem of disappearing file descriptors |
1609 | |
1700 | |
1610 | Some backends (e.g. kqueue, epoll) need to be told about closing a file |
1701 | Some backends (e.g. kqueue, epoll, linuxaio) need to be told about closing |
1611 | descriptor (either due to calling C<close> explicitly or any other means, |
1702 | a file descriptor (either due to calling C<close> explicitly or any other |
1612 | such as C<dup2>). The reason is that you register interest in some file |
1703 | means, such as C<dup2>). The reason is that you register interest in some |
1613 | descriptor, but when it goes away, the operating system will silently drop |
1704 | file descriptor, but when it goes away, the operating system will silently |
1614 | this interest. If another file descriptor with the same number then is |
1705 | drop this interest. If another file descriptor with the same number then |
1615 | registered with libev, there is no efficient way to see that this is, in |
1706 | is registered with libev, there is no efficient way to see that this is, |
1616 | fact, a different file descriptor. |
1707 | in fact, a different file descriptor. |
1617 | |
1708 | |
1618 | To avoid having to explicitly tell libev about such cases, libev follows |
1709 | To avoid having to explicitly tell libev about such cases, libev follows |
1619 | the following policy: Each time C<ev_io_set> is being called, libev |
1710 | the following policy: Each time C<ev_io_set> is being called, libev |
1620 | will assume that this is potentially a new file descriptor, otherwise |
1711 | will assume that this is potentially a new file descriptor, otherwise |
1621 | it is assumed that the file descriptor stays the same. That means that |
1712 | it is assumed that the file descriptor stays the same. That means that |
… | |
… | |
1670 | when you rarely read from a file instead of from a socket, and want to |
1761 | when you rarely read from a file instead of from a socket, and want to |
1671 | reuse the same code path. |
1762 | reuse the same code path. |
1672 | |
1763 | |
1673 | =head3 The special problem of fork |
1764 | =head3 The special problem of fork |
1674 | |
1765 | |
1675 | Some backends (epoll, kqueue) do not support C<fork ()> at all or exhibit |
1766 | Some backends (epoll, kqueue, linuxaio, iouring) do not support C<fork ()> |
1676 | useless behaviour. Libev fully supports fork, but needs to be told about |
1767 | at all or exhibit useless behaviour. Libev fully supports fork, but needs |
1677 | it in the child if you want to continue to use it in the child. |
1768 | to be told about it in the child if you want to continue to use it in the |
|
|
1769 | child. |
1678 | |
1770 | |
1679 | To support fork in your child processes, you have to call C<ev_loop_fork |
1771 | To support fork in your child processes, you have to call C<ev_loop_fork |
1680 | ()> after a fork in the child, enable C<EVFLAG_FORKCHECK>, or resort to |
1772 | ()> after a fork in the child, enable C<EVFLAG_FORKCHECK>, or resort to |
1681 | C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>. |
1773 | C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>. |
1682 | |
1774 | |
… | |
… | |
1740 | |
1832 | |
1741 | Configures an C<ev_io> watcher. The C<fd> is the file descriptor to |
1833 | Configures an C<ev_io> watcher. The C<fd> is the file descriptor to |
1742 | receive events for and C<events> is either C<EV_READ>, C<EV_WRITE> or |
1834 | receive events for and C<events> is either C<EV_READ>, C<EV_WRITE> or |
1743 | C<EV_READ | EV_WRITE>, to express the desire to receive the given events. |
1835 | C<EV_READ | EV_WRITE>, to express the desire to receive the given events. |
1744 | |
1836 | |
1745 | =item int fd [read-only] |
1837 | =item ev_io_modify (ev_io *, int events) |
1746 | |
1838 | |
1747 | The file descriptor being watched. |
1839 | Similar to C<ev_io_set>, but only changes the event mask. Using this might |
|
|
1840 | be faster with some backends, as libev can assume that the C<fd> still |
|
|
1841 | refers to the same underlying file description, something it cannot do |
|
|
1842 | when using C<ev_io_set>. |
1748 | |
1843 | |
|
|
1844 | =item int fd [no-modify] |
|
|
1845 | |
|
|
1846 | The file descriptor being watched. While it can be read at any time, you |
|
|
1847 | must not modify this member even when the watcher is stopped - always use |
|
|
1848 | C<ev_io_set> for that. |
|
|
1849 | |
1749 | =item int events [read-only] |
1850 | =item int events [no-modify] |
1750 | |
1851 | |
1751 | The events being watched. |
1852 | The set of events the fd is being watched for, among other flags. Remember |
|
|
1853 | that this is a bit set - to test for C<EV_READ>, use C<< w->events & |
|
|
1854 | EV_READ >>, and similarly for C<EV_WRITE>. |
|
|
1855 | |
|
|
1856 | As with C<fd>, you must not modify this member even when the watcher is |
|
|
1857 | stopped, always use C<ev_io_set> or C<ev_io_modify> for that. |
1752 | |
1858 | |
1753 | =back |
1859 | =back |
1754 | |
1860 | |
1755 | =head3 Examples |
1861 | =head3 Examples |
1756 | |
1862 | |
… | |
… | |
2028 | |
2134 | |
2029 | The relative timeouts are calculated relative to the C<ev_now ()> |
2135 | The relative timeouts are calculated relative to the C<ev_now ()> |
2030 | time. This is usually the right thing as this timestamp refers to the time |
2136 | time. This is usually the right thing as this timestamp refers to the time |
2031 | of the event triggering whatever timeout you are modifying/starting. If |
2137 | of the event triggering whatever timeout you are modifying/starting. If |
2032 | you suspect event processing to be delayed and you I<need> to base the |
2138 | you suspect event processing to be delayed and you I<need> to base the |
2033 | timeout on the current time, use something like this to adjust for this: |
2139 | timeout on the current time, use something like the following to adjust |
|
|
2140 | for it: |
2034 | |
2141 | |
2035 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
2142 | ev_timer_set (&timer, after + (ev_time () - ev_now ()), 0.); |
2036 | |
2143 | |
2037 | If the event loop is suspended for a long time, you can also force an |
2144 | If the event loop is suspended for a long time, you can also force an |
2038 | update of the time returned by C<ev_now ()> by calling C<ev_now_update |
2145 | update of the time returned by C<ev_now ()> by calling C<ev_now_update |
2039 | ()>. |
2146 | ()>, although that will push the event time of all outstanding events |
|
|
2147 | further into the future. |
2040 | |
2148 | |
2041 | =head3 The special problem of unsynchronised clocks |
2149 | =head3 The special problem of unsynchronised clocks |
2042 | |
2150 | |
2043 | Modern systems have a variety of clocks - libev itself uses the normal |
2151 | Modern systems have a variety of clocks - libev itself uses the normal |
2044 | "wall clock" clock and, if available, the monotonic clock (to avoid time |
2152 | "wall clock" clock and, if available, the monotonic clock (to avoid time |
… | |
… | |
2107 | |
2215 | |
2108 | =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat) |
2216 | =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat) |
2109 | |
2217 | |
2110 | =item ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat) |
2218 | =item ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat) |
2111 | |
2219 | |
2112 | Configure the timer to trigger after C<after> seconds. If C<repeat> |
2220 | Configure the timer to trigger after C<after> seconds (fractional and |
2113 | is C<0.>, then it will automatically be stopped once the timeout is |
2221 | negative values are supported). If C<repeat> is C<0.>, then it will |
2114 | reached. If it is positive, then the timer will automatically be |
2222 | automatically be stopped once the timeout is reached. If it is positive, |
2115 | configured to trigger again C<repeat> seconds later, again, and again, |
2223 | then the timer will automatically be configured to trigger again C<repeat> |
2116 | until stopped manually. |
2224 | seconds later, again, and again, until stopped manually. |
2117 | |
2225 | |
2118 | The timer itself will do a best-effort at avoiding drift, that is, if |
2226 | The timer itself will do a best-effort at avoiding drift, that is, if |
2119 | you configure a timer to trigger every 10 seconds, then it will normally |
2227 | you configure a timer to trigger every 10 seconds, then it will normally |
2120 | trigger at exactly 10 second intervals. If, however, your program cannot |
2228 | trigger at exactly 10 second intervals. If, however, your program cannot |
2121 | keep up with the timer (because it takes longer than those 10 seconds to |
2229 | keep up with the timer (because it takes longer than those 10 seconds to |
… | |
… | |
2203 | Periodic watchers are also timers of a kind, but they are very versatile |
2311 | Periodic watchers are also timers of a kind, but they are very versatile |
2204 | (and unfortunately a bit complex). |
2312 | (and unfortunately a bit complex). |
2205 | |
2313 | |
2206 | Unlike C<ev_timer>, periodic watchers are not based on real time (or |
2314 | Unlike C<ev_timer>, periodic watchers are not based on real time (or |
2207 | relative time, the physical time that passes) but on wall clock time |
2315 | relative time, the physical time that passes) but on wall clock time |
2208 | (absolute time, the thing you can read on your calender or clock). The |
2316 | (absolute time, the thing you can read on your calendar or clock). The |
2209 | difference is that wall clock time can run faster or slower than real |
2317 | difference is that wall clock time can run faster or slower than real |
2210 | time, and time jumps are not uncommon (e.g. when you adjust your |
2318 | time, and time jumps are not uncommon (e.g. when you adjust your |
2211 | wrist-watch). |
2319 | wrist-watch). |
2212 | |
2320 | |
2213 | You can tell a periodic watcher to trigger after some specific point |
2321 | You can tell a periodic watcher to trigger after some specific point |
… | |
… | |
2218 | C<ev_timer>, which would still trigger roughly 10 seconds after starting |
2326 | C<ev_timer>, which would still trigger roughly 10 seconds after starting |
2219 | it, as it uses a relative timeout). |
2327 | it, as it uses a relative timeout). |
2220 | |
2328 | |
2221 | C<ev_periodic> watchers can also be used to implement vastly more complex |
2329 | C<ev_periodic> watchers can also be used to implement vastly more complex |
2222 | timers, such as triggering an event on each "midnight, local time", or |
2330 | timers, such as triggering an event on each "midnight, local time", or |
2223 | other complicated rules. This cannot be done with C<ev_timer> watchers, as |
2331 | other complicated rules. This cannot easily be done with C<ev_timer> |
2224 | those cannot react to time jumps. |
2332 | watchers, as those cannot react to time jumps. |
2225 | |
2333 | |
2226 | As with timers, the callback is guaranteed to be invoked only when the |
2334 | As with timers, the callback is guaranteed to be invoked only when the |
2227 | point in time where it is supposed to trigger has passed. If multiple |
2335 | point in time where it is supposed to trigger has passed. If multiple |
2228 | timers become ready during the same loop iteration then the ones with |
2336 | timers become ready during the same loop iteration then the ones with |
2229 | earlier time-out values are invoked before ones with later time-out values |
2337 | earlier time-out values are invoked before ones with later time-out values |
… | |
… | |
2315 | |
2423 | |
2316 | NOTE: I<< This callback must always return a time that is higher than or |
2424 | NOTE: I<< This callback must always return a time that is higher than or |
2317 | equal to the passed C<now> value >>. |
2425 | equal to the passed C<now> value >>. |
2318 | |
2426 | |
2319 | This can be used to create very complex timers, such as a timer that |
2427 | This can be used to create very complex timers, such as a timer that |
2320 | triggers on "next midnight, local time". To do this, you would calculate the |
2428 | triggers on "next midnight, local time". To do this, you would calculate |
2321 | next midnight after C<now> and return the timestamp value for this. How |
2429 | the next midnight after C<now> and return the timestamp value for |
2322 | you do this is, again, up to you (but it is not trivial, which is the main |
2430 | this. Here is a (completely untested, no error checking) example on how to |
2323 | reason I omitted it as an example). |
2431 | do this: |
|
|
2432 | |
|
|
2433 | #include <time.h> |
|
|
2434 | |
|
|
2435 | static ev_tstamp |
|
|
2436 | my_rescheduler (ev_periodic *w, ev_tstamp now) |
|
|
2437 | { |
|
|
2438 | time_t tnow = (time_t)now; |
|
|
2439 | struct tm tm; |
|
|
2440 | localtime_r (&tnow, &tm); |
|
|
2441 | |
|
|
2442 | tm.tm_sec = tm.tm_min = tm.tm_hour = 0; // midnight current day |
|
|
2443 | ++tm.tm_mday; // midnight next day |
|
|
2444 | |
|
|
2445 | return mktime (&tm); |
|
|
2446 | } |
|
|
2447 | |
|
|
2448 | Note: this code might run into trouble on days that have more then two |
|
|
2449 | midnights (beginning and end). |
2324 | |
2450 | |
2325 | =back |
2451 | =back |
2326 | |
2452 | |
2327 | =item ev_periodic_again (loop, ev_periodic *) |
2453 | =item ev_periodic_again (loop, ev_periodic *) |
2328 | |
2454 | |
… | |
… | |
2907 | |
3033 | |
2908 | Prepare and check watchers are often (but not always) used in pairs: |
3034 | Prepare and check watchers are often (but not always) used in pairs: |
2909 | prepare watchers get invoked before the process blocks and check watchers |
3035 | prepare watchers get invoked before the process blocks and check watchers |
2910 | afterwards. |
3036 | afterwards. |
2911 | |
3037 | |
2912 | You I<must not> call C<ev_run> or similar functions that enter |
3038 | You I<must not> call C<ev_run> (or similar functions that enter the |
2913 | the current event loop from either C<ev_prepare> or C<ev_check> |
3039 | current event loop) or C<ev_loop_fork> from either C<ev_prepare> or |
2914 | watchers. Other loops than the current one are fine, however. The |
3040 | C<ev_check> watchers. Other loops than the current one are fine, |
2915 | rationale behind this is that you do not need to check for recursion in |
3041 | however. The rationale behind this is that you do not need to check |
2916 | those watchers, i.e. the sequence will always be C<ev_prepare>, blocking, |
3042 | for recursion in those watchers, i.e. the sequence will always be |
2917 | C<ev_check> so if you have one watcher of each kind they will always be |
3043 | C<ev_prepare>, blocking, C<ev_check> so if you have one watcher of each |
2918 | called in pairs bracketing the blocking call. |
3044 | kind they will always be called in pairs bracketing the blocking call. |
2919 | |
3045 | |
2920 | Their main purpose is to integrate other event mechanisms into libev and |
3046 | Their main purpose is to integrate other event mechanisms into libev and |
2921 | their use is somewhat advanced. They could be used, for example, to track |
3047 | their use is somewhat advanced. They could be used, for example, to track |
2922 | variable changes, implement your own watchers, integrate net-snmp or a |
3048 | variable changes, implement your own watchers, integrate net-snmp or a |
2923 | coroutine library and lots more. They are also occasionally useful if |
3049 | coroutine library and lots more. They are also occasionally useful if |
… | |
… | |
3263 | and calls it in the wrong process, the fork handlers will be invoked, too, |
3389 | and calls it in the wrong process, the fork handlers will be invoked, too, |
3264 | of course. |
3390 | of course. |
3265 | |
3391 | |
3266 | =head3 The special problem of life after fork - how is it possible? |
3392 | =head3 The special problem of life after fork - how is it possible? |
3267 | |
3393 | |
3268 | Most uses of C<fork()> consist of forking, then some simple calls to set |
3394 | Most uses of C<fork ()> consist of forking, then some simple calls to set |
3269 | up/change the process environment, followed by a call to C<exec()>. This |
3395 | up/change the process environment, followed by a call to C<exec()>. This |
3270 | sequence should be handled by libev without any problems. |
3396 | sequence should be handled by libev without any problems. |
3271 | |
3397 | |
3272 | This changes when the application actually wants to do event handling |
3398 | This changes when the application actually wants to do event handling |
3273 | in the child, or both parent in child, in effect "continuing" after the |
3399 | in the child, or both parent in child, in effect "continuing" after the |
… | |
… | |
3511 | |
3637 | |
3512 | There are some other functions of possible interest. Described. Here. Now. |
3638 | There are some other functions of possible interest. Described. Here. Now. |
3513 | |
3639 | |
3514 | =over 4 |
3640 | =over 4 |
3515 | |
3641 | |
3516 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
3642 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback, arg) |
3517 | |
3643 | |
3518 | This function combines a simple timer and an I/O watcher, calls your |
3644 | This function combines a simple timer and an I/O watcher, calls your |
3519 | callback on whichever event happens first and automatically stops both |
3645 | callback on whichever event happens first and automatically stops both |
3520 | watchers. This is useful if you want to wait for a single event on an fd |
3646 | watchers. This is useful if you want to wait for a single event on an fd |
3521 | or timeout without having to allocate/configure/start/stop/free one or |
3647 | or timeout without having to allocate/configure/start/stop/free one or |
… | |
… | |
3897 | To embed libev, see L</EMBEDDING>, but in short, it's easiest to create two |
4023 | To embed libev, see L</EMBEDDING>, but in short, it's easiest to create two |
3898 | files, F<my_ev.h> and F<my_ev.c> that include the respective libev files: |
4024 | files, F<my_ev.h> and F<my_ev.c> that include the respective libev files: |
3899 | |
4025 | |
3900 | // my_ev.h |
4026 | // my_ev.h |
3901 | #define EV_CB_DECLARE(type) struct my_coro *cb; |
4027 | #define EV_CB_DECLARE(type) struct my_coro *cb; |
3902 | #define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb); |
4028 | #define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb) |
3903 | #include "../libev/ev.h" |
4029 | #include "../libev/ev.h" |
3904 | |
4030 | |
3905 | // my_ev.c |
4031 | // my_ev.c |
3906 | #define EV_H "my_ev.h" |
4032 | #define EV_H "my_ev.h" |
3907 | #include "../libev/ev.c" |
4033 | #include "../libev/ev.c" |
… | |
… | |
3953 | The normal C API should work fine when used from C++: both ev.h and the |
4079 | The normal C API should work fine when used from C++: both ev.h and the |
3954 | libev sources can be compiled as C++. Therefore, code that uses the C API |
4080 | libev sources can be compiled as C++. Therefore, code that uses the C API |
3955 | will work fine. |
4081 | will work fine. |
3956 | |
4082 | |
3957 | Proper exception specifications might have to be added to callbacks passed |
4083 | Proper exception specifications might have to be added to callbacks passed |
3958 | to libev: exceptions may be thrown only from watcher callbacks, all |
4084 | to libev: exceptions may be thrown only from watcher callbacks, all other |
3959 | other callbacks (allocator, syserr, loop acquire/release and periodic |
4085 | callbacks (allocator, syserr, loop acquire/release and periodic reschedule |
3960 | reschedule callbacks) must not throw exceptions, and might need a C<throw |
4086 | callbacks) must not throw exceptions, and might need a C<noexcept> |
3961 | ()> specification. If you have code that needs to be compiled as both C |
4087 | specification. If you have code that needs to be compiled as both C and |
3962 | and C++ you can use the C<EV_THROW> macro for this: |
4088 | C++ you can use the C<EV_NOEXCEPT> macro for this: |
3963 | |
4089 | |
3964 | static void |
4090 | static void |
3965 | fatal_error (const char *msg) EV_THROW |
4091 | fatal_error (const char *msg) EV_NOEXCEPT |
3966 | { |
4092 | { |
3967 | perror (msg); |
4093 | perror (msg); |
3968 | abort (); |
4094 | abort (); |
3969 | } |
4095 | } |
3970 | |
4096 | |
… | |
… | |
4380 | ev_vars.h |
4506 | ev_vars.h |
4381 | ev_wrap.h |
4507 | ev_wrap.h |
4382 | |
4508 | |
4383 | ev_win32.c required on win32 platforms only |
4509 | ev_win32.c required on win32 platforms only |
4384 | |
4510 | |
4385 | ev_select.c only when select backend is enabled (which is enabled by default) |
4511 | ev_select.c only when select backend is enabled |
4386 | ev_poll.c only when poll backend is enabled (disabled by default) |
4512 | ev_poll.c only when poll backend is enabled |
4387 | ev_epoll.c only when the epoll backend is enabled (disabled by default) |
4513 | ev_epoll.c only when the epoll backend is enabled |
|
|
4514 | ev_linuxaio.c only when the linux aio backend is enabled |
|
|
4515 | ev_iouring.c only when the linux io_uring backend is enabled |
4388 | ev_kqueue.c only when the kqueue backend is enabled (disabled by default) |
4516 | ev_kqueue.c only when the kqueue backend is enabled |
4389 | ev_port.c only when the solaris port backend is enabled (disabled by default) |
4517 | ev_port.c only when the solaris port backend is enabled |
4390 | |
4518 | |
4391 | F<ev.c> includes the backend files directly when enabled, so you only need |
4519 | F<ev.c> includes the backend files directly when enabled, so you only need |
4392 | to compile this single file. |
4520 | to compile this single file. |
4393 | |
4521 | |
4394 | =head3 LIBEVENT COMPATIBILITY API |
4522 | =head3 LIBEVENT COMPATIBILITY API |
… | |
… | |
4513 | available and will probe for kernel support at runtime. This will improve |
4641 | available and will probe for kernel support at runtime. This will improve |
4514 | C<ev_signal> and C<ev_async> performance and reduce resource consumption. |
4642 | C<ev_signal> and C<ev_async> performance and reduce resource consumption. |
4515 | If undefined, it will be enabled if the headers indicate GNU/Linux + Glibc |
4643 | If undefined, it will be enabled if the headers indicate GNU/Linux + Glibc |
4516 | 2.7 or newer, otherwise disabled. |
4644 | 2.7 or newer, otherwise disabled. |
4517 | |
4645 | |
|
|
4646 | =item EV_USE_SIGNALFD |
|
|
4647 | |
|
|
4648 | If defined to be C<1>, then libev will assume that C<signalfd ()> is |
|
|
4649 | available and will probe for kernel support at runtime. This enables |
|
|
4650 | the use of EVFLAG_SIGNALFD for faster and simpler signal handling. If |
|
|
4651 | undefined, it will be enabled if the headers indicate GNU/Linux + Glibc |
|
|
4652 | 2.7 or newer, otherwise disabled. |
|
|
4653 | |
|
|
4654 | =item EV_USE_TIMERFD |
|
|
4655 | |
|
|
4656 | If defined to be C<1>, then libev will assume that C<timerfd ()> is |
|
|
4657 | available and will probe for kernel support at runtime. This allows |
|
|
4658 | libev to detect time jumps accurately. If undefined, it will be enabled |
|
|
4659 | if the headers indicate GNU/Linux + Glibc 2.8 or newer and define |
|
|
4660 | C<TFD_TIMER_CANCEL_ON_SET>, otherwise disabled. |
|
|
4661 | |
|
|
4662 | =item EV_USE_EVENTFD |
|
|
4663 | |
|
|
4664 | If defined to be C<1>, then libev will assume that C<eventfd ()> is |
|
|
4665 | available and will probe for kernel support at runtime. This will improve |
|
|
4666 | C<ev_signal> and C<ev_async> performance and reduce resource consumption. |
|
|
4667 | If undefined, it will be enabled if the headers indicate GNU/Linux + Glibc |
|
|
4668 | 2.7 or newer, otherwise disabled. |
|
|
4669 | |
4518 | =item EV_USE_SELECT |
4670 | =item EV_USE_SELECT |
4519 | |
4671 | |
4520 | If undefined or defined to be C<1>, libev will compile in support for the |
4672 | If undefined or defined to be C<1>, libev will compile in support for the |
4521 | C<select>(2) backend. No attempt at auto-detection will be done: if no |
4673 | C<select>(2) backend. No attempt at auto-detection will be done: if no |
4522 | other method takes over, select will be it. Otherwise the select backend |
4674 | other method takes over, select will be it. Otherwise the select backend |
… | |
… | |
4582 | If defined to be C<1>, libev will compile in support for the Linux |
4734 | If defined to be C<1>, libev will compile in support for the Linux |
4583 | C<epoll>(7) backend. Its availability will be detected at runtime, |
4735 | C<epoll>(7) backend. Its availability will be detected at runtime, |
4584 | otherwise another method will be used as fallback. This is the preferred |
4736 | otherwise another method will be used as fallback. This is the preferred |
4585 | backend for GNU/Linux systems. If undefined, it will be enabled if the |
4737 | backend for GNU/Linux systems. If undefined, it will be enabled if the |
4586 | headers indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
4738 | headers indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
|
|
4739 | |
|
|
4740 | =item EV_USE_LINUXAIO |
|
|
4741 | |
|
|
4742 | If defined to be C<1>, libev will compile in support for the Linux aio |
|
|
4743 | backend (C<EV_USE_EPOLL> must also be enabled). If undefined, it will be |
|
|
4744 | enabled on linux, otherwise disabled. |
|
|
4745 | |
|
|
4746 | =item EV_USE_IOURING |
|
|
4747 | |
|
|
4748 | If defined to be C<1>, libev will compile in support for the Linux |
|
|
4749 | io_uring backend (C<EV_USE_EPOLL> must also be enabled). Due to it's |
|
|
4750 | current limitations it has to be requested explicitly. If undefined, it |
|
|
4751 | will be enabled on linux, otherwise disabled. |
4587 | |
4752 | |
4588 | =item EV_USE_KQUEUE |
4753 | =item EV_USE_KQUEUE |
4589 | |
4754 | |
4590 | If defined to be C<1>, libev will compile in support for the BSD style |
4755 | If defined to be C<1>, libev will compile in support for the BSD style |
4591 | C<kqueue>(2) backend. Its actual availability will be detected at runtime, |
4756 | C<kqueue>(2) backend. Its actual availability will be detected at runtime, |
… | |
… | |
4869 | called. If set to C<2>, then the internal verification code will be |
5034 | called. If set to C<2>, then the internal verification code will be |
4870 | called once per loop, which can slow down libev. If set to C<3>, then the |
5035 | called once per loop, which can slow down libev. If set to C<3>, then the |
4871 | verification code will be called very frequently, which will slow down |
5036 | verification code will be called very frequently, which will slow down |
4872 | libev considerably. |
5037 | libev considerably. |
4873 | |
5038 | |
|
|
5039 | Verification errors are reported via C's C<assert> mechanism, so if you |
|
|
5040 | disable that (e.g. by defining C<NDEBUG>) then no errors will be reported. |
|
|
5041 | |
4874 | The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it |
5042 | The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it |
4875 | will be C<0>. |
5043 | will be C<0>. |
4876 | |
5044 | |
4877 | =item EV_COMMON |
5045 | =item EV_COMMON |
4878 | |
5046 | |
… | |
… | |
5294 | structure (guaranteed by POSIX but not by ISO C for example), but it also |
5462 | structure (guaranteed by POSIX but not by ISO C for example), but it also |
5295 | assumes that the same (machine) code can be used to call any watcher |
5463 | assumes that the same (machine) code can be used to call any watcher |
5296 | callback: The watcher callbacks have different type signatures, but libev |
5464 | callback: The watcher callbacks have different type signatures, but libev |
5297 | calls them using an C<ev_watcher *> internally. |
5465 | calls them using an C<ev_watcher *> internally. |
5298 | |
5466 | |
|
|
5467 | =item null pointers and integer zero are represented by 0 bytes |
|
|
5468 | |
|
|
5469 | Libev uses C<memset> to initialise structs and arrays to C<0> bytes, and |
|
|
5470 | relies on this setting pointers and integers to null. |
|
|
5471 | |
5299 | =item pointer accesses must be thread-atomic |
5472 | =item pointer accesses must be thread-atomic |
5300 | |
5473 | |
5301 | Accessing a pointer value must be atomic, it must both be readable and |
5474 | Accessing a pointer value must be atomic, it must both be readable and |
5302 | writable in one piece - this is the case on all current architectures. |
5475 | writable in one piece - this is the case on all current architectures. |
5303 | |
5476 | |