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

Comparing libev/ev.html (file contents):
Revision 1.2 by root, Mon Nov 12 08:02:54 2007 UTC vs.
Revision 1.31 by root, Fri Nov 23 04:36:03 2007 UTC

… …
4<head> 4<head>
5 <title>libev</title> 5 <title>libev</title>
6 <meta name="description" content="Pod documentation for libev" /> 6 <meta name="description" content="Pod documentation for libev" />
7 <meta name="inputfile" content="&lt;standard input&gt;" /> 7 <meta name="inputfile" content="&lt;standard input&gt;" />
8 <meta name="outputfile" content="&lt;standard output&gt;" /> 8 <meta name="outputfile" content="&lt;standard output&gt;" />
9 <meta name="created" content="Mon Nov 12 09:02:48 2007" /> 9 <meta name="created" content="Fri Nov 23 05:35:59 2007" />
10 <meta name="generator" content="Pod::Xhtml 1.57" /> 10 <meta name="generator" content="Pod::Xhtml 1.57" />
11<link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head> 11<link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head>
12<body> 12<body>
13<div class="pod"> 13<div class="pod">
14<!-- INDEX START --> 14<!-- INDEX START -->
… …
17<ul><li><a href="#NAME">NAME</a></li> 17<ul><li><a href="#NAME">NAME</a></li>
18<li><a href="#SYNOPSIS">SYNOPSIS</a></li> 18<li><a href="#SYNOPSIS">SYNOPSIS</a></li>
19<li><a href="#DESCRIPTION">DESCRIPTION</a></li> 19<li><a href="#DESCRIPTION">DESCRIPTION</a></li>
20<li><a href="#FEATURES">FEATURES</a></li> 20<li><a href="#FEATURES">FEATURES</a></li>
21<li><a href="#CONVENTIONS">CONVENTIONS</a></li> 21<li><a href="#CONVENTIONS">CONVENTIONS</a></li>
22<li><a href="#TIME_REPRESENTATION">TIME REPRESENTATION</a></li>
22<li><a href="#TIME_AND_OTHER_GLOBAL_FUNCTIONS">TIME AND OTHER GLOBAL FUNCTIONS</a></li> 23<li><a href="#GLOBAL_FUNCTIONS">GLOBAL FUNCTIONS</a></li>
23<li><a href="#FUNCTIONS_CONTROLLING_THE_EVENT_LOOP">FUNCTIONS CONTROLLING THE EVENT LOOP</a></li> 24<li><a href="#FUNCTIONS_CONTROLLING_THE_EVENT_LOOP">FUNCTIONS CONTROLLING THE EVENT LOOP</a></li>
24<li><a href="#ANATOMY_OF_A_WATCHER">ANATOMY OF A WATCHER</a> 25<li><a href="#ANATOMY_OF_A_WATCHER">ANATOMY OF A WATCHER</a>
25<ul><li><a href="#ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH">ASSOCIATING CUSTOM DATA WITH A WATCHER</a></li> 26<ul><li><a href="#ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH">ASSOCIATING CUSTOM DATA WITH A WATCHER</a></li>
26</ul> 27</ul>
27</li> 28</li>
28<li><a href="#WATCHER_TYPES">WATCHER TYPES</a> 29<li><a href="#WATCHER_TYPES">WATCHER TYPES</a>
29<ul><li><a href="#struct_ev_io_is_my_file_descriptor_r">struct ev_io - is my file descriptor readable or writable</a></li> 30<ul><li><a href="#code_ev_io_code_is_this_file_descrip"><code>ev_io</code> - is this file descriptor readable or writable</a></li>
30<li><a href="#struct_ev_timer_relative_and_optiona">struct ev_timer - relative and optionally recurring timeouts</a></li> 31<li><a href="#code_ev_timer_code_relative_and_opti"><code>ev_timer</code> - relative and optionally recurring timeouts</a></li>
31<li><a href="#ev_periodic">ev_periodic</a></li> 32<li><a href="#code_ev_periodic_code_to_cron_or_not"><code>ev_periodic</code> - to cron or not to cron</a></li>
32<li><a href="#ev_signal_signal_me_when_a_signal_ge">ev_signal - signal me when a signal gets signalled</a></li> 33<li><a href="#code_ev_signal_code_signal_me_when_a"><code>ev_signal</code> - signal me when a signal gets signalled</a></li>
33<li><a href="#ev_child_wait_for_pid_status_changes">ev_child - wait for pid status changes</a></li> 34<li><a href="#code_ev_child_code_wait_for_pid_stat"><code>ev_child</code> - wait for pid status changes</a></li>
34<li><a href="#ev_idle_when_you_ve_got_nothing_bett">ev_idle - when you've got nothing better to do</a></li> 35<li><a href="#code_ev_idle_code_when_you_ve_got_no"><code>ev_idle</code> - when you've got nothing better to do</a></li>
35<li><a href="#prepare_and_check_your_hooks_into_th">prepare and check - your hooks into the event loop</a></li> 36<li><a href="#code_ev_prepare_code_and_code_ev_che"><code>ev_prepare</code> and <code>ev_check</code> - customise your event loop</a></li>
36</ul> 37</ul>
37</li> 38</li>
38<li><a href="#OTHER_FUNCTIONS">OTHER FUNCTIONS</a></li> 39<li><a href="#OTHER_FUNCTIONS">OTHER FUNCTIONS</a></li>
40<li><a href="#LIBEVENT_EMULATION">LIBEVENT EMULATION</a></li>
41<li><a href="#C_SUPPORT">C++ SUPPORT</a></li>
39<li><a href="#AUTHOR">AUTHOR</a> 42<li><a href="#AUTHOR">AUTHOR</a>
40</li> 43</li>
41</ul><hr /> 44</ul><hr />
42<!-- INDEX END --> 45<!-- INDEX END -->
43 46
… …
55</div> 58</div>
56<h1 id="DESCRIPTION">DESCRIPTION</h1><p><a href="#TOP" class="toplink">Top</a></p> 59<h1 id="DESCRIPTION">DESCRIPTION</h1><p><a href="#TOP" class="toplink">Top</a></p>
57<div id="DESCRIPTION_CONTENT"> 60<div id="DESCRIPTION_CONTENT">
58<p>Libev is an event loop: you register interest in certain events (such as a 61<p>Libev is an event loop: you register interest in certain events (such as a
59file descriptor being readable or a timeout occuring), and it will manage 62file descriptor being readable or a timeout occuring), and it will manage
60these event sources and provide your program events.</p> 63these event sources and provide your program with events.</p>
61<p>To do this, it must take more or less complete control over your process 64<p>To do this, it must take more or less complete control over your process
62(or thread) by executing the <i>event loop</i> handler, and will then 65(or thread) by executing the <i>event loop</i> handler, and will then
63communicate events via a callback mechanism.</p> 66communicate events via a callback mechanism.</p>
64<p>You register interest in certain events by registering so-called <i>event 67<p>You register interest in certain events by registering so-called <i>event
65watchers</i>, which are relatively small C structures you initialise with the 68watchers</i>, which are relatively small C structures you initialise with the
… …
71<div id="FEATURES_CONTENT"> 74<div id="FEATURES_CONTENT">
72<p>Libev supports select, poll, the linux-specific epoll and the bsd-specific 75<p>Libev supports select, poll, the linux-specific epoll and the bsd-specific
73kqueue mechanisms for file descriptor events, relative timers, absolute 76kqueue mechanisms for file descriptor events, relative timers, absolute
74timers with customised rescheduling, signal events, process status change 77timers with customised rescheduling, signal events, process status change
75events (related to SIGCHLD), and event watchers dealing with the event 78events (related to SIGCHLD), and event watchers dealing with the event
76loop mechanism itself (idle, prepare and check watchers).</p> 79loop mechanism itself (idle, prepare and check watchers). It also is quite
80fast (see this <a href="http://libev.schmorp.de/bench.html">benchmark</a> comparing
81it to libevent for example).</p>
77 82
78</div> 83</div>
79<h1 id="CONVENTIONS">CONVENTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p> 84<h1 id="CONVENTIONS">CONVENTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p>
80<div id="CONVENTIONS_CONTENT"> 85<div id="CONVENTIONS_CONTENT">
81<p>Libev is very configurable. In this manual the default configuration 86<p>Libev is very configurable. In this manual the default configuration
82will be described, which supports multiple event loops. For more info 87will be described, which supports multiple event loops. For more info
83about various configuraiton options please have a look at the file 88about various configuration options please have a look at the file
84<cite>README.embed</cite> in the libev distribution. If libev was configured without 89<cite>README.embed</cite> in the libev distribution. If libev was configured without
85support for multiple event loops, then all functions taking an initial 90support for multiple event loops, then all functions taking an initial
86argument of name <code>loop</code> (which is always of type <code>struct ev_loop *</code>) 91argument of name <code>loop</code> (which is always of type <code>struct ev_loop *</code>)
87will not have this argument.</p> 92will not have this argument.</p>
88 93
89</div> 94</div>
90<h1 id="TIME_AND_OTHER_GLOBAL_FUNCTIONS">TIME AND OTHER GLOBAL FUNCTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p> 95<h1 id="TIME_REPRESENTATION">TIME REPRESENTATION</h1><p><a href="#TOP" class="toplink">Top</a></p>
91<div id="TIME_AND_OTHER_GLOBAL_FUNCTIONS_CONT"> 96<div id="TIME_REPRESENTATION_CONTENT">
92<p>Libev represents time as a single floating point number, representing the 97<p>Libev represents time as a single floating point number, representing the
93(fractional) number of seconds since the (POSIX) epoch (somewhere near 98(fractional) number of seconds since the (POSIX) epoch (somewhere near
94the beginning of 1970, details are complicated, don't ask). This type is 99the beginning of 1970, details are complicated, don't ask). This type is
95called <code>ev_tstamp</code>, which is what you should use too. It usually aliases 100called <code>ev_tstamp</code>, which is what you should use too. It usually aliases
96to the double type in C.</p> 101to the double type in C.</p>
102
103</div>
104<h1 id="GLOBAL_FUNCTIONS">GLOBAL FUNCTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p>
105<div id="GLOBAL_FUNCTIONS_CONTENT">
106<p>These functions can be called anytime, even before initialising the
107library in any way.</p>
97<dl> 108<dl>
98 <dt>ev_tstamp ev_time ()</dt> 109 <dt>ev_tstamp ev_time ()</dt>
99 <dd> 110 <dd>
100 <p>Returns the current time as libev would use it.</p> 111 <p>Returns the current time as libev would use it. Please note that the
112<code>ev_now</code> function is usually faster and also often returns the timestamp
113you actually want to know.</p>
101 </dd> 114 </dd>
102 <dt>int ev_version_major ()</dt> 115 <dt>int ev_version_major ()</dt>
103 <dt>int ev_version_minor ()</dt> 116 <dt>int ev_version_minor ()</dt>
104 <dd> 117 <dd>
105 <p>You can find out the major and minor version numbers of the library 118 <p>You can find out the major and minor version numbers of the library
106you linked against by calling the functions <code>ev_version_major</code> and 119you linked against by calling the functions <code>ev_version_major</code> and
107<code>ev_version_minor</code>. If you want, you can compare against the global 120<code>ev_version_minor</code>. If you want, you can compare against the global
108symbols <code>EV_VERSION_MAJOR</code> and <code>EV_VERSION_MINOR</code>, which specify the 121symbols <code>EV_VERSION_MAJOR</code> and <code>EV_VERSION_MINOR</code>, which specify the
109version of the library your program was compiled against.</p> 122version of the library your program was compiled against.</p>
110 <p>Usually, its a good idea to terminate if the major versions mismatch, 123 <p>Usually, it's a good idea to terminate if the major versions mismatch,
111as this indicates an incompatible change. Minor versions are usually 124as this indicates an incompatible change. Minor versions are usually
112compatible to older versions, so a larger minor version alone is usually 125compatible to older versions, so a larger minor version alone is usually
113not a problem.</p> 126not a problem.</p>
114 </dd> 127 </dd>
115 <dt>ev_set_allocator (void *(*cb)(void *ptr, long size))</dt> 128 <dt>ev_set_allocator (void *(*cb)(void *ptr, long size))</dt>
116 <dd> 129 <dd>
117 <p>Sets the allocation function to use (the prototype is similar to the 130 <p>Sets the allocation function to use (the prototype is similar to the
118realloc function). It is used to allocate and free memory (no surprises 131realloc C function, the semantics are identical). It is used to allocate
119here). If it returns zero when memory needs to be allocated, the library 132and free memory (no surprises here). If it returns zero when memory
120might abort or take some potentially destructive action. The default is 133needs to be allocated, the library might abort or take some potentially
121your system realloc function.</p> 134destructive action. The default is your system realloc function.</p>
122 <p>You could override this function in high-availability programs to, say, 135 <p>You could override this function in high-availability programs to, say,
123free some memory if it cannot allocate memory, to use a special allocator, 136free some memory if it cannot allocate memory, to use a special allocator,
124or even to sleep a while and retry until some memory is available.</p> 137or even to sleep a while and retry until some memory is available.</p>
125 </dd> 138 </dd>
126 <dt>ev_set_syserr_cb (void (*cb)(const char *msg));</dt> 139 <dt>ev_set_syserr_cb (void (*cb)(const char *msg));</dt>
127 <dd> 140 <dd>
128 <p>Set the callback function to call on a retryable syscall error (such 141 <p>Set the callback function to call on a retryable syscall error (such
129as failed select, poll, epoll_wait). The message is a printable string 142as failed select, poll, epoll_wait). The message is a printable string
130indicating the system call or subsystem causing the problem. If this 143indicating the system call or subsystem causing the problem. If this
131callback is set, then libev will expect it to remedy the sitution, no 144callback is set, then libev will expect it to remedy the sitution, no
132matter what, when it returns. That is, libev will geenrally retry the 145matter what, when it returns. That is, libev will generally retry the
133requested operation, or, if the condition doesn't go away, do bad stuff 146requested operation, or, if the condition doesn't go away, do bad stuff
134(such as abort).</p> 147(such as abort).</p>
135 </dd> 148 </dd>
136</dl> 149</dl>
137 150
… …
140<div id="FUNCTIONS_CONTROLLING_THE_EVENT_LOOP-2"> 153<div id="FUNCTIONS_CONTROLLING_THE_EVENT_LOOP-2">
141<p>An event loop is described by a <code>struct ev_loop *</code>. The library knows two 154<p>An event loop is described by a <code>struct ev_loop *</code>. The library knows two
142types of such loops, the <i>default</i> loop, which supports signals and child 155types of such loops, the <i>default</i> loop, which supports signals and child
143events, and dynamically created loops which do not.</p> 156events, and dynamically created loops which do not.</p>
144<p>If you use threads, a common model is to run the default event loop 157<p>If you use threads, a common model is to run the default event loop
145in your main thread (or in a separate thrad) and for each thread you 158in your main thread (or in a separate thread) and for each thread you
146create, you also create another event loop. Libev itself does no lockign 159create, you also create another event loop. Libev itself does no locking
147whatsoever, so if you mix calls to different event loops, make sure you 160whatsoever, so if you mix calls to the same event loop in different
148lock (this is usually a bad idea, though, even if done right).</p> 161threads, make sure you lock (this is usually a bad idea, though, even if
162done correctly, because it's hideous and inefficient).</p>
149<dl> 163<dl>
150 <dt>struct ev_loop *ev_default_loop (unsigned int flags)</dt> 164 <dt>struct ev_loop *ev_default_loop (unsigned int flags)</dt>
151 <dd> 165 <dd>
152 <p>This will initialise the default event loop if it hasn't been initialised 166 <p>This will initialise the default event loop if it hasn't been initialised
153yet and return it. If the default loop could not be initialised, returns 167yet and return it. If the default loop could not be initialised, returns
154false. If it already was initialised it simply returns it (and ignores the 168false. If it already was initialised it simply returns it (and ignores the
155flags).</p> 169flags).</p>
156 <p>If you don't know what event loop to use, use the one returned from this 170 <p>If you don't know what event loop to use, use the one returned from this
157function.</p> 171function.</p>
158 <p>The flags argument can be used to specify special behaviour or specific 172 <p>The flags argument can be used to specify special behaviour or specific
159backends to use, and is usually specified as 0 (or EVFLAG_AUTO)</p> 173backends to use, and is usually specified as 0 (or EVFLAG_AUTO).</p>
160 <p>It supports the following flags:</p> 174 <p>It supports the following flags:</p>
161 <p> 175 <p>
162 <dl> 176 <dl>
163 <dt>EVFLAG_AUTO</dt> 177 <dt><code>EVFLAG_AUTO</code></dt>
164 <dd> 178 <dd>
165 <p>The default flags value. Use this if you have no clue (its the right 179 <p>The default flags value. Use this if you have no clue (it's the right
166thing, believe me).</p> 180thing, believe me).</p>
167 </dd> 181 </dd>
168 <dt>EVFLAG_NOENV</dt> 182 <dt><code>EVFLAG_NOENV</code></dt>
169 <dd>
170 <p>If this flag bit is ored into the flag value then libev will <i>not</i> look
171at the environment variable <code>LIBEV_FLAGS</code>. Otherwise (the default), this
172environment variable will override the flags completely. This is useful
173to try out specific backends to tets their performance, or to work around
174bugs.</p>
175 </dd> 183 <dd>
176 <dt>EVMETHOD_SELECT portable select backend</dt> 184 <p>If this flag bit is ored into the flag value (or the program runs setuid
177 <dt>EVMETHOD_POLL poll backend (everywhere except windows)</dt> 185or setgid) then libev will <i>not</i> look at the environment variable
178 <dt>EVMETHOD_EPOLL linux only</dt> 186<code>LIBEV_FLAGS</code>. Otherwise (the default), this environment variable will
179 <dt>EVMETHOD_KQUEUE some bsds only</dt> 187override the flags completely if it is found in the environment. This is
180 <dt>EVMETHOD_DEVPOLL solaris 8 only</dt> 188useful to try out specific backends to test their performance, or to work
181 <dt>EVMETHOD_PORT solaris 10 only</dt> 189around bugs.</p>
182 <dd> 190 </dd>
183 <p>If one or more of these are ored into the flags value, then only these 191 <dt><code>EVMETHOD_SELECT</code> (value 1, portable select backend)</dt>
184backends will be tried (in the reverse order as given here). If one are 192 <dd>
185specified, any backend will do.</p> 193 <p>This is your standard select(2) backend. Not <i>completely</i> standard, as
194libev tries to roll its own fd_set with no limits on the number of fds,
195but if that fails, expect a fairly low limit on the number of fds when
196using this backend. It doesn't scale too well (O(highest_fd)), but its usually
197the fastest backend for a low number of fds.</p>
198 </dd>
199 <dt><code>EVMETHOD_POLL</code> (value 2, poll backend, available everywhere except on windows)</dt>
200 <dd>
201 <p>And this is your standard poll(2) backend. It's more complicated than
202select, but handles sparse fds better and has no artificial limit on the
203number of fds you can use (except it will slow down considerably with a
204lot of inactive fds). It scales similarly to select, i.e. O(total_fds).</p>
205 </dd>
206 <dt><code>EVMETHOD_EPOLL</code> (value 4, Linux)</dt>
207 <dd>
208 <p>For few fds, this backend is a bit little slower than poll and select,
209but it scales phenomenally better. While poll and select usually scale like
210O(total_fds) where n is the total number of fds (or the highest fd), epoll scales
211either O(1) or O(active_fds).</p>
212 <p>While stopping and starting an I/O watcher in the same iteration will
213result in some caching, there is still a syscall per such incident
214(because the fd could point to a different file description now), so its
215best to avoid that. Also, dup()ed file descriptors might not work very
216well if you register events for both fds.</p>
217 </dd>
218 <dt><code>EVMETHOD_KQUEUE</code> (value 8, most BSD clones)</dt>
219 <dd>
220 <p>Kqueue deserves special mention, as at the time of this writing, it
221was broken on all BSDs except NetBSD (usually it doesn't work with
222anything but sockets and pipes, except on Darwin, where of course its
223completely useless). For this reason its not being &quot;autodetected&quot; unless
224you explicitly specify the flags (i.e. you don't use EVFLAG_AUTO).</p>
225 <p>It scales in the same way as the epoll backend, but the interface to the
226kernel is more efficient (which says nothing about its actual speed, of
227course). While starting and stopping an I/O watcher does not cause an
228extra syscall as with epoll, it still adds up to four event changes per
229incident, so its best to avoid that.</p>
230 </dd>
231 <dt><code>EVMETHOD_DEVPOLL</code> (value 16, Solaris 8)</dt>
232 <dd>
233 <p>This is not implemented yet (and might never be).</p>
234 </dd>
235 <dt><code>EVMETHOD_PORT</code> (value 32, Solaris 10)</dt>
236 <dd>
237 <p>This uses the Solaris 10 port mechanism. As with everything on Solaris,
238it's really slow, but it still scales very well (O(active_fds)).</p>
239 </dd>
240 <dt><code>EVMETHOD_ALL</code></dt>
241 <dd>
242 <p>Try all backends (even potentially broken ones that wouldn't be tried
243with <code>EVFLAG_AUTO</code>). Since this is a mask, you can do stuff such as
244<code>EVMETHOD_ALL &amp; ~EVMETHOD_KQUEUE</code>.</p>
186 </dd> 245 </dd>
187 </dl> 246 </dl>
188 </p> 247 </p>
248 <p>If one or more of these are ored into the flags value, then only these
249backends will be tried (in the reverse order as given here). If none are
250specified, most compiled-in backend will be tried, usually in reverse
251order of their flag values :)</p>
189 </dd> 252 </dd>
190 <dt>struct ev_loop *ev_loop_new (unsigned int flags)</dt> 253 <dt>struct ev_loop *ev_loop_new (unsigned int flags)</dt>
191 <dd> 254 <dd>
192 <p>Similar to <code>ev_default_loop</code>, but always creates a new event loop that is 255 <p>Similar to <code>ev_default_loop</code>, but always creates a new event loop that is
193always distinct from the default loop. Unlike the default loop, it cannot 256always distinct from the default loop. Unlike the default loop, it cannot
… …
196 </dd> 259 </dd>
197 <dt>ev_default_destroy ()</dt> 260 <dt>ev_default_destroy ()</dt>
198 <dd> 261 <dd>
199 <p>Destroys the default loop again (frees all memory and kernel state 262 <p>Destroys the default loop again (frees all memory and kernel state
200etc.). This stops all registered event watchers (by not touching them in 263etc.). This stops all registered event watchers (by not touching them in
201any way whatsoever, although you cnanot rely on this :).</p> 264any way whatsoever, although you cannot rely on this :).</p>
202 </dd> 265 </dd>
203 <dt>ev_loop_destroy (loop)</dt> 266 <dt>ev_loop_destroy (loop)</dt>
204 <dd> 267 <dd>
205 <p>Like <code>ev_default_destroy</code>, but destroys an event loop created by an 268 <p>Like <code>ev_default_destroy</code>, but destroys an event loop created by an
206earlier call to <code>ev_loop_new</code>.</p> 269earlier call to <code>ev_loop_new</code>.</p>
… …
209 <dd> 272 <dd>
210 <p>This function reinitialises the kernel state for backends that have 273 <p>This function reinitialises the kernel state for backends that have
211one. Despite the name, you can call it anytime, but it makes most sense 274one. Despite the name, you can call it anytime, but it makes most sense
212after forking, in either the parent or child process (or both, but that 275after forking, in either the parent or child process (or both, but that
213again makes little sense).</p> 276again makes little sense).</p>
214 <p>You <i>must</i> call this function after forking if and only if you want to 277 <p>You <i>must</i> call this function in the child process after forking if and
215use the event library in both processes. If you just fork+exec, you don't 278only if you want to use the event library in both processes. If you just
216have to call it.</p> 279fork+exec, you don't have to call it.</p>
217 <p>The function itself is quite fast and its usually not a problem to call 280 <p>The function itself is quite fast and it's usually not a problem to call
218it just in case after a fork. To make this easy, the function will fit in 281it just in case after a fork. To make this easy, the function will fit in
219quite nicely into a call to <code>pthread_atfork</code>:</p> 282quite nicely into a call to <code>pthread_atfork</code>:</p>
220<pre> pthread_atfork (0, 0, ev_default_fork); 283<pre> pthread_atfork (0, 0, ev_default_fork);
221 284
222</pre> 285</pre>
… …
230 <dt>unsigned int ev_method (loop)</dt> 293 <dt>unsigned int ev_method (loop)</dt>
231 <dd> 294 <dd>
232 <p>Returns one of the <code>EVMETHOD_*</code> flags indicating the event backend in 295 <p>Returns one of the <code>EVMETHOD_*</code> flags indicating the event backend in
233use.</p> 296use.</p>
234 </dd> 297 </dd>
235 <dt>ev_tstamp = ev_now (loop)</dt> 298 <dt>ev_tstamp ev_now (loop)</dt>
236 <dd> 299 <dd>
237 <p>Returns the current &quot;event loop time&quot;, which is the time the event loop 300 <p>Returns the current &quot;event loop time&quot;, which is the time the event loop
238got events and started processing them. This timestamp does not change 301got events and started processing them. This timestamp does not change
239as long as callbacks are being processed, and this is also the base time 302as long as callbacks are being processed, and this is also the base time
240used for relative timers. You can treat it as the timestamp of the event 303used for relative timers. You can treat it as the timestamp of the event
… …
247events.</p> 310events.</p>
248 <p>If the flags argument is specified as 0, it will not return until either 311 <p>If the flags argument is specified as 0, it will not return until either
249no event watchers are active anymore or <code>ev_unloop</code> was called.</p> 312no event watchers are active anymore or <code>ev_unloop</code> was called.</p>
250 <p>A flags value of <code>EVLOOP_NONBLOCK</code> will look for new events, will handle 313 <p>A flags value of <code>EVLOOP_NONBLOCK</code> will look for new events, will handle
251those events and any outstanding ones, but will not block your process in 314those events and any outstanding ones, but will not block your process in
252case there are no events.</p> 315case there are no events and will return after one iteration of the loop.</p>
253 <p>A flags value of <code>EVLOOP_ONESHOT</code> will look for new events (waiting if 316 <p>A flags value of <code>EVLOOP_ONESHOT</code> will look for new events (waiting if
254neccessary) and will handle those and any outstanding ones. It will block 317neccessary) and will handle those and any outstanding ones. It will block
255your process until at least one new event arrives.</p> 318your process until at least one new event arrives, and will return after
319one iteration of the loop.</p>
256 <p>This flags value could be used to implement alternative looping 320 <p>This flags value could be used to implement alternative looping
257constructs, but the <code>prepare</code> and <code>check</code> watchers provide a better and 321constructs, but the <code>prepare</code> and <code>check</code> watchers provide a better and
258more generic mechanism.</p> 322more generic mechanism.</p>
323 <p>Here are the gory details of what ev_loop does:</p>
324<pre> 1. If there are no active watchers (reference count is zero), return.
325 2. Queue and immediately call all prepare watchers.
326 3. If we have been forked, recreate the kernel state.
327 4. Update the kernel state with all outstanding changes.
328 5. Update the &quot;event loop time&quot;.
329 6. Calculate for how long to block.
330 7. Block the process, waiting for events.
331 8. Update the &quot;event loop time&quot; and do time jump handling.
332 9. Queue all outstanding timers.
333 10. Queue all outstanding periodics.
334 11. If no events are pending now, queue all idle watchers.
335 12. Queue all check watchers.
336 13. Call all queued watchers in reverse order (i.e. check watchers first).
337 14. If ev_unloop has been called or EVLOOP_ONESHOT or EVLOOP_NONBLOCK
338 was used, return, otherwise continue with step #1.
339
340</pre>
259 </dd> 341 </dd>
260 <dt>ev_unloop (loop, how)</dt> 342 <dt>ev_unloop (loop, how)</dt>
261 <dd> 343 <dd>
262 <p>Can be used to make a call to <code>ev_loop</code> return early. The <code>how</code> argument 344 <p>Can be used to make a call to <code>ev_loop</code> return early (but only after it
345has processed all outstanding events). The <code>how</code> argument must be either
263must be either <code>EVUNLOOP_ONCE</code>, which will make the innermost <code>ev_loop</code> 346<code>EVUNLOOP_ONE</code>, which will make the innermost <code>ev_loop</code> call return, or
264call return, or <code>EVUNLOOP_ALL</code>, which will make all nested <code>ev_loop</code> 347<code>EVUNLOOP_ALL</code>, which will make all nested <code>ev_loop</code> calls return.</p>
265calls return.</p>
266 </dd> 348 </dd>
267 <dt>ev_ref (loop)</dt> 349 <dt>ev_ref (loop)</dt>
268 <dt>ev_unref (loop)</dt> 350 <dt>ev_unref (loop)</dt>
269 <dd> 351 <dd>
270 <p>Ref/unref can be used to add or remove a refcount on the event loop: Every 352 <p>Ref/unref can be used to add or remove a reference count on the event
271watcher keeps one reference. If you have a long-runing watcher you never 353loop: Every watcher keeps one reference, and as long as the reference
272unregister that should not keep ev_loop from running, ev_unref() after 354count is nonzero, <code>ev_loop</code> will not return on its own. If you have
273starting, and ev_ref() before stopping it. Libev itself uses this for 355a watcher you never unregister that should not keep <code>ev_loop</code> from
274example for its internal signal pipe: It is not visible to you as a user 356returning, ev_unref() after starting, and ev_ref() before stopping it. For
275and should not keep <code>ev_loop</code> from exiting if the work is done. It is 357example, libev itself uses this for its internal signal pipe: It is not
276also an excellent way to do this for generic recurring timers or from 358visible to the libev user and should not keep <code>ev_loop</code> from exiting if
277within third-party libraries. Just remember to unref after start and ref 359no event watchers registered by it are active. It is also an excellent
278before stop.</p> 360way to do this for generic recurring timers or from within third-party
361libraries. Just remember to <i>unref after start</i> and <i>ref before stop</i>.</p>
279 </dd> 362 </dd>
280</dl> 363</dl>
281 364
282</div> 365</div>
283<h1 id="ANATOMY_OF_A_WATCHER">ANATOMY OF A WATCHER</h1><p><a href="#TOP" class="toplink">Top</a></p> 366<h1 id="ANATOMY_OF_A_WATCHER">ANATOMY OF A WATCHER</h1><p><a href="#TOP" class="toplink">Top</a></p>
284<div id="ANATOMY_OF_A_WATCHER_CONTENT"> 367<div id="ANATOMY_OF_A_WATCHER_CONTENT">
285<p>A watcher is a structure that you create and register to record your 368<p>A watcher is a structure that you create and register to record your
286interest in some event. For instance, if you want to wait for STDIN to 369interest in some event. For instance, if you want to wait for STDIN to
287become readable, you would create an ev_io watcher for that:</p> 370become readable, you would create an <code>ev_io</code> watcher for that:</p>
288<pre> static void my_cb (struct ev_loop *loop, struct ev_io *w, int revents) 371<pre> static void my_cb (struct ev_loop *loop, struct ev_io *w, int revents)
289 { 372 {
290 ev_io_stop (w); 373 ev_io_stop (w);
291 ev_unloop (loop, EVUNLOOP_ALL); 374 ev_unloop (loop, EVUNLOOP_ALL);
292 } 375 }
… …
316*)</code>), and you can stop watching for events at any time by calling the 399*)</code>), and you can stop watching for events at any time by calling the
317corresponding stop function (<code>ev_&lt;type&gt;_stop (loop, watcher *)</code>.</p> 400corresponding stop function (<code>ev_&lt;type&gt;_stop (loop, watcher *)</code>.</p>
318<p>As long as your watcher is active (has been started but not stopped) you 401<p>As long as your watcher is active (has been started but not stopped) you
319must not touch the values stored in it. Most specifically you must never 402must not touch the values stored in it. Most specifically you must never
320reinitialise it or call its set method.</p> 403reinitialise it or call its set method.</p>
321<p>You cna check wether an event is active by calling the <code>ev_is_active 404<p>You can check whether an event is active by calling the <code>ev_is_active
322(watcher *)</code> macro. To see wether an event is outstanding (but the 405(watcher *)</code> macro. To see whether an event is outstanding (but the
323callback for it has not been called yet) you cna use the <code>ev_is_pending 406callback for it has not been called yet) you can use the <code>ev_is_pending
324(watcher *)</code> macro.</p> 407(watcher *)</code> macro.</p>
325<p>Each and every callback receives the event loop pointer as first, the 408<p>Each and every callback receives the event loop pointer as first, the
326registered watcher structure as second, and a bitset of received events as 409registered watcher structure as second, and a bitset of received events as
327third argument.</p> 410third argument.</p>
328<p>The rceeived events usually include a single bit per event type received 411<p>The received events usually include a single bit per event type received
329(you can receive multiple events at the same time). The possible bit masks 412(you can receive multiple events at the same time). The possible bit masks
330are:</p> 413are:</p>
331<dl> 414<dl>
332 <dt>EV_READ</dt> 415 <dt><code>EV_READ</code></dt>
333 <dt>EV_WRITE</dt> 416 <dt><code>EV_WRITE</code></dt>
334 <dd> 417 <dd>
335 <p>The file descriptor in the ev_io watcher has become readable and/or 418 <p>The file descriptor in the <code>ev_io</code> watcher has become readable and/or
336writable.</p> 419writable.</p>
337 </dd> 420 </dd>
338 <dt>EV_TIMEOUT</dt> 421 <dt><code>EV_TIMEOUT</code></dt>
339 <dd>
340 <p>The ev_timer watcher has timed out.</p>
341 </dd> 422 <dd>
342 <dt>EV_PERIODIC</dt> 423 <p>The <code>ev_timer</code> watcher has timed out.</p>
343 <dd> 424 </dd>
344 <p>The ev_periodic watcher has timed out.</p> 425 <dt><code>EV_PERIODIC</code></dt>
345 </dd> 426 <dd>
346 <dt>EV_SIGNAL</dt> 427 <p>The <code>ev_periodic</code> watcher has timed out.</p>
347 <dd> 428 </dd>
429 <dt><code>EV_SIGNAL</code></dt>
430 <dd>
348 <p>The signal specified in the ev_signal watcher has been received by a thread.</p> 431 <p>The signal specified in the <code>ev_signal</code> watcher has been received by a thread.</p>
349 </dd>
350 <dt>EV_CHILD</dt>
351 <dd> 432 </dd>
433 <dt><code>EV_CHILD</code></dt>
434 <dd>
352 <p>The pid specified in the ev_child watcher has received a status change.</p> 435 <p>The pid specified in the <code>ev_child</code> watcher has received a status change.</p>
353 </dd>
354 <dt>EV_IDLE</dt>
355 <dd> 436 </dd>
437 <dt><code>EV_IDLE</code></dt>
438 <dd>
356 <p>The ev_idle watcher has determined that you have nothing better to do.</p> 439 <p>The <code>ev_idle</code> watcher has determined that you have nothing better to do.</p>
357 </dd>
358 <dt>EV_PREPARE</dt>
359 <dt>EV_CHECK</dt>
360 <dd> 440 </dd>
441 <dt><code>EV_PREPARE</code></dt>
442 <dt><code>EV_CHECK</code></dt>
443 <dd>
361 <p>All ev_prepare watchers are invoked just <i>before</i> <code>ev_loop</code> starts 444 <p>All <code>ev_prepare</code> watchers are invoked just <i>before</i> <code>ev_loop</code> starts
362to gather new events, and all ev_check watchers are invoked just after 445to gather new events, and all <code>ev_check</code> watchers are invoked just after
363<code>ev_loop</code> has gathered them, but before it invokes any callbacks for any 446<code>ev_loop</code> has gathered them, but before it invokes any callbacks for any
364received events. Callbacks of both watcher types can start and stop as 447received events. Callbacks of both watcher types can start and stop as
365many watchers as they want, and all of them will be taken into account 448many watchers as they want, and all of them will be taken into account
366(for example, a ev_prepare watcher might start an idle watcher to keep 449(for example, a <code>ev_prepare</code> watcher might start an idle watcher to keep
367<code>ev_loop</code> from blocking).</p> 450<code>ev_loop</code> from blocking).</p>
368 </dd> 451 </dd>
369 <dt>EV_ERROR</dt> 452 <dt><code>EV_ERROR</code></dt>
370 <dd> 453 <dd>
371 <p>An unspecified error has occured, the watcher has been stopped. This might 454 <p>An unspecified error has occured, the watcher has been stopped. This might
372happen because the watcher could not be properly started because libev 455happen because the watcher could not be properly started because libev
373ran out of memory, a file descriptor was found to be closed or any other 456ran out of memory, a file descriptor was found to be closed or any other
374problem. You best act on it by reporting the problem and somehow coping 457problem. You best act on it by reporting the problem and somehow coping
… …
383 466
384</div> 467</div>
385<h2 id="ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH">ASSOCIATING CUSTOM DATA WITH A WATCHER</h2> 468<h2 id="ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH">ASSOCIATING CUSTOM DATA WITH A WATCHER</h2>
386<div id="ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH-2"> 469<div id="ASSOCIATING_CUSTOM_DATA_WITH_A_WATCH-2">
387<p>Each watcher has, by default, a member <code>void *data</code> that you can change 470<p>Each watcher has, by default, a member <code>void *data</code> that you can change
388and read at any time, libev will completely ignore it. This cna be used 471and read at any time, libev will completely ignore it. This can be used
389to associate arbitrary data with your watcher. If you need more data and 472to associate arbitrary data with your watcher. If you need more data and
390don't want to allocate memory and store a pointer to it in that data 473don't want to allocate memory and store a pointer to it in that data
391member, you can also &quot;subclass&quot; the watcher type and provide your own 474member, you can also &quot;subclass&quot; the watcher type and provide your own
392data:</p> 475data:</p>
393<pre> struct my_io 476<pre> struct my_io
… …
420<div id="WATCHER_TYPES_CONTENT"> 503<div id="WATCHER_TYPES_CONTENT">
421<p>This section describes each watcher in detail, but will not repeat 504<p>This section describes each watcher in detail, but will not repeat
422information given in the last section.</p> 505information given in the last section.</p>
423 506
424</div> 507</div>
425<h2 id="struct_ev_io_is_my_file_descriptor_r">struct ev_io - is my file descriptor readable or writable</h2> 508<h2 id="code_ev_io_code_is_this_file_descrip"><code>ev_io</code> - is this file descriptor readable or writable</h2>
426<div id="struct_ev_io_is_my_file_descriptor_r-2"> 509<div id="code_ev_io_code_is_this_file_descrip-2">
427<p>I/O watchers check wether a file descriptor is readable or writable 510<p>I/O watchers check whether a file descriptor is readable or writable
428in each iteration of the event loop (This behaviour is called 511in each iteration of the event loop (This behaviour is called
429level-triggering because you keep receiving events as long as the 512level-triggering because you keep receiving events as long as the
430condition persists. Remember you cna stop the watcher if you don't want to 513condition persists. Remember you can stop the watcher if you don't want to
431act on the event and neither want to receive future events).</p> 514act on the event and neither want to receive future events).</p>
515<p>In general you can register as many read and/or write event watchers per
516fd as you want (as long as you don't confuse yourself). Setting all file
517descriptors to non-blocking mode is also usually a good idea (but not
518required if you know what you are doing).</p>
519<p>You have to be careful with dup'ed file descriptors, though. Some backends
520(the linux epoll backend is a notable example) cannot handle dup'ed file
521descriptors correctly if you register interest in two or more fds pointing
522to the same underlying file/socket etc. description (that is, they share
523the same underlying &quot;file open&quot;).</p>
524<p>If you must do this, then force the use of a known-to-be-good backend
525(at the time of this writing, this includes only EVMETHOD_SELECT and
526EVMETHOD_POLL).</p>
432<dl> 527<dl>
433 <dt>ev_io_init (ev_io *, callback, int fd, int events)</dt> 528 <dt>ev_io_init (ev_io *, callback, int fd, int events)</dt>
434 <dt>ev_io_set (ev_io *, int fd, int events)</dt> 529 <dt>ev_io_set (ev_io *, int fd, int events)</dt>
435 <dd> 530 <dd>
436 <p>Configures an ev_io watcher. The fd is the file descriptor to rceeive 531 <p>Configures an <code>ev_io</code> watcher. The fd is the file descriptor to rceeive
437events for and events is either <code>EV_READ</code>, <code>EV_WRITE</code> or <code>EV_READ | 532events for and events is either <code>EV_READ</code>, <code>EV_WRITE</code> or <code>EV_READ |
438EV_WRITE</code> to receive the given events.</p> 533EV_WRITE</code> to receive the given events.</p>
439 </dd> 534 </dd>
440</dl> 535</dl>
441 536
442</div> 537</div>
443<h2 id="struct_ev_timer_relative_and_optiona">struct ev_timer - relative and optionally recurring timeouts</h2> 538<h2 id="code_ev_timer_code_relative_and_opti"><code>ev_timer</code> - relative and optionally recurring timeouts</h2>
444<div id="struct_ev_timer_relative_and_optiona-2"> 539<div id="code_ev_timer_code_relative_and_opti-2">
445<p>Timer watchers are simple relative timers that generate an event after a 540<p>Timer watchers are simple relative timers that generate an event after a
446given time, and optionally repeating in regular intervals after that.</p> 541given time, and optionally repeating in regular intervals after that.</p>
447<p>The timers are based on real time, that is, if you register an event that 542<p>The timers are based on real time, that is, if you register an event that
448times out after an hour and youreset your system clock to last years 543times out after an hour and you reset your system clock to last years
449time, it will still time out after (roughly) and hour. &quot;Roughly&quot; because 544time, it will still time out after (roughly) and hour. &quot;Roughly&quot; because
450detecting time jumps is hard, and soem inaccuracies are unavoidable (the 545detecting time jumps is hard, and some inaccuracies are unavoidable (the
451monotonic clock option helps a lot here).</p> 546monotonic clock option helps a lot here).</p>
547<p>The relative timeouts are calculated relative to the <code>ev_now ()</code>
548time. This is usually the right thing as this timestamp refers to the time
549of the event triggering whatever timeout you are modifying/starting. If
550you suspect event processing to be delayed and you <i>need</i> to base the timeout
551on the current time, use something like this to adjust for this:</p>
552<pre> ev_timer_set (&amp;timer, after + ev_now () - ev_time (), 0.);
553
554</pre>
555<p>The callback is guarenteed to be invoked only when its timeout has passed,
556but if multiple timers become ready during the same loop iteration then
557order of execution is undefined.</p>
452<dl> 558<dl>
453 <dt>ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)</dt> 559 <dt>ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)</dt>
454 <dt>ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)</dt> 560 <dt>ev_timer_set (ev_timer *, ev_tstamp after, ev_tstamp repeat)</dt>
455 <dd> 561 <dd>
456 <p>Configure the timer to trigger after <code>after</code> seconds. If <code>repeat</code> is 562 <p>Configure the timer to trigger after <code>after</code> seconds. If <code>repeat</code> is
… …
458timer will automatically be configured to trigger again <code>repeat</code> seconds 564timer will automatically be configured to trigger again <code>repeat</code> seconds
459later, again, and again, until stopped manually.</p> 565later, again, and again, until stopped manually.</p>
460 <p>The timer itself will do a best-effort at avoiding drift, that is, if you 566 <p>The timer itself will do a best-effort at avoiding drift, that is, if you
461configure a timer to trigger every 10 seconds, then it will trigger at 567configure a timer to trigger every 10 seconds, then it will trigger at
462exactly 10 second intervals. If, however, your program cannot keep up with 568exactly 10 second intervals. If, however, your program cannot keep up with
463the timer (ecause it takes longer than those 10 seconds to do stuff) the 569the timer (because it takes longer than those 10 seconds to do stuff) the
464timer will not fire more than once per event loop iteration.</p> 570timer will not fire more than once per event loop iteration.</p>
465 </dd> 571 </dd>
466 <dt>ev_timer_again (loop)</dt> 572 <dt>ev_timer_again (loop)</dt>
467 <dd> 573 <dd>
468 <p>This will act as if the timer timed out and restart it again if it is 574 <p>This will act as if the timer timed out and restart it again if it is
… …
472value), or reset the running timer to the repeat value.</p> 578value), or reset the running timer to the repeat value.</p>
473 <p>This sounds a bit complicated, but here is a useful and typical 579 <p>This sounds a bit complicated, but here is a useful and typical
474example: Imagine you have a tcp connection and you want a so-called idle 580example: Imagine you have a tcp connection and you want a so-called idle
475timeout, that is, you want to be called when there have been, say, 60 581timeout, that is, you want to be called when there have been, say, 60
476seconds of inactivity on the socket. The easiest way to do this is to 582seconds of inactivity on the socket. The easiest way to do this is to
477configure an ev_timer with after=repeat=60 and calling ev_timer_again each 583configure an <code>ev_timer</code> with after=repeat=60 and calling ev_timer_again each
478time you successfully read or write some data. If you go into an idle 584time you successfully read or write some data. If you go into an idle
479state where you do not expect data to travel on the socket, you can stop 585state where you do not expect data to travel on the socket, you can stop
480the timer, and again will automatically restart it if need be.</p> 586the timer, and again will automatically restart it if need be.</p>
481 </dd> 587 </dd>
482</dl> 588</dl>
483 589
484</div> 590</div>
485<h2 id="ev_periodic">ev_periodic</h2> 591<h2 id="code_ev_periodic_code_to_cron_or_not"><code>ev_periodic</code> - to cron or not to cron</h2>
486<div id="ev_periodic_CONTENT"> 592<div id="code_ev_periodic_code_to_cron_or_not-2">
487<p>Periodic watchers are also timers of a kind, but they are very versatile 593<p>Periodic watchers are also timers of a kind, but they are very versatile
488(and unfortunately a bit complex).</p> 594(and unfortunately a bit complex).</p>
489<p>Unlike ev_timer's, they are not based on real time (or relative time) 595<p>Unlike <code>ev_timer</code>'s, they are not based on real time (or relative time)
490but on wallclock time (absolute time). You can tell a periodic watcher 596but on wallclock time (absolute time). You can tell a periodic watcher
491to trigger &quot;at&quot; some specific point in time. For example, if you tell a 597to trigger &quot;at&quot; some specific point in time. For example, if you tell a
492periodic watcher to trigger in 10 seconds (by specifiying e.g. c&lt;ev_now () 598periodic watcher to trigger in 10 seconds (by specifiying e.g. c&lt;ev_now ()
493+ 10.&gt;) and then reset your system clock to the last year, then it will 599+ 10.&gt;) and then reset your system clock to the last year, then it will
494take a year to trigger the event (unlike an ev_timer, which would trigger 600take a year to trigger the event (unlike an <code>ev_timer</code>, which would trigger
495roughly 10 seconds later and of course not if you reset your system time 601roughly 10 seconds later and of course not if you reset your system time
496again).</p> 602again).</p>
497<p>They can also be used to implement vastly more complex timers, such as 603<p>They can also be used to implement vastly more complex timers, such as
498triggering an event on eahc midnight, local time.</p> 604triggering an event on eahc midnight, local time.</p>
605<p>As with timers, the callback is guarenteed to be invoked only when the
606time (<code>at</code>) has been passed, but if multiple periodic timers become ready
607during the same loop iteration then order of execution is undefined.</p>
499<dl> 608<dl>
500 <dt>ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)</dt> 609 <dt>ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)</dt>
501 <dt>ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)</dt> 610 <dt>ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)</dt>
502 <dd> 611 <dd>
503 <p>Lots of arguments, lets sort it out... There are basically three modes of 612 <p>Lots of arguments, lets sort it out... There are basically three modes of
504operation, and we will explain them from simplest to complex:</p> 613operation, and we will explain them from simplest to complex:</p>
505
506
507
508
509 <p> 614 <p>
510 <dl> 615 <dl>
511 <dt>* absolute timer (interval = reschedule_cb = 0)</dt> 616 <dt>* absolute timer (interval = reschedule_cb = 0)</dt>
512 <dd> 617 <dd>
513 <p>In this configuration the watcher triggers an event at the wallclock time 618 <p>In this configuration the watcher triggers an event at the wallclock time
… …
525<pre> ev_periodic_set (&amp;periodic, 0., 3600., 0); 630<pre> ev_periodic_set (&amp;periodic, 0., 3600., 0);
526 631
527</pre> 632</pre>
528 <p>This doesn't mean there will always be 3600 seconds in between triggers, 633 <p>This doesn't mean there will always be 3600 seconds in between triggers,
529but only that the the callback will be called when the system time shows a 634but only that the the callback will be called when the system time shows a
530full hour (UTC), or more correct, when the system time is evenly divisible 635full hour (UTC), or more correctly, when the system time is evenly divisible
531by 3600.</p> 636by 3600.</p>
532 <p>Another way to think about it (for the mathematically inclined) is that 637 <p>Another way to think about it (for the mathematically inclined) is that
533ev_periodic will try to run the callback in this mode at the next possible 638<code>ev_periodic</code> will try to run the callback in this mode at the next possible
534time where <code>time = at (mod interval)</code>, regardless of any time jumps.</p> 639time where <code>time = at (mod interval)</code>, regardless of any time jumps.</p>
535 </dd> 640 </dd>
536 <dt>* manual reschedule mode (reschedule_cb = callback)</dt> 641 <dt>* manual reschedule mode (reschedule_cb = callback)</dt>
537 <dd> 642 <dd>
538 <p>In this mode the values for <code>interval</code> and <code>at</code> are both being 643 <p>In this mode the values for <code>interval</code> and <code>at</code> are both being
539ignored. Instead, each time the periodic watcher gets scheduled, the 644ignored. Instead, each time the periodic watcher gets scheduled, the
540reschedule callback will be called with the watcher as first, and the 645reschedule callback will be called with the watcher as first, and the
541current time as second argument.</p> 646current time as second argument.</p>
542 <p>NOTE: <i>This callback MUST NOT stop or destroy the periodic or any other 647 <p>NOTE: <i>This callback MUST NOT stop or destroy any periodic watcher,
543periodic watcher, ever, or make any event loop modificstions</i>. If you need 648ever, or make any event loop modifications</i>. If you need to stop it,
544to stop it, return 1e30 (or so, fudge fudge) and stop it afterwards.</p> 649return <code>now + 1e30</code> (or so, fudge fudge) and stop it afterwards (e.g. by
650starting a prepare watcher).</p>
545 <p>Its prototype is c&lt;ev_tstamp (*reschedule_cb)(struct ev_periodic *w, 651 <p>Its prototype is <code>ev_tstamp (*reschedule_cb)(struct ev_periodic *w,
546ev_tstamp now)&gt;, e.g.:</p> 652ev_tstamp now)</code>, e.g.:</p>
547<pre> static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) 653<pre> static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now)
548 { 654 {
549 return now + 60.; 655 return now + 60.;
550 } 656 }
551 657
552</pre> 658</pre>
553 <p>It must return the next time to trigger, based on the passed time value 659 <p>It must return the next time to trigger, based on the passed time value
554(that is, the lowest time value larger than to the second argument). It 660(that is, the lowest time value larger than to the second argument). It
555will usually be called just before the callback will be triggered, but 661will usually be called just before the callback will be triggered, but
556might be called at other times, too.</p> 662might be called at other times, too.</p>
663 <p>NOTE: <i>This callback must always return a time that is later than the
664passed <code>now</code> value</i>. Not even <code>now</code> itself will do, it <i>must</i> be larger.</p>
557 <p>This can be used to create very complex timers, such as a timer that 665 <p>This can be used to create very complex timers, such as a timer that
558triggers on each midnight, local time. To do this, you would calculate the 666triggers on each midnight, local time. To do this, you would calculate the
559next midnight after <code>now</code> and return the timestamp value for this. How you do this 667next midnight after <code>now</code> and return the timestamp value for this. How
560is, again, up to you (but it is not trivial).</p> 668you do this is, again, up to you (but it is not trivial, which is the main
669reason I omitted it as an example).</p>
561 </dd> 670 </dd>
562 </dl> 671 </dl>
563 </p> 672 </p>
564 </dd> 673 </dd>
565 <dt>ev_periodic_again (loop, ev_periodic *)</dt> 674 <dt>ev_periodic_again (loop, ev_periodic *)</dt>
… …
570program when the crontabs have changed).</p> 679program when the crontabs have changed).</p>
571 </dd> 680 </dd>
572</dl> 681</dl>
573 682
574</div> 683</div>
575<h2 id="ev_signal_signal_me_when_a_signal_ge">ev_signal - signal me when a signal gets signalled</h2> 684<h2 id="code_ev_signal_code_signal_me_when_a"><code>ev_signal</code> - signal me when a signal gets signalled</h2>
576<div id="ev_signal_signal_me_when_a_signal_ge-2"> 685<div id="code_ev_signal_code_signal_me_when_a-2">
577<p>Signal watchers will trigger an event when the process receives a specific 686<p>Signal watchers will trigger an event when the process receives a specific
578signal one or more times. Even though signals are very asynchronous, libev 687signal one or more times. Even though signals are very asynchronous, libev
579will try its best to deliver signals synchronously, i.e. as part of the 688will try it's best to deliver signals synchronously, i.e. as part of the
580normal event processing, like any other event.</p> 689normal event processing, like any other event.</p>
581<p>You cna configure as many watchers as you like per signal. Only when the 690<p>You can configure as many watchers as you like per signal. Only when the
582first watcher gets started will libev actually register a signal watcher 691first watcher gets started will libev actually register a signal watcher
583with the kernel (thus it coexists with your own signal handlers as long 692with the kernel (thus it coexists with your own signal handlers as long
584as you don't register any with libev). Similarly, when the last signal 693as you don't register any with libev). Similarly, when the last signal
585watcher for a signal is stopped libev will reset the signal handler to 694watcher for a signal is stopped libev will reset the signal handler to
586SIG_DFL (regardless of what it was set to before).</p> 695SIG_DFL (regardless of what it was set to before).</p>
… …
592of the <code>SIGxxx</code> constants).</p> 701of the <code>SIGxxx</code> constants).</p>
593 </dd> 702 </dd>
594</dl> 703</dl>
595 704
596</div> 705</div>
597<h2 id="ev_child_wait_for_pid_status_changes">ev_child - wait for pid status changes</h2> 706<h2 id="code_ev_child_code_wait_for_pid_stat"><code>ev_child</code> - wait for pid status changes</h2>
598<div id="ev_child_wait_for_pid_status_changes-2"> 707<div id="code_ev_child_code_wait_for_pid_stat-2">
599<p>Child watchers trigger when your process receives a SIGCHLD in response to 708<p>Child watchers trigger when your process receives a SIGCHLD in response to
600some child status changes (most typically when a child of yours dies).</p> 709some child status changes (most typically when a child of yours dies).</p>
601<dl> 710<dl>
602 <dt>ev_child_init (ev_child *, callback, int pid)</dt> 711 <dt>ev_child_init (ev_child *, callback, int pid)</dt>
603 <dt>ev_child_set (ev_child *, int pid)</dt> 712 <dt>ev_child_set (ev_child *, int pid)</dt>
604 <dd> 713 <dd>
605 <p>Configures the watcher to wait for status changes of process <code>pid</code> (or 714 <p>Configures the watcher to wait for status changes of process <code>pid</code> (or
606<i>any</i> process if <code>pid</code> is specified as <code>0</code>). The callback can look 715<i>any</i> process if <code>pid</code> is specified as <code>0</code>). The callback can look
607at the <code>rstatus</code> member of the <code>ev_child</code> watcher structure to see 716at the <code>rstatus</code> member of the <code>ev_child</code> watcher structure to see
608the status word (use the macros from <code>sys/wait.h</code>). The <code>rpid</code> member 717the status word (use the macros from <code>sys/wait.h</code> and see your systems
718<code>waitpid</code> documentation). The <code>rpid</code> member contains the pid of the
609contains the pid of the process causing the status change.</p> 719process causing the status change.</p>
610 </dd> 720 </dd>
611</dl> 721</dl>
612 722
613</div> 723</div>
614<h2 id="ev_idle_when_you_ve_got_nothing_bett">ev_idle - when you've got nothing better to do</h2> 724<h2 id="code_ev_idle_code_when_you_ve_got_no"><code>ev_idle</code> - when you've got nothing better to do</h2>
615<div id="ev_idle_when_you_ve_got_nothing_bett-2"> 725<div id="code_ev_idle_code_when_you_ve_got_no-2">
616<p>Idle watchers trigger events when there are no other I/O or timer (or 726<p>Idle watchers trigger events when there are no other events are pending
617periodic) events pending. That is, as long as your process is busy 727(prepare, check and other idle watchers do not count). That is, as long
618handling sockets or timeouts it will not be called. But when your process 728as your process is busy handling sockets or timeouts (or even signals,
619is idle all idle watchers are being called again and again - until 729imagine) it will not be triggered. But when your process is idle all idle
730watchers are being called again and again, once per event loop iteration -
620stopped, that is, or your process receives more events.</p> 731until stopped, that is, or your process receives more events and becomes
732busy.</p>
621<p>The most noteworthy effect is that as long as any idle watchers are 733<p>The most noteworthy effect is that as long as any idle watchers are
622active, the process will not block when waiting for new events.</p> 734active, the process will not block when waiting for new events.</p>
623<p>Apart from keeping your process non-blocking (which is a useful 735<p>Apart from keeping your process non-blocking (which is a useful
624effect on its own sometimes), idle watchers are a good place to do 736effect on its own sometimes), idle watchers are a good place to do
625&quot;pseudo-background processing&quot;, or delay processing stuff to after the 737&quot;pseudo-background processing&quot;, or delay processing stuff to after the
… …
632believe me.</p> 744believe me.</p>
633 </dd> 745 </dd>
634</dl> 746</dl>
635 747
636</div> 748</div>
637<h2 id="prepare_and_check_your_hooks_into_th">prepare and check - your hooks into the event loop</h2> 749<h2 id="code_ev_prepare_code_and_code_ev_che"><code>ev_prepare</code> and <code>ev_check</code> - customise your event loop</h2>
638<div id="prepare_and_check_your_hooks_into_th-2"> 750<div id="code_ev_prepare_code_and_code_ev_che-2">
639<p>Prepare and check watchers usually (but not always) are used in 751<p>Prepare and check watchers are usually (but not always) used in tandem:
640tandom. Prepare watchers get invoked before the process blocks and check 752prepare watchers get invoked before the process blocks and check watchers
641watchers afterwards.</p> 753afterwards.</p>
642<p>Their main purpose is to integrate other event mechanisms into libev. This 754<p>Their main purpose is to integrate other event mechanisms into libev. This
643could be used, for example, to track variable changes, implement your own 755could be used, for example, to track variable changes, implement your own
644watchers, integrate net-snmp or a coroutine library and lots more.</p> 756watchers, integrate net-snmp or a coroutine library and lots more.</p>
645<p>This is done by examining in each prepare call which file descriptors need 757<p>This is done by examining in each prepare call which file descriptors need
646to be watched by the other library, registering ev_io watchers for them 758to be watched by the other library, registering <code>ev_io</code> watchers for
647and starting an ev_timer watcher for any timeouts (many libraries provide 759them and starting an <code>ev_timer</code> watcher for any timeouts (many libraries
648just this functionality). Then, in the check watcher you check for any 760provide just this functionality). Then, in the check watcher you check for
649events that occured (by making your callbacks set soem flags for example) 761any events that occured (by checking the pending status of all watchers
650and call back into the library.</p> 762and stopping them) and call back into the library. The I/O and timer
763callbacks will never actually be called (but must be valid nevertheless,
764because you never know, you know?).</p>
651<p>As another example, the perl Coro module uses these hooks to integrate 765<p>As another example, the Perl Coro module uses these hooks to integrate
652coroutines into libev programs, by yielding to other active coroutines 766coroutines into libev programs, by yielding to other active coroutines
653during each prepare and only letting the process block if no coroutines 767during each prepare and only letting the process block if no coroutines
654are ready to run.</p> 768are ready to run (it's actually more complicated: it only runs coroutines
769with priority higher than or equal to the event loop and one coroutine
770of lower priority, but only once, using idle watchers to keep the event
771loop from blocking if lower-priority coroutines are active, thus mapping
772low-priority coroutines to idle/background tasks).</p>
655<dl> 773<dl>
656 <dt>ev_prepare_init (ev_prepare *, callback)</dt> 774 <dt>ev_prepare_init (ev_prepare *, callback)</dt>
657 <dt>ev_check_init (ev_check *, callback)</dt> 775 <dt>ev_check_init (ev_check *, callback)</dt>
658 <dd> 776 <dd>
659 <p>Initialises and configures the prepare or check watcher - they have no 777 <p>Initialises and configures the prepare or check watcher - they have no
660parameters of any kind. There are <code>ev_prepare_set</code> and <code>ev_check_set</code> 778parameters of any kind. There are <code>ev_prepare_set</code> and <code>ev_check_set</code>
661macros, but using them is utterly, utterly pointless.</p> 779macros, but using them is utterly, utterly and completely pointless.</p>
662 </dd> 780 </dd>
663</dl> 781</dl>
664 782
665</div> 783</div>
666<h1 id="OTHER_FUNCTIONS">OTHER FUNCTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p> 784<h1 id="OTHER_FUNCTIONS">OTHER FUNCTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p>
667<div id="OTHER_FUNCTIONS_CONTENT"> 785<div id="OTHER_FUNCTIONS_CONTENT">
668<p>There are some other fucntions of possible interest. Described. Here. Now.</p> 786<p>There are some other functions of possible interest. Described. Here. Now.</p>
669<dl> 787<dl>
670 <dt>ev_once (loop, int fd, int events, ev_tstamp timeout, callback)</dt> 788 <dt>ev_once (loop, int fd, int events, ev_tstamp timeout, callback)</dt>
671 <dd> 789 <dd>
672 <p>This function combines a simple timer and an I/O watcher, calls your 790 <p>This function combines a simple timer and an I/O watcher, calls your
673callback on whichever event happens first and automatically stop both 791callback on whichever event happens first and automatically stop both
674watchers. This is useful if you want to wait for a single event on an fd 792watchers. This is useful if you want to wait for a single event on an fd
675or timeout without havign to allocate/configure/start/stop/free one or 793or timeout without having to allocate/configure/start/stop/free one or
676more watchers yourself.</p> 794more watchers yourself.</p>
677 <p>If <code>fd</code> is less than 0, then no I/O watcher will be started and events is 795 <p>If <code>fd</code> is less than 0, then no I/O watcher will be started and events
678ignored. Otherwise, an ev_io watcher for the given <code>fd</code> and <code>events</code> set 796is being ignored. Otherwise, an <code>ev_io</code> watcher for the given <code>fd</code> and
679will be craeted and started.</p> 797<code>events</code> set will be craeted and started.</p>
680 <p>If <code>timeout</code> is less than 0, then no timeout watcher will be 798 <p>If <code>timeout</code> is less than 0, then no timeout watcher will be
681started. Otherwise an ev_timer watcher with after = <code>timeout</code> (and repeat 799started. Otherwise an <code>ev_timer</code> watcher with after = <code>timeout</code> (and
682= 0) will be started.</p> 800repeat = 0) will be started. While <code>0</code> is a valid timeout, it is of
801dubious value.</p>
683 <p>The callback has the type <code>void (*cb)(int revents, void *arg)</code> and 802 <p>The callback has the type <code>void (*cb)(int revents, void *arg)</code> and gets
684gets passed an events set (normally a combination of EV_ERROR, EV_READ, 803passed an <code>revents</code> set like normal event callbacks (a combination of
685EV_WRITE or EV_TIMEOUT) and the <code>arg</code> value passed to <code>ev_once</code>:</p> 804<code>EV_ERROR</code>, <code>EV_READ</code>, <code>EV_WRITE</code> or <code>EV_TIMEOUT</code>) and the <code>arg</code>
805value passed to <code>ev_once</code>:</p>
686<pre> static void stdin_ready (int revents, void *arg) 806<pre> static void stdin_ready (int revents, void *arg)
687 { 807 {
688 if (revents &amp; EV_TIMEOUT) 808 if (revents &amp; EV_TIMEOUT)
689 /* doh, nothing entered */ 809 /* doh, nothing entered */;
690 else if (revents &amp; EV_READ) 810 else if (revents &amp; EV_READ)
691 /* stdin might have data for us, joy! */ 811 /* stdin might have data for us, joy! */;
692 } 812 }
693 813
694 ev_once (STDIN_FILENO, EV_READm 10., stdin_ready, 0); 814 ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);
695 815
696</pre> 816</pre>
697 </dd> 817 </dd>
698 <dt>ev_feed_event (loop, watcher, int events)</dt> 818 <dt>ev_feed_event (loop, watcher, int events)</dt>
699 <dd> 819 <dd>
700 <p>Feeds the given event set into the event loop, as if the specified event 820 <p>Feeds the given event set into the event loop, as if the specified event
701has happened for the specified watcher (which must be a pointer to an 821had happened for the specified watcher (which must be a pointer to an
702initialised but not necessarily active event watcher).</p> 822initialised but not necessarily started event watcher).</p>
703 </dd> 823 </dd>
704 <dt>ev_feed_fd_event (loop, int fd, int revents)</dt> 824 <dt>ev_feed_fd_event (loop, int fd, int revents)</dt>
705 <dd> 825 <dd>
706 <p>Feed an event on the given fd, as if a file descriptor backend detected it.</p> 826 <p>Feed an event on the given fd, as if a file descriptor backend detected
827the given events it.</p>
707 </dd> 828 </dd>
708 <dt>ev_feed_signal_event (loop, int signum)</dt> 829 <dt>ev_feed_signal_event (loop, int signum)</dt>
709 <dd> 830 <dd>
710 <p>Feed an event as if the given signal occured (loop must be the default loop!).</p> 831 <p>Feed an event as if the given signal occured (loop must be the default loop!).</p>
711 </dd> 832 </dd>
712</dl> 833</dl>
834
835</div>
836<h1 id="LIBEVENT_EMULATION">LIBEVENT EMULATION</h1><p><a href="#TOP" class="toplink">Top</a></p>
837<div id="LIBEVENT_EMULATION_CONTENT">
838<p>Libev offers a compatibility emulation layer for libevent. It cannot
839emulate the internals of libevent, so here are some usage hints:</p>
840<dl>
841 <dt>* Use it by including &lt;event.h&gt;, as usual.</dt>
842 <dt>* The following members are fully supported: ev_base, ev_callback,
843ev_arg, ev_fd, ev_res, ev_events.</dt>
844 <dt>* Avoid using ev_flags and the EVLIST_*-macros, while it is
845maintained by libev, it does not work exactly the same way as in libevent (consider
846it a private API).</dt>
847 <dt>* Priorities are not currently supported. Initialising priorities
848will fail and all watchers will have the same priority, even though there
849is an ev_pri field.</dt>
850 <dt>* Other members are not supported.</dt>
851 <dt>* The libev emulation is <i>not</i> ABI compatible to libevent, you need
852to use the libev header file and library.</dt>
853</dl>
854
855</div>
856<h1 id="C_SUPPORT">C++ SUPPORT</h1><p><a href="#TOP" class="toplink">Top</a></p>
857<div id="C_SUPPORT_CONTENT">
858<p>TBD.</p>
713 859
714</div> 860</div>
715<h1 id="AUTHOR">AUTHOR</h1><p><a href="#TOP" class="toplink">Top</a></p> 861<h1 id="AUTHOR">AUTHOR</h1><p><a href="#TOP" class="toplink">Top</a></p>
716<div id="AUTHOR_CONTENT"> 862<div id="AUTHOR_CONTENT">
717<p>Marc Lehmann &lt;libev@schmorp.de&gt;.</p> 863<p>Marc Lehmann &lt;libev@schmorp.de&gt;.</p>

Diff Legend

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