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

Comparing libev/ev.3 (file contents):
Revision 1.7 by root, Fri Nov 23 08:36:35 2007 UTC vs.
Revision 1.51 by root, Wed Dec 12 17:55:30 2007 UTC

… …
127.\} 127.\}
128.rm #[ #] #H #V #F C 128.rm #[ #] #H #V #F C
129.\" ======================================================================== 129.\" ========================================================================
130.\" 130.\"
131.IX Title ""<STANDARD INPUT>" 1" 131.IX Title ""<STANDARD INPUT>" 1"
132.TH "<STANDARD INPUT>" 1 "2007-11-23" "perl v5.8.8" "User Contributed Perl Documentation" 132.TH "<STANDARD INPUT>" 1 "2007-12-12" "perl v5.8.8" "User Contributed Perl Documentation"
133.SH "NAME" 133.SH "NAME"
134libev \- a high performance full\-featured event loop written in C 134libev \- a high performance full\-featured event loop written in C
135.SH "SYNOPSIS" 135.SH "SYNOPSIS"
136.IX Header "SYNOPSIS" 136.IX Header "SYNOPSIS"
137.Vb 1 137.Vb 1
138\& #include <ev.h> 138\& #include <ev.h>
139.Ve 139.Ve
140.SH "EXAMPLE PROGRAM"
141.IX Header "EXAMPLE PROGRAM"
142.Vb 1
143\& #include <ev.h>
144.Ve
145.PP
146.Vb 2
147\& ev_io stdin_watcher;
148\& ev_timer timeout_watcher;
149.Ve
150.PP
151.Vb 8
152\& /* called when data readable on stdin */
153\& static void
154\& stdin_cb (EV_P_ struct ev_io *w, int revents)
155\& {
156\& /* puts ("stdin ready"); */
157\& ev_io_stop (EV_A_ w); /* just a syntax example */
158\& ev_unloop (EV_A_ EVUNLOOP_ALL); /* leave all loop calls */
159\& }
160.Ve
161.PP
162.Vb 6
163\& static void
164\& timeout_cb (EV_P_ struct ev_timer *w, int revents)
165\& {
166\& /* puts ("timeout"); */
167\& ev_unloop (EV_A_ EVUNLOOP_ONE); /* leave one loop call */
168\& }
169.Ve
170.PP
171.Vb 4
172\& int
173\& main (void)
174\& {
175\& struct ev_loop *loop = ev_default_loop (0);
176.Ve
177.PP
178.Vb 3
179\& /* initialise an io watcher, then start it */
180\& ev_io_init (&stdin_watcher, stdin_cb, /*STDIN_FILENO*/ 0, EV_READ);
181\& ev_io_start (loop, &stdin_watcher);
182.Ve
183.PP
184.Vb 3
185\& /* simple non-repeating 5.5 second timeout */
186\& ev_timer_init (&timeout_watcher, timeout_cb, 5.5, 0.);
187\& ev_timer_start (loop, &timeout_watcher);
188.Ve
189.PP
190.Vb 2
191\& /* loop till timeout or data ready */
192\& ev_loop (loop, 0);
193.Ve
194.PP
195.Vb 2
196\& return 0;
197\& }
198.Ve
140.SH "DESCRIPTION" 199.SH "DESCRIPTION"
141.IX Header "DESCRIPTION" 200.IX Header "DESCRIPTION"
201The newest version of this document is also available as a html-formatted
202web page you might find easier to navigate when reading it for the first
203time: <http://cvs.schmorp.de/libev/ev.html>.
204.PP
142Libev is an event loop: you register interest in certain events (such as a 205Libev is an event loop: you register interest in certain events (such as a
143file descriptor being readable or a timeout occuring), and it will manage 206file descriptor being readable or a timeout occuring), and it will manage
144these event sources and provide your program with events. 207these event sources and provide your program with events.
145.PP 208.PP
146To do this, it must take more or less complete control over your process 209To do this, it must take more or less complete control over your process
… …
151watchers\fR, which are relatively small C structures you initialise with the 214watchers\fR, which are relatively small C structures you initialise with the
152details of the event, and then hand it over to libev by \fIstarting\fR the 215details of the event, and then hand it over to libev by \fIstarting\fR the
153watcher. 216watcher.
154.SH "FEATURES" 217.SH "FEATURES"
155.IX Header "FEATURES" 218.IX Header "FEATURES"
156Libev supports select, poll, the linux-specific epoll and the bsd-specific 219Libev supports \f(CW\*(C`select\*(C'\fR, \f(CW\*(C`poll\*(C'\fR, the Linux-specific \f(CW\*(C`epoll\*(C'\fR, the
157kqueue mechanisms for file descriptor events, relative timers, absolute 220BSD-specific \f(CW\*(C`kqueue\*(C'\fR and the Solaris-specific event port mechanisms
158timers with customised rescheduling, signal events, process status change 221for file descriptor events (\f(CW\*(C`ev_io\*(C'\fR), the Linux \f(CW\*(C`inotify\*(C'\fR interface
159events (related to \s-1SIGCHLD\s0), and event watchers dealing with the event 222(for \f(CW\*(C`ev_stat\*(C'\fR), relative timers (\f(CW\*(C`ev_timer\*(C'\fR), absolute timers
160loop mechanism itself (idle, prepare and check watchers). It also is quite 223with customised rescheduling (\f(CW\*(C`ev_periodic\*(C'\fR), synchronous signals
161fast (see this benchmark comparing 224(\f(CW\*(C`ev_signal\*(C'\fR), process status change events (\f(CW\*(C`ev_child\*(C'\fR), and event
162it to libevent for example). 225watchers dealing with the event loop mechanism itself (\f(CW\*(C`ev_idle\*(C'\fR,
226\&\f(CW\*(C`ev_embed\*(C'\fR, \f(CW\*(C`ev_prepare\*(C'\fR and \f(CW\*(C`ev_check\*(C'\fR watchers) as well as
227file watchers (\f(CW\*(C`ev_stat\*(C'\fR) and even limited support for fork events
228(\f(CW\*(C`ev_fork\*(C'\fR).
229.PP
230It also is quite fast (see this
231benchmark comparing it to libevent
232for example).
163.SH "CONVENTIONS" 233.SH "CONVENTIONS"
164.IX Header "CONVENTIONS" 234.IX Header "CONVENTIONS"
165Libev is very configurable. In this manual the default configuration 235Libev is very configurable. In this manual the default configuration will
166will be described, which supports multiple event loops. For more info 236be described, which supports multiple event loops. For more info about
167about various configuration options please have a look at the file 237various configuration options please have a look at \fB\s-1EMBED\s0\fR section in
168\&\fI\s-1README\s0.embed\fR in the libev distribution. If libev was configured without 238this manual. If libev was configured without support for multiple event
169support for multiple event loops, then all functions taking an initial 239loops, then all functions taking an initial argument of name \f(CW\*(C`loop\*(C'\fR
170argument of name \f(CW\*(C`loop\*(C'\fR (which is always of type \f(CW\*(C`struct ev_loop *\*(C'\fR) 240(which is always of type \f(CW\*(C`struct ev_loop *\*(C'\fR) will not have this argument.
171will not have this argument.
172.SH "TIME REPRESENTATION" 241.SH "TIME REPRESENTATION"
173.IX Header "TIME REPRESENTATION" 242.IX Header "TIME REPRESENTATION"
174Libev represents time as a single floating point number, representing the 243Libev represents time as a single floating point number, representing the
175(fractional) number of seconds since the (\s-1POSIX\s0) epoch (somewhere near 244(fractional) number of seconds since the (\s-1POSIX\s0) epoch (somewhere near
176the beginning of 1970, details are complicated, don't ask). This type is 245the beginning of 1970, details are complicated, don't ask). This type is
177called \f(CW\*(C`ev_tstamp\*(C'\fR, which is what you should use too. It usually aliases 246called \f(CW\*(C`ev_tstamp\*(C'\fR, which is what you should use too. It usually aliases
178to the double type in C. 247to the \f(CW\*(C`double\*(C'\fR type in C, and when you need to do any calculations on
248it, you should treat it as such.
179.SH "GLOBAL FUNCTIONS" 249.SH "GLOBAL FUNCTIONS"
180.IX Header "GLOBAL FUNCTIONS" 250.IX Header "GLOBAL FUNCTIONS"
181These functions can be called anytime, even before initialising the 251These functions can be called anytime, even before initialising the
182library in any way. 252library in any way.
183.IP "ev_tstamp ev_time ()" 4 253.IP "ev_tstamp ev_time ()" 4
… …
189.IX Item "int ev_version_major ()" 259.IX Item "int ev_version_major ()"
190.PD 0 260.PD 0
191.IP "int ev_version_minor ()" 4 261.IP "int ev_version_minor ()" 4
192.IX Item "int ev_version_minor ()" 262.IX Item "int ev_version_minor ()"
193.PD 263.PD
194You can find out the major and minor version numbers of the library 264You can find out the major and minor \s-1ABI\s0 version numbers of the library
195you linked against by calling the functions \f(CW\*(C`ev_version_major\*(C'\fR and 265you linked against by calling the functions \f(CW\*(C`ev_version_major\*(C'\fR and
196\&\f(CW\*(C`ev_version_minor\*(C'\fR. If you want, you can compare against the global 266\&\f(CW\*(C`ev_version_minor\*(C'\fR. If you want, you can compare against the global
197symbols \f(CW\*(C`EV_VERSION_MAJOR\*(C'\fR and \f(CW\*(C`EV_VERSION_MINOR\*(C'\fR, which specify the 267symbols \f(CW\*(C`EV_VERSION_MAJOR\*(C'\fR and \f(CW\*(C`EV_VERSION_MINOR\*(C'\fR, which specify the
198version of the library your program was compiled against. 268version of the library your program was compiled against.
199.Sp 269.Sp
270These version numbers refer to the \s-1ABI\s0 version of the library, not the
271release version.
272.Sp
200Usually, it's a good idea to terminate if the major versions mismatch, 273Usually, it's a good idea to terminate if the major versions mismatch,
201as this indicates an incompatible change. Minor versions are usually 274as this indicates an incompatible change. Minor versions are usually
202compatible to older versions, so a larger minor version alone is usually 275compatible to older versions, so a larger minor version alone is usually
203not a problem. 276not a problem.
277.Sp
278Example: Make sure we haven't accidentally been linked against the wrong
279version.
280.Sp
281.Vb 3
282\& assert (("libev version mismatch",
283\& ev_version_major () == EV_VERSION_MAJOR
284\& && ev_version_minor () >= EV_VERSION_MINOR));
285.Ve
204.IP "unsigned int ev_supported_backends ()" 4 286.IP "unsigned int ev_supported_backends ()" 4
205.IX Item "unsigned int ev_supported_backends ()" 287.IX Item "unsigned int ev_supported_backends ()"
206Return the set of all backends (i.e. their corresponding \f(CW\*(C`EV_BACKEND_*\*(C'\fR 288Return the set of all backends (i.e. their corresponding \f(CW\*(C`EV_BACKEND_*\*(C'\fR
207value) compiled into this binary of libev (independent of their 289value) compiled into this binary of libev (independent of their
208availability on the system you are running on). See \f(CW\*(C`ev_default_loop\*(C'\fR for 290availability on the system you are running on). See \f(CW\*(C`ev_default_loop\*(C'\fR for
209a description of the set values. 291a description of the set values.
292.Sp
293Example: make sure we have the epoll method, because yeah this is cool and
294a must have and can we have a torrent of it please!!!11
295.Sp
296.Vb 2
297\& assert (("sorry, no epoll, no sex",
298\& ev_supported_backends () & EVBACKEND_EPOLL));
299.Ve
210.IP "unsigned int ev_recommended_backends ()" 4 300.IP "unsigned int ev_recommended_backends ()" 4
211.IX Item "unsigned int ev_recommended_backends ()" 301.IX Item "unsigned int ev_recommended_backends ()"
212Return the set of all backends compiled into this binary of libev and also 302Return the set of all backends compiled into this binary of libev and also
213recommended for this platform. This set is often smaller than the one 303recommended for this platform. This set is often smaller than the one
214returned by \f(CW\*(C`ev_supported_backends\*(C'\fR, as for example kqueue is broken on 304returned by \f(CW\*(C`ev_supported_backends\*(C'\fR, as for example kqueue is broken on
215most BSDs and will not be autodetected unless you explicitly request it 305most BSDs and will not be autodetected unless you explicitly request it
216(assuming you know what you are doing). This is the set of backends that 306(assuming you know what you are doing). This is the set of backends that
217\&\f(CW\*(C`EVFLAG_AUTO\*(C'\fR will probe for. 307libev will probe for if you specify no backends explicitly.
308.IP "unsigned int ev_embeddable_backends ()" 4
309.IX Item "unsigned int ev_embeddable_backends ()"
310Returns the set of backends that are embeddable in other event loops. This
311is the theoretical, all\-platform, value. To find which backends
312might be supported on the current system, you would need to look at
313\&\f(CW\*(C`ev_embeddable_backends () & ev_supported_backends ()\*(C'\fR, likewise for
314recommended ones.
315.Sp
316See the description of \f(CW\*(C`ev_embed\*(C'\fR watchers for more info.
218.IP "ev_set_allocator (void *(*cb)(void *ptr, long size))" 4 317.IP "ev_set_allocator (void *(*cb)(void *ptr, long size))" 4
219.IX Item "ev_set_allocator (void *(*cb)(void *ptr, long size))" 318.IX Item "ev_set_allocator (void *(*cb)(void *ptr, long size))"
220Sets the allocation function to use (the prototype is similar to the 319Sets the allocation function to use (the prototype is similar \- the
221realloc C function, the semantics are identical). It is used to allocate 320semantics is identical \- to the realloc C function). It is used to
222and free memory (no surprises here). If it returns zero when memory 321allocate and free memory (no surprises here). If it returns zero when
223needs to be allocated, the library might abort or take some potentially 322memory needs to be allocated, the library might abort or take some
224destructive action. The default is your system realloc function. 323potentially destructive action. The default is your system realloc
324function.
225.Sp 325.Sp
226You could override this function in high-availability programs to, say, 326You could override this function in high-availability programs to, say,
227free some memory if it cannot allocate memory, to use a special allocator, 327free some memory if it cannot allocate memory, to use a special allocator,
228or even to sleep a while and retry until some memory is available. 328or even to sleep a while and retry until some memory is available.
329.Sp
330Example: Replace the libev allocator with one that waits a bit and then
331retries).
332.Sp
333.Vb 6
334\& static void *
335\& persistent_realloc (void *ptr, size_t size)
336\& {
337\& for (;;)
338\& {
339\& void *newptr = realloc (ptr, size);
340.Ve
341.Sp
342.Vb 2
343\& if (newptr)
344\& return newptr;
345.Ve
346.Sp
347.Vb 3
348\& sleep (60);
349\& }
350\& }
351.Ve
352.Sp
353.Vb 2
354\& ...
355\& ev_set_allocator (persistent_realloc);
356.Ve
229.IP "ev_set_syserr_cb (void (*cb)(const char *msg));" 4 357.IP "ev_set_syserr_cb (void (*cb)(const char *msg));" 4
230.IX Item "ev_set_syserr_cb (void (*cb)(const char *msg));" 358.IX Item "ev_set_syserr_cb (void (*cb)(const char *msg));"
231Set the callback function to call on a retryable syscall error (such 359Set the callback function to call on a retryable syscall error (such
232as failed select, poll, epoll_wait). The message is a printable string 360as failed select, poll, epoll_wait). The message is a printable string
233indicating the system call or subsystem causing the problem. If this 361indicating the system call or subsystem causing the problem. If this
234callback is set, then libev will expect it to remedy the sitution, no 362callback is set, then libev will expect it to remedy the sitution, no
235matter what, when it returns. That is, libev will generally retry the 363matter what, when it returns. That is, libev will generally retry the
236requested operation, or, if the condition doesn't go away, do bad stuff 364requested operation, or, if the condition doesn't go away, do bad stuff
237(such as abort). 365(such as abort).
366.Sp
367Example: This is basically the same thing that libev does internally, too.
368.Sp
369.Vb 6
370\& static void
371\& fatal_error (const char *msg)
372\& {
373\& perror (msg);
374\& abort ();
375\& }
376.Ve
377.Sp
378.Vb 2
379\& ...
380\& ev_set_syserr_cb (fatal_error);
381.Ve
238.SH "FUNCTIONS CONTROLLING THE EVENT LOOP" 382.SH "FUNCTIONS CONTROLLING THE EVENT LOOP"
239.IX Header "FUNCTIONS CONTROLLING THE EVENT LOOP" 383.IX Header "FUNCTIONS CONTROLLING THE EVENT LOOP"
240An event loop is described by a \f(CW\*(C`struct ev_loop *\*(C'\fR. The library knows two 384An event loop is described by a \f(CW\*(C`struct ev_loop *\*(C'\fR. The library knows two
241types of such loops, the \fIdefault\fR loop, which supports signals and child 385types of such loops, the \fIdefault\fR loop, which supports signals and child
242events, and dynamically created loops which do not. 386events, and dynamically created loops which do not.
… …
256.Sp 400.Sp
257If you don't know what event loop to use, use the one returned from this 401If you don't know what event loop to use, use the one returned from this
258function. 402function.
259.Sp 403.Sp
260The flags argument can be used to specify special behaviour or specific 404The flags argument can be used to specify special behaviour or specific
261backends to use, and is usually specified as \f(CW0\fR (or \s-1EVFLAG_AUTO\s0). 405backends to use, and is usually specified as \f(CW0\fR (or \f(CW\*(C`EVFLAG_AUTO\*(C'\fR).
262.Sp 406.Sp
263It supports the following flags: 407The following flags are supported:
264.RS 4 408.RS 4
265.ie n .IP """EVFLAG_AUTO""" 4 409.ie n .IP """EVFLAG_AUTO""" 4
266.el .IP "\f(CWEVFLAG_AUTO\fR" 4 410.el .IP "\f(CWEVFLAG_AUTO\fR" 4
267.IX Item "EVFLAG_AUTO" 411.IX Item "EVFLAG_AUTO"
268The default flags value. Use this if you have no clue (it's the right 412The default flags value. Use this if you have no clue (it's the right
… …
274or setgid) then libev will \fInot\fR look at the environment variable 418or setgid) then libev will \fInot\fR look at the environment variable
275\&\f(CW\*(C`LIBEV_FLAGS\*(C'\fR. Otherwise (the default), this environment variable will 419\&\f(CW\*(C`LIBEV_FLAGS\*(C'\fR. Otherwise (the default), this environment variable will
276override the flags completely if it is found in the environment. This is 420override the flags completely if it is found in the environment. This is
277useful to try out specific backends to test their performance, or to work 421useful to try out specific backends to test their performance, or to work
278around bugs. 422around bugs.
423.ie n .IP """EVFLAG_FORKCHECK""" 4
424.el .IP "\f(CWEVFLAG_FORKCHECK\fR" 4
425.IX Item "EVFLAG_FORKCHECK"
426Instead of calling \f(CW\*(C`ev_default_fork\*(C'\fR or \f(CW\*(C`ev_loop_fork\*(C'\fR manually after
427a fork, you can also make libev check for a fork in each iteration by
428enabling this flag.
429.Sp
430This works by calling \f(CW\*(C`getpid ()\*(C'\fR on every iteration of the loop,
431and thus this might slow down your event loop if you do a lot of loop
432iterations and little real work, but is usually not noticeable (on my
433Linux system for example, \f(CW\*(C`getpid\*(C'\fR is actually a simple 5\-insn sequence
434without a syscall and thus \fIvery\fR fast, but my Linux system also has
435\&\f(CW\*(C`pthread_atfork\*(C'\fR which is even faster).
436.Sp
437The big advantage of this flag is that you can forget about fork (and
438forget about forgetting to tell libev about forking) when you use this
439flag.
440.Sp
441This flag setting cannot be overriden or specified in the \f(CW\*(C`LIBEV_FLAGS\*(C'\fR
442environment variable.
279.ie n .IP """EVBACKEND_SELECT"" (value 1, portable select backend)" 4 443.ie n .IP """EVBACKEND_SELECT"" (value 1, portable select backend)" 4
280.el .IP "\f(CWEVBACKEND_SELECT\fR (value 1, portable select backend)" 4 444.el .IP "\f(CWEVBACKEND_SELECT\fR (value 1, portable select backend)" 4
281.IX Item "EVBACKEND_SELECT (value 1, portable select backend)" 445.IX Item "EVBACKEND_SELECT (value 1, portable select backend)"
282This is your standard \fIselect\fR\|(2) backend. Not \fIcompletely\fR standard, as 446This is your standard \fIselect\fR\|(2) backend. Not \fIcompletely\fR standard, as
283libev tries to roll its own fd_set with no limits on the number of fds, 447libev tries to roll its own fd_set with no limits on the number of fds,
… …
312.el .IP "\f(CWEVBACKEND_KQUEUE\fR (value 8, most \s-1BSD\s0 clones)" 4 476.el .IP "\f(CWEVBACKEND_KQUEUE\fR (value 8, most \s-1BSD\s0 clones)" 4
313.IX Item "EVBACKEND_KQUEUE (value 8, most BSD clones)" 477.IX Item "EVBACKEND_KQUEUE (value 8, most BSD clones)"
314Kqueue deserves special mention, as at the time of this writing, it 478Kqueue deserves special mention, as at the time of this writing, it
315was broken on all BSDs except NetBSD (usually it doesn't work with 479was broken on all BSDs except NetBSD (usually it doesn't work with
316anything but sockets and pipes, except on Darwin, where of course its 480anything but sockets and pipes, except on Darwin, where of course its
317completely useless). For this reason its not being \*(L"autodetected\*(R" unless 481completely useless). For this reason its not being \*(L"autodetected\*(R"
318you explicitly specify the flags (i.e. you don't use \s-1EVFLAG_AUTO\s0). 482unless you explicitly specify it explicitly in the flags (i.e. using
483\&\f(CW\*(C`EVBACKEND_KQUEUE\*(C'\fR).
319.Sp 484.Sp
320It scales in the same way as the epoll backend, but the interface to the 485It scales in the same way as the epoll backend, but the interface to the
321kernel is more efficient (which says nothing about its actual speed, of 486kernel is more efficient (which says nothing about its actual speed, of
322course). While starting and stopping an I/O watcher does not cause an 487course). While starting and stopping an I/O watcher does not cause an
323extra syscall as with epoll, it still adds up to four event changes per 488extra syscall as with epoll, it still adds up to four event changes per
… …
346.Sp 511.Sp
347If one or more of these are ored into the flags value, then only these 512If one or more of these are ored into the flags value, then only these
348backends will be tried (in the reverse order as given here). If none are 513backends will be tried (in the reverse order as given here). If none are
349specified, most compiled-in backend will be tried, usually in reverse 514specified, most compiled-in backend will be tried, usually in reverse
350order of their flag values :) 515order of their flag values :)
516.Sp
517The most typical usage is like this:
518.Sp
519.Vb 2
520\& if (!ev_default_loop (0))
521\& fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");
522.Ve
523.Sp
524Restrict libev to the select and poll backends, and do not allow
525environment settings to be taken into account:
526.Sp
527.Vb 1
528\& ev_default_loop (EVBACKEND_POLL | EVBACKEND_SELECT | EVFLAG_NOENV);
529.Ve
530.Sp
531Use whatever libev has to offer, but make sure that kqueue is used if
532available (warning, breaks stuff, best use only with your own private
533event loop and only if you know the \s-1OS\s0 supports your types of fds):
534.Sp
535.Vb 1
536\& ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE);
537.Ve
351.RE 538.RE
352.IP "struct ev_loop *ev_loop_new (unsigned int flags)" 4 539.IP "struct ev_loop *ev_loop_new (unsigned int flags)" 4
353.IX Item "struct ev_loop *ev_loop_new (unsigned int flags)" 540.IX Item "struct ev_loop *ev_loop_new (unsigned int flags)"
354Similar to \f(CW\*(C`ev_default_loop\*(C'\fR, but always creates a new event loop that is 541Similar to \f(CW\*(C`ev_default_loop\*(C'\fR, but always creates a new event loop that is
355always distinct from the default loop. Unlike the default loop, it cannot 542always distinct from the default loop. Unlike the default loop, it cannot
356handle signal and child watchers, and attempts to do so will be greeted by 543handle signal and child watchers, and attempts to do so will be greeted by
357undefined behaviour (or a failed assertion if assertions are enabled). 544undefined behaviour (or a failed assertion if assertions are enabled).
545.Sp
546Example: Try to create a event loop that uses epoll and nothing else.
547.Sp
548.Vb 3
549\& struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV);
550\& if (!epoller)
551\& fatal ("no epoll found here, maybe it hides under your chair");
552.Ve
358.IP "ev_default_destroy ()" 4 553.IP "ev_default_destroy ()" 4
359.IX Item "ev_default_destroy ()" 554.IX Item "ev_default_destroy ()"
360Destroys the default loop again (frees all memory and kernel state 555Destroys the default loop again (frees all memory and kernel state
361etc.). This stops all registered event watchers (by not touching them in 556etc.). None of the active event watchers will be stopped in the normal
362any way whatsoever, although you cannot rely on this :). 557sense, so e.g. \f(CW\*(C`ev_is_active\*(C'\fR might still return true. It is your
558responsibility to either stop all watchers cleanly yoursef \fIbefore\fR
559calling this function, or cope with the fact afterwards (which is usually
560the easiest thing, youc na just ignore the watchers and/or \f(CW\*(C`free ()\*(C'\fR them
561for example).
363.IP "ev_loop_destroy (loop)" 4 562.IP "ev_loop_destroy (loop)" 4
364.IX Item "ev_loop_destroy (loop)" 563.IX Item "ev_loop_destroy (loop)"
365Like \f(CW\*(C`ev_default_destroy\*(C'\fR, but destroys an event loop created by an 564Like \f(CW\*(C`ev_default_destroy\*(C'\fR, but destroys an event loop created by an
366earlier call to \f(CW\*(C`ev_loop_new\*(C'\fR. 565earlier call to \f(CW\*(C`ev_loop_new\*(C'\fR.
367.IP "ev_default_fork ()" 4 566.IP "ev_default_fork ()" 4
… …
389.IP "ev_loop_fork (loop)" 4 588.IP "ev_loop_fork (loop)" 4
390.IX Item "ev_loop_fork (loop)" 589.IX Item "ev_loop_fork (loop)"
391Like \f(CW\*(C`ev_default_fork\*(C'\fR, but acts on an event loop created by 590Like \f(CW\*(C`ev_default_fork\*(C'\fR, but acts on an event loop created by
392\&\f(CW\*(C`ev_loop_new\*(C'\fR. Yes, you have to call this on every allocated event loop 591\&\f(CW\*(C`ev_loop_new\*(C'\fR. Yes, you have to call this on every allocated event loop
393after fork, and how you do this is entirely your own problem. 592after fork, and how you do this is entirely your own problem.
593.IP "unsigned int ev_loop_count (loop)" 4
594.IX Item "unsigned int ev_loop_count (loop)"
595Returns the count of loop iterations for the loop, which is identical to
596the number of times libev did poll for new events. It starts at \f(CW0\fR and
597happily wraps around with enough iterations.
598.Sp
599This value can sometimes be useful as a generation counter of sorts (it
600\&\*(L"ticks\*(R" the number of loop iterations), as it roughly corresponds with
601\&\f(CW\*(C`ev_prepare\*(C'\fR and \f(CW\*(C`ev_check\*(C'\fR calls.
394.IP "unsigned int ev_backend (loop)" 4 602.IP "unsigned int ev_backend (loop)" 4
395.IX Item "unsigned int ev_backend (loop)" 603.IX Item "unsigned int ev_backend (loop)"
396Returns one of the \f(CW\*(C`EVBACKEND_*\*(C'\fR flags indicating the event backend in 604Returns one of the \f(CW\*(C`EVBACKEND_*\*(C'\fR flags indicating the event backend in
397use. 605use.
398.IP "ev_tstamp ev_now (loop)" 4 606.IP "ev_tstamp ev_now (loop)" 4
399.IX Item "ev_tstamp ev_now (loop)" 607.IX Item "ev_tstamp ev_now (loop)"
400Returns the current \*(L"event loop time\*(R", which is the time the event loop 608Returns the current \*(L"event loop time\*(R", which is the time the event loop
401got events and started processing them. This timestamp does not change 609received events and started processing them. This timestamp does not
402as long as callbacks are being processed, and this is also the base time 610change as long as callbacks are being processed, and this is also the base
403used for relative timers. You can treat it as the timestamp of the event 611time used for relative timers. You can treat it as the timestamp of the
404occuring (or more correctly, the mainloop finding out about it). 612event occuring (or more correctly, libev finding out about it).
405.IP "ev_loop (loop, int flags)" 4 613.IP "ev_loop (loop, int flags)" 4
406.IX Item "ev_loop (loop, int flags)" 614.IX Item "ev_loop (loop, int flags)"
407Finally, this is it, the event handler. This function usually is called 615Finally, this is it, the event handler. This function usually is called
408after you initialised all your watchers and you want to start handling 616after you initialised all your watchers and you want to start handling
409events. 617events.
410.Sp 618.Sp
411If the flags argument is specified as 0, it will not return until either 619If the flags argument is specified as \f(CW0\fR, it will not return until
412no event watchers are active anymore or \f(CW\*(C`ev_unloop\*(C'\fR was called. 620either no event watchers are active anymore or \f(CW\*(C`ev_unloop\*(C'\fR was called.
621.Sp
622Please note that an explicit \f(CW\*(C`ev_unloop\*(C'\fR is usually better than
623relying on all watchers to be stopped when deciding when a program has
624finished (especially in interactive programs), but having a program that
625automatically loops as long as it has to and no longer by virtue of
626relying on its watchers stopping correctly is a thing of beauty.
413.Sp 627.Sp
414A flags value of \f(CW\*(C`EVLOOP_NONBLOCK\*(C'\fR will look for new events, will handle 628A flags value of \f(CW\*(C`EVLOOP_NONBLOCK\*(C'\fR will look for new events, will handle
415those events and any outstanding ones, but will not block your process in 629those events and any outstanding ones, but will not block your process in
416case there are no events and will return after one iteration of the loop. 630case there are no events and will return after one iteration of the loop.
417.Sp 631.Sp
418A flags value of \f(CW\*(C`EVLOOP_ONESHOT\*(C'\fR will look for new events (waiting if 632A flags value of \f(CW\*(C`EVLOOP_ONESHOT\*(C'\fR will look for new events (waiting if
419neccessary) and will handle those and any outstanding ones. It will block 633neccessary) and will handle those and any outstanding ones. It will block
420your process until at least one new event arrives, and will return after 634your process until at least one new event arrives, and will return after
421one iteration of the loop. 635one iteration of the loop. This is useful if you are waiting for some
636external event in conjunction with something not expressible using other
637libev watchers. However, a pair of \f(CW\*(C`ev_prepare\*(C'\fR/\f(CW\*(C`ev_check\*(C'\fR watchers is
638usually a better approach for this kind of thing.
422.Sp 639.Sp
423This flags value could be used to implement alternative looping
424constructs, but the \f(CW\*(C`prepare\*(C'\fR and \f(CW\*(C`check\*(C'\fR watchers provide a better and
425more generic mechanism.
426.Sp
427Here are the gory details of what ev_loop does: 640Here are the gory details of what \f(CW\*(C`ev_loop\*(C'\fR does:
428.Sp 641.Sp
429.Vb 15 642.Vb 19
643\& - Before the first iteration, call any pending watchers.
430\& 1. If there are no active watchers (reference count is zero), return. 644\& * If there are no active watchers (reference count is zero), return.
431\& 2. Queue and immediately call all prepare watchers. 645\& - Queue all prepare watchers and then call all outstanding watchers.
432\& 3. If we have been forked, recreate the kernel state. 646\& - If we have been forked, recreate the kernel state.
433\& 4. Update the kernel state with all outstanding changes. 647\& - Update the kernel state with all outstanding changes.
434\& 5. Update the "event loop time". 648\& - Update the "event loop time".
435\& 6. Calculate for how long to block. 649\& - Calculate for how long to block.
436\& 7. Block the process, waiting for events. 650\& - Block the process, waiting for any events.
651\& - Queue all outstanding I/O (fd) events.
437\& 8. Update the "event loop time" and do time jump handling. 652\& - Update the "event loop time" and do time jump handling.
438\& 9. Queue all outstanding timers. 653\& - Queue all outstanding timers.
439\& 10. Queue all outstanding periodics. 654\& - Queue all outstanding periodics.
440\& 11. If no events are pending now, queue all idle watchers. 655\& - If no events are pending now, queue all idle watchers.
441\& 12. Queue all check watchers. 656\& - Queue all check watchers.
442\& 13. Call all queued watchers in reverse order (i.e. check watchers first). 657\& - Call all queued watchers in reverse order (i.e. check watchers first).
658\& Signals and child watchers are implemented as I/O watchers, and will
659\& be handled here by queueing them when their watcher gets executed.
443\& 14. If ev_unloop has been called or EVLOOP_ONESHOT or EVLOOP_NONBLOCK 660\& - If ev_unloop has been called or EVLOOP_ONESHOT or EVLOOP_NONBLOCK
444\& was used, return, otherwise continue with step #1. 661\& were used, return, otherwise continue with step *.
662.Ve
663.Sp
664Example: Queue some jobs and then loop until no events are outsanding
665anymore.
666.Sp
667.Vb 4
668\& ... queue jobs here, make sure they register event watchers as long
669\& ... as they still have work to do (even an idle watcher will do..)
670\& ev_loop (my_loop, 0);
671\& ... jobs done. yeah!
445.Ve 672.Ve
446.IP "ev_unloop (loop, how)" 4 673.IP "ev_unloop (loop, how)" 4
447.IX Item "ev_unloop (loop, how)" 674.IX Item "ev_unloop (loop, how)"
448Can be used to make a call to \f(CW\*(C`ev_loop\*(C'\fR return early (but only after it 675Can be used to make a call to \f(CW\*(C`ev_loop\*(C'\fR return early (but only after it
449has processed all outstanding events). The \f(CW\*(C`how\*(C'\fR argument must be either 676has processed all outstanding events). The \f(CW\*(C`how\*(C'\fR argument must be either
… …
463example, libev itself uses this for its internal signal pipe: It is not 690example, libev itself uses this for its internal signal pipe: It is not
464visible to the libev user and should not keep \f(CW\*(C`ev_loop\*(C'\fR from exiting if 691visible to the libev user and should not keep \f(CW\*(C`ev_loop\*(C'\fR from exiting if
465no event watchers registered by it are active. It is also an excellent 692no event watchers registered by it are active. It is also an excellent
466way to do this for generic recurring timers or from within third-party 693way to do this for generic recurring timers or from within third-party
467libraries. Just remember to \fIunref after start\fR and \fIref before stop\fR. 694libraries. Just remember to \fIunref after start\fR and \fIref before stop\fR.
695.Sp
696Example: Create a signal watcher, but keep it from keeping \f(CW\*(C`ev_loop\*(C'\fR
697running when nothing else is active.
698.Sp
699.Vb 4
700\& struct ev_signal exitsig;
701\& ev_signal_init (&exitsig, sig_cb, SIGINT);
702\& ev_signal_start (loop, &exitsig);
703\& evf_unref (loop);
704.Ve
705.Sp
706Example: For some weird reason, unregister the above signal handler again.
707.Sp
708.Vb 2
709\& ev_ref (loop);
710\& ev_signal_stop (loop, &exitsig);
711.Ve
468.SH "ANATOMY OF A WATCHER" 712.SH "ANATOMY OF A WATCHER"
469.IX Header "ANATOMY OF A WATCHER" 713.IX Header "ANATOMY OF A WATCHER"
470A watcher is a structure that you create and register to record your 714A watcher is a structure that you create and register to record your
471interest in some event. For instance, if you want to wait for \s-1STDIN\s0 to 715interest in some event. For instance, if you want to wait for \s-1STDIN\s0 to
472become readable, you would create an \f(CW\*(C`ev_io\*(C'\fR watcher for that: 716become readable, you would create an \f(CW\*(C`ev_io\*(C'\fR watcher for that:
… …
508*)\*(C'\fR), and you can stop watching for events at any time by calling the 752*)\*(C'\fR), and you can stop watching for events at any time by calling the
509corresponding stop function (\f(CW\*(C`ev_<type>_stop (loop, watcher *)\*(C'\fR. 753corresponding stop function (\f(CW\*(C`ev_<type>_stop (loop, watcher *)\*(C'\fR.
510.PP 754.PP
511As long as your watcher is active (has been started but not stopped) you 755As long as your watcher is active (has been started but not stopped) you
512must not touch the values stored in it. Most specifically you must never 756must not touch the values stored in it. Most specifically you must never
513reinitialise it or call its set macro. 757reinitialise it or call its \f(CW\*(C`set\*(C'\fR macro.
514.PP
515You can check whether an event is active by calling the \f(CW\*(C`ev_is_active
516(watcher *)\*(C'\fR macro. To see whether an event is outstanding (but the
517callback for it has not been called yet) you can use the \f(CW\*(C`ev_is_pending
518(watcher *)\*(C'\fR macro.
519.PP 758.PP
520Each and every callback receives the event loop pointer as first, the 759Each and every callback receives the event loop pointer as first, the
521registered watcher structure as second, and a bitset of received events as 760registered watcher structure as second, and a bitset of received events as
522third argument. 761third argument.
523.PP 762.PP
… …
548The signal specified in the \f(CW\*(C`ev_signal\*(C'\fR watcher has been received by a thread. 787The signal specified in the \f(CW\*(C`ev_signal\*(C'\fR watcher has been received by a thread.
549.ie n .IP """EV_CHILD""" 4 788.ie n .IP """EV_CHILD""" 4
550.el .IP "\f(CWEV_CHILD\fR" 4 789.el .IP "\f(CWEV_CHILD\fR" 4
551.IX Item "EV_CHILD" 790.IX Item "EV_CHILD"
552The pid specified in the \f(CW\*(C`ev_child\*(C'\fR watcher has received a status change. 791The pid specified in the \f(CW\*(C`ev_child\*(C'\fR watcher has received a status change.
792.ie n .IP """EV_STAT""" 4
793.el .IP "\f(CWEV_STAT\fR" 4
794.IX Item "EV_STAT"
795The path specified in the \f(CW\*(C`ev_stat\*(C'\fR watcher changed its attributes somehow.
553.ie n .IP """EV_IDLE""" 4 796.ie n .IP """EV_IDLE""" 4
554.el .IP "\f(CWEV_IDLE\fR" 4 797.el .IP "\f(CWEV_IDLE\fR" 4
555.IX Item "EV_IDLE" 798.IX Item "EV_IDLE"
556The \f(CW\*(C`ev_idle\*(C'\fR watcher has determined that you have nothing better to do. 799The \f(CW\*(C`ev_idle\*(C'\fR watcher has determined that you have nothing better to do.
557.ie n .IP """EV_PREPARE""" 4 800.ie n .IP """EV_PREPARE""" 4
… …
567\&\f(CW\*(C`ev_loop\*(C'\fR has gathered them, but before it invokes any callbacks for any 810\&\f(CW\*(C`ev_loop\*(C'\fR has gathered them, but before it invokes any callbacks for any
568received events. Callbacks of both watcher types can start and stop as 811received events. Callbacks of both watcher types can start and stop as
569many watchers as they want, and all of them will be taken into account 812many watchers as they want, and all of them will be taken into account
570(for example, a \f(CW\*(C`ev_prepare\*(C'\fR watcher might start an idle watcher to keep 813(for example, a \f(CW\*(C`ev_prepare\*(C'\fR watcher might start an idle watcher to keep
571\&\f(CW\*(C`ev_loop\*(C'\fR from blocking). 814\&\f(CW\*(C`ev_loop\*(C'\fR from blocking).
815.ie n .IP """EV_EMBED""" 4
816.el .IP "\f(CWEV_EMBED\fR" 4
817.IX Item "EV_EMBED"
818The embedded event loop specified in the \f(CW\*(C`ev_embed\*(C'\fR watcher needs attention.
819.ie n .IP """EV_FORK""" 4
820.el .IP "\f(CWEV_FORK\fR" 4
821.IX Item "EV_FORK"
822The event loop has been resumed in the child process after fork (see
823\&\f(CW\*(C`ev_fork\*(C'\fR).
572.ie n .IP """EV_ERROR""" 4 824.ie n .IP """EV_ERROR""" 4
573.el .IP "\f(CWEV_ERROR\fR" 4 825.el .IP "\f(CWEV_ERROR\fR" 4
574.IX Item "EV_ERROR" 826.IX Item "EV_ERROR"
575An unspecified error has occured, the watcher has been stopped. This might 827An unspecified error has occured, the watcher has been stopped. This might
576happen because the watcher could not be properly started because libev 828happen because the watcher could not be properly started because libev
… …
581Libev will usually signal a few \*(L"dummy\*(R" events together with an error, 833Libev will usually signal a few \*(L"dummy\*(R" events together with an error,
582for example it might indicate that a fd is readable or writable, and if 834for example it might indicate that a fd is readable or writable, and if
583your callbacks is well-written it can just attempt the operation and cope 835your callbacks is well-written it can just attempt the operation and cope
584with the error from \fIread()\fR or \fIwrite()\fR. This will not work in multithreaded 836with the error from \fIread()\fR or \fIwrite()\fR. This will not work in multithreaded
585programs, though, so beware. 837programs, though, so beware.
838.Sh "\s-1GENERIC\s0 \s-1WATCHER\s0 \s-1FUNCTIONS\s0"
839.IX Subsection "GENERIC WATCHER FUNCTIONS"
840In the following description, \f(CW\*(C`TYPE\*(C'\fR stands for the watcher type,
841e.g. \f(CW\*(C`timer\*(C'\fR for \f(CW\*(C`ev_timer\*(C'\fR watchers and \f(CW\*(C`io\*(C'\fR for \f(CW\*(C`ev_io\*(C'\fR watchers.
842.ie n .IP """ev_init"" (ev_TYPE *watcher, callback)" 4
843.el .IP "\f(CWev_init\fR (ev_TYPE *watcher, callback)" 4
844.IX Item "ev_init (ev_TYPE *watcher, callback)"
845This macro initialises the generic portion of a watcher. The contents
846of the watcher object can be arbitrary (so \f(CW\*(C`malloc\*(C'\fR will do). Only
847the generic parts of the watcher are initialised, you \fIneed\fR to call
848the type-specific \f(CW\*(C`ev_TYPE_set\*(C'\fR macro afterwards to initialise the
849type-specific parts. For each type there is also a \f(CW\*(C`ev_TYPE_init\*(C'\fR macro
850which rolls both calls into one.
851.Sp
852You can reinitialise a watcher at any time as long as it has been stopped
853(or never started) and there are no pending events outstanding.
854.Sp
855The callback is always of type \f(CW\*(C`void (*)(ev_loop *loop, ev_TYPE *watcher,
856int revents)\*(C'\fR.
857.ie n .IP """ev_TYPE_set"" (ev_TYPE *, [args])" 4
858.el .IP "\f(CWev_TYPE_set\fR (ev_TYPE *, [args])" 4
859.IX Item "ev_TYPE_set (ev_TYPE *, [args])"
860This macro initialises the type-specific parts of a watcher. You need to
861call \f(CW\*(C`ev_init\*(C'\fR at least once before you call this macro, but you can
862call \f(CW\*(C`ev_TYPE_set\*(C'\fR any number of times. You must not, however, call this
863macro on a watcher that is active (it can be pending, however, which is a
864difference to the \f(CW\*(C`ev_init\*(C'\fR macro).
865.Sp
866Although some watcher types do not have type-specific arguments
867(e.g. \f(CW\*(C`ev_prepare\*(C'\fR) you still need to call its \f(CW\*(C`set\*(C'\fR macro.
868.ie n .IP """ev_TYPE_init"" (ev_TYPE *watcher, callback, [args])" 4
869.el .IP "\f(CWev_TYPE_init\fR (ev_TYPE *watcher, callback, [args])" 4
870.IX Item "ev_TYPE_init (ev_TYPE *watcher, callback, [args])"
871This convinience macro rolls both \f(CW\*(C`ev_init\*(C'\fR and \f(CW\*(C`ev_TYPE_set\*(C'\fR macro
872calls into a single call. This is the most convinient method to initialise
873a watcher. The same limitations apply, of course.
874.ie n .IP """ev_TYPE_start"" (loop *, ev_TYPE *watcher)" 4
875.el .IP "\f(CWev_TYPE_start\fR (loop *, ev_TYPE *watcher)" 4
876.IX Item "ev_TYPE_start (loop *, ev_TYPE *watcher)"
877Starts (activates) the given watcher. Only active watchers will receive
878events. If the watcher is already active nothing will happen.
879.ie n .IP """ev_TYPE_stop"" (loop *, ev_TYPE *watcher)" 4
880.el .IP "\f(CWev_TYPE_stop\fR (loop *, ev_TYPE *watcher)" 4
881.IX Item "ev_TYPE_stop (loop *, ev_TYPE *watcher)"
882Stops the given watcher again (if active) and clears the pending
883status. It is possible that stopped watchers are pending (for example,
884non-repeating timers are being stopped when they become pending), but
885\&\f(CW\*(C`ev_TYPE_stop\*(C'\fR ensures that the watcher is neither active nor pending. If
886you want to free or reuse the memory used by the watcher it is therefore a
887good idea to always call its \f(CW\*(C`ev_TYPE_stop\*(C'\fR function.
888.IP "bool ev_is_active (ev_TYPE *watcher)" 4
889.IX Item "bool ev_is_active (ev_TYPE *watcher)"
890Returns a true value iff the watcher is active (i.e. it has been started
891and not yet been stopped). As long as a watcher is active you must not modify
892it.
893.IP "bool ev_is_pending (ev_TYPE *watcher)" 4
894.IX Item "bool ev_is_pending (ev_TYPE *watcher)"
895Returns a true value iff the watcher is pending, (i.e. it has outstanding
896events but its callback has not yet been invoked). As long as a watcher
897is pending (but not active) you must not call an init function on it (but
898\&\f(CW\*(C`ev_TYPE_set\*(C'\fR is safe), you must not change its priority, and you must
899make sure the watcher is available to libev (e.g. you cannot \f(CW\*(C`free ()\*(C'\fR
900it).
901.IP "callback ev_cb (ev_TYPE *watcher)" 4
902.IX Item "callback ev_cb (ev_TYPE *watcher)"
903Returns the callback currently set on the watcher.
904.IP "ev_cb_set (ev_TYPE *watcher, callback)" 4
905.IX Item "ev_cb_set (ev_TYPE *watcher, callback)"
906Change the callback. You can change the callback at virtually any time
907(modulo threads).
908.IP "ev_set_priority (ev_TYPE *watcher, priority)" 4
909.IX Item "ev_set_priority (ev_TYPE *watcher, priority)"
910.PD 0
911.IP "int ev_priority (ev_TYPE *watcher)" 4
912.IX Item "int ev_priority (ev_TYPE *watcher)"
913.PD
914Set and query the priority of the watcher. The priority is a small
915integer between \f(CW\*(C`EV_MAXPRI\*(C'\fR (default: \f(CW2\fR) and \f(CW\*(C`EV_MINPRI\*(C'\fR
916(default: \f(CW\*(C`\-2\*(C'\fR). Pending watchers with higher priority will be invoked
917before watchers with lower priority, but priority will not keep watchers
918from being executed (except for \f(CW\*(C`ev_idle\*(C'\fR watchers).
919.Sp
920This means that priorities are \fIonly\fR used for ordering callback
921invocation after new events have been received. This is useful, for
922example, to reduce latency after idling, or more often, to bind two
923watchers on the same event and make sure one is called first.
924.Sp
925If you need to suppress invocation when higher priority events are pending
926you need to look at \f(CW\*(C`ev_idle\*(C'\fR watchers, which provide this functionality.
927.Sp
928You \fImust not\fR change the priority of a watcher as long as it is active or
929pending.
930.Sp
931The default priority used by watchers when no priority has been set is
932always \f(CW0\fR, which is supposed to not be too high and not be too low :).
933.Sp
934Setting a priority outside the range of \f(CW\*(C`EV_MINPRI\*(C'\fR to \f(CW\*(C`EV_MAXPRI\*(C'\fR is
935fine, as long as you do not mind that the priority value you query might
936or might not have been adjusted to be within valid range.
937.IP "ev_invoke (loop, ev_TYPE *watcher, int revents)" 4
938.IX Item "ev_invoke (loop, ev_TYPE *watcher, int revents)"
939Invoke the \f(CW\*(C`watcher\*(C'\fR with the given \f(CW\*(C`loop\*(C'\fR and \f(CW\*(C`revents\*(C'\fR. Neither
940\&\f(CW\*(C`loop\*(C'\fR nor \f(CW\*(C`revents\*(C'\fR need to be valid as long as the watcher callback
941can deal with that fact.
942.IP "int ev_clear_pending (loop, ev_TYPE *watcher)" 4
943.IX Item "int ev_clear_pending (loop, ev_TYPE *watcher)"
944If the watcher is pending, this function returns clears its pending status
945and returns its \f(CW\*(C`revents\*(C'\fR bitset (as if its callback was invoked). If the
946watcher isn't pending it does nothing and returns \f(CW0\fR.
586.Sh "\s-1ASSOCIATING\s0 \s-1CUSTOM\s0 \s-1DATA\s0 \s-1WITH\s0 A \s-1WATCHER\s0" 947.Sh "\s-1ASSOCIATING\s0 \s-1CUSTOM\s0 \s-1DATA\s0 \s-1WITH\s0 A \s-1WATCHER\s0"
587.IX Subsection "ASSOCIATING CUSTOM DATA WITH A WATCHER" 948.IX Subsection "ASSOCIATING CUSTOM DATA WITH A WATCHER"
588Each watcher has, by default, a member \f(CW\*(C`void *data\*(C'\fR that you can change 949Each watcher has, by default, a member \f(CW\*(C`void *data\*(C'\fR that you can change
589and read at any time, libev will completely ignore it. This can be used 950and read at any time, libev will completely ignore it. This can be used
590to associate arbitrary data with your watcher. If you need more data and 951to associate arbitrary data with your watcher. If you need more data and
… …
611\& struct my_io *w = (struct my_io *)w_; 972\& struct my_io *w = (struct my_io *)w_;
612\& ... 973\& ...
613\& } 974\& }
614.Ve 975.Ve
615.PP 976.PP
616More interesting and less C\-conformant ways of catsing your callback type 977More interesting and less C\-conformant ways of casting your callback type
617have been omitted.... 978instead have been omitted.
979.PP
980Another common scenario is having some data structure with multiple
981watchers:
982.PP
983.Vb 6
984\& struct my_biggy
985\& {
986\& int some_data;
987\& ev_timer t1;
988\& ev_timer t2;
989\& }
990.Ve
991.PP
992In this case getting the pointer to \f(CW\*(C`my_biggy\*(C'\fR is a bit more complicated,
993you need to use \f(CW\*(C`offsetof\*(C'\fR:
994.PP
995.Vb 1
996\& #include <stddef.h>
997.Ve
998.PP
999.Vb 6
1000\& static void
1001\& t1_cb (EV_P_ struct ev_timer *w, int revents)
1002\& {
1003\& struct my_biggy big = (struct my_biggy *
1004\& (((char *)w) - offsetof (struct my_biggy, t1));
1005\& }
1006.Ve
1007.PP
1008.Vb 6
1009\& static void
1010\& t2_cb (EV_P_ struct ev_timer *w, int revents)
1011\& {
1012\& struct my_biggy big = (struct my_biggy *
1013\& (((char *)w) - offsetof (struct my_biggy, t2));
1014\& }
1015.Ve
618.SH "WATCHER TYPES" 1016.SH "WATCHER TYPES"
619.IX Header "WATCHER TYPES" 1017.IX Header "WATCHER TYPES"
620This section describes each watcher in detail, but will not repeat 1018This section describes each watcher in detail, but will not repeat
621information given in the last section. 1019information given in the last section. Any initialisation/set macros,
1020functions and members specific to the watcher type are explained.
1021.PP
1022Members are additionally marked with either \fI[read\-only]\fR, meaning that,
1023while the watcher is active, you can look at the member and expect some
1024sensible content, but you must not modify it (you can modify it while the
1025watcher is stopped to your hearts content), or \fI[read\-write]\fR, which
1026means you can expect it to have some sensible content while the watcher
1027is active, but you can also modify it. Modifying it may not do something
1028sensible or take immediate effect (or do anything at all), but libev will
1029not crash or malfunction in any way.
622.ie n .Sh """ev_io"" \- is this file descriptor readable or writable" 1030.ie n .Sh """ev_io"" \- is this file descriptor readable or writable?"
623.el .Sh "\f(CWev_io\fP \- is this file descriptor readable or writable" 1031.el .Sh "\f(CWev_io\fP \- is this file descriptor readable or writable?"
624.IX Subsection "ev_io - is this file descriptor readable or writable" 1032.IX Subsection "ev_io - is this file descriptor readable or writable?"
625I/O watchers check whether a file descriptor is readable or writable 1033I/O watchers check whether a file descriptor is readable or writable
626in each iteration of the event loop (This behaviour is called 1034in each iteration of the event loop, or, more precisely, when reading
627level-triggering because you keep receiving events as long as the 1035would not block the process and writing would at least be able to write
628condition persists. Remember you can stop the watcher if you don't want to 1036some data. This behaviour is called level-triggering because you keep
629act on the event and neither want to receive future events). 1037receiving events as long as the condition persists. Remember you can stop
1038the watcher if you don't want to act on the event and neither want to
1039receive future events.
630.PP 1040.PP
631In general you can register as many read and/or write event watchers per 1041In general you can register as many read and/or write event watchers per
632fd as you want (as long as you don't confuse yourself). Setting all file 1042fd as you want (as long as you don't confuse yourself). Setting all file
633descriptors to non-blocking mode is also usually a good idea (but not 1043descriptors to non-blocking mode is also usually a good idea (but not
634required if you know what you are doing). 1044required if you know what you are doing).
635.PP 1045.PP
636You have to be careful with dup'ed file descriptors, though. Some backends 1046You have to be careful with dup'ed file descriptors, though. Some backends
637(the linux epoll backend is a notable example) cannot handle dup'ed file 1047(the linux epoll backend is a notable example) cannot handle dup'ed file
638descriptors correctly if you register interest in two or more fds pointing 1048descriptors correctly if you register interest in two or more fds pointing
639to the same underlying file/socket etc. description (that is, they share 1049to the same underlying file/socket/etc. description (that is, they share
640the same underlying \*(L"file open\*(R"). 1050the same underlying \*(L"file open\*(R").
641.PP 1051.PP
642If you must do this, then force the use of a known-to-be-good backend 1052If you must do this, then force the use of a known-to-be-good backend
643(at the time of this writing, this includes only \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR and 1053(at the time of this writing, this includes only \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR and
644\&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR). 1054\&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR).
1055.PP
1056Another thing you have to watch out for is that it is quite easy to
1057receive \*(L"spurious\*(R" readyness notifications, that is your callback might
1058be called with \f(CW\*(C`EV_READ\*(C'\fR but a subsequent \f(CW\*(C`read\*(C'\fR(2) will actually block
1059because there is no data. Not only are some backends known to create a
1060lot of those (for example solaris ports), it is very easy to get into
1061this situation even with a relatively standard program structure. Thus
1062it is best to always use non-blocking I/O: An extra \f(CW\*(C`read\*(C'\fR(2) returning
1063\&\f(CW\*(C`EAGAIN\*(C'\fR is far preferable to a program hanging until some data arrives.
1064.PP
1065If you cannot run the fd in non-blocking mode (for example you should not
1066play around with an Xlib connection), then you have to seperately re-test
1067whether a file descriptor is really ready with a known-to-be good interface
1068such as poll (fortunately in our Xlib example, Xlib already does this on
1069its own, so its quite safe to use).
1070.PP
1071\fIThe special problem of disappearing file descriptors\fR
1072.IX Subsection "The special problem of disappearing file descriptors"
1073.PP
1074Some backends (e.g kqueue, epoll) need to be told about closing a file
1075descriptor (either by calling \f(CW\*(C`close\*(C'\fR explicitly or by any other means,
1076such as \f(CW\*(C`dup\*(C'\fR). The reason is that you register interest in some file
1077descriptor, but when it goes away, the operating system will silently drop
1078this interest. If another file descriptor with the same number then is
1079registered with libev, there is no efficient way to see that this is, in
1080fact, a different file descriptor.
1081.PP
1082To avoid having to explicitly tell libev about such cases, libev follows
1083the following policy: Each time \f(CW\*(C`ev_io_set\*(C'\fR is being called, libev
1084will assume that this is potentially a new file descriptor, otherwise
1085it is assumed that the file descriptor stays the same. That means that
1086you \fIhave\fR to call \f(CW\*(C`ev_io_set\*(C'\fR (or \f(CW\*(C`ev_io_init\*(C'\fR) when you change the
1087descriptor even if the file descriptor number itself did not change.
1088.PP
1089This is how one would do it normally anyway, the important point is that
1090the libev application should not optimise around libev but should leave
1091optimisations to libev.
1092.PP
1093\fIWatcher-Specific Functions\fR
1094.IX Subsection "Watcher-Specific Functions"
645.IP "ev_io_init (ev_io *, callback, int fd, int events)" 4 1095.IP "ev_io_init (ev_io *, callback, int fd, int events)" 4
646.IX Item "ev_io_init (ev_io *, callback, int fd, int events)" 1096.IX Item "ev_io_init (ev_io *, callback, int fd, int events)"
647.PD 0 1097.PD 0
648.IP "ev_io_set (ev_io *, int fd, int events)" 4 1098.IP "ev_io_set (ev_io *, int fd, int events)" 4
649.IX Item "ev_io_set (ev_io *, int fd, int events)" 1099.IX Item "ev_io_set (ev_io *, int fd, int events)"
650.PD 1100.PD
651Configures an \f(CW\*(C`ev_io\*(C'\fR watcher. The fd is the file descriptor to rceeive 1101Configures an \f(CW\*(C`ev_io\*(C'\fR watcher. The \f(CW\*(C`fd\*(C'\fR is the file descriptor to
652events for and events is either \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR or \f(CW\*(C`EV_READ | 1102rceeive events for and events is either \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR or
653EV_WRITE\*(C'\fR to receive the given events. 1103\&\f(CW\*(C`EV_READ | EV_WRITE\*(C'\fR to receive the given events.
654.Sp 1104.IP "int fd [read\-only]" 4
655Please note that most of the more scalable backend mechanisms (for example 1105.IX Item "int fd [read-only]"
656epoll and solaris ports) can result in spurious readyness notifications 1106The file descriptor being watched.
657for file descriptors, so you practically need to use non-blocking I/O (and 1107.IP "int events [read\-only]" 4
658treat callback invocation as hint only), or retest separately with a safe 1108.IX Item "int events [read-only]"
659interface before doing I/O (XLib can do this), or force the use of either 1109The events being watched.
660\&\f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or \f(CW\*(C`EVBACKEND_POLL\*(C'\fR, which don't suffer from this 1110.PP
661problem. Also note that it is quite easy to have your callback invoked 1111Example: Call \f(CW\*(C`stdin_readable_cb\*(C'\fR when \s-1STDIN_FILENO\s0 has become, well
662when the readyness condition is no longer valid even when employing 1112readable, but only once. Since it is likely line\-buffered, you could
663typical ways of handling events, so its a good idea to use non-blocking 1113attempt to read a whole line in the callback.
664I/O unconditionally. 1114.PP
1115.Vb 6
1116\& static void
1117\& stdin_readable_cb (struct ev_loop *loop, struct ev_io *w, int revents)
1118\& {
1119\& ev_io_stop (loop, w);
1120\& .. read from stdin here (or from w->fd) and haqndle any I/O errors
1121\& }
1122.Ve
1123.PP
1124.Vb 6
1125\& ...
1126\& struct ev_loop *loop = ev_default_init (0);
1127\& struct ev_io stdin_readable;
1128\& ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ);
1129\& ev_io_start (loop, &stdin_readable);
1130\& ev_loop (loop, 0);
1131.Ve
665.ie n .Sh """ev_timer"" \- relative and optionally recurring timeouts" 1132.ie n .Sh """ev_timer"" \- relative and optionally repeating timeouts"
666.el .Sh "\f(CWev_timer\fP \- relative and optionally recurring timeouts" 1133.el .Sh "\f(CWev_timer\fP \- relative and optionally repeating timeouts"
667.IX Subsection "ev_timer - relative and optionally recurring timeouts" 1134.IX Subsection "ev_timer - relative and optionally repeating timeouts"
668Timer watchers are simple relative timers that generate an event after a 1135Timer watchers are simple relative timers that generate an event after a
669given time, and optionally repeating in regular intervals after that. 1136given time, and optionally repeating in regular intervals after that.
670.PP 1137.PP
671The timers are based on real time, that is, if you register an event that 1138The timers are based on real time, that is, if you register an event that
672times out after an hour and you reset your system clock to last years 1139times out after an hour and you reset your system clock to last years
… …
685.Ve 1152.Ve
686.PP 1153.PP
687The callback is guarenteed to be invoked only when its timeout has passed, 1154The callback is guarenteed to be invoked only when its timeout has passed,
688but if multiple timers become ready during the same loop iteration then 1155but if multiple timers become ready during the same loop iteration then
689order of execution is undefined. 1156order of execution is undefined.
1157.PP
1158\fIWatcher-Specific Functions and Data Members\fR
1159.IX Subsection "Watcher-Specific Functions and Data Members"
690.IP "ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)" 4 1160.IP "ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)" 4
691.IX Item "ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)" 1161.IX Item "ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)"
692.PD 0 1162.PD 0
693.IP "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" 4 1163.IP "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" 4
694.IX Item "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)" 1164.IX Item "ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)"
… …
706.IP "ev_timer_again (loop)" 4 1176.IP "ev_timer_again (loop)" 4
707.IX Item "ev_timer_again (loop)" 1177.IX Item "ev_timer_again (loop)"
708This will act as if the timer timed out and restart it again if it is 1178This will act as if the timer timed out and restart it again if it is
709repeating. The exact semantics are: 1179repeating. The exact semantics are:
710.Sp 1180.Sp
1181If the timer is pending, its pending status is cleared.
1182.Sp
711If the timer is started but nonrepeating, stop it. 1183If the timer is started but nonrepeating, stop it (as if it timed out).
712.Sp 1184.Sp
713If the timer is repeating, either start it if necessary (with the repeat 1185If the timer is repeating, either start it if necessary (with the
714value), or reset the running timer to the repeat value. 1186\&\f(CW\*(C`repeat\*(C'\fR value), or reset the running timer to the \f(CW\*(C`repeat\*(C'\fR value.
715.Sp 1187.Sp
716This sounds a bit complicated, but here is a useful and typical 1188This sounds a bit complicated, but here is a useful and typical
717example: Imagine you have a tcp connection and you want a so-called idle 1189example: Imagine you have a tcp connection and you want a so-called idle
718timeout, that is, you want to be called when there have been, say, 60 1190timeout, that is, you want to be called when there have been, say, 60
719seconds of inactivity on the socket. The easiest way to do this is to 1191seconds of inactivity on the socket. The easiest way to do this is to
720configure an \f(CW\*(C`ev_timer\*(C'\fR with after=repeat=60 and calling ev_timer_again each 1192configure an \f(CW\*(C`ev_timer\*(C'\fR with a \f(CW\*(C`repeat\*(C'\fR value of \f(CW60\fR and then call
721time you successfully read or write some data. If you go into an idle 1193\&\f(CW\*(C`ev_timer_again\*(C'\fR each time you successfully read or write some data. If
722state where you do not expect data to travel on the socket, you can stop 1194you go into an idle state where you do not expect data to travel on the
723the timer, and again will automatically restart it if need be. 1195socket, you can \f(CW\*(C`ev_timer_stop\*(C'\fR the timer, and \f(CW\*(C`ev_timer_again\*(C'\fR will
1196automatically restart it if need be.
1197.Sp
1198That means you can ignore the \f(CW\*(C`after\*(C'\fR value and \f(CW\*(C`ev_timer_start\*(C'\fR
1199altogether and only ever use the \f(CW\*(C`repeat\*(C'\fR value and \f(CW\*(C`ev_timer_again\*(C'\fR:
1200.Sp
1201.Vb 8
1202\& ev_timer_init (timer, callback, 0., 5.);
1203\& ev_timer_again (loop, timer);
1204\& ...
1205\& timer->again = 17.;
1206\& ev_timer_again (loop, timer);
1207\& ...
1208\& timer->again = 10.;
1209\& ev_timer_again (loop, timer);
1210.Ve
1211.Sp
1212This is more slightly efficient then stopping/starting the timer each time
1213you want to modify its timeout value.
1214.IP "ev_tstamp repeat [read\-write]" 4
1215.IX Item "ev_tstamp repeat [read-write]"
1216The current \f(CW\*(C`repeat\*(C'\fR value. Will be used each time the watcher times out
1217or \f(CW\*(C`ev_timer_again\*(C'\fR is called and determines the next timeout (if any),
1218which is also when any modifications are taken into account.
1219.PP
1220Example: Create a timer that fires after 60 seconds.
1221.PP
1222.Vb 5
1223\& static void
1224\& one_minute_cb (struct ev_loop *loop, struct ev_timer *w, int revents)
1225\& {
1226\& .. one minute over, w is actually stopped right here
1227\& }
1228.Ve
1229.PP
1230.Vb 3
1231\& struct ev_timer mytimer;
1232\& ev_timer_init (&mytimer, one_minute_cb, 60., 0.);
1233\& ev_timer_start (loop, &mytimer);
1234.Ve
1235.PP
1236Example: Create a timeout timer that times out after 10 seconds of
1237inactivity.
1238.PP
1239.Vb 5
1240\& static void
1241\& timeout_cb (struct ev_loop *loop, struct ev_timer *w, int revents)
1242\& {
1243\& .. ten seconds without any activity
1244\& }
1245.Ve
1246.PP
1247.Vb 4
1248\& struct ev_timer mytimer;
1249\& ev_timer_init (&mytimer, timeout_cb, 0., 10.); /* note, only repeat used */
1250\& ev_timer_again (&mytimer); /* start timer */
1251\& ev_loop (loop, 0);
1252.Ve
1253.PP
1254.Vb 3
1255\& // and in some piece of code that gets executed on any "activity":
1256\& // reset the timeout to start ticking again at 10 seconds
1257\& ev_timer_again (&mytimer);
1258.Ve
724.ie n .Sh """ev_periodic"" \- to cron or not to cron" 1259.ie n .Sh """ev_periodic"" \- to cron or not to cron?"
725.el .Sh "\f(CWev_periodic\fP \- to cron or not to cron" 1260.el .Sh "\f(CWev_periodic\fP \- to cron or not to cron?"
726.IX Subsection "ev_periodic - to cron or not to cron" 1261.IX Subsection "ev_periodic - to cron or not to cron?"
727Periodic watchers are also timers of a kind, but they are very versatile 1262Periodic watchers are also timers of a kind, but they are very versatile
728(and unfortunately a bit complex). 1263(and unfortunately a bit complex).
729.PP 1264.PP
730Unlike \f(CW\*(C`ev_timer\*(C'\fR's, they are not based on real time (or relative time) 1265Unlike \f(CW\*(C`ev_timer\*(C'\fR's, they are not based on real time (or relative time)
731but on wallclock time (absolute time). You can tell a periodic watcher 1266but on wallclock time (absolute time). You can tell a periodic watcher
732to trigger \*(L"at\*(R" some specific point in time. For example, if you tell a 1267to trigger \*(L"at\*(R" some specific point in time. For example, if you tell a
733periodic watcher to trigger in 10 seconds (by specifiying e.g. c<ev_now () 1268periodic watcher to trigger in 10 seconds (by specifiying e.g. \f(CW\*(C`ev_now ()
734+ 10.>) and then reset your system clock to the last year, then it will 1269+ 10.\*(C'\fR) and then reset your system clock to the last year, then it will
735take a year to trigger the event (unlike an \f(CW\*(C`ev_timer\*(C'\fR, which would trigger 1270take a year to trigger the event (unlike an \f(CW\*(C`ev_timer\*(C'\fR, which would trigger
736roughly 10 seconds later and of course not if you reset your system time 1271roughly 10 seconds later).
737again).
738.PP 1272.PP
739They can also be used to implement vastly more complex timers, such as 1273They can also be used to implement vastly more complex timers, such as
740triggering an event on eahc midnight, local time. 1274triggering an event on each midnight, local time or other, complicated,
1275rules.
741.PP 1276.PP
742As with timers, the callback is guarenteed to be invoked only when the 1277As with timers, the callback is guarenteed to be invoked only when the
743time (\f(CW\*(C`at\*(C'\fR) has been passed, but if multiple periodic timers become ready 1278time (\f(CW\*(C`at\*(C'\fR) has been passed, but if multiple periodic timers become ready
744during the same loop iteration then order of execution is undefined. 1279during the same loop iteration then order of execution is undefined.
1280.PP
1281\fIWatcher-Specific Functions and Data Members\fR
1282.IX Subsection "Watcher-Specific Functions and Data Members"
745.IP "ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)" 4 1283.IP "ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)" 4
746.IX Item "ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)" 1284.IX Item "ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)"
747.PD 0 1285.PD 0
748.IP "ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)" 4 1286.IP "ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)" 4
749.IX Item "ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)" 1287.IX Item "ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)"
750.PD 1288.PD
751Lots of arguments, lets sort it out... There are basically three modes of 1289Lots of arguments, lets sort it out... There are basically three modes of
752operation, and we will explain them from simplest to complex: 1290operation, and we will explain them from simplest to complex:
753.RS 4 1291.RS 4
754.IP "* absolute timer (interval = reschedule_cb = 0)" 4 1292.IP "* absolute timer (at = time, interval = reschedule_cb = 0)" 4
755.IX Item "absolute timer (interval = reschedule_cb = 0)" 1293.IX Item "absolute timer (at = time, interval = reschedule_cb = 0)"
756In this configuration the watcher triggers an event at the wallclock time 1294In this configuration the watcher triggers an event at the wallclock time
757\&\f(CW\*(C`at\*(C'\fR and doesn't repeat. It will not adjust when a time jump occurs, 1295\&\f(CW\*(C`at\*(C'\fR and doesn't repeat. It will not adjust when a time jump occurs,
758that is, if it is to be run at January 1st 2011 then it will run when the 1296that is, if it is to be run at January 1st 2011 then it will run when the
759system time reaches or surpasses this time. 1297system time reaches or surpasses this time.
760.IP "* non-repeating interval timer (interval > 0, reschedule_cb = 0)" 4 1298.IP "* non-repeating interval timer (at = offset, interval > 0, reschedule_cb = 0)" 4
761.IX Item "non-repeating interval timer (interval > 0, reschedule_cb = 0)" 1299.IX Item "non-repeating interval timer (at = offset, interval > 0, reschedule_cb = 0)"
762In this mode the watcher will always be scheduled to time out at the next 1300In this mode the watcher will always be scheduled to time out at the next
763\&\f(CW\*(C`at + N * interval\*(C'\fR time (for some integer N) and then repeat, regardless 1301\&\f(CW\*(C`at + N * interval\*(C'\fR time (for some integer N, which can also be negative)
764of any time jumps. 1302and then repeat, regardless of any time jumps.
765.Sp 1303.Sp
766This can be used to create timers that do not drift with respect to system 1304This can be used to create timers that do not drift with respect to system
767time: 1305time:
768.Sp 1306.Sp
769.Vb 1 1307.Vb 1
… …
776by 3600. 1314by 3600.
777.Sp 1315.Sp
778Another way to think about it (for the mathematically inclined) is that 1316Another way to think about it (for the mathematically inclined) is that
779\&\f(CW\*(C`ev_periodic\*(C'\fR will try to run the callback in this mode at the next possible 1317\&\f(CW\*(C`ev_periodic\*(C'\fR will try to run the callback in this mode at the next possible
780time where \f(CW\*(C`time = at (mod interval)\*(C'\fR, regardless of any time jumps. 1318time where \f(CW\*(C`time = at (mod interval)\*(C'\fR, regardless of any time jumps.
1319.Sp
1320For numerical stability it is preferable that the \f(CW\*(C`at\*(C'\fR value is near
1321\&\f(CW\*(C`ev_now ()\*(C'\fR (the current time), but there is no range requirement for
1322this value.
781.IP "* manual reschedule mode (reschedule_cb = callback)" 4 1323.IP "* manual reschedule mode (at and interval ignored, reschedule_cb = callback)" 4
782.IX Item "manual reschedule mode (reschedule_cb = callback)" 1324.IX Item "manual reschedule mode (at and interval ignored, reschedule_cb = callback)"
783In this mode the values for \f(CW\*(C`interval\*(C'\fR and \f(CW\*(C`at\*(C'\fR are both being 1325In this mode the values for \f(CW\*(C`interval\*(C'\fR and \f(CW\*(C`at\*(C'\fR are both being
784ignored. Instead, each time the periodic watcher gets scheduled, the 1326ignored. Instead, each time the periodic watcher gets scheduled, the
785reschedule callback will be called with the watcher as first, and the 1327reschedule callback will be called with the watcher as first, and the
786current time as second argument. 1328current time as second argument.
787.Sp 1329.Sp
788\&\s-1NOTE:\s0 \fIThis callback \s-1MUST\s0 \s-1NOT\s0 stop or destroy any periodic watcher, 1330\&\s-1NOTE:\s0 \fIThis callback \s-1MUST\s0 \s-1NOT\s0 stop or destroy any periodic watcher,
789ever, or make any event loop modifications\fR. If you need to stop it, 1331ever, or make any event loop modifications\fR. If you need to stop it,
790return \f(CW\*(C`now + 1e30\*(C'\fR (or so, fudge fudge) and stop it afterwards (e.g. by 1332return \f(CW\*(C`now + 1e30\*(C'\fR (or so, fudge fudge) and stop it afterwards (e.g. by
791starting a prepare watcher). 1333starting an \f(CW\*(C`ev_prepare\*(C'\fR watcher, which is legal).
792.Sp 1334.Sp
793Its prototype is \f(CW\*(C`ev_tstamp (*reschedule_cb)(struct ev_periodic *w, 1335Its prototype is \f(CW\*(C`ev_tstamp (*reschedule_cb)(struct ev_periodic *w,
794ev_tstamp now)\*(C'\fR, e.g.: 1336ev_tstamp now)\*(C'\fR, e.g.:
795.Sp 1337.Sp
796.Vb 4 1338.Vb 4
… …
820.IX Item "ev_periodic_again (loop, ev_periodic *)" 1362.IX Item "ev_periodic_again (loop, ev_periodic *)"
821Simply stops and restarts the periodic watcher again. This is only useful 1363Simply stops and restarts the periodic watcher again. This is only useful
822when you changed some parameters or the reschedule callback would return 1364when you changed some parameters or the reschedule callback would return
823a different time than the last time it was called (e.g. in a crond like 1365a different time than the last time it was called (e.g. in a crond like
824program when the crontabs have changed). 1366program when the crontabs have changed).
1367.IP "ev_tstamp offset [read\-write]" 4
1368.IX Item "ev_tstamp offset [read-write]"
1369When repeating, this contains the offset value, otherwise this is the
1370absolute point in time (the \f(CW\*(C`at\*(C'\fR value passed to \f(CW\*(C`ev_periodic_set\*(C'\fR).
1371.Sp
1372Can be modified any time, but changes only take effect when the periodic
1373timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being called.
1374.IP "ev_tstamp interval [read\-write]" 4
1375.IX Item "ev_tstamp interval [read-write]"
1376The current interval value. Can be modified any time, but changes only
1377take effect when the periodic timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being
1378called.
1379.IP "ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read\-write]" 4
1380.IX Item "ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read-write]"
1381The current reschedule callback, or \f(CW0\fR, if this functionality is
1382switched off. Can be changed any time, but changes only take effect when
1383the periodic timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being called.
1384.PP
1385Example: Call a callback every hour, or, more precisely, whenever the
1386system clock is divisible by 3600. The callback invocation times have
1387potentially a lot of jittering, but good long-term stability.
1388.PP
1389.Vb 5
1390\& static void
1391\& clock_cb (struct ev_loop *loop, struct ev_io *w, int revents)
1392\& {
1393\& ... its now a full hour (UTC, or TAI or whatever your clock follows)
1394\& }
1395.Ve
1396.PP
1397.Vb 3
1398\& struct ev_periodic hourly_tick;
1399\& ev_periodic_init (&hourly_tick, clock_cb, 0., 3600., 0);
1400\& ev_periodic_start (loop, &hourly_tick);
1401.Ve
1402.PP
1403Example: The same as above, but use a reschedule callback to do it:
1404.PP
1405.Vb 1
1406\& #include <math.h>
1407.Ve
1408.PP
1409.Vb 5
1410\& static ev_tstamp
1411\& my_scheduler_cb (struct ev_periodic *w, ev_tstamp now)
1412\& {
1413\& return fmod (now, 3600.) + 3600.;
1414\& }
1415.Ve
1416.PP
1417.Vb 1
1418\& ev_periodic_init (&hourly_tick, clock_cb, 0., 0., my_scheduler_cb);
1419.Ve
1420.PP
1421Example: Call a callback every hour, starting now:
1422.PP
1423.Vb 4
1424\& struct ev_periodic hourly_tick;
1425\& ev_periodic_init (&hourly_tick, clock_cb,
1426\& fmod (ev_now (loop), 3600.), 3600., 0);
1427\& ev_periodic_start (loop, &hourly_tick);
1428.Ve
825.ie n .Sh """ev_signal"" \- signal me when a signal gets signalled" 1429.ie n .Sh """ev_signal"" \- signal me when a signal gets signalled!"
826.el .Sh "\f(CWev_signal\fP \- signal me when a signal gets signalled" 1430.el .Sh "\f(CWev_signal\fP \- signal me when a signal gets signalled!"
827.IX Subsection "ev_signal - signal me when a signal gets signalled" 1431.IX Subsection "ev_signal - signal me when a signal gets signalled!"
828Signal watchers will trigger an event when the process receives a specific 1432Signal watchers will trigger an event when the process receives a specific
829signal one or more times. Even though signals are very asynchronous, libev 1433signal one or more times. Even though signals are very asynchronous, libev
830will try it's best to deliver signals synchronously, i.e. as part of the 1434will try it's best to deliver signals synchronously, i.e. as part of the
831normal event processing, like any other event. 1435normal event processing, like any other event.
832.PP 1436.PP
… …
834first watcher gets started will libev actually register a signal watcher 1438first watcher gets started will libev actually register a signal watcher
835with the kernel (thus it coexists with your own signal handlers as long 1439with the kernel (thus it coexists with your own signal handlers as long
836as you don't register any with libev). Similarly, when the last signal 1440as you don't register any with libev). Similarly, when the last signal
837watcher for a signal is stopped libev will reset the signal handler to 1441watcher for a signal is stopped libev will reset the signal handler to
838\&\s-1SIG_DFL\s0 (regardless of what it was set to before). 1442\&\s-1SIG_DFL\s0 (regardless of what it was set to before).
1443.PP
1444\fIWatcher-Specific Functions and Data Members\fR
1445.IX Subsection "Watcher-Specific Functions and Data Members"
839.IP "ev_signal_init (ev_signal *, callback, int signum)" 4 1446.IP "ev_signal_init (ev_signal *, callback, int signum)" 4
840.IX Item "ev_signal_init (ev_signal *, callback, int signum)" 1447.IX Item "ev_signal_init (ev_signal *, callback, int signum)"
841.PD 0 1448.PD 0
842.IP "ev_signal_set (ev_signal *, int signum)" 4 1449.IP "ev_signal_set (ev_signal *, int signum)" 4
843.IX Item "ev_signal_set (ev_signal *, int signum)" 1450.IX Item "ev_signal_set (ev_signal *, int signum)"
844.PD 1451.PD
845Configures the watcher to trigger on the given signal number (usually one 1452Configures the watcher to trigger on the given signal number (usually one
846of the \f(CW\*(C`SIGxxx\*(C'\fR constants). 1453of the \f(CW\*(C`SIGxxx\*(C'\fR constants).
1454.IP "int signum [read\-only]" 4
1455.IX Item "int signum [read-only]"
1456The signal the watcher watches out for.
847.ie n .Sh """ev_child"" \- wait for pid status changes" 1457.ie n .Sh """ev_child"" \- watch out for process status changes"
848.el .Sh "\f(CWev_child\fP \- wait for pid status changes" 1458.el .Sh "\f(CWev_child\fP \- watch out for process status changes"
849.IX Subsection "ev_child - wait for pid status changes" 1459.IX Subsection "ev_child - watch out for process status changes"
850Child watchers trigger when your process receives a \s-1SIGCHLD\s0 in response to 1460Child watchers trigger when your process receives a \s-1SIGCHLD\s0 in response to
851some child status changes (most typically when a child of yours dies). 1461some child status changes (most typically when a child of yours dies).
1462.PP
1463\fIWatcher-Specific Functions and Data Members\fR
1464.IX Subsection "Watcher-Specific Functions and Data Members"
852.IP "ev_child_init (ev_child *, callback, int pid)" 4 1465.IP "ev_child_init (ev_child *, callback, int pid)" 4
853.IX Item "ev_child_init (ev_child *, callback, int pid)" 1466.IX Item "ev_child_init (ev_child *, callback, int pid)"
854.PD 0 1467.PD 0
855.IP "ev_child_set (ev_child *, int pid)" 4 1468.IP "ev_child_set (ev_child *, int pid)" 4
856.IX Item "ev_child_set (ev_child *, int pid)" 1469.IX Item "ev_child_set (ev_child *, int pid)"
… …
859\&\fIany\fR process if \f(CW\*(C`pid\*(C'\fR is specified as \f(CW0\fR). The callback can look 1472\&\fIany\fR process if \f(CW\*(C`pid\*(C'\fR is specified as \f(CW0\fR). The callback can look
860at the \f(CW\*(C`rstatus\*(C'\fR member of the \f(CW\*(C`ev_child\*(C'\fR watcher structure to see 1473at the \f(CW\*(C`rstatus\*(C'\fR member of the \f(CW\*(C`ev_child\*(C'\fR watcher structure to see
861the status word (use the macros from \f(CW\*(C`sys/wait.h\*(C'\fR and see your systems 1474the status word (use the macros from \f(CW\*(C`sys/wait.h\*(C'\fR and see your systems
862\&\f(CW\*(C`waitpid\*(C'\fR documentation). The \f(CW\*(C`rpid\*(C'\fR member contains the pid of the 1475\&\f(CW\*(C`waitpid\*(C'\fR documentation). The \f(CW\*(C`rpid\*(C'\fR member contains the pid of the
863process causing the status change. 1476process causing the status change.
1477.IP "int pid [read\-only]" 4
1478.IX Item "int pid [read-only]"
1479The process id this watcher watches out for, or \f(CW0\fR, meaning any process id.
1480.IP "int rpid [read\-write]" 4
1481.IX Item "int rpid [read-write]"
1482The process id that detected a status change.
1483.IP "int rstatus [read\-write]" 4
1484.IX Item "int rstatus [read-write]"
1485The process exit/trace status caused by \f(CW\*(C`rpid\*(C'\fR (see your systems
1486\&\f(CW\*(C`waitpid\*(C'\fR and \f(CW\*(C`sys/wait.h\*(C'\fR documentation for details).
1487.PP
1488Example: Try to exit cleanly on \s-1SIGINT\s0 and \s-1SIGTERM\s0.
1489.PP
1490.Vb 5
1491\& static void
1492\& sigint_cb (struct ev_loop *loop, struct ev_signal *w, int revents)
1493\& {
1494\& ev_unloop (loop, EVUNLOOP_ALL);
1495\& }
1496.Ve
1497.PP
1498.Vb 3
1499\& struct ev_signal signal_watcher;
1500\& ev_signal_init (&signal_watcher, sigint_cb, SIGINT);
1501\& ev_signal_start (loop, &sigint_cb);
1502.Ve
1503.ie n .Sh """ev_stat"" \- did the file attributes just change?"
1504.el .Sh "\f(CWev_stat\fP \- did the file attributes just change?"
1505.IX Subsection "ev_stat - did the file attributes just change?"
1506This watches a filesystem path for attribute changes. That is, it calls
1507\&\f(CW\*(C`stat\*(C'\fR regularly (or when the \s-1OS\s0 says it changed) and sees if it changed
1508compared to the last time, invoking the callback if it did.
1509.PP
1510The path does not need to exist: changing from \*(L"path exists\*(R" to \*(L"path does
1511not exist\*(R" is a status change like any other. The condition \*(L"path does
1512not exist\*(R" is signified by the \f(CW\*(C`st_nlink\*(C'\fR field being zero (which is
1513otherwise always forced to be at least one) and all the other fields of
1514the stat buffer having unspecified contents.
1515.PP
1516The path \fIshould\fR be absolute and \fImust not\fR end in a slash. If it is
1517relative and your working directory changes, the behaviour is undefined.
1518.PP
1519Since there is no standard to do this, the portable implementation simply
1520calls \f(CW\*(C`stat (2)\*(C'\fR regularly on the path to see if it changed somehow. You
1521can specify a recommended polling interval for this case. If you specify
1522a polling interval of \f(CW0\fR (highly recommended!) then a \fIsuitable,
1523unspecified default\fR value will be used (which you can expect to be around
1524five seconds, although this might change dynamically). Libev will also
1525impose a minimum interval which is currently around \f(CW0.1\fR, but thats
1526usually overkill.
1527.PP
1528This watcher type is not meant for massive numbers of stat watchers,
1529as even with OS-supported change notifications, this can be
1530resource\-intensive.
1531.PP
1532At the time of this writing, only the Linux inotify interface is
1533implemented (implementing kqueue support is left as an exercise for the
1534reader). Inotify will be used to give hints only and should not change the
1535semantics of \f(CW\*(C`ev_stat\*(C'\fR watchers, which means that libev sometimes needs
1536to fall back to regular polling again even with inotify, but changes are
1537usually detected immediately, and if the file exists there will be no
1538polling.
1539.PP
1540\fIWatcher-Specific Functions and Data Members\fR
1541.IX Subsection "Watcher-Specific Functions and Data Members"
1542.IP "ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)" 4
1543.IX Item "ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)"
1544.PD 0
1545.IP "ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)" 4
1546.IX Item "ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)"
1547.PD
1548Configures the watcher to wait for status changes of the given
1549\&\f(CW\*(C`path\*(C'\fR. The \f(CW\*(C`interval\*(C'\fR is a hint on how quickly a change is expected to
1550be detected and should normally be specified as \f(CW0\fR to let libev choose
1551a suitable value. The memory pointed to by \f(CW\*(C`path\*(C'\fR must point to the same
1552path for as long as the watcher is active.
1553.Sp
1554The callback will be receive \f(CW\*(C`EV_STAT\*(C'\fR when a change was detected,
1555relative to the attributes at the time the watcher was started (or the
1556last change was detected).
1557.IP "ev_stat_stat (ev_stat *)" 4
1558.IX Item "ev_stat_stat (ev_stat *)"
1559Updates the stat buffer immediately with new values. If you change the
1560watched path in your callback, you could call this fucntion to avoid
1561detecting this change (while introducing a race condition). Can also be
1562useful simply to find out the new values.
1563.IP "ev_statdata attr [read\-only]" 4
1564.IX Item "ev_statdata attr [read-only]"
1565The most-recently detected attributes of the file. Although the type is of
1566\&\f(CW\*(C`ev_statdata\*(C'\fR, this is usually the (or one of the) \f(CW\*(C`struct stat\*(C'\fR types
1567suitable for your system. If the \f(CW\*(C`st_nlink\*(C'\fR member is \f(CW0\fR, then there
1568was some error while \f(CW\*(C`stat\*(C'\fRing the file.
1569.IP "ev_statdata prev [read\-only]" 4
1570.IX Item "ev_statdata prev [read-only]"
1571The previous attributes of the file. The callback gets invoked whenever
1572\&\f(CW\*(C`prev\*(C'\fR != \f(CW\*(C`attr\*(C'\fR.
1573.IP "ev_tstamp interval [read\-only]" 4
1574.IX Item "ev_tstamp interval [read-only]"
1575The specified interval.
1576.IP "const char *path [read\-only]" 4
1577.IX Item "const char *path [read-only]"
1578The filesystem path that is being watched.
1579.PP
1580Example: Watch \f(CW\*(C`/etc/passwd\*(C'\fR for attribute changes.
1581.PP
1582.Vb 15
1583\& static void
1584\& passwd_cb (struct ev_loop *loop, ev_stat *w, int revents)
1585\& {
1586\& /* /etc/passwd changed in some way */
1587\& if (w->attr.st_nlink)
1588\& {
1589\& printf ("passwd current size %ld\en", (long)w->attr.st_size);
1590\& printf ("passwd current atime %ld\en", (long)w->attr.st_mtime);
1591\& printf ("passwd current mtime %ld\en", (long)w->attr.st_mtime);
1592\& }
1593\& else
1594\& /* you shalt not abuse printf for puts */
1595\& puts ("wow, /etc/passwd is not there, expect problems. "
1596\& "if this is windows, they already arrived\en");
1597\& }
1598.Ve
1599.PP
1600.Vb 2
1601\& ...
1602\& ev_stat passwd;
1603.Ve
1604.PP
1605.Vb 2
1606\& ev_stat_init (&passwd, passwd_cb, "/etc/passwd");
1607\& ev_stat_start (loop, &passwd);
1608.Ve
864.ie n .Sh """ev_idle"" \- when you've got nothing better to do" 1609.ie n .Sh """ev_idle"" \- when you've got nothing better to do..."
865.el .Sh "\f(CWev_idle\fP \- when you've got nothing better to do" 1610.el .Sh "\f(CWev_idle\fP \- when you've got nothing better to do..."
866.IX Subsection "ev_idle - when you've got nothing better to do" 1611.IX Subsection "ev_idle - when you've got nothing better to do..."
867Idle watchers trigger events when there are no other events are pending 1612Idle watchers trigger events when no other events of the same or higher
868(prepare, check and other idle watchers do not count). That is, as long 1613priority are pending (prepare, check and other idle watchers do not
869as your process is busy handling sockets or timeouts (or even signals, 1614count).
870imagine) it will not be triggered. But when your process is idle all idle 1615.PP
871watchers are being called again and again, once per event loop iteration \- 1616That is, as long as your process is busy handling sockets or timeouts
1617(or even signals, imagine) of the same or higher priority it will not be
1618triggered. But when your process is idle (or only lower-priority watchers
1619are pending), the idle watchers are being called once per event loop
872until stopped, that is, or your process receives more events and becomes 1620iteration \- until stopped, that is, or your process receives more events
873busy. 1621and becomes busy again with higher priority stuff.
874.PP 1622.PP
875The most noteworthy effect is that as long as any idle watchers are 1623The most noteworthy effect is that as long as any idle watchers are
876active, the process will not block when waiting for new events. 1624active, the process will not block when waiting for new events.
877.PP 1625.PP
878Apart from keeping your process non-blocking (which is a useful 1626Apart from keeping your process non-blocking (which is a useful
879effect on its own sometimes), idle watchers are a good place to do 1627effect on its own sometimes), idle watchers are a good place to do
880\&\*(L"pseudo\-background processing\*(R", or delay processing stuff to after the 1628\&\*(L"pseudo\-background processing\*(R", or delay processing stuff to after the
881event loop has handled all outstanding events. 1629event loop has handled all outstanding events.
1630.PP
1631\fIWatcher-Specific Functions and Data Members\fR
1632.IX Subsection "Watcher-Specific Functions and Data Members"
882.IP "ev_idle_init (ev_signal *, callback)" 4 1633.IP "ev_idle_init (ev_signal *, callback)" 4
883.IX Item "ev_idle_init (ev_signal *, callback)" 1634.IX Item "ev_idle_init (ev_signal *, callback)"
884Initialises and configures the idle watcher \- it has no parameters of any 1635Initialises and configures the idle watcher \- it has no parameters of any
885kind. There is a \f(CW\*(C`ev_idle_set\*(C'\fR macro, but using it is utterly pointless, 1636kind. There is a \f(CW\*(C`ev_idle_set\*(C'\fR macro, but using it is utterly pointless,
886believe me. 1637believe me.
1638.PP
1639Example: Dynamically allocate an \f(CW\*(C`ev_idle\*(C'\fR watcher, start it, and in the
1640callback, free it. Also, use no error checking, as usual.
1641.PP
1642.Vb 7
1643\& static void
1644\& idle_cb (struct ev_loop *loop, struct ev_idle *w, int revents)
1645\& {
1646\& free (w);
1647\& // now do something you wanted to do when the program has
1648\& // no longer asnything immediate to do.
1649\& }
1650.Ve
1651.PP
1652.Vb 3
1653\& struct ev_idle *idle_watcher = malloc (sizeof (struct ev_idle));
1654\& ev_idle_init (idle_watcher, idle_cb);
1655\& ev_idle_start (loop, idle_cb);
1656.Ve
887.ie n .Sh """ev_prepare""\fP and \f(CW""ev_check"" \- customise your event loop" 1657.ie n .Sh """ev_prepare""\fP and \f(CW""ev_check"" \- customise your event loop!"
888.el .Sh "\f(CWev_prepare\fP and \f(CWev_check\fP \- customise your event loop" 1658.el .Sh "\f(CWev_prepare\fP and \f(CWev_check\fP \- customise your event loop!"
889.IX Subsection "ev_prepare and ev_check - customise your event loop" 1659.IX Subsection "ev_prepare and ev_check - customise your event loop!"
890Prepare and check watchers are usually (but not always) used in tandem: 1660Prepare and check watchers are usually (but not always) used in tandem:
891prepare watchers get invoked before the process blocks and check watchers 1661prepare watchers get invoked before the process blocks and check watchers
892afterwards. 1662afterwards.
893.PP 1663.PP
1664You \fImust not\fR call \f(CW\*(C`ev_loop\*(C'\fR or similar functions that enter
1665the current event loop from either \f(CW\*(C`ev_prepare\*(C'\fR or \f(CW\*(C`ev_check\*(C'\fR
1666watchers. Other loops than the current one are fine, however. The
1667rationale behind this is that you do not need to check for recursion in
1668those watchers, i.e. the sequence will always be \f(CW\*(C`ev_prepare\*(C'\fR, blocking,
1669\&\f(CW\*(C`ev_check\*(C'\fR so if you have one watcher of each kind they will always be
1670called in pairs bracketing the blocking call.
1671.PP
894Their main purpose is to integrate other event mechanisms into libev. This 1672Their main purpose is to integrate other event mechanisms into libev and
895could be used, for example, to track variable changes, implement your own 1673their use is somewhat advanced. This could be used, for example, to track
896watchers, integrate net-snmp or a coroutine library and lots more. 1674variable changes, implement your own watchers, integrate net-snmp or a
1675coroutine library and lots more. They are also occasionally useful if
1676you cache some data and want to flush it before blocking (for example,
1677in X programs you might want to do an \f(CW\*(C`XFlush ()\*(C'\fR in an \f(CW\*(C`ev_prepare\*(C'\fR
1678watcher).
897.PP 1679.PP
898This is done by examining in each prepare call which file descriptors need 1680This is done by examining in each prepare call which file descriptors need
899to be watched by the other library, registering \f(CW\*(C`ev_io\*(C'\fR watchers for 1681to be watched by the other library, registering \f(CW\*(C`ev_io\*(C'\fR watchers for
900them and starting an \f(CW\*(C`ev_timer\*(C'\fR watcher for any timeouts (many libraries 1682them and starting an \f(CW\*(C`ev_timer\*(C'\fR watcher for any timeouts (many libraries
901provide just this functionality). Then, in the check watcher you check for 1683provide just this functionality). Then, in the check watcher you check for
… …
910are ready to run (it's actually more complicated: it only runs coroutines 1692are ready to run (it's actually more complicated: it only runs coroutines
911with priority higher than or equal to the event loop and one coroutine 1693with priority higher than or equal to the event loop and one coroutine
912of lower priority, but only once, using idle watchers to keep the event 1694of lower priority, but only once, using idle watchers to keep the event
913loop from blocking if lower-priority coroutines are active, thus mapping 1695loop from blocking if lower-priority coroutines are active, thus mapping
914low-priority coroutines to idle/background tasks). 1696low-priority coroutines to idle/background tasks).
1697.PP
1698It is recommended to give \f(CW\*(C`ev_check\*(C'\fR watchers highest (\f(CW\*(C`EV_MAXPRI\*(C'\fR)
1699priority, to ensure that they are being run before any other watchers
1700after the poll. Also, \f(CW\*(C`ev_check\*(C'\fR watchers (and \f(CW\*(C`ev_prepare\*(C'\fR watchers,
1701too) should not activate (\*(L"feed\*(R") events into libev. While libev fully
1702supports this, they will be called before other \f(CW\*(C`ev_check\*(C'\fR watchers did
1703their job. As \f(CW\*(C`ev_check\*(C'\fR watchers are often used to embed other event
1704loops those other event loops might be in an unusable state until their
1705\&\f(CW\*(C`ev_check\*(C'\fR watcher ran (always remind yourself to coexist peacefully with
1706others).
1707.PP
1708\fIWatcher-Specific Functions and Data Members\fR
1709.IX Subsection "Watcher-Specific Functions and Data Members"
915.IP "ev_prepare_init (ev_prepare *, callback)" 4 1710.IP "ev_prepare_init (ev_prepare *, callback)" 4
916.IX Item "ev_prepare_init (ev_prepare *, callback)" 1711.IX Item "ev_prepare_init (ev_prepare *, callback)"
917.PD 0 1712.PD 0
918.IP "ev_check_init (ev_check *, callback)" 4 1713.IP "ev_check_init (ev_check *, callback)" 4
919.IX Item "ev_check_init (ev_check *, callback)" 1714.IX Item "ev_check_init (ev_check *, callback)"
920.PD 1715.PD
921Initialises and configures the prepare or check watcher \- they have no 1716Initialises and configures the prepare or check watcher \- they have no
922parameters of any kind. There are \f(CW\*(C`ev_prepare_set\*(C'\fR and \f(CW\*(C`ev_check_set\*(C'\fR 1717parameters of any kind. There are \f(CW\*(C`ev_prepare_set\*(C'\fR and \f(CW\*(C`ev_check_set\*(C'\fR
923macros, but using them is utterly, utterly and completely pointless. 1718macros, but using them is utterly, utterly and completely pointless.
1719.PP
1720There are a number of principal ways to embed other event loops or modules
1721into libev. Here are some ideas on how to include libadns into libev
1722(there is a Perl module named \f(CW\*(C`EV::ADNS\*(C'\fR that does this, which you could
1723use for an actually working example. Another Perl module named \f(CW\*(C`EV::Glib\*(C'\fR
1724embeds a Glib main context into libev, and finally, \f(CW\*(C`Glib::EV\*(C'\fR embeds \s-1EV\s0
1725into the Glib event loop).
1726.PP
1727Method 1: Add \s-1IO\s0 watchers and a timeout watcher in a prepare handler,
1728and in a check watcher, destroy them and call into libadns. What follows
1729is pseudo-code only of course. This requires you to either use a low
1730priority for the check watcher or use \f(CW\*(C`ev_clear_pending\*(C'\fR explicitly, as
1731the callbacks for the IO/timeout watchers might not have been called yet.
1732.PP
1733.Vb 2
1734\& static ev_io iow [nfd];
1735\& static ev_timer tw;
1736.Ve
1737.PP
1738.Vb 4
1739\& static void
1740\& io_cb (ev_loop *loop, ev_io *w, int revents)
1741\& {
1742\& }
1743.Ve
1744.PP
1745.Vb 8
1746\& // create io watchers for each fd and a timer before blocking
1747\& static void
1748\& adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents)
1749\& {
1750\& int timeout = 3600000;
1751\& struct pollfd fds [nfd];
1752\& // actual code will need to loop here and realloc etc.
1753\& adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ()));
1754.Ve
1755.PP
1756.Vb 3
1757\& /* the callback is illegal, but won't be called as we stop during check */
1758\& ev_timer_init (&tw, 0, timeout * 1e-3);
1759\& ev_timer_start (loop, &tw);
1760.Ve
1761.PP
1762.Vb 6
1763\& // create one ev_io per pollfd
1764\& for (int i = 0; i < nfd; ++i)
1765\& {
1766\& ev_io_init (iow + i, io_cb, fds [i].fd,
1767\& ((fds [i].events & POLLIN ? EV_READ : 0)
1768\& | (fds [i].events & POLLOUT ? EV_WRITE : 0)));
1769.Ve
1770.PP
1771.Vb 4
1772\& fds [i].revents = 0;
1773\& ev_io_start (loop, iow + i);
1774\& }
1775\& }
1776.Ve
1777.PP
1778.Vb 5
1779\& // stop all watchers after blocking
1780\& static void
1781\& adns_check_cb (ev_loop *loop, ev_check *w, int revents)
1782\& {
1783\& ev_timer_stop (loop, &tw);
1784.Ve
1785.PP
1786.Vb 8
1787\& for (int i = 0; i < nfd; ++i)
1788\& {
1789\& // set the relevant poll flags
1790\& // could also call adns_processreadable etc. here
1791\& struct pollfd *fd = fds + i;
1792\& int revents = ev_clear_pending (iow + i);
1793\& if (revents & EV_READ ) fd->revents |= fd->events & POLLIN;
1794\& if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT;
1795.Ve
1796.PP
1797.Vb 3
1798\& // now stop the watcher
1799\& ev_io_stop (loop, iow + i);
1800\& }
1801.Ve
1802.PP
1803.Vb 2
1804\& adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop));
1805\& }
1806.Ve
1807.PP
1808Method 2: This would be just like method 1, but you run \f(CW\*(C`adns_afterpoll\*(C'\fR
1809in the prepare watcher and would dispose of the check watcher.
1810.PP
1811Method 3: If the module to be embedded supports explicit event
1812notification (adns does), you can also make use of the actual watcher
1813callbacks, and only destroy/create the watchers in the prepare watcher.
1814.PP
1815.Vb 5
1816\& static void
1817\& timer_cb (EV_P_ ev_timer *w, int revents)
1818\& {
1819\& adns_state ads = (adns_state)w->data;
1820\& update_now (EV_A);
1821.Ve
1822.PP
1823.Vb 2
1824\& adns_processtimeouts (ads, &tv_now);
1825\& }
1826.Ve
1827.PP
1828.Vb 5
1829\& static void
1830\& io_cb (EV_P_ ev_io *w, int revents)
1831\& {
1832\& adns_state ads = (adns_state)w->data;
1833\& update_now (EV_A);
1834.Ve
1835.PP
1836.Vb 3
1837\& if (revents & EV_READ ) adns_processreadable (ads, w->fd, &tv_now);
1838\& if (revents & EV_WRITE) adns_processwriteable (ads, w->fd, &tv_now);
1839\& }
1840.Ve
1841.PP
1842.Vb 1
1843\& // do not ever call adns_afterpoll
1844.Ve
1845.PP
1846Method 4: Do not use a prepare or check watcher because the module you
1847want to embed is too inflexible to support it. Instead, youc na override
1848their poll function. The drawback with this solution is that the main
1849loop is now no longer controllable by \s-1EV\s0. The \f(CW\*(C`Glib::EV\*(C'\fR module does
1850this.
1851.PP
1852.Vb 4
1853\& static gint
1854\& event_poll_func (GPollFD *fds, guint nfds, gint timeout)
1855\& {
1856\& int got_events = 0;
1857.Ve
1858.PP
1859.Vb 2
1860\& for (n = 0; n < nfds; ++n)
1861\& // create/start io watcher that sets the relevant bits in fds[n] and increment got_events
1862.Ve
1863.PP
1864.Vb 2
1865\& if (timeout >= 0)
1866\& // create/start timer
1867.Ve
1868.PP
1869.Vb 2
1870\& // poll
1871\& ev_loop (EV_A_ 0);
1872.Ve
1873.PP
1874.Vb 3
1875\& // stop timer again
1876\& if (timeout >= 0)
1877\& ev_timer_stop (EV_A_ &to);
1878.Ve
1879.PP
1880.Vb 3
1881\& // stop io watchers again - their callbacks should have set
1882\& for (n = 0; n < nfds; ++n)
1883\& ev_io_stop (EV_A_ iow [n]);
1884.Ve
1885.PP
1886.Vb 2
1887\& return got_events;
1888\& }
1889.Ve
1890.ie n .Sh """ev_embed"" \- when one backend isn't enough..."
1891.el .Sh "\f(CWev_embed\fP \- when one backend isn't enough..."
1892.IX Subsection "ev_embed - when one backend isn't enough..."
1893This is a rather advanced watcher type that lets you embed one event loop
1894into another (currently only \f(CW\*(C`ev_io\*(C'\fR events are supported in the embedded
1895loop, other types of watchers might be handled in a delayed or incorrect
1896fashion and must not be used).
1897.PP
1898There are primarily two reasons you would want that: work around bugs and
1899prioritise I/O.
1900.PP
1901As an example for a bug workaround, the kqueue backend might only support
1902sockets on some platform, so it is unusable as generic backend, but you
1903still want to make use of it because you have many sockets and it scales
1904so nicely. In this case, you would create a kqueue-based loop and embed it
1905into your default loop (which might use e.g. poll). Overall operation will
1906be a bit slower because first libev has to poll and then call kevent, but
1907at least you can use both at what they are best.
1908.PP
1909As for prioritising I/O: rarely you have the case where some fds have
1910to be watched and handled very quickly (with low latency), and even
1911priorities and idle watchers might have too much overhead. In this case
1912you would put all the high priority stuff in one loop and all the rest in
1913a second one, and embed the second one in the first.
1914.PP
1915As long as the watcher is active, the callback will be invoked every time
1916there might be events pending in the embedded loop. The callback must then
1917call \f(CW\*(C`ev_embed_sweep (mainloop, watcher)\*(C'\fR to make a single sweep and invoke
1918their callbacks (you could also start an idle watcher to give the embedded
1919loop strictly lower priority for example). You can also set the callback
1920to \f(CW0\fR, in which case the embed watcher will automatically execute the
1921embedded loop sweep.
1922.PP
1923As long as the watcher is started it will automatically handle events. The
1924callback will be invoked whenever some events have been handled. You can
1925set the callback to \f(CW0\fR to avoid having to specify one if you are not
1926interested in that.
1927.PP
1928Also, there have not currently been made special provisions for forking:
1929when you fork, you not only have to call \f(CW\*(C`ev_loop_fork\*(C'\fR on both loops,
1930but you will also have to stop and restart any \f(CW\*(C`ev_embed\*(C'\fR watchers
1931yourself.
1932.PP
1933Unfortunately, not all backends are embeddable, only the ones returned by
1934\&\f(CW\*(C`ev_embeddable_backends\*(C'\fR are, which, unfortunately, does not include any
1935portable one.
1936.PP
1937So when you want to use this feature you will always have to be prepared
1938that you cannot get an embeddable loop. The recommended way to get around
1939this is to have a separate variables for your embeddable loop, try to
1940create it, and if that fails, use the normal loop for everything:
1941.PP
1942.Vb 3
1943\& struct ev_loop *loop_hi = ev_default_init (0);
1944\& struct ev_loop *loop_lo = 0;
1945\& struct ev_embed embed;
1946.Ve
1947.PP
1948.Vb 5
1949\& // see if there is a chance of getting one that works
1950\& // (remember that a flags value of 0 means autodetection)
1951\& loop_lo = ev_embeddable_backends () & ev_recommended_backends ()
1952\& ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ())
1953\& : 0;
1954.Ve
1955.PP
1956.Vb 8
1957\& // if we got one, then embed it, otherwise default to loop_hi
1958\& if (loop_lo)
1959\& {
1960\& ev_embed_init (&embed, 0, loop_lo);
1961\& ev_embed_start (loop_hi, &embed);
1962\& }
1963\& else
1964\& loop_lo = loop_hi;
1965.Ve
1966.PP
1967\fIWatcher-Specific Functions and Data Members\fR
1968.IX Subsection "Watcher-Specific Functions and Data Members"
1969.IP "ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)" 4
1970.IX Item "ev_embed_init (ev_embed *, callback, struct ev_loop *embedded_loop)"
1971.PD 0
1972.IP "ev_embed_set (ev_embed *, callback, struct ev_loop *embedded_loop)" 4
1973.IX Item "ev_embed_set (ev_embed *, callback, struct ev_loop *embedded_loop)"
1974.PD
1975Configures the watcher to embed the given loop, which must be
1976embeddable. If the callback is \f(CW0\fR, then \f(CW\*(C`ev_embed_sweep\*(C'\fR will be
1977invoked automatically, otherwise it is the responsibility of the callback
1978to invoke it (it will continue to be called until the sweep has been done,
1979if you do not want thta, you need to temporarily stop the embed watcher).
1980.IP "ev_embed_sweep (loop, ev_embed *)" 4
1981.IX Item "ev_embed_sweep (loop, ev_embed *)"
1982Make a single, non-blocking sweep over the embedded loop. This works
1983similarly to \f(CW\*(C`ev_loop (embedded_loop, EVLOOP_NONBLOCK)\*(C'\fR, but in the most
1984apropriate way for embedded loops.
1985.IP "struct ev_loop *loop [read\-only]" 4
1986.IX Item "struct ev_loop *loop [read-only]"
1987The embedded event loop.
1988.ie n .Sh """ev_fork"" \- the audacity to resume the event loop after a fork"
1989.el .Sh "\f(CWev_fork\fP \- the audacity to resume the event loop after a fork"
1990.IX Subsection "ev_fork - the audacity to resume the event loop after a fork"
1991Fork watchers are called when a \f(CW\*(C`fork ()\*(C'\fR was detected (usually because
1992whoever is a good citizen cared to tell libev about it by calling
1993\&\f(CW\*(C`ev_default_fork\*(C'\fR or \f(CW\*(C`ev_loop_fork\*(C'\fR). The invocation is done before the
1994event loop blocks next and before \f(CW\*(C`ev_check\*(C'\fR watchers are being called,
1995and only in the child after the fork. If whoever good citizen calling
1996\&\f(CW\*(C`ev_default_fork\*(C'\fR cheats and calls it in the wrong process, the fork
1997handlers will be invoked, too, of course.
1998.PP
1999\fIWatcher-Specific Functions and Data Members\fR
2000.IX Subsection "Watcher-Specific Functions and Data Members"
2001.IP "ev_fork_init (ev_signal *, callback)" 4
2002.IX Item "ev_fork_init (ev_signal *, callback)"
2003Initialises and configures the fork watcher \- it has no parameters of any
2004kind. There is a \f(CW\*(C`ev_fork_set\*(C'\fR macro, but using it is utterly pointless,
2005believe me.
924.SH "OTHER FUNCTIONS" 2006.SH "OTHER FUNCTIONS"
925.IX Header "OTHER FUNCTIONS" 2007.IX Header "OTHER FUNCTIONS"
926There are some other functions of possible interest. Described. Here. Now. 2008There are some other functions of possible interest. Described. Here. Now.
927.IP "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)" 4 2009.IP "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)" 4
928.IX Item "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)" 2010.IX Item "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)"
… …
957.Ve 2039.Ve
958.Sp 2040.Sp
959.Vb 1 2041.Vb 1
960\& ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); 2042\& ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);
961.Ve 2043.Ve
962.IP "ev_feed_event (loop, watcher, int events)" 4 2044.IP "ev_feed_event (ev_loop *, watcher *, int revents)" 4
963.IX Item "ev_feed_event (loop, watcher, int events)" 2045.IX Item "ev_feed_event (ev_loop *, watcher *, int revents)"
964Feeds the given event set into the event loop, as if the specified event 2046Feeds the given event set into the event loop, as if the specified event
965had happened for the specified watcher (which must be a pointer to an 2047had happened for the specified watcher (which must be a pointer to an
966initialised but not necessarily started event watcher). 2048initialised but not necessarily started event watcher).
967.IP "ev_feed_fd_event (loop, int fd, int revents)" 4 2049.IP "ev_feed_fd_event (ev_loop *, int fd, int revents)" 4
968.IX Item "ev_feed_fd_event (loop, int fd, int revents)" 2050.IX Item "ev_feed_fd_event (ev_loop *, int fd, int revents)"
969Feed an event on the given fd, as if a file descriptor backend detected 2051Feed an event on the given fd, as if a file descriptor backend detected
970the given events it. 2052the given events it.
971.IP "ev_feed_signal_event (loop, int signum)" 4 2053.IP "ev_feed_signal_event (ev_loop *loop, int signum)" 4
972.IX Item "ev_feed_signal_event (loop, int signum)" 2054.IX Item "ev_feed_signal_event (ev_loop *loop, int signum)"
973Feed an event as if the given signal occured (loop must be the default loop!). 2055Feed an event as if the given signal occured (\f(CW\*(C`loop\*(C'\fR must be the default
2056loop!).
974.SH "LIBEVENT EMULATION" 2057.SH "LIBEVENT EMULATION"
975.IX Header "LIBEVENT EMULATION" 2058.IX Header "LIBEVENT EMULATION"
976Libev offers a compatibility emulation layer for libevent. It cannot 2059Libev offers a compatibility emulation layer for libevent. It cannot
977emulate the internals of libevent, so here are some usage hints: 2060emulate the internals of libevent, so here are some usage hints:
978.IP "* Use it by including <event.h>, as usual." 4 2061.IP "* Use it by including <event.h>, as usual." 4
… …
989.IP "* The libev emulation is \fInot\fR \s-1ABI\s0 compatible to libevent, you need to use the libev header file and library." 4 2072.IP "* The libev emulation is \fInot\fR \s-1ABI\s0 compatible to libevent, you need to use the libev header file and library." 4
990.IX Item "The libev emulation is not ABI compatible to libevent, you need to use the libev header file and library." 2073.IX Item "The libev emulation is not ABI compatible to libevent, you need to use the libev header file and library."
991.PD 2074.PD
992.SH "\*(C+ SUPPORT" 2075.SH "\*(C+ SUPPORT"
993.IX Header " SUPPORT" 2076.IX Header " SUPPORT"
994\&\s-1TBD\s0. 2077Libev comes with some simplistic wrapper classes for \*(C+ that mainly allow
2078you to use some convinience methods to start/stop watchers and also change
2079the callback model to a model using method callbacks on objects.
2080.PP
2081To use it,
2082.PP
2083.Vb 1
2084\& #include <ev++.h>
2085.Ve
2086.PP
2087This automatically includes \fIev.h\fR and puts all of its definitions (many
2088of them macros) into the global namespace. All \*(C+ specific things are
2089put into the \f(CW\*(C`ev\*(C'\fR namespace. It should support all the same embedding
2090options as \fIev.h\fR, most notably \f(CW\*(C`EV_MULTIPLICITY\*(C'\fR.
2091.PP
2092Care has been taken to keep the overhead low. The only data member the \*(C+
2093classes add (compared to plain C\-style watchers) is the event loop pointer
2094that the watcher is associated with (or no additional members at all if
2095you disable \f(CW\*(C`EV_MULTIPLICITY\*(C'\fR when embedding libev).
2096.PP
2097Currently, functions, and static and non-static member functions can be
2098used as callbacks. Other types should be easy to add as long as they only
2099need one additional pointer for context. If you need support for other
2100types of functors please contact the author (preferably after implementing
2101it).
2102.PP
2103Here is a list of things available in the \f(CW\*(C`ev\*(C'\fR namespace:
2104.ie n .IP """ev::READ""\fR, \f(CW""ev::WRITE"" etc." 4
2105.el .IP "\f(CWev::READ\fR, \f(CWev::WRITE\fR etc." 4
2106.IX Item "ev::READ, ev::WRITE etc."
2107These are just enum values with the same values as the \f(CW\*(C`EV_READ\*(C'\fR etc.
2108macros from \fIev.h\fR.
2109.ie n .IP """ev::tstamp""\fR, \f(CW""ev::now""" 4
2110.el .IP "\f(CWev::tstamp\fR, \f(CWev::now\fR" 4
2111.IX Item "ev::tstamp, ev::now"
2112Aliases to the same types/functions as with the \f(CW\*(C`ev_\*(C'\fR prefix.
2113.ie n .IP """ev::io""\fR, \f(CW""ev::timer""\fR, \f(CW""ev::periodic""\fR, \f(CW""ev::idle""\fR, \f(CW""ev::sig"" etc." 4
2114.el .IP "\f(CWev::io\fR, \f(CWev::timer\fR, \f(CWev::periodic\fR, \f(CWev::idle\fR, \f(CWev::sig\fR etc." 4
2115.IX Item "ev::io, ev::timer, ev::periodic, ev::idle, ev::sig etc."
2116For each \f(CW\*(C`ev_TYPE\*(C'\fR watcher in \fIev.h\fR there is a corresponding class of
2117the same name in the \f(CW\*(C`ev\*(C'\fR namespace, with the exception of \f(CW\*(C`ev_signal\*(C'\fR
2118which is called \f(CW\*(C`ev::sig\*(C'\fR to avoid clashes with the \f(CW\*(C`signal\*(C'\fR macro
2119defines by many implementations.
2120.Sp
2121All of those classes have these methods:
2122.RS 4
2123.IP "ev::TYPE::TYPE ()" 4
2124.IX Item "ev::TYPE::TYPE ()"
2125.PD 0
2126.IP "ev::TYPE::TYPE (struct ev_loop *)" 4
2127.IX Item "ev::TYPE::TYPE (struct ev_loop *)"
2128.IP "ev::TYPE::~TYPE" 4
2129.IX Item "ev::TYPE::~TYPE"
2130.PD
2131The constructor (optionally) takes an event loop to associate the watcher
2132with. If it is omitted, it will use \f(CW\*(C`EV_DEFAULT\*(C'\fR.
2133.Sp
2134The constructor calls \f(CW\*(C`ev_init\*(C'\fR for you, which means you have to call the
2135\&\f(CW\*(C`set\*(C'\fR method before starting it.
2136.Sp
2137It will not set a callback, however: You have to call the templated \f(CW\*(C`set\*(C'\fR
2138method to set a callback before you can start the watcher.
2139.Sp
2140(The reason why you have to use a method is a limitation in \*(C+ which does
2141not allow explicit template arguments for constructors).
2142.Sp
2143The destructor automatically stops the watcher if it is active.
2144.IP "w\->set<class, &class::method> (object *)" 4
2145.IX Item "w->set<class, &class::method> (object *)"
2146This method sets the callback method to call. The method has to have a
2147signature of \f(CW\*(C`void (*)(ev_TYPE &, int)\*(C'\fR, it receives the watcher as
2148first argument and the \f(CW\*(C`revents\*(C'\fR as second. The object must be given as
2149parameter and is stored in the \f(CW\*(C`data\*(C'\fR member of the watcher.
2150.Sp
2151This method synthesizes efficient thunking code to call your method from
2152the C callback that libev requires. If your compiler can inline your
2153callback (i.e. it is visible to it at the place of the \f(CW\*(C`set\*(C'\fR call and
2154your compiler is good :), then the method will be fully inlined into the
2155thunking function, making it as fast as a direct C callback.
2156.Sp
2157Example: simple class declaration and watcher initialisation
2158.Sp
2159.Vb 4
2160\& struct myclass
2161\& {
2162\& void io_cb (ev::io &w, int revents) { }
2163\& }
2164.Ve
2165.Sp
2166.Vb 3
2167\& myclass obj;
2168\& ev::io iow;
2169\& iow.set <myclass, &myclass::io_cb> (&obj);
2170.Ve
2171.IP "w\->set<function> (void *data = 0)" 4
2172.IX Item "w->set<function> (void *data = 0)"
2173Also sets a callback, but uses a static method or plain function as
2174callback. The optional \f(CW\*(C`data\*(C'\fR argument will be stored in the watcher's
2175\&\f(CW\*(C`data\*(C'\fR member and is free for you to use.
2176.Sp
2177The prototype of the \f(CW\*(C`function\*(C'\fR must be \f(CW\*(C`void (*)(ev::TYPE &w, int)\*(C'\fR.
2178.Sp
2179See the method\-\f(CW\*(C`set\*(C'\fR above for more details.
2180.Sp
2181Example:
2182.Sp
2183.Vb 2
2184\& static void io_cb (ev::io &w, int revents) { }
2185\& iow.set <io_cb> ();
2186.Ve
2187.IP "w\->set (struct ev_loop *)" 4
2188.IX Item "w->set (struct ev_loop *)"
2189Associates a different \f(CW\*(C`struct ev_loop\*(C'\fR with this watcher. You can only
2190do this when the watcher is inactive (and not pending either).
2191.IP "w\->set ([args])" 4
2192.IX Item "w->set ([args])"
2193Basically the same as \f(CW\*(C`ev_TYPE_set\*(C'\fR, with the same args. Must be
2194called at least once. Unlike the C counterpart, an active watcher gets
2195automatically stopped and restarted when reconfiguring it with this
2196method.
2197.IP "w\->start ()" 4
2198.IX Item "w->start ()"
2199Starts the watcher. Note that there is no \f(CW\*(C`loop\*(C'\fR argument, as the
2200constructor already stores the event loop.
2201.IP "w\->stop ()" 4
2202.IX Item "w->stop ()"
2203Stops the watcher if it is active. Again, no \f(CW\*(C`loop\*(C'\fR argument.
2204.ie n .IP "w\->again () ""ev::timer""\fR, \f(CW""ev::periodic"" only" 4
2205.el .IP "w\->again () \f(CWev::timer\fR, \f(CWev::periodic\fR only" 4
2206.IX Item "w->again () ev::timer, ev::periodic only"
2207For \f(CW\*(C`ev::timer\*(C'\fR and \f(CW\*(C`ev::periodic\*(C'\fR, this invokes the corresponding
2208\&\f(CW\*(C`ev_TYPE_again\*(C'\fR function.
2209.ie n .IP "w\->sweep () ""ev::embed"" only" 4
2210.el .IP "w\->sweep () \f(CWev::embed\fR only" 4
2211.IX Item "w->sweep () ev::embed only"
2212Invokes \f(CW\*(C`ev_embed_sweep\*(C'\fR.
2213.ie n .IP "w\->update () ""ev::stat"" only" 4
2214.el .IP "w\->update () \f(CWev::stat\fR only" 4
2215.IX Item "w->update () ev::stat only"
2216Invokes \f(CW\*(C`ev_stat_stat\*(C'\fR.
2217.RE
2218.RS 4
2219.RE
2220.PP
2221Example: Define a class with an \s-1IO\s0 and idle watcher, start one of them in
2222the constructor.
2223.PP
2224.Vb 4
2225\& class myclass
2226\& {
2227\& ev_io io; void io_cb (ev::io &w, int revents);
2228\& ev_idle idle void idle_cb (ev::idle &w, int revents);
2229.Ve
2230.PP
2231.Vb 2
2232\& myclass ();
2233\& }
2234.Ve
2235.PP
2236.Vb 4
2237\& myclass::myclass (int fd)
2238\& {
2239\& io .set <myclass, &myclass::io_cb > (this);
2240\& idle.set <myclass, &myclass::idle_cb> (this);
2241.Ve
2242.PP
2243.Vb 2
2244\& io.start (fd, ev::READ);
2245\& }
2246.Ve
2247.SH "MACRO MAGIC"
2248.IX Header "MACRO MAGIC"
2249Libev can be compiled with a variety of options, the most fundemantal is
2250\&\f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. This option determines whether (most) functions and
2251callbacks have an initial \f(CW\*(C`struct ev_loop *\*(C'\fR argument.
2252.PP
2253To make it easier to write programs that cope with either variant, the
2254following macros are defined:
2255.ie n .IP """EV_A""\fR, \f(CW""EV_A_""" 4
2256.el .IP "\f(CWEV_A\fR, \f(CWEV_A_\fR" 4
2257.IX Item "EV_A, EV_A_"
2258This provides the loop \fIargument\fR for functions, if one is required (\*(L"ev
2259loop argument\*(R"). The \f(CW\*(C`EV_A\*(C'\fR form is used when this is the sole argument,
2260\&\f(CW\*(C`EV_A_\*(C'\fR is used when other arguments are following. Example:
2261.Sp
2262.Vb 3
2263\& ev_unref (EV_A);
2264\& ev_timer_add (EV_A_ watcher);
2265\& ev_loop (EV_A_ 0);
2266.Ve
2267.Sp
2268It assumes the variable \f(CW\*(C`loop\*(C'\fR of type \f(CW\*(C`struct ev_loop *\*(C'\fR is in scope,
2269which is often provided by the following macro.
2270.ie n .IP """EV_P""\fR, \f(CW""EV_P_""" 4
2271.el .IP "\f(CWEV_P\fR, \f(CWEV_P_\fR" 4
2272.IX Item "EV_P, EV_P_"
2273This provides the loop \fIparameter\fR for functions, if one is required (\*(L"ev
2274loop parameter\*(R"). The \f(CW\*(C`EV_P\*(C'\fR form is used when this is the sole parameter,
2275\&\f(CW\*(C`EV_P_\*(C'\fR is used when other parameters are following. Example:
2276.Sp
2277.Vb 2
2278\& // this is how ev_unref is being declared
2279\& static void ev_unref (EV_P);
2280.Ve
2281.Sp
2282.Vb 2
2283\& // this is how you can declare your typical callback
2284\& static void cb (EV_P_ ev_timer *w, int revents)
2285.Ve
2286.Sp
2287It declares a parameter \f(CW\*(C`loop\*(C'\fR of type \f(CW\*(C`struct ev_loop *\*(C'\fR, quite
2288suitable for use with \f(CW\*(C`EV_A\*(C'\fR.
2289.ie n .IP """EV_DEFAULT""\fR, \f(CW""EV_DEFAULT_""" 4
2290.el .IP "\f(CWEV_DEFAULT\fR, \f(CWEV_DEFAULT_\fR" 4
2291.IX Item "EV_DEFAULT, EV_DEFAULT_"
2292Similar to the other two macros, this gives you the value of the default
2293loop, if multiple loops are supported (\*(L"ev loop default\*(R").
2294.PP
2295Example: Declare and initialise a check watcher, utilising the above
2296macros so it will work regardless of whether multiple loops are supported
2297or not.
2298.PP
2299.Vb 5
2300\& static void
2301\& check_cb (EV_P_ ev_timer *w, int revents)
2302\& {
2303\& ev_check_stop (EV_A_ w);
2304\& }
2305.Ve
2306.PP
2307.Vb 4
2308\& ev_check check;
2309\& ev_check_init (&check, check_cb);
2310\& ev_check_start (EV_DEFAULT_ &check);
2311\& ev_loop (EV_DEFAULT_ 0);
2312.Ve
2313.SH "EMBEDDING"
2314.IX Header "EMBEDDING"
2315Libev can (and often is) directly embedded into host
2316applications. Examples of applications that embed it include the Deliantra
2317Game Server, the \s-1EV\s0 perl module, the \s-1GNU\s0 Virtual Private Ethernet (gvpe)
2318and rxvt\-unicode.
2319.PP
2320The goal is to enable you to just copy the neecssary files into your
2321source directory without having to change even a single line in them, so
2322you can easily upgrade by simply copying (or having a checked-out copy of
2323libev somewhere in your source tree).
2324.Sh "\s-1FILESETS\s0"
2325.IX Subsection "FILESETS"
2326Depending on what features you need you need to include one or more sets of files
2327in your app.
2328.PP
2329\fI\s-1CORE\s0 \s-1EVENT\s0 \s-1LOOP\s0\fR
2330.IX Subsection "CORE EVENT LOOP"
2331.PP
2332To include only the libev core (all the \f(CW\*(C`ev_*\*(C'\fR functions), with manual
2333configuration (no autoconf):
2334.PP
2335.Vb 2
2336\& #define EV_STANDALONE 1
2337\& #include "ev.c"
2338.Ve
2339.PP
2340This will automatically include \fIev.h\fR, too, and should be done in a
2341single C source file only to provide the function implementations. To use
2342it, do the same for \fIev.h\fR in all files wishing to use this \s-1API\s0 (best
2343done by writing a wrapper around \fIev.h\fR that you can include instead and
2344where you can put other configuration options):
2345.PP
2346.Vb 2
2347\& #define EV_STANDALONE 1
2348\& #include "ev.h"
2349.Ve
2350.PP
2351Both header files and implementation files can be compiled with a \*(C+
2352compiler (at least, thats a stated goal, and breakage will be treated
2353as a bug).
2354.PP
2355You need the following files in your source tree, or in a directory
2356in your include path (e.g. in libev/ when using \-Ilibev):
2357.PP
2358.Vb 4
2359\& ev.h
2360\& ev.c
2361\& ev_vars.h
2362\& ev_wrap.h
2363.Ve
2364.PP
2365.Vb 1
2366\& ev_win32.c required on win32 platforms only
2367.Ve
2368.PP
2369.Vb 5
2370\& ev_select.c only when select backend is enabled (which is enabled by default)
2371\& ev_poll.c only when poll backend is enabled (disabled by default)
2372\& ev_epoll.c only when the epoll backend is enabled (disabled by default)
2373\& ev_kqueue.c only when the kqueue backend is enabled (disabled by default)
2374\& ev_port.c only when the solaris port backend is enabled (disabled by default)
2375.Ve
2376.PP
2377\&\fIev.c\fR includes the backend files directly when enabled, so you only need
2378to compile this single file.
2379.PP
2380\fI\s-1LIBEVENT\s0 \s-1COMPATIBILITY\s0 \s-1API\s0\fR
2381.IX Subsection "LIBEVENT COMPATIBILITY API"
2382.PP
2383To include the libevent compatibility \s-1API\s0, also include:
2384.PP
2385.Vb 1
2386\& #include "event.c"
2387.Ve
2388.PP
2389in the file including \fIev.c\fR, and:
2390.PP
2391.Vb 1
2392\& #include "event.h"
2393.Ve
2394.PP
2395in the files that want to use the libevent \s-1API\s0. This also includes \fIev.h\fR.
2396.PP
2397You need the following additional files for this:
2398.PP
2399.Vb 2
2400\& event.h
2401\& event.c
2402.Ve
2403.PP
2404\fI\s-1AUTOCONF\s0 \s-1SUPPORT\s0\fR
2405.IX Subsection "AUTOCONF SUPPORT"
2406.PP
2407Instead of using \f(CW\*(C`EV_STANDALONE=1\*(C'\fR and providing your config in
2408whatever way you want, you can also \f(CW\*(C`m4_include([libev.m4])\*(C'\fR in your
2409\&\fIconfigure.ac\fR and leave \f(CW\*(C`EV_STANDALONE\*(C'\fR undefined. \fIev.c\fR will then
2410include \fIconfig.h\fR and configure itself accordingly.
2411.PP
2412For this of course you need the m4 file:
2413.PP
2414.Vb 1
2415\& libev.m4
2416.Ve
2417.Sh "\s-1PREPROCESSOR\s0 \s-1SYMBOLS/MACROS\s0"
2418.IX Subsection "PREPROCESSOR SYMBOLS/MACROS"
2419Libev can be configured via a variety of preprocessor symbols you have to define
2420before including any of its files. The default is not to build for multiplicity
2421and only include the select backend.
2422.IP "\s-1EV_STANDALONE\s0" 4
2423.IX Item "EV_STANDALONE"
2424Must always be \f(CW1\fR if you do not use autoconf configuration, which
2425keeps libev from including \fIconfig.h\fR, and it also defines dummy
2426implementations for some libevent functions (such as logging, which is not
2427supported). It will also not define any of the structs usually found in
2428\&\fIevent.h\fR that are not directly supported by the libev core alone.
2429.IP "\s-1EV_USE_MONOTONIC\s0" 4
2430.IX Item "EV_USE_MONOTONIC"
2431If defined to be \f(CW1\fR, libev will try to detect the availability of the
2432monotonic clock option at both compiletime and runtime. Otherwise no use
2433of the monotonic clock option will be attempted. If you enable this, you
2434usually have to link against librt or something similar. Enabling it when
2435the functionality isn't available is safe, though, althoguh you have
2436to make sure you link against any libraries where the \f(CW\*(C`clock_gettime\*(C'\fR
2437function is hiding in (often \fI\-lrt\fR).
2438.IP "\s-1EV_USE_REALTIME\s0" 4
2439.IX Item "EV_USE_REALTIME"
2440If defined to be \f(CW1\fR, libev will try to detect the availability of the
2441realtime clock option at compiletime (and assume its availability at
2442runtime if successful). Otherwise no use of the realtime clock option will
2443be attempted. This effectively replaces \f(CW\*(C`gettimeofday\*(C'\fR by \f(CW\*(C`clock_get
2444(CLOCK_REALTIME, ...)\*(C'\fR and will not normally affect correctness. See tzhe note about libraries
2445in the description of \f(CW\*(C`EV_USE_MONOTONIC\*(C'\fR, though.
2446.IP "\s-1EV_USE_SELECT\s0" 4
2447.IX Item "EV_USE_SELECT"
2448If undefined or defined to be \f(CW1\fR, libev will compile in support for the
2449\&\f(CW\*(C`select\*(C'\fR(2) backend. No attempt at autodetection will be done: if no
2450other method takes over, select will be it. Otherwise the select backend
2451will not be compiled in.
2452.IP "\s-1EV_SELECT_USE_FD_SET\s0" 4
2453.IX Item "EV_SELECT_USE_FD_SET"
2454If defined to \f(CW1\fR, then the select backend will use the system \f(CW\*(C`fd_set\*(C'\fR
2455structure. This is useful if libev doesn't compile due to a missing
2456\&\f(CW\*(C`NFDBITS\*(C'\fR or \f(CW\*(C`fd_mask\*(C'\fR definition or it misguesses the bitset layout on
2457exotic systems. This usually limits the range of file descriptors to some
2458low limit such as 1024 or might have other limitations (winsocket only
2459allows 64 sockets). The \f(CW\*(C`FD_SETSIZE\*(C'\fR macro, set before compilation, might
2460influence the size of the \f(CW\*(C`fd_set\*(C'\fR used.
2461.IP "\s-1EV_SELECT_IS_WINSOCKET\s0" 4
2462.IX Item "EV_SELECT_IS_WINSOCKET"
2463When defined to \f(CW1\fR, the select backend will assume that
2464select/socket/connect etc. don't understand file descriptors but
2465wants osf handles on win32 (this is the case when the select to
2466be used is the winsock select). This means that it will call
2467\&\f(CW\*(C`_get_osfhandle\*(C'\fR on the fd to convert it to an \s-1OS\s0 handle. Otherwise,
2468it is assumed that all these functions actually work on fds, even
2469on win32. Should not be defined on non\-win32 platforms.
2470.IP "\s-1EV_USE_POLL\s0" 4
2471.IX Item "EV_USE_POLL"
2472If defined to be \f(CW1\fR, libev will compile in support for the \f(CW\*(C`poll\*(C'\fR(2)
2473backend. Otherwise it will be enabled on non\-win32 platforms. It
2474takes precedence over select.
2475.IP "\s-1EV_USE_EPOLL\s0" 4
2476.IX Item "EV_USE_EPOLL"
2477If defined to be \f(CW1\fR, libev will compile in support for the Linux
2478\&\f(CW\*(C`epoll\*(C'\fR(7) backend. Its availability will be detected at runtime,
2479otherwise another method will be used as fallback. This is the
2480preferred backend for GNU/Linux systems.
2481.IP "\s-1EV_USE_KQUEUE\s0" 4
2482.IX Item "EV_USE_KQUEUE"
2483If defined to be \f(CW1\fR, libev will compile in support for the \s-1BSD\s0 style
2484\&\f(CW\*(C`kqueue\*(C'\fR(2) backend. Its actual availability will be detected at runtime,
2485otherwise another method will be used as fallback. This is the preferred
2486backend for \s-1BSD\s0 and BSD-like systems, although on most BSDs kqueue only
2487supports some types of fds correctly (the only platform we found that
2488supports ptys for example was NetBSD), so kqueue might be compiled in, but
2489not be used unless explicitly requested. The best way to use it is to find
2490out whether kqueue supports your type of fd properly and use an embedded
2491kqueue loop.
2492.IP "\s-1EV_USE_PORT\s0" 4
2493.IX Item "EV_USE_PORT"
2494If defined to be \f(CW1\fR, libev will compile in support for the Solaris
249510 port style backend. Its availability will be detected at runtime,
2496otherwise another method will be used as fallback. This is the preferred
2497backend for Solaris 10 systems.
2498.IP "\s-1EV_USE_DEVPOLL\s0" 4
2499.IX Item "EV_USE_DEVPOLL"
2500reserved for future expansion, works like the \s-1USE\s0 symbols above.
2501.IP "\s-1EV_USE_INOTIFY\s0" 4
2502.IX Item "EV_USE_INOTIFY"
2503If defined to be \f(CW1\fR, libev will compile in support for the Linux inotify
2504interface to speed up \f(CW\*(C`ev_stat\*(C'\fR watchers. Its actual availability will
2505be detected at runtime.
2506.IP "\s-1EV_H\s0" 4
2507.IX Item "EV_H"
2508The name of the \fIev.h\fR header file used to include it. The default if
2509undefined is \f(CW\*(C`<ev.h>\*(C'\fR in \fIevent.h\fR and \f(CW"ev.h"\fR in \fIev.c\fR. This
2510can be used to virtually rename the \fIev.h\fR header file in case of conflicts.
2511.IP "\s-1EV_CONFIG_H\s0" 4
2512.IX Item "EV_CONFIG_H"
2513If \f(CW\*(C`EV_STANDALONE\*(C'\fR isn't \f(CW1\fR, this variable can be used to override
2514\&\fIev.c\fR's idea of where to find the \fIconfig.h\fR file, similarly to
2515\&\f(CW\*(C`EV_H\*(C'\fR, above.
2516.IP "\s-1EV_EVENT_H\s0" 4
2517.IX Item "EV_EVENT_H"
2518Similarly to \f(CW\*(C`EV_H\*(C'\fR, this macro can be used to override \fIevent.c\fR's idea
2519of how the \fIevent.h\fR header can be found.
2520.IP "\s-1EV_PROTOTYPES\s0" 4
2521.IX Item "EV_PROTOTYPES"
2522If defined to be \f(CW0\fR, then \fIev.h\fR will not define any function
2523prototypes, but still define all the structs and other symbols. This is
2524occasionally useful if you want to provide your own wrapper functions
2525around libev functions.
2526.IP "\s-1EV_MULTIPLICITY\s0" 4
2527.IX Item "EV_MULTIPLICITY"
2528If undefined or defined to \f(CW1\fR, then all event-loop-specific functions
2529will have the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument, and you can create
2530additional independent event loops. Otherwise there will be no support
2531for multiple event loops and there is no first event loop pointer
2532argument. Instead, all functions act on the single default loop.
2533.IP "\s-1EV_MINPRI\s0" 4
2534.IX Item "EV_MINPRI"
2535.PD 0
2536.IP "\s-1EV_MAXPRI\s0" 4
2537.IX Item "EV_MAXPRI"
2538.PD
2539The range of allowed priorities. \f(CW\*(C`EV_MINPRI\*(C'\fR must be smaller or equal to
2540\&\f(CW\*(C`EV_MAXPRI\*(C'\fR, but otherwise there are no non-obvious limitations. You can
2541provide for more priorities by overriding those symbols (usually defined
2542to be \f(CW\*(C`\-2\*(C'\fR and \f(CW2\fR, respectively).
2543.Sp
2544When doing priority-based operations, libev usually has to linearly search
2545all the priorities, so having many of them (hundreds) uses a lot of space
2546and time, so using the defaults of five priorities (\-2 .. +2) is usually
2547fine.
2548.Sp
2549If your embedding app does not need any priorities, defining these both to
2550\&\f(CW0\fR will save some memory and cpu.
2551.IP "\s-1EV_PERIODIC_ENABLE\s0" 4
2552.IX Item "EV_PERIODIC_ENABLE"
2553If undefined or defined to be \f(CW1\fR, then periodic timers are supported. If
2554defined to be \f(CW0\fR, then they are not. Disabling them saves a few kB of
2555code.
2556.IP "\s-1EV_IDLE_ENABLE\s0" 4
2557.IX Item "EV_IDLE_ENABLE"
2558If undefined or defined to be \f(CW1\fR, then idle watchers are supported. If
2559defined to be \f(CW0\fR, then they are not. Disabling them saves a few kB of
2560code.
2561.IP "\s-1EV_EMBED_ENABLE\s0" 4
2562.IX Item "EV_EMBED_ENABLE"
2563If undefined or defined to be \f(CW1\fR, then embed watchers are supported. If
2564defined to be \f(CW0\fR, then they are not.
2565.IP "\s-1EV_STAT_ENABLE\s0" 4
2566.IX Item "EV_STAT_ENABLE"
2567If undefined or defined to be \f(CW1\fR, then stat watchers are supported. If
2568defined to be \f(CW0\fR, then they are not.
2569.IP "\s-1EV_FORK_ENABLE\s0" 4
2570.IX Item "EV_FORK_ENABLE"
2571If undefined or defined to be \f(CW1\fR, then fork watchers are supported. If
2572defined to be \f(CW0\fR, then they are not.
2573.IP "\s-1EV_MINIMAL\s0" 4
2574.IX Item "EV_MINIMAL"
2575If you need to shave off some kilobytes of code at the expense of some
2576speed, define this symbol to \f(CW1\fR. Currently only used for gcc to override
2577some inlining decisions, saves roughly 30% codesize of amd64.
2578.IP "\s-1EV_PID_HASHSIZE\s0" 4
2579.IX Item "EV_PID_HASHSIZE"
2580\&\f(CW\*(C`ev_child\*(C'\fR watchers use a small hash table to distribute workload by
2581pid. The default size is \f(CW16\fR (or \f(CW1\fR with \f(CW\*(C`EV_MINIMAL\*(C'\fR), usually more
2582than enough. If you need to manage thousands of children you might want to
2583increase this value (\fImust\fR be a power of two).
2584.IP "\s-1EV_INOTIFY_HASHSIZE\s0" 4
2585.IX Item "EV_INOTIFY_HASHSIZE"
2586\&\f(CW\*(C`ev_staz\*(C'\fR watchers use a small hash table to distribute workload by
2587inotify watch id. The default size is \f(CW16\fR (or \f(CW1\fR with \f(CW\*(C`EV_MINIMAL\*(C'\fR),
2588usually more than enough. If you need to manage thousands of \f(CW\*(C`ev_stat\*(C'\fR
2589watchers you might want to increase this value (\fImust\fR be a power of
2590two).
2591.IP "\s-1EV_COMMON\s0" 4
2592.IX Item "EV_COMMON"
2593By default, all watchers have a \f(CW\*(C`void *data\*(C'\fR member. By redefining
2594this macro to a something else you can include more and other types of
2595members. You have to define it each time you include one of the files,
2596though, and it must be identical each time.
2597.Sp
2598For example, the perl \s-1EV\s0 module uses something like this:
2599.Sp
2600.Vb 3
2601\& #define EV_COMMON \e
2602\& SV *self; /* contains this struct */ \e
2603\& SV *cb_sv, *fh /* note no trailing ";" */
2604.Ve
2605.IP "\s-1EV_CB_DECLARE\s0 (type)" 4
2606.IX Item "EV_CB_DECLARE (type)"
2607.PD 0
2608.IP "\s-1EV_CB_INVOKE\s0 (watcher, revents)" 4
2609.IX Item "EV_CB_INVOKE (watcher, revents)"
2610.IP "ev_set_cb (ev, cb)" 4
2611.IX Item "ev_set_cb (ev, cb)"
2612.PD
2613Can be used to change the callback member declaration in each watcher,
2614and the way callbacks are invoked and set. Must expand to a struct member
2615definition and a statement, respectively. See the \fIev.v\fR header file for
2616their default definitions. One possible use for overriding these is to
2617avoid the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument in all cases, or to use
2618method calls instead of plain function calls in \*(C+.
2619.Sh "\s-1EXAMPLES\s0"
2620.IX Subsection "EXAMPLES"
2621For a real-world example of a program the includes libev
2622verbatim, you can have a look at the \s-1EV\s0 perl module
2623(<http://software.schmorp.de/pkg/EV.html>). It has the libev files in
2624the \fIlibev/\fR subdirectory and includes them in the \fI\s-1EV/EVAPI\s0.h\fR (public
2625interface) and \fI\s-1EV\s0.xs\fR (implementation) files. Only the \fI\s-1EV\s0.xs\fR file
2626will be compiled. It is pretty complex because it provides its own header
2627file.
2628.Sp
2629The usage in rxvt-unicode is simpler. It has a \fIev_cpp.h\fR header file
2630that everybody includes and which overrides some configure choices:
2631.Sp
2632.Vb 9
2633\& #define EV_MINIMAL 1
2634\& #define EV_USE_POLL 0
2635\& #define EV_MULTIPLICITY 0
2636\& #define EV_PERIODIC_ENABLE 0
2637\& #define EV_STAT_ENABLE 0
2638\& #define EV_FORK_ENABLE 0
2639\& #define EV_CONFIG_H <config.h>
2640\& #define EV_MINPRI 0
2641\& #define EV_MAXPRI 0
2642.Ve
2643.Sp
2644.Vb 1
2645\& #include "ev++.h"
2646.Ve
2647.Sp
2648And a \fIev_cpp.C\fR implementation file that contains libev proper and is compiled:
2649.Sp
2650.Vb 2
2651\& #include "ev_cpp.h"
2652\& #include "ev.c"
2653.Ve
2654.SH "COMPLEXITIES"
2655.IX Header "COMPLEXITIES"
2656In this section the complexities of (many of) the algorithms used inside
2657libev will be explained. For complexity discussions about backends see the
2658documentation for \f(CW\*(C`ev_default_init\*(C'\fR.
2659.Sp
2660All of the following are about amortised time: If an array needs to be
2661extended, libev needs to realloc and move the whole array, but this
2662happens asymptotically never with higher number of elements, so O(1) might
2663mean it might do a lengthy realloc operation in rare cases, but on average
2664it is much faster and asymptotically approaches constant time.
2665.RS 4
2666.IP "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" 4
2667.IX Item "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)"
2668This means that, when you have a watcher that triggers in one hour and
2669there are 100 watchers that would trigger before that then inserting will
2670have to skip those 100 watchers.
2671.IP "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)" 4
2672.IX Item "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)"
2673That means that for changing a timer costs less than removing/adding them
2674as only the relative motion in the event queue has to be paid for.
2675.IP "Starting io/check/prepare/idle/signal/child watchers: O(1)" 4
2676.IX Item "Starting io/check/prepare/idle/signal/child watchers: O(1)"
2677These just add the watcher into an array or at the head of a list.
2678=item Stopping check/prepare/idle watchers: O(1)
2679.IP "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % \s-1EV_PID_HASHSIZE\s0))" 4
2680.IX Item "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))"
2681These watchers are stored in lists then need to be walked to find the
2682correct watcher to remove. The lists are usually short (you don't usually
2683have many watchers waiting for the same fd or signal).
2684.IP "Finding the next timer per loop iteration: O(1)" 4
2685.IX Item "Finding the next timer per loop iteration: O(1)"
2686.PD 0
2687.IP "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)" 4
2688.IX Item "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)"
2689.PD
2690A change means an I/O watcher gets started or stopped, which requires
2691libev to recalculate its status (and possibly tell the kernel).
2692.IP "Activating one watcher: O(1)" 4
2693.IX Item "Activating one watcher: O(1)"
2694.PD 0
2695.IP "Priority handling: O(number_of_priorities)" 4
2696.IX Item "Priority handling: O(number_of_priorities)"
2697.PD
2698Priorities are implemented by allocating some space for each
2699priority. When doing priority-based operations, libev usually has to
2700linearly search all the priorities.
2701.RE
2702.RS 4
995.SH "AUTHOR" 2703.SH "AUTHOR"
996.IX Header "AUTHOR" 2704.IX Header "AUTHOR"
997Marc Lehmann <libev@schmorp.de>. 2705Marc Lehmann <libev@schmorp.de>.

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines