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

Comparing libev/ev.html (file contents):
Revision 1.21 by root, Mon Nov 12 09:01:12 2007 UTC vs.
Revision 1.29 by root, Thu Nov 22 12:28:27 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 10:01:12 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 -->
… …
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="#code_ev_idle_code_when_you_ve_got_no"><code>ev_idle</code> - when you've got nothing better to do</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<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>
37</ul> 37</ul>
38</li> 38</li>
39<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>
40<li><a href="#AUTHOR">AUTHOR</a> 42<li><a href="#AUTHOR">AUTHOR</a>
41</li> 43</li>
42</ul><hr /> 44</ul><hr />
43<!-- INDEX END --> 45<!-- INDEX END -->
44 46
… …
104<p>These functions can be called anytime, even before initialising the 106<p>These functions can be called anytime, even before initialising the
105library in any way.</p> 107library in any way.</p>
106<dl> 108<dl>
107 <dt>ev_tstamp ev_time ()</dt> 109 <dt>ev_tstamp ev_time ()</dt>
108 <dd> 110 <dd>
109 <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>
110 </dd> 114 </dd>
111 <dt>int ev_version_major ()</dt> 115 <dt>int ev_version_major ()</dt>
112 <dt>int ev_version_minor ()</dt> 116 <dt>int ev_version_minor ()</dt>
113 <dd> 117 <dd>
114 <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
… …
182<code>LIBEV_FLAGS</code>. Otherwise (the default), this environment variable will 186<code>LIBEV_FLAGS</code>. Otherwise (the default), this environment variable will
183override the flags completely if it is found in the environment. This is 187override the flags completely if it is found in the environment. This is
184useful to try out specific backends to test their performance, or to work 188useful to try out specific backends to test their performance, or to work
185around bugs.</p> 189around bugs.</p>
186 </dd> 190 </dd>
187 <dt><code>EVMETHOD_SELECT</code> (portable select backend)</dt> 191 <dt><code>EVMETHOD_SELECT</code> (value 1, portable select backend)</dt>
192 <dd>
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>
188 <dt><code>EVMETHOD_POLL</code> (poll backend, available everywhere except on windows)</dt> 199 <dt><code>EVMETHOD_POLL</code> (value 2, poll backend, available everywhere except on windows)</dt>
189 <dt><code>EVMETHOD_EPOLL</code> (linux only)</dt> 200 <dd>
190 <dt><code>EVMETHOD_KQUEUE</code> (some bsds only)</dt> 201 <p>And this is your standard poll(2) backend. It's more complicated than
191 <dt><code>EVMETHOD_DEVPOLL</code> (solaris 8 only)</dt> 202select, but handles sparse fds better and has no artificial limit on the
192 <dt><code>EVMETHOD_PORT</code> (solaris 10 only)</dt> 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>
193 <dd> 205 </dd>
194 <p>If one or more of these are ored into the flags value, then only these 206 <dt><code>EVMETHOD_EPOLL</code> (value 4, Linux)</dt>
195backends will be tried (in the reverse order as given here). If one are 207 <dd>
196specified, any backend will do.</p> 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). Since this is a mask, you
243can do stuff like <code>EVMETHOD_ALL &amp; ~EVMETHOD_KQUEUE</code>.</p>
197 </dd> 244 </dd>
198 </dl> 245 </dl>
199 </p> 246 </p>
247 <p>If one or more of these are ored into the flags value, then only these
248backends will be tried (in the reverse order as given here). If none are
249specified, most compiled-in backend will be tried, usually in reverse
250order of their flag values :)</p>
200 </dd> 251 </dd>
201 <dt>struct ev_loop *ev_loop_new (unsigned int flags)</dt> 252 <dt>struct ev_loop *ev_loop_new (unsigned int flags)</dt>
202 <dd> 253 <dd>
203 <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
204always distinct from the default loop. Unlike the default loop, it cannot 255always distinct from the default loop. Unlike the default loop, it cannot
… …
266your process until at least one new event arrives, and will return after 317your process until at least one new event arrives, and will return after
267one iteration of the loop.</p> 318one iteration of the loop.</p>
268 <p>This flags value could be used to implement alternative looping 319 <p>This flags value could be used to implement alternative looping
269constructs, but the <code>prepare</code> and <code>check</code> watchers provide a better and 320constructs, but the <code>prepare</code> and <code>check</code> watchers provide a better and
270more generic mechanism.</p> 321more 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 &quot;event loop time&quot;.
328 6. Calculate for how long to block.
329 7. Block the process, waiting for events.
330 8. Update the &quot;event loop time&quot; 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>
271 </dd> 340 </dd>
272 <dt>ev_unloop (loop, how)</dt> 341 <dt>ev_unloop (loop, how)</dt>
273 <dd> 342 <dd>
274 <p>Can be used to make a call to <code>ev_loop</code> return early (but only after it 343 <p>Can be used to make a call to <code>ev_loop</code> return early (but only after it
275has processed all outstanding events). The <code>how</code> argument must be either 344has processed all outstanding events). The <code>how</code> argument must be either
276<code>EVUNLOOP_ONCE</code>, which will make the innermost <code>ev_loop</code> call return, or 345<code>EVUNLOOP_ONE</code>, which will make the innermost <code>ev_loop</code> call return, or
277<code>EVUNLOOP_ALL</code>, which will make all nested <code>ev_loop</code> calls return.</p> 346<code>EVUNLOOP_ALL</code>, which will make all nested <code>ev_loop</code> calls return.</p>
278 </dd> 347 </dd>
279 <dt>ev_ref (loop)</dt> 348 <dt>ev_ref (loop)</dt>
280 <dt>ev_unref (loop)</dt> 349 <dt>ev_unref (loop)</dt>
281 <dd> 350 <dd>
… …
440<p>I/O watchers check whether a file descriptor is readable or writable 509<p>I/O watchers check whether a file descriptor is readable or writable
441in each iteration of the event loop (This behaviour is called 510in each iteration of the event loop (This behaviour is called
442level-triggering because you keep receiving events as long as the 511level-triggering because you keep receiving events as long as the
443condition persists. Remember you can stop the watcher if you don't want to 512condition persists. Remember you can stop the watcher if you don't want to
444act on the event and neither want to receive future events).</p> 513act on the event and neither want to receive future events).</p>
445<p>In general you can register as many read and/or write event watchers oer 514<p>In general you can register as many read and/or write event watchers per
446fd as you want (as long as you don't confuse yourself). Setting all file 515fd as you want (as long as you don't confuse yourself). Setting all file
447descriptors to non-blocking mode is also usually a good idea (but not 516descriptors to non-blocking mode is also usually a good idea (but not
448required if you know what you are doing).</p> 517required if you know what you are doing).</p>
449<p>You have to be careful with dup'ed file descriptors, though. Some backends 518<p>You have to be careful with dup'ed file descriptors, though. Some backends
450(the linux epoll backend is a notable example) cannot handle dup'ed file 519(the linux epoll backend is a notable example) cannot handle dup'ed file
451descriptors correctly if you register interest in two or more fds pointing 520descriptors correctly if you register interest in two or more fds pointing
452to the same file/socket etc. description.</p> 521to the same underlying file/socket etc. description (that is, they share
522the same underlying &quot;file open&quot;).</p>
453<p>If you must do this, then force the use of a known-to-be-good backend 523<p>If you must do this, then force the use of a known-to-be-good backend
454(at the time of this writing, this includes only EVMETHOD_SELECT and 524(at the time of this writing, this includes only EVMETHOD_SELECT and
455EVMETHOD_POLL).</p> 525EVMETHOD_POLL).</p>
456<dl> 526<dl>
457 <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>
… …
467<h2 id="code_ev_timer_code_relative_and_opti"><code>ev_timer</code> - 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>
468<div id="code_ev_timer_code_relative_and_opti-2"> 538<div id="code_ev_timer_code_relative_and_opti-2">
469<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
470given time, and optionally repeating in regular intervals after that.</p> 540given time, and optionally repeating in regular intervals after that.</p>
471<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
472times out after an hour and youreset your system clock to last years 542times out after an hour and you reset your system clock to last years
473time, it will still time out after (roughly) and hour. &quot;Roughly&quot; because 543time, it will still time out after (roughly) and hour. &quot;Roughly&quot; because
474detecting time jumps is hard, and soem inaccuracies are unavoidable (the 544detecting time jumps is hard, and some inaccuracies are unavoidable (the
475monotonic clock option helps a lot here).</p> 545monotonic clock option helps a lot here).</p>
476<p>The relative timeouts are calculated relative to the <code>ev_now ()</code> 546<p>The relative timeouts are calculated relative to the <code>ev_now ()</code>
477time. This is usually the right thing as this timestamp refers to the time 547time. This is usually the right thing as this timestamp refers to the time
478of the event triggering whatever timeout you are modifying/starting. If 548of the event triggering whatever timeout you are modifying/starting. If
479you suspect event processing to be delayed and you *need* to base the timeout 549you suspect event processing to be delayed and you <i>need</i> to base the timeout
480ion the current time, use something like this to adjust for this:</p> 550on the current time, use something like this to adjust for this:</p>
481<pre> ev_timer_set (&amp;timer, after + ev_now () - ev_time (), 0.); 551<pre> ev_timer_set (&amp;timer, after + ev_now () - ev_time (), 0.);
482 552
483</pre> 553</pre>
554<p>The callback is guarenteed to be invoked only when its timeout has passed,
555but if multiple timers become ready during the same loop iteration then
556order of execution is undefined.</p>
484<dl> 557<dl>
485 <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>
486 <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>
487 <dd> 560 <dd>
488 <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
… …
490timer will automatically be configured to trigger again <code>repeat</code> seconds 563timer will automatically be configured to trigger again <code>repeat</code> seconds
491later, again, and again, until stopped manually.</p> 564later, again, and again, until stopped manually.</p>
492 <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
493configure a timer to trigger every 10 seconds, then it will trigger at 566configure a timer to trigger every 10 seconds, then it will trigger at
494exactly 10 second intervals. If, however, your program cannot keep up with 567exactly 10 second intervals. If, however, your program cannot keep up with
495the timer (ecause it takes longer than those 10 seconds to do stuff) the 568the timer (because it takes longer than those 10 seconds to do stuff) the
496timer will not fire more than once per event loop iteration.</p> 569timer will not fire more than once per event loop iteration.</p>
497 </dd> 570 </dd>
498 <dt>ev_timer_again (loop)</dt> 571 <dt>ev_timer_again (loop)</dt>
499 <dd> 572 <dd>
500 <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
… …
526take a year to trigger the event (unlike an <code>ev_timer</code>, which would trigger 599take a year to trigger the event (unlike an <code>ev_timer</code>, which would trigger
527roughly 10 seconds later and of course not if you reset your system time 600roughly 10 seconds later and of course not if you reset your system time
528again).</p> 601again).</p>
529<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
530triggering an event on eahc midnight, local time.</p> 603triggering an event on eahc midnight, local time.</p>
604<p>As with timers, the callback is guarenteed to be invoked only when the
605time (<code>at</code>) has been passed, but if multiple periodic timers become ready
606during the same loop iteration then order of execution is undefined.</p>
531<dl> 607<dl>
532 <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>
533 <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>
534 <dd> 610 <dd>
535 <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
536operation, and we will explain them from simplest to complex:</p> 612operation, and we will explain them from simplest to complex:</p>
537
538
539
540
541 <p> 613 <p>
542 <dl> 614 <dl>
543 <dt>* absolute timer (interval = reschedule_cb = 0)</dt> 615 <dt>* absolute timer (interval = reschedule_cb = 0)</dt>
544 <dd> 616 <dd>
545 <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
… …
586 <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
587(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
588will usually be called just before the callback will be triggered, but 660will usually be called just before the callback will be triggered, but
589might be called at other times, too.</p> 661might be called at other times, too.</p>
590 <p>NOTE: <i>This callback must always return a time that is later than the 662 <p>NOTE: <i>This callback must always return a time that is later than the
591passed <code>now</code> value</i>. Not even <code>now</code> itself will do, it must be larger.</p> 663passed <code>now</code> value</i>. Not even <code>now</code> itself will do, it <i>must</i> be larger.</p>
592 <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
593triggers on each midnight, local time. To do this, you would calculate the 665triggers on each midnight, local time. To do this, you would calculate the
594next midnight after <code>now</code> and return the timestamp value for this. How you do this 666next midnight after <code>now</code> and return the timestamp value for this. How
595is, again, up to you (but it is not trivial).</p> 667you do this is, again, up to you (but it is not trivial, which is the main
668reason I omitted it as an example).</p>
596 </dd> 669 </dd>
597 </dl> 670 </dl>
598 </p> 671 </p>
599 </dd> 672 </dd>
600 <dt>ev_periodic_again (loop, ev_periodic *)</dt> 673 <dt>ev_periodic_again (loop, ev_periodic *)</dt>
… …
673 746
674</div> 747</div>
675<h2 id="code_ev_prepare_code_and_code_ev_che"><code>ev_prepare</code> and <code>ev_check</code> - customise your 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>
676<div id="code_ev_prepare_code_and_code_ev_che-2"> 749<div id="code_ev_prepare_code_and_code_ev_che-2">
677<p>Prepare and check watchers are usually (but not always) used in tandem: 750<p>Prepare and check watchers are usually (but not always) used in tandem:
678Prepare watchers get invoked before the process blocks and check watchers 751prepare watchers get invoked before the process blocks and check watchers
679afterwards.</p> 752afterwards.</p>
680<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
681could be used, for example, to track variable changes, implement your own 754could be used, for example, to track variable changes, implement your own
682watchers, integrate net-snmp or a coroutine library and lots more.</p> 755watchers, integrate net-snmp or a coroutine library and lots more.</p>
683<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
684to be watched by the other library, registering <code>ev_io</code> watchers for 757to be watched by the other library, registering <code>ev_io</code> watchers for
685them and starting an <code>ev_timer</code> watcher for any timeouts (many libraries 758them and starting an <code>ev_timer</code> watcher for any timeouts (many libraries
686provide just this functionality). Then, in the check watcher you check for 759provide just this functionality). Then, in the check watcher you check for
687any events that occured (by checking the pending status of all watchers 760any events that occured (by checking the pending status of all watchers
688and stopping them) and call back into the library. The I/O and timer 761and stopping them) and call back into the library. The I/O and timer
689callbacks will never actually be called (but must be valid neverthelles, 762callbacks will never actually be called (but must be valid nevertheless,
690because you never know, you know?).</p> 763because you never know, you know?).</p>
691<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
692coroutines into libev programs, by yielding to other active coroutines 765coroutines into libev programs, by yielding to other active coroutines
693during each prepare and only letting the process block if no coroutines 766during each prepare and only letting the process block if no coroutines
694are ready to run (its actually more complicated, it only runs coroutines 767are ready to run (it's actually more complicated: it only runs coroutines
695with priority higher than the event loop and one lower priority once, 768with priority higher than or equal to the event loop and one coroutine
696using idle watchers to keep the event loop from blocking if lower-priority 769of lower priority, but only once, using idle watchers to keep the event
697coroutines exist, thus mapping low-priority coroutines to idle/background 770loop from blocking if lower-priority coroutines are active, thus mapping
698tasks).</p> 771low-priority coroutines to idle/background tasks).</p>
699<dl> 772<dl>
700 <dt>ev_prepare_init (ev_prepare *, callback)</dt> 773 <dt>ev_prepare_init (ev_prepare *, callback)</dt>
701 <dt>ev_check_init (ev_check *, callback)</dt> 774 <dt>ev_check_init (ev_check *, callback)</dt>
702 <dd> 775 <dd>
703 <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
… …
714 <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>
715 <dd> 788 <dd>
716 <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
717callback on whichever event happens first and automatically stop both 790callback on whichever event happens first and automatically stop both
718watchers. This is useful if you want to wait for a single event on an fd 791watchers. This is useful if you want to wait for a single event on an fd
719or timeout without havign to allocate/configure/start/stop/free one or 792or timeout without having to allocate/configure/start/stop/free one or
720more watchers yourself.</p> 793more watchers yourself.</p>
721 <p>If <code>fd</code> is less than 0, then no I/O watcher will be started and events 794 <p>If <code>fd</code> is less than 0, then no I/O watcher will be started and events
722is being ignored. Otherwise, an <code>ev_io</code> watcher for the given <code>fd</code> and 795is being ignored. Otherwise, an <code>ev_io</code> watcher for the given <code>fd</code> and
723<code>events</code> set will be craeted and started.</p> 796<code>events</code> set will be craeted and started.</p>
724 <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
725started. Otherwise an <code>ev_timer</code> watcher with after = <code>timeout</code> (and 798started. Otherwise an <code>ev_timer</code> watcher with after = <code>timeout</code> (and
726repeat = 0) will be started. While <code>0</code> is a valid timeout, it is of 799repeat = 0) will be started. While <code>0</code> is a valid timeout, it is of
727dubious value.</p> 800dubious value.</p>
728 <p>The callback has the type <code>void (*cb)(int revents, void *arg)</code> and gets 801 <p>The callback has the type <code>void (*cb)(int revents, void *arg)</code> and gets
729passed an events set like normal event callbacks (with a combination of 802passed an <code>revents</code> set like normal event callbacks (a combination of
730<code>EV_ERROR</code>, <code>EV_READ</code>, <code>EV_WRITE</code> or <code>EV_TIMEOUT</code>) and the <code>arg</code> 803<code>EV_ERROR</code>, <code>EV_READ</code>, <code>EV_WRITE</code> or <code>EV_TIMEOUT</code>) and the <code>arg</code>
731value passed to <code>ev_once</code>:</p> 804value passed to <code>ev_once</code>:</p>
732<pre> static void stdin_ready (int revents, void *arg) 805<pre> static void stdin_ready (int revents, void *arg)
733 { 806 {
734 if (revents &amp; EV_TIMEOUT) 807 if (revents &amp; EV_TIMEOUT)
… …
757 <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>
758 </dd> 831 </dd>
759</dl> 832</dl>
760 833
761</div> 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
838emulate the internals of libevent, so here are some usage hints:</p>
839<dl>
840 <dt>* Use it by including &lt;event.h&gt;, as usual.</dt>
841 <dt>* The following members are fully supported: ev_base, ev_callback,
842ev_arg, ev_fd, ev_res, ev_events.</dt>
843 <dt>* Avoid using ev_flags and the EVLIST_*-macros, while it is
844maintained by libev, it does not work exactly the same way as in libevent (consider
845it a private API).</dt>
846 <dt>* Priorities are not currently supported. Initialising priorities
847will fail and all watchers will have the same priority, even though there
848is 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
851to 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>
858
859</div>
762<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>
763<div id="AUTHOR_CONTENT"> 861<div id="AUTHOR_CONTENT">
764<p>Marc Lehmann &lt;libev@schmorp.de&gt;.</p> 862<p>Marc Lehmann &lt;libev@schmorp.de&gt;.</p>
765 863
766</div> 864</div>

Diff Legend

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