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

Comparing libev/ev.3 (file contents):
Revision 1.33 by root, Wed Nov 28 18:29:29 2007 UTC vs.
Revision 1.48 by root, Sun Dec 9 19:47:29 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-28" "perl v5.8.8" "User Contributed Perl Documentation" 132.TH "<STANDARD INPUT>" 1 "2007-12-09" "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
… …
196\& return 0; 196\& return 0;
197\& } 197\& }
198.Ve 198.Ve
199.SH "DESCRIPTION" 199.SH "DESCRIPTION"
200.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
201Libev 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
202file descriptor being readable or a timeout occuring), and it will manage 206file descriptor being readable or a timeout occuring), and it will manage
203these event sources and provide your program with events. 207these event sources and provide your program with events.
204.PP 208.PP
205To 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
… …
255.IX Item "int ev_version_major ()" 259.IX Item "int ev_version_major ()"
256.PD 0 260.PD 0
257.IP "int ev_version_minor ()" 4 261.IP "int ev_version_minor ()" 4
258.IX Item "int ev_version_minor ()" 262.IX Item "int ev_version_minor ()"
259.PD 263.PD
260You can find out the major and minor version numbers of the library 264You can find out the major and minor \s-1ABI\s0 version numbers of the library
261you linked against by calling the functions \f(CW\*(C`ev_version_major\*(C'\fR and 265you linked against by calling the functions \f(CW\*(C`ev_version_major\*(C'\fR and
262\&\f(CW\*(C`ev_version_minor\*(C'\fR. If you want, you can compare against the global 266\&\f(CW\*(C`ev_version_minor\*(C'\fR. If you want, you can compare against the global
263symbols \f(CW\*(C`EV_VERSION_MAJOR\*(C'\fR and \f(CW\*(C`EV_VERSION_MINOR\*(C'\fR, which specify the 267symbols \f(CW\*(C`EV_VERSION_MAJOR\*(C'\fR and \f(CW\*(C`EV_VERSION_MINOR\*(C'\fR, which specify the
264version of the library your program was compiled against. 268version of the library your program was compiled against.
265.Sp 269.Sp
270These version numbers refer to the \s-1ABI\s0 version of the library, not the
271release version.
272.Sp
266Usually, it's a good idea to terminate if the major versions mismatch, 273Usually, it's a good idea to terminate if the major versions mismatch,
267as this indicates an incompatible change. Minor versions are usually 274as this indicates an incompatible change. Minor versions are usually
268compatible to older versions, so a larger minor version alone is usually 275compatible to older versions, so a larger minor version alone is usually
269not a problem. 276not a problem.
270.Sp 277.Sp
271Example: Make sure we haven't accidentally been linked against the wrong 278Example: Make sure we haven't accidentally been linked against the wrong
272version. 279version.
… …
411or setgid) then libev will \fInot\fR look at the environment variable 418or setgid) then libev will \fInot\fR look at the environment variable
412\&\f(CW\*(C`LIBEV_FLAGS\*(C'\fR. Otherwise (the default), this environment variable will 419\&\f(CW\*(C`LIBEV_FLAGS\*(C'\fR. Otherwise (the default), this environment variable will
413override the flags completely if it is found in the environment. This is 420override the flags completely if it is found in the environment. This is
414useful to try out specific backends to test their performance, or to work 421useful to try out specific backends to test their performance, or to work
415around bugs. 422around bugs.
423.ie n .IP """EVFLAG_FORKCHECK""" 4
424.el .IP "\f(CWEVFLAG_FORKCHECK\fR" 4
425.IX Item "EVFLAG_FORKCHECK"
426Instead of calling \f(CW\*(C`ev_default_fork\*(C'\fR or \f(CW\*(C`ev_loop_fork\*(C'\fR manually after
427a fork, you can also make libev check for a fork in each iteration by
428enabling this flag.
429.Sp
430This works by calling \f(CW\*(C`getpid ()\*(C'\fR on every iteration of the loop,
431and thus this might slow down your event loop if you do a lot of loop
432iterations and little real work, but is usually not noticeable (on my
433Linux system for example, \f(CW\*(C`getpid\*(C'\fR is actually a simple 5\-insn sequence
434without a syscall and thus \fIvery\fR fast, but my Linux system also has
435\&\f(CW\*(C`pthread_atfork\*(C'\fR which is even faster).
436.Sp
437The big advantage of this flag is that you can forget about fork (and
438forget about forgetting to tell libev about forking) when you use this
439flag.
440.Sp
441This flag setting cannot be overriden or specified in the \f(CW\*(C`LIBEV_FLAGS\*(C'\fR
442environment variable.
416.ie n .IP """EVBACKEND_SELECT"" (value 1, portable select backend)" 4 443.ie n .IP """EVBACKEND_SELECT"" (value 1, portable select backend)" 4
417.el .IP "\f(CWEVBACKEND_SELECT\fR (value 1, portable select backend)" 4 444.el .IP "\f(CWEVBACKEND_SELECT\fR (value 1, portable select backend)" 4
418.IX Item "EVBACKEND_SELECT (value 1, portable select backend)" 445.IX Item "EVBACKEND_SELECT (value 1, portable select backend)"
419This is your standard \fIselect\fR\|(2) backend. Not \fIcompletely\fR standard, as 446This is your standard \fIselect\fR\|(2) backend. Not \fIcompletely\fR standard, as
420libev tries to roll its own fd_set with no limits on the number of fds, 447libev tries to roll its own fd_set with no limits on the number of fds,
… …
561.IP "ev_loop_fork (loop)" 4 588.IP "ev_loop_fork (loop)" 4
562.IX Item "ev_loop_fork (loop)" 589.IX Item "ev_loop_fork (loop)"
563Like \f(CW\*(C`ev_default_fork\*(C'\fR, but acts on an event loop created by 590Like \f(CW\*(C`ev_default_fork\*(C'\fR, but acts on an event loop created by
564\&\f(CW\*(C`ev_loop_new\*(C'\fR. Yes, you have to call this on every allocated event loop 591\&\f(CW\*(C`ev_loop_new\*(C'\fR. Yes, you have to call this on every allocated event loop
565after fork, and how you do this is entirely your own problem. 592after fork, and how you do this is entirely your own problem.
593.IP "unsigned int ev_loop_count (loop)" 4
594.IX Item "unsigned int ev_loop_count (loop)"
595Returns the count of loop iterations for the loop, which is identical to
596the number of times libev did poll for new events. It starts at \f(CW0\fR and
597happily wraps around with enough iterations.
598.Sp
599This value can sometimes be useful as a generation counter of sorts (it
600\&\*(L"ticks\*(R" the number of loop iterations), as it roughly corresponds with
601\&\f(CW\*(C`ev_prepare\*(C'\fR and \f(CW\*(C`ev_check\*(C'\fR calls.
566.IP "unsigned int ev_backend (loop)" 4 602.IP "unsigned int ev_backend (loop)" 4
567.IX Item "unsigned int ev_backend (loop)" 603.IX Item "unsigned int ev_backend (loop)"
568Returns one of the \f(CW\*(C`EVBACKEND_*\*(C'\fR flags indicating the event backend in 604Returns one of the \f(CW\*(C`EVBACKEND_*\*(C'\fR flags indicating the event backend in
569use. 605use.
570.IP "ev_tstamp ev_now (loop)" 4 606.IP "ev_tstamp ev_now (loop)" 4
… …
601libev watchers. However, a pair of \f(CW\*(C`ev_prepare\*(C'\fR/\f(CW\*(C`ev_check\*(C'\fR watchers is 637libev watchers. However, a pair of \f(CW\*(C`ev_prepare\*(C'\fR/\f(CW\*(C`ev_check\*(C'\fR watchers is
602usually a better approach for this kind of thing. 638usually a better approach for this kind of thing.
603.Sp 639.Sp
604Here are the gory details of what \f(CW\*(C`ev_loop\*(C'\fR does: 640Here are the gory details of what \f(CW\*(C`ev_loop\*(C'\fR does:
605.Sp 641.Sp
606.Vb 18 642.Vb 19
643\& - Before the first iteration, call any pending watchers.
607\& * If there are no active watchers (reference count is zero), return. 644\& * If there are no active watchers (reference count is zero), return.
608\& - Queue prepare watchers and then call all outstanding watchers. 645\& - Queue all prepare watchers and then call all outstanding watchers.
609\& - If we have been forked, recreate the kernel state. 646\& - If we have been forked, recreate the kernel state.
610\& - Update the kernel state with all outstanding changes. 647\& - Update the kernel state with all outstanding changes.
611\& - Update the "event loop time". 648\& - Update the "event loop time".
612\& - Calculate for how long to block. 649\& - Calculate for how long to block.
613\& - Block the process, waiting for any events. 650\& - Block the process, waiting for any events.
… …
856.IP "bool ev_is_pending (ev_TYPE *watcher)" 4 893.IP "bool ev_is_pending (ev_TYPE *watcher)" 4
857.IX Item "bool ev_is_pending (ev_TYPE *watcher)" 894.IX Item "bool ev_is_pending (ev_TYPE *watcher)"
858Returns a true value iff the watcher is pending, (i.e. it has outstanding 895Returns a true value iff the watcher is pending, (i.e. it has outstanding
859events but its callback has not yet been invoked). As long as a watcher 896events but its callback has not yet been invoked). As long as a watcher
860is pending (but not active) you must not call an init function on it (but 897is pending (but not active) you must not call an init function on it (but
861\&\f(CW\*(C`ev_TYPE_set\*(C'\fR is safe) and you must make sure the watcher is available to 898\&\f(CW\*(C`ev_TYPE_set\*(C'\fR is safe), you must not change its priority, and you must
862libev (e.g. you cnanot \f(CW\*(C`free ()\*(C'\fR it). 899make sure the watcher is available to libev (e.g. you cannot \f(CW\*(C`free ()\*(C'\fR
900it).
863.IP "callback ev_cb (ev_TYPE *watcher)" 4 901.IP "callback ev_cb (ev_TYPE *watcher)" 4
864.IX Item "callback ev_cb (ev_TYPE *watcher)" 902.IX Item "callback ev_cb (ev_TYPE *watcher)"
865Returns the callback currently set on the watcher. 903Returns the callback currently set on the watcher.
866.IP "ev_cb_set (ev_TYPE *watcher, callback)" 4 904.IP "ev_cb_set (ev_TYPE *watcher, callback)" 4
867.IX Item "ev_cb_set (ev_TYPE *watcher, callback)" 905.IX Item "ev_cb_set (ev_TYPE *watcher, callback)"
868Change the callback. You can change the callback at virtually any time 906Change the callback. You can change the callback at virtually any time
869(modulo threads). 907(modulo threads).
908.IP "ev_set_priority (ev_TYPE *watcher, priority)" 4
909.IX Item "ev_set_priority (ev_TYPE *watcher, priority)"
910.PD 0
911.IP "int ev_priority (ev_TYPE *watcher)" 4
912.IX Item "int ev_priority (ev_TYPE *watcher)"
913.PD
914Set and query the priority of the watcher. The priority is a small
915integer between \f(CW\*(C`EV_MAXPRI\*(C'\fR (default: \f(CW2\fR) and \f(CW\*(C`EV_MINPRI\*(C'\fR
916(default: \f(CW\*(C`\-2\*(C'\fR). Pending watchers with higher priority will be invoked
917before watchers with lower priority, but priority will not keep watchers
918from being executed (except for \f(CW\*(C`ev_idle\*(C'\fR watchers).
919.Sp
920This means that priorities are \fIonly\fR used for ordering callback
921invocation after new events have been received. This is useful, for
922example, to reduce latency after idling, or more often, to bind two
923watchers on the same event and make sure one is called first.
924.Sp
925If you need to suppress invocation when higher priority events are pending
926you need to look at \f(CW\*(C`ev_idle\*(C'\fR watchers, which provide this functionality.
927.Sp
928You \fImust not\fR change the priority of a watcher as long as it is active or
929pending.
930.Sp
931The default priority used by watchers when no priority has been set is
932always \f(CW0\fR, which is supposed to not be too high and not be too low :).
933.Sp
934Setting a priority outside the range of \f(CW\*(C`EV_MINPRI\*(C'\fR to \f(CW\*(C`EV_MAXPRI\*(C'\fR is
935fine, as long as you do not mind that the priority value you query might
936or might not have been adjusted to be within valid range.
937.IP "ev_invoke (loop, ev_TYPE *watcher, int revents)" 4
938.IX Item "ev_invoke (loop, ev_TYPE *watcher, int revents)"
939Invoke the \f(CW\*(C`watcher\*(C'\fR with the given \f(CW\*(C`loop\*(C'\fR and \f(CW\*(C`revents\*(C'\fR. Neither
940\&\f(CW\*(C`loop\*(C'\fR nor \f(CW\*(C`revents\*(C'\fR need to be valid as long as the watcher callback
941can deal with that fact.
942.IP "int ev_clear_pending (loop, ev_TYPE *watcher)" 4
943.IX Item "int ev_clear_pending (loop, ev_TYPE *watcher)"
944If the watcher is pending, this function returns clears its pending status
945and returns its \f(CW\*(C`revents\*(C'\fR bitset (as if its callback was invoked). If the
946watcher isn't pending it does nothing and returns \f(CW0\fR.
870.Sh "\s-1ASSOCIATING\s0 \s-1CUSTOM\s0 \s-1DATA\s0 \s-1WITH\s0 A \s-1WATCHER\s0" 947.Sh "\s-1ASSOCIATING\s0 \s-1CUSTOM\s0 \s-1DATA\s0 \s-1WITH\s0 A \s-1WATCHER\s0"
871.IX Subsection "ASSOCIATING CUSTOM DATA WITH A WATCHER" 948.IX Subsection "ASSOCIATING CUSTOM DATA WITH A WATCHER"
872Each watcher has, by default, a member \f(CW\*(C`void *data\*(C'\fR that you can change 949Each watcher has, by default, a member \f(CW\*(C`void *data\*(C'\fR that you can change
873and read at any time, libev will completely ignore it. This can be used 950and read at any time, libev will completely ignore it. This can be used
874to associate arbitrary data with your watcher. If you need more data and 951to associate arbitrary data with your watcher. If you need more data and
… …
985it is best to always use non-blocking I/O: An extra \f(CW\*(C`read\*(C'\fR(2) returning 1062it is best to always use non-blocking I/O: An extra \f(CW\*(C`read\*(C'\fR(2) returning
986\&\f(CW\*(C`EAGAIN\*(C'\fR is far preferable to a program hanging until some data arrives. 1063\&\f(CW\*(C`EAGAIN\*(C'\fR is far preferable to a program hanging until some data arrives.
987.PP 1064.PP
988If you cannot run the fd in non-blocking mode (for example you should not 1065If you cannot run the fd in non-blocking mode (for example you should not
989play around with an Xlib connection), then you have to seperately re-test 1066play around with an Xlib connection), then you have to seperately re-test
990wether a file descriptor is really ready with a known-to-be good interface 1067whether a file descriptor is really ready with a known-to-be good interface
991such as poll (fortunately in our Xlib example, Xlib already does this on 1068such as poll (fortunately in our Xlib example, Xlib already does this on
992its own, so its quite safe to use). 1069its own, so its quite safe to use).
993.IP "ev_io_init (ev_io *, callback, int fd, int events)" 4 1070.IP "ev_io_init (ev_io *, callback, int fd, int events)" 4
994.IX Item "ev_io_init (ev_io *, callback, int fd, int events)" 1071.IX Item "ev_io_init (ev_io *, callback, int fd, int events)"
995.PD 0 1072.PD 0
… …
1071.IP "ev_timer_again (loop)" 4 1148.IP "ev_timer_again (loop)" 4
1072.IX Item "ev_timer_again (loop)" 1149.IX Item "ev_timer_again (loop)"
1073This will act as if the timer timed out and restart it again if it is 1150This will act as if the timer timed out and restart it again if it is
1074repeating. The exact semantics are: 1151repeating. The exact semantics are:
1075.Sp 1152.Sp
1153If the timer is pending, its pending status is cleared.
1154.Sp
1076If the timer is started but nonrepeating, stop it. 1155If the timer is started but nonrepeating, stop it (as if it timed out).
1077.Sp 1156.Sp
1078If the timer is repeating, either start it if necessary (with the repeat 1157If the timer is repeating, either start it if necessary (with the
1079value), or reset the running timer to the repeat value. 1158\&\f(CW\*(C`repeat\*(C'\fR value), or reset the running timer to the \f(CW\*(C`repeat\*(C'\fR value.
1080.Sp 1159.Sp
1081This sounds a bit complicated, but here is a useful and typical 1160This sounds a bit complicated, but here is a useful and typical
1082example: Imagine you have a tcp connection and you want a so-called 1161example: Imagine you have a tcp connection and you want a so-called idle
1083idle timeout, that is, you want to be called when there have been, 1162timeout, that is, you want to be called when there have been, say, 60
1084say, 60 seconds of inactivity on the socket. The easiest way to do 1163seconds of inactivity on the socket. The easiest way to do this is to
1085this 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 1164configure an \f(CW\*(C`ev_timer\*(C'\fR with a \f(CW\*(C`repeat\*(C'\fR value of \f(CW60\fR and then call
1086\&\f(CW\*(C`ev_timer_again\*(C'\fR each time you successfully read or write some data. If 1165\&\f(CW\*(C`ev_timer_again\*(C'\fR each time you successfully read or write some data. If
1087you go into an idle state where you do not expect data to travel on the 1166you go into an idle state where you do not expect data to travel on the
1088socket, you can stop the timer, and again will automatically restart it if 1167socket, you can \f(CW\*(C`ev_timer_stop\*(C'\fR the timer, and \f(CW\*(C`ev_timer_again\*(C'\fR will
1089need be. 1168automatically restart it if need be.
1090.Sp 1169.Sp
1091You can also ignore the \f(CW\*(C`after\*(C'\fR value and \f(CW\*(C`ev_timer_start\*(C'\fR altogether 1170That means you can ignore the \f(CW\*(C`after\*(C'\fR value and \f(CW\*(C`ev_timer_start\*(C'\fR
1092and only ever use the \f(CW\*(C`repeat\*(C'\fR value: 1171altogether and only ever use the \f(CW\*(C`repeat\*(C'\fR value and \f(CW\*(C`ev_timer_again\*(C'\fR:
1093.Sp 1172.Sp
1094.Vb 8 1173.Vb 8
1095\& ev_timer_init (timer, callback, 0., 5.); 1174\& ev_timer_init (timer, callback, 0., 5.);
1096\& ev_timer_again (loop, timer); 1175\& ev_timer_again (loop, timer);
1097\& ... 1176\& ...
… …
1100\& ... 1179\& ...
1101\& timer->again = 10.; 1180\& timer->again = 10.;
1102\& ev_timer_again (loop, timer); 1181\& ev_timer_again (loop, timer);
1103.Ve 1182.Ve
1104.Sp 1183.Sp
1105This is more efficient then stopping/starting the timer eahc time you want 1184This is more slightly efficient then stopping/starting the timer each time
1106to modify its timeout value. 1185you want to modify its timeout value.
1107.IP "ev_tstamp repeat [read\-write]" 4 1186.IP "ev_tstamp repeat [read\-write]" 4
1108.IX Item "ev_tstamp repeat [read-write]" 1187.IX Item "ev_tstamp repeat [read-write]"
1109The current \f(CW\*(C`repeat\*(C'\fR value. Will be used each time the watcher times out 1188The current \f(CW\*(C`repeat\*(C'\fR value. Will be used each time the watcher times out
1110or \f(CW\*(C`ev_timer_again\*(C'\fR is called and determines the next timeout (if any), 1189or \f(CW\*(C`ev_timer_again\*(C'\fR is called and determines the next timeout (if any),
1111which is also when any modifications are taken into account. 1190which is also when any modifications are taken into account.
… …
1159but on wallclock time (absolute time). You can tell a periodic watcher 1238but on wallclock time (absolute time). You can tell a periodic watcher
1160to trigger \*(L"at\*(R" some specific point in time. For example, if you tell a 1239to trigger \*(L"at\*(R" some specific point in time. For example, if you tell a
1161periodic watcher to trigger in 10 seconds (by specifiying e.g. \f(CW\*(C`ev_now () 1240periodic watcher to trigger in 10 seconds (by specifiying e.g. \f(CW\*(C`ev_now ()
1162+ 10.\*(C'\fR) and then reset your system clock to the last year, then it will 1241+ 10.\*(C'\fR) and then reset your system clock to the last year, then it will
1163take a year to trigger the event (unlike an \f(CW\*(C`ev_timer\*(C'\fR, which would trigger 1242take a year to trigger the event (unlike an \f(CW\*(C`ev_timer\*(C'\fR, which would trigger
1164roughly 10 seconds later and of course not if you reset your system time 1243roughly 10 seconds later).
1165again).
1166.PP 1244.PP
1167They can also be used to implement vastly more complex timers, such as 1245They can also be used to implement vastly more complex timers, such as
1168triggering an event on eahc midnight, local time. 1246triggering an event on each midnight, local time or other, complicated,
1247rules.
1169.PP 1248.PP
1170As with timers, the callback is guarenteed to be invoked only when the 1249As with timers, the callback is guarenteed to be invoked only when the
1171time (\f(CW\*(C`at\*(C'\fR) has been passed, but if multiple periodic timers become ready 1250time (\f(CW\*(C`at\*(C'\fR) has been passed, but if multiple periodic timers become ready
1172during the same loop iteration then order of execution is undefined. 1251during the same loop iteration then order of execution is undefined.
1173.IP "ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)" 4 1252.IP "ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)" 4
… …
1177.IX Item "ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)" 1256.IX Item "ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)"
1178.PD 1257.PD
1179Lots of arguments, lets sort it out... There are basically three modes of 1258Lots of arguments, lets sort it out... There are basically three modes of
1180operation, and we will explain them from simplest to complex: 1259operation, and we will explain them from simplest to complex:
1181.RS 4 1260.RS 4
1182.IP "* absolute timer (interval = reschedule_cb = 0)" 4 1261.IP "* absolute timer (at = time, interval = reschedule_cb = 0)" 4
1183.IX Item "absolute timer (interval = reschedule_cb = 0)" 1262.IX Item "absolute timer (at = time, interval = reschedule_cb = 0)"
1184In this configuration the watcher triggers an event at the wallclock time 1263In this configuration the watcher triggers an event at the wallclock time
1185\&\f(CW\*(C`at\*(C'\fR and doesn't repeat. It will not adjust when a time jump occurs, 1264\&\f(CW\*(C`at\*(C'\fR and doesn't repeat. It will not adjust when a time jump occurs,
1186that is, if it is to be run at January 1st 2011 then it will run when the 1265that is, if it is to be run at January 1st 2011 then it will run when the
1187system time reaches or surpasses this time. 1266system time reaches or surpasses this time.
1188.IP "* non-repeating interval timer (interval > 0, reschedule_cb = 0)" 4 1267.IP "* non-repeating interval timer (at = offset, interval > 0, reschedule_cb = 0)" 4
1189.IX Item "non-repeating interval timer (interval > 0, reschedule_cb = 0)" 1268.IX Item "non-repeating interval timer (at = offset, interval > 0, reschedule_cb = 0)"
1190In this mode the watcher will always be scheduled to time out at the next 1269In this mode the watcher will always be scheduled to time out at the next
1191\&\f(CW\*(C`at + N * interval\*(C'\fR time (for some integer N) and then repeat, regardless 1270\&\f(CW\*(C`at + N * interval\*(C'\fR time (for some integer N, which can also be negative)
1192of any time jumps. 1271and then repeat, regardless of any time jumps.
1193.Sp 1272.Sp
1194This can be used to create timers that do not drift with respect to system 1273This can be used to create timers that do not drift with respect to system
1195time: 1274time:
1196.Sp 1275.Sp
1197.Vb 1 1276.Vb 1
… …
1204by 3600. 1283by 3600.
1205.Sp 1284.Sp
1206Another way to think about it (for the mathematically inclined) is that 1285Another way to think about it (for the mathematically inclined) is that
1207\&\f(CW\*(C`ev_periodic\*(C'\fR will try to run the callback in this mode at the next possible 1286\&\f(CW\*(C`ev_periodic\*(C'\fR will try to run the callback in this mode at the next possible
1208time where \f(CW\*(C`time = at (mod interval)\*(C'\fR, regardless of any time jumps. 1287time where \f(CW\*(C`time = at (mod interval)\*(C'\fR, regardless of any time jumps.
1288.Sp
1289For numerical stability it is preferable that the \f(CW\*(C`at\*(C'\fR value is near
1290\&\f(CW\*(C`ev_now ()\*(C'\fR (the current time), but there is no range requirement for
1291this value.
1209.IP "* manual reschedule mode (reschedule_cb = callback)" 4 1292.IP "* manual reschedule mode (at and interval ignored, reschedule_cb = callback)" 4
1210.IX Item "manual reschedule mode (reschedule_cb = callback)" 1293.IX Item "manual reschedule mode (at and interval ignored, reschedule_cb = callback)"
1211In this mode the values for \f(CW\*(C`interval\*(C'\fR and \f(CW\*(C`at\*(C'\fR are both being 1294In this mode the values for \f(CW\*(C`interval\*(C'\fR and \f(CW\*(C`at\*(C'\fR are both being
1212ignored. Instead, each time the periodic watcher gets scheduled, the 1295ignored. Instead, each time the periodic watcher gets scheduled, the
1213reschedule callback will be called with the watcher as first, and the 1296reschedule callback will be called with the watcher as first, and the
1214current time as second argument. 1297current time as second argument.
1215.Sp 1298.Sp
1216\&\s-1NOTE:\s0 \fIThis callback \s-1MUST\s0 \s-1NOT\s0 stop or destroy any periodic watcher, 1299\&\s-1NOTE:\s0 \fIThis callback \s-1MUST\s0 \s-1NOT\s0 stop or destroy any periodic watcher,
1217ever, or make any event loop modifications\fR. If you need to stop it, 1300ever, or make any event loop modifications\fR. If you need to stop it,
1218return \f(CW\*(C`now + 1e30\*(C'\fR (or so, fudge fudge) and stop it afterwards (e.g. by 1301return \f(CW\*(C`now + 1e30\*(C'\fR (or so, fudge fudge) and stop it afterwards (e.g. by
1219starting a prepare watcher). 1302starting an \f(CW\*(C`ev_prepare\*(C'\fR watcher, which is legal).
1220.Sp 1303.Sp
1221Its prototype is \f(CW\*(C`ev_tstamp (*reschedule_cb)(struct ev_periodic *w, 1304Its prototype is \f(CW\*(C`ev_tstamp (*reschedule_cb)(struct ev_periodic *w,
1222ev_tstamp now)\*(C'\fR, e.g.: 1305ev_tstamp now)\*(C'\fR, e.g.:
1223.Sp 1306.Sp
1224.Vb 4 1307.Vb 4
… …
1248.IX Item "ev_periodic_again (loop, ev_periodic *)" 1331.IX Item "ev_periodic_again (loop, ev_periodic *)"
1249Simply stops and restarts the periodic watcher again. This is only useful 1332Simply stops and restarts the periodic watcher again. This is only useful
1250when you changed some parameters or the reschedule callback would return 1333when you changed some parameters or the reschedule callback would return
1251a different time than the last time it was called (e.g. in a crond like 1334a different time than the last time it was called (e.g. in a crond like
1252program when the crontabs have changed). 1335program when the crontabs have changed).
1336.IP "ev_tstamp offset [read\-write]" 4
1337.IX Item "ev_tstamp offset [read-write]"
1338When repeating, this contains the offset value, otherwise this is the
1339absolute point in time (the \f(CW\*(C`at\*(C'\fR value passed to \f(CW\*(C`ev_periodic_set\*(C'\fR).
1340.Sp
1341Can be modified any time, but changes only take effect when the periodic
1342timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being called.
1253.IP "ev_tstamp interval [read\-write]" 4 1343.IP "ev_tstamp interval [read\-write]" 4
1254.IX Item "ev_tstamp interval [read-write]" 1344.IX Item "ev_tstamp interval [read-write]"
1255The current interval value. Can be modified any time, but changes only 1345The current interval value. Can be modified any time, but changes only
1256take effect when the periodic timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being 1346take effect when the periodic timer fires or \f(CW\*(C`ev_periodic_again\*(C'\fR is being
1257called. 1347called.
… …
1477\& ev_stat_start (loop, &passwd); 1567\& ev_stat_start (loop, &passwd);
1478.Ve 1568.Ve
1479.ie n .Sh """ev_idle"" \- when you've got nothing better to do..." 1569.ie n .Sh """ev_idle"" \- when you've got nothing better to do..."
1480.el .Sh "\f(CWev_idle\fP \- when you've got nothing better to do..." 1570.el .Sh "\f(CWev_idle\fP \- when you've got nothing better to do..."
1481.IX Subsection "ev_idle - when you've got nothing better to do..." 1571.IX Subsection "ev_idle - when you've got nothing better to do..."
1482Idle watchers trigger events when there are no other events are pending 1572Idle watchers trigger events when no other events of the same or higher
1483(prepare, check and other idle watchers do not count). That is, as long 1573priority are pending (prepare, check and other idle watchers do not
1484as your process is busy handling sockets or timeouts (or even signals, 1574count).
1485imagine) it will not be triggered. But when your process is idle all idle 1575.PP
1486watchers are being called again and again, once per event loop iteration \- 1576That is, as long as your process is busy handling sockets or timeouts
1577(or even signals, imagine) of the same or higher priority it will not be
1578triggered. But when your process is idle (or only lower-priority watchers
1579are pending), the idle watchers are being called once per event loop
1487until stopped, that is, or your process receives more events and becomes 1580iteration \- until stopped, that is, or your process receives more events
1488busy. 1581and becomes busy again with higher priority stuff.
1489.PP 1582.PP
1490The most noteworthy effect is that as long as any idle watchers are 1583The most noteworthy effect is that as long as any idle watchers are
1491active, the process will not block when waiting for new events. 1584active, the process will not block when waiting for new events.
1492.PP 1585.PP
1493Apart from keeping your process non-blocking (which is a useful 1586Apart from keeping your process non-blocking (which is a useful
… …
1556are ready to run (it's actually more complicated: it only runs coroutines 1649are ready to run (it's actually more complicated: it only runs coroutines
1557with priority higher than or equal to the event loop and one coroutine 1650with priority higher than or equal to the event loop and one coroutine
1558of lower priority, but only once, using idle watchers to keep the event 1651of lower priority, but only once, using idle watchers to keep the event
1559loop from blocking if lower-priority coroutines are active, thus mapping 1652loop from blocking if lower-priority coroutines are active, thus mapping
1560low-priority coroutines to idle/background tasks). 1653low-priority coroutines to idle/background tasks).
1654.PP
1655It is recommended to give \f(CW\*(C`ev_check\*(C'\fR watchers highest (\f(CW\*(C`EV_MAXPRI\*(C'\fR)
1656priority, to ensure that they are being run before any other watchers
1657after the poll. Also, \f(CW\*(C`ev_check\*(C'\fR watchers (and \f(CW\*(C`ev_prepare\*(C'\fR watchers,
1658too) should not activate (\*(L"feed\*(R") events into libev. While libev fully
1659supports this, they will be called before other \f(CW\*(C`ev_check\*(C'\fR watchers did
1660their job. As \f(CW\*(C`ev_check\*(C'\fR watchers are often used to embed other event
1661loops those other event loops might be in an unusable state until their
1662\&\f(CW\*(C`ev_check\*(C'\fR watcher ran (always remind yourself to coexist peacefully with
1663others).
1561.IP "ev_prepare_init (ev_prepare *, callback)" 4 1664.IP "ev_prepare_init (ev_prepare *, callback)" 4
1562.IX Item "ev_prepare_init (ev_prepare *, callback)" 1665.IX Item "ev_prepare_init (ev_prepare *, callback)"
1563.PD 0 1666.PD 0
1564.IP "ev_check_init (ev_check *, callback)" 4 1667.IP "ev_check_init (ev_check *, callback)" 4
1565.IX Item "ev_check_init (ev_check *, callback)" 1668.IX Item "ev_check_init (ev_check *, callback)"
1566.PD 1669.PD
1567Initialises and configures the prepare or check watcher \- they have no 1670Initialises and configures the prepare or check watcher \- they have no
1568parameters of any kind. There are \f(CW\*(C`ev_prepare_set\*(C'\fR and \f(CW\*(C`ev_check_set\*(C'\fR 1671parameters of any kind. There are \f(CW\*(C`ev_prepare_set\*(C'\fR and \f(CW\*(C`ev_check_set\*(C'\fR
1569macros, but using them is utterly, utterly and completely pointless. 1672macros, but using them is utterly, utterly and completely pointless.
1570.PP 1673.PP
1571Example: To include a library such as adns, you would add \s-1IO\s0 watchers 1674There are a number of principal ways to embed other event loops or modules
1572and a timeout watcher in a prepare handler, as required by libadns, and 1675into libev. Here are some ideas on how to include libadns into libev
1676(there is a Perl module named \f(CW\*(C`EV::ADNS\*(C'\fR that does this, which you could
1677use for an actually working example. Another Perl module named \f(CW\*(C`EV::Glib\*(C'\fR
1678embeds a Glib main context into libev, and finally, \f(CW\*(C`Glib::EV\*(C'\fR embeds \s-1EV\s0
1679into the Glib event loop).
1680.PP
1681Method 1: Add \s-1IO\s0 watchers and a timeout watcher in a prepare handler,
1573in a check watcher, destroy them and call into libadns. What follows is 1682and in a check watcher, destroy them and call into libadns. What follows
1574pseudo-code only of course: 1683is pseudo-code only of course. This requires you to either use a low
1684priority for the check watcher or use \f(CW\*(C`ev_clear_pending\*(C'\fR explicitly, as
1685the callbacks for the IO/timeout watchers might not have been called yet.
1575.PP 1686.PP
1576.Vb 2 1687.Vb 2
1577\& static ev_io iow [nfd]; 1688\& static ev_io iow [nfd];
1578\& static ev_timer tw; 1689\& static ev_timer tw;
1579.Ve 1690.Ve
1580.PP 1691.PP
1581.Vb 9 1692.Vb 4
1582\& static void 1693\& static void
1583\& io_cb (ev_loop *loop, ev_io *w, int revents) 1694\& io_cb (ev_loop *loop, ev_io *w, int revents)
1584\& { 1695\& {
1585\& // set the relevant poll flags
1586\& // could also call adns_processreadable etc. here
1587\& struct pollfd *fd = (struct pollfd *)w->data;
1588\& if (revents & EV_READ ) fd->revents |= fd->events & POLLIN;
1589\& if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT;
1590\& } 1696\& }
1591.Ve 1697.Ve
1592.PP 1698.PP
1593.Vb 7 1699.Vb 8
1594\& // create io watchers for each fd and a timer before blocking 1700\& // create io watchers for each fd and a timer before blocking
1595\& static void 1701\& static void
1596\& adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) 1702\& adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents)
1597\& { 1703\& {
1598\& int timeout = 3600000;truct pollfd fds [nfd]; 1704\& int timeout = 3600000;
1705\& struct pollfd fds [nfd];
1599\& // actual code will need to loop here and realloc etc. 1706\& // actual code will need to loop here and realloc etc.
1600\& adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ())); 1707\& adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ()));
1601.Ve 1708.Ve
1602.PP 1709.PP
1603.Vb 3 1710.Vb 3
… …
1605\& ev_timer_init (&tw, 0, timeout * 1e-3); 1712\& ev_timer_init (&tw, 0, timeout * 1e-3);
1606\& ev_timer_start (loop, &tw); 1713\& ev_timer_start (loop, &tw);
1607.Ve 1714.Ve
1608.PP 1715.PP
1609.Vb 6 1716.Vb 6
1610\& // create on ev_io per pollfd 1717\& // create one ev_io per pollfd
1611\& for (int i = 0; i < nfd; ++i) 1718\& for (int i = 0; i < nfd; ++i)
1612\& { 1719\& {
1613\& ev_io_init (iow + i, io_cb, fds [i].fd, 1720\& ev_io_init (iow + i, io_cb, fds [i].fd,
1614\& ((fds [i].events & POLLIN ? EV_READ : 0) 1721\& ((fds [i].events & POLLIN ? EV_READ : 0)
1615\& | (fds [i].events & POLLOUT ? EV_WRITE : 0))); 1722\& | (fds [i].events & POLLOUT ? EV_WRITE : 0)));
1616.Ve 1723.Ve
1617.PP 1724.PP
1618.Vb 5 1725.Vb 4
1619\& fds [i].revents = 0; 1726\& fds [i].revents = 0;
1620\& iow [i].data = fds + i;
1621\& ev_io_start (loop, iow + i); 1727\& ev_io_start (loop, iow + i);
1622\& } 1728\& }
1623\& } 1729\& }
1624.Ve 1730.Ve
1625.PP 1731.PP
… …
1629\& adns_check_cb (ev_loop *loop, ev_check *w, int revents) 1735\& adns_check_cb (ev_loop *loop, ev_check *w, int revents)
1630\& { 1736\& {
1631\& ev_timer_stop (loop, &tw); 1737\& ev_timer_stop (loop, &tw);
1632.Ve 1738.Ve
1633.PP 1739.PP
1634.Vb 2 1740.Vb 8
1635\& for (int i = 0; i < nfd; ++i) 1741\& for (int i = 0; i < nfd; ++i)
1742\& {
1743\& // set the relevant poll flags
1744\& // could also call adns_processreadable etc. here
1745\& struct pollfd *fd = fds + i;
1746\& int revents = ev_clear_pending (iow + i);
1747\& if (revents & EV_READ ) fd->revents |= fd->events & POLLIN;
1748\& if (revents & EV_WRITE) fd->revents |= fd->events & POLLOUT;
1749.Ve
1750.PP
1751.Vb 3
1752\& // now stop the watcher
1636\& ev_io_stop (loop, iow + i); 1753\& ev_io_stop (loop, iow + i);
1754\& }
1637.Ve 1755.Ve
1638.PP 1756.PP
1639.Vb 2 1757.Vb 2
1640\& adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop)); 1758\& adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop));
1759\& }
1760.Ve
1761.PP
1762Method 2: This would be just like method 1, but you run \f(CW\*(C`adns_afterpoll\*(C'\fR
1763in the prepare watcher and would dispose of the check watcher.
1764.PP
1765Method 3: If the module to be embedded supports explicit event
1766notification (adns does), you can also make use of the actual watcher
1767callbacks, and only destroy/create the watchers in the prepare watcher.
1768.PP
1769.Vb 5
1770\& static void
1771\& timer_cb (EV_P_ ev_timer *w, int revents)
1772\& {
1773\& adns_state ads = (adns_state)w->data;
1774\& update_now (EV_A);
1775.Ve
1776.PP
1777.Vb 2
1778\& adns_processtimeouts (ads, &tv_now);
1779\& }
1780.Ve
1781.PP
1782.Vb 5
1783\& static void
1784\& io_cb (EV_P_ ev_io *w, int revents)
1785\& {
1786\& adns_state ads = (adns_state)w->data;
1787\& update_now (EV_A);
1788.Ve
1789.PP
1790.Vb 3
1791\& if (revents & EV_READ ) adns_processreadable (ads, w->fd, &tv_now);
1792\& if (revents & EV_WRITE) adns_processwriteable (ads, w->fd, &tv_now);
1793\& }
1794.Ve
1795.PP
1796.Vb 1
1797\& // do not ever call adns_afterpoll
1798.Ve
1799.PP
1800Method 4: Do not use a prepare or check watcher because the module you
1801want to embed is too inflexible to support it. Instead, youc na override
1802their poll function. The drawback with this solution is that the main
1803loop is now no longer controllable by \s-1EV\s0. The \f(CW\*(C`Glib::EV\*(C'\fR module does
1804this.
1805.PP
1806.Vb 4
1807\& static gint
1808\& event_poll_func (GPollFD *fds, guint nfds, gint timeout)
1809\& {
1810\& int got_events = 0;
1811.Ve
1812.PP
1813.Vb 2
1814\& for (n = 0; n < nfds; ++n)
1815\& // create/start io watcher that sets the relevant bits in fds[n] and increment got_events
1816.Ve
1817.PP
1818.Vb 2
1819\& if (timeout >= 0)
1820\& // create/start timer
1821.Ve
1822.PP
1823.Vb 2
1824\& // poll
1825\& ev_loop (EV_A_ 0);
1826.Ve
1827.PP
1828.Vb 3
1829\& // stop timer again
1830\& if (timeout >= 0)
1831\& ev_timer_stop (EV_A_ &to);
1832.Ve
1833.PP
1834.Vb 3
1835\& // stop io watchers again - their callbacks should have set
1836\& for (n = 0; n < nfds; ++n)
1837\& ev_io_stop (EV_A_ iow [n]);
1838.Ve
1839.PP
1840.Vb 2
1841\& return got_events;
1641\& } 1842\& }
1642.Ve 1843.Ve
1643.ie n .Sh """ev_embed"" \- when one backend isn't enough..." 1844.ie n .Sh """ev_embed"" \- when one backend isn't enough..."
1644.el .Sh "\f(CWev_embed\fP \- when one backend isn't enough..." 1845.el .Sh "\f(CWev_embed\fP \- when one backend isn't enough..."
1645.IX Subsection "ev_embed - when one backend isn't enough..." 1846.IX Subsection "ev_embed - when one backend isn't enough..."
… …
1829.PP 2030.PP
1830.Vb 1 2031.Vb 1
1831\& #include <ev++.h> 2032\& #include <ev++.h>
1832.Ve 2033.Ve
1833.PP 2034.PP
1834(it is not installed by default). This automatically includes \fIev.h\fR 2035This automatically includes \fIev.h\fR and puts all of its definitions (many
1835and puts all of its definitions (many of them macros) into the global 2036of them macros) into the global namespace. All \*(C+ specific things are
1836namespace. All \*(C+ specific things are put into the \f(CW\*(C`ev\*(C'\fR namespace. 2037put into the \f(CW\*(C`ev\*(C'\fR namespace. It should support all the same embedding
2038options as \fIev.h\fR, most notably \f(CW\*(C`EV_MULTIPLICITY\*(C'\fR.
1837.PP 2039.PP
1838It should support all the same embedding options as \fIev.h\fR, most notably 2040Care has been taken to keep the overhead low. The only data member the \*(C+
1839\&\f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. 2041classes add (compared to plain C\-style watchers) is the event loop pointer
2042that the watcher is associated with (or no additional members at all if
2043you disable \f(CW\*(C`EV_MULTIPLICITY\*(C'\fR when embedding libev).
2044.PP
2045Currently, functions, and static and non-static member functions can be
2046used as callbacks. Other types should be easy to add as long as they only
2047need one additional pointer for context. If you need support for other
2048types of functors please contact the author (preferably after implementing
2049it).
1840.PP 2050.PP
1841Here is a list of things available in the \f(CW\*(C`ev\*(C'\fR namespace: 2051Here is a list of things available in the \f(CW\*(C`ev\*(C'\fR namespace:
1842.ie n .IP """ev::READ""\fR, \f(CW""ev::WRITE"" etc." 4 2052.ie n .IP """ev::READ""\fR, \f(CW""ev::WRITE"" etc." 4
1843.el .IP "\f(CWev::READ\fR, \f(CWev::WRITE\fR etc." 4 2053.el .IP "\f(CWev::READ\fR, \f(CWev::WRITE\fR etc." 4
1844.IX Item "ev::READ, ev::WRITE etc." 2054.IX Item "ev::READ, ev::WRITE etc."
… …
1856which is called \f(CW\*(C`ev::sig\*(C'\fR to avoid clashes with the \f(CW\*(C`signal\*(C'\fR macro 2066which is called \f(CW\*(C`ev::sig\*(C'\fR to avoid clashes with the \f(CW\*(C`signal\*(C'\fR macro
1857defines by many implementations. 2067defines by many implementations.
1858.Sp 2068.Sp
1859All of those classes have these methods: 2069All of those classes have these methods:
1860.RS 4 2070.RS 4
1861.IP "ev::TYPE::TYPE (object *, object::method *)" 4 2071.IP "ev::TYPE::TYPE ()" 4
1862.IX Item "ev::TYPE::TYPE (object *, object::method *)" 2072.IX Item "ev::TYPE::TYPE ()"
1863.PD 0 2073.PD 0
1864.IP "ev::TYPE::TYPE (object *, object::method *, struct ev_loop *)" 4 2074.IP "ev::TYPE::TYPE (struct ev_loop *)" 4
1865.IX Item "ev::TYPE::TYPE (object *, object::method *, struct ev_loop *)" 2075.IX Item "ev::TYPE::TYPE (struct ev_loop *)"
1866.IP "ev::TYPE::~TYPE" 4 2076.IP "ev::TYPE::~TYPE" 4
1867.IX Item "ev::TYPE::~TYPE" 2077.IX Item "ev::TYPE::~TYPE"
1868.PD 2078.PD
1869The constructor takes a pointer to an object and a method pointer to 2079The constructor (optionally) takes an event loop to associate the watcher
1870the event handler callback to call in this class. The constructor calls 2080with. If it is omitted, it will use \f(CW\*(C`EV_DEFAULT\*(C'\fR.
1871\&\f(CW\*(C`ev_init\*(C'\fR for you, which means you have to call the \f(CW\*(C`set\*(C'\fR method 2081.Sp
1872before starting it. If you do not specify a loop then the constructor 2082The constructor calls \f(CW\*(C`ev_init\*(C'\fR for you, which means you have to call the
1873automatically associates the default loop with this watcher. 2083\&\f(CW\*(C`set\*(C'\fR method before starting it.
2084.Sp
2085It will not set a callback, however: You have to call the templated \f(CW\*(C`set\*(C'\fR
2086method to set a callback before you can start the watcher.
2087.Sp
2088(The reason why you have to use a method is a limitation in \*(C+ which does
2089not allow explicit template arguments for constructors).
1874.Sp 2090.Sp
1875The destructor automatically stops the watcher if it is active. 2091The destructor automatically stops the watcher if it is active.
2092.IP "w\->set<class, &class::method> (object *)" 4
2093.IX Item "w->set<class, &class::method> (object *)"
2094This method sets the callback method to call. The method has to have a
2095signature of \f(CW\*(C`void (*)(ev_TYPE &, int)\*(C'\fR, it receives the watcher as
2096first argument and the \f(CW\*(C`revents\*(C'\fR as second. The object must be given as
2097parameter and is stored in the \f(CW\*(C`data\*(C'\fR member of the watcher.
2098.Sp
2099This method synthesizes efficient thunking code to call your method from
2100the C callback that libev requires. If your compiler can inline your
2101callback (i.e. it is visible to it at the place of the \f(CW\*(C`set\*(C'\fR call and
2102your compiler is good :), then the method will be fully inlined into the
2103thunking function, making it as fast as a direct C callback.
2104.Sp
2105Example: simple class declaration and watcher initialisation
2106.Sp
2107.Vb 4
2108\& struct myclass
2109\& {
2110\& void io_cb (ev::io &w, int revents) { }
2111\& }
2112.Ve
2113.Sp
2114.Vb 3
2115\& myclass obj;
2116\& ev::io iow;
2117\& iow.set <myclass, &myclass::io_cb> (&obj);
2118.Ve
2119.IP "w\->set<function> (void *data = 0)" 4
2120.IX Item "w->set<function> (void *data = 0)"
2121Also sets a callback, but uses a static method or plain function as
2122callback. The optional \f(CW\*(C`data\*(C'\fR argument will be stored in the watcher's
2123\&\f(CW\*(C`data\*(C'\fR member and is free for you to use.
2124.Sp
2125The prototype of the \f(CW\*(C`function\*(C'\fR must be \f(CW\*(C`void (*)(ev::TYPE &w, int)\*(C'\fR.
2126.Sp
2127See the method\-\f(CW\*(C`set\*(C'\fR above for more details.
2128.Sp
2129Example:
2130.Sp
2131.Vb 2
2132\& static void io_cb (ev::io &w, int revents) { }
2133\& iow.set <io_cb> ();
2134.Ve
1876.IP "w\->set (struct ev_loop *)" 4 2135.IP "w\->set (struct ev_loop *)" 4
1877.IX Item "w->set (struct ev_loop *)" 2136.IX Item "w->set (struct ev_loop *)"
1878Associates a different \f(CW\*(C`struct ev_loop\*(C'\fR with this watcher. You can only 2137Associates a different \f(CW\*(C`struct ev_loop\*(C'\fR with this watcher. You can only
1879do this when the watcher is inactive (and not pending either). 2138do this when the watcher is inactive (and not pending either).
1880.IP "w\->set ([args])" 4 2139.IP "w\->set ([args])" 4
1881.IX Item "w->set ([args])" 2140.IX Item "w->set ([args])"
1882Basically the same as \f(CW\*(C`ev_TYPE_set\*(C'\fR, with the same args. Must be 2141Basically the same as \f(CW\*(C`ev_TYPE_set\*(C'\fR, with the same args. Must be
1883called at least once. Unlike the C counterpart, an active watcher gets 2142called at least once. Unlike the C counterpart, an active watcher gets
1884automatically stopped and restarted. 2143automatically stopped and restarted when reconfiguring it with this
2144method.
1885.IP "w\->start ()" 4 2145.IP "w\->start ()" 4
1886.IX Item "w->start ()" 2146.IX Item "w->start ()"
1887Starts the watcher. Note that there is no \f(CW\*(C`loop\*(C'\fR argument as the 2147Starts the watcher. Note that there is no \f(CW\*(C`loop\*(C'\fR argument, as the
1888constructor already takes the loop. 2148constructor already stores the event loop.
1889.IP "w\->stop ()" 4 2149.IP "w\->stop ()" 4
1890.IX Item "w->stop ()" 2150.IX Item "w->stop ()"
1891Stops the watcher if it is active. Again, no \f(CW\*(C`loop\*(C'\fR argument. 2151Stops the watcher if it is active. Again, no \f(CW\*(C`loop\*(C'\fR argument.
1892.ie n .IP "w\->again () ""ev::timer""\fR, \f(CW""ev::periodic"" only" 4 2152.ie n .IP "w\->again () ""ev::timer""\fR, \f(CW""ev::periodic"" only" 4
1893.el .IP "w\->again () \f(CWev::timer\fR, \f(CWev::periodic\fR only" 4 2153.el .IP "w\->again () \f(CWev::timer\fR, \f(CWev::periodic\fR only" 4
… …
1919.Vb 2 2179.Vb 2
1920\& myclass (); 2180\& myclass ();
1921\& } 2181\& }
1922.Ve 2182.Ve
1923.PP 2183.PP
1924.Vb 6 2184.Vb 4
1925\& myclass::myclass (int fd) 2185\& myclass::myclass (int fd)
1926\& : io (this, &myclass::io_cb),
1927\& idle (this, &myclass::idle_cb)
1928\& { 2186\& {
2187\& io .set <myclass, &myclass::io_cb > (this);
2188\& idle.set <myclass, &myclass::idle_cb> (this);
2189.Ve
2190.PP
2191.Vb 2
1929\& io.start (fd, ev::READ); 2192\& io.start (fd, ev::READ);
1930\& } 2193\& }
1931.Ve 2194.Ve
1932.SH "MACRO MAGIC" 2195.SH "MACRO MAGIC"
1933.IX Header "MACRO MAGIC" 2196.IX Header "MACRO MAGIC"
1934Libev can be compiled with a variety of options, the most fundemantal is 2197Libev can be compiled with a variety of options, the most fundemantal is
1935\&\f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. This option determines wether (most) functions and 2198\&\f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. This option determines whether (most) functions and
1936callbacks have an initial \f(CW\*(C`struct ev_loop *\*(C'\fR argument. 2199callbacks have an initial \f(CW\*(C`struct ev_loop *\*(C'\fR argument.
1937.PP 2200.PP
1938To make it easier to write programs that cope with either variant, the 2201To make it easier to write programs that cope with either variant, the
1939following macros are defined: 2202following macros are defined:
1940.ie n .IP """EV_A""\fR, \f(CW""EV_A_""" 4 2203.ie n .IP """EV_A""\fR, \f(CW""EV_A_""" 4
… …
1975.el .IP "\f(CWEV_DEFAULT\fR, \f(CWEV_DEFAULT_\fR" 4 2238.el .IP "\f(CWEV_DEFAULT\fR, \f(CWEV_DEFAULT_\fR" 4
1976.IX Item "EV_DEFAULT, EV_DEFAULT_" 2239.IX Item "EV_DEFAULT, EV_DEFAULT_"
1977Similar to the other two macros, this gives you the value of the default 2240Similar to the other two macros, this gives you the value of the default
1978loop, if multiple loops are supported (\*(L"ev loop default\*(R"). 2241loop, if multiple loops are supported (\*(L"ev loop default\*(R").
1979.PP 2242.PP
1980Example: Declare and initialise a check watcher, working regardless of 2243Example: Declare and initialise a check watcher, utilising the above
1981wether multiple loops are supported or not. 2244macros so it will work regardless of whether multiple loops are supported
2245or not.
1982.PP 2246.PP
1983.Vb 5 2247.Vb 5
1984\& static void 2248\& static void
1985\& check_cb (EV_P_ ev_timer *w, int revents) 2249\& check_cb (EV_P_ ev_timer *w, int revents)
1986\& { 2250\& {
… …
2049.Vb 1 2313.Vb 1
2050\& ev_win32.c required on win32 platforms only 2314\& ev_win32.c required on win32 platforms only
2051.Ve 2315.Ve
2052.PP 2316.PP
2053.Vb 5 2317.Vb 5
2054\& ev_select.c only when select backend is enabled (which is by default) 2318\& ev_select.c only when select backend is enabled (which is enabled by default)
2055\& ev_poll.c only when poll backend is enabled (disabled by default) 2319\& ev_poll.c only when poll backend is enabled (disabled by default)
2056\& ev_epoll.c only when the epoll backend is enabled (disabled by default) 2320\& ev_epoll.c only when the epoll backend is enabled (disabled by default)
2057\& ev_kqueue.c only when the kqueue backend is enabled (disabled by default) 2321\& ev_kqueue.c only when the kqueue backend is enabled (disabled by default)
2058\& ev_port.c only when the solaris port backend is enabled (disabled by default) 2322\& ev_port.c only when the solaris port backend is enabled (disabled by default)
2059.Ve 2323.Ve
… …
2212If undefined or defined to \f(CW1\fR, then all event-loop-specific functions 2476If undefined or defined to \f(CW1\fR, then all event-loop-specific functions
2213will have the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument, and you can create 2477will have the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument, and you can create
2214additional independent event loops. Otherwise there will be no support 2478additional independent event loops. Otherwise there will be no support
2215for multiple event loops and there is no first event loop pointer 2479for multiple event loops and there is no first event loop pointer
2216argument. Instead, all functions act on the single default loop. 2480argument. Instead, all functions act on the single default loop.
2481.IP "\s-1EV_MINPRI\s0" 4
2482.IX Item "EV_MINPRI"
2483.PD 0
2484.IP "\s-1EV_MAXPRI\s0" 4
2485.IX Item "EV_MAXPRI"
2486.PD
2487The range of allowed priorities. \f(CW\*(C`EV_MINPRI\*(C'\fR must be smaller or equal to
2488\&\f(CW\*(C`EV_MAXPRI\*(C'\fR, but otherwise there are no non-obvious limitations. You can
2489provide for more priorities by overriding those symbols (usually defined
2490to be \f(CW\*(C`\-2\*(C'\fR and \f(CW2\fR, respectively).
2491.Sp
2492When doing priority-based operations, libev usually has to linearly search
2493all the priorities, so having many of them (hundreds) uses a lot of space
2494and time, so using the defaults of five priorities (\-2 .. +2) is usually
2495fine.
2496.Sp
2497If your embedding app does not need any priorities, defining these both to
2498\&\f(CW0\fR will save some memory and cpu.
2217.IP "\s-1EV_PERIODIC_ENABLE\s0" 4 2499.IP "\s-1EV_PERIODIC_ENABLE\s0" 4
2218.IX Item "EV_PERIODIC_ENABLE" 2500.IX Item "EV_PERIODIC_ENABLE"
2219If undefined or defined to be \f(CW1\fR, then periodic timers are supported. If 2501If undefined or defined to be \f(CW1\fR, then periodic timers are supported. If
2502defined to be \f(CW0\fR, then they are not. Disabling them saves a few kB of
2503code.
2504.IP "\s-1EV_IDLE_ENABLE\s0" 4
2505.IX Item "EV_IDLE_ENABLE"
2506If undefined or defined to be \f(CW1\fR, then idle watchers are supported. If
2220defined to be \f(CW0\fR, then they are not. Disabling them saves a few kB of 2507defined to be \f(CW0\fR, then they are not. Disabling them saves a few kB of
2221code. 2508code.
2222.IP "\s-1EV_EMBED_ENABLE\s0" 4 2509.IP "\s-1EV_EMBED_ENABLE\s0" 4
2223.IX Item "EV_EMBED_ENABLE" 2510.IX Item "EV_EMBED_ENABLE"
2224If undefined or defined to be \f(CW1\fR, then embed watchers are supported. If 2511If undefined or defined to be \f(CW1\fR, then embed watchers are supported. If
… …
2286interface) and \fI\s-1EV\s0.xs\fR (implementation) files. Only the \fI\s-1EV\s0.xs\fR file 2573interface) and \fI\s-1EV\s0.xs\fR (implementation) files. Only the \fI\s-1EV\s0.xs\fR file
2287will be compiled. It is pretty complex because it provides its own header 2574will be compiled. It is pretty complex because it provides its own header
2288file. 2575file.
2289.Sp 2576.Sp
2290The usage in rxvt-unicode is simpler. It has a \fIev_cpp.h\fR header file 2577The usage in rxvt-unicode is simpler. It has a \fIev_cpp.h\fR header file
2291that everybody includes and which overrides some autoconf choices: 2578that everybody includes and which overrides some configure choices:
2292.Sp 2579.Sp
2293.Vb 4 2580.Vb 9
2581\& #define EV_MINIMAL 1
2294\& #define EV_USE_POLL 0 2582\& #define EV_USE_POLL 0
2295\& #define EV_MULTIPLICITY 0 2583\& #define EV_MULTIPLICITY 0
2296\& #define EV_PERIODICS 0 2584\& #define EV_PERIODIC_ENABLE 0
2585\& #define EV_STAT_ENABLE 0
2586\& #define EV_FORK_ENABLE 0
2297\& #define EV_CONFIG_H <config.h> 2587\& #define EV_CONFIG_H <config.h>
2588\& #define EV_MINPRI 0
2589\& #define EV_MAXPRI 0
2298.Ve 2590.Ve
2299.Sp 2591.Sp
2300.Vb 1 2592.Vb 1
2301\& #include "ev++.h" 2593\& #include "ev++.h"
2302.Ve 2594.Ve
… …
2310.SH "COMPLEXITIES" 2602.SH "COMPLEXITIES"
2311.IX Header "COMPLEXITIES" 2603.IX Header "COMPLEXITIES"
2312In this section the complexities of (many of) the algorithms used inside 2604In this section the complexities of (many of) the algorithms used inside
2313libev will be explained. For complexity discussions about backends see the 2605libev will be explained. For complexity discussions about backends see the
2314documentation for \f(CW\*(C`ev_default_init\*(C'\fR. 2606documentation for \f(CW\*(C`ev_default_init\*(C'\fR.
2607.Sp
2608All of the following are about amortised time: If an array needs to be
2609extended, libev needs to realloc and move the whole array, but this
2610happens asymptotically never with higher number of elements, so O(1) might
2611mean it might do a lengthy realloc operation in rare cases, but on average
2612it is much faster and asymptotically approaches constant time.
2315.RS 4 2613.RS 4
2316.IP "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" 4 2614.IP "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" 4
2317.IX Item "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)" 2615.IX Item "Starting and stopping timer/periodic watchers: O(log skipped_other_timers)"
2318.PD 0 2616This means that, when you have a watcher that triggers in one hour and
2617there are 100 watchers that would trigger before that then inserting will
2618have to skip those 100 watchers.
2319.IP "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)" 4 2619.IP "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)" 4
2320.IX Item "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)" 2620.IX Item "Changing timer/periodic watchers (by autorepeat, again): O(log skipped_other_timers)"
2621That means that for changing a timer costs less than removing/adding them
2622as only the relative motion in the event queue has to be paid for.
2321.IP "Starting io/check/prepare/idle/signal/child watchers: O(1)" 4 2623.IP "Starting io/check/prepare/idle/signal/child watchers: O(1)" 4
2322.IX Item "Starting io/check/prepare/idle/signal/child watchers: O(1)" 2624.IX Item "Starting io/check/prepare/idle/signal/child watchers: O(1)"
2323.IP "Stopping check/prepare/idle watchers: O(1)" 4 2625These just add the watcher into an array or at the head of a list.
2324.IX Item "Stopping check/prepare/idle watchers: O(1)" 2626=item Stopping check/prepare/idle watchers: O(1)
2325.IP "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % \s-1EV_PID_HASHSIZE\s0))" 4 2627.IP "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % \s-1EV_PID_HASHSIZE\s0))" 4
2326.IX Item "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))" 2628.IX Item "Stopping an io/signal/child watcher: O(number_of_watchers_for_this_(fd/signal/pid % EV_PID_HASHSIZE))"
2629These watchers are stored in lists then need to be walked to find the
2630correct watcher to remove. The lists are usually short (you don't usually
2631have many watchers waiting for the same fd or signal).
2327.IP "Finding the next timer per loop iteration: O(1)" 4 2632.IP "Finding the next timer per loop iteration: O(1)" 4
2328.IX Item "Finding the next timer per loop iteration: O(1)" 2633.IX Item "Finding the next timer per loop iteration: O(1)"
2634.PD 0
2329.IP "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)" 4 2635.IP "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)" 4
2330.IX Item "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)" 2636.IX Item "Each change on a file descriptor per loop iteration: O(number_of_watchers_for_this_fd)"
2637.PD
2638A change means an I/O watcher gets started or stopped, which requires
2639libev to recalculate its status (and possibly tell the kernel).
2331.IP "Activating one watcher: O(1)" 4 2640.IP "Activating one watcher: O(1)" 4
2332.IX Item "Activating one watcher: O(1)" 2641.IX Item "Activating one watcher: O(1)"
2642.PD 0
2643.IP "Priority handling: O(number_of_priorities)" 4
2644.IX Item "Priority handling: O(number_of_priorities)"
2645.PD
2646Priorities are implemented by allocating some space for each
2647priority. When doing priority-based operations, libev usually has to
2648linearly search all the priorities.
2333.RE 2649.RE
2334.RS 4 2650.RS 4
2335.PD
2336.SH "AUTHOR" 2651.SH "AUTHOR"
2337.IX Header "AUTHOR" 2652.IX Header "AUTHOR"
2338Marc Lehmann <libev@schmorp.de>. 2653Marc Lehmann <libev@schmorp.de>.

Diff Legend

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