| … | |
… | |
| 574 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
574 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
| 575 | C<EVBACKEND_POLL>. |
575 | C<EVBACKEND_POLL>. |
| 576 | |
576 | |
| 577 | =item C<EVBACKEND_LINUXAIO> (value 64, Linux) |
577 | =item C<EVBACKEND_LINUXAIO> (value 64, Linux) |
| 578 | |
578 | |
| 579 | Use the linux-specific linux aio (I<not> C<< aio(7) >>) event interface |
579 | Use the linux-specific linux aio (I<not> C<< aio(7) >> but C<< |
| 580 | available in post-4.18 kernels. |
580 | io_submit(2) >>) event interface available in post-4.18 kernels. |
| 581 | |
581 | |
| 582 | If this backend works for you (as of this writing, it was very |
582 | If this backend works for you (as of this writing, it was very |
| 583 | experimental and only supports a subset of file types), it is the best |
583 | experimental), it is the best event interface available on linux and might |
| 584 | event interface available on linux and might be well worth it enabling it |
584 | be well worth enabling it - if it isn't available in your kernel this will |
| 585 | - if it isn't available in your kernel this will be detected and another |
585 | be detected and this backend will be skipped. |
| 586 | backend will be chosen. |
|
|
| 587 | |
586 | |
| 588 | This backend can batch oneshot requests and uses a user-space ring buffer |
587 | This backend can batch oneshot requests and supports a user-space ring |
| 589 | to receive events. It also doesn't suffer from most of the design problems |
588 | buffer to receive events. It also doesn't suffer from most of the design |
| 590 | of epoll (such as not being able to remove event sources from the epoll |
589 | problems of epoll (such as not being able to remove event sources from |
| 591 | set), and generally sounds too good to be true. Because, this being the |
590 | the epoll set), and generally sounds too good to be true. Because, this |
| 592 | linux kernel, of course it suffers from a whole new set of limitations. |
591 | being the linux kernel, of course it suffers from a whole new set of |
|
|
592 | limitations. |
| 593 | |
593 | |
| 594 | For one, it is not easily embeddable (but probably could be done using |
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 various |
595 | an event fd at some extra overhead). It also is subject to a system wide |
| 596 | arbitrary limits that can be configured in F</proc/sys/fs/aio-max-nr> |
596 | limit that can be configured in F</proc/sys/fs/aio-max-nr> - each loop |
| 597 | and F</proc/sys/fs/aio-nr>), which could lead to it being skipped during |
597 | currently requires C<61> of this number. If no aio requests are left, this |
| 598 | initialisation. |
598 | backend will be skipped during initialisation. |
| 599 | |
599 | |
| 600 | Most problematic in practise, however, is that, like kqueue, it requires |
600 | Most problematic in practise, however, is that not all file descriptors |
| 601 | special support from drivers, and, not surprisingly, not all drivers |
|
|
| 602 | implement it. For example, in linux 4.19, tcp sockets, pipes, event fds, |
601 | work with it. For example, in linux 5.1, tcp sockets, pipes, event fds, |
| 603 | files, F</dev/null> and a few others are supported, but ttys are not, so |
602 | files, F</dev/null> and a few others are supported, but ttys do not work |
| 604 | this is not (yet?) a generic event polling interface but is probably still |
603 | (probably because of a bug), so this is not (yet?) a generic event polling |
| 605 | be very useful in a web server or similar program. |
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. |
| 606 | |
610 | |
| 607 | 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 |
| 608 | C<EVBACKEND_POLL>. |
612 | C<EVBACKEND_POLL>. |
| 609 | |
613 | |
| 610 | =item C<EVBACKEND_KQUEUE> (value 8, most BSD clones) |
614 | =item C<EVBACKEND_KQUEUE> (value 8, most BSD clones) |
