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

Comparing libev/ev.3 (file contents):
Revision 1.27 by root, Tue Nov 27 20:15:01 2007 UTC vs.
Revision 1.45 by root, Sat Dec 8 22:11:14 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-27" "perl v5.8.8" "User Contributed Perl Documentation" 132.TH "<STANDARD INPUT>" 1 "2007-12-08" "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
138\& #include <ev.h>
139.Ve
140.SH "EXAMPLE PROGRAM"
141.IX Header "EXAMPLE PROGRAM"
142.Vb 1
143\& #include <ev.h>
144.Ve
145.PP
137.Vb 2 146.Vb 2
138\& /* this is the only header you need */
139\& #include <ev.h>
140.Ve
141.PP
142.Vb 3
143\& /* what follows is a fully working example program */
144\& ev_io stdin_watcher; 147\& ev_io stdin_watcher;
145\& ev_timer timeout_watcher; 148\& ev_timer timeout_watcher;
146.Ve 149.Ve
147.PP 150.PP
148.Vb 8 151.Vb 8
… …
193\& return 0; 196\& return 0;
194\& } 197\& }
195.Ve 198.Ve
196.SH "DESCRIPTION" 199.SH "DESCRIPTION"
197.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
198Libev 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
199file descriptor being readable or a timeout occuring), and it will manage 206file descriptor being readable or a timeout occuring), and it will manage
200these event sources and provide your program with events. 207these event sources and provide your program with events.
201.PP 208.PP
202To 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
… …
207watchers\fR, which are relatively small C structures you initialise with the 214watchers\fR, which are relatively small C structures you initialise with the
208details 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
209watcher. 216watcher.
210.SH "FEATURES" 217.SH "FEATURES"
211.IX Header "FEATURES" 218.IX Header "FEATURES"
212Libev 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
213kqueue mechanisms for file descriptor events, relative timers, absolute 220BSD-specific \f(CW\*(C`kqueue\*(C'\fR and the Solaris-specific event port mechanisms
214timers 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
215events (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
216loop mechanism itself (idle, prepare and check watchers). It also is quite 223with customised rescheduling (\f(CW\*(C`ev_periodic\*(C'\fR), synchronous signals
217fast (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
218it 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).
219.SH "CONVENTIONS" 233.SH "CONVENTIONS"
220.IX Header "CONVENTIONS" 234.IX Header "CONVENTIONS"
221Libev is very configurable. In this manual the default configuration 235Libev is very configurable. In this manual the default configuration will
222will be described, which supports multiple event loops. For more info 236be described, which supports multiple event loops. For more info about
223about 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
224\&\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
225support 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
226argument 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.
227will not have this argument.
228.SH "TIME REPRESENTATION" 241.SH "TIME REPRESENTATION"
229.IX Header "TIME REPRESENTATION" 242.IX Header "TIME REPRESENTATION"
230Libev represents time as a single floating point number, representing the 243Libev represents time as a single floating point number, representing the
231(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
232the 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
… …
257Usually, it's a good idea to terminate if the major versions mismatch, 270Usually, it's a good idea to terminate if the major versions mismatch,
258as this indicates an incompatible change. Minor versions are usually 271as this indicates an incompatible change. Minor versions are usually
259compatible to older versions, so a larger minor version alone is usually 272compatible to older versions, so a larger minor version alone is usually
260not a problem. 273not a problem.
261.Sp 274.Sp
262Example: make sure we haven't accidentally been linked against the wrong 275Example: Make sure we haven't accidentally been linked against the wrong
263version: 276version.
264.Sp 277.Sp
265.Vb 3 278.Vb 3
266\& assert (("libev version mismatch", 279\& assert (("libev version mismatch",
267\& ev_version_major () == EV_VERSION_MAJOR 280\& ev_version_major () == EV_VERSION_MAJOR
268\& && ev_version_minor () >= EV_VERSION_MINOR)); 281\& && ev_version_minor () >= EV_VERSION_MINOR));
… …
296might be supported on the current system, you would need to look at 309might be supported on the current system, you would need to look at
297\&\f(CW\*(C`ev_embeddable_backends () & ev_supported_backends ()\*(C'\fR, likewise for 310\&\f(CW\*(C`ev_embeddable_backends () & ev_supported_backends ()\*(C'\fR, likewise for
298recommended ones. 311recommended ones.
299.Sp 312.Sp
300See the description of \f(CW\*(C`ev_embed\*(C'\fR watchers for more info. 313See the description of \f(CW\*(C`ev_embed\*(C'\fR watchers for more info.
301.IP "ev_set_allocator (void *(*cb)(void *ptr, size_t size))" 4 314.IP "ev_set_allocator (void *(*cb)(void *ptr, long size))" 4
302.IX Item "ev_set_allocator (void *(*cb)(void *ptr, size_t size))" 315.IX Item "ev_set_allocator (void *(*cb)(void *ptr, long size))"
303Sets the allocation function to use (the prototype and semantics are 316Sets the allocation function to use (the prototype is similar \- the
304identical to the realloc C function). It is used to allocate and free 317semantics is identical \- to the realloc C function). It is used to
305memory (no surprises here). If it returns zero when memory needs to be 318allocate and free memory (no surprises here). If it returns zero when
306allocated, the library might abort or take some potentially destructive 319memory needs to be allocated, the library might abort or take some
307action. The default is your system realloc function. 320potentially destructive action. The default is your system realloc
321function.
308.Sp 322.Sp
309You could override this function in high-availability programs to, say, 323You could override this function in high-availability programs to, say,
310free some memory if it cannot allocate memory, to use a special allocator, 324free some memory if it cannot allocate memory, to use a special allocator,
311or even to sleep a while and retry until some memory is available. 325or even to sleep a while and retry until some memory is available.
312.Sp 326.Sp
313Example: replace the libev allocator with one that waits a bit and then 327Example: Replace the libev allocator with one that waits a bit and then
314retries: better than mine). 328retries).
315.Sp 329.Sp
316.Vb 6 330.Vb 6
317\& static void * 331\& static void *
318\& persistent_realloc (void *ptr, size_t size) 332\& persistent_realloc (void *ptr, size_t size)
319\& { 333\& {
… …
345callback is set, then libev will expect it to remedy the sitution, no 359callback is set, then libev will expect it to remedy the sitution, no
346matter what, when it returns. That is, libev will generally retry the 360matter what, when it returns. That is, libev will generally retry the
347requested operation, or, if the condition doesn't go away, do bad stuff 361requested operation, or, if the condition doesn't go away, do bad stuff
348(such as abort). 362(such as abort).
349.Sp 363.Sp
350Example: do the same thing as libev does internally: 364Example: This is basically the same thing that libev does internally, too.
351.Sp 365.Sp
352.Vb 6 366.Vb 6
353\& static void 367\& static void
354\& fatal_error (const char *msg) 368\& fatal_error (const char *msg)
355\& { 369\& {
… …
401or setgid) then libev will \fInot\fR look at the environment variable 415or setgid) then libev will \fInot\fR look at the environment variable
402\&\f(CW\*(C`LIBEV_FLAGS\*(C'\fR. Otherwise (the default), this environment variable will 416\&\f(CW\*(C`LIBEV_FLAGS\*(C'\fR. Otherwise (the default), this environment variable will
403override the flags completely if it is found in the environment. This is 417override the flags completely if it is found in the environment. This is
404useful to try out specific backends to test their performance, or to work 418useful to try out specific backends to test their performance, or to work
405around bugs. 419around bugs.
420.ie n .IP """EVFLAG_FORKCHECK""" 4
421.el .IP "\f(CWEVFLAG_FORKCHECK\fR" 4
422.IX Item "EVFLAG_FORKCHECK"
423Instead of calling \f(CW\*(C`ev_default_fork\*(C'\fR or \f(CW\*(C`ev_loop_fork\*(C'\fR manually after
424a fork, you can also make libev check for a fork in each iteration by
425enabling this flag.
426.Sp
427This works by calling \f(CW\*(C`getpid ()\*(C'\fR on every iteration of the loop,
428and thus this might slow down your event loop if you do a lot of loop
429iterations and little real work, but is usually not noticeable (on my
430Linux system for example, \f(CW\*(C`getpid\*(C'\fR is actually a simple 5\-insn sequence
431without a syscall and thus \fIvery\fR fast, but my Linux system also has
432\&\f(CW\*(C`pthread_atfork\*(C'\fR which is even faster).
433.Sp
434The big advantage of this flag is that you can forget about fork (and
435forget about forgetting to tell libev about forking) when you use this
436flag.
437.Sp
438This flag setting cannot be overriden or specified in the \f(CW\*(C`LIBEV_FLAGS\*(C'\fR
439environment variable.
406.ie n .IP """EVBACKEND_SELECT"" (value 1, portable select backend)" 4 440.ie n .IP """EVBACKEND_SELECT"" (value 1, portable select backend)" 4
407.el .IP "\f(CWEVBACKEND_SELECT\fR (value 1, portable select backend)" 4 441.el .IP "\f(CWEVBACKEND_SELECT\fR (value 1, portable select backend)" 4
408.IX Item "EVBACKEND_SELECT (value 1, portable select backend)" 442.IX Item "EVBACKEND_SELECT (value 1, portable select backend)"
409This is your standard \fIselect\fR\|(2) backend. Not \fIcompletely\fR standard, as 443This is your standard \fIselect\fR\|(2) backend. Not \fIcompletely\fR standard, as
410libev tries to roll its own fd_set with no limits on the number of fds, 444libev tries to roll its own fd_set with no limits on the number of fds,
… …
504Similar to \f(CW\*(C`ev_default_loop\*(C'\fR, but always creates a new event loop that is 538Similar to \f(CW\*(C`ev_default_loop\*(C'\fR, but always creates a new event loop that is
505always distinct from the default loop. Unlike the default loop, it cannot 539always distinct from the default loop. Unlike the default loop, it cannot
506handle signal and child watchers, and attempts to do so will be greeted by 540handle signal and child watchers, and attempts to do so will be greeted by
507undefined behaviour (or a failed assertion if assertions are enabled). 541undefined behaviour (or a failed assertion if assertions are enabled).
508.Sp 542.Sp
509Example: try to create a event loop that uses epoll and nothing else. 543Example: Try to create a event loop that uses epoll and nothing else.
510.Sp 544.Sp
511.Vb 3 545.Vb 3
512\& struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV); 546\& struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV);
513\& if (!epoller) 547\& if (!epoller)
514\& fatal ("no epoll found here, maybe it hides under your chair"); 548\& fatal ("no epoll found here, maybe it hides under your chair");
… …
551.IP "ev_loop_fork (loop)" 4 585.IP "ev_loop_fork (loop)" 4
552.IX Item "ev_loop_fork (loop)" 586.IX Item "ev_loop_fork (loop)"
553Like \f(CW\*(C`ev_default_fork\*(C'\fR, but acts on an event loop created by 587Like \f(CW\*(C`ev_default_fork\*(C'\fR, but acts on an event loop created by
554\&\f(CW\*(C`ev_loop_new\*(C'\fR. Yes, you have to call this on every allocated event loop 588\&\f(CW\*(C`ev_loop_new\*(C'\fR. Yes, you have to call this on every allocated event loop
555after fork, and how you do this is entirely your own problem. 589after fork, and how you do this is entirely your own problem.
590.IP "unsigned int ev_loop_count (loop)" 4
591.IX Item "unsigned int ev_loop_count (loop)"
592Returns the count of loop iterations for the loop, which is identical to
593the number of times libev did poll for new events. It starts at \f(CW0\fR and
594happily wraps around with enough iterations.
595.Sp
596This value can sometimes be useful as a generation counter of sorts (it
597\&\*(L"ticks\*(R" the number of loop iterations), as it roughly corresponds with
598\&\f(CW\*(C`ev_prepare\*(C'\fR and \f(CW\*(C`ev_check\*(C'\fR calls.
556.IP "unsigned int ev_backend (loop)" 4 599.IP "unsigned int ev_backend (loop)" 4
557.IX Item "unsigned int ev_backend (loop)" 600.IX Item "unsigned int ev_backend (loop)"
558Returns one of the \f(CW\*(C`EVBACKEND_*\*(C'\fR flags indicating the event backend in 601Returns one of the \f(CW\*(C`EVBACKEND_*\*(C'\fR flags indicating the event backend in
559use. 602use.
560.IP "ev_tstamp ev_now (loop)" 4 603.IP "ev_tstamp ev_now (loop)" 4
… …
591libev watchers. However, a pair of \f(CW\*(C`ev_prepare\*(C'\fR/\f(CW\*(C`ev_check\*(C'\fR watchers is 634libev watchers. However, a pair of \f(CW\*(C`ev_prepare\*(C'\fR/\f(CW\*(C`ev_check\*(C'\fR watchers is
592usually a better approach for this kind of thing. 635usually a better approach for this kind of thing.
593.Sp 636.Sp
594Here are the gory details of what \f(CW\*(C`ev_loop\*(C'\fR does: 637Here are the gory details of what \f(CW\*(C`ev_loop\*(C'\fR does:
595.Sp 638.Sp
596.Vb 18 639.Vb 19
640\& - Before the first iteration, call any pending watchers.
597\& * If there are no active watchers (reference count is zero), return. 641\& * If there are no active watchers (reference count is zero), return.
598\& - Queue prepare watchers and then call all outstanding watchers. 642\& - Queue all prepare watchers and then call all outstanding watchers.
599\& - If we have been forked, recreate the kernel state. 643\& - If we have been forked, recreate the kernel state.
600\& - Update the kernel state with all outstanding changes. 644\& - Update the kernel state with all outstanding changes.
601\& - Update the "event loop time". 645\& - Update the "event loop time".
602\& - Calculate for how long to block. 646\& - Calculate for how long to block.
603\& - Block the process, waiting for any events. 647\& - Block the process, waiting for any events.
… …
612\& be handled here by queueing them when their watcher gets executed. 656\& be handled here by queueing them when their watcher gets executed.
613\& - If ev_unloop has been called or EVLOOP_ONESHOT or EVLOOP_NONBLOCK 657\& - If ev_unloop has been called or EVLOOP_ONESHOT or EVLOOP_NONBLOCK
614\& were used, return, otherwise continue with step *. 658\& were used, return, otherwise continue with step *.
615.Ve 659.Ve
616.Sp 660.Sp
617Example: queue some jobs and then loop until no events are outsanding 661Example: Queue some jobs and then loop until no events are outsanding
618anymore. 662anymore.
619.Sp 663.Sp
620.Vb 4 664.Vb 4
621\& ... queue jobs here, make sure they register event watchers as long 665\& ... queue jobs here, make sure they register event watchers as long
622\& ... as they still have work to do (even an idle watcher will do..) 666\& ... as they still have work to do (even an idle watcher will do..)
… …
644visible to the libev user and should not keep \f(CW\*(C`ev_loop\*(C'\fR from exiting if 688visible to the libev user and should not keep \f(CW\*(C`ev_loop\*(C'\fR from exiting if
645no event watchers registered by it are active. It is also an excellent 689no event watchers registered by it are active. It is also an excellent
646way to do this for generic recurring timers or from within third-party 690way to do this for generic recurring timers or from within third-party
647libraries. Just remember to \fIunref after start\fR and \fIref before stop\fR. 691libraries. Just remember to \fIunref after start\fR and \fIref before stop\fR.
648.Sp 692.Sp
649Example: create a signal watcher, but keep it from keeping \f(CW\*(C`ev_loop\*(C'\fR 693Example: Create a signal watcher, but keep it from keeping \f(CW\*(C`ev_loop\*(C'\fR
650running when nothing else is active. 694running when nothing else is active.
651.Sp 695.Sp
652.Vb 4 696.Vb 4
653\& struct dv_signal exitsig; 697\& struct ev_signal exitsig;
654\& ev_signal_init (&exitsig, sig_cb, SIGINT); 698\& ev_signal_init (&exitsig, sig_cb, SIGINT);
655\& ev_signal_start (myloop, &exitsig); 699\& ev_signal_start (loop, &exitsig);
656\& evf_unref (myloop); 700\& evf_unref (loop);
657.Ve 701.Ve
658.Sp 702.Sp
659Example: for some weird reason, unregister the above signal handler again. 703Example: For some weird reason, unregister the above signal handler again.
660.Sp 704.Sp
661.Vb 2 705.Vb 2
662\& ev_ref (myloop); 706\& ev_ref (loop);
663\& ev_signal_stop (myloop, &exitsig); 707\& ev_signal_stop (loop, &exitsig);
664.Ve 708.Ve
665.SH "ANATOMY OF A WATCHER" 709.SH "ANATOMY OF A WATCHER"
666.IX Header "ANATOMY OF A WATCHER" 710.IX Header "ANATOMY OF A WATCHER"
667A watcher is a structure that you create and register to record your 711A watcher is a structure that you create and register to record your
668interest in some event. For instance, if you want to wait for \s-1STDIN\s0 to 712interest in some event. For instance, if you want to wait for \s-1STDIN\s0 to
… …
846.IP "bool ev_is_pending (ev_TYPE *watcher)" 4 890.IP "bool ev_is_pending (ev_TYPE *watcher)" 4
847.IX Item "bool ev_is_pending (ev_TYPE *watcher)" 891.IX Item "bool ev_is_pending (ev_TYPE *watcher)"
848Returns a true value iff the watcher is pending, (i.e. it has outstanding 892Returns a true value iff the watcher is pending, (i.e. it has outstanding
849events but its callback has not yet been invoked). As long as a watcher 893events but its callback has not yet been invoked). As long as a watcher
850is pending (but not active) you must not call an init function on it (but 894is pending (but not active) you must not call an init function on it (but
851\&\f(CW\*(C`ev_TYPE_set\*(C'\fR is safe) and you must make sure the watcher is available to 895\&\f(CW\*(C`ev_TYPE_set\*(C'\fR is safe), you must not change its priority, and you must
852libev (e.g. you cnanot \f(CW\*(C`free ()\*(C'\fR it). 896make sure the watcher is available to libev (e.g. you cannot \f(CW\*(C`free ()\*(C'\fR
897it).
853.IP "callback = ev_cb (ev_TYPE *watcher)" 4 898.IP "callback ev_cb (ev_TYPE *watcher)" 4
854.IX Item "callback = ev_cb (ev_TYPE *watcher)" 899.IX Item "callback ev_cb (ev_TYPE *watcher)"
855Returns the callback currently set on the watcher. 900Returns the callback currently set on the watcher.
856.IP "ev_cb_set (ev_TYPE *watcher, callback)" 4 901.IP "ev_cb_set (ev_TYPE *watcher, callback)" 4
857.IX Item "ev_cb_set (ev_TYPE *watcher, callback)" 902.IX Item "ev_cb_set (ev_TYPE *watcher, callback)"
858Change the callback. You can change the callback at virtually any time 903Change the callback. You can change the callback at virtually any time
859(modulo threads). 904(modulo threads).
905.IP "ev_set_priority (ev_TYPE *watcher, priority)" 4
906.IX Item "ev_set_priority (ev_TYPE *watcher, priority)"
907.PD 0
908.IP "int ev_priority (ev_TYPE *watcher)" 4
909.IX Item "int ev_priority (ev_TYPE *watcher)"
910.PD
911Set and query the priority of the watcher. The priority is a small
912integer between \f(CW\*(C`EV_MAXPRI\*(C'\fR (default: \f(CW2\fR) and \f(CW\*(C`EV_MINPRI\*(C'\fR
913(default: \f(CW\*(C`\-2\*(C'\fR). Pending watchers with higher priority will be invoked
914before watchers with lower priority, but priority will not keep watchers
915from being executed (except for \f(CW\*(C`ev_idle\*(C'\fR watchers).
916.Sp
917This means that priorities are \fIonly\fR used for ordering callback
918invocation after new events have been received. This is useful, for
919example, to reduce latency after idling, or more often, to bind two
920watchers on the same event and make sure one is called first.
921.Sp
922If you need to suppress invocation when higher priority events are pending
923you need to look at \f(CW\*(C`ev_idle\*(C'\fR watchers, which provide this functionality.
924.Sp
925You \fImust not\fR change the priority of a watcher as long as it is active or
926pending.
927.Sp
928The default priority used by watchers when no priority has been set is
929always \f(CW0\fR, which is supposed to not be too high and not be too low :).
930.Sp
931Setting a priority outside the range of \f(CW\*(C`EV_MINPRI\*(C'\fR to \f(CW\*(C`EV_MAXPRI\*(C'\fR is
932fine, as long as you do not mind that the priority value you query might
933or might not have been adjusted to be within valid range.
934.IP "ev_invoke (loop, ev_TYPE *watcher, int revents)" 4
935.IX Item "ev_invoke (loop, ev_TYPE *watcher, int revents)"
936Invoke the \f(CW\*(C`watcher\*(C'\fR with the given \f(CW\*(C`loop\*(C'\fR and \f(CW\*(C`revents\*(C'\fR. Neither
937\&\f(CW\*(C`loop\*(C'\fR nor \f(CW\*(C`revents\*(C'\fR need to be valid as long as the watcher callback
938can deal with that fact.
939.IP "int ev_clear_pending (loop, ev_TYPE *watcher)" 4
940.IX Item "int ev_clear_pending (loop, ev_TYPE *watcher)"
941If the watcher is pending, this function returns clears its pending status
942and returns its \f(CW\*(C`revents\*(C'\fR bitset (as if its callback was invoked). If the
943watcher isn't pending it does nothing and returns \f(CW0\fR.
860.Sh "\s-1ASSOCIATING\s0 \s-1CUSTOM\s0 \s-1DATA\s0 \s-1WITH\s0 A \s-1WATCHER\s0" 944.Sh "\s-1ASSOCIATING\s0 \s-1CUSTOM\s0 \s-1DATA\s0 \s-1WITH\s0 A \s-1WATCHER\s0"
861.IX Subsection "ASSOCIATING CUSTOM DATA WITH A WATCHER" 945.IX Subsection "ASSOCIATING CUSTOM DATA WITH A WATCHER"
862Each watcher has, by default, a member \f(CW\*(C`void *data\*(C'\fR that you can change 946Each watcher has, by default, a member \f(CW\*(C`void *data\*(C'\fR that you can change
863and read at any time, libev will completely ignore it. This can be used 947and read at any time, libev will completely ignore it. This can be used
864to associate arbitrary data with your watcher. If you need more data and 948to associate arbitrary data with your watcher. If you need more data and
… …
885\& struct my_io *w = (struct my_io *)w_; 969\& struct my_io *w = (struct my_io *)w_;
886\& ... 970\& ...
887\& } 971\& }
888.Ve 972.Ve
889.PP 973.PP
890More interesting and less C\-conformant ways of catsing your callback type 974More interesting and less C\-conformant ways of casting your callback type
891have been omitted.... 975instead have been omitted.
976.PP
977Another common scenario is having some data structure with multiple
978watchers:
979.PP
980.Vb 6
981\& struct my_biggy
982\& {
983\& int some_data;
984\& ev_timer t1;
985\& ev_timer t2;
986\& }
987.Ve
988.PP
989In this case getting the pointer to \f(CW\*(C`my_biggy\*(C'\fR is a bit more complicated,
990you need to use \f(CW\*(C`offsetof\*(C'\fR:
991.PP
992.Vb 1
993\& #include <stddef.h>
994.Ve
995.PP
996.Vb 6
997\& static void
998\& t1_cb (EV_P_ struct ev_timer *w, int revents)
999\& {
1000\& struct my_biggy big = (struct my_biggy *
1001\& (((char *)w) - offsetof (struct my_biggy, t1));
1002\& }
1003.Ve
1004.PP
1005.Vb 6
1006\& static void
1007\& t2_cb (EV_P_ struct ev_timer *w, int revents)
1008\& {
1009\& struct my_biggy big = (struct my_biggy *
1010\& (((char *)w) - offsetof (struct my_biggy, t2));
1011\& }
1012.Ve
892.SH "WATCHER TYPES" 1013.SH "WATCHER TYPES"
893.IX Header "WATCHER TYPES" 1014.IX Header "WATCHER TYPES"
894This section describes each watcher in detail, but will not repeat 1015This section describes each watcher in detail, but will not repeat
895information given in the last section. Any initialisation/set macros, 1016information given in the last section. Any initialisation/set macros,
896functions and members specific to the watcher type are explained. 1017functions and members specific to the watcher type are explained.
… …
938it is best to always use non-blocking I/O: An extra \f(CW\*(C`read\*(C'\fR(2) returning 1059it is best to always use non-blocking I/O: An extra \f(CW\*(C`read\*(C'\fR(2) returning
939\&\f(CW\*(C`EAGAIN\*(C'\fR is far preferable to a program hanging until some data arrives. 1060\&\f(CW\*(C`EAGAIN\*(C'\fR is far preferable to a program hanging until some data arrives.
940.PP 1061.PP
941If you cannot run the fd in non-blocking mode (for example you should not 1062If you cannot run the fd in non-blocking mode (for example you should not
942play around with an Xlib connection), then you have to seperately re-test 1063play around with an Xlib connection), then you have to seperately re-test
943wether a file descriptor is really ready with a known-to-be good interface 1064whether a file descriptor is really ready with a known-to-be good interface
944such as poll (fortunately in our Xlib example, Xlib already does this on 1065such as poll (fortunately in our Xlib example, Xlib already does this on
945its own, so its quite safe to use). 1066its own, so its quite safe to use).
946.IP "ev_io_init (ev_io *, callback, int fd, int events)" 4 1067.IP "ev_io_init (ev_io *, callback, int fd, int events)" 4
947.IX Item "ev_io_init (ev_io *, callback, int fd, int events)" 1068.IX Item "ev_io_init (ev_io *, callback, int fd, int events)"
948.PD 0 1069.PD 0
… …
957The file descriptor being watched. 1078The file descriptor being watched.
958.IP "int events [read\-only]" 4 1079.IP "int events [read\-only]" 4
959.IX Item "int events [read-only]" 1080.IX Item "int events [read-only]"
960The events being watched. 1081The events being watched.
961.PP 1082.PP
962Example: call \f(CW\*(C`stdin_readable_cb\*(C'\fR when \s-1STDIN_FILENO\s0 has become, well 1083Example: Call \f(CW\*(C`stdin_readable_cb\*(C'\fR when \s-1STDIN_FILENO\s0 has become, well
963readable, but only once. Since it is likely line\-buffered, you could 1084readable, but only once. Since it is likely line\-buffered, you could
964attempt to read a whole line in the callback: 1085attempt to read a whole line in the callback.
965.PP 1086.PP
966.Vb 6 1087.Vb 6
967\& static void 1088\& static void
968\& stdin_readable_cb (struct ev_loop *loop, struct ev_io *w, int revents) 1089\& stdin_readable_cb (struct ev_loop *loop, struct ev_io *w, int revents)
969\& { 1090\& {
… …
1024.IP "ev_timer_again (loop)" 4 1145.IP "ev_timer_again (loop)" 4
1025.IX Item "ev_timer_again (loop)" 1146.IX Item "ev_timer_again (loop)"
1026This will act as if the timer timed out and restart it again if it is 1147This will act as if the timer timed out and restart it again if it is
1027repeating. The exact semantics are: 1148repeating. The exact semantics are:
1028.Sp 1149.Sp
1150If the timer is pending, its pending status is cleared.
1151.Sp
1029If the timer is started but nonrepeating, stop it. 1152If the timer is started but nonrepeating, stop it (as if it timed out).
1030.Sp 1153.Sp
1031If the timer is repeating, either start it if necessary (with the repeat 1154If the timer is repeating, either start it if necessary (with the
1032value), or reset the running timer to the repeat value. 1155\&\f(CW\*(C`repeat\*(C'\fR value), or reset the running timer to the \f(CW\*(C`repeat\*(C'\fR value.
1033.Sp 1156.Sp
1034This sounds a bit complicated, but here is a useful and typical 1157This sounds a bit complicated, but here is a useful and typical
1035example: Imagine you have a tcp connection and you want a so-called 1158example: Imagine you have a tcp connection and you want a so-called idle
1036idle timeout, that is, you want to be called when there have been, 1159timeout, that is, you want to be called when there have been, say, 60
1037say, 60 seconds of inactivity on the socket. The easiest way to do 1160seconds of inactivity on the socket. The easiest way to do this is to
1038this 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 1161configure an \f(CW\*(C`ev_timer\*(C'\fR with a \f(CW\*(C`repeat\*(C'\fR value of \f(CW60\fR and then call
1039\&\f(CW\*(C`ev_timer_again\*(C'\fR each time you successfully read or write some data. If 1162\&\f(CW\*(C`ev_timer_again\*(C'\fR each time you successfully read or write some data. If
1040you go into an idle state where you do not expect data to travel on the 1163you go into an idle state where you do not expect data to travel on the
1041socket, you can stop the timer, and again will automatically restart it if 1164socket, you can \f(CW\*(C`ev_timer_stop\*(C'\fR the timer, and \f(CW\*(C`ev_timer_again\*(C'\fR will
1042need be. 1165automatically restart it if need be.
1043.Sp 1166.Sp
1044You can also ignore the \f(CW\*(C`after\*(C'\fR value and \f(CW\*(C`ev_timer_start\*(C'\fR altogether 1167That means you can ignore the \f(CW\*(C`after\*(C'\fR value and \f(CW\*(C`ev_timer_start\*(C'\fR
1045and only ever use the \f(CW\*(C`repeat\*(C'\fR value: 1168altogether and only ever use the \f(CW\*(C`repeat\*(C'\fR value and \f(CW\*(C`ev_timer_again\*(C'\fR:
1046.Sp 1169.Sp
1047.Vb 8 1170.Vb 8
1048\& ev_timer_init (timer, callback, 0., 5.); 1171\& ev_timer_init (timer, callback, 0., 5.);
1049\& ev_timer_again (loop, timer); 1172\& ev_timer_again (loop, timer);
1050\& ... 1173\& ...
… …
1053\& ... 1176\& ...
1054\& timer->again = 10.; 1177\& timer->again = 10.;
1055\& ev_timer_again (loop, timer); 1178\& ev_timer_again (loop, timer);
1056.Ve 1179.Ve
1057.Sp 1180.Sp
1058This is more efficient then stopping/starting the timer eahc time you want 1181This is more slightly efficient then stopping/starting the timer each time
1059to modify its timeout value. 1182you want to modify its timeout value.
1060.IP "ev_tstamp repeat [read\-write]" 4 1183.IP "ev_tstamp repeat [read\-write]" 4
1061.IX Item "ev_tstamp repeat [read-write]" 1184.IX Item "ev_tstamp repeat [read-write]"
1062The current \f(CW\*(C`repeat\*(C'\fR value. Will be used each time the watcher times out 1185The current \f(CW\*(C`repeat\*(C'\fR value. Will be used each time the watcher times out
1063or \f(CW\*(C`ev_timer_again\*(C'\fR is called and determines the next timeout (if any), 1186or \f(CW\*(C`ev_timer_again\*(C'\fR is called and determines the next timeout (if any),
1064which is also when any modifications are taken into account. 1187which is also when any modifications are taken into account.
1065.PP 1188.PP
1066Example: create a timer that fires after 60 seconds. 1189Example: Create a timer that fires after 60 seconds.
1067.PP 1190.PP
1068.Vb 5 1191.Vb 5
1069\& static void 1192\& static void
1070\& one_minute_cb (struct ev_loop *loop, struct ev_timer *w, int revents) 1193\& one_minute_cb (struct ev_loop *loop, struct ev_timer *w, int revents)
1071\& { 1194\& {
… …
1077\& struct ev_timer mytimer; 1200\& struct ev_timer mytimer;
1078\& ev_timer_init (&mytimer, one_minute_cb, 60., 0.); 1201\& ev_timer_init (&mytimer, one_minute_cb, 60., 0.);
1079\& ev_timer_start (loop, &mytimer); 1202\& ev_timer_start (loop, &mytimer);
1080.Ve 1203.Ve
1081.PP 1204.PP
1082Example: create a timeout timer that times out after 10 seconds of 1205Example: Create a timeout timer that times out after 10 seconds of
1083inactivity. 1206inactivity.
1084.PP 1207.PP
1085.Vb 5 1208.Vb 5
1086\& static void 1209\& static void
1087\& timeout_cb (struct ev_loop *loop, struct ev_timer *w, int revents) 1210\& timeout_cb (struct ev_loop *loop, struct ev_timer *w, int revents)
… …
1212.IX Item "ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read-write]" 1335.IX Item "ev_tstamp (*reschedule_cb)(struct ev_periodic *w, ev_tstamp now) [read-write]"
1213The current reschedule callback, or \f(CW0\fR, if this functionality is 1336The current reschedule callback, or \f(CW0\fR, if this functionality is
1214switched off. Can be changed any time, but changes only take effect when 1337switched off. Can be changed any time, but changes only take effect when
1215the periodic timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being called. 1338the periodic timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being called.
1216.PP 1339.PP
1217Example: call a callback every hour, or, more precisely, whenever the 1340Example: Call a callback every hour, or, more precisely, whenever the
1218system clock is divisible by 3600. The callback invocation times have 1341system clock is divisible by 3600. The callback invocation times have
1219potentially a lot of jittering, but good long-term stability. 1342potentially a lot of jittering, but good long-term stability.
1220.PP 1343.PP
1221.Vb 5 1344.Vb 5
1222\& static void 1345\& static void
… …
1230\& struct ev_periodic hourly_tick; 1353\& struct ev_periodic hourly_tick;
1231\& ev_periodic_init (&hourly_tick, clock_cb, 0., 3600., 0); 1354\& ev_periodic_init (&hourly_tick, clock_cb, 0., 3600., 0);
1232\& ev_periodic_start (loop, &hourly_tick); 1355\& ev_periodic_start (loop, &hourly_tick);
1233.Ve 1356.Ve
1234.PP 1357.PP
1235Example: the same as above, but use a reschedule callback to do it: 1358Example: The same as above, but use a reschedule callback to do it:
1236.PP 1359.PP
1237.Vb 1 1360.Vb 1
1238\& #include <math.h> 1361\& #include <math.h>
1239.Ve 1362.Ve
1240.PP 1363.PP
… …
1248.PP 1371.PP
1249.Vb 1 1372.Vb 1
1250\& ev_periodic_init (&hourly_tick, clock_cb, 0., 0., my_scheduler_cb); 1373\& ev_periodic_init (&hourly_tick, clock_cb, 0., 0., my_scheduler_cb);
1251.Ve 1374.Ve
1252.PP 1375.PP
1253Example: call a callback every hour, starting now: 1376Example: Call a callback every hour, starting now:
1254.PP 1377.PP
1255.Vb 4 1378.Vb 4
1256\& struct ev_periodic hourly_tick; 1379\& struct ev_periodic hourly_tick;
1257\& ev_periodic_init (&hourly_tick, clock_cb, 1380\& ev_periodic_init (&hourly_tick, clock_cb,
1258\& fmod (ev_now (loop), 3600.), 3600., 0); 1381\& fmod (ev_now (loop), 3600.), 3600., 0);
… …
1309.IP "int rstatus [read\-write]" 4 1432.IP "int rstatus [read\-write]" 4
1310.IX Item "int rstatus [read-write]" 1433.IX Item "int rstatus [read-write]"
1311The process exit/trace status caused by \f(CW\*(C`rpid\*(C'\fR (see your systems 1434The process exit/trace status caused by \f(CW\*(C`rpid\*(C'\fR (see your systems
1312\&\f(CW\*(C`waitpid\*(C'\fR and \f(CW\*(C`sys/wait.h\*(C'\fR documentation for details). 1435\&\f(CW\*(C`waitpid\*(C'\fR and \f(CW\*(C`sys/wait.h\*(C'\fR documentation for details).
1313.PP 1436.PP
1314Example: try to exit cleanly on \s-1SIGINT\s0 and \s-1SIGTERM\s0. 1437Example: Try to exit cleanly on \s-1SIGINT\s0 and \s-1SIGTERM\s0.
1315.PP 1438.PP
1316.Vb 5 1439.Vb 5
1317\& static void 1440\& static void
1318\& sigint_cb (struct ev_loop *loop, struct ev_signal *w, int revents) 1441\& sigint_cb (struct ev_loop *loop, struct ev_signal *w, int revents)
1319\& { 1442\& {
… …
1337not exist\*(R" is a status change like any other. The condition \*(L"path does 1460not exist\*(R" is a status change like any other. The condition \*(L"path does
1338not exist\*(R" is signified by the \f(CW\*(C`st_nlink\*(C'\fR field being zero (which is 1461not exist\*(R" is signified by the \f(CW\*(C`st_nlink\*(C'\fR field being zero (which is
1339otherwise always forced to be at least one) and all the other fields of 1462otherwise always forced to be at least one) and all the other fields of
1340the stat buffer having unspecified contents. 1463the stat buffer having unspecified contents.
1341.PP 1464.PP
1465The path \fIshould\fR be absolute and \fImust not\fR end in a slash. If it is
1466relative and your working directory changes, the behaviour is undefined.
1467.PP
1342Since there is no standard to do this, the portable implementation simply 1468Since there is no standard to do this, the portable implementation simply
1343calls \f(CW\*(C`stat (2)\*(C'\fR regulalry on the path to see if it changed somehow. You 1469calls \f(CW\*(C`stat (2)\*(C'\fR regularly on the path to see if it changed somehow. You
1344can specify a recommended polling interval for this case. If you specify 1470can specify a recommended polling interval for this case. If you specify
1345a polling interval of \f(CW0\fR (highly recommended!) then a \fIsuitable, 1471a polling interval of \f(CW0\fR (highly recommended!) then a \fIsuitable,
1346unspecified default\fR value will be used (which you can expect to be around 1472unspecified default\fR value will be used (which you can expect to be around
1347five seconds, although this might change dynamically). Libev will also 1473five seconds, although this might change dynamically). Libev will also
1348impose a minimum interval which is currently around \f(CW0.1\fR, but thats 1474impose a minimum interval which is currently around \f(CW0.1\fR, but thats
… …
1350.PP 1476.PP
1351This watcher type is not meant for massive numbers of stat watchers, 1477This watcher type is not meant for massive numbers of stat watchers,
1352as even with OS-supported change notifications, this can be 1478as even with OS-supported change notifications, this can be
1353resource\-intensive. 1479resource\-intensive.
1354.PP 1480.PP
1355At the time of this writing, no specific \s-1OS\s0 backends are implemented, but 1481At the time of this writing, only the Linux inotify interface is
1356if demand increases, at least a kqueue and inotify backend will be added. 1482implemented (implementing kqueue support is left as an exercise for the
1483reader). Inotify will be used to give hints only and should not change the
1484semantics of \f(CW\*(C`ev_stat\*(C'\fR watchers, which means that libev sometimes needs
1485to fall back to regular polling again even with inotify, but changes are
1486usually detected immediately, and if the file exists there will be no
1487polling.
1357.IP "ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)" 4 1488.IP "ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)" 4
1358.IX Item "ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)" 1489.IX Item "ev_stat_init (ev_stat *, callback, const char *path, ev_tstamp interval)"
1359.PD 0 1490.PD 0
1360.IP "ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)" 4 1491.IP "ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)" 4
1361.IX Item "ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)" 1492.IX Item "ev_stat_set (ev_stat *, const char *path, ev_tstamp interval)"
… …
1422\& ev_stat_start (loop, &passwd); 1553\& ev_stat_start (loop, &passwd);
1423.Ve 1554.Ve
1424.ie n .Sh """ev_idle"" \- when you've got nothing better to do..." 1555.ie n .Sh """ev_idle"" \- when you've got nothing better to do..."
1425.el .Sh "\f(CWev_idle\fP \- when you've got nothing better to do..." 1556.el .Sh "\f(CWev_idle\fP \- when you've got nothing better to do..."
1426.IX Subsection "ev_idle - when you've got nothing better to do..." 1557.IX Subsection "ev_idle - when you've got nothing better to do..."
1427Idle watchers trigger events when there are no other events are pending 1558Idle watchers trigger events when no other events of the same or higher
1428(prepare, check and other idle watchers do not count). That is, as long 1559priority are pending (prepare, check and other idle watchers do not
1429as your process is busy handling sockets or timeouts (or even signals, 1560count).
1430imagine) it will not be triggered. But when your process is idle all idle 1561.PP
1431watchers are being called again and again, once per event loop iteration \- 1562That is, as long as your process is busy handling sockets or timeouts
1563(or even signals, imagine) of the same or higher priority it will not be
1564triggered. But when your process is idle (or only lower-priority watchers
1565are pending), the idle watchers are being called once per event loop
1432until stopped, that is, or your process receives more events and becomes 1566iteration \- until stopped, that is, or your process receives more events
1433busy. 1567and becomes busy again with higher priority stuff.
1434.PP 1568.PP
1435The most noteworthy effect is that as long as any idle watchers are 1569The most noteworthy effect is that as long as any idle watchers are
1436active, the process will not block when waiting for new events. 1570active, the process will not block when waiting for new events.
1437.PP 1571.PP
1438Apart from keeping your process non-blocking (which is a useful 1572Apart from keeping your process non-blocking (which is a useful
… …
1443.IX Item "ev_idle_init (ev_signal *, callback)" 1577.IX Item "ev_idle_init (ev_signal *, callback)"
1444Initialises and configures the idle watcher \- it has no parameters of any 1578Initialises and configures the idle watcher \- it has no parameters of any
1445kind. There is a \f(CW\*(C`ev_idle_set\*(C'\fR macro, but using it is utterly pointless, 1579kind. There is a \f(CW\*(C`ev_idle_set\*(C'\fR macro, but using it is utterly pointless,
1446believe me. 1580believe me.
1447.PP 1581.PP
1448Example: dynamically allocate an \f(CW\*(C`ev_idle\*(C'\fR, start it, and in the 1582Example: Dynamically allocate an \f(CW\*(C`ev_idle\*(C'\fR watcher, start it, and in the
1449callback, free it. Alos, use no error checking, as usual. 1583callback, free it. Also, use no error checking, as usual.
1450.PP 1584.PP
1451.Vb 7 1585.Vb 7
1452\& static void 1586\& static void
1453\& idle_cb (struct ev_loop *loop, struct ev_idle *w, int revents) 1587\& idle_cb (struct ev_loop *loop, struct ev_idle *w, int revents)
1454\& { 1588\& {
… …
1501are ready to run (it's actually more complicated: it only runs coroutines 1635are ready to run (it's actually more complicated: it only runs coroutines
1502with priority higher than or equal to the event loop and one coroutine 1636with priority higher than or equal to the event loop and one coroutine
1503of lower priority, but only once, using idle watchers to keep the event 1637of lower priority, but only once, using idle watchers to keep the event
1504loop from blocking if lower-priority coroutines are active, thus mapping 1638loop from blocking if lower-priority coroutines are active, thus mapping
1505low-priority coroutines to idle/background tasks). 1639low-priority coroutines to idle/background tasks).
1640.PP
1641It is recommended to give \f(CW\*(C`ev_check\*(C'\fR watchers highest (\f(CW\*(C`EV_MAXPRI\*(C'\fR)
1642priority, to ensure that they are being run before any other watchers
1643after the poll. Also, \f(CW\*(C`ev_check\*(C'\fR watchers (and \f(CW\*(C`ev_prepare\*(C'\fR watchers,
1644too) should not activate (\*(L"feed\*(R") events into libev. While libev fully
1645supports this, they will be called before other \f(CW\*(C`ev_check\*(C'\fR watchers did
1646their job. As \f(CW\*(C`ev_check\*(C'\fR watchers are often used to embed other event
1647loops those other event loops might be in an unusable state until their
1648\&\f(CW\*(C`ev_check\*(C'\fR watcher ran (always remind yourself to coexist peacefully with
1649others).
1506.IP "ev_prepare_init (ev_prepare *, callback)" 4 1650.IP "ev_prepare_init (ev_prepare *, callback)" 4
1507.IX Item "ev_prepare_init (ev_prepare *, callback)" 1651.IX Item "ev_prepare_init (ev_prepare *, callback)"
1508.PD 0 1652.PD 0
1509.IP "ev_check_init (ev_check *, callback)" 4 1653.IP "ev_check_init (ev_check *, callback)" 4
1510.IX Item "ev_check_init (ev_check *, callback)" 1654.IX Item "ev_check_init (ev_check *, callback)"
1511.PD 1655.PD
1512Initialises and configures the prepare or check watcher \- they have no 1656Initialises and configures the prepare or check watcher \- they have no
1513parameters of any kind. There are \f(CW\*(C`ev_prepare_set\*(C'\fR and \f(CW\*(C`ev_check_set\*(C'\fR 1657parameters of any kind. There are \f(CW\*(C`ev_prepare_set\*(C'\fR and \f(CW\*(C`ev_check_set\*(C'\fR
1514macros, but using them is utterly, utterly and completely pointless. 1658macros, but using them is utterly, utterly and completely pointless.
1515.PP 1659.PP
1516Example: To include a library such as adns, you would add \s-1IO\s0 watchers 1660There are a number of principal ways to embed other event loops or modules
1517and a timeout watcher in a prepare handler, as required by libadns, and 1661into libev. Here are some ideas on how to include libadns into libev
1662(there is a Perl module named \f(CW\*(C`EV::ADNS\*(C'\fR that does this, which you could
1663use for an actually working example. Another Perl module named \f(CW\*(C`EV::Glib\*(C'\fR
1664embeds a Glib main context into libev, and finally, \f(CW\*(C`Glib::EV\*(C'\fR embeds \s-1EV\s0
1665into the Glib event loop).
1666.PP
1667Method 1: Add \s-1IO\s0 watchers and a timeout watcher in a prepare handler,
1518in a check watcher, destroy them and call into libadns. What follows is 1668and in a check watcher, destroy them and call into libadns. What follows
1519pseudo-code only of course: 1669is pseudo-code only of course. This requires you to either use a low
1670priority for the check watcher or use \f(CW\*(C`ev_clear_pending\*(C'\fR explicitly, as
1671the callbacks for the IO/timeout watchers might not have been called yet.
1520.PP 1672.PP
1521.Vb 2 1673.Vb 2
1522\& static ev_io iow [nfd]; 1674\& static ev_io iow [nfd];
1523\& static ev_timer tw; 1675\& static ev_timer tw;
1524.Ve 1676.Ve
1525.PP 1677.PP
1526.Vb 9 1678.Vb 4
1527\& static void 1679\& static void
1528\& io_cb (ev_loop *loop, ev_io *w, int revents) 1680\& io_cb (ev_loop *loop, ev_io *w, int revents)
1529\& { 1681\& {
1530\& // set the relevant poll flags
1531\& // could also call adns_processreadable etc. here
1532\& struct pollfd *fd = (struct pollfd *)w->data;
1533\& if (revents & EV_READ ) fd->revents |= fd->events & POLLIN;
1534\& if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT;
1535\& } 1682\& }
1536.Ve 1683.Ve
1537.PP 1684.PP
1538.Vb 7 1685.Vb 8
1539\& // create io watchers for each fd and a timer before blocking 1686\& // create io watchers for each fd and a timer before blocking
1540\& static void 1687\& static void
1541\& adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) 1688\& adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents)
1542\& { 1689\& {
1543\& int timeout = 3600000;truct pollfd fds [nfd]; 1690\& int timeout = 3600000;
1691\& struct pollfd fds [nfd];
1544\& // actual code will need to loop here and realloc etc. 1692\& // actual code will need to loop here and realloc etc.
1545\& adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ())); 1693\& adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ()));
1546.Ve 1694.Ve
1547.PP 1695.PP
1548.Vb 3 1696.Vb 3
… …
1550\& ev_timer_init (&tw, 0, timeout * 1e-3); 1698\& ev_timer_init (&tw, 0, timeout * 1e-3);
1551\& ev_timer_start (loop, &tw); 1699\& ev_timer_start (loop, &tw);
1552.Ve 1700.Ve
1553.PP 1701.PP
1554.Vb 6 1702.Vb 6
1555\& // create on ev_io per pollfd 1703\& // create one ev_io per pollfd
1556\& for (int i = 0; i < nfd; ++i) 1704\& for (int i = 0; i < nfd; ++i)
1557\& { 1705\& {
1558\& ev_io_init (iow + i, io_cb, fds [i].fd, 1706\& ev_io_init (iow + i, io_cb, fds [i].fd,
1559\& ((fds [i].events & POLLIN ? EV_READ : 0) 1707\& ((fds [i].events & POLLIN ? EV_READ : 0)
1560\& | (fds [i].events & POLLOUT ? EV_WRITE : 0))); 1708\& | (fds [i].events & POLLOUT ? EV_WRITE : 0)));
1561.Ve 1709.Ve
1562.PP 1710.PP
1563.Vb 5 1711.Vb 4
1564\& fds [i].revents = 0; 1712\& fds [i].revents = 0;
1565\& iow [i].data = fds + i;
1566\& ev_io_start (loop, iow + i); 1713\& ev_io_start (loop, iow + i);
1567\& } 1714\& }
1568\& } 1715\& }
1569.Ve 1716.Ve
1570.PP 1717.PP
… …
1574\& adns_check_cb (ev_loop *loop, ev_check *w, int revents) 1721\& adns_check_cb (ev_loop *loop, ev_check *w, int revents)
1575\& { 1722\& {
1576\& ev_timer_stop (loop, &tw); 1723\& ev_timer_stop (loop, &tw);
1577.Ve 1724.Ve
1578.PP 1725.PP
1579.Vb 2 1726.Vb 8
1580\& for (int i = 0; i < nfd; ++i) 1727\& for (int i = 0; i < nfd; ++i)
1728\& {
1729\& // set the relevant poll flags
1730\& // could also call adns_processreadable etc. here
1731\& struct pollfd *fd = fds + i;
1732\& int revents = ev_clear_pending (iow + i);
1733\& if (revents & EV_READ ) fd->revents |= fd->events & POLLIN;
1734\& if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT;
1735.Ve
1736.PP
1737.Vb 3
1738\& // now stop the watcher
1581\& ev_io_stop (loop, iow + i); 1739\& ev_io_stop (loop, iow + i);
1740\& }
1582.Ve 1741.Ve
1583.PP 1742.PP
1584.Vb 2 1743.Vb 2
1585\& adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop)); 1744\& adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop));
1745\& }
1746.Ve
1747.PP
1748Method 2: This would be just like method 1, but you run \f(CW\*(C`adns_afterpoll\*(C'\fR
1749in the prepare watcher and would dispose of the check watcher.
1750.PP
1751Method 3: If the module to be embedded supports explicit event
1752notification (adns does), you can also make use of the actual watcher
1753callbacks, and only destroy/create the watchers in the prepare watcher.
1754.PP
1755.Vb 5
1756\& static void
1757\& timer_cb (EV_P_ ev_timer *w, int revents)
1758\& {
1759\& adns_state ads = (adns_state)w->data;
1760\& update_now (EV_A);
1761.Ve
1762.PP
1763.Vb 2
1764\& adns_processtimeouts (ads, &tv_now);
1765\& }
1766.Ve
1767.PP
1768.Vb 5
1769\& static void
1770\& io_cb (EV_P_ ev_io *w, int revents)
1771\& {
1772\& adns_state ads = (adns_state)w->data;
1773\& update_now (EV_A);
1774.Ve
1775.PP
1776.Vb 3
1777\& if (revents & EV_READ ) adns_processreadable (ads, w->fd, &tv_now);
1778\& if (revents & EV_WRITE) adns_processwriteable (ads, w->fd, &tv_now);
1779\& }
1780.Ve
1781.PP
1782.Vb 1
1783\& // do not ever call adns_afterpoll
1784.Ve
1785.PP
1786Method 4: Do not use a prepare or check watcher because the module you
1787want to embed is too inflexible to support it. Instead, youc na override
1788their poll function. The drawback with this solution is that the main
1789loop is now no longer controllable by \s-1EV\s0. The \f(CW\*(C`Glib::EV\*(C'\fR module does
1790this.
1791.PP
1792.Vb 4
1793\& static gint
1794\& event_poll_func (GPollFD *fds, guint nfds, gint timeout)
1795\& {
1796\& int got_events = 0;
1797.Ve
1798.PP
1799.Vb 2
1800\& for (n = 0; n < nfds; ++n)
1801\& // create/start io watcher that sets the relevant bits in fds[n] and increment got_events
1802.Ve
1803.PP
1804.Vb 2
1805\& if (timeout >= 0)
1806\& // create/start timer
1807.Ve
1808.PP
1809.Vb 2
1810\& // poll
1811\& ev_loop (EV_A_ 0);
1812.Ve
1813.PP
1814.Vb 3
1815\& // stop timer again
1816\& if (timeout >= 0)
1817\& ev_timer_stop (EV_A_ &to);
1818.Ve
1819.PP
1820.Vb 3
1821\& // stop io watchers again - their callbacks should have set
1822\& for (n = 0; n < nfds; ++n)
1823\& ev_io_stop (EV_A_ iow [n]);
1824.Ve
1825.PP
1826.Vb 2
1827\& return got_events;
1586\& } 1828\& }
1587.Ve 1829.Ve
1588.ie n .Sh """ev_embed"" \- when one backend isn't enough..." 1830.ie n .Sh """ev_embed"" \- when one backend isn't enough..."
1589.el .Sh "\f(CWev_embed\fP \- when one backend isn't enough..." 1831.el .Sh "\f(CWev_embed\fP \- when one backend isn't enough..."
1590.IX Subsection "ev_embed - when one backend isn't enough..." 1832.IX Subsection "ev_embed - when one backend isn't enough..."
… …
1774.PP 2016.PP
1775.Vb 1 2017.Vb 1
1776\& #include <ev++.h> 2018\& #include <ev++.h>
1777.Ve 2019.Ve
1778.PP 2020.PP
1779(it is not installed by default). This automatically includes \fIev.h\fR 2021This automatically includes \fIev.h\fR and puts all of its definitions (many
1780and puts all of its definitions (many of them macros) into the global 2022of them macros) into the global namespace. All \*(C+ specific things are
1781namespace. All \*(C+ specific things are put into the \f(CW\*(C`ev\*(C'\fR namespace. 2023put into the \f(CW\*(C`ev\*(C'\fR namespace. It should support all the same embedding
2024options as \fIev.h\fR, most notably \f(CW\*(C`EV_MULTIPLICITY\*(C'\fR.
1782.PP 2025.PP
1783It should support all the same embedding options as \fIev.h\fR, most notably 2026Care has been taken to keep the overhead low. The only data member the \*(C+
1784\&\f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. 2027classes add (compared to plain C\-style watchers) is the event loop pointer
2028that the watcher is associated with (or no additional members at all if
2029you disable \f(CW\*(C`EV_MULTIPLICITY\*(C'\fR when embedding libev).
2030.PP
2031Currently, functions, and static and non-static member functions can be
2032used as callbacks. Other types should be easy to add as long as they only
2033need one additional pointer for context. If you need support for other
2034types of functors please contact the author (preferably after implementing
2035it).
1785.PP 2036.PP
1786Here is a list of things available in the \f(CW\*(C`ev\*(C'\fR namespace: 2037Here is a list of things available in the \f(CW\*(C`ev\*(C'\fR namespace:
1787.ie n .IP """ev::READ""\fR, \f(CW""ev::WRITE"" etc." 4 2038.ie n .IP """ev::READ""\fR, \f(CW""ev::WRITE"" etc." 4
1788.el .IP "\f(CWev::READ\fR, \f(CWev::WRITE\fR etc." 4 2039.el .IP "\f(CWev::READ\fR, \f(CWev::WRITE\fR etc." 4
1789.IX Item "ev::READ, ev::WRITE etc." 2040.IX Item "ev::READ, ev::WRITE etc."
… …
1801which is called \f(CW\*(C`ev::sig\*(C'\fR to avoid clashes with the \f(CW\*(C`signal\*(C'\fR macro 2052which is called \f(CW\*(C`ev::sig\*(C'\fR to avoid clashes with the \f(CW\*(C`signal\*(C'\fR macro
1802defines by many implementations. 2053defines by many implementations.
1803.Sp 2054.Sp
1804All of those classes have these methods: 2055All of those classes have these methods:
1805.RS 4 2056.RS 4
1806.IP "ev::TYPE::TYPE (object *, object::method *)" 4 2057.IP "ev::TYPE::TYPE ()" 4
1807.IX Item "ev::TYPE::TYPE (object *, object::method *)" 2058.IX Item "ev::TYPE::TYPE ()"
1808.PD 0 2059.PD 0
1809.IP "ev::TYPE::TYPE (object *, object::method *, struct ev_loop *)" 4 2060.IP "ev::TYPE::TYPE (struct ev_loop *)" 4
1810.IX Item "ev::TYPE::TYPE (object *, object::method *, struct ev_loop *)" 2061.IX Item "ev::TYPE::TYPE (struct ev_loop *)"
1811.IP "ev::TYPE::~TYPE" 4 2062.IP "ev::TYPE::~TYPE" 4
1812.IX Item "ev::TYPE::~TYPE" 2063.IX Item "ev::TYPE::~TYPE"
1813.PD 2064.PD
1814The constructor takes a pointer to an object and a method pointer to 2065The constructor (optionally) takes an event loop to associate the watcher
1815the event handler callback to call in this class. The constructor calls 2066with. If it is omitted, it will use \f(CW\*(C`EV_DEFAULT\*(C'\fR.
1816\&\f(CW\*(C`ev_init\*(C'\fR for you, which means you have to call the \f(CW\*(C`set\*(C'\fR method 2067.Sp
1817before starting it. If you do not specify a loop then the constructor 2068The constructor calls \f(CW\*(C`ev_init\*(C'\fR for you, which means you have to call the
1818automatically associates the default loop with this watcher. 2069\&\f(CW\*(C`set\*(C'\fR method before starting it.
2070.Sp
2071It will not set a callback, however: You have to call the templated \f(CW\*(C`set\*(C'\fR
2072method to set a callback before you can start the watcher.
2073.Sp
2074(The reason why you have to use a method is a limitation in \*(C+ which does
2075not allow explicit template arguments for constructors).
1819.Sp 2076.Sp
1820The destructor automatically stops the watcher if it is active. 2077The destructor automatically stops the watcher if it is active.
2078.IP "w\->set<class, &class::method> (object *)" 4
2079.IX Item "w->set<class, &class::method> (object *)"
2080This method sets the callback method to call. The method has to have a
2081signature of \f(CW\*(C`void (*)(ev_TYPE &, int)\*(C'\fR, it receives the watcher as
2082first argument and the \f(CW\*(C`revents\*(C'\fR as second. The object must be given as
2083parameter and is stored in the \f(CW\*(C`data\*(C'\fR member of the watcher.
2084.Sp
2085This method synthesizes efficient thunking code to call your method from
2086the C callback that libev requires. If your compiler can inline your
2087callback (i.e. it is visible to it at the place of the \f(CW\*(C`set\*(C'\fR call and
2088your compiler is good :), then the method will be fully inlined into the
2089thunking function, making it as fast as a direct C callback.
2090.Sp
2091Example: simple class declaration and watcher initialisation
2092.Sp
2093.Vb 4
2094\& struct myclass
2095\& {
2096\& void io_cb (ev::io &w, int revents) { }
2097\& }
2098.Ve
2099.Sp
2100.Vb 3
2101\& myclass obj;
2102\& ev::io iow;
2103\& iow.set <myclass, &myclass::io_cb> (&obj);
2104.Ve
2105.IP "w\->set<function> (void *data = 0)" 4
2106.IX Item "w->set<function> (void *data = 0)"
2107Also sets a callback, but uses a static method or plain function as
2108callback. The optional \f(CW\*(C`data\*(C'\fR argument will be stored in the watcher's
2109\&\f(CW\*(C`data\*(C'\fR member and is free for you to use.
2110.Sp
2111The prototype of the \f(CW\*(C`function\*(C'\fR must be \f(CW\*(C`void (*)(ev::TYPE &w, int)\*(C'\fR.
2112.Sp
2113See the method\-\f(CW\*(C`set\*(C'\fR above for more details.
2114.Sp
2115Example:
2116.Sp
2117.Vb 2
2118\& static void io_cb (ev::io &w, int revents) { }
2119\& iow.set <io_cb> ();
2120.Ve
1821.IP "w\->set (struct ev_loop *)" 4 2121.IP "w\->set (struct ev_loop *)" 4
1822.IX Item "w->set (struct ev_loop *)" 2122.IX Item "w->set (struct ev_loop *)"
1823Associates a different \f(CW\*(C`struct ev_loop\*(C'\fR with this watcher. You can only 2123Associates a different \f(CW\*(C`struct ev_loop\*(C'\fR with this watcher. You can only
1824do this when the watcher is inactive (and not pending either). 2124do this when the watcher is inactive (and not pending either).
1825.IP "w\->set ([args])" 4 2125.IP "w\->set ([args])" 4
1826.IX Item "w->set ([args])" 2126.IX Item "w->set ([args])"
1827Basically the same as \f(CW\*(C`ev_TYPE_set\*(C'\fR, with the same args. Must be 2127Basically the same as \f(CW\*(C`ev_TYPE_set\*(C'\fR, with the same args. Must be
1828called at least once. Unlike the C counterpart, an active watcher gets 2128called at least once. Unlike the C counterpart, an active watcher gets
1829automatically stopped and restarted. 2129automatically stopped and restarted when reconfiguring it with this
2130method.
1830.IP "w\->start ()" 4 2131.IP "w\->start ()" 4
1831.IX Item "w->start ()" 2132.IX Item "w->start ()"
1832Starts the watcher. Note that there is no \f(CW\*(C`loop\*(C'\fR argument as the 2133Starts the watcher. Note that there is no \f(CW\*(C`loop\*(C'\fR argument, as the
1833constructor already takes the loop. 2134constructor already stores the event loop.
1834.IP "w\->stop ()" 4 2135.IP "w\->stop ()" 4
1835.IX Item "w->stop ()" 2136.IX Item "w->stop ()"
1836Stops the watcher if it is active. Again, no \f(CW\*(C`loop\*(C'\fR argument. 2137Stops the watcher if it is active. Again, no \f(CW\*(C`loop\*(C'\fR argument.
1837.ie n .IP "w\->again () ""ev::timer""\fR, \f(CW""ev::periodic"" only" 4 2138.ie n .IP "w\->again () ""ev::timer""\fR, \f(CW""ev::periodic"" only" 4
1838.el .IP "w\->again () \f(CWev::timer\fR, \f(CWev::periodic\fR only" 4 2139.el .IP "w\->again () \f(CWev::timer\fR, \f(CWev::periodic\fR only" 4
… …
1864.Vb 2 2165.Vb 2
1865\& myclass (); 2166\& myclass ();
1866\& } 2167\& }
1867.Ve 2168.Ve
1868.PP 2169.PP
1869.Vb 6 2170.Vb 4
1870\& myclass::myclass (int fd) 2171\& myclass::myclass (int fd)
1871\& : io (this, &myclass::io_cb),
1872\& idle (this, &myclass::idle_cb)
1873\& { 2172\& {
2173\& io .set <myclass, &myclass::io_cb > (this);
2174\& idle.set <myclass, &myclass::idle_cb> (this);
2175.Ve
2176.PP
2177.Vb 2
1874\& io.start (fd, ev::READ); 2178\& io.start (fd, ev::READ);
1875\& } 2179\& }
1876.Ve 2180.Ve
1877.SH "MACRO MAGIC" 2181.SH "MACRO MAGIC"
1878.IX Header "MACRO MAGIC" 2182.IX Header "MACRO MAGIC"
1879Libev can be compiled with a variety of options, the most fundemantal is 2183Libev can be compiled with a variety of options, the most fundemantal is
1880\&\f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. This option determines wether (most) functions and 2184\&\f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. This option determines whether (most) functions and
1881callbacks have an initial \f(CW\*(C`struct ev_loop *\*(C'\fR argument. 2185callbacks have an initial \f(CW\*(C`struct ev_loop *\*(C'\fR argument.
1882.PP 2186.PP
1883To make it easier to write programs that cope with either variant, the 2187To make it easier to write programs that cope with either variant, the
1884following macros are defined: 2188following macros are defined:
1885.ie n .IP """EV_A""\fR, \f(CW""EV_A_""" 4 2189.ie n .IP """EV_A""\fR, \f(CW""EV_A_""" 4
… …
1920.el .IP "\f(CWEV_DEFAULT\fR, \f(CWEV_DEFAULT_\fR" 4 2224.el .IP "\f(CWEV_DEFAULT\fR, \f(CWEV_DEFAULT_\fR" 4
1921.IX Item "EV_DEFAULT, EV_DEFAULT_" 2225.IX Item "EV_DEFAULT, EV_DEFAULT_"
1922Similar to the other two macros, this gives you the value of the default 2226Similar to the other two macros, this gives you the value of the default
1923loop, if multiple loops are supported (\*(L"ev loop default\*(R"). 2227loop, if multiple loops are supported (\*(L"ev loop default\*(R").
1924.PP 2228.PP
1925Example: Declare and initialise a check watcher, working regardless of 2229Example: Declare and initialise a check watcher, utilising the above
1926wether multiple loops are supported or not. 2230macros so it will work regardless of whether multiple loops are supported
2231or not.
1927.PP 2232.PP
1928.Vb 5 2233.Vb 5
1929\& static void 2234\& static void
1930\& check_cb (EV_P_ ev_timer *w, int revents) 2235\& check_cb (EV_P_ ev_timer *w, int revents)
1931\& { 2236\& {
… …
1994.Vb 1 2299.Vb 1
1995\& ev_win32.c required on win32 platforms only 2300\& ev_win32.c required on win32 platforms only
1996.Ve 2301.Ve
1997.PP 2302.PP
1998.Vb 5 2303.Vb 5
1999\& ev_select.c only when select backend is enabled (which is by default) 2304\& ev_select.c only when select backend is enabled (which is enabled by default)
2000\& ev_poll.c only when poll backend is enabled (disabled by default) 2305\& ev_poll.c only when poll backend is enabled (disabled by default)
2001\& ev_epoll.c only when the epoll backend is enabled (disabled by default) 2306\& ev_epoll.c only when the epoll backend is enabled (disabled by default)
2002\& ev_kqueue.c only when the kqueue backend is enabled (disabled by default) 2307\& ev_kqueue.c only when the kqueue backend is enabled (disabled by default)
2003\& ev_port.c only when the solaris port backend is enabled (disabled by default) 2308\& ev_port.c only when the solaris port backend is enabled (disabled by default)
2004.Ve 2309.Ve
… …
2125otherwise another method will be used as fallback. This is the preferred 2430otherwise another method will be used as fallback. This is the preferred
2126backend for Solaris 10 systems. 2431backend for Solaris 10 systems.
2127.IP "\s-1EV_USE_DEVPOLL\s0" 4 2432.IP "\s-1EV_USE_DEVPOLL\s0" 4
2128.IX Item "EV_USE_DEVPOLL" 2433.IX Item "EV_USE_DEVPOLL"
2129reserved for future expansion, works like the \s-1USE\s0 symbols above. 2434reserved for future expansion, works like the \s-1USE\s0 symbols above.
2435.IP "\s-1EV_USE_INOTIFY\s0" 4
2436.IX Item "EV_USE_INOTIFY"
2437If defined to be \f(CW1\fR, libev will compile in support for the Linux inotify
2438interface to speed up \f(CW\*(C`ev_stat\*(C'\fR watchers. Its actual availability will
2439be detected at runtime.
2130.IP "\s-1EV_H\s0" 4 2440.IP "\s-1EV_H\s0" 4
2131.IX Item "EV_H" 2441.IX Item "EV_H"
2132The name of the \fIev.h\fR header file used to include it. The default if 2442The name of the \fIev.h\fR header file used to include it. The default if
2133undefined is \f(CW\*(C`<ev.h>\*(C'\fR in \fIevent.h\fR and \f(CW"ev.h"\fR in \fIev.c\fR. This 2443undefined is \f(CW\*(C`<ev.h>\*(C'\fR in \fIevent.h\fR and \f(CW"ev.h"\fR in \fIev.c\fR. This
2134can be used to virtually rename the \fIev.h\fR header file in case of conflicts. 2444can be used to virtually rename the \fIev.h\fR header file in case of conflicts.
… …
2152If undefined or defined to \f(CW1\fR, then all event-loop-specific functions 2462If undefined or defined to \f(CW1\fR, then all event-loop-specific functions
2153will have the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument, and you can create 2463will have the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument, and you can create
2154additional independent event loops. Otherwise there will be no support 2464additional independent event loops. Otherwise there will be no support
2155for multiple event loops and there is no first event loop pointer 2465for multiple event loops and there is no first event loop pointer
2156argument. Instead, all functions act on the single default loop. 2466argument. Instead, all functions act on the single default loop.
2467.IP "\s-1EV_MINPRI\s0" 4
2468.IX Item "EV_MINPRI"
2469.PD 0
2470.IP "\s-1EV_MAXPRI\s0" 4
2471.IX Item "EV_MAXPRI"
2472.PD
2473The range of allowed priorities. \f(CW\*(C`EV_MINPRI\*(C'\fR must be smaller or equal to
2474\&\f(CW\*(C`EV_MAXPRI\*(C'\fR, but otherwise there are no non-obvious limitations. You can
2475provide for more priorities by overriding those symbols (usually defined
2476to be \f(CW\*(C`\-2\*(C'\fR and \f(CW2\fR, respectively).
2477.Sp
2478When doing priority-based operations, libev usually has to linearly search
2479all the priorities, so having many of them (hundreds) uses a lot of space
2480and time, so using the defaults of five priorities (\-2 .. +2) is usually
2481fine.
2482.Sp
2483If your embedding app does not need any priorities, defining these both to
2484\&\f(CW0\fR will save some memory and cpu.
2157.IP "\s-1EV_PERIODIC_ENABLE\s0" 4 2485.IP "\s-1EV_PERIODIC_ENABLE\s0" 4
2158.IX Item "EV_PERIODIC_ENABLE" 2486.IX Item "EV_PERIODIC_ENABLE"
2159If undefined or defined to be \f(CW1\fR, then periodic timers are supported. If 2487If undefined or defined to be \f(CW1\fR, then periodic timers are supported. If
2488defined to be \f(CW0\fR, then they are not. Disabling them saves a few kB of
2489code.
2490.IP "\s-1EV_IDLE_ENABLE\s0" 4
2491.IX Item "EV_IDLE_ENABLE"
2492If undefined or defined to be \f(CW1\fR, then idle watchers are supported. If
2160defined to be \f(CW0\fR, then they are not. Disabling them saves a few kB of 2493defined to be \f(CW0\fR, then they are not. Disabling them saves a few kB of
2161code. 2494code.
2162.IP "\s-1EV_EMBED_ENABLE\s0" 4 2495.IP "\s-1EV_EMBED_ENABLE\s0" 4
2163.IX Item "EV_EMBED_ENABLE" 2496.IX Item "EV_EMBED_ENABLE"
2164If undefined or defined to be \f(CW1\fR, then embed watchers are supported. If 2497If undefined or defined to be \f(CW1\fR, then embed watchers are supported. If
… …
2179.IP "\s-1EV_PID_HASHSIZE\s0" 4 2512.IP "\s-1EV_PID_HASHSIZE\s0" 4
2180.IX Item "EV_PID_HASHSIZE" 2513.IX Item "EV_PID_HASHSIZE"
2181\&\f(CW\*(C`ev_child\*(C'\fR watchers use a small hash table to distribute workload by 2514\&\f(CW\*(C`ev_child\*(C'\fR watchers use a small hash table to distribute workload by
2182pid. The default size is \f(CW16\fR (or \f(CW1\fR with \f(CW\*(C`EV_MINIMAL\*(C'\fR), usually more 2515pid. The default size is \f(CW16\fR (or \f(CW1\fR with \f(CW\*(C`EV_MINIMAL\*(C'\fR), usually more
2183than enough. If you need to manage thousands of children you might want to 2516than enough. If you need to manage thousands of children you might want to
2184increase this value. 2517increase this value (\fImust\fR be a power of two).
2518.IP "\s-1EV_INOTIFY_HASHSIZE\s0" 4
2519.IX Item "EV_INOTIFY_HASHSIZE"
2520\&\f(CW\*(C`ev_staz\*(C'\fR watchers use a small hash table to distribute workload by
2521inotify watch id. The default size is \f(CW16\fR (or \f(CW1\fR with \f(CW\*(C`EV_MINIMAL\*(C'\fR),
2522usually more than enough. If you need to manage thousands of \f(CW\*(C`ev_stat\*(C'\fR
2523watchers you might want to increase this value (\fImust\fR be a power of
2524two).
2185.IP "\s-1EV_COMMON\s0" 4 2525.IP "\s-1EV_COMMON\s0" 4
2186.IX Item "EV_COMMON" 2526.IX Item "EV_COMMON"
2187By default, all watchers have a \f(CW\*(C`void *data\*(C'\fR member. By redefining 2527By default, all watchers have a \f(CW\*(C`void *data\*(C'\fR member. By redefining
2188this macro to a something else you can include more and other types of 2528this macro to a something else you can include more and other types of
2189members. You have to define it each time you include one of the files, 2529members. You have to define it each time you include one of the files,
… …
2219interface) and \fI\s-1EV\s0.xs\fR (implementation) files. Only the \fI\s-1EV\s0.xs\fR file 2559interface) and \fI\s-1EV\s0.xs\fR (implementation) files. Only the \fI\s-1EV\s0.xs\fR file
2220will be compiled. It is pretty complex because it provides its own header 2560will be compiled. It is pretty complex because it provides its own header
2221file. 2561file.
2222.Sp 2562.Sp
2223The usage in rxvt-unicode is simpler. It has a \fIev_cpp.h\fR header file 2563The usage in rxvt-unicode is simpler. It has a \fIev_cpp.h\fR header file
2224that everybody includes and which overrides some autoconf choices: 2564that everybody includes and which overrides some configure choices:
2225.Sp 2565.Sp
2226.Vb 4 2566.Vb 9
2567\& #define EV_MINIMAL 1
2227\& #define EV_USE_POLL 0 2568\& #define EV_USE_POLL 0
2228\& #define EV_MULTIPLICITY 0 2569\& #define EV_MULTIPLICITY 0
2229\& #define EV_PERIODICS 0 2570\& #define EV_PERIODIC_ENABLE 0
2571\& #define EV_STAT_ENABLE 0
2572\& #define EV_FORK_ENABLE 0
2230\& #define EV_CONFIG_H <config.h> 2573\& #define EV_CONFIG_H <config.h>
2574\& #define EV_MINPRI 0
2575\& #define EV_MAXPRI 0
2231.Ve 2576.Ve
2232.Sp 2577.Sp
2233.Vb 1 2578.Vb 1
2234\& #include "ev++.h" 2579\& #include "ev++.h"
2235.Ve 2580.Ve
… …
2243.SH "COMPLEXITIES" 2588.SH "COMPLEXITIES"
2244.IX Header "COMPLEXITIES" 2589.IX Header "COMPLEXITIES"
2245In this section the complexities of (many of) the algorithms used inside 2590In this section the complexities of (many of) the algorithms used inside
2246libev will be explained. For complexity discussions about backends see the 2591libev will be explained. For complexity discussions about backends see the
2247documentation for \f(CW\*(C`ev_default_init\*(C'\fR. 2592documentation for \f(CW\*(C`ev_default_init\*(C'\fR.
2593.Sp
2594All of the following are about amortised time: If an array needs to be
2595extended, libev needs to realloc and move the whole array, but this
2596happens asymptotically never with higher number of elements, so O(1) might
2597mean it might do a lengthy realloc operation in rare cases, but on average
2598it is much faster and asymptotically approaches constant time.
2248.RS 4 2599.RS 4
2249.IP "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" 4 2600.IP "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" 4
2250.IX Item "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" 2601.IX Item "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)"
2251.PD 0 2602This means that, when you have a watcher that triggers in one hour and
2603there are 100 watchers that would trigger before that then inserting will
2604have to skip those 100 watchers.
2252.IP "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)" 4 2605.IP "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)" 4
2253.IX Item "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)" 2606.IX Item "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)"
2607That means that for changing a timer costs less than removing/adding them
2608as only the relative motion in the event queue has to be paid for.
2254.IP "Starting io/check/prepare/idle/signal/child watchers: O(1)" 4 2609.IP "Starting io/check/prepare/idle/signal/child watchers: O(1)" 4
2255.IX Item "Starting io/check/prepare/idle/signal/child watchers: O(1)" 2610.IX Item "Starting io/check/prepare/idle/signal/child watchers: O(1)"
2256.IP "Stopping check/prepare/idle watchers: O(1)" 4 2611These just add the watcher into an array or at the head of a list.
2257.IX Item "Stopping check/prepare/idle watchers: O(1)" 2612=item Stopping check/prepare/idle watchers: O(1)
2258.IP "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % 16))" 4 2613.IP "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % \s-1EV_PID_HASHSIZE\s0))" 4
2259.IX Item "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % 16))" 2614.IX Item "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))"
2615These watchers are stored in lists then need to be walked to find the
2616correct watcher to remove. The lists are usually short (you don't usually
2617have many watchers waiting for the same fd or signal).
2260.IP "Finding the next timer per loop iteration: O(1)" 4 2618.IP "Finding the next timer per loop iteration: O(1)" 4
2261.IX Item "Finding the next timer per loop iteration: O(1)" 2619.IX Item "Finding the next timer per loop iteration: O(1)"
2620.PD 0
2262.IP "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)" 4 2621.IP "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)" 4
2263.IX Item "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)" 2622.IX Item "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)"
2623.PD
2624A change means an I/O watcher gets started or stopped, which requires
2625libev to recalculate its status (and possibly tell the kernel).
2264.IP "Activating one watcher: O(1)" 4 2626.IP "Activating one watcher: O(1)" 4
2265.IX Item "Activating one watcher: O(1)" 2627.IX Item "Activating one watcher: O(1)"
2628.PD 0
2629.IP "Priority handling: O(number_of_priorities)" 4
2630.IX Item "Priority handling: O(number_of_priorities)"
2631.PD
2632Priorities are implemented by allocating some space for each
2633priority. When doing priority-based operations, libev usually has to
2634linearly search all the priorities.
2266.RE 2635.RE
2267.RS 4 2636.RS 4
2268.PD
2269.SH "AUTHOR" 2637.SH "AUTHOR"
2270.IX Header "AUTHOR" 2638.IX Header "AUTHOR"
2271Marc Lehmann <libev@schmorp.de>. 2639Marc Lehmann <libev@schmorp.de>.

Diff Legend

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