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

Comparing libev/ev.3 (file contents):
Revision 1.11 by root, Sat Nov 24 07:14:26 2007 UTC vs.
Revision 1.29 by root, Tue Nov 27 20:38:07 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-24" "perl v5.8.8" "User Contributed Perl Documentation" 132.TH "<STANDARD INPUT>" 1 "2007-11-27" "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"
142Libev is an event loop: you register interest in certain events (such as a 201Libev 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 202file descriptor being readable or a timeout occuring), and it will manage
144these event sources and provide your program with events. 203these event sources and provide your program with events.
… …
151watchers\fR, which are relatively small C structures you initialise with the 210watchers\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 211details of the event, and then hand it over to libev by \fIstarting\fR the
153watcher. 212watcher.
154.SH "FEATURES" 213.SH "FEATURES"
155.IX Header "FEATURES" 214.IX Header "FEATURES"
156Libev supports select, poll, the linux-specific epoll and the bsd-specific 215Libev 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 216bsd-specific \f(CW\*(C`kqueue\*(C'\fR and the solaris-specific event port mechanisms
158timers with customised rescheduling, signal events, process status change 217for file descriptor events (\f(CW\*(C`ev_io\*(C'\fR), relative timers (\f(CW\*(C`ev_timer\*(C'\fR),
159events (related to \s-1SIGCHLD\s0), and event watchers dealing with the event 218absolute timers with customised rescheduling (\f(CW\*(C`ev_periodic\*(C'\fR), synchronous
160loop mechanism itself (idle, prepare and check watchers). It also is quite 219signals (\f(CW\*(C`ev_signal\*(C'\fR), process status change events (\f(CW\*(C`ev_child\*(C'\fR), and
161fast (see this benchmark comparing 220event watchers dealing with the event loop mechanism itself (\f(CW\*(C`ev_idle\*(C'\fR,
162it to libevent for example). 221\&\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
222file watchers (\f(CW\*(C`ev_stat\*(C'\fR) and even limited support for fork events
223(\f(CW\*(C`ev_fork\*(C'\fR).
224.PP
225It also is quite fast (see this
226benchmark comparing it to libevent
227for example).
163.SH "CONVENTIONS" 228.SH "CONVENTIONS"
164.IX Header "CONVENTIONS" 229.IX Header "CONVENTIONS"
165Libev is very configurable. In this manual the default configuration 230Libev is very configurable. In this manual the default configuration will
166will be described, which supports multiple event loops. For more info 231be described, which supports multiple event loops. For more info about
167about various configuration options please have a look at the file 232various 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 233this manual. If libev was configured without support for multiple event
169support for multiple event loops, then all functions taking an initial 234loops, 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) 235(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" 236.SH "TIME REPRESENTATION"
173.IX Header "TIME REPRESENTATION" 237.IX Header "TIME REPRESENTATION"
174Libev represents time as a single floating point number, representing the 238Libev represents time as a single floating point number, representing the
175(fractional) number of seconds since the (\s-1POSIX\s0) epoch (somewhere near 239(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 240the beginning of 1970, details are complicated, don't ask). This type is
… …
201Usually, it's a good idea to terminate if the major versions mismatch, 265Usually, it's a good idea to terminate if the major versions mismatch,
202as this indicates an incompatible change. Minor versions are usually 266as this indicates an incompatible change. Minor versions are usually
203compatible to older versions, so a larger minor version alone is usually 267compatible to older versions, so a larger minor version alone is usually
204not a problem. 268not a problem.
205.Sp 269.Sp
206Example: make sure we haven't accidentally been linked against the wrong 270Example: Make sure we haven't accidentally been linked against the wrong
207version: 271version.
208.Sp 272.Sp
209.Vb 3 273.Vb 3
210\& assert (("libev version mismatch", 274\& assert (("libev version mismatch",
211\& ev_version_major () == EV_VERSION_MAJOR 275\& ev_version_major () == EV_VERSION_MAJOR
212\& && ev_version_minor () >= EV_VERSION_MINOR)); 276\& && ev_version_minor () >= EV_VERSION_MINOR));
… …
240might be supported on the current system, you would need to look at 304might be supported on the current system, you would need to look at
241\&\f(CW\*(C`ev_embeddable_backends () & ev_supported_backends ()\*(C'\fR, likewise for 305\&\f(CW\*(C`ev_embeddable_backends () & ev_supported_backends ()\*(C'\fR, likewise for
242recommended ones. 306recommended ones.
243.Sp 307.Sp
244See the description of \f(CW\*(C`ev_embed\*(C'\fR watchers for more info. 308See the description of \f(CW\*(C`ev_embed\*(C'\fR watchers for more info.
245.IP "ev_set_allocator (void *(*cb)(void *ptr, long size))" 4 309.IP "ev_set_allocator (void *(*cb)(void *ptr, size_t size))" 4
246.IX Item "ev_set_allocator (void *(*cb)(void *ptr, long size))" 310.IX Item "ev_set_allocator (void *(*cb)(void *ptr, size_t size))"
247Sets the allocation function to use (the prototype is similar to the 311Sets the allocation function to use (the prototype and semantics are
248realloc C function, the semantics are identical). It is used to allocate 312identical to the realloc C function). It is used to allocate and free
249and free memory (no surprises here). If it returns zero when memory 313memory (no surprises here). If it returns zero when memory needs to be
250needs to be allocated, the library might abort or take some potentially 314allocated, the library might abort or take some potentially destructive
251destructive action. The default is your system realloc function. 315action. The default is your system realloc function.
252.Sp 316.Sp
253You could override this function in high-availability programs to, say, 317You could override this function in high-availability programs to, say,
254free some memory if it cannot allocate memory, to use a special allocator, 318free some memory if it cannot allocate memory, to use a special allocator,
255or even to sleep a while and retry until some memory is available. 319or even to sleep a while and retry until some memory is available.
256.Sp 320.Sp
257Example: replace the libev allocator with one that waits a bit and then 321Example: Replace the libev allocator with one that waits a bit and then
258retries: better than mine). 322retries).
259.Sp 323.Sp
260.Vb 6 324.Vb 6
261\& static void * 325\& static void *
262\& persistent_realloc (void *ptr, long size) 326\& persistent_realloc (void *ptr, size_t size)
263\& { 327\& {
264\& for (;;) 328\& for (;;)
265\& { 329\& {
266\& void *newptr = realloc (ptr, size); 330\& void *newptr = realloc (ptr, size);
267.Ve 331.Ve
… …
289callback is set, then libev will expect it to remedy the sitution, no 353callback is set, then libev will expect it to remedy the sitution, no
290matter what, when it returns. That is, libev will generally retry the 354matter what, when it returns. That is, libev will generally retry the
291requested operation, or, if the condition doesn't go away, do bad stuff 355requested operation, or, if the condition doesn't go away, do bad stuff
292(such as abort). 356(such as abort).
293.Sp 357.Sp
294Example: do the same thing as libev does internally: 358Example: This is basically the same thing that libev does internally, too.
295.Sp 359.Sp
296.Vb 6 360.Vb 6
297\& static void 361\& static void
298\& fatal_error (const char *msg) 362\& fatal_error (const char *msg)
299\& { 363\& {
… …
448Similar to \f(CW\*(C`ev_default_loop\*(C'\fR, but always creates a new event loop that is 512Similar to \f(CW\*(C`ev_default_loop\*(C'\fR, but always creates a new event loop that is
449always distinct from the default loop. Unlike the default loop, it cannot 513always distinct from the default loop. Unlike the default loop, it cannot
450handle signal and child watchers, and attempts to do so will be greeted by 514handle signal and child watchers, and attempts to do so will be greeted by
451undefined behaviour (or a failed assertion if assertions are enabled). 515undefined behaviour (or a failed assertion if assertions are enabled).
452.Sp 516.Sp
453Example: try to create a event loop that uses epoll and nothing else. 517Example: Try to create a event loop that uses epoll and nothing else.
454.Sp 518.Sp
455.Vb 3 519.Vb 3
456\& struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV); 520\& struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV);
457\& if (!epoller) 521\& if (!epoller)
458\& fatal ("no epoll found here, maybe it hides under your chair"); 522\& fatal ("no epoll found here, maybe it hides under your chair");
459.Ve 523.Ve
460.IP "ev_default_destroy ()" 4 524.IP "ev_default_destroy ()" 4
461.IX Item "ev_default_destroy ()" 525.IX Item "ev_default_destroy ()"
462Destroys the default loop again (frees all memory and kernel state 526Destroys the default loop again (frees all memory and kernel state
463etc.). This stops all registered event watchers (by not touching them in 527etc.). None of the active event watchers will be stopped in the normal
464any way whatsoever, although you cannot rely on this :). 528sense, so e.g. \f(CW\*(C`ev_is_active\*(C'\fR might still return true. It is your
529responsibility to either stop all watchers cleanly yoursef \fIbefore\fR
530calling this function, or cope with the fact afterwards (which is usually
531the easiest thing, youc na just ignore the watchers and/or \f(CW\*(C`free ()\*(C'\fR them
532for example).
465.IP "ev_loop_destroy (loop)" 4 533.IP "ev_loop_destroy (loop)" 4
466.IX Item "ev_loop_destroy (loop)" 534.IX Item "ev_loop_destroy (loop)"
467Like \f(CW\*(C`ev_default_destroy\*(C'\fR, but destroys an event loop created by an 535Like \f(CW\*(C`ev_default_destroy\*(C'\fR, but destroys an event loop created by an
468earlier call to \f(CW\*(C`ev_loop_new\*(C'\fR. 536earlier call to \f(CW\*(C`ev_loop_new\*(C'\fR.
469.IP "ev_default_fork ()" 4 537.IP "ev_default_fork ()" 4
… …
552\& be handled here by queueing them when their watcher gets executed. 620\& be handled here by queueing them when their watcher gets executed.
553\& - If ev_unloop has been called or EVLOOP_ONESHOT or EVLOOP_NONBLOCK 621\& - If ev_unloop has been called or EVLOOP_ONESHOT or EVLOOP_NONBLOCK
554\& were used, return, otherwise continue with step *. 622\& were used, return, otherwise continue with step *.
555.Ve 623.Ve
556.Sp 624.Sp
557Example: queue some jobs and then loop until no events are outsanding 625Example: Queue some jobs and then loop until no events are outsanding
558anymore. 626anymore.
559.Sp 627.Sp
560.Vb 4 628.Vb 4
561\& ... queue jobs here, make sure they register event watchers as long 629\& ... queue jobs here, make sure they register event watchers as long
562\& ... as they still have work to do (even an idle watcher will do..) 630\& ... as they still have work to do (even an idle watcher will do..)
… …
584visible to the libev user and should not keep \f(CW\*(C`ev_loop\*(C'\fR from exiting if 652visible to the libev user and should not keep \f(CW\*(C`ev_loop\*(C'\fR from exiting if
585no event watchers registered by it are active. It is also an excellent 653no event watchers registered by it are active. It is also an excellent
586way to do this for generic recurring timers or from within third-party 654way to do this for generic recurring timers or from within third-party
587libraries. Just remember to \fIunref after start\fR and \fIref before stop\fR. 655libraries. Just remember to \fIunref after start\fR and \fIref before stop\fR.
588.Sp 656.Sp
589Example: create a signal watcher, but keep it from keeping \f(CW\*(C`ev_loop\*(C'\fR 657Example: Create a signal watcher, but keep it from keeping \f(CW\*(C`ev_loop\*(C'\fR
590running when nothing else is active. 658running when nothing else is active.
591.Sp 659.Sp
592.Vb 4 660.Vb 4
593\& struct dv_signal exitsig; 661\& struct ev_signal exitsig;
594\& ev_signal_init (&exitsig, sig_cb, SIGINT); 662\& ev_signal_init (&exitsig, sig_cb, SIGINT);
595\& ev_signal_start (myloop, &exitsig); 663\& ev_signal_start (loop, &exitsig);
596\& evf_unref (myloop); 664\& evf_unref (loop);
597.Ve 665.Ve
598.Sp 666.Sp
599Example: for some weird reason, unregister the above signal handler again. 667Example: For some weird reason, unregister the above signal handler again.
600.Sp 668.Sp
601.Vb 2 669.Vb 2
602\& ev_ref (myloop); 670\& ev_ref (loop);
603\& ev_signal_stop (myloop, &exitsig); 671\& ev_signal_stop (loop, &exitsig);
604.Ve 672.Ve
605.SH "ANATOMY OF A WATCHER" 673.SH "ANATOMY OF A WATCHER"
606.IX Header "ANATOMY OF A WATCHER" 674.IX Header "ANATOMY OF A WATCHER"
607A watcher is a structure that you create and register to record your 675A watcher is a structure that you create and register to record your
608interest in some event. For instance, if you want to wait for \s-1STDIN\s0 to 676interest in some event. For instance, if you want to wait for \s-1STDIN\s0 to
… …
680The signal specified in the \f(CW\*(C`ev_signal\*(C'\fR watcher has been received by a thread. 748The signal specified in the \f(CW\*(C`ev_signal\*(C'\fR watcher has been received by a thread.
681.ie n .IP """EV_CHILD""" 4 749.ie n .IP """EV_CHILD""" 4
682.el .IP "\f(CWEV_CHILD\fR" 4 750.el .IP "\f(CWEV_CHILD\fR" 4
683.IX Item "EV_CHILD" 751.IX Item "EV_CHILD"
684The pid specified in the \f(CW\*(C`ev_child\*(C'\fR watcher has received a status change. 752The pid specified in the \f(CW\*(C`ev_child\*(C'\fR watcher has received a status change.
753.ie n .IP """EV_STAT""" 4
754.el .IP "\f(CWEV_STAT\fR" 4
755.IX Item "EV_STAT"
756The path specified in the \f(CW\*(C`ev_stat\*(C'\fR watcher changed its attributes somehow.
685.ie n .IP """EV_IDLE""" 4 757.ie n .IP """EV_IDLE""" 4
686.el .IP "\f(CWEV_IDLE\fR" 4 758.el .IP "\f(CWEV_IDLE\fR" 4
687.IX Item "EV_IDLE" 759.IX Item "EV_IDLE"
688The \f(CW\*(C`ev_idle\*(C'\fR watcher has determined that you have nothing better to do. 760The \f(CW\*(C`ev_idle\*(C'\fR watcher has determined that you have nothing better to do.
689.ie n .IP """EV_PREPARE""" 4 761.ie n .IP """EV_PREPARE""" 4
… …
699\&\f(CW\*(C`ev_loop\*(C'\fR has gathered them, but before it invokes any callbacks for any 771\&\f(CW\*(C`ev_loop\*(C'\fR has gathered them, but before it invokes any callbacks for any
700received events. Callbacks of both watcher types can start and stop as 772received events. Callbacks of both watcher types can start and stop as
701many watchers as they want, and all of them will be taken into account 773many watchers as they want, and all of them will be taken into account
702(for example, a \f(CW\*(C`ev_prepare\*(C'\fR watcher might start an idle watcher to keep 774(for example, a \f(CW\*(C`ev_prepare\*(C'\fR watcher might start an idle watcher to keep
703\&\f(CW\*(C`ev_loop\*(C'\fR from blocking). 775\&\f(CW\*(C`ev_loop\*(C'\fR from blocking).
776.ie n .IP """EV_EMBED""" 4
777.el .IP "\f(CWEV_EMBED\fR" 4
778.IX Item "EV_EMBED"
779The embedded event loop specified in the \f(CW\*(C`ev_embed\*(C'\fR watcher needs attention.
780.ie n .IP """EV_FORK""" 4
781.el .IP "\f(CWEV_FORK\fR" 4
782.IX Item "EV_FORK"
783The event loop has been resumed in the child process after fork (see
784\&\f(CW\*(C`ev_fork\*(C'\fR).
704.ie n .IP """EV_ERROR""" 4 785.ie n .IP """EV_ERROR""" 4
705.el .IP "\f(CWEV_ERROR\fR" 4 786.el .IP "\f(CWEV_ERROR\fR" 4
706.IX Item "EV_ERROR" 787.IX Item "EV_ERROR"
707An unspecified error has occured, the watcher has been stopped. This might 788An unspecified error has occured, the watcher has been stopped. This might
708happen because the watcher could not be properly started because libev 789happen because the watcher could not be properly started because libev
… …
713Libev will usually signal a few \*(L"dummy\*(R" events together with an error, 794Libev will usually signal a few \*(L"dummy\*(R" events together with an error,
714for example it might indicate that a fd is readable or writable, and if 795for example it might indicate that a fd is readable or writable, and if
715your callbacks is well-written it can just attempt the operation and cope 796your callbacks is well-written it can just attempt the operation and cope
716with the error from \fIread()\fR or \fIwrite()\fR. This will not work in multithreaded 797with the error from \fIread()\fR or \fIwrite()\fR. This will not work in multithreaded
717programs, though, so beware. 798programs, though, so beware.
718.Sh "\s-1SUMMARY\s0 \s-1OF\s0 \s-1GENERIC\s0 \s-1WATCHER\s0 \s-1FUNCTIONS\s0" 799.Sh "\s-1GENERIC\s0 \s-1WATCHER\s0 \s-1FUNCTIONS\s0"
719.IX Subsection "SUMMARY OF GENERIC WATCHER FUNCTIONS" 800.IX Subsection "GENERIC WATCHER FUNCTIONS"
720In the following description, \f(CW\*(C`TYPE\*(C'\fR stands for the watcher type, 801In the following description, \f(CW\*(C`TYPE\*(C'\fR stands for the watcher type,
721e.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. 802e.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.
722.ie n .IP """ev_init"" (ev_TYPE *watcher, callback)" 4 803.ie n .IP """ev_init"" (ev_TYPE *watcher, callback)" 4
723.el .IP "\f(CWev_init\fR (ev_TYPE *watcher, callback)" 4 804.el .IP "\f(CWev_init\fR (ev_TYPE *watcher, callback)" 4
724.IX Item "ev_init (ev_TYPE *watcher, callback)" 805.IX Item "ev_init (ev_TYPE *watcher, callback)"
… …
730which rolls both calls into one. 811which rolls both calls into one.
731.Sp 812.Sp
732You can reinitialise a watcher at any time as long as it has been stopped 813You can reinitialise a watcher at any time as long as it has been stopped
733(or never started) and there are no pending events outstanding. 814(or never started) and there are no pending events outstanding.
734.Sp 815.Sp
735The callbakc is always of type \f(CW\*(C`void (*)(ev_loop *loop, ev_TYPE *watcher, 816The callback is always of type \f(CW\*(C`void (*)(ev_loop *loop, ev_TYPE *watcher,
736int revents)\*(C'\fR. 817int revents)\*(C'\fR.
737.ie n .IP """ev_TYPE_set"" (ev_TYPE *, [args])" 4 818.ie n .IP """ev_TYPE_set"" (ev_TYPE *, [args])" 4
738.el .IP "\f(CWev_TYPE_set\fR (ev_TYPE *, [args])" 4 819.el .IP "\f(CWev_TYPE_set\fR (ev_TYPE *, [args])" 4
739.IX Item "ev_TYPE_set (ev_TYPE *, [args])" 820.IX Item "ev_TYPE_set (ev_TYPE *, [args])"
740This macro initialises the type-specific parts of a watcher. You need to 821This macro initialises the type-specific parts of a watcher. You need to
… …
775Returns a true value iff the watcher is pending, (i.e. it has outstanding 856Returns a true value iff the watcher is pending, (i.e. it has outstanding
776events but its callback has not yet been invoked). As long as a watcher 857events but its callback has not yet been invoked). As long as a watcher
777is pending (but not active) you must not call an init function on it (but 858is pending (but not active) you must not call an init function on it (but
778\&\f(CW\*(C`ev_TYPE_set\*(C'\fR is safe) and you must make sure the watcher is available to 859\&\f(CW\*(C`ev_TYPE_set\*(C'\fR is safe) and you must make sure the watcher is available to
779libev (e.g. you cnanot \f(CW\*(C`free ()\*(C'\fR it). 860libev (e.g. you cnanot \f(CW\*(C`free ()\*(C'\fR it).
780.IP "callback = ev_cb (ev_TYPE *watcher)" 4 861.IP "callback ev_cb (ev_TYPE *watcher)" 4
781.IX Item "callback = ev_cb (ev_TYPE *watcher)" 862.IX Item "callback ev_cb (ev_TYPE *watcher)"
782Returns the callback currently set on the watcher. 863Returns the callback currently set on the watcher.
783.IP "ev_cb_set (ev_TYPE *watcher, callback)" 4 864.IP "ev_cb_set (ev_TYPE *watcher, callback)" 4
784.IX Item "ev_cb_set (ev_TYPE *watcher, callback)" 865.IX Item "ev_cb_set (ev_TYPE *watcher, callback)"
785Change the callback. You can change the callback at virtually any time 866Change the callback. You can change the callback at virtually any time
786(modulo threads). 867(modulo threads).
… …
812\& struct my_io *w = (struct my_io *)w_; 893\& struct my_io *w = (struct my_io *)w_;
813\& ... 894\& ...
814\& } 895\& }
815.Ve 896.Ve
816.PP 897.PP
817More interesting and less C\-conformant ways of catsing your callback type 898More interesting and less C\-conformant ways of casting your callback type
818have been omitted.... 899instead have been omitted.
900.PP
901Another common scenario is having some data structure with multiple
902watchers:
903.PP
904.Vb 6
905\& struct my_biggy
906\& {
907\& int some_data;
908\& ev_timer t1;
909\& ev_timer t2;
910\& }
911.Ve
912.PP
913In this case getting the pointer to \f(CW\*(C`my_biggy\*(C'\fR is a bit more complicated,
914you need to use \f(CW\*(C`offsetof\*(C'\fR:
915.PP
916.Vb 1
917\& #include <stddef.h>
918.Ve
919.PP
920.Vb 6
921\& static void
922\& t1_cb (EV_P_ struct ev_timer *w, int revents)
923\& {
924\& struct my_biggy big = (struct my_biggy *
925\& (((char *)w) - offsetof (struct my_biggy, t1));
926\& }
927.Ve
928.PP
929.Vb 6
930\& static void
931\& t2_cb (EV_P_ struct ev_timer *w, int revents)
932\& {
933\& struct my_biggy big = (struct my_biggy *
934\& (((char *)w) - offsetof (struct my_biggy, t2));
935\& }
936.Ve
819.SH "WATCHER TYPES" 937.SH "WATCHER TYPES"
820.IX Header "WATCHER TYPES" 938.IX Header "WATCHER TYPES"
821This section describes each watcher in detail, but will not repeat 939This section describes each watcher in detail, but will not repeat
822information given in the last section. 940information given in the last section. Any initialisation/set macros,
941functions and members specific to the watcher type are explained.
942.PP
943Members are additionally marked with either \fI[read\-only]\fR, meaning that,
944while the watcher is active, you can look at the member and expect some
945sensible content, but you must not modify it (you can modify it while the
946watcher is stopped to your hearts content), or \fI[read\-write]\fR, which
947means you can expect it to have some sensible content while the watcher
948is active, but you can also modify it. Modifying it may not do something
949sensible or take immediate effect (or do anything at all), but libev will
950not crash or malfunction in any way.
823.ie n .Sh """ev_io"" \- is this file descriptor readable or writable" 951.ie n .Sh """ev_io"" \- is this file descriptor readable or writable?"
824.el .Sh "\f(CWev_io\fP \- is this file descriptor readable or writable" 952.el .Sh "\f(CWev_io\fP \- is this file descriptor readable or writable?"
825.IX Subsection "ev_io - is this file descriptor readable or writable" 953.IX Subsection "ev_io - is this file descriptor readable or writable?"
826I/O watchers check whether a file descriptor is readable or writable 954I/O watchers check whether a file descriptor is readable or writable
827in each iteration of the event loop (This behaviour is called 955in each iteration of the event loop, or, more precisely, when reading
828level-triggering because you keep receiving events as long as the 956would not block the process and writing would at least be able to write
829condition persists. Remember you can stop the watcher if you don't want to 957some data. This behaviour is called level-triggering because you keep
830act on the event and neither want to receive future events). 958receiving events as long as the condition persists. Remember you can stop
959the watcher if you don't want to act on the event and neither want to
960receive future events.
831.PP 961.PP
832In general you can register as many read and/or write event watchers per 962In general you can register as many read and/or write event watchers per
833fd as you want (as long as you don't confuse yourself). Setting all file 963fd as you want (as long as you don't confuse yourself). Setting all file
834descriptors to non-blocking mode is also usually a good idea (but not 964descriptors to non-blocking mode is also usually a good idea (but not
835required if you know what you are doing). 965required if you know what you are doing).
836.PP 966.PP
837You have to be careful with dup'ed file descriptors, though. Some backends 967You have to be careful with dup'ed file descriptors, though. Some backends
838(the linux epoll backend is a notable example) cannot handle dup'ed file 968(the linux epoll backend is a notable example) cannot handle dup'ed file
839descriptors correctly if you register interest in two or more fds pointing 969descriptors correctly if you register interest in two or more fds pointing
840to the same underlying file/socket etc. description (that is, they share 970to the same underlying file/socket/etc. description (that is, they share
841the same underlying \*(L"file open\*(R"). 971the same underlying \*(L"file open\*(R").
842.PP 972.PP
843If you must do this, then force the use of a known-to-be-good backend 973If you must do this, then force the use of a known-to-be-good backend
844(at the time of this writing, this includes only \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR and 974(at the time of this writing, this includes only \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR and
845\&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR). 975\&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR).
976.PP
977Another thing you have to watch out for is that it is quite easy to
978receive \*(L"spurious\*(R" readyness notifications, that is your callback might
979be called with \f(CW\*(C`EV_READ\*(C'\fR but a subsequent \f(CW\*(C`read\*(C'\fR(2) will actually block
980because there is no data. Not only are some backends known to create a
981lot of those (for example solaris ports), it is very easy to get into
982this situation even with a relatively standard program structure. Thus
983it is best to always use non-blocking I/O: An extra \f(CW\*(C`read\*(C'\fR(2) returning
984\&\f(CW\*(C`EAGAIN\*(C'\fR is far preferable to a program hanging until some data arrives.
985.PP
986If you cannot run the fd in non-blocking mode (for example you should not
987play around with an Xlib connection), then you have to seperately re-test
988wether a file descriptor is really ready with a known-to-be good interface
989such as poll (fortunately in our Xlib example, Xlib already does this on
990its own, so its quite safe to use).
846.IP "ev_io_init (ev_io *, callback, int fd, int events)" 4 991.IP "ev_io_init (ev_io *, callback, int fd, int events)" 4
847.IX Item "ev_io_init (ev_io *, callback, int fd, int events)" 992.IX Item "ev_io_init (ev_io *, callback, int fd, int events)"
848.PD 0 993.PD 0
849.IP "ev_io_set (ev_io *, int fd, int events)" 4 994.IP "ev_io_set (ev_io *, int fd, int events)" 4
850.IX Item "ev_io_set (ev_io *, int fd, int events)" 995.IX Item "ev_io_set (ev_io *, int fd, int events)"
851.PD 996.PD
852Configures an \f(CW\*(C`ev_io\*(C'\fR watcher. The fd is the file descriptor to rceeive 997Configures an \f(CW\*(C`ev_io\*(C'\fR watcher. The \f(CW\*(C`fd\*(C'\fR is the file descriptor to
853events 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 | 998rceeive events for and events is either \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR or
854EV_WRITE\*(C'\fR to receive the given events. 999\&\f(CW\*(C`EV_READ | EV_WRITE\*(C'\fR to receive the given events.
855.Sp 1000.IP "int fd [read\-only]" 4
856Please note that most of the more scalable backend mechanisms (for example 1001.IX Item "int fd [read-only]"
857epoll and solaris ports) can result in spurious readyness notifications 1002The file descriptor being watched.
858for file descriptors, so you practically need to use non-blocking I/O (and 1003.IP "int events [read\-only]" 4
859treat callback invocation as hint only), or retest separately with a safe 1004.IX Item "int events [read-only]"
860interface before doing I/O (XLib can do this), or force the use of either 1005The events being watched.
861\&\f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or \f(CW\*(C`EVBACKEND_POLL\*(C'\fR, which don't suffer from this
862problem. Also note that it is quite easy to have your callback invoked
863when the readyness condition is no longer valid even when employing
864typical ways of handling events, so its a good idea to use non-blocking
865I/O unconditionally.
866.PP 1006.PP
867Example: call \f(CW\*(C`stdin_readable_cb\*(C'\fR when \s-1STDIN_FILENO\s0 has become, well 1007Example: Call \f(CW\*(C`stdin_readable_cb\*(C'\fR when \s-1STDIN_FILENO\s0 has become, well
868readable, but only once. Since it is likely line\-buffered, you could 1008readable, but only once. Since it is likely line\-buffered, you could
869attempt to read a whole line in the callback: 1009attempt to read a whole line in the callback.
870.PP 1010.PP
871.Vb 6 1011.Vb 6
872\& static void 1012\& static void
873\& stdin_readable_cb (struct ev_loop *loop, struct ev_io *w, int revents) 1013\& stdin_readable_cb (struct ev_loop *loop, struct ev_io *w, int revents)
874\& { 1014\& {
… …
883\& struct ev_io stdin_readable; 1023\& struct ev_io stdin_readable;
884\& ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ); 1024\& ev_io_init (&stdin_readable, stdin_readable_cb, STDIN_FILENO, EV_READ);
885\& ev_io_start (loop, &stdin_readable); 1025\& ev_io_start (loop, &stdin_readable);
886\& ev_loop (loop, 0); 1026\& ev_loop (loop, 0);
887.Ve 1027.Ve
888.ie n .Sh """ev_timer"" \- relative and optionally recurring timeouts" 1028.ie n .Sh """ev_timer"" \- relative and optionally repeating timeouts"
889.el .Sh "\f(CWev_timer\fP \- relative and optionally recurring timeouts" 1029.el .Sh "\f(CWev_timer\fP \- relative and optionally repeating timeouts"
890.IX Subsection "ev_timer - relative and optionally recurring timeouts" 1030.IX Subsection "ev_timer - relative and optionally repeating timeouts"
891Timer watchers are simple relative timers that generate an event after a 1031Timer watchers are simple relative timers that generate an event after a
892given time, and optionally repeating in regular intervals after that. 1032given time, and optionally repeating in regular intervals after that.
893.PP 1033.PP
894The timers are based on real time, that is, if you register an event that 1034The timers are based on real time, that is, if you register an event that
895times out after an hour and you reset your system clock to last years 1035times out after an hour and you reset your system clock to last years
… …
935.Sp 1075.Sp
936If the timer is repeating, either start it if necessary (with the repeat 1076If the timer is repeating, either start it if necessary (with the repeat
937value), or reset the running timer to the repeat value. 1077value), or reset the running timer to the repeat value.
938.Sp 1078.Sp
939This sounds a bit complicated, but here is a useful and typical 1079This sounds a bit complicated, but here is a useful and typical
940example: Imagine you have a tcp connection and you want a so-called idle 1080example: Imagine you have a tcp connection and you want a so-called
941timeout, that is, you want to be called when there have been, say, 60 1081idle timeout, that is, you want to be called when there have been,
942seconds of inactivity on the socket. The easiest way to do this is to 1082say, 60 seconds of inactivity on the socket. The easiest way to do
943configure an \f(CW\*(C`ev_timer\*(C'\fR with after=repeat=60 and calling ev_timer_again each 1083this is to configure an \f(CW\*(C`ev_timer\*(C'\fR with \f(CW\*(C`after\*(C'\fR=\f(CW\*(C`repeat\*(C'\fR=\f(CW60\fR and calling
944time you successfully read or write some data. If you go into an idle 1084\&\f(CW\*(C`ev_timer_again\*(C'\fR each time you successfully read or write some data. If
945state where you do not expect data to travel on the socket, you can stop 1085you go into an idle state where you do not expect data to travel on the
946the timer, and again will automatically restart it if need be. 1086socket, you can stop the timer, and again will automatically restart it if
1087need be.
1088.Sp
1089You can also ignore the \f(CW\*(C`after\*(C'\fR value and \f(CW\*(C`ev_timer_start\*(C'\fR altogether
1090and only ever use the \f(CW\*(C`repeat\*(C'\fR value:
1091.Sp
1092.Vb 8
1093\& ev_timer_init (timer, callback, 0., 5.);
1094\& ev_timer_again (loop, timer);
1095\& ...
1096\& timer->again = 17.;
1097\& ev_timer_again (loop, timer);
1098\& ...
1099\& timer->again = 10.;
1100\& ev_timer_again (loop, timer);
1101.Ve
1102.Sp
1103This is more efficient then stopping/starting the timer eahc time you want
1104to modify its timeout value.
1105.IP "ev_tstamp repeat [read\-write]" 4
1106.IX Item "ev_tstamp repeat [read-write]"
1107The current \f(CW\*(C`repeat\*(C'\fR value. Will be used each time the watcher times out
1108or \f(CW\*(C`ev_timer_again\*(C'\fR is called and determines the next timeout (if any),
1109which is also when any modifications are taken into account.
947.PP 1110.PP
948Example: create a timer that fires after 60 seconds. 1111Example: Create a timer that fires after 60 seconds.
949.PP 1112.PP
950.Vb 5 1113.Vb 5
951\& static void 1114\& static void
952\& one_minute_cb (struct ev_loop *loop, struct ev_timer *w, int revents) 1115\& one_minute_cb (struct ev_loop *loop, struct ev_timer *w, int revents)
953\& { 1116\& {
… …
959\& struct ev_timer mytimer; 1122\& struct ev_timer mytimer;
960\& ev_timer_init (&mytimer, one_minute_cb, 60., 0.); 1123\& ev_timer_init (&mytimer, one_minute_cb, 60., 0.);
961\& ev_timer_start (loop, &mytimer); 1124\& ev_timer_start (loop, &mytimer);
962.Ve 1125.Ve
963.PP 1126.PP
964Example: create a timeout timer that times out after 10 seconds of 1127Example: Create a timeout timer that times out after 10 seconds of
965inactivity. 1128inactivity.
966.PP 1129.PP
967.Vb 5 1130.Vb 5
968\& static void 1131\& static void
969\& timeout_cb (struct ev_loop *loop, struct ev_timer *w, int revents) 1132\& timeout_cb (struct ev_loop *loop, struct ev_timer *w, int revents)
… …
982.Vb 3 1145.Vb 3
983\& // and in some piece of code that gets executed on any "activity": 1146\& // and in some piece of code that gets executed on any "activity":
984\& // reset the timeout to start ticking again at 10 seconds 1147\& // reset the timeout to start ticking again at 10 seconds
985\& ev_timer_again (&mytimer); 1148\& ev_timer_again (&mytimer);
986.Ve 1149.Ve
987.ie n .Sh """ev_periodic"" \- to cron or not to cron" 1150.ie n .Sh """ev_periodic"" \- to cron or not to cron?"
988.el .Sh "\f(CWev_periodic\fP \- to cron or not to cron" 1151.el .Sh "\f(CWev_periodic\fP \- to cron or not to cron?"
989.IX Subsection "ev_periodic - to cron or not to cron" 1152.IX Subsection "ev_periodic - to cron or not to cron?"
990Periodic watchers are also timers of a kind, but they are very versatile 1153Periodic watchers are also timers of a kind, but they are very versatile
991(and unfortunately a bit complex). 1154(and unfortunately a bit complex).
992.PP 1155.PP
993Unlike \f(CW\*(C`ev_timer\*(C'\fR's, they are not based on real time (or relative time) 1156Unlike \f(CW\*(C`ev_timer\*(C'\fR's, they are not based on real time (or relative time)
994but on wallclock time (absolute time). You can tell a periodic watcher 1157but on wallclock time (absolute time). You can tell a periodic watcher
995to trigger \*(L"at\*(R" some specific point in time. For example, if you tell a 1158to trigger \*(L"at\*(R" some specific point in time. For example, if you tell a
996periodic watcher to trigger in 10 seconds (by specifiying e.g. c<ev_now () 1159periodic watcher to trigger in 10 seconds (by specifiying e.g. \f(CW\*(C`ev_now ()
997+ 10.>) and then reset your system clock to the last year, then it will 1160+ 10.\*(C'\fR) and then reset your system clock to the last year, then it will
998take a year to trigger the event (unlike an \f(CW\*(C`ev_timer\*(C'\fR, which would trigger 1161take a year to trigger the event (unlike an \f(CW\*(C`ev_timer\*(C'\fR, which would trigger
999roughly 10 seconds later and of course not if you reset your system time 1162roughly 10 seconds later and of course not if you reset your system time
1000again). 1163again).
1001.PP 1164.PP
1002They can also be used to implement vastly more complex timers, such as 1165They can also be used to implement vastly more complex timers, such as
… …
1083.IX Item "ev_periodic_again (loop, ev_periodic *)" 1246.IX Item "ev_periodic_again (loop, ev_periodic *)"
1084Simply stops and restarts the periodic watcher again. This is only useful 1247Simply stops and restarts the periodic watcher again. This is only useful
1085when you changed some parameters or the reschedule callback would return 1248when you changed some parameters or the reschedule callback would return
1086a different time than the last time it was called (e.g. in a crond like 1249a different time than the last time it was called (e.g. in a crond like
1087program when the crontabs have changed). 1250program when the crontabs have changed).
1251.IP "ev_tstamp interval [read\-write]" 4
1252.IX Item "ev_tstamp interval [read-write]"
1253The current interval value. Can be modified any time, but changes only
1254take effect when the periodic timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being
1255called.
1256.IP "ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read\-write]" 4
1257.IX Item "ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read-write]"
1258The current reschedule callback, or \f(CW0\fR, if this functionality is
1259switched off. Can be changed any time, but changes only take effect when
1260the periodic timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being called.
1088.PP 1261.PP
1089Example: call a callback every hour, or, more precisely, whenever the 1262Example: Call a callback every hour, or, more precisely, whenever the
1090system clock is divisible by 3600. The callback invocation times have 1263system clock is divisible by 3600. The callback invocation times have
1091potentially a lot of jittering, but good long-term stability. 1264potentially a lot of jittering, but good long-term stability.
1092.PP 1265.PP
1093.Vb 5 1266.Vb 5
1094\& static void 1267\& static void
… …
1102\& struct ev_periodic hourly_tick; 1275\& struct ev_periodic hourly_tick;
1103\& ev_periodic_init (&hourly_tick, clock_cb, 0., 3600., 0); 1276\& ev_periodic_init (&hourly_tick, clock_cb, 0., 3600., 0);
1104\& ev_periodic_start (loop, &hourly_tick); 1277\& ev_periodic_start (loop, &hourly_tick);
1105.Ve 1278.Ve
1106.PP 1279.PP
1107Example: the same as above, but use a reschedule callback to do it: 1280Example: The same as above, but use a reschedule callback to do it:
1108.PP 1281.PP
1109.Vb 1 1282.Vb 1
1110\& #include <math.h> 1283\& #include <math.h>
1111.Ve 1284.Ve
1112.PP 1285.PP
… …
1120.PP 1293.PP
1121.Vb 1 1294.Vb 1
1122\& ev_periodic_init (&hourly_tick, clock_cb, 0., 0., my_scheduler_cb); 1295\& ev_periodic_init (&hourly_tick, clock_cb, 0., 0., my_scheduler_cb);
1123.Ve 1296.Ve
1124.PP 1297.PP
1125Example: call a callback every hour, starting now: 1298Example: Call a callback every hour, starting now:
1126.PP 1299.PP
1127.Vb 4 1300.Vb 4
1128\& struct ev_periodic hourly_tick; 1301\& struct ev_periodic hourly_tick;
1129\& ev_periodic_init (&hourly_tick, clock_cb, 1302\& ev_periodic_init (&hourly_tick, clock_cb,
1130\& fmod (ev_now (loop), 3600.), 3600., 0); 1303\& fmod (ev_now (loop), 3600.), 3600., 0);
1131\& ev_periodic_start (loop, &hourly_tick); 1304\& ev_periodic_start (loop, &hourly_tick);
1132.Ve 1305.Ve
1133.ie n .Sh """ev_signal"" \- signal me when a signal gets signalled" 1306.ie n .Sh """ev_signal"" \- signal me when a signal gets signalled!"
1134.el .Sh "\f(CWev_signal\fP \- signal me when a signal gets signalled" 1307.el .Sh "\f(CWev_signal\fP \- signal me when a signal gets signalled!"
1135.IX Subsection "ev_signal - signal me when a signal gets signalled" 1308.IX Subsection "ev_signal - signal me when a signal gets signalled!"
1136Signal watchers will trigger an event when the process receives a specific 1309Signal watchers will trigger an event when the process receives a specific
1137signal one or more times. Even though signals are very asynchronous, libev 1310signal one or more times. Even though signals are very asynchronous, libev
1138will try it's best to deliver signals synchronously, i.e. as part of the 1311will try it's best to deliver signals synchronously, i.e. as part of the
1139normal event processing, like any other event. 1312normal event processing, like any other event.
1140.PP 1313.PP
… …
1150.IP "ev_signal_set (ev_signal *, int signum)" 4 1323.IP "ev_signal_set (ev_signal *, int signum)" 4
1151.IX Item "ev_signal_set (ev_signal *, int signum)" 1324.IX Item "ev_signal_set (ev_signal *, int signum)"
1152.PD 1325.PD
1153Configures the watcher to trigger on the given signal number (usually one 1326Configures the watcher to trigger on the given signal number (usually one
1154of the \f(CW\*(C`SIGxxx\*(C'\fR constants). 1327of the \f(CW\*(C`SIGxxx\*(C'\fR constants).
1328.IP "int signum [read\-only]" 4
1329.IX Item "int signum [read-only]"
1330The signal the watcher watches out for.
1155.ie n .Sh """ev_child"" \- wait for pid status changes" 1331.ie n .Sh """ev_child"" \- watch out for process status changes"
1156.el .Sh "\f(CWev_child\fP \- wait for pid status changes" 1332.el .Sh "\f(CWev_child\fP \- watch out for process status changes"
1157.IX Subsection "ev_child - wait for pid status changes" 1333.IX Subsection "ev_child - watch out for process status changes"
1158Child watchers trigger when your process receives a \s-1SIGCHLD\s0 in response to 1334Child watchers trigger when your process receives a \s-1SIGCHLD\s0 in response to
1159some child status changes (most typically when a child of yours dies). 1335some child status changes (most typically when a child of yours dies).
1160.IP "ev_child_init (ev_child *, callback, int pid)" 4 1336.IP "ev_child_init (ev_child *, callback, int pid)" 4
1161.IX Item "ev_child_init (ev_child *, callback, int pid)" 1337.IX Item "ev_child_init (ev_child *, callback, int pid)"
1162.PD 0 1338.PD 0
… …
1167\&\fIany\fR process if \f(CW\*(C`pid\*(C'\fR is specified as \f(CW0\fR). The callback can look 1343\&\fIany\fR process if \f(CW\*(C`pid\*(C'\fR is specified as \f(CW0\fR). The callback can look
1168at the \f(CW\*(C`rstatus\*(C'\fR member of the \f(CW\*(C`ev_child\*(C'\fR watcher structure to see 1344at the \f(CW\*(C`rstatus\*(C'\fR member of the \f(CW\*(C`ev_child\*(C'\fR watcher structure to see
1169the status word (use the macros from \f(CW\*(C`sys/wait.h\*(C'\fR and see your systems 1345the status word (use the macros from \f(CW\*(C`sys/wait.h\*(C'\fR and see your systems
1170\&\f(CW\*(C`waitpid\*(C'\fR documentation). The \f(CW\*(C`rpid\*(C'\fR member contains the pid of the 1346\&\f(CW\*(C`waitpid\*(C'\fR documentation). The \f(CW\*(C`rpid\*(C'\fR member contains the pid of the
1171process causing the status change. 1347process causing the status change.
1348.IP "int pid [read\-only]" 4
1349.IX Item "int pid [read-only]"
1350The process id this watcher watches out for, or \f(CW0\fR, meaning any process id.
1351.IP "int rpid [read\-write]" 4
1352.IX Item "int rpid [read-write]"
1353The process id that detected a status change.
1354.IP "int rstatus [read\-write]" 4
1355.IX Item "int rstatus [read-write]"
1356The process exit/trace status caused by \f(CW\*(C`rpid\*(C'\fR (see your systems
1357\&\f(CW\*(C`waitpid\*(C'\fR and \f(CW\*(C`sys/wait.h\*(C'\fR documentation for details).
1172.PP 1358.PP
1173Example: try to exit cleanly on \s-1SIGINT\s0 and \s-1SIGTERM\s0. 1359Example: Try to exit cleanly on \s-1SIGINT\s0 and \s-1SIGTERM\s0.
1174.PP 1360.PP
1175.Vb 5 1361.Vb 5
1176\& static void 1362\& static void
1177\& sigint_cb (struct ev_loop *loop, struct ev_signal *w, int revents) 1363\& sigint_cb (struct ev_loop *loop, struct ev_signal *w, int revents)
1178\& { 1364\& {
… …
1183.Vb 3 1369.Vb 3
1184\& struct ev_signal signal_watcher; 1370\& struct ev_signal signal_watcher;
1185\& ev_signal_init (&signal_watcher, sigint_cb, SIGINT); 1371\& ev_signal_init (&signal_watcher, sigint_cb, SIGINT);
1186\& ev_signal_start (loop, &sigint_cb); 1372\& ev_signal_start (loop, &sigint_cb);
1187.Ve 1373.Ve
1374.ie n .Sh """ev_stat"" \- did the file attributes just change?"
1375.el .Sh "\f(CWev_stat\fP \- did the file attributes just change?"
1376.IX Subsection "ev_stat - did the file attributes just change?"
1377This watches a filesystem path for attribute changes. That is, it calls
1378\&\f(CW\*(C`stat\*(C'\fR regularly (or when the \s-1OS\s0 says it changed) and sees if it changed
1379compared to the last time, invoking the callback if it did.
1380.PP
1381The path does not need to exist: changing from \*(L"path exists\*(R" to \*(L"path does
1382not exist\*(R" is a status change like any other. The condition \*(L"path does
1383not exist\*(R" is signified by the \f(CW\*(C`st_nlink\*(C'\fR field being zero (which is
1384otherwise always forced to be at least one) and all the other fields of
1385the stat buffer having unspecified contents.
1386.PP
1387Since there is no standard to do this, the portable implementation simply
1388calls \f(CW\*(C`stat (2)\*(C'\fR regulalry on the path to see if it changed somehow. You
1389can specify a recommended polling interval for this case. If you specify
1390a polling interval of \f(CW0\fR (highly recommended!) then a \fIsuitable,
1391unspecified default\fR value will be used (which you can expect to be around
1392five seconds, although this might change dynamically). Libev will also
1393impose a minimum interval which is currently around \f(CW0.1\fR, but thats
1394usually overkill.
1395.PP
1396This watcher type is not meant for massive numbers of stat watchers,
1397as even with OS-supported change notifications, this can be
1398resource\-intensive.
1399.PP
1400At the time of this writing, no specific \s-1OS\s0 backends are implemented, but
1401if demand increases, at least a kqueue and inotify backend will be added.
1402.IP "ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)" 4
1403.IX Item "ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)"
1404.PD 0
1405.IP "ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)" 4
1406.IX Item "ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)"
1407.PD
1408Configures the watcher to wait for status changes of the given
1409\&\f(CW\*(C`path\*(C'\fR. The \f(CW\*(C`interval\*(C'\fR is a hint on how quickly a change is expected to
1410be detected and should normally be specified as \f(CW0\fR to let libev choose
1411a suitable value. The memory pointed to by \f(CW\*(C`path\*(C'\fR must point to the same
1412path for as long as the watcher is active.
1413.Sp
1414The callback will be receive \f(CW\*(C`EV_STAT\*(C'\fR when a change was detected,
1415relative to the attributes at the time the watcher was started (or the
1416last change was detected).
1417.IP "ev_stat_stat (ev_stat *)" 4
1418.IX Item "ev_stat_stat (ev_stat *)"
1419Updates the stat buffer immediately with new values. If you change the
1420watched path in your callback, you could call this fucntion to avoid
1421detecting this change (while introducing a race condition). Can also be
1422useful simply to find out the new values.
1423.IP "ev_statdata attr [read\-only]" 4
1424.IX Item "ev_statdata attr [read-only]"
1425The most-recently detected attributes of the file. Although the type is of
1426\&\f(CW\*(C`ev_statdata\*(C'\fR, this is usually the (or one of the) \f(CW\*(C`struct stat\*(C'\fR types
1427suitable for your system. If the \f(CW\*(C`st_nlink\*(C'\fR member is \f(CW0\fR, then there
1428was some error while \f(CW\*(C`stat\*(C'\fRing the file.
1429.IP "ev_statdata prev [read\-only]" 4
1430.IX Item "ev_statdata prev [read-only]"
1431The previous attributes of the file. The callback gets invoked whenever
1432\&\f(CW\*(C`prev\*(C'\fR != \f(CW\*(C`attr\*(C'\fR.
1433.IP "ev_tstamp interval [read\-only]" 4
1434.IX Item "ev_tstamp interval [read-only]"
1435The specified interval.
1436.IP "const char *path [read\-only]" 4
1437.IX Item "const char *path [read-only]"
1438The filesystem path that is being watched.
1439.PP
1440Example: Watch \f(CW\*(C`/etc/passwd\*(C'\fR for attribute changes.
1441.PP
1442.Vb 15
1443\& static void
1444\& passwd_cb (struct ev_loop *loop, ev_stat *w, int revents)
1445\& {
1446\& /* /etc/passwd changed in some way */
1447\& if (w->attr.st_nlink)
1448\& {
1449\& printf ("passwd current size %ld\en", (long)w->attr.st_size);
1450\& printf ("passwd current atime %ld\en", (long)w->attr.st_mtime);
1451\& printf ("passwd current mtime %ld\en", (long)w->attr.st_mtime);
1452\& }
1453\& else
1454\& /* you shalt not abuse printf for puts */
1455\& puts ("wow, /etc/passwd is not there, expect problems. "
1456\& "if this is windows, they already arrived\en");
1457\& }
1458.Ve
1459.PP
1460.Vb 2
1461\& ...
1462\& ev_stat passwd;
1463.Ve
1464.PP
1465.Vb 2
1466\& ev_stat_init (&passwd, passwd_cb, "/etc/passwd");
1467\& ev_stat_start (loop, &passwd);
1468.Ve
1188.ie n .Sh """ev_idle"" \- when you've got nothing better to do" 1469.ie n .Sh """ev_idle"" \- when you've got nothing better to do..."
1189.el .Sh "\f(CWev_idle\fP \- when you've got nothing better to do" 1470.el .Sh "\f(CWev_idle\fP \- when you've got nothing better to do..."
1190.IX Subsection "ev_idle - when you've got nothing better to do" 1471.IX Subsection "ev_idle - when you've got nothing better to do..."
1191Idle watchers trigger events when there are no other events are pending 1472Idle watchers trigger events when there are no other events are pending
1192(prepare, check and other idle watchers do not count). That is, as long 1473(prepare, check and other idle watchers do not count). That is, as long
1193as your process is busy handling sockets or timeouts (or even signals, 1474as your process is busy handling sockets or timeouts (or even signals,
1194imagine) it will not be triggered. But when your process is idle all idle 1475imagine) it will not be triggered. But when your process is idle all idle
1195watchers are being called again and again, once per event loop iteration \- 1476watchers are being called again and again, once per event loop iteration \-
… …
1207.IX Item "ev_idle_init (ev_signal *, callback)" 1488.IX Item "ev_idle_init (ev_signal *, callback)"
1208Initialises and configures the idle watcher \- it has no parameters of any 1489Initialises and configures the idle watcher \- it has no parameters of any
1209kind. There is a \f(CW\*(C`ev_idle_set\*(C'\fR macro, but using it is utterly pointless, 1490kind. There is a \f(CW\*(C`ev_idle_set\*(C'\fR macro, but using it is utterly pointless,
1210believe me. 1491believe me.
1211.PP 1492.PP
1212Example: dynamically allocate an \f(CW\*(C`ev_idle\*(C'\fR, start it, and in the 1493Example: Dynamically allocate an \f(CW\*(C`ev_idle\*(C'\fR watcher, start it, and in the
1213callback, free it. Alos, use no error checking, as usual. 1494callback, free it. Also, use no error checking, as usual.
1214.PP 1495.PP
1215.Vb 7 1496.Vb 7
1216\& static void 1497\& static void
1217\& idle_cb (struct ev_loop *loop, struct ev_idle *w, int revents) 1498\& idle_cb (struct ev_loop *loop, struct ev_idle *w, int revents)
1218\& { 1499\& {
… …
1225.Vb 3 1506.Vb 3
1226\& struct ev_idle *idle_watcher = malloc (sizeof (struct ev_idle)); 1507\& struct ev_idle *idle_watcher = malloc (sizeof (struct ev_idle));
1227\& ev_idle_init (idle_watcher, idle_cb); 1508\& ev_idle_init (idle_watcher, idle_cb);
1228\& ev_idle_start (loop, idle_cb); 1509\& ev_idle_start (loop, idle_cb);
1229.Ve 1510.Ve
1230.ie n .Sh """ev_prepare""\fP and \f(CW""ev_check"" \- customise your event loop" 1511.ie n .Sh """ev_prepare""\fP and \f(CW""ev_check"" \- customise your event loop!"
1231.el .Sh "\f(CWev_prepare\fP and \f(CWev_check\fP \- customise your event loop" 1512.el .Sh "\f(CWev_prepare\fP and \f(CWev_check\fP \- customise your event loop!"
1232.IX Subsection "ev_prepare and ev_check - customise your event loop" 1513.IX Subsection "ev_prepare and ev_check - customise your event loop!"
1233Prepare and check watchers are usually (but not always) used in tandem: 1514Prepare and check watchers are usually (but not always) used in tandem:
1234prepare watchers get invoked before the process blocks and check watchers 1515prepare watchers get invoked before the process blocks and check watchers
1235afterwards. 1516afterwards.
1236.PP 1517.PP
1518You \fImust not\fR call \f(CW\*(C`ev_loop\*(C'\fR or similar functions that enter
1519the current event loop from either \f(CW\*(C`ev_prepare\*(C'\fR or \f(CW\*(C`ev_check\*(C'\fR
1520watchers. Other loops than the current one are fine, however. The
1521rationale behind this is that you do not need to check for recursion in
1522those watchers, i.e. the sequence will always be \f(CW\*(C`ev_prepare\*(C'\fR, blocking,
1523\&\f(CW\*(C`ev_check\*(C'\fR so if you have one watcher of each kind they will always be
1524called in pairs bracketing the blocking call.
1525.PP
1237Their main purpose is to integrate other event mechanisms into libev and 1526Their main purpose is to integrate other event mechanisms into libev and
1238their use is somewhat advanced. This could be used, for example, to track 1527their use is somewhat advanced. This could be used, for example, to track
1239variable changes, implement your own watchers, integrate net-snmp or a 1528variable changes, implement your own watchers, integrate net-snmp or a
1240coroutine library and lots more. 1529coroutine library and lots more. They are also occasionally useful if
1530you cache some data and want to flush it before blocking (for example,
1531in X programs you might want to do an \f(CW\*(C`XFlush ()\*(C'\fR in an \f(CW\*(C`ev_prepare\*(C'\fR
1532watcher).
1241.PP 1533.PP
1242This is done by examining in each prepare call which file descriptors need 1534This is done by examining in each prepare call which file descriptors need
1243to be watched by the other library, registering \f(CW\*(C`ev_io\*(C'\fR watchers for 1535to be watched by the other library, registering \f(CW\*(C`ev_io\*(C'\fR watchers for
1244them and starting an \f(CW\*(C`ev_timer\*(C'\fR watcher for any timeouts (many libraries 1536them and starting an \f(CW\*(C`ev_timer\*(C'\fR watcher for any timeouts (many libraries
1245provide just this functionality). Then, in the check watcher you check for 1537provide just this functionality). Then, in the check watcher you check for
… …
1264.PD 1556.PD
1265Initialises and configures the prepare or check watcher \- they have no 1557Initialises and configures the prepare or check watcher \- they have no
1266parameters of any kind. There are \f(CW\*(C`ev_prepare_set\*(C'\fR and \f(CW\*(C`ev_check_set\*(C'\fR 1558parameters of any kind. There are \f(CW\*(C`ev_prepare_set\*(C'\fR and \f(CW\*(C`ev_check_set\*(C'\fR
1267macros, but using them is utterly, utterly and completely pointless. 1559macros, but using them is utterly, utterly and completely pointless.
1268.PP 1560.PP
1269Example: *TODO*. 1561Example: To include a library such as adns, you would add \s-1IO\s0 watchers
1562and a timeout watcher in a prepare handler, as required by libadns, and
1563in a check watcher, destroy them and call into libadns. What follows is
1564pseudo-code only of course:
1565.PP
1566.Vb 2
1567\& static ev_io iow [nfd];
1568\& static ev_timer tw;
1569.Ve
1570.PP
1571.Vb 9
1572\& static void
1573\& io_cb (ev_loop *loop, ev_io *w, int revents)
1574\& {
1575\& // set the relevant poll flags
1576\& // could also call adns_processreadable etc. here
1577\& struct pollfd *fd = (struct pollfd *)w->data;
1578\& if (revents & EV_READ ) fd->revents |= fd->events & POLLIN;
1579\& if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT;
1580\& }
1581.Ve
1582.PP
1583.Vb 7
1584\& // create io watchers for each fd and a timer before blocking
1585\& static void
1586\& adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents)
1587\& {
1588\& int timeout = 3600000;truct pollfd fds [nfd];
1589\& // actual code will need to loop here and realloc etc.
1590\& adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ()));
1591.Ve
1592.PP
1593.Vb 3
1594\& /* the callback is illegal, but won't be called as we stop during check */
1595\& ev_timer_init (&tw, 0, timeout * 1e-3);
1596\& ev_timer_start (loop, &tw);
1597.Ve
1598.PP
1599.Vb 6
1600\& // create on ev_io per pollfd
1601\& for (int i = 0; i < nfd; ++i)
1602\& {
1603\& ev_io_init (iow + i, io_cb, fds [i].fd,
1604\& ((fds [i].events & POLLIN ? EV_READ : 0)
1605\& | (fds [i].events & POLLOUT ? EV_WRITE : 0)));
1606.Ve
1607.PP
1608.Vb 5
1609\& fds [i].revents = 0;
1610\& iow [i].data = fds + i;
1611\& ev_io_start (loop, iow + i);
1612\& }
1613\& }
1614.Ve
1615.PP
1616.Vb 5
1617\& // stop all watchers after blocking
1618\& static void
1619\& adns_check_cb (ev_loop *loop, ev_check *w, int revents)
1620\& {
1621\& ev_timer_stop (loop, &tw);
1622.Ve
1623.PP
1624.Vb 2
1625\& for (int i = 0; i < nfd; ++i)
1626\& ev_io_stop (loop, iow + i);
1627.Ve
1628.PP
1629.Vb 2
1630\& adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop));
1631\& }
1632.Ve
1270.ie n .Sh """ev_embed"" \- when one backend isn't enough" 1633.ie n .Sh """ev_embed"" \- when one backend isn't enough..."
1271.el .Sh "\f(CWev_embed\fP \- when one backend isn't enough" 1634.el .Sh "\f(CWev_embed\fP \- when one backend isn't enough..."
1272.IX Subsection "ev_embed - when one backend isn't enough" 1635.IX Subsection "ev_embed - when one backend isn't enough..."
1273This is a rather advanced watcher type that lets you embed one event loop 1636This is a rather advanced watcher type that lets you embed one event loop
1274into another (currently only \f(CW\*(C`ev_io\*(C'\fR events are supported in the embedded 1637into another (currently only \f(CW\*(C`ev_io\*(C'\fR events are supported in the embedded
1275loop, other types of watchers might be handled in a delayed or incorrect 1638loop, other types of watchers might be handled in a delayed or incorrect
1276fashion and must not be used). 1639fashion and must not be used).
1277.PP 1640.PP
… …
1357.IP "ev_embed_sweep (loop, ev_embed *)" 4 1720.IP "ev_embed_sweep (loop, ev_embed *)" 4
1358.IX Item "ev_embed_sweep (loop, ev_embed *)" 1721.IX Item "ev_embed_sweep (loop, ev_embed *)"
1359Make a single, non-blocking sweep over the embedded loop. This works 1722Make a single, non-blocking sweep over the embedded loop. This works
1360similarly to \f(CW\*(C`ev_loop (embedded_loop, EVLOOP_NONBLOCK)\*(C'\fR, but in the most 1723similarly to \f(CW\*(C`ev_loop (embedded_loop, EVLOOP_NONBLOCK)\*(C'\fR, but in the most
1361apropriate way for embedded loops. 1724apropriate way for embedded loops.
1725.IP "struct ev_loop *loop [read\-only]" 4
1726.IX Item "struct ev_loop *loop [read-only]"
1727The embedded event loop.
1728.ie n .Sh """ev_fork"" \- the audacity to resume the event loop after a fork"
1729.el .Sh "\f(CWev_fork\fP \- the audacity to resume the event loop after a fork"
1730.IX Subsection "ev_fork - the audacity to resume the event loop after a fork"
1731Fork watchers are called when a \f(CW\*(C`fork ()\*(C'\fR was detected (usually because
1732whoever is a good citizen cared to tell libev about it by calling
1733\&\f(CW\*(C`ev_default_fork\*(C'\fR or \f(CW\*(C`ev_loop_fork\*(C'\fR). The invocation is done before the
1734event loop blocks next and before \f(CW\*(C`ev_check\*(C'\fR watchers are being called,
1735and only in the child after the fork. If whoever good citizen calling
1736\&\f(CW\*(C`ev_default_fork\*(C'\fR cheats and calls it in the wrong process, the fork
1737handlers will be invoked, too, of course.
1738.IP "ev_fork_init (ev_signal *, callback)" 4
1739.IX Item "ev_fork_init (ev_signal *, callback)"
1740Initialises and configures the fork watcher \- it has no parameters of any
1741kind. There is a \f(CW\*(C`ev_fork_set\*(C'\fR macro, but using it is utterly pointless,
1742believe me.
1362.SH "OTHER FUNCTIONS" 1743.SH "OTHER FUNCTIONS"
1363.IX Header "OTHER FUNCTIONS" 1744.IX Header "OTHER FUNCTIONS"
1364There are some other functions of possible interest. Described. Here. Now. 1745There are some other functions of possible interest. Described. Here. Now.
1365.IP "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)" 4 1746.IP "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)" 4
1366.IX Item "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)" 1747.IX Item "ev_once (loop, int fd, int events, ev_tstamp timeout, callback)"
… …
1428.IP "* The libev emulation is \fInot\fR \s-1ABI\s0 compatible to libevent, you need to use the libev header file and library." 4 1809.IP "* The libev emulation is \fInot\fR \s-1ABI\s0 compatible to libevent, you need to use the libev header file and library." 4
1429.IX Item "The libev emulation is not ABI compatible to libevent, you need to use the libev header file and library." 1810.IX Item "The libev emulation is not ABI compatible to libevent, you need to use the libev header file and library."
1430.PD 1811.PD
1431.SH "\*(C+ SUPPORT" 1812.SH "\*(C+ SUPPORT"
1432.IX Header " SUPPORT" 1813.IX Header " SUPPORT"
1433\&\s-1TBD\s0. 1814Libev comes with some simplistic wrapper classes for \*(C+ that mainly allow
1815you to use some convinience methods to start/stop watchers and also change
1816the callback model to a model using method callbacks on objects.
1817.PP
1818To use it,
1819.PP
1820.Vb 1
1821\& #include <ev++.h>
1822.Ve
1823.PP
1824(it is not installed by default). This automatically includes \fIev.h\fR
1825and puts all of its definitions (many of them macros) into the global
1826namespace. All \*(C+ specific things are put into the \f(CW\*(C`ev\*(C'\fR namespace.
1827.PP
1828It should support all the same embedding options as \fIev.h\fR, most notably
1829\&\f(CW\*(C`EV_MULTIPLICITY\*(C'\fR.
1830.PP
1831Here is a list of things available in the \f(CW\*(C`ev\*(C'\fR namespace:
1832.ie n .IP """ev::READ""\fR, \f(CW""ev::WRITE"" etc." 4
1833.el .IP "\f(CWev::READ\fR, \f(CWev::WRITE\fR etc." 4
1834.IX Item "ev::READ, ev::WRITE etc."
1835These are just enum values with the same values as the \f(CW\*(C`EV_READ\*(C'\fR etc.
1836macros from \fIev.h\fR.
1837.ie n .IP """ev::tstamp""\fR, \f(CW""ev::now""" 4
1838.el .IP "\f(CWev::tstamp\fR, \f(CWev::now\fR" 4
1839.IX Item "ev::tstamp, ev::now"
1840Aliases to the same types/functions as with the \f(CW\*(C`ev_\*(C'\fR prefix.
1841.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
1842.el .IP "\f(CWev::io\fR, \f(CWev::timer\fR, \f(CWev::periodic\fR, \f(CWev::idle\fR, \f(CWev::sig\fR etc." 4
1843.IX Item "ev::io, ev::timer, ev::periodic, ev::idle, ev::sig etc."
1844For each \f(CW\*(C`ev_TYPE\*(C'\fR watcher in \fIev.h\fR there is a corresponding class of
1845the same name in the \f(CW\*(C`ev\*(C'\fR namespace, with the exception of \f(CW\*(C`ev_signal\*(C'\fR
1846which is called \f(CW\*(C`ev::sig\*(C'\fR to avoid clashes with the \f(CW\*(C`signal\*(C'\fR macro
1847defines by many implementations.
1848.Sp
1849All of those classes have these methods:
1850.RS 4
1851.IP "ev::TYPE::TYPE (object *, object::method *)" 4
1852.IX Item "ev::TYPE::TYPE (object *, object::method *)"
1853.PD 0
1854.IP "ev::TYPE::TYPE (object *, object::method *, struct ev_loop *)" 4
1855.IX Item "ev::TYPE::TYPE (object *, object::method *, struct ev_loop *)"
1856.IP "ev::TYPE::~TYPE" 4
1857.IX Item "ev::TYPE::~TYPE"
1858.PD
1859The constructor takes a pointer to an object and a method pointer to
1860the event handler callback to call in this class. The constructor calls
1861\&\f(CW\*(C`ev_init\*(C'\fR for you, which means you have to call the \f(CW\*(C`set\*(C'\fR method
1862before starting it. If you do not specify a loop then the constructor
1863automatically associates the default loop with this watcher.
1864.Sp
1865The destructor automatically stops the watcher if it is active.
1866.IP "w\->set (struct ev_loop *)" 4
1867.IX Item "w->set (struct ev_loop *)"
1868Associates a different \f(CW\*(C`struct ev_loop\*(C'\fR with this watcher. You can only
1869do this when the watcher is inactive (and not pending either).
1870.IP "w\->set ([args])" 4
1871.IX Item "w->set ([args])"
1872Basically the same as \f(CW\*(C`ev_TYPE_set\*(C'\fR, with the same args. Must be
1873called at least once. Unlike the C counterpart, an active watcher gets
1874automatically stopped and restarted.
1875.IP "w\->start ()" 4
1876.IX Item "w->start ()"
1877Starts the watcher. Note that there is no \f(CW\*(C`loop\*(C'\fR argument as the
1878constructor already takes the loop.
1879.IP "w\->stop ()" 4
1880.IX Item "w->stop ()"
1881Stops the watcher if it is active. Again, no \f(CW\*(C`loop\*(C'\fR argument.
1882.ie n .IP "w\->again () ""ev::timer""\fR, \f(CW""ev::periodic"" only" 4
1883.el .IP "w\->again () \f(CWev::timer\fR, \f(CWev::periodic\fR only" 4
1884.IX Item "w->again () ev::timer, ev::periodic only"
1885For \f(CW\*(C`ev::timer\*(C'\fR and \f(CW\*(C`ev::periodic\*(C'\fR, this invokes the corresponding
1886\&\f(CW\*(C`ev_TYPE_again\*(C'\fR function.
1887.ie n .IP "w\->sweep () ""ev::embed"" only" 4
1888.el .IP "w\->sweep () \f(CWev::embed\fR only" 4
1889.IX Item "w->sweep () ev::embed only"
1890Invokes \f(CW\*(C`ev_embed_sweep\*(C'\fR.
1891.ie n .IP "w\->update () ""ev::stat"" only" 4
1892.el .IP "w\->update () \f(CWev::stat\fR only" 4
1893.IX Item "w->update () ev::stat only"
1894Invokes \f(CW\*(C`ev_stat_stat\*(C'\fR.
1895.RE
1896.RS 4
1897.RE
1898.PP
1899Example: Define a class with an \s-1IO\s0 and idle watcher, start one of them in
1900the constructor.
1901.PP
1902.Vb 4
1903\& class myclass
1904\& {
1905\& ev_io io; void io_cb (ev::io &w, int revents);
1906\& ev_idle idle void idle_cb (ev::idle &w, int revents);
1907.Ve
1908.PP
1909.Vb 2
1910\& myclass ();
1911\& }
1912.Ve
1913.PP
1914.Vb 6
1915\& myclass::myclass (int fd)
1916\& : io (this, &myclass::io_cb),
1917\& idle (this, &myclass::idle_cb)
1918\& {
1919\& io.start (fd, ev::READ);
1920\& }
1921.Ve
1922.SH "MACRO MAGIC"
1923.IX Header "MACRO MAGIC"
1924Libev can be compiled with a variety of options, the most fundemantal is
1925\&\f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. This option determines wether (most) functions and
1926callbacks have an initial \f(CW\*(C`struct ev_loop *\*(C'\fR argument.
1927.PP
1928To make it easier to write programs that cope with either variant, the
1929following macros are defined:
1930.ie n .IP """EV_A""\fR, \f(CW""EV_A_""" 4
1931.el .IP "\f(CWEV_A\fR, \f(CWEV_A_\fR" 4
1932.IX Item "EV_A, EV_A_"
1933This provides the loop \fIargument\fR for functions, if one is required (\*(L"ev
1934loop argument\*(R"). The \f(CW\*(C`EV_A\*(C'\fR form is used when this is the sole argument,
1935\&\f(CW\*(C`EV_A_\*(C'\fR is used when other arguments are following. Example:
1936.Sp
1937.Vb 3
1938\& ev_unref (EV_A);
1939\& ev_timer_add (EV_A_ watcher);
1940\& ev_loop (EV_A_ 0);
1941.Ve
1942.Sp
1943It assumes the variable \f(CW\*(C`loop\*(C'\fR of type \f(CW\*(C`struct ev_loop *\*(C'\fR is in scope,
1944which is often provided by the following macro.
1945.ie n .IP """EV_P""\fR, \f(CW""EV_P_""" 4
1946.el .IP "\f(CWEV_P\fR, \f(CWEV_P_\fR" 4
1947.IX Item "EV_P, EV_P_"
1948This provides the loop \fIparameter\fR for functions, if one is required (\*(L"ev
1949loop parameter\*(R"). The \f(CW\*(C`EV_P\*(C'\fR form is used when this is the sole parameter,
1950\&\f(CW\*(C`EV_P_\*(C'\fR is used when other parameters are following. Example:
1951.Sp
1952.Vb 2
1953\& // this is how ev_unref is being declared
1954\& static void ev_unref (EV_P);
1955.Ve
1956.Sp
1957.Vb 2
1958\& // this is how you can declare your typical callback
1959\& static void cb (EV_P_ ev_timer *w, int revents)
1960.Ve
1961.Sp
1962It declares a parameter \f(CW\*(C`loop\*(C'\fR of type \f(CW\*(C`struct ev_loop *\*(C'\fR, quite
1963suitable for use with \f(CW\*(C`EV_A\*(C'\fR.
1964.ie n .IP """EV_DEFAULT""\fR, \f(CW""EV_DEFAULT_""" 4
1965.el .IP "\f(CWEV_DEFAULT\fR, \f(CWEV_DEFAULT_\fR" 4
1966.IX Item "EV_DEFAULT, EV_DEFAULT_"
1967Similar to the other two macros, this gives you the value of the default
1968loop, if multiple loops are supported (\*(L"ev loop default\*(R").
1969.PP
1970Example: Declare and initialise a check watcher, working regardless of
1971wether multiple loops are supported or not.
1972.PP
1973.Vb 5
1974\& static void
1975\& check_cb (EV_P_ ev_timer *w, int revents)
1976\& {
1977\& ev_check_stop (EV_A_ w);
1978\& }
1979.Ve
1980.PP
1981.Vb 4
1982\& ev_check check;
1983\& ev_check_init (&check, check_cb);
1984\& ev_check_start (EV_DEFAULT_ &check);
1985\& ev_loop (EV_DEFAULT_ 0);
1986.Ve
1987.SH "EMBEDDING"
1988.IX Header "EMBEDDING"
1989Libev can (and often is) directly embedded into host
1990applications. Examples of applications that embed it include the Deliantra
1991Game Server, the \s-1EV\s0 perl module, the \s-1GNU\s0 Virtual Private Ethernet (gvpe)
1992and rxvt\-unicode.
1993.PP
1994The goal is to enable you to just copy the neecssary files into your
1995source directory without having to change even a single line in them, so
1996you can easily upgrade by simply copying (or having a checked-out copy of
1997libev somewhere in your source tree).
1998.Sh "\s-1FILESETS\s0"
1999.IX Subsection "FILESETS"
2000Depending on what features you need you need to include one or more sets of files
2001in your app.
2002.PP
2003\fI\s-1CORE\s0 \s-1EVENT\s0 \s-1LOOP\s0\fR
2004.IX Subsection "CORE EVENT LOOP"
2005.PP
2006To include only the libev core (all the \f(CW\*(C`ev_*\*(C'\fR functions), with manual
2007configuration (no autoconf):
2008.PP
2009.Vb 2
2010\& #define EV_STANDALONE 1
2011\& #include "ev.c"
2012.Ve
2013.PP
2014This will automatically include \fIev.h\fR, too, and should be done in a
2015single C source file only to provide the function implementations. To use
2016it, do the same for \fIev.h\fR in all files wishing to use this \s-1API\s0 (best
2017done by writing a wrapper around \fIev.h\fR that you can include instead and
2018where you can put other configuration options):
2019.PP
2020.Vb 2
2021\& #define EV_STANDALONE 1
2022\& #include "ev.h"
2023.Ve
2024.PP
2025Both header files and implementation files can be compiled with a \*(C+
2026compiler (at least, thats a stated goal, and breakage will be treated
2027as a bug).
2028.PP
2029You need the following files in your source tree, or in a directory
2030in your include path (e.g. in libev/ when using \-Ilibev):
2031.PP
2032.Vb 4
2033\& ev.h
2034\& ev.c
2035\& ev_vars.h
2036\& ev_wrap.h
2037.Ve
2038.PP
2039.Vb 1
2040\& ev_win32.c required on win32 platforms only
2041.Ve
2042.PP
2043.Vb 5
2044\& ev_select.c only when select backend is enabled (which is by default)
2045\& ev_poll.c only when poll backend is enabled (disabled by default)
2046\& ev_epoll.c only when the epoll backend is enabled (disabled by default)
2047\& ev_kqueue.c only when the kqueue backend is enabled (disabled by default)
2048\& ev_port.c only when the solaris port backend is enabled (disabled by default)
2049.Ve
2050.PP
2051\&\fIev.c\fR includes the backend files directly when enabled, so you only need
2052to compile this single file.
2053.PP
2054\fI\s-1LIBEVENT\s0 \s-1COMPATIBILITY\s0 \s-1API\s0\fR
2055.IX Subsection "LIBEVENT COMPATIBILITY API"
2056.PP
2057To include the libevent compatibility \s-1API\s0, also include:
2058.PP
2059.Vb 1
2060\& #include "event.c"
2061.Ve
2062.PP
2063in the file including \fIev.c\fR, and:
2064.PP
2065.Vb 1
2066\& #include "event.h"
2067.Ve
2068.PP
2069in the files that want to use the libevent \s-1API\s0. This also includes \fIev.h\fR.
2070.PP
2071You need the following additional files for this:
2072.PP
2073.Vb 2
2074\& event.h
2075\& event.c
2076.Ve
2077.PP
2078\fI\s-1AUTOCONF\s0 \s-1SUPPORT\s0\fR
2079.IX Subsection "AUTOCONF SUPPORT"
2080.PP
2081Instead of using \f(CW\*(C`EV_STANDALONE=1\*(C'\fR and providing your config in
2082whatever way you want, you can also \f(CW\*(C`m4_include([libev.m4])\*(C'\fR in your
2083\&\fIconfigure.ac\fR and leave \f(CW\*(C`EV_STANDALONE\*(C'\fR undefined. \fIev.c\fR will then
2084include \fIconfig.h\fR and configure itself accordingly.
2085.PP
2086For this of course you need the m4 file:
2087.PP
2088.Vb 1
2089\& libev.m4
2090.Ve
2091.Sh "\s-1PREPROCESSOR\s0 \s-1SYMBOLS/MACROS\s0"
2092.IX Subsection "PREPROCESSOR SYMBOLS/MACROS"
2093Libev can be configured via a variety of preprocessor symbols you have to define
2094before including any of its files. The default is not to build for multiplicity
2095and only include the select backend.
2096.IP "\s-1EV_STANDALONE\s0" 4
2097.IX Item "EV_STANDALONE"
2098Must always be \f(CW1\fR if you do not use autoconf configuration, which
2099keeps libev from including \fIconfig.h\fR, and it also defines dummy
2100implementations for some libevent functions (such as logging, which is not
2101supported). It will also not define any of the structs usually found in
2102\&\fIevent.h\fR that are not directly supported by the libev core alone.
2103.IP "\s-1EV_USE_MONOTONIC\s0" 4
2104.IX Item "EV_USE_MONOTONIC"
2105If defined to be \f(CW1\fR, libev will try to detect the availability of the
2106monotonic clock option at both compiletime and runtime. Otherwise no use
2107of the monotonic clock option will be attempted. If you enable this, you
2108usually have to link against librt or something similar. Enabling it when
2109the functionality isn't available is safe, though, althoguh you have
2110to make sure you link against any libraries where the \f(CW\*(C`clock_gettime\*(C'\fR
2111function is hiding in (often \fI\-lrt\fR).
2112.IP "\s-1EV_USE_REALTIME\s0" 4
2113.IX Item "EV_USE_REALTIME"
2114If defined to be \f(CW1\fR, libev will try to detect the availability of the
2115realtime clock option at compiletime (and assume its availability at
2116runtime if successful). Otherwise no use of the realtime clock option will
2117be attempted. This effectively replaces \f(CW\*(C`gettimeofday\*(C'\fR by \f(CW\*(C`clock_get
2118(CLOCK_REALTIME, ...)\*(C'\fR and will not normally affect correctness. See tzhe note about libraries
2119in the description of \f(CW\*(C`EV_USE_MONOTONIC\*(C'\fR, though.
2120.IP "\s-1EV_USE_SELECT\s0" 4
2121.IX Item "EV_USE_SELECT"
2122If undefined or defined to be \f(CW1\fR, libev will compile in support for the
2123\&\f(CW\*(C`select\*(C'\fR(2) backend. No attempt at autodetection will be done: if no
2124other method takes over, select will be it. Otherwise the select backend
2125will not be compiled in.
2126.IP "\s-1EV_SELECT_USE_FD_SET\s0" 4
2127.IX Item "EV_SELECT_USE_FD_SET"
2128If defined to \f(CW1\fR, then the select backend will use the system \f(CW\*(C`fd_set\*(C'\fR
2129structure. This is useful if libev doesn't compile due to a missing
2130\&\f(CW\*(C`NFDBITS\*(C'\fR or \f(CW\*(C`fd_mask\*(C'\fR definition or it misguesses the bitset layout on
2131exotic systems. This usually limits the range of file descriptors to some
2132low limit such as 1024 or might have other limitations (winsocket only
2133allows 64 sockets). The \f(CW\*(C`FD_SETSIZE\*(C'\fR macro, set before compilation, might
2134influence the size of the \f(CW\*(C`fd_set\*(C'\fR used.
2135.IP "\s-1EV_SELECT_IS_WINSOCKET\s0" 4
2136.IX Item "EV_SELECT_IS_WINSOCKET"
2137When defined to \f(CW1\fR, the select backend will assume that
2138select/socket/connect etc. don't understand file descriptors but
2139wants osf handles on win32 (this is the case when the select to
2140be used is the winsock select). This means that it will call
2141\&\f(CW\*(C`_get_osfhandle\*(C'\fR on the fd to convert it to an \s-1OS\s0 handle. Otherwise,
2142it is assumed that all these functions actually work on fds, even
2143on win32. Should not be defined on non\-win32 platforms.
2144.IP "\s-1EV_USE_POLL\s0" 4
2145.IX Item "EV_USE_POLL"
2146If defined to be \f(CW1\fR, libev will compile in support for the \f(CW\*(C`poll\*(C'\fR(2)
2147backend. Otherwise it will be enabled on non\-win32 platforms. It
2148takes precedence over select.
2149.IP "\s-1EV_USE_EPOLL\s0" 4
2150.IX Item "EV_USE_EPOLL"
2151If defined to be \f(CW1\fR, libev will compile in support for the Linux
2152\&\f(CW\*(C`epoll\*(C'\fR(7) backend. Its availability will be detected at runtime,
2153otherwise another method will be used as fallback. This is the
2154preferred backend for GNU/Linux systems.
2155.IP "\s-1EV_USE_KQUEUE\s0" 4
2156.IX Item "EV_USE_KQUEUE"
2157If defined to be \f(CW1\fR, libev will compile in support for the \s-1BSD\s0 style
2158\&\f(CW\*(C`kqueue\*(C'\fR(2) backend. Its actual availability will be detected at runtime,
2159otherwise another method will be used as fallback. This is the preferred
2160backend for \s-1BSD\s0 and BSD-like systems, although on most BSDs kqueue only
2161supports some types of fds correctly (the only platform we found that
2162supports ptys for example was NetBSD), so kqueue might be compiled in, but
2163not be used unless explicitly requested. The best way to use it is to find
2164out whether kqueue supports your type of fd properly and use an embedded
2165kqueue loop.
2166.IP "\s-1EV_USE_PORT\s0" 4
2167.IX Item "EV_USE_PORT"
2168If defined to be \f(CW1\fR, libev will compile in support for the Solaris
216910 port style backend. Its availability will be detected at runtime,
2170otherwise another method will be used as fallback. This is the preferred
2171backend for Solaris 10 systems.
2172.IP "\s-1EV_USE_DEVPOLL\s0" 4
2173.IX Item "EV_USE_DEVPOLL"
2174reserved for future expansion, works like the \s-1USE\s0 symbols above.
2175.IP "\s-1EV_H\s0" 4
2176.IX Item "EV_H"
2177The name of the \fIev.h\fR header file used to include it. The default if
2178undefined is \f(CW\*(C`<ev.h>\*(C'\fR in \fIevent.h\fR and \f(CW"ev.h"\fR in \fIev.c\fR. This
2179can be used to virtually rename the \fIev.h\fR header file in case of conflicts.
2180.IP "\s-1EV_CONFIG_H\s0" 4
2181.IX Item "EV_CONFIG_H"
2182If \f(CW\*(C`EV_STANDALONE\*(C'\fR isn't \f(CW1\fR, this variable can be used to override
2183\&\fIev.c\fR's idea of where to find the \fIconfig.h\fR file, similarly to
2184\&\f(CW\*(C`EV_H\*(C'\fR, above.
2185.IP "\s-1EV_EVENT_H\s0" 4
2186.IX Item "EV_EVENT_H"
2187Similarly to \f(CW\*(C`EV_H\*(C'\fR, this macro can be used to override \fIevent.c\fR's idea
2188of how the \fIevent.h\fR header can be found.
2189.IP "\s-1EV_PROTOTYPES\s0" 4
2190.IX Item "EV_PROTOTYPES"
2191If defined to be \f(CW0\fR, then \fIev.h\fR will not define any function
2192prototypes, but still define all the structs and other symbols. This is
2193occasionally useful if you want to provide your own wrapper functions
2194around libev functions.
2195.IP "\s-1EV_MULTIPLICITY\s0" 4
2196.IX Item "EV_MULTIPLICITY"
2197If undefined or defined to \f(CW1\fR, then all event-loop-specific functions
2198will have the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument, and you can create
2199additional independent event loops. Otherwise there will be no support
2200for multiple event loops and there is no first event loop pointer
2201argument. Instead, all functions act on the single default loop.
2202.IP "\s-1EV_PERIODIC_ENABLE\s0" 4
2203.IX Item "EV_PERIODIC_ENABLE"
2204If undefined or defined to be \f(CW1\fR, then periodic timers are supported. If
2205defined to be \f(CW0\fR, then they are not. Disabling them saves a few kB of
2206code.
2207.IP "\s-1EV_EMBED_ENABLE\s0" 4
2208.IX Item "EV_EMBED_ENABLE"
2209If undefined or defined to be \f(CW1\fR, then embed watchers are supported. If
2210defined to be \f(CW0\fR, then they are not.
2211.IP "\s-1EV_STAT_ENABLE\s0" 4
2212.IX Item "EV_STAT_ENABLE"
2213If undefined or defined to be \f(CW1\fR, then stat watchers are supported. If
2214defined to be \f(CW0\fR, then they are not.
2215.IP "\s-1EV_FORK_ENABLE\s0" 4
2216.IX Item "EV_FORK_ENABLE"
2217If undefined or defined to be \f(CW1\fR, then fork watchers are supported. If
2218defined to be \f(CW0\fR, then they are not.
2219.IP "\s-1EV_MINIMAL\s0" 4
2220.IX Item "EV_MINIMAL"
2221If you need to shave off some kilobytes of code at the expense of some
2222speed, define this symbol to \f(CW1\fR. Currently only used for gcc to override
2223some inlining decisions, saves roughly 30% codesize of amd64.
2224.IP "\s-1EV_PID_HASHSIZE\s0" 4
2225.IX Item "EV_PID_HASHSIZE"
2226\&\f(CW\*(C`ev_child\*(C'\fR watchers use a small hash table to distribute workload by
2227pid. The default size is \f(CW16\fR (or \f(CW1\fR with \f(CW\*(C`EV_MINIMAL\*(C'\fR), usually more
2228than enough. If you need to manage thousands of children you might want to
2229increase this value.
2230.IP "\s-1EV_COMMON\s0" 4
2231.IX Item "EV_COMMON"
2232By default, all watchers have a \f(CW\*(C`void *data\*(C'\fR member. By redefining
2233this macro to a something else you can include more and other types of
2234members. You have to define it each time you include one of the files,
2235though, and it must be identical each time.
2236.Sp
2237For example, the perl \s-1EV\s0 module uses something like this:
2238.Sp
2239.Vb 3
2240\& #define EV_COMMON \e
2241\& SV *self; /* contains this struct */ \e
2242\& SV *cb_sv, *fh /* note no trailing ";" */
2243.Ve
2244.IP "\s-1EV_CB_DECLARE\s0 (type)" 4
2245.IX Item "EV_CB_DECLARE (type)"
2246.PD 0
2247.IP "\s-1EV_CB_INVOKE\s0 (watcher, revents)" 4
2248.IX Item "EV_CB_INVOKE (watcher, revents)"
2249.IP "ev_set_cb (ev, cb)" 4
2250.IX Item "ev_set_cb (ev, cb)"
2251.PD
2252Can be used to change the callback member declaration in each watcher,
2253and the way callbacks are invoked and set. Must expand to a struct member
2254definition and a statement, respectively. See the \fIev.v\fR header file for
2255their default definitions. One possible use for overriding these is to
2256avoid the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument in all cases, or to use
2257method calls instead of plain function calls in \*(C+.
2258.Sh "\s-1EXAMPLES\s0"
2259.IX Subsection "EXAMPLES"
2260For a real-world example of a program the includes libev
2261verbatim, you can have a look at the \s-1EV\s0 perl module
2262(<http://software.schmorp.de/pkg/EV.html>). It has the libev files in
2263the \fIlibev/\fR subdirectory and includes them in the \fI\s-1EV/EVAPI\s0.h\fR (public
2264interface) and \fI\s-1EV\s0.xs\fR (implementation) files. Only the \fI\s-1EV\s0.xs\fR file
2265will be compiled. It is pretty complex because it provides its own header
2266file.
2267.Sp
2268The usage in rxvt-unicode is simpler. It has a \fIev_cpp.h\fR header file
2269that everybody includes and which overrides some autoconf choices:
2270.Sp
2271.Vb 4
2272\& #define EV_USE_POLL 0
2273\& #define EV_MULTIPLICITY 0
2274\& #define EV_PERIODICS 0
2275\& #define EV_CONFIG_H <config.h>
2276.Ve
2277.Sp
2278.Vb 1
2279\& #include "ev++.h"
2280.Ve
2281.Sp
2282And a \fIev_cpp.C\fR implementation file that contains libev proper and is compiled:
2283.Sp
2284.Vb 2
2285\& #include "ev_cpp.h"
2286\& #include "ev.c"
2287.Ve
2288.SH "COMPLEXITIES"
2289.IX Header "COMPLEXITIES"
2290In this section the complexities of (many of) the algorithms used inside
2291libev will be explained. For complexity discussions about backends see the
2292documentation for \f(CW\*(C`ev_default_init\*(C'\fR.
2293.RS 4
2294.IP "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" 4
2295.IX Item "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)"
2296.PD 0
2297.IP "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)" 4
2298.IX Item "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)"
2299.IP "Starting io/check/prepare/idle/signal/child watchers: O(1)" 4
2300.IX Item "Starting io/check/prepare/idle/signal/child watchers: O(1)"
2301.IP "Stopping check/prepare/idle watchers: O(1)" 4
2302.IX Item "Stopping check/prepare/idle watchers: O(1)"
2303.IP "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % 16))" 4
2304.IX Item "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % 16))"
2305.IP "Finding the next timer per loop iteration: O(1)" 4
2306.IX Item "Finding the next timer per loop iteration: O(1)"
2307.IP "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)" 4
2308.IX Item "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)"
2309.IP "Activating one watcher: O(1)" 4
2310.IX Item "Activating one watcher: O(1)"
2311.RE
2312.RS 4
2313.PD
1434.SH "AUTHOR" 2314.SH "AUTHOR"
1435.IX Header "AUTHOR" 2315.IX Header "AUTHOR"
1436Marc Lehmann <libev@schmorp.de>. 2316Marc Lehmann <libev@schmorp.de>.

Diff Legend

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