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