| 1 | Revision history for libev, a high-performance and full-featured event loop. |
1 | Revision history for libev, a high-performance and full-featured event loop. |
| 2 | |
2 | |
| 3 | TODO: revisit 59.x timer in the light of modern powersaving |
3 | TODO: revisit 59.x timer in the light of modern powersaving |
| 4 | TODO: maybe use timerfd to detect time jumps on linux |
4 | TODO: ^ maybe just increase it when timerfd, modern linux only thing that counts? |
| 5 | TODO: document EV_TSTAMP_T |
5 | TODO: document EV_TSTAMP_T |
|
|
6 | TODO: for next ABI/API change, consider moving EV__IOFDSSET into io->fd instead and provide a getter. |
| 6 | |
7 | |
| 7 | 4.29 |
8 | TODO: maybe allow events = 0 for io watchers |
|
|
9 | - the 4.31 timerfd code wrongly changes the priority of the signal |
|
|
10 | fd watcher, which is usually harmless unless signal fds are |
|
|
11 | also used (found via cpan tester service). |
|
|
12 | - the documentation wrongly claimed that user may modify fd and events |
|
|
13 | members in io watchers when the wqatcher was stopped |
|
|
14 | (found by b_jonas). |
|
|
15 | - new ev_io_modify mutator which changes only the events member, |
|
|
16 | which cna be faster. |
|
|
17 | - do not wake up every minute when timerfd is used to detect timejumps. |
|
|
18 | - support a lot more "uncommon" compile time configurations, |
|
|
19 | such as ev_embed enabled but ev_timer disabled. |
|
|
20 | - the linux aio backend is no longer compiled in by default. |
|
|
21 | - update to libecb version 0x00010008. |
|
|
22 | |
|
|
23 | 4.31 Fri Dec 20 21:58:29 CET 2019 |
|
|
24 | - handle backends with minimum wait time a bit better by not |
|
|
25 | waiting in the presence of already-expired timers |
|
|
26 | (behaviour reported by Felipe Gasper). |
|
|
27 | - new feature: use timerfd to detect timejumps quickly, |
|
|
28 | can be disabled with the new EVFLAG_NOTIMERFD loop flag. |
|
|
29 | - document EV_USE_SIGNALFD feature macro. |
|
|
30 | |
|
|
31 | 4.30 (EV only) |
|
|
32 | - change non-autoconf test for __kernel_rwf_t by testing |
|
|
33 | LINUX_VERSION_CODE, the most direct test I could find. |
|
|
34 | - fix a bug in the io_uring backend that polled the wrong |
|
|
35 | backend fd, causing it to not work in many cases. |
|
|
36 | |
|
|
37 | 4.29 (EV only) |
| 8 | - (libev) add io uring autoconf and non-autoconf detection, |
38 | - add io uring autoconf and non-autoconf detection. |
| 9 | the latter of which should disable io_uring compilation |
39 | - disable io_uring when some header files are too old. |
| 10 | on old systems. |
|
|
| 11 | |
40 | |
| 12 | 4.28 (EV only) |
41 | 4.28 (EV only) |
| 13 | - linuxaio backend resulted in random memory corruption |
42 | - linuxaio backend resulted in random memory corruption |
| 14 | when loop is forked. |
43 | when loop is forked. |
| 15 | - linuxaio backend might have tried to cancel an iocb |
44 | - linuxaio backend might have tried to cancel an iocb |
