| 1 | libev is a high-performanc3 event loop/event model with lots of features. |
1 | libev is a high-performance event loop/event model with lots of features. |
|
|
2 | (see benchmark at http://libev.schmorp.de/bench.html) |
| 2 | |
3 | |
| 3 | It is modelled (very losely) after libevent |
4 | Homepage: http://software.schmorp.de/pkg/libev |
| 4 | (http://monkey.org/~provos/libevent/) and the Event perl module, but aims |
5 | E-Mail: libev@lists.schmorp.de |
| 5 | to be faster and more correct, and also more featureful. |
6 | Library Documentation: http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod |
| 6 | |
7 | |
| 7 | DIFFERENCES AND COMPARISON TO LIBEVENT: |
8 | It is modelled (very losely) after libevent and the Event perl module, |
|
|
9 | but aims to be faster and more correct, and also more featureful. And |
|
|
10 | also smaller. Yay. |
| 8 | |
11 | |
| 9 | (comparisons relative to libevent-1.3e and libev-0.00) |
12 | ABOUT THIS DISTRIBUTION |
| 10 | |
13 | |
| 11 | - multiple watchers can wait for the same event without deregistering others, |
14 | If you downloaded the libevent+libev distribution of libev, you will |
| 12 | both for file descriptors as well as signals. |
15 | find it looks very much like libevent. In fact, the distributed libev |
| 13 | (registering two read events on fd 10 and unregistering one will not |
16 | tarballs are indeed libevent tarballs patched up with the libev |
| 14 | break the other). |
17 | event core, taking the evbuffer, evtag, evdns and evhttpd parts from |
|
|
18 | libevent (they use the libevent emulation inside libev). Configure and |
|
|
19 | Makefile stuff is also a more or less direct copy of libevent, and are |
|
|
20 | maintained by the libevent authors. |
| 15 | |
21 | |
| 16 | - fork() is supported and can be handled |
22 | If you downloaded the libev distribution (without libevent), then |
| 17 | (there is no way to recover from a fork when libevent is active). |
23 | you only get the core parts of the library, meaning http and dns |
|
|
24 | client/server code and similar things are missing. Only the core event |
|
|
25 | loop is included. |
| 18 | |
26 | |
| 19 | - timers are handled as a priority queue (important operations are O(1)) |
27 | If you are looking for an easily embeddable version, I recommend using |
| 20 | (libevent uses a much less efficient but more complex red-black tree). |
28 | the libev standalone distribution or the CVS repository. |
| 21 | |
29 | |
| 22 | - supports absolute (wallclock-based) timers in addition to relative ones, |
30 | Examples of programs that embed libev: the EV perl module, |
| 23 | i.e. can schedule timers to occur after n seconds, or at a specific time. |
31 | rxvt-unicode, gvpe (GNU Virtual Private Ethernet) and deliantra |
|
|
32 | (http://www.deliantra.net). |
| 24 | |
33 | |
| 25 | - timers can be repeating (both absolute and relative ones). |
34 | DIFFERENCES AND COMPARISON TO LIBEVENT |
| 26 | |
35 | |
| 27 | - detects time jumps and adjusts timers |
36 | The comparisons below are relative to libevent-1.3e. |
| 28 | (works for both forward and backward time jumps and also for absolute timers). |
|
|
| 29 | |
37 | |
| 30 | - can correctly remove timers while executing callbacks |
38 | - multiple watchers can wait for the same event without deregistering others, |
| 31 | (libevent doesn't handle this reliably and can crash). |
39 | both for file descriptors as well as signals. |
|
|
40 | (registering two read events on fd 10 and unregistering one will not |
|
|
41 | break the other). |
| 32 | |
42 | |
| 33 | - race-free signal processing |
43 | - fork() is supported and can be handled |
| 34 | (libevent may delay processing signals till after the next event). |
44 | (there is no way to recover from a fork with libevent). |
| 35 | |
45 | |
| 36 | - less calls to epoll_ctl |
46 | - timers are handled as a priority queue (important operations are O(1)) |
| 37 | (stopping and starting an io watcher between two loop iterations will now |
47 | (libevent uses a much less efficient but more complex red-black tree). |
| 38 | result in spuriois epoll_ctl calls). |
|
|
| 39 | |
48 | |
| 40 | - usually less calls to gettimeofday and clock_gettime |
49 | - supports absolute (wallclock-based) timers in addition to relative ones, |
| 41 | (libevent calls it on every timer event change, libev twice per iteration). |
50 | i.e. can schedule timers to occur after n seconds, or at a specific time. |
| 42 | |
51 | |
| 43 | - watchers use less memory |
52 | - timers can be repeating (both absolute and relative ones). |
| 44 | (libevent on amd64: 152 bytes, libev: <= 56 bytes). |
|
|
| 45 | |
53 | |
| 46 | - library uses less memory |
54 | - absolute timers can have customised rescheduling hooks (suitable for cron-like |
| 47 | (libevent allocates large data structures wether used or not, libev |
55 | applications). |
| 48 | scales all its data structures dynamically). |
|
|
| 49 | |
56 | |
| 50 | - no hardcoded arbitrary limits |
57 | - detects time jumps and adjusts timers |
| 51 | (libevent contains an off-by-one bug and sometimes hardcodes a limit of |
58 | (works for both forward and backward time jumps and also for absolute timers). |
| 52 | 32000 fds). |
|
|
| 53 | |
59 | |
| 54 | - libev separates timer, signal and io watchers from each other |
60 | - race-free signal processing |
| 55 | (libevent combines them, but with libev you can combine them yourself |
61 | (libevent may delay processing signals till after the next event). |
| 56 | by reusing the same callback and still save memory). |
|
|
| 57 | |
62 | |
| 58 | - simpler design, backends are potentially much simpler |
63 | - more efficient epoll backend |
| 59 | (in libevent, backends have to deal with watchers, thus the problems) |
64 | (stopping and starting an io watcher between two loop iterations will not |
| 60 | (epoll backend in libevent: 366 lines, libev: 90 lines, and more features). |
65 | result in spurious epoll_ctl calls). |
| 61 | |
66 | |
| 62 | - libev handles EBADF gracefully by removing the offending fds. |
67 | - usually less calls to gettimeofday and clock_gettime |
|
|
68 | (libevent calls it on every timer event change, libev twice per iteration). |
| 63 | |
69 | |
| 64 | - doesn't rely on nonportable BSD header files. |
70 | - watchers use less memory |
|
|
71 | (libevent watcher on amd64: 152 bytes, libev native: <= 56 bytes, libevent emulation: 144 bytes). |
| 65 | |
72 | |
| 66 | - a event.h compatibility header exists, and can be used to run a wide |
73 | - library uses less memory |
| 67 | range of libevent programs unchanged (such as evdns.c). |
74 | (libevent allocates large data structures wether used or not, libev |
|
|
75 | scales all its data structures dynamically). |
| 68 | |
76 | |
| 69 | whats missing? |
77 | - no hardcoded arbitrary limits |
|
|
78 | (libevent contains an off-by-one bug and sometimes hardcodes limits). |
| 70 | |
79 | |
| 71 | - evbuffer, evhttp, bufferevent are missing. |
80 | - libev separates timer, signal and io watchers from each other |
|
|
81 | (libevent combines them, but with libev you can combine them yourself |
|
|
82 | by reusing the same callback and still save memory). |
| 72 | |
83 | |
| 73 | - no priority support at the moment (but likely to be delivered later). |
84 | - simpler design, backends are potentially much simpler |
|
|
85 | (in libevent, backends have to deal with watchers, thus the problems with |
|
|
86 | wildly different semantics between diferent backends) |
|
|
87 | (epoll backend in libevent: 366 lines no caching, libev: 90 lines full caching). |
| 74 | |
88 | |
| 75 | - kqueue, poll (libev currently implements epoll and select). |
89 | - libev handles EBADF gracefully by removing the offending fds. |
| 76 | |
90 | |
| 77 | - windows support (whats windows?). |
91 | - libev communicates errors to the callback, libevent to the |
|
|
92 | event adder or not at all. |
| 78 | |
93 | |
|
|
94 | - doesn't rely on nonportable BSD header files. |
|
|
95 | |
|
|
96 | - an event.h compatibility header exists, and can be used to run a wide |
|
|
97 | range of libevent programs unchanged (such as evdns.c). |
|
|
98 | |
|
|
99 | - win32 compatibility for the core parts. |
|
|
100 | (the backend is fd-based as documented and on other platforms, |
|
|
101 | not handle-based like libevent, and can be used for both winscoket environments |
|
|
102 | and unix-like ones). |
|
|
103 | |
|
|
104 | - libev can be embedded easily with or without autoconf support into |
|
|
105 | other programs, with no changes to the source code necessary. |
|
|
106 | |
|
|
107 | - the event core library (ev and event layer) compiles and works both as |
|
|
108 | C and C++. |
|
|
109 | |
|
|
110 | - a simple C++ wrapper that supports methods as callbacks exists. |
|
|
111 | |
|
|
112 | - a full featured and widely used perl module is available. |
|
|
113 | |
|
|
114 | whats missing? |
|
|
115 | |
|
|
116 | - no event-like priority support at the moment (the ev priorities work |
|
|
117 | differently, but you can use idle watchers to get a similar effect). |
|
|
118 | |
|
|
119 | AUTHOR |
|
|
120 | |
|
|
121 | libev was written and designed by Marc Lehmann and Emanuele Giaquinta. |
|
|
122 | |
|
|
123 | The following people sent in patches or made other noteworthy |
|
|
124 | contributions to the design (if I forgot to include you, please shout |
|
|
125 | at me, it was an accident): |
|
|
126 | |
|
|
127 | W.C.A. Wijngaards |
|
|
128 | Christopher Layne |
|
|
129 | Chris Brody |
|
|
130 | |
