|
|
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> |
… | |
… | |
451 | unblocking the signals. |
480 | unblocking the signals. |
452 | |
481 | |
453 | 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 |
454 | C<sigprocmask>, whose behaviour is officially unspecified. |
483 | C<sigprocmask>, whose behaviour is officially unspecified. |
455 | |
484 | |
456 | 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. |
457 | |
495 | |
458 | =item C<EVBACKEND_SELECT> (value 1, portable select backend) |
496 | =item C<EVBACKEND_SELECT> (value 1, portable select backend) |
459 | |
497 | |
460 | 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 |
461 | 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, |
… | |
… | |
486 | 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 |
487 | C<EV_WRITE> to C<POLLOUT | POLLERR | POLLHUP>. |
525 | C<EV_WRITE> to C<POLLOUT | POLLERR | POLLHUP>. |
488 | |
526 | |
489 | =item C<EVBACKEND_EPOLL> (value 4, Linux) |
527 | =item C<EVBACKEND_EPOLL> (value 4, Linux) |
490 | |
528 | |
491 | 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 |
492 | kernels). |
530 | kernels). |
493 | |
531 | |
494 | 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 |
495 | it scales phenomenally better. While poll and select usually scale like |
533 | 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 |
534 | 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 |
580 | 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 |
581 | faster than epoll for maybe up to a hundred file descriptors, depending on |
544 | the usage. So sad. |
582 | the usage. So sad. |
545 | |
583 | |
546 | 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 |
547 | all kernel versions tested so far. |
585 | a lot of kernel revisions, but probably(!) works in current versions. |
548 | |
586 | |
549 | 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 |
550 | C<EVBACKEND_POLL>. |
588 | C<EVBACKEND_POLL>. |
551 | |
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 | |
552 | =item C<EVBACKEND_KQUEUE> (value 8, most BSD clones) |
634 | =item C<EVBACKEND_KQUEUE> (value 8, most BSD clones) |
553 | |
635 | |
554 | Kqueue deserves special mention, as at the time of this writing, it |
636 | 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 |
637 | 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 |
638 | work reliably with anything but sockets and pipes, except on Darwin, |
557 | it's completely useless). Unlike epoll, however, whose brokenness |
639 | where of course it's completely useless). Unlike epoll, however, whose |
558 | 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) |
559 | 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 |
560 | "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 |
561 | 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 |
562 | system like NetBSD. |
644 | known-to-be-good (-enough) system like NetBSD. |
563 | |
645 | |
564 | 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 |
565 | 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 |
566 | the target platform). See C<ev_embed> watchers for more info. |
648 | the target platform). See C<ev_embed> watchers for more info. |
567 | |
649 | |
568 | 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 |
569 | 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 |
570 | 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 |
571 | 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 |
572 | 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 |
573 | 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 |
574 | drops fds silently in similarly hard-to-detect cases. |
656 | drops fds silently in similarly hard-to-detect cases. |
575 | |
657 | |
576 | This backend usually performs well under most conditions. |
658 | This backend usually performs well under most conditions. |
577 | |
659 | |
578 | While nominally embeddable in other event loops, this doesn't work |
660 | While nominally embeddable in other event loops, this doesn't work |
… | |
… | |
593 | and is not embeddable, which would limit the usefulness of this backend |
675 | and is not embeddable, which would limit the usefulness of this backend |
594 | immensely. |
676 | immensely. |
595 | |
677 | |
596 | =item C<EVBACKEND_PORT> (value 32, Solaris 10) |
678 | =item C<EVBACKEND_PORT> (value 32, Solaris 10) |
597 | |
679 | |
598 | This uses the Solaris 10 event port mechanism. As with everything on Solaris, |
680 | This uses the Solaris 10 event port mechanism. As with everything on |
599 | it's really slow, but it still scales very well (O(active_fds)). |
681 | Solaris, it's really slow, but it still scales very well (O(active_fds)). |
600 | |
682 | |
601 | While this backend scales well, it requires one system call per active |
683 | While this backend scales well, it requires one system call per active |
602 | file descriptor per loop iteration. For small and medium numbers of file |
684 | file descriptor per loop iteration. For small and medium numbers of file |
603 | descriptors a "slow" C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> backend |
685 | descriptors a "slow" C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> backend |
604 | might perform better. |
686 | might perform better. |
… | |
… | |
653 | 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 |
654 | used if available. |
736 | used if available. |
655 | |
737 | |
656 | 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); |
657 | |
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 | |
658 | =item ev_loop_destroy (loop) |
746 | =item ev_loop_destroy (loop) |
659 | |
747 | |
660 | Destroys an event loop object (frees all memory and kernel state |
748 | 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 |
749 | 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 |
750 | 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> |
766 | If you need dynamically allocated loops it is better to use C<ev_loop_new> |
679 | and C<ev_loop_destroy>. |
767 | and C<ev_loop_destroy>. |
680 | |
768 | |
681 | =item ev_loop_fork (loop) |
769 | =item ev_loop_fork (loop) |
682 | |
770 | |
683 | 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 |
684 | reinitialise the kernel state for backends that have one. Despite the |
772 | 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 |
773 | 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 |
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 |
687 | child before resuming or calling C<ev_run>. |
776 | C<EVFLAG_FORKCHECK>) in the child before resuming or calling C<ev_run>. |
688 | |
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>. |
|
|
780 | |
689 | 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 |
690 | 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 |
691 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
783 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
692 | during fork. |
784 | during fork. |
693 | |
785 | |
694 | On the other hand, you only need to call this function in the child |
786 | On the other hand, you only need to call this function in the child |
… | |
… | |
867 | - Queue all expired timers. |
959 | - Queue all expired timers. |
868 | - Queue all expired periodics. |
960 | - Queue all expired periodics. |
869 | - Queue all idle watchers with priority higher than that of pending events. |
961 | - Queue all idle watchers with priority higher than that of pending events. |
870 | - Queue all check watchers. |
962 | - Queue all check watchers. |
871 | - Call all queued watchers in reverse order (i.e. check watchers first). |
963 | - Call all queued watchers in reverse order (i.e. check watchers first). |
872 | Signals and child watchers are implemented as I/O watchers, and will |
964 | Signals, async and child watchers are implemented as I/O watchers, and |
873 | be handled here by queueing them when their watcher gets executed. |
965 | will be handled here by queueing them when their watcher gets executed. |
874 | - If ev_break has been called, or EVRUN_ONCE or EVRUN_NOWAIT |
966 | - If ev_break has been called, or EVRUN_ONCE or EVRUN_NOWAIT |
875 | were used, or there are no active watchers, goto FINISH, otherwise |
967 | were used, or there are no active watchers, goto FINISH, otherwise |
876 | continue with step LOOP. |
968 | continue with step LOOP. |
877 | FINISH: |
969 | FINISH: |
878 | - Reset the ev_break status iff it was EVBREAK_ONE. |
970 | - Reset the ev_break status iff it was EVBREAK_ONE. |
… | |
… | |
1126 | 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 |
1127 | *) >>), 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 |
1128 | corresponding stop function (C<< ev_TYPE_stop (loop, watcher *) >>. |
1220 | corresponding stop function (C<< ev_TYPE_stop (loop, watcher *) >>. |
1129 | |
1221 | |
1130 | 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 |
1131 | 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 |
1132 | 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. |
1133 | |
1226 | |
1134 | 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 |
1135 | 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 |
1136 | third argument. |
1229 | third argument. |
1137 | |
1230 | |
… | |
… | |
1303 | |
1396 | |
1304 | =item bool ev_is_active (ev_TYPE *watcher) |
1397 | =item bool ev_is_active (ev_TYPE *watcher) |
1305 | |
1398 | |
1306 | Returns a true value iff the watcher is active (i.e. it has been started |
1399 | Returns a true value iff the watcher is active (i.e. it has been started |
1307 | and not yet been stopped). As long as a watcher is active you must not modify |
1400 | and not yet been stopped). As long as a watcher is active you must not modify |
1308 | it. |
1401 | it unless documented otherwise. |
|
|
1402 | |
|
|
1403 | Obviously, it is safe to call this on an active watcher, or actually any |
|
|
1404 | watcher that is initialised. |
1309 | |
1405 | |
1310 | =item bool ev_is_pending (ev_TYPE *watcher) |
1406 | =item bool ev_is_pending (ev_TYPE *watcher) |
1311 | |
1407 | |
1312 | Returns a true value iff the watcher is pending, (i.e. it has outstanding |
1408 | Returns a true value iff the watcher is pending, (i.e. it has outstanding |
1313 | events but its callback has not yet been invoked). As long as a watcher |
1409 | events but its callback has not yet been invoked). As long as a watcher |
1314 | is pending (but not active) you must not call an init function on it (but |
1410 | is pending (but not active) you must not call an init function on it (but |
1315 | C<ev_TYPE_set> is safe), you must not change its priority, and you must |
1411 | C<ev_TYPE_set> is safe), you must not change its priority, and you must |
1316 | make sure the watcher is available to libev (e.g. you cannot C<free ()> |
1412 | make sure the watcher is available to libev (e.g. you cannot C<free ()> |
1317 | it). |
1413 | it). |
1318 | |
1414 | |
|
|
1415 | It is safe to call this on any watcher in any state as long as it is |
|
|
1416 | initialised. |
|
|
1417 | |
1319 | =item callback ev_cb (ev_TYPE *watcher) |
1418 | =item callback ev_cb (ev_TYPE *watcher) |
1320 | |
1419 | |
1321 | Returns the callback currently set on the watcher. |
1420 | Returns the callback currently set on the watcher. |
1322 | |
1421 | |
1323 | =item ev_set_cb (ev_TYPE *watcher, callback) |
1422 | =item ev_set_cb (ev_TYPE *watcher, callback) |
… | |
… | |
1336 | from being executed (except for C<ev_idle> watchers). |
1435 | from being executed (except for C<ev_idle> watchers). |
1337 | |
1436 | |
1338 | If you need to suppress invocation when higher priority events are pending |
1437 | If you need to suppress invocation when higher priority events are pending |
1339 | you need to look at C<ev_idle> watchers, which provide this functionality. |
1438 | you need to look at C<ev_idle> watchers, which provide this functionality. |
1340 | |
1439 | |
1341 | You I<must not> change the priority of a watcher as long as it is active or |
1440 | You I<must not> change the priority of a watcher as long as it is active |
1342 | pending. |
1441 | or pending. Reading the priority with C<ev_priority> is fine in any state. |
1343 | |
1442 | |
1344 | Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is |
1443 | Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is |
1345 | fine, as long as you do not mind that the priority value you query might |
1444 | fine, as long as you do not mind that the priority value you query might |
1346 | or might not have been clamped to the valid range. |
1445 | or might not have been clamped to the valid range. |
1347 | |
1446 | |
… | |
… | |
1369 | |
1468 | |
1370 | =item ev_feed_event (loop, ev_TYPE *watcher, int revents) |
1469 | =item ev_feed_event (loop, ev_TYPE *watcher, int revents) |
1371 | |
1470 | |
1372 | Feeds the given event set into the event loop, as if the specified event |
1471 | Feeds the given event set into the event loop, as if the specified event |
1373 | had happened for the specified watcher (which must be a pointer to an |
1472 | had happened for the specified watcher (which must be a pointer to an |
1374 | initialised but not necessarily started event watcher). Obviously you must |
1473 | initialised but not necessarily started event watcher, though it can be |
1375 | not free the watcher as long as it has pending events. |
1474 | active). Obviously you must not free the watcher as long as it has pending |
|
|
1475 | events. |
1376 | |
1476 | |
1377 | Stopping the watcher, letting libev invoke it, or calling |
1477 | Stopping the watcher, letting libev invoke it, or calling |
1378 | C<ev_clear_pending> will clear the pending event, even if the watcher was |
1478 | C<ev_clear_pending> will clear the pending event, even if the watcher was |
1379 | not started in the first place. |
1479 | not started in the first place. |
1380 | |
1480 | |
… | |
… | |
1408 | |
1508 | |
1409 | =item started/running/active |
1509 | =item started/running/active |
1410 | |
1510 | |
1411 | Once a watcher has been started with a call to C<ev_TYPE_start> it becomes |
1511 | Once a watcher has been started with a call to C<ev_TYPE_start> it becomes |
1412 | property of the event loop, and is actively waiting for events. While in |
1512 | property of the event loop, and is actively waiting for events. While in |
1413 | this state it cannot be accessed (except in a few documented ways), moved, |
1513 | this state it cannot be accessed (except in a few documented ways, such as |
1414 | freed or anything else - the only legal thing is to keep a pointer to it, |
1514 | stoping it), moved, freed or anything else - the only legal thing is to |
1415 | and call libev functions on it that are documented to work on active watchers. |
1515 | keep a pointer to it, and call libev functions on it that are documented |
|
|
1516 | to work on active watchers. |
|
|
1517 | |
|
|
1518 | As a rule of thumb, before accessing a member or calling any function on |
|
|
1519 | a watcher, it should be stopped (or freshly initialised). If that is not |
|
|
1520 | convenient, you can check the documentation for that function or member to |
|
|
1521 | see if it is safe to use on an active watcher. |
1416 | |
1522 | |
1417 | =item pending |
1523 | =item pending |
1418 | |
1524 | |
1419 | If a watcher is active and libev determines that an event it is interested |
1525 | If a watcher is active and libev determines that an event it is interested |
1420 | in has occurred (such as a timer expiring), it will become pending. It will |
1526 | in has occurred (such as a timer expiring), it will become pending. It |
1421 | stay in this pending state until either it is stopped or its callback is |
1527 | will stay in this pending state until either it is explicitly stopped or |
1422 | about to be invoked, so it is not normally pending inside the watcher |
1528 | its callback is about to be invoked, so it is not normally pending inside |
1423 | callback. |
1529 | the watcher callback. |
1424 | |
1530 | |
1425 | The watcher might or might not be active while it is pending (for example, |
1531 | Generally, the watcher might or might not be active while it is pending |
1426 | an expired non-repeating timer can be pending but no longer active). If it |
1532 | (for example, an expired non-repeating timer can be pending but no longer |
1427 | is stopped, it can be freely accessed (e.g. by calling C<ev_TYPE_set>), |
1533 | active). If it is pending but not active, it can be freely accessed (e.g. |
1428 | but it is still property of the event loop at this time, so cannot be |
1534 | by calling C<ev_TYPE_set>), but it is still property of the event loop at |
1429 | moved, freed or reused. And if it is active the rules described in the |
1535 | this time, so cannot be moved, freed or reused. And if it is active the |
1430 | previous item still apply. |
1536 | rules described in the previous item still apply. |
|
|
1537 | |
|
|
1538 | Explicitly stopping a watcher will also clear the pending state |
|
|
1539 | unconditionally, so it is safe to stop a watcher and then free it. |
1431 | |
1540 | |
1432 | It is also possible to feed an event on a watcher that is not active (e.g. |
1541 | It is also possible to feed an event on a watcher that is not active (e.g. |
1433 | via C<ev_feed_event>), in which case it becomes pending without being |
1542 | via C<ev_feed_event>), in which case it becomes pending without being |
1434 | active. |
1543 | active. |
1435 | |
1544 | |
… | |
… | |
1452 | |
1561 | |
1453 | Many event loops support I<watcher priorities>, which are usually small |
1562 | Many event loops support I<watcher priorities>, which are usually small |
1454 | integers that influence the ordering of event callback invocation |
1563 | integers that influence the ordering of event callback invocation |
1455 | between watchers in some way, all else being equal. |
1564 | between watchers in some way, all else being equal. |
1456 | |
1565 | |
1457 | In libev, Watcher priorities can be set using C<ev_set_priority>. See its |
1566 | In libev, watcher priorities can be set using C<ev_set_priority>. See its |
1458 | description for the more technical details such as the actual priority |
1567 | description for the more technical details such as the actual priority |
1459 | range. |
1568 | range. |
1460 | |
1569 | |
1461 | There are two common ways how these these priorities are being interpreted |
1570 | There are two common ways how these these priorities are being interpreted |
1462 | by event loops: |
1571 | by event loops: |
… | |
… | |
1556 | |
1665 | |
1557 | This section describes each watcher in detail, but will not repeat |
1666 | This section describes each watcher in detail, but will not repeat |
1558 | information given in the last section. Any initialisation/set macros, |
1667 | information given in the last section. Any initialisation/set macros, |
1559 | functions and members specific to the watcher type are explained. |
1668 | functions and members specific to the watcher type are explained. |
1560 | |
1669 | |
1561 | Members are additionally marked with either I<[read-only]>, meaning that, |
1670 | Most members are additionally marked with either I<[read-only]>, meaning |
1562 | while the watcher is active, you can look at the member and expect some |
1671 | that, while the watcher is active, you can look at the member and expect |
1563 | sensible content, but you must not modify it (you can modify it while the |
1672 | some sensible content, but you must not modify it (you can modify it while |
1564 | watcher is stopped to your hearts content), or I<[read-write]>, which |
1673 | the watcher is stopped to your hearts content), or I<[read-write]>, which |
1565 | means you can expect it to have some sensible content while the watcher |
1674 | means you can expect it to have some sensible content while the watcher is |
1566 | is active, but you can also modify it. Modifying it may not do something |
1675 | active, but you can also modify it (within the same thread as the event |
|
|
1676 | loop, i.e. without creating data races). Modifying it may not do something |
1567 | sensible or take immediate effect (or do anything at all), but libev will |
1677 | sensible or take immediate effect (or do anything at all), but libev will |
1568 | not crash or malfunction in any way. |
1678 | not crash or malfunction in any way. |
1569 | |
1679 | |
|
|
1680 | In any case, the documentation for each member will explain what the |
|
|
1681 | effects are, and if there are any additional access restrictions. |
1570 | |
1682 | |
1571 | =head2 C<ev_io> - is this file descriptor readable or writable? |
1683 | =head2 C<ev_io> - is this file descriptor readable or writable? |
1572 | |
1684 | |
1573 | I/O watchers check whether a file descriptor is readable or writable |
1685 | I/O watchers check whether a file descriptor is readable or writable |
1574 | in each iteration of the event loop, or, more precisely, when reading |
1686 | in each iteration of the event loop, or, more precisely, when reading |
… | |
… | |
1601 | |
1713 | |
1602 | But really, best use non-blocking mode. |
1714 | But really, best use non-blocking mode. |
1603 | |
1715 | |
1604 | =head3 The special problem of disappearing file descriptors |
1716 | =head3 The special problem of disappearing file descriptors |
1605 | |
1717 | |
1606 | Some backends (e.g. kqueue, epoll) need to be told about closing a file |
1718 | 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, |
1719 | 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 |
1720 | 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 |
1721 | 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 |
1722 | 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 |
1723 | is registered with libev, there is no efficient way to see that this is, |
1612 | fact, a different file descriptor. |
1724 | in fact, a different file descriptor. |
1613 | |
1725 | |
1614 | To avoid having to explicitly tell libev about such cases, libev follows |
1726 | 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 |
1727 | 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 |
1728 | 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 |
1729 | 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 |
1778 | when you rarely read from a file instead of from a socket, and want to |
1667 | reuse the same code path. |
1779 | reuse the same code path. |
1668 | |
1780 | |
1669 | =head3 The special problem of fork |
1781 | =head3 The special problem of fork |
1670 | |
1782 | |
1671 | Some backends (epoll, kqueue) do not support C<fork ()> at all or exhibit |
1783 | Some backends (epoll, kqueue, linuxaio, iouring) do not support C<fork ()> |
1672 | useless behaviour. Libev fully supports fork, but needs to be told about |
1784 | 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. |
1785 | to be told about it in the child if you want to continue to use it in the |
|
|
1786 | child. |
1674 | |
1787 | |
1675 | To support fork in your child processes, you have to call C<ev_loop_fork |
1788 | 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 |
1789 | ()> after a fork in the child, enable C<EVFLAG_FORKCHECK>, or resort to |
1677 | C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>. |
1790 | C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>. |
1678 | |
1791 | |
… | |
… | |
1733 | =item ev_io_init (ev_io *, callback, int fd, int events) |
1846 | =item ev_io_init (ev_io *, callback, int fd, int events) |
1734 | |
1847 | |
1735 | =item ev_io_set (ev_io *, int fd, int events) |
1848 | =item ev_io_set (ev_io *, int fd, int events) |
1736 | |
1849 | |
1737 | Configures an C<ev_io> watcher. The C<fd> is the file descriptor to |
1850 | Configures an C<ev_io> watcher. The C<fd> is the file descriptor to |
1738 | receive events for and C<events> is either C<EV_READ>, C<EV_WRITE> or |
1851 | receive events for and C<events> is either C<EV_READ>, C<EV_WRITE>, both |
1739 | C<EV_READ | EV_WRITE>, to express the desire to receive the given events. |
1852 | C<EV_READ | EV_WRITE> or C<0>, to express the desire to receive the given |
|
|
1853 | events. |
1740 | |
1854 | |
1741 | =item int fd [read-only] |
1855 | Note that setting the C<events> to C<0> and starting the watcher is |
|
|
1856 | supported, but not specially optimized - if your program sometimes happens |
|
|
1857 | to generate this combination this is fine, but if it is easy to avoid |
|
|
1858 | starting an io watcher watching for no events you should do so. |
1742 | |
1859 | |
1743 | The file descriptor being watched. |
1860 | =item ev_io_modify (ev_io *, int events) |
1744 | |
1861 | |
|
|
1862 | Similar to C<ev_io_set>, but only changes the requested events. Using this |
|
|
1863 | might be faster with some backends, as libev can assume that the C<fd> |
|
|
1864 | still refers to the same underlying file description, something it cannot |
|
|
1865 | do when using C<ev_io_set>. |
|
|
1866 | |
|
|
1867 | =item int fd [no-modify] |
|
|
1868 | |
|
|
1869 | The file descriptor being watched. While it can be read at any time, you |
|
|
1870 | must not modify this member even when the watcher is stopped - always use |
|
|
1871 | C<ev_io_set> for that. |
|
|
1872 | |
1745 | =item int events [read-only] |
1873 | =item int events [no-modify] |
1746 | |
1874 | |
1747 | The events being watched. |
1875 | The set of events the fd is being watched for, among other flags. Remember |
|
|
1876 | that this is a bit set - to test for C<EV_READ>, use C<< w->events & |
|
|
1877 | EV_READ >>, and similarly for C<EV_WRITE>. |
|
|
1878 | |
|
|
1879 | As with C<fd>, you must not modify this member even when the watcher is |
|
|
1880 | stopped, always use C<ev_io_set> or C<ev_io_modify> for that. |
1748 | |
1881 | |
1749 | =back |
1882 | =back |
1750 | |
1883 | |
1751 | =head3 Examples |
1884 | =head3 Examples |
1752 | |
1885 | |
… | |
… | |
2024 | |
2157 | |
2025 | The relative timeouts are calculated relative to the C<ev_now ()> |
2158 | 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 |
2159 | 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 |
2160 | 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 |
2161 | 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: |
2162 | timeout on the current time, use something like the following to adjust |
|
|
2163 | for it: |
2030 | |
2164 | |
2031 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
2165 | ev_timer_set (&timer, after + (ev_time () - ev_now ()), 0.); |
2032 | |
2166 | |
2033 | If the event loop is suspended for a long time, you can also force an |
2167 | 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 |
2168 | update of the time returned by C<ev_now ()> by calling C<ev_now_update |
2035 | ()>. |
2169 | ()>, although that will push the event time of all outstanding events |
|
|
2170 | further into the future. |
2036 | |
2171 | |
2037 | =head3 The special problem of unsynchronised clocks |
2172 | =head3 The special problem of unsynchronised clocks |
2038 | |
2173 | |
2039 | Modern systems have a variety of clocks - libev itself uses the normal |
2174 | 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 |
2175 | "wall clock" clock and, if available, the monotonic clock (to avoid time |
… | |
… | |
2103 | |
2238 | |
2104 | =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat) |
2239 | =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat) |
2105 | |
2240 | |
2106 | =item ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat) |
2241 | =item ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat) |
2107 | |
2242 | |
2108 | Configure the timer to trigger after C<after> seconds. If C<repeat> |
2243 | 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 |
2244 | 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 |
2245 | automatically be stopped once the timeout is reached. If it is positive, |
2111 | configured to trigger again C<repeat> seconds later, again, and again, |
2246 | then the timer will automatically be configured to trigger again C<repeat> |
2112 | until stopped manually. |
2247 | seconds later, again, and again, until stopped manually. |
2113 | |
2248 | |
2114 | The timer itself will do a best-effort at avoiding drift, that is, if |
2249 | 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 |
2250 | 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 |
2251 | 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 |
2252 | 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 |
2334 | Periodic watchers are also timers of a kind, but they are very versatile |
2200 | (and unfortunately a bit complex). |
2335 | (and unfortunately a bit complex). |
2201 | |
2336 | |
2202 | Unlike C<ev_timer>, periodic watchers are not based on real time (or |
2337 | 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 |
2338 | 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 |
2339 | (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 |
2340 | 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 |
2341 | time, and time jumps are not uncommon (e.g. when you adjust your |
2207 | wrist-watch). |
2342 | wrist-watch). |
2208 | |
2343 | |
2209 | You can tell a periodic watcher to trigger after some specific point |
2344 | 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 |
2349 | C<ev_timer>, which would still trigger roughly 10 seconds after starting |
2215 | it, as it uses a relative timeout). |
2350 | it, as it uses a relative timeout). |
2216 | |
2351 | |
2217 | C<ev_periodic> watchers can also be used to implement vastly more complex |
2352 | 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 |
2353 | 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 |
2354 | other complicated rules. This cannot easily be done with C<ev_timer> |
2220 | those cannot react to time jumps. |
2355 | watchers, as those cannot react to time jumps. |
2221 | |
2356 | |
2222 | As with timers, the callback is guaranteed to be invoked only when the |
2357 | 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 |
2358 | 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 |
2359 | 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 |
2360 | earlier time-out values are invoked before ones with later time-out values |
… | |
… | |
2311 | |
2446 | |
2312 | NOTE: I<< This callback must always return a time that is higher than or |
2447 | NOTE: I<< This callback must always return a time that is higher than or |
2313 | equal to the passed C<now> value >>. |
2448 | equal to the passed C<now> value >>. |
2314 | |
2449 | |
2315 | This can be used to create very complex timers, such as a timer that |
2450 | 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 |
2451 | 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 |
2452 | 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 |
2453 | this. Here is a (completely untested, no error checking) example on how to |
2319 | reason I omitted it as an example). |
2454 | do this: |
|
|
2455 | |
|
|
2456 | #include <time.h> |
|
|
2457 | |
|
|
2458 | static ev_tstamp |
|
|
2459 | my_rescheduler (ev_periodic *w, ev_tstamp now) |
|
|
2460 | { |
|
|
2461 | time_t tnow = (time_t)now; |
|
|
2462 | struct tm tm; |
|
|
2463 | localtime_r (&tnow, &tm); |
|
|
2464 | |
|
|
2465 | tm.tm_sec = tm.tm_min = tm.tm_hour = 0; // midnight current day |
|
|
2466 | ++tm.tm_mday; // midnight next day |
|
|
2467 | |
|
|
2468 | return mktime (&tm); |
|
|
2469 | } |
|
|
2470 | |
|
|
2471 | Note: this code might run into trouble on days that have more then two |
|
|
2472 | midnights (beginning and end). |
2320 | |
2473 | |
2321 | =back |
2474 | =back |
2322 | |
2475 | |
2323 | =item ev_periodic_again (loop, ev_periodic *) |
2476 | =item ev_periodic_again (loop, ev_periodic *) |
2324 | |
2477 | |
… | |
… | |
2389 | |
2542 | |
2390 | ev_periodic hourly_tick; |
2543 | ev_periodic hourly_tick; |
2391 | ev_periodic_init (&hourly_tick, clock_cb, |
2544 | ev_periodic_init (&hourly_tick, clock_cb, |
2392 | fmod (ev_now (loop), 3600.), 3600., 0); |
2545 | fmod (ev_now (loop), 3600.), 3600., 0); |
2393 | ev_periodic_start (loop, &hourly_tick); |
2546 | ev_periodic_start (loop, &hourly_tick); |
2394 | |
2547 | |
2395 | |
2548 | |
2396 | =head2 C<ev_signal> - signal me when a signal gets signalled! |
2549 | =head2 C<ev_signal> - signal me when a signal gets signalled! |
2397 | |
2550 | |
2398 | Signal watchers will trigger an event when the process receives a specific |
2551 | 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 |
2552 | 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 |
2562 | 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 |
2563 | 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 |
2564 | 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. |
2565 | the moment, C<SIGCHLD> is permanently tied to the default loop. |
2413 | |
2566 | |
2414 | When the first watcher gets started will libev actually register something |
2567 | 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 |
2568 | register something with the kernel. It thus coexists with your own signal |
2416 | you don't register any with libev for the same signal). |
2569 | handlers as long as you don't register any with libev for the same signal. |
2417 | |
2570 | |
2418 | If possible and supported, libev will install its handlers with |
2571 | If possible and supported, libev will install its handlers with |
2419 | C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should |
2572 | 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 |
2573 | 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 |
2574 | interrupted by signals you can block all signals in an C<ev_check> watcher |
… | |
… | |
2903 | |
3056 | |
2904 | Prepare and check watchers are often (but not always) used in pairs: |
3057 | Prepare and check watchers are often (but not always) used in pairs: |
2905 | prepare watchers get invoked before the process blocks and check watchers |
3058 | prepare watchers get invoked before the process blocks and check watchers |
2906 | afterwards. |
3059 | afterwards. |
2907 | |
3060 | |
2908 | You I<must not> call C<ev_run> or similar functions that enter |
3061 | 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> |
3062 | 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 |
3063 | 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 |
3064 | 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, |
3065 | 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 |
3066 | C<ev_prepare>, blocking, C<ev_check> so if you have one watcher of each |
2914 | called in pairs bracketing the blocking call. |
3067 | kind they will always be called in pairs bracketing the blocking call. |
2915 | |
3068 | |
2916 | Their main purpose is to integrate other event mechanisms into libev and |
3069 | 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 |
3070 | 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 |
3071 | variable changes, implement your own watchers, integrate net-snmp or a |
2919 | coroutine library and lots more. They are also occasionally useful if |
3072 | coroutine library and lots more. They are also occasionally useful if |
… | |
… | |
3209 | used). |
3362 | used). |
3210 | |
3363 | |
3211 | struct ev_loop *loop_hi = ev_default_init (0); |
3364 | struct ev_loop *loop_hi = ev_default_init (0); |
3212 | struct ev_loop *loop_lo = 0; |
3365 | struct ev_loop *loop_lo = 0; |
3213 | ev_embed embed; |
3366 | ev_embed embed; |
3214 | |
3367 | |
3215 | // see if there is a chance of getting one that works |
3368 | // see if there is a chance of getting one that works |
3216 | // (remember that a flags value of 0 means autodetection) |
3369 | // (remember that a flags value of 0 means autodetection) |
3217 | loop_lo = ev_embeddable_backends () & ev_recommended_backends () |
3370 | loop_lo = ev_embeddable_backends () & ev_recommended_backends () |
3218 | ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ()) |
3371 | ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ()) |
3219 | : 0; |
3372 | : 0; |
… | |
… | |
3233 | C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too). |
3386 | C<loop_socket>. (One might optionally use C<EVFLAG_NOENV>, too). |
3234 | |
3387 | |
3235 | struct ev_loop *loop = ev_default_init (0); |
3388 | struct ev_loop *loop = ev_default_init (0); |
3236 | struct ev_loop *loop_socket = 0; |
3389 | struct ev_loop *loop_socket = 0; |
3237 | ev_embed embed; |
3390 | ev_embed embed; |
3238 | |
3391 | |
3239 | if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE) |
3392 | if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE) |
3240 | if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE)) |
3393 | if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE)) |
3241 | { |
3394 | { |
3242 | ev_embed_init (&embed, 0, loop_socket); |
3395 | ev_embed_init (&embed, 0, loop_socket); |
3243 | ev_embed_start (loop, &embed); |
3396 | ev_embed_start (loop, &embed); |
… | |
… | |
3259 | and calls it in the wrong process, the fork handlers will be invoked, too, |
3412 | and calls it in the wrong process, the fork handlers will be invoked, too, |
3260 | of course. |
3413 | of course. |
3261 | |
3414 | |
3262 | =head3 The special problem of life after fork - how is it possible? |
3415 | =head3 The special problem of life after fork - how is it possible? |
3263 | |
3416 | |
3264 | Most uses of C<fork()> consist of forking, then some simple calls to set |
3417 | 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 |
3418 | up/change the process environment, followed by a call to C<exec()>. This |
3266 | sequence should be handled by libev without any problems. |
3419 | sequence should be handled by libev without any problems. |
3267 | |
3420 | |
3268 | This changes when the application actually wants to do event handling |
3421 | 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 |
3422 | in the child, or both parent in child, in effect "continuing" after the |
… | |
… | |
3507 | |
3660 | |
3508 | There are some other functions of possible interest. Described. Here. Now. |
3661 | There are some other functions of possible interest. Described. Here. Now. |
3509 | |
3662 | |
3510 | =over 4 |
3663 | =over 4 |
3511 | |
3664 | |
3512 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
3665 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback, arg) |
3513 | |
3666 | |
3514 | This function combines a simple timer and an I/O watcher, calls your |
3667 | This function combines a simple timer and an I/O watcher, calls your |
3515 | callback on whichever event happens first and automatically stops both |
3668 | 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 |
3669 | 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 |
3670 | or timeout without having to allocate/configure/start/stop/free one or |
… | |
… | |
3725 | event loop thread and an unspecified mechanism to wake up the main thread. |
3878 | event loop thread and an unspecified mechanism to wake up the main thread. |
3726 | |
3879 | |
3727 | First, you need to associate some data with the event loop: |
3880 | First, you need to associate some data with the event loop: |
3728 | |
3881 | |
3729 | typedef struct { |
3882 | typedef struct { |
3730 | mutex_t lock; /* global loop lock */ |
3883 | pthread_mutex_t lock; /* global loop lock */ |
|
|
3884 | pthread_t tid; |
|
|
3885 | pthread_cond_t invoke_cv; |
3731 | ev_async async_w; |
3886 | ev_async async_w; |
3732 | thread_t tid; |
|
|
3733 | cond_t invoke_cv; |
|
|
3734 | } userdata; |
3887 | } userdata; |
3735 | |
3888 | |
3736 | void prepare_loop (EV_P) |
3889 | void prepare_loop (EV_P) |
3737 | { |
3890 | { |
3738 | // for simplicity, we use a static userdata struct. |
3891 | // for simplicity, we use a static userdata struct. |
3739 | static userdata u; |
3892 | static userdata u; |
3740 | |
3893 | |
3741 | ev_async_init (&u->async_w, async_cb); |
3894 | ev_async_init (&u.async_w, async_cb); |
3742 | ev_async_start (EV_A_ &u->async_w); |
3895 | ev_async_start (EV_A_ &u.async_w); |
3743 | |
3896 | |
3744 | pthread_mutex_init (&u->lock, 0); |
3897 | pthread_mutex_init (&u.lock, 0); |
3745 | pthread_cond_init (&u->invoke_cv, 0); |
3898 | pthread_cond_init (&u.invoke_cv, 0); |
3746 | |
3899 | |
3747 | // now associate this with the loop |
3900 | // now associate this with the loop |
3748 | ev_set_userdata (EV_A_ u); |
3901 | ev_set_userdata (EV_A_ &u); |
3749 | ev_set_invoke_pending_cb (EV_A_ l_invoke); |
3902 | ev_set_invoke_pending_cb (EV_A_ l_invoke); |
3750 | ev_set_loop_release_cb (EV_A_ l_release, l_acquire); |
3903 | ev_set_loop_release_cb (EV_A_ l_release, l_acquire); |
3751 | |
3904 | |
3752 | // then create the thread running ev_run |
3905 | // then create the thread running ev_run |
3753 | pthread_create (&u->tid, 0, l_run, EV_A); |
3906 | pthread_create (&u.tid, 0, l_run, EV_A); |
3754 | } |
3907 | } |
3755 | |
3908 | |
3756 | The callback for the C<ev_async> watcher does nothing: the watcher is used |
3909 | The callback for the C<ev_async> watcher does nothing: the watcher is used |
3757 | solely to wake up the event loop so it takes notice of any new watchers |
3910 | solely to wake up the event loop so it takes notice of any new watchers |
3758 | that might have been added: |
3911 | that might have been added: |
… | |
… | |
3893 | To embed libev, see L</EMBEDDING>, but in short, it's easiest to create two |
4046 | 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: |
4047 | files, F<my_ev.h> and F<my_ev.c> that include the respective libev files: |
3895 | |
4048 | |
3896 | // my_ev.h |
4049 | // my_ev.h |
3897 | #define EV_CB_DECLARE(type) struct my_coro *cb; |
4050 | #define EV_CB_DECLARE(type) struct my_coro *cb; |
3898 | #define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb); |
4051 | #define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb) |
3899 | #include "../libev/ev.h" |
4052 | #include "../libev/ev.h" |
3900 | |
4053 | |
3901 | // my_ev.c |
4054 | // my_ev.c |
3902 | #define EV_H "my_ev.h" |
4055 | #define EV_H "my_ev.h" |
3903 | #include "../libev/ev.c" |
4056 | #include "../libev/ev.c" |
… | |
… | |
3949 | The normal C API should work fine when used from C++: both ev.h and the |
4102 | 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 |
4103 | libev sources can be compiled as C++. Therefore, code that uses the C API |
3951 | will work fine. |
4104 | will work fine. |
3952 | |
4105 | |
3953 | Proper exception specifications might have to be added to callbacks passed |
4106 | Proper exception specifications might have to be added to callbacks passed |
3954 | to libev: exceptions may be thrown only from watcher callbacks, all |
4107 | to libev: exceptions may be thrown only from watcher callbacks, all other |
3955 | other callbacks (allocator, syserr, loop acquire/release and periodic |
4108 | callbacks (allocator, syserr, loop acquire/release and periodic reschedule |
3956 | reschedule callbacks) must not throw exceptions, and might need a C<throw |
4109 | 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 |
4110 | 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: |
4111 | C++ you can use the C<EV_NOEXCEPT> macro for this: |
3959 | |
4112 | |
3960 | static void |
4113 | static void |
3961 | fatal_error (const char *msg) EV_THROW |
4114 | fatal_error (const char *msg) EV_NOEXCEPT |
3962 | { |
4115 | { |
3963 | perror (msg); |
4116 | perror (msg); |
3964 | abort (); |
4117 | abort (); |
3965 | } |
4118 | } |
3966 | |
4119 | |
… | |
… | |
3980 | Libev comes with some simplistic wrapper classes for C++ that mainly allow |
4133 | 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 |
4134 | 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. |
4135 | the callback model to a model using method callbacks on objects. |
3983 | |
4136 | |
3984 | To use it, |
4137 | To use it, |
3985 | |
4138 | |
3986 | #include <ev++.h> |
4139 | #include <ev++.h> |
3987 | |
4140 | |
3988 | This automatically includes F<ev.h> and puts all of its definitions (many |
4141 | 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 |
4142 | 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 |
4143 | put into the C<ev> namespace. It should support all the same embedding |
… | |
… | |
4093 | void operator() (ev::io &w, int revents) |
4246 | void operator() (ev::io &w, int revents) |
4094 | { |
4247 | { |
4095 | ... |
4248 | ... |
4096 | } |
4249 | } |
4097 | } |
4250 | } |
4098 | |
4251 | |
4099 | myfunctor f; |
4252 | myfunctor f; |
4100 | |
4253 | |
4101 | ev::io w; |
4254 | ev::io w; |
4102 | w.set (&f); |
4255 | w.set (&f); |
4103 | |
4256 | |
… | |
… | |
4129 | gets automatically stopped and restarted when reconfiguring it with this |
4282 | gets automatically stopped and restarted when reconfiguring it with this |
4130 | method. |
4283 | method. |
4131 | |
4284 | |
4132 | For C<ev::embed> watchers this method is called C<set_embed>, to avoid |
4285 | For C<ev::embed> watchers this method is called C<set_embed>, to avoid |
4133 | clashing with the C<set (loop)> method. |
4286 | clashing with the C<set (loop)> method. |
|
|
4287 | |
|
|
4288 | For C<ev::io> watchers there is an additional C<set> method that acepts a |
|
|
4289 | new event mask only, and internally calls C<ev_io_modify>. |
4134 | |
4290 | |
4135 | =item w->start () |
4291 | =item w->start () |
4136 | |
4292 | |
4137 | Starts the watcher. Note that there is no C<loop> argument, as the |
4293 | Starts the watcher. Note that there is no C<loop> argument, as the |
4138 | constructor already stores the event loop. |
4294 | constructor already stores the event loop. |
… | |
… | |
4376 | ev_vars.h |
4532 | ev_vars.h |
4377 | ev_wrap.h |
4533 | ev_wrap.h |
4378 | |
4534 | |
4379 | ev_win32.c required on win32 platforms only |
4535 | ev_win32.c required on win32 platforms only |
4380 | |
4536 | |
4381 | ev_select.c only when select backend is enabled (which is enabled by default) |
4537 | ev_select.c only when select backend is enabled |
4382 | ev_poll.c only when poll backend is enabled (disabled by default) |
4538 | ev_poll.c only when poll backend is enabled |
4383 | ev_epoll.c only when the epoll backend is enabled (disabled by default) |
4539 | ev_epoll.c only when the epoll backend is enabled |
|
|
4540 | ev_linuxaio.c only when the linux aio backend is enabled |
|
|
4541 | 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) |
4542 | 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) |
4543 | ev_port.c only when the solaris port backend is enabled |
4386 | |
4544 | |
4387 | F<ev.c> includes the backend files directly when enabled, so you only need |
4545 | F<ev.c> includes the backend files directly when enabled, so you only need |
4388 | to compile this single file. |
4546 | to compile this single file. |
4389 | |
4547 | |
4390 | =head3 LIBEVENT COMPATIBILITY API |
4548 | =head3 LIBEVENT COMPATIBILITY API |
… | |
… | |
4509 | available and will probe for kernel support at runtime. This will improve |
4667 | available and will probe for kernel support at runtime. This will improve |
4510 | C<ev_signal> and C<ev_async> performance and reduce resource consumption. |
4668 | C<ev_signal> and C<ev_async> performance and reduce resource consumption. |
4511 | If undefined, it will be enabled if the headers indicate GNU/Linux + Glibc |
4669 | If undefined, it will be enabled if the headers indicate GNU/Linux + Glibc |
4512 | 2.7 or newer, otherwise disabled. |
4670 | 2.7 or newer, otherwise disabled. |
4513 | |
4671 | |
|
|
4672 | =item EV_USE_SIGNALFD |
|
|
4673 | |
|
|
4674 | If defined to be C<1>, then libev will assume that C<signalfd ()> is |
|
|
4675 | available and will probe for kernel support at runtime. This enables |
|
|
4676 | the use of EVFLAG_SIGNALFD for faster and simpler signal handling. If |
|
|
4677 | undefined, it will be enabled if the headers indicate GNU/Linux + Glibc |
|
|
4678 | 2.7 or newer, otherwise disabled. |
|
|
4679 | |
|
|
4680 | =item EV_USE_TIMERFD |
|
|
4681 | |
|
|
4682 | If defined to be C<1>, then libev will assume that C<timerfd ()> is |
|
|
4683 | available and will probe for kernel support at runtime. This allows |
|
|
4684 | libev to detect time jumps accurately. If undefined, it will be enabled |
|
|
4685 | if the headers indicate GNU/Linux + Glibc 2.8 or newer and define |
|
|
4686 | C<TFD_TIMER_CANCEL_ON_SET>, otherwise disabled. |
|
|
4687 | |
|
|
4688 | =item EV_USE_EVENTFD |
|
|
4689 | |
|
|
4690 | If defined to be C<1>, then libev will assume that C<eventfd ()> is |
|
|
4691 | available and will probe for kernel support at runtime. This will improve |
|
|
4692 | C<ev_signal> and C<ev_async> performance and reduce resource consumption. |
|
|
4693 | If undefined, it will be enabled if the headers indicate GNU/Linux + Glibc |
|
|
4694 | 2.7 or newer, otherwise disabled. |
|
|
4695 | |
4514 | =item EV_USE_SELECT |
4696 | =item EV_USE_SELECT |
4515 | |
4697 | |
4516 | If undefined or defined to be C<1>, libev will compile in support for the |
4698 | If undefined or defined to be C<1>, libev will compile in support for the |
4517 | C<select>(2) backend. No attempt at auto-detection will be done: if no |
4699 | C<select>(2) backend. No attempt at auto-detection will be done: if no |
4518 | other method takes over, select will be it. Otherwise the select backend |
4700 | other method takes over, select will be it. Otherwise the select backend |
… | |
… | |
4578 | If defined to be C<1>, libev will compile in support for the Linux |
4760 | 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, |
4761 | C<epoll>(7) backend. Its availability will be detected at runtime, |
4580 | otherwise another method will be used as fallback. This is the preferred |
4762 | 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 |
4763 | 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. |
4764 | headers indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
|
|
4765 | |
|
|
4766 | =item EV_USE_LINUXAIO |
|
|
4767 | |
|
|
4768 | If defined to be C<1>, libev will compile in support for the Linux aio |
|
|
4769 | backend (C<EV_USE_EPOLL> must also be enabled). If undefined, it will be |
|
|
4770 | enabled on linux, otherwise disabled. |
|
|
4771 | |
|
|
4772 | =item EV_USE_IOURING |
|
|
4773 | |
|
|
4774 | If defined to be C<1>, libev will compile in support for the Linux |
|
|
4775 | io_uring backend (C<EV_USE_EPOLL> must also be enabled). Due to it's |
|
|
4776 | current limitations it has to be requested explicitly. If undefined, it |
|
|
4777 | will be enabled on linux, otherwise disabled. |
4583 | |
4778 | |
4584 | =item EV_USE_KQUEUE |
4779 | =item EV_USE_KQUEUE |
4585 | |
4780 | |
4586 | If defined to be C<1>, libev will compile in support for the BSD style |
4781 | 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, |
4782 | C<kqueue>(2) backend. Its actual availability will be detected at runtime, |
… | |
… | |
4618 | different cpus (or different cpu cores). This reduces dependencies |
4813 | different cpus (or different cpu cores). This reduces dependencies |
4619 | and makes libev faster. |
4814 | and makes libev faster. |
4620 | |
4815 | |
4621 | =item EV_NO_THREADS |
4816 | =item EV_NO_THREADS |
4622 | |
4817 | |
4623 | If defined to be C<1>, libev will assume that it will never be called |
4818 | If defined to be C<1>, libev will assume that it will never be called from |
4624 | from different threads, which is a stronger assumption than C<EV_NO_SMP>, |
4819 | different threads (that includes signal handlers), which is a stronger |
4625 | above. This reduces dependencies and makes libev faster. |
4820 | assumption than C<EV_NO_SMP>, above. This reduces dependencies and makes |
|
|
4821 | libev faster. |
4626 | |
4822 | |
4627 | =item EV_ATOMIC_T |
4823 | =item EV_ATOMIC_T |
4628 | |
4824 | |
4629 | Libev requires an integer type (suitable for storing C<0> or C<1>) whose |
4825 | Libev requires an integer type (suitable for storing C<0> or C<1>) whose |
4630 | access is atomic with respect to other threads or signal contexts. No |
4826 | access is atomic with respect to other threads or signal contexts. No |
… | |
… | |
4863 | in. If set to C<1>, then verification code will be compiled in, but not |
5059 | in. If set to C<1>, then verification code will be compiled in, but not |
4864 | called. If set to C<2>, then the internal verification code will be |
5060 | called. If set to C<2>, then the internal verification code will be |
4865 | called once per loop, which can slow down libev. If set to C<3>, then the |
5061 | called once per loop, which can slow down libev. If set to C<3>, then the |
4866 | verification code will be called very frequently, which will slow down |
5062 | verification code will be called very frequently, which will slow down |
4867 | libev considerably. |
5063 | libev considerably. |
|
|
5064 | |
|
|
5065 | Verification errors are reported via C's C<assert> mechanism, so if you |
|
|
5066 | disable that (e.g. by defining C<NDEBUG>) then no errors will be reported. |
4868 | |
5067 | |
4869 | The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it |
5068 | The default is C<1>, unless C<EV_FEATURES> overrides it, in which case it |
4870 | will be C<0>. |
5069 | will be C<0>. |
4871 | |
5070 | |
4872 | =item EV_COMMON |
5071 | =item EV_COMMON |
… | |
… | |
5289 | structure (guaranteed by POSIX but not by ISO C for example), but it also |
5488 | structure (guaranteed by POSIX but not by ISO C for example), but it also |
5290 | assumes that the same (machine) code can be used to call any watcher |
5489 | assumes that the same (machine) code can be used to call any watcher |
5291 | callback: The watcher callbacks have different type signatures, but libev |
5490 | callback: The watcher callbacks have different type signatures, but libev |
5292 | calls them using an C<ev_watcher *> internally. |
5491 | calls them using an C<ev_watcher *> internally. |
5293 | |
5492 | |
|
|
5493 | =item null pointers and integer zero are represented by 0 bytes |
|
|
5494 | |
|
|
5495 | Libev uses C<memset> to initialise structs and arrays to C<0> bytes, and |
|
|
5496 | relies on this setting pointers and integers to null. |
|
|
5497 | |
5294 | =item pointer accesses must be thread-atomic |
5498 | =item pointer accesses must be thread-atomic |
5295 | |
5499 | |
5296 | Accessing a pointer value must be atomic, it must both be readable and |
5500 | Accessing a pointer value must be atomic, it must both be readable and |
5297 | writable in one piece - this is the case on all current architectures. |
5501 | writable in one piece - this is the case on all current architectures. |
5298 | |
5502 | |
… | |
… | |
5426 | =over 4 |
5630 | =over 4 |
5427 | |
5631 | |
5428 | =item C<EV_COMPAT3> backwards compatibility mechanism |
5632 | =item C<EV_COMPAT3> backwards compatibility mechanism |
5429 | |
5633 | |
5430 | The backward compatibility mechanism can be controlled by |
5634 | The backward compatibility mechanism can be controlled by |
5431 | C<EV_COMPAT3>. See L</PREPROCESSOR SYMBOLS/MACROS> in the L</EMBEDDING> |
5635 | C<EV_COMPAT3>. See L</"PREPROCESSOR SYMBOLS/MACROS"> in the L</EMBEDDING> |
5432 | section. |
5636 | section. |
5433 | |
5637 | |
5434 | =item C<ev_default_destroy> and C<ev_default_fork> have been removed |
5638 | =item C<ev_default_destroy> and C<ev_default_fork> have been removed |
5435 | |
5639 | |
5436 | These calls can be replaced easily by their C<ev_loop_xxx> counterparts: |
5640 | These calls can be replaced easily by their C<ev_loop_xxx> counterparts: |