… | |
… | |
480 | unblocking the signals. |
480 | unblocking the signals. |
481 | |
481 | |
482 | 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 |
483 | C<sigprocmask>, whose behaviour is officially unspecified. |
483 | C<sigprocmask>, whose behaviour is officially unspecified. |
484 | |
484 | |
485 | 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. |
486 | |
495 | |
487 | =item C<EVBACKEND_SELECT> (value 1, portable select backend) |
496 | =item C<EVBACKEND_SELECT> (value 1, portable select backend) |
488 | |
497 | |
489 | 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 |
490 | 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, |
… | |
… | |
1209 | 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 |
1210 | *) >>), 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 |
1211 | corresponding stop function (C<< ev_TYPE_stop (loop, watcher *) >>. |
1220 | corresponding stop function (C<< ev_TYPE_stop (loop, watcher *) >>. |
1212 | |
1221 | |
1213 | 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 |
1214 | 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 |
1215 | 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. |
1216 | |
1226 | |
1217 | 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 |
1218 | 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 |
1219 | third argument. |
1229 | third argument. |
1220 | |
1230 | |
… | |
… | |
1535 | |
1545 | |
1536 | Many event loops support I<watcher priorities>, which are usually small |
1546 | Many event loops support I<watcher priorities>, which are usually small |
1537 | integers that influence the ordering of event callback invocation |
1547 | integers that influence the ordering of event callback invocation |
1538 | between watchers in some way, all else being equal. |
1548 | between watchers in some way, all else being equal. |
1539 | |
1549 | |
1540 | In libev, Watcher priorities can be set using C<ev_set_priority>. See its |
1550 | In libev, watcher priorities can be set using C<ev_set_priority>. See its |
1541 | description for the more technical details such as the actual priority |
1551 | description for the more technical details such as the actual priority |
1542 | range. |
1552 | range. |
1543 | |
1553 | |
1544 | There are two common ways how these these priorities are being interpreted |
1554 | There are two common ways how these these priorities are being interpreted |
1545 | by event loops: |
1555 | by event loops: |
… | |
… | |
1639 | |
1649 | |
1640 | This section describes each watcher in detail, but will not repeat |
1650 | This section describes each watcher in detail, but will not repeat |
1641 | information given in the last section. Any initialisation/set macros, |
1651 | information given in the last section. Any initialisation/set macros, |
1642 | functions and members specific to the watcher type are explained. |
1652 | functions and members specific to the watcher type are explained. |
1643 | |
1653 | |
1644 | Members are additionally marked with either I<[read-only]>, meaning that, |
1654 | Most members are additionally marked with either I<[read-only]>, meaning |
1645 | while the watcher is active, you can look at the member and expect some |
1655 | that, while the watcher is active, you can look at the member and expect |
1646 | sensible content, but you must not modify it (you can modify it while the |
1656 | some sensible content, but you must not modify it (you can modify it while |
1647 | watcher is stopped to your hearts content), or I<[read-write]>, which |
1657 | the watcher is stopped to your hearts content), or I<[read-write]>, which |
1648 | means you can expect it to have some sensible content while the watcher |
1658 | means you can expect it to have some sensible content while the watcher |
1649 | is active, but you can also modify it. Modifying it may not do something |
1659 | is active, but you can also modify it. Modifying it may not do something |
1650 | sensible or take immediate effect (or do anything at all), but libev will |
1660 | sensible or take immediate effect (or do anything at all), but libev will |
1651 | not crash or malfunction in any way. |
1661 | not crash or malfunction in any way. |
1652 | |
1662 | |
|
|
1663 | In any case, the documentation for each member will explain what the |
|
|
1664 | effects are, and if there are any additional access restrictions. |
1653 | |
1665 | |
1654 | =head2 C<ev_io> - is this file descriptor readable or writable? |
1666 | =head2 C<ev_io> - is this file descriptor readable or writable? |
1655 | |
1667 | |
1656 | I/O watchers check whether a file descriptor is readable or writable |
1668 | I/O watchers check whether a file descriptor is readable or writable |
1657 | in each iteration of the event loop, or, more precisely, when reading |
1669 | in each iteration of the event loop, or, more precisely, when reading |
… | |
… | |
1817 | =item ev_io_init (ev_io *, callback, int fd, int events) |
1829 | =item ev_io_init (ev_io *, callback, int fd, int events) |
1818 | |
1830 | |
1819 | =item ev_io_set (ev_io *, int fd, int events) |
1831 | =item ev_io_set (ev_io *, int fd, int events) |
1820 | |
1832 | |
1821 | Configures an C<ev_io> watcher. The C<fd> is the file descriptor to |
1833 | Configures an C<ev_io> watcher. The C<fd> is the file descriptor to |
1822 | receive events for and C<events> is either C<EV_READ>, C<EV_WRITE> or |
1834 | receive events for and C<events> is either C<EV_READ>, C<EV_WRITE>, both |
1823 | C<EV_READ | EV_WRITE>, to express the desire to receive the given events. |
1835 | C<EV_READ | EV_WRITE> or C<0>, to express the desire to receive the given |
|
|
1836 | events. |
1824 | |
1837 | |
1825 | =item int fd [read-only] |
1838 | Note that setting the C<events> to C<0> and starting the watcher is |
|
|
1839 | supported, but not specially optimized - if your program sometimes happens |
|
|
1840 | to generate this combination this is fine, but if it is easy to avoid |
|
|
1841 | starting an io watcher watching for no events you should do so. |
1826 | |
1842 | |
1827 | The file descriptor being watched. |
1843 | =item ev_io_modify (ev_io *, int events) |
1828 | |
1844 | |
|
|
1845 | Similar to C<ev_io_set>, but only changes the event mask. Using this might |
|
|
1846 | be faster with some backends, as libev can assume that the C<fd> still |
|
|
1847 | refers to the same underlying file description, something it cannot do |
|
|
1848 | when using C<ev_io_set>. |
|
|
1849 | |
|
|
1850 | =item int fd [no-modify] |
|
|
1851 | |
|
|
1852 | The file descriptor being watched. While it can be read at any time, you |
|
|
1853 | must not modify this member even when the watcher is stopped - always use |
|
|
1854 | C<ev_io_set> for that. |
|
|
1855 | |
1829 | =item int events [read-only] |
1856 | =item int events [no-modify] |
1830 | |
1857 | |
1831 | The events being watched. |
1858 | The set of events the fd is being watched for, among other flags. Remember |
|
|
1859 | that this is a bit set - to test for C<EV_READ>, use C<< w->events & |
|
|
1860 | EV_READ >>, and similarly for C<EV_WRITE>. |
|
|
1861 | |
|
|
1862 | As with C<fd>, you must not modify this member even when the watcher is |
|
|
1863 | stopped, always use C<ev_io_set> or C<ev_io_modify> for that. |
1832 | |
1864 | |
1833 | =back |
1865 | =back |
1834 | |
1866 | |
1835 | =head3 Examples |
1867 | =head3 Examples |
1836 | |
1868 | |
… | |
… | |
4234 | method. |
4266 | method. |
4235 | |
4267 | |
4236 | For C<ev::embed> watchers this method is called C<set_embed>, to avoid |
4268 | For C<ev::embed> watchers this method is called C<set_embed>, to avoid |
4237 | clashing with the C<set (loop)> method. |
4269 | clashing with the C<set (loop)> method. |
4238 | |
4270 | |
|
|
4271 | For C<ev::io> watchers there is an additional C<set> method that acepts a |
|
|
4272 | new event mask only, and internally calls C<ev_io_modfify>. |
|
|
4273 | |
4239 | =item w->start () |
4274 | =item w->start () |
4240 | |
4275 | |
4241 | Starts the watcher. Note that there is no C<loop> argument, as the |
4276 | Starts the watcher. Note that there is no C<loop> argument, as the |
4242 | constructor already stores the event loop. |
4277 | constructor already stores the event loop. |
4243 | |
4278 | |
… | |
… | |
4606 | |
4641 | |
4607 | =item EV_USE_NANOSLEEP |
4642 | =item EV_USE_NANOSLEEP |
4608 | |
4643 | |
4609 | If defined to be C<1>, libev will assume that C<nanosleep ()> is available |
4644 | If defined to be C<1>, libev will assume that C<nanosleep ()> is available |
4610 | and will use it for delays. Otherwise it will use C<select ()>. |
4645 | and will use it for delays. Otherwise it will use C<select ()>. |
|
|
4646 | |
|
|
4647 | =item EV_USE_EVENTFD |
|
|
4648 | |
|
|
4649 | If defined to be C<1>, then libev will assume that C<eventfd ()> is |
|
|
4650 | available and will probe for kernel support at runtime. This will improve |
|
|
4651 | C<ev_signal> and C<ev_async> performance and reduce resource consumption. |
|
|
4652 | If undefined, it will be enabled if the headers indicate GNU/Linux + Glibc |
|
|
4653 | 2.7 or newer, otherwise disabled. |
|
|
4654 | |
|
|
4655 | =item EV_USE_SIGNALFD |
|
|
4656 | |
|
|
4657 | If defined to be C<1>, then libev will assume that C<signalfd ()> is |
|
|
4658 | available and will probe for kernel support at runtime. This enables |
|
|
4659 | the use of EVFLAG_SIGNALFD for faster and simpler signal handling. If |
|
|
4660 | undefined, it will be enabled if the headers indicate GNU/Linux + Glibc |
|
|
4661 | 2.7 or newer, otherwise disabled. |
|
|
4662 | |
|
|
4663 | =item EV_USE_TIMERFD |
|
|
4664 | |
|
|
4665 | If defined to be C<1>, then libev will assume that C<timerfd ()> is |
|
|
4666 | available and will probe for kernel support at runtime. This allows |
|
|
4667 | libev to detect time jumps accurately. If undefined, it will be enabled |
|
|
4668 | if the headers indicate GNU/Linux + Glibc 2.8 or newer and define |
|
|
4669 | C<TFD_TIMER_CANCEL_ON_SET>, otherwise disabled. |
4611 | |
4670 | |
4612 | =item EV_USE_EVENTFD |
4671 | =item EV_USE_EVENTFD |
4613 | |
4672 | |
4614 | If defined to be C<1>, then libev will assume that C<eventfd ()> is |
4673 | If defined to be C<1>, then libev will assume that C<eventfd ()> is |
4615 | available and will probe for kernel support at runtime. This will improve |
4674 | available and will probe for kernel support at runtime. This will improve |