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

Comparing libev/ev.pod (file contents):
Revision 1.259 by root, Sun Jul 19 01:36:34 2009 UTC vs.
Revision 1.260 by root, Sun Jul 19 21:18:03 2009 UTC

… …
362flag. 362flag.
363 363
364This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS> 364This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS>
365environment variable. 365environment variable.
366 366
367=item C<EVFLAG_NOINOTIFY>
368
369When this flag is specified, then libev will not attempt to use the
370I<inotify> API for it's C<ev_stat> watchers. Apart from debugging and
371testing, this flag can be useful to conserve inotify file descriptors, as
372otherwise each loop using C<ev_stat> watchers consumes one inotify handle.
373
374=item C<EVFLAG_NOSIGNALFD>
375
376When this flag is specified, then libev will not attempt to use the
377I<signalfd> API for it's C<ev_signal> (and C<ev_child>) watchers. This is
378probably only useful to work around any bugs in libev. Consequently, this
379flag might go away once the signalfd functionality is considered stable,
380so it's useful mostly in environment variables and not in program code.
381
367=item C<EVBACKEND_SELECT> (value 1, portable select backend) 382=item C<EVBACKEND_SELECT> (value 1, portable select backend)
368 383
369This is your standard select(2) backend. Not I<completely> standard, as 384This is your standard select(2) backend. Not I<completely> standard, as
370libev tries to roll its own fd_set with no limits on the number of fds, 385libev tries to roll its own fd_set with no limits on the number of fds,
371but if that fails, expect a fairly low limit on the number of fds when 386but if that fails, expect a fairly low limit on the number of fds when
… …
518 533
519It is definitely not recommended to use this flag. 534It is definitely not recommended to use this flag.
520 535
521=back 536=back
522 537
523If one or more of these are or'ed into the flags value, then only these 538If one or more of the backend flags are or'ed into the flags value,
524backends will be tried (in the reverse order as listed here). If none are 539then only these backends will be tried (in the reverse order as listed
525specified, all backends in C<ev_recommended_backends ()> will be tried. 540here). If none are specified, all backends in C<ev_recommended_backends
541()> will be tried.
526 542
527Example: This is the most typical usage. 543Example: This is the most typical usage.
528 544
529 if (!ev_default_loop (0)) 545 if (!ev_default_loop (0))
530 fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?"); 546 fatal ("could not initialise libev, bad $LIBEV_FLAGS in environment?");
… …
2076Signal watchers will trigger an event when the process receives a specific 2092Signal watchers will trigger an event when the process receives a specific
2077signal one or more times. Even though signals are very asynchronous, libev 2093signal one or more times. Even though signals are very asynchronous, libev
2078will try it's best to deliver signals synchronously, i.e. as part of the 2094will try it's best to deliver signals synchronously, i.e. as part of the
2079normal event processing, like any other event. 2095normal event processing, like any other event.
2080 2096
2081Note that only the default loop supports registering signal watchers 2097If you want signals to be delivered truly asynchronously, just use
2082currently. 2098C<sigaction> as you would do without libev and forget about sharing
2099the signal. You can even use C<ev_async> from a signal handler to
2100synchronously wake up an event loop.
2083 2101
2084If you want signals asynchronously, just use C<sigaction> as you would
2085do without libev and forget about sharing the signal. You can even use
2086C<ev_async> from a signal handler to synchronously wake up an event loop.
2087
2088You can configure as many watchers as you like per signal. Only when the 2102You can configure as many watchers as you like for the same signal, but
2103only within the same loop, i.e. you can watch for C<SIGINT> in your
2104default loop and for C<SIGIO> in another loop, but you cannot watch for
2105C<SIGINT> in both the default loop and another loop at the same time. At
2106the moment, C<SIGCHLD> is permanently tied to the default loop.
2107
2089first watcher gets started will libev actually register something with 2108When the first watcher gets started will libev actually register something
2090the kernel (thus it coexists with your own signal handlers as long as you 2109with the kernel (thus it coexists with your own signal handlers as long as
2091don't register any with libev for the same signal). 2110you don't register any with libev for the same signal).
2092 2111
2093Both the signal mask state (C<sigprocmask>) and the signal handler state 2112Both the signal mask state (C<sigprocmask>) and the signal handler state
2094(C<sigaction>) are unspecified after starting a signal watcher (and after 2113(C<sigaction>) are unspecified after starting a signal watcher (and after
2095sotpping it again), that is, libev might or might not block the signal, 2114sotpping it again), that is, libev might or might not block the signal,
2096and might or might not set or restore the installed signal handler. 2115and might or might not set or restore the installed signal handler.
… …
3799Defining C<EV_MINIMAL> to C<2> will additionally reduce the core API to 3818Defining C<EV_MINIMAL> to C<2> will additionally reduce the core API to
3800provide a bare-bones event library. See C<ev.h> for details on what parts 3819provide a bare-bones event library. See C<ev.h> for details on what parts
3801of the API are still available, and do not complain if this subset changes 3820of the API are still available, and do not complain if this subset changes
3802over time. 3821over time.
3803 3822
3823=item EV_NSIG
3824
3825The highest supported signal number, +1 (or, the number of
3826signals): Normally, libev tries to deduce the maximum number of signals
3827automatically, but sometimes this fails, in which case it can be
3828specified. Also, using a lower number than detected (C<32> should be
3829good for about any system in existance) can save some memory, as libev
3830statically allocates some 12-24 bytes per signal number.
3831
3804=item EV_PID_HASHSIZE 3832=item EV_PID_HASHSIZE
3805 3833
3806C<ev_child> watchers use a small hash table to distribute workload by 3834C<ev_child> watchers use a small hash table to distribute workload by
3807pid. The default size is C<16> (or C<1> with C<EV_MINIMAL>), usually more 3835pid. The default size is C<16> (or C<1> with C<EV_MINIMAL>), usually more
3808than enough. If you need to manage thousands of children you might want to 3836than enough. If you need to manage thousands of children you might want to

Diff Legend

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