ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/libev/README
(Generate patch)

Comparing libev/README (file contents):
Revision 1.5 by root, Wed Oct 31 07:45:55 2007 UTC vs.
Revision 1.23 by root, Sat Jun 26 16:24:25 2021 UTC

1libev is modelled after libevent (http://monkey.org/~provos/libevent/), but aims 1libev is a high-performance event loop/event model with lots of features.
2to be faster and more correct, and also more featureful. Examples: 2(see benchmark at http://libev.schmorp.de/bench.html)
3 3
4(comparisons relative to libevent-1.3e and libev-0.00)
5 4
6- multiple watchers can wait for the same event without deregistering others, 5ABOUT
7 both for file descriptors as well as signals.
8 (registering two read events on fd 10 and unregistering one will not
9 break the other)
10 6
11- fork() is supported and can be handled 7 Homepage: http://software.schmorp.de/pkg/libev
12 (there is no way to recover from a fork when libevent is active) 8 Mailinglist: libev@lists.schmorp.de
9 http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
10 Library Documentation: http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod
13 11
14- timers are handled as a priority queue 12 Libev is modelled (very losely) after libevent and the Event perl
15 (libevent uses a less efficient red-black tree) 13 module, but is faster, scales better and is more correct, and also more
14 featureful. And also smaller. Yay.
16 15
17- supports absolute (wallclock-based) timers in addition to relative ones, 16 Some of the specialties of libev not commonly found elsewhere are:
18 i.e. can schedule timers to occur after n seconds, or at a specific time. 17
18 - extensive and detailed, readable documentation (not doxygen garbage).
19 - fully supports fork, can detect fork in various ways and automatically
20 re-arms kernel mechanisms that do not support fork.
21 - highly optimised select, poll, linux epoll, linux aio, bsd kqueue
22 and solaris event ports backends.
23 - filesystem object (path) watching (with optional linux inotify support).
24 - wallclock-based times (using absolute time, cron-like).
25 - relative timers/timeouts (handle time jumps).
26 - fast intra-thread communication between multiple
27 event loops (with optional fast linux eventfd backend).
28 - extremely easy to embed (fully documented, no dependencies,
29 autoconf supported but optional).
30 - very small codebase, no bloated library, simple code.
31 - fully extensible by being able to plug into the event loop,
32 integrate other event loops, integrate other event loop users.
33 - very little memory use (small watchers, small event loop data).
34 - optional C++ interface allowing method and function callbacks
35 at no extra memory or runtime overhead.
36 - optional Perl interface with similar characteristics (capable
37 of running Glib/Gtk2 on libev).
38 - support for other languages (multiple C++ interfaces, D, Ruby,
39 Python) available from third-parties.
19 40
20- timers can be repeating (both absolute and relative ones) 41 Examples of programs that embed libev: the EV perl module, auditd,
42 rxvt-unicode, gvpe (GNU Virtual Private Ethernet), the Deliantra MMORPG
43 server (http://www.deliantra.net/), Rubinius (a next-generation Ruby
44 VM), the Ebb web server, the Rev event toolkit.
21 45
22- detects time jumps and adjusts timers
23 (works for both forward and backward time jumps and also for absolute timers)
24 46
25- can correctly remove timers while executing callbacks 47CONTRIBUTORS
26 (libevent doesn't handle this reliably and can crash)
27 48
28- race-free signal processing 49 libev was written and designed by Marc Lehmann and Emanuele Giaquinta.
29 (libevent may delay processing signals till after the next event)
30 50
31- less calls to epoll_ctl 51 The following people sent in patches or made other noteworthy
32 (stopping and starting an io watcher between two loop iterations will now 52 contributions to the design (for minor patches, see the Changes
33 result in spuriois epoll_ctl calls) 53 file. If I forgot to include you, please shout at me, it was an
54 accident):
34 55
35- usually less calls to gettimeofday and clock_gettime 56 W.C.A. Wijngaards
36 (libevent calls it on every timer event change, libev twice per iteration) 57 Christopher Layne
58 Chris Brody
37 59
38- watchers use less memory
39 (libevent on amd64: 152 bytes, libev: <= 56 bytes)
40
41- library uses less memory
42 (libevent allocates large data structures wether used or not, libev
43 scales all its data structures dynamically)
44
45- no hardcoded arbitrary limits
46 (libevent contains an off-by-one bug and sometimes hardcodes a limit of
47 32000 fds)
48
49- libev separates timer, signal and io watchers from each other
50 (libevent combines them, but with libev you can combine them yourself
51 by reusing the same callback and still save memory)
52
53- simpler design, backends are potentially much simpler
54 (in libevent, backends have to deal with watchers, thus the problems)
55 (epoll backend in libevent: 366 lines, libev: 90 lines, and more features)
56
57whats missing?
58
59- evdns, evhttp, bufferevent are missing, libev is only an even library at
60 the moment.
61
62- no priority support at the moment
63
64- kqueue, poll (libev currently implements epoll and select)
65
66- windows support (whats windows?)
67

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines