… | |
… | |
131 | .\} |
131 | .\} |
132 | .rm #[ #] #H #V #F C |
132 | .rm #[ #] #H #V #F C |
133 | .\" ======================================================================== |
133 | .\" ======================================================================== |
134 | .\" |
134 | .\" |
135 | .IX Title "LIBEV 3" |
135 | .IX Title "LIBEV 3" |
136 | .TH LIBEV 3 "2019-06-24" "libev-4.25" "libev - high performance full featured event loop" |
136 | .TH LIBEV 3 "2019-06-25" "libev-4.25" "libev - high performance full featured event loop" |
137 | .\" For nroff, turn off justification. Always turn off hyphenation; it makes |
137 | .\" For nroff, turn off justification. Always turn off hyphenation; it makes |
138 | .\" way too many mistakes in technical documents. |
138 | .\" way too many mistakes in technical documents. |
139 | .if n .ad l |
139 | .if n .ad l |
140 | .nh |
140 | .nh |
141 | .SH "NAME" |
141 | .SH "NAME" |
… | |
… | |
291 | When libev detects a usage error such as a negative timer interval, then |
291 | When libev detects a usage error such as a negative timer interval, then |
292 | it will print a diagnostic message and abort (via the \f(CW\*(C`assert\*(C'\fR mechanism, |
292 | it will print a diagnostic message and abort (via the \f(CW\*(C`assert\*(C'\fR mechanism, |
293 | so \f(CW\*(C`NDEBUG\*(C'\fR will disable this checking): these are programming errors in |
293 | so \f(CW\*(C`NDEBUG\*(C'\fR will disable this checking): these are programming errors in |
294 | the libev caller and need to be fixed there. |
294 | the libev caller and need to be fixed there. |
295 | .PP |
295 | .PP |
|
|
296 | Via the \f(CW\*(C`EV_FREQUENT\*(C'\fR macro you can compile in and/or enable extensive |
|
|
297 | consistency checking code inside libev that can be used to check for |
|
|
298 | internal inconsistencies, suually caused by application bugs. |
|
|
299 | .PP |
296 | Libev also has a few internal error-checking \f(CW\*(C`assert\*(C'\fRions, and also has |
300 | Libev also has a few internal error-checking \f(CW\*(C`assert\*(C'\fRions. These do not |
297 | extensive consistency checking code. These do not trigger under normal |
|
|
298 | circumstances, as they indicate either a bug in libev or worse. |
301 | trigger under normal circumstances, as they indicate either a bug in libev |
|
|
302 | or worse. |
299 | .SH "GLOBAL FUNCTIONS" |
303 | .SH "GLOBAL FUNCTIONS" |
300 | .IX Header "GLOBAL FUNCTIONS" |
304 | .IX Header "GLOBAL FUNCTIONS" |
301 | These functions can be called anytime, even before initialising the |
305 | These functions can be called anytime, even before initialising the |
302 | library in any way. |
306 | library in any way. |
303 | .IP "ev_tstamp ev_time ()" 4 |
307 | .IP "ev_tstamp ev_time ()" 4 |
… | |
… | |
638 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR to \f(CW\*(C`POLLIN | POLLERR | POLLHUP\*(C'\fR, and |
642 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR to \f(CW\*(C`POLLIN | POLLERR | POLLHUP\*(C'\fR, and |
639 | \&\f(CW\*(C`EV_WRITE\*(C'\fR to \f(CW\*(C`POLLOUT | POLLERR | POLLHUP\*(C'\fR. |
643 | \&\f(CW\*(C`EV_WRITE\*(C'\fR to \f(CW\*(C`POLLOUT | POLLERR | POLLHUP\*(C'\fR. |
640 | .ie n .IP """EVBACKEND_EPOLL"" (value 4, Linux)" 4 |
644 | .ie n .IP """EVBACKEND_EPOLL"" (value 4, Linux)" 4 |
641 | .el .IP "\f(CWEVBACKEND_EPOLL\fR (value 4, Linux)" 4 |
645 | .el .IP "\f(CWEVBACKEND_EPOLL\fR (value 4, Linux)" 4 |
642 | .IX Item "EVBACKEND_EPOLL (value 4, Linux)" |
646 | .IX Item "EVBACKEND_EPOLL (value 4, Linux)" |
643 | Use the linux-specific \fBepoll\fR\|(7) interface (for both pre\- and post\-2.6.9 |
647 | Use the Linux-specific \fBepoll\fR\|(7) interface (for both pre\- and post\-2.6.9 |
644 | kernels). |
648 | kernels). |
645 | .Sp |
649 | .Sp |
646 | For few fds, this backend is a bit little slower than poll and select, but |
650 | For few fds, this backend is a bit little slower than poll and select, but |
647 | it scales phenomenally better. While poll and select usually scale like |
651 | it scales phenomenally better. While poll and select usually scale like |
648 | O(total_fds) where total_fds is the total number of fds (or the highest |
652 | O(total_fds) where total_fds is the total number of fds (or the highest |
… | |
… | |
701 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR and \f(CW\*(C`EV_WRITE\*(C'\fR in the same way as |
705 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR and \f(CW\*(C`EV_WRITE\*(C'\fR in the same way as |
702 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
706 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
703 | .ie n .IP """EVBACKEND_LINUXAIO"" (value 64, Linux)" 4 |
707 | .ie n .IP """EVBACKEND_LINUXAIO"" (value 64, Linux)" 4 |
704 | .el .IP "\f(CWEVBACKEND_LINUXAIO\fR (value 64, Linux)" 4 |
708 | .el .IP "\f(CWEVBACKEND_LINUXAIO\fR (value 64, Linux)" 4 |
705 | .IX Item "EVBACKEND_LINUXAIO (value 64, Linux)" |
709 | .IX Item "EVBACKEND_LINUXAIO (value 64, Linux)" |
706 | Use the linux-specific linux aio (\fInot\fR \f(CWaio(7)\fR but \f(CWio_submit(2)\fR) event interface available in post\-4.18 kernels. |
710 | Use the Linux-specific Linux \s-1AIO\s0 (\fInot\fR \f(CWaio(7)\fR but \f(CWio_submit(2)\fR) event interface available in post\-4.18 kernels (but libev |
|
|
711 | only tries to use it in 4.19+). |
|
|
712 | .Sp |
|
|
713 | This is another Linux train wreck of an event interface. |
707 | .Sp |
714 | .Sp |
708 | If this backend works for you (as of this writing, it was very |
715 | If this backend works for you (as of this writing, it was very |
709 | experimental), it is the best event interface available on linux and might |
716 | experimental), it is the best event interface available on Linux and might |
710 | be well worth enabling it \- if it isn't available in your kernel this will |
717 | be well worth enabling it \- if it isn't available in your kernel this will |
711 | be detected and this backend will be skipped. |
718 | be detected and this backend will be skipped. |
712 | .Sp |
719 | .Sp |
713 | This backend can batch oneshot requests and supports a user-space ring |
720 | This backend can batch oneshot requests and supports a user-space ring |
714 | buffer to receive events. It also doesn't suffer from most of the design |
721 | buffer to receive events. It also doesn't suffer from most of the design |
715 | problems of epoll (such as not being able to remove event sources from the |
722 | problems of epoll (such as not being able to remove event sources from |
716 | epoll set), and generally sounds too good to be true. Because, this being |
723 | the epoll set), and generally sounds too good to be true. Because, this |
717 | the linux kernel, of course it suffers from a whole new set of limitations. |
724 | being the Linux kernel, of course it suffers from a whole new set of |
|
|
725 | limitations, forcing you to fall back to epoll, inheriting all its design |
|
|
726 | issues. |
718 | .Sp |
727 | .Sp |
719 | For one, it is not easily embeddable (but probably could be done using |
728 | For one, it is not easily embeddable (but probably could be done using |
720 | an event fd at some extra overhead). It also is subject to a system wide |
729 | an event fd at some extra overhead). It also is subject to a system wide |
721 | limit that can be configured in \fI/proc/sys/fs/aio\-max\-nr\fR \- each loop |
730 | limit that can be configured in \fI/proc/sys/fs/aio\-max\-nr\fR. If no \s-1AIO\s0 |
722 | currently requires \f(CW61\fR of this number. If no aio requests are left, this |
|
|
723 | backend will be skipped during initialisation. |
731 | requests are left, this backend will be skipped during initialisation, and |
|
|
732 | will switch to epoll when the loop is active. |
724 | .Sp |
733 | .Sp |
725 | Most problematic in practise, however, is that not all file descriptors |
734 | Most problematic in practice, however, is that not all file descriptors |
726 | work with it. For example, in linux 5.1, tcp sockets, pipes, event fds, |
735 | work with it. For example, in Linux 5.1, \s-1TCP\s0 sockets, pipes, event fds, |
727 | files, \fI/dev/null\fR and a few others are supported, but ttys do not work |
736 | files, \fI/dev/null\fR and many others are supported, but ttys do not work |
728 | properly (a known bug that the kernel developers don't care about, see |
737 | properly (a known bug that the kernel developers don't care about, see |
729 | <https://lore.kernel.org/patchwork/patch/1047453/>), so this is not |
738 | <https://lore.kernel.org/patchwork/patch/1047453/>), so this is not |
730 | (yet?) a generic event polling interface. |
739 | (yet?) a generic event polling interface. |
731 | .Sp |
740 | .Sp |
732 | Overall, it seems the linux developers just don't want it to have a |
741 | Overall, it seems the Linux developers just don't want it to have a |
733 | generic event handling mechanism other than \f(CW\*(C`select\*(C'\fR or \f(CW\*(C`poll\*(C'\fR. |
742 | generic event handling mechanism other than \f(CW\*(C`select\*(C'\fR or \f(CW\*(C`poll\*(C'\fR. |
734 | .Sp |
743 | .Sp |
735 | To work around the fd type problem, the current version of libev uses |
744 | To work around all these problem, the current version of libev uses its |
736 | epoll as a fallback for file deescriptor types that do not work. Epoll |
745 | epoll backend as a fallback for file descriptor types that do not work. Or |
737 | is used in, kind of, slow mode that hopefully avoids most of its design |
746 | falls back completely to epoll if the kernel acts up. |
738 | problems and requires 1\-3 extra syscalls per active fd every iteration. |
|
|
739 | .Sp |
747 | .Sp |
740 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR and \f(CW\*(C`EV_WRITE\*(C'\fR in the same way as |
748 | This backend maps \f(CW\*(C`EV_READ\*(C'\fR and \f(CW\*(C`EV_WRITE\*(C'\fR in the same way as |
741 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
749 | \&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR. |
742 | .ie n .IP """EVBACKEND_KQUEUE"" (value 8, most \s-1BSD\s0 clones)" 4 |
750 | .ie n .IP """EVBACKEND_KQUEUE"" (value 8, most \s-1BSD\s0 clones)" 4 |
743 | .el .IP "\f(CWEVBACKEND_KQUEUE\fR (value 8, most \s-1BSD\s0 clones)" 4 |
751 | .el .IP "\f(CWEVBACKEND_KQUEUE\fR (value 8, most \s-1BSD\s0 clones)" 4 |
744 | .IX Item "EVBACKEND_KQUEUE (value 8, most BSD clones)" |
752 | .IX Item "EVBACKEND_KQUEUE (value 8, most BSD clones)" |
745 | Kqueue deserves special mention, as at the time of this writing, it |
753 | Kqueue deserves special mention, as at the time this backend was |
746 | was broken on all BSDs except NetBSD (usually it doesn't work reliably |
754 | implemented, it was broken on all BSDs except NetBSD (usually it doesn't |
747 | with anything but sockets and pipes, except on Darwin, where of course |
755 | work reliably with anything but sockets and pipes, except on Darwin, |
748 | it's completely useless). Unlike epoll, however, whose brokenness |
756 | where of course it's completely useless). Unlike epoll, however, whose |
749 | is by design, these kqueue bugs can (and eventually will) be fixed |
757 | brokenness is by design, these kqueue bugs can be (and mostly have been) |
750 | without \s-1API\s0 changes to existing programs. For this reason it's not being |
758 | fixed without \s-1API\s0 changes to existing programs. For this reason it's not |
751 | \&\*(L"auto-detected\*(R" unless you explicitly specify it in the flags (i.e. using |
759 | being \*(L"auto-detected\*(R" on all platforms unless you explicitly specify it |
752 | \&\f(CW\*(C`EVBACKEND_KQUEUE\*(C'\fR) or libev was compiled on a known-to-be-good (\-enough) |
760 | in the flags (i.e. using \f(CW\*(C`EVBACKEND_KQUEUE\*(C'\fR) or libev was compiled on a |
753 | system like NetBSD. |
761 | known-to-be-good (\-enough) system like NetBSD. |
754 | .Sp |
762 | .Sp |
755 | You still can embed kqueue into a normal poll or select backend and use it |
763 | You still can embed kqueue into a normal poll or select backend and use it |
756 | only for sockets (after having made sure that sockets work with kqueue on |
764 | only for sockets (after having made sure that sockets work with kqueue on |
757 | the target platform). See \f(CW\*(C`ev_embed\*(C'\fR watchers for more info. |
765 | the target platform). See \f(CW\*(C`ev_embed\*(C'\fR watchers for more info. |
758 | .Sp |
766 | .Sp |
759 | It scales in the same way as the epoll backend, but the interface to the |
767 | It scales in the same way as the epoll backend, but the interface to the |
760 | kernel is more efficient (which says nothing about its actual speed, of |
768 | kernel is more efficient (which says nothing about its actual speed, of |
761 | course). While stopping, setting and starting an I/O watcher does never |
769 | course). While stopping, setting and starting an I/O watcher does never |
762 | cause an extra system call as with \f(CW\*(C`EVBACKEND_EPOLL\*(C'\fR, it still adds up to |
770 | cause an extra system call as with \f(CW\*(C`EVBACKEND_EPOLL\*(C'\fR, it still adds up to |
763 | two event changes per incident. Support for \f(CW\*(C`fork ()\*(C'\fR is very bad (you |
771 | two event changes per incident. Support for \f(CW\*(C`fork ()\*(C'\fR is very bad (you |
764 | might have to leak fd's on fork, but it's more sane than epoll) and it |
772 | might have to leak fds on fork, but it's more sane than epoll) and it |
765 | drops fds silently in similarly hard-to-detect cases. |
773 | drops fds silently in similarly hard-to-detect cases. |
766 | .Sp |
774 | .Sp |
767 | This backend usually performs well under most conditions. |
775 | This backend usually performs well under most conditions. |
768 | .Sp |
776 | .Sp |
769 | While nominally embeddable in other event loops, this doesn't work |
777 | While nominally embeddable in other event loops, this doesn't work |
… | |
… | |
5078 | called. If set to \f(CW2\fR, then the internal verification code will be |
5086 | called. If set to \f(CW2\fR, then the internal verification code will be |
5079 | called once per loop, which can slow down libev. If set to \f(CW3\fR, then the |
5087 | called once per loop, which can slow down libev. If set to \f(CW3\fR, then the |
5080 | verification code will be called very frequently, which will slow down |
5088 | verification code will be called very frequently, which will slow down |
5081 | libev considerably. |
5089 | libev considerably. |
5082 | .Sp |
5090 | .Sp |
|
|
5091 | Verification errors are reported via C's \f(CW\*(C`assert\*(C'\fR mechanism, so if you |
|
|
5092 | disable that (e.g. by defining \f(CW\*(C`NDEBUG\*(C'\fR) then no errors will be reported. |
|
|
5093 | .Sp |
5083 | The default is \f(CW1\fR, unless \f(CW\*(C`EV_FEATURES\*(C'\fR overrides it, in which case it |
5094 | The default is \f(CW1\fR, unless \f(CW\*(C`EV_FEATURES\*(C'\fR overrides it, in which case it |
5084 | will be \f(CW0\fR. |
5095 | will be \f(CW0\fR. |
5085 | .IP "\s-1EV_COMMON\s0" 4 |
5096 | .IP "\s-1EV_COMMON\s0" 4 |
5086 | .IX Item "EV_COMMON" |
5097 | .IX Item "EV_COMMON" |
5087 | By default, all watchers have a \f(CW\*(C`void *data\*(C'\fR member. By redefining |
5098 | By default, all watchers have a \f(CW\*(C`void *data\*(C'\fR member. By redefining |