| 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 | WISH? monotonic clocks times/GetTickCount for coarse corrections? |
| 3 | |
4 | |
| 4 | WISH? monotonic clocks times/GetTickCount for coarse corrections? |
5 | - further optimise away the EPOLL_CTL_ADD/MOD combo in the epoll |
| 5 | TODO: document 2.6.24-- breakage of inotify |
6 | backend by assuming the kernel event mask hasn't changed if |
|
|
7 | ADD fails with EEXIST. |
|
|
8 | - work around spurious event notification bugs in epoll by using |
|
|
9 | a 32-bit generation counter. recreate kernel state if we receive |
|
|
10 | spurious notifications or unwanted events. this is very costly, |
|
|
11 | but I didn't come up with this horrible design. |
|
|
12 | - use memset to initialise most arrays now and do away with the |
|
|
13 | init functions. |
|
|
14 | - expand time-out strategies into a "Be smart about timeouts" section. |
|
|
15 | - drop the "struct" from all ev_watcher declarations in the |
|
|
16 | documentation and did other clarifications (yeah, it was a mistake |
|
|
17 | to have a struct AND a function called ev_loop). |
|
|
18 | - fix a bug where ev_default would not initialise the default |
|
|
19 | loop again after it was destroyed with ev_default_destroy. |
|
|
20 | - rename syserr to ev_syserr to avoid name clashes when embedding, |
|
|
21 | do similar changes for event.c. |
|
|
22 | |
|
|
23 | 3.45 Tue Oct 21 21:59:26 CEST 2008 |
| 6 | - disable inotify usage on linux <2.6.25, as it is broken |
24 | - disable inotify usage on linux <2.6.25, as it is broken |
| 7 | (reported by Yoann Vandoorselaere). |
25 | (reported by Yoann Vandoorselaere). |
| 8 | - ev_stat errornously would try to add inotify watchers |
26 | - ev_stat errornously would try to add inotify watchers |
| 9 | even when inotify wasn't available (this should only |
27 | even when inotify wasn't available (this should only |
| 10 | have a performance impact). |
28 | have a performance impact). |
