X-Git-Url: https://git.llucax.com/software/libev.git/blobdiff_plain/573d6272d87fe4d451a5dbde4a8800ad048bdd1a..54a57c74105dc818388cec05e6fc874cdbfebf7f:/ev.pod?ds=inline diff --git a/ev.pod b/ev.pod index 9300479..9845aff 100644 --- a/ev.pod +++ b/ev.pod @@ -41,7 +41,7 @@ support for multiple event loops, then all functions taking an initial argument of name C (which is always of type C) will not have this argument. -=head1 TIME AND OTHER GLOBAL FUNCTIONS +=head1 TIME REPRESENTATION Libev represents time as a single floating point number, representing the (fractional) number of seconds since the (POSIX) epoch (somewhere near @@ -49,11 +49,18 @@ the beginning of 1970, details are complicated, don't ask). This type is called C, which is what you should use too. It usually aliases to the double type in C. +=head1 GLOBAL FUNCTIONS + +These functions can be called anytime, even before initialising the +library in any way. + =over 4 =item ev_tstamp ev_time () -Returns the current time as libev would use it. +Returns the current time as libev would use it. Please note that the +C function is usually faster and also often returns the timestamp +you actually want to know. =item int ev_version_major () @@ -65,7 +72,7 @@ C. If you want, you can compare against the global symbols C and C, which specify the version of the library your program was compiled against. -Usually, its a good idea to terminate if the major versions mismatch, +Usually, it's a good idea to terminate if the major versions mismatch, as this indicates an incompatible change. Minor versions are usually compatible to older versions, so a larger minor version alone is usually not a problem. @@ -101,11 +108,11 @@ types of such loops, the I loop, which supports signals and child events, and dynamically created loops which do not. If you use threads, a common model is to run the default event loop -in your main thread (or in a separate thrad) and for each thread you +in your main thread (or in a separate thread) and for each thread you create, you also create another event loop. Libev itself does no locking whatsoever, so if you mix calls to the same event loop in different threads, make sure you lock (this is usually a bad idea, though, even if -done correctly, because its hideous and inefficient). +done correctly, because it's hideous and inefficient). =over 4 @@ -120,43 +127,90 @@ If you don't know what event loop to use, use the one returned from this function. The flags argument can be used to specify special behaviour or specific -backends to use, and is usually specified as 0 (or EVFLAG_AUTO) +backends to use, and is usually specified as 0 (or EVFLAG_AUTO). It supports the following flags: =over 4 -=item EVFLAG_AUTO +=item C -The default flags value. Use this if you have no clue (its the right +The default flags value. Use this if you have no clue (it's the right thing, believe me). -=item EVFLAG_NOENV +=item C -If this flag bit is ored into the flag value then libev will I look -at the environment variable C. Otherwise (the default), this -environment variable will override the flags completely. This is useful -to try out specific backends to tets their performance, or to work around -bugs. +If this flag bit is ored into the flag value (or the program runs setuid +or setgid) then libev will I look at the environment variable +C. Otherwise (the default), this environment variable will +override the flags completely if it is found in the environment. This is +useful to try out specific backends to test their performance, or to work +around bugs. -=item EVMETHOD_SELECT portable select backend +=item C (value 1, portable select backend) -=item EVMETHOD_POLL poll backend (everywhere except windows) +This is your standard select(2) backend. Not I standard, as +libev tries to roll its own fd_set with no limits on the number of fds, +but if that fails, expect a fairly low limit on the number of fds when +using this backend. It doesn't scale too well (O(highest_fd)), but its usually +the fastest backend for a low number of fds. -=item EVMETHOD_EPOLL linux only +=item C (value 2, poll backend, available everywhere except on windows) -=item EVMETHOD_KQUEUE some bsds only +And this is your standard poll(2) backend. It's more complicated than +select, but handles sparse fds better and has no artificial limit on the +number of fds you can use (except it will slow down considerably with a +lot of inactive fds). It scales similarly to select, i.e. O(total_fds). -=item EVMETHOD_DEVPOLL solaris 8 only +=item C (value 4, Linux) -=item EVMETHOD_PORT solaris 10 only +For few fds, this backend is a bit little slower than poll and select, +but it scales phenomenally better. While poll and select usually scale like +O(total_fds) where n is the total number of fds (or the highest fd), epoll scales +either O(1) or O(active_fds). -If one or more of these are ored into the flags value, then only these -backends will be tried (in the reverse order as given here). If one are -specified, any backend will do. +While stopping and starting an I/O watcher in the same iteration will +result in some caching, there is still a syscall per such incident +(because the fd could point to a different file description now), so its +best to avoid that. Also, dup()ed file descriptors might not work very +well if you register events for both fds. + +=item C (value 8, most BSD clones) + +Kqueue deserves special mention, as at the time of this writing, it +was broken on all BSDs except NetBSD (usually it doesn't work with +anything but sockets and pipes, except on Darwin, where of course its +completely useless). For this reason its not being "autodetected" unless +you explicitly specify the flags (i.e. you don't use EVFLAG_AUTO). + +It scales in the same way as the epoll backend, but the interface to the +kernel is more efficient (which says nothing about its actual speed, of +course). While starting and stopping an I/O watcher does not cause an +extra syscall as with epoll, it still adds up to four event changes per +incident, so its best to avoid that. + +=item C (value 16, Solaris 8) + +This is not implemented yet (and might never be). + +=item C (value 32, Solaris 10) + +This uses the Solaris 10 port mechanism. As with everything on Solaris, +it's really slow, but it still scales very well (O(active_fds)). + +=item C + +Try all backends (even potentially broken ones that wouldn't be tried +with C). Since this is a mask, you can do stuff such as +C. =back +If one or more of these are ored into the flags value, then only these +backends will be tried (in the reverse order as given here). If none are +specified, most compiled-in backend will be tried, usually in reverse +order of their flag values :) + =item struct ev_loop *ev_loop_new (unsigned int flags) Similar to C, but always creates a new event loop that is @@ -168,7 +222,7 @@ undefined behaviour (or a failed assertion if assertions are enabled). Destroys the default loop again (frees all memory and kernel state etc.). This stops all registered event watchers (by not touching them in -any way whatsoever, although you cnanot rely on this :). +any way whatsoever, although you cannot rely on this :). =item ev_loop_destroy (loop) @@ -186,7 +240,7 @@ You I call this function after forking if and only if you want to use the event library in both processes. If you just fork+exec, you don't have to call it. -The function itself is quite fast and its usually not a problem to call +The function itself is quite fast and it's usually not a problem to call it just in case after a fork. To make this easy, the function will fit in quite nicely into a call to C: @@ -203,7 +257,7 @@ after fork, and how you do this is entirely your own problem. Returns one of the C flags indicating the event backend in use. -=item ev_tstamp = ev_now (loop) +=item ev_tstamp ev_now (loop) Returns the current "event loop time", which is the time the event loop got events and started processing them. This timestamp does not change @@ -222,36 +276,56 @@ no event watchers are active anymore or C was called. A flags value of C will look for new events, will handle those events and any outstanding ones, but will not block your process in -case there are no events. +case there are no events and will return after one iteration of the loop. A flags value of C will look for new events (waiting if neccessary) and will handle those and any outstanding ones. It will block -your process until at least one new event arrives. +your process until at least one new event arrives, and will return after +one iteration of the loop. This flags value could be used to implement alternative looping constructs, but the C and C watchers provide a better and more generic mechanism. +Here are the gory details of what ev_loop does: + + 1. If there are no active watchers (reference count is zero), return. + 2. Queue and immediately call all prepare watchers. + 3. If we have been forked, recreate the kernel state. + 4. Update the kernel state with all outstanding changes. + 5. Update the "event loop time". + 6. Calculate for how long to block. + 7. Block the process, waiting for events. + 8. Update the "event loop time" and do time jump handling. + 9. Queue all outstanding timers. + 10. Queue all outstanding periodics. + 11. If no events are pending now, queue all idle watchers. + 12. Queue all check watchers. + 13. Call all queued watchers in reverse order (i.e. check watchers first). + 14. If ev_unloop has been called or EVLOOP_ONESHOT or EVLOOP_NONBLOCK + was used, return, otherwise continue with step #1. + =item ev_unloop (loop, how) -Can be used to make a call to C return early. The C argument -must be either C, which will make the innermost C -call return, or C, which will make all nested C -calls return. +Can be used to make a call to C return early (but only after it +has processed all outstanding events). The C argument must be either +C, which will make the innermost C call return, or +C, which will make all nested C calls return. =item ev_ref (loop) =item ev_unref (loop) -Ref/unref can be used to add or remove a refcount on the event loop: Every -watcher keeps one reference. If you have a long-runing watcher you never -unregister that should not keep ev_loop from running, ev_unref() after -starting, and ev_ref() before stopping it. Libev itself uses this for -example for its internal signal pipe: It is not visible to you as a user -and should not keep C from exiting if the work is done. It is -also an excellent way to do this for generic recurring timers or from -within third-party libraries. Just remember to unref after start and ref -before stop. +Ref/unref can be used to add or remove a reference count on the event +loop: Every watcher keeps one reference, and as long as the reference +count is nonzero, C will not return on its own. If you have +a watcher you never unregister that should not keep C from +returning, ev_unref() after starting, and ev_ref() before stopping it. For +example, libev itself uses this for its internal signal pipe: It is not +visible to the libev user and should not keep C from exiting if +no event watchers registered by it are active. It is also an excellent +way to do this for generic recurring timers or from within third-party +libraries. Just remember to I and I. =back @@ -259,7 +333,7 @@ before stop. A watcher is a structure that you create and register to record your interest in some event. For instance, if you want to wait for STDIN to -become readable, you would create an ev_io watcher for that: +become readable, you would create an C watcher for that: static void my_cb (struct ev_loop *loop, struct ev_io *w, int revents) { @@ -298,61 +372,61 @@ As long as your watcher is active (has been started but not stopped) you must not touch the values stored in it. Most specifically you must never reinitialise it or call its set method. -You cna check whether an event is active by calling the C macro. To see whether an event is outstanding (but the -callback for it has not been called yet) you cna use the C macro. Each and every callback receives the event loop pointer as first, the registered watcher structure as second, and a bitset of received events as third argument. -The rceeived events usually include a single bit per event type received +The received events usually include a single bit per event type received (you can receive multiple events at the same time). The possible bit masks are: =over 4 -=item EV_READ +=item C -=item EV_WRITE +=item C -The file descriptor in the ev_io watcher has become readable and/or +The file descriptor in the C watcher has become readable and/or writable. -=item EV_TIMEOUT +=item C -The ev_timer watcher has timed out. +The C watcher has timed out. -=item EV_PERIODIC +=item C -The ev_periodic watcher has timed out. +The C watcher has timed out. -=item EV_SIGNAL +=item C -The signal specified in the ev_signal watcher has been received by a thread. +The signal specified in the C watcher has been received by a thread. -=item EV_CHILD +=item C -The pid specified in the ev_child watcher has received a status change. +The pid specified in the C watcher has received a status change. -=item EV_IDLE +=item C -The ev_idle watcher has determined that you have nothing better to do. +The C watcher has determined that you have nothing better to do. -=item EV_PREPARE +=item C -=item EV_CHECK +=item C -All ev_prepare watchers are invoked just I C starts -to gather new events, and all ev_check watchers are invoked just after +All C watchers are invoked just I C starts +to gather new events, and all C watchers are invoked just after C has gathered them, but before it invokes any callbacks for any received events. Callbacks of both watcher types can start and stop as many watchers as they want, and all of them will be taken into account -(for example, a ev_prepare watcher might start an idle watcher to keep +(for example, a C watcher might start an idle watcher to keep C from blocking). -=item EV_ERROR +=item C An unspecified error has occured, the watcher has been stopped. This might happen because the watcher could not be properly started because libev @@ -371,7 +445,7 @@ programs, though, so beware. =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER Each watcher has, by default, a member C that you can change -and read at any time, libev will completely ignore it. This cna be used +and read at any time, libev will completely ignore it. This can be used to associate arbitrary data with your watcher. If you need more data and don't want to allocate memory and store a pointer to it in that data member, you can also "subclass" the watcher type and provide your own @@ -403,37 +477,64 @@ have been omitted.... This section describes each watcher in detail, but will not repeat information given in the last section. -=head2 struct ev_io - is my file descriptor readable or writable +=head2 C - is this file descriptor readable or writable I/O watchers check whether a file descriptor is readable or writable in each iteration of the event loop (This behaviour is called level-triggering because you keep receiving events as long as the -condition persists. Remember you cna stop the watcher if you don't want to +condition persists. Remember you can stop the watcher if you don't want to act on the event and neither want to receive future events). +In general you can register as many read and/or write event watchers per +fd as you want (as long as you don't confuse yourself). Setting all file +descriptors to non-blocking mode is also usually a good idea (but not +required if you know what you are doing). + +You have to be careful with dup'ed file descriptors, though. Some backends +(the linux epoll backend is a notable example) cannot handle dup'ed file +descriptors correctly if you register interest in two or more fds pointing +to the same underlying file/socket etc. description (that is, they share +the same underlying "file open"). + +If you must do this, then force the use of a known-to-be-good backend +(at the time of this writing, this includes only EVMETHOD_SELECT and +EVMETHOD_POLL). + =over 4 =item ev_io_init (ev_io *, callback, int fd, int events) =item ev_io_set (ev_io *, int fd, int events) -Configures an ev_io watcher. The fd is the file descriptor to rceeive +Configures an C watcher. The fd is the file descriptor to rceeive events for and events is either C, C or C to receive the given events. =back -=head2 struct ev_timer - relative and optionally recurring timeouts +=head2 C - relative and optionally recurring timeouts Timer watchers are simple relative timers that generate an event after a given time, and optionally repeating in regular intervals after that. The timers are based on real time, that is, if you register an event that -times out after an hour and youreset your system clock to last years +times out after an hour and you reset your system clock to last years time, it will still time out after (roughly) and hour. "Roughly" because -detecting time jumps is hard, and soem inaccuracies are unavoidable (the +detecting time jumps is hard, and some inaccuracies are unavoidable (the monotonic clock option helps a lot here). +The relative timeouts are calculated relative to the C +time. This is usually the right thing as this timestamp refers to the time +of the event triggering whatever timeout you are modifying/starting. If +you suspect event processing to be delayed and you I to base the timeout +on the current time, use something like this to adjust for this: + + ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); + +The callback is guarenteed to be invoked only when its timeout has passed, +but if multiple timers become ready during the same loop iteration then +order of execution is undefined. + =over 4 =item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat) @@ -448,7 +549,7 @@ later, again, and again, until stopped manually. The timer itself will do a best-effort at avoiding drift, that is, if you configure a timer to trigger every 10 seconds, then it will trigger at exactly 10 second intervals. If, however, your program cannot keep up with -the timer (ecause it takes longer than those 10 seconds to do stuff) the +the timer (because it takes longer than those 10 seconds to do stuff) the timer will not fire more than once per event loop iteration. =item ev_timer_again (loop) @@ -465,30 +566,34 @@ This sounds a bit complicated, but here is a useful and typical example: Imagine you have a tcp connection and you want a so-called idle timeout, that is, you want to be called when there have been, say, 60 seconds of inactivity on the socket. The easiest way to do this is to -configure an ev_timer with after=repeat=60 and calling ev_timer_again each +configure an C with after=repeat=60 and calling ev_timer_again each time you successfully read or write some data. If you go into an idle state where you do not expect data to travel on the socket, you can stop the timer, and again will automatically restart it if need be. =back -=head2 ev_periodic - to cron or not to cron it +=head2 C - to cron or not to cron Periodic watchers are also timers of a kind, but they are very versatile (and unfortunately a bit complex). -Unlike ev_timer's, they are not based on real time (or relative time) +Unlike C's, they are not based on real time (or relative time) but on wallclock time (absolute time). You can tell a periodic watcher to trigger "at" some specific point in time. For example, if you tell a periodic watcher to trigger in 10 seconds (by specifiying e.g. c) and then reset your system clock to the last year, then it will -take a year to trigger the event (unlike an ev_timer, which would trigger +take a year to trigger the event (unlike an C, which would trigger roughly 10 seconds later and of course not if you reset your system time again). They can also be used to implement vastly more complex timers, such as triggering an event on eahc midnight, local time. +As with timers, the callback is guarenteed to be invoked only when the +time (C) has been passed, but if multiple periodic timers become ready +during the same loop iteration then order of execution is undefined. + =over 4 =item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb) @@ -498,7 +603,6 @@ triggering an event on eahc midnight, local time. Lots of arguments, lets sort it out... There are basically three modes of operation, and we will explain them from simplest to complex: - =over 4 =item * absolute timer (interval = reschedule_cb = 0) @@ -521,11 +625,11 @@ time: This doesn't mean there will always be 3600 seconds in between triggers, but only that the the callback will be called when the system time shows a -full hour (UTC), or more correct, when the system time is evenly divisible +full hour (UTC), or more correctly, when the system time is evenly divisible by 3600. Another way to think about it (for the mathematically inclined) is that -ev_periodic will try to run the callback in this mode at the next possible +C will try to run the callback in this mode at the next possible time where C