… | |
… | |
105 | details of the event, and then hand it over to libev by I<starting> the |
105 | details of the event, and then hand it over to libev by I<starting> the |
106 | watcher. |
106 | watcher. |
107 | |
107 | |
108 | =head2 FEATURES |
108 | =head2 FEATURES |
109 | |
109 | |
110 | Libev supports C<select>, C<poll>, the Linux-specific C<epoll>, the |
110 | Libev supports C<select>, C<poll>, the Linux-specific aio and C<epoll> |
111 | BSD-specific C<kqueue> and the Solaris-specific event port mechanisms |
111 | interfaces, the BSD-specific C<kqueue> and the Solaris-specific event port |
112 | for file descriptor events (C<ev_io>), the Linux C<inotify> interface |
112 | mechanisms for file descriptor events (C<ev_io>), the Linux C<inotify> |
113 | (for C<ev_stat>), Linux eventfd/signalfd (for faster and cleaner |
113 | interface (for C<ev_stat>), Linux eventfd/signalfd (for faster and cleaner |
114 | inter-thread wakeup (C<ev_async>)/signal handling (C<ev_signal>)) relative |
114 | inter-thread wakeup (C<ev_async>)/signal handling (C<ev_signal>)) relative |
115 | timers (C<ev_timer>), absolute timers with customised rescheduling |
115 | timers (C<ev_timer>), absolute timers with customised rescheduling |
116 | (C<ev_periodic>), synchronous signals (C<ev_signal>), process status |
116 | (C<ev_periodic>), synchronous signals (C<ev_signal>), process status |
117 | change events (C<ev_child>), and event watchers dealing with the event |
117 | change events (C<ev_child>), and event watchers dealing with the event |
118 | loop mechanism itself (C<ev_idle>, C<ev_embed>, C<ev_prepare> and |
118 | loop mechanism itself (C<ev_idle>, C<ev_embed>, C<ev_prepare> and |
… | |
… | |
567 | All this means that, in practice, C<EVBACKEND_SELECT> can be as fast or |
567 | All this means that, in practice, C<EVBACKEND_SELECT> can be as fast or |
568 | faster than epoll for maybe up to a hundred file descriptors, depending on |
568 | faster than epoll for maybe up to a hundred file descriptors, depending on |
569 | the usage. So sad. |
569 | the usage. So sad. |
570 | |
570 | |
571 | While nominally embeddable in other event loops, this feature is broken in |
571 | While nominally embeddable in other event loops, this feature is broken in |
572 | all kernel versions tested so far. |
572 | a lot of kernel revisions, but probably(!) works in current versions. |
|
|
573 | |
|
|
574 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
|
|
575 | C<EVBACKEND_POLL>. |
|
|
576 | |
|
|
577 | =item C<EVBACKEND_LINUXAIO> (value 64, Linux) |
|
|
578 | |
|
|
579 | Use the linux-specific linux aio (I<not> C<< aio(7) >> but C<< |
|
|
580 | io_submit(2) >>) event interface available in post-4.18 kernels. |
|
|
581 | |
|
|
582 | If this backend works for you (as of this writing, it was very |
|
|
583 | experimental), it is the best event interface available on linux and might |
|
|
584 | be well worth enabling it - if it isn't available in your kernel this will |
|
|
585 | be detected and this backend will be skipped. |
|
|
586 | |
|
|
587 | This backend can batch oneshot requests and supports a user-space ring |
|
|
588 | buffer to receive events. It also doesn't suffer from most of the design |
|
|
589 | problems of epoll (such as not being able to remove event sources from |
|
|
590 | the epoll set), and generally sounds too good to be true. Because, this |
|
|
591 | being the linux kernel, of course it suffers from a whole new set of |
|
|
592 | limitations. |
|
|
593 | |
|
|
594 | For one, it is not easily embeddable (but probably could be done using |
|
|
595 | an event fd at some extra overhead). It also is subject to a system wide |
|
|
596 | limit that can be configured in F</proc/sys/fs/aio-max-nr> - each loop |
|
|
597 | currently requires C<61> of this number. If no aio requests are left, this |
|
|
598 | backend will be skipped during initialisation. |
|
|
599 | |
|
|
600 | Most problematic in practise, however, is that not all file descriptors |
|
|
601 | work with it. For example, in linux 5.1, tcp sockets, pipes, event fds, |
|
|
602 | files, F</dev/null> and a few others are supported, but ttys do not work |
|
|
603 | (probably because of a bug), so this is not (yet?) a generic event polling |
|
|
604 | interface. |
|
|
605 | |
|
|
606 | To work around this latter problem, the current version of libev uses |
|
|
607 | epoll as a fallback for file deescriptor types that do not work. Epoll |
|
|
608 | is used in, kind of, slow mode that hopefully avoids most of its design |
|
|
609 | problems. |
573 | |
610 | |
574 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
611 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
575 | C<EVBACKEND_POLL>. |
612 | C<EVBACKEND_POLL>. |
576 | |
613 | |
577 | =item C<EVBACKEND_KQUEUE> (value 8, most BSD clones) |
614 | =item C<EVBACKEND_KQUEUE> (value 8, most BSD clones) |
… | |
… | |
677 | |
714 | |
678 | Example: Use whatever libev has to offer, but make sure that kqueue is |
715 | Example: Use whatever libev has to offer, but make sure that kqueue is |
679 | used if available. |
716 | used if available. |
680 | |
717 | |
681 | struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_KQUEUE); |
718 | struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_KQUEUE); |
|
|
719 | |
|
|
720 | Example: Similarly, on linux, you mgiht want to take advantage of the |
|
|
721 | linux aio backend if possible, but fall back to something else if that |
|
|
722 | isn't available. |
|
|
723 | |
|
|
724 | struct ev_loop *loop = ev_loop_new (ev_recommended_backends () | EVBACKEND_LINUXAIO); |
682 | |
725 | |
683 | =item ev_loop_destroy (loop) |
726 | =item ev_loop_destroy (loop) |
684 | |
727 | |
685 | Destroys an event loop object (frees all memory and kernel state |
728 | Destroys an event loop object (frees all memory and kernel state |
686 | etc.). None of the active event watchers will be stopped in the normal |
729 | etc.). None of the active event watchers will be stopped in the normal |
… | |
… | |
1630 | |
1673 | |
1631 | But really, best use non-blocking mode. |
1674 | But really, best use non-blocking mode. |
1632 | |
1675 | |
1633 | =head3 The special problem of disappearing file descriptors |
1676 | =head3 The special problem of disappearing file descriptors |
1634 | |
1677 | |
1635 | Some backends (e.g. kqueue, epoll) need to be told about closing a file |
1678 | Some backends (e.g. kqueue, epoll, linuxaio) need to be told about closing |
1636 | descriptor (either due to calling C<close> explicitly or any other means, |
1679 | a file descriptor (either due to calling C<close> explicitly or any other |
1637 | such as C<dup2>). The reason is that you register interest in some file |
1680 | means, such as C<dup2>). The reason is that you register interest in some |
1638 | descriptor, but when it goes away, the operating system will silently drop |
1681 | file descriptor, but when it goes away, the operating system will silently |
1639 | this interest. If another file descriptor with the same number then is |
1682 | drop this interest. If another file descriptor with the same number then |
1640 | registered with libev, there is no efficient way to see that this is, in |
1683 | is registered with libev, there is no efficient way to see that this is, |
1641 | fact, a different file descriptor. |
1684 | in fact, a different file descriptor. |
1642 | |
1685 | |
1643 | To avoid having to explicitly tell libev about such cases, libev follows |
1686 | To avoid having to explicitly tell libev about such cases, libev follows |
1644 | the following policy: Each time C<ev_io_set> is being called, libev |
1687 | the following policy: Each time C<ev_io_set> is being called, libev |
1645 | will assume that this is potentially a new file descriptor, otherwise |
1688 | will assume that this is potentially a new file descriptor, otherwise |
1646 | it is assumed that the file descriptor stays the same. That means that |
1689 | it is assumed that the file descriptor stays the same. That means that |
… | |
… | |
1695 | when you rarely read from a file instead of from a socket, and want to |
1738 | when you rarely read from a file instead of from a socket, and want to |
1696 | reuse the same code path. |
1739 | reuse the same code path. |
1697 | |
1740 | |
1698 | =head3 The special problem of fork |
1741 | =head3 The special problem of fork |
1699 | |
1742 | |
1700 | Some backends (epoll, kqueue) do not support C<fork ()> at all or exhibit |
1743 | Some backends (epoll, kqueue, probably linuxaio) do not support C<fork ()> |
1701 | useless behaviour. Libev fully supports fork, but needs to be told about |
1744 | at all or exhibit useless behaviour. Libev fully supports fork, but needs |
1702 | it in the child if you want to continue to use it in the child. |
1745 | to be told about it in the child if you want to continue to use it in the |
|
|
1746 | child. |
1703 | |
1747 | |
1704 | To support fork in your child processes, you have to call C<ev_loop_fork |
1748 | To support fork in your child processes, you have to call C<ev_loop_fork |
1705 | ()> after a fork in the child, enable C<EVFLAG_FORKCHECK>, or resort to |
1749 | ()> after a fork in the child, enable C<EVFLAG_FORKCHECK>, or resort to |
1706 | C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>. |
1750 | C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>. |
1707 | |
1751 | |
… | |
… | |
4428 | ev_win32.c required on win32 platforms only |
4472 | ev_win32.c required on win32 platforms only |
4429 | |
4473 | |
4430 | ev_select.c only when select backend is enabled |
4474 | ev_select.c only when select backend is enabled |
4431 | ev_poll.c only when poll backend is enabled |
4475 | ev_poll.c only when poll backend is enabled |
4432 | ev_epoll.c only when the epoll backend is enabled |
4476 | ev_epoll.c only when the epoll backend is enabled |
|
|
4477 | ev_linuxaio.c only when the linux aio backend is enabled |
4433 | ev_kqueue.c only when the kqueue backend is enabled |
4478 | ev_kqueue.c only when the kqueue backend is enabled |
4434 | ev_port.c only when the solaris port backend is enabled |
4479 | ev_port.c only when the solaris port backend is enabled |
4435 | |
4480 | |
4436 | F<ev.c> includes the backend files directly when enabled, so you only need |
4481 | F<ev.c> includes the backend files directly when enabled, so you only need |
4437 | to compile this single file. |
4482 | to compile this single file. |
… | |
… | |
4627 | If defined to be C<1>, libev will compile in support for the Linux |
4672 | If defined to be C<1>, libev will compile in support for the Linux |
4628 | C<epoll>(7) backend. Its availability will be detected at runtime, |
4673 | C<epoll>(7) backend. Its availability will be detected at runtime, |
4629 | otherwise another method will be used as fallback. This is the preferred |
4674 | otherwise another method will be used as fallback. This is the preferred |
4630 | backend for GNU/Linux systems. If undefined, it will be enabled if the |
4675 | backend for GNU/Linux systems. If undefined, it will be enabled if the |
4631 | headers indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
4676 | headers indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled. |
|
|
4677 | |
|
|
4678 | =item EV_USE_LINUXAIO |
|
|
4679 | |
|
|
4680 | If defined to be C<1>, libev will compile in support for the Linux |
|
|
4681 | aio backend. Due to it's currenbt limitations it has to be requested |
|
|
4682 | explicitly. If undefined, it will be enabled on linux, otherwise |
|
|
4683 | disabled. |
4632 | |
4684 | |
4633 | =item EV_USE_KQUEUE |
4685 | =item EV_USE_KQUEUE |
4634 | |
4686 | |
4635 | If defined to be C<1>, libev will compile in support for the BSD style |
4687 | If defined to be C<1>, libev will compile in support for the BSD style |
4636 | C<kqueue>(2) backend. Its actual availability will be detected at runtime, |
4688 | C<kqueue>(2) backend. Its actual availability will be detected at runtime, |