| 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 | |
|
|
7 | TODO: add ev_io_set_events, or ev_io_modify, or ev_io_change, or..., without IOFDSET |
|
|
8 | - the 4.31 timerfd code wrongly changes the priority of the signal |
|
|
9 | fd watcher, which is usually harmless unless signal fds are |
|
|
10 | also used (found via cpan tester service). |
|
|
11 | - do not wake up every minute when timerfd is used to detect timejumps. |
|
|
12 | - support a lot more "uncommon" compile time configurations, |
|
|
13 | such as ev_embed enabled but ev_timer disabled. |
|
|
14 | - the linux aio backend is no longer compiled in by default. |
|
|
15 | - update to libecb version 0x00010008. |
|
|
16 | |
|
|
17 | 4.31 Fri Dec 20 21:58:29 CET 2019 |
|
|
18 | - handle backends with minimum wait time a bit better by not |
|
|
19 | waiting in the presence of already-expired timers |
|
|
20 | (behaviour reported by Felipe Gasper). |
|
|
21 | - new feature: use timerfd to detect timejumps quickly, |
|
|
22 | can be disabled with the new EVFLAG_NOTIMERFD loop flag. |
|
|
23 | - document EV_USE_SIGNALFD feature macro. |
|
|
24 | |
|
|
25 | 4.30 (EV only) |
|
|
26 | - change non-autoconf test for __kernel_rwf_t by testing |
|
|
27 | LINUX_VERSION_CODE, the most direct test I could find. |
|
|
28 | - fix a bug in the io_uring backend that polled the wrong |
|
|
29 | backend fd, causing it to not work in many cases. |
|
|
30 | |
|
|
31 | 4.29 (EV only) |
|
|
32 | - add io uring autoconf and non-autoconf detection. |
|
|
33 | - disable io_uring when some header files are too old. |
|
|
34 | |
|
|
35 | 4.28 (EV only) |
| 6 | - linuxaio backend resulted in random memory corruption |
36 | - linuxaio backend resulted in random memory corruption |
| 7 | when loop is forked. |
37 | when loop is forked. |
| 8 | - linuxaio backend might have tried to cancel an iocb |
38 | - linuxaio backend might have tried to cancel an iocb |
| 9 | multiple times (was unable to trigger this). |
39 | multiple times (was unable to trigger this). |
| 10 | - linuxaio backend now employs a generation counter to |
40 | - linuxaio backend now employs a generation counter to |
