… | |
… | |
241 | the current system, you would need to look at C<ev_embeddable_backends () |
241 | the current system, you would need to look at C<ev_embeddable_backends () |
242 | & ev_supported_backends ()>, likewise for recommended ones. |
242 | & ev_supported_backends ()>, likewise for recommended ones. |
243 | |
243 | |
244 | See the description of C<ev_embed> watchers for more info. |
244 | See the description of C<ev_embed> watchers for more info. |
245 | |
245 | |
246 | =item ev_set_allocator (void *(*cb)(void *ptr, long size)) [NOT REENTRANT] |
246 | =item ev_set_allocator (void *(*cb)(void *ptr, long size)) |
247 | |
247 | |
248 | Sets the allocation function to use (the prototype is similar - the |
248 | Sets the allocation function to use (the prototype is similar - the |
249 | semantics are identical to the C<realloc> C89/SuS/POSIX function). It is |
249 | semantics are identical to the C<realloc> C89/SuS/POSIX function). It is |
250 | used to allocate and free memory (no surprises here). If it returns zero |
250 | used to allocate and free memory (no surprises here). If it returns zero |
251 | when memory needs to be allocated (C<size != 0>), the library might abort |
251 | when memory needs to be allocated (C<size != 0>), the library might abort |
… | |
… | |
277 | } |
277 | } |
278 | |
278 | |
279 | ... |
279 | ... |
280 | ev_set_allocator (persistent_realloc); |
280 | ev_set_allocator (persistent_realloc); |
281 | |
281 | |
282 | =item ev_set_syserr_cb (void (*cb)(const char *msg)); [NOT REENTRANT] |
282 | =item ev_set_syserr_cb (void (*cb)(const char *msg)) |
283 | |
283 | |
284 | Set the callback function to call on a retryable system call error (such |
284 | Set the callback function to call on a retryable system call error (such |
285 | as failed select, poll, epoll_wait). The message is a printable string |
285 | as failed select, poll, epoll_wait). The message is a printable string |
286 | indicating the system call or subsystem causing the problem. If this |
286 | indicating the system call or subsystem causing the problem. If this |
287 | callback is set, then libev will expect it to remedy the situation, no |
287 | callback is set, then libev will expect it to remedy the situation, no |
… | |
… | |
355 | =item struct ev_loop *ev_loop_new (unsigned int flags) |
355 | =item struct ev_loop *ev_loop_new (unsigned int flags) |
356 | |
356 | |
357 | This will create and initialise a new event loop object. If the loop |
357 | This will create and initialise a new event loop object. If the loop |
358 | could not be initialised, returns false. |
358 | could not be initialised, returns false. |
359 | |
359 | |
360 | Note that this function I<is> thread-safe, and one common way to use |
360 | This function is thread-safe, and one common way to use libev with |
361 | libev with threads is indeed to create one loop per thread, and using the |
361 | threads is indeed to create one loop per thread, and using the default |
362 | default loop in the "main" or "initial" thread. |
362 | loop in the "main" or "initial" thread. |
363 | |
363 | |
364 | The flags argument can be used to specify special behaviour or specific |
364 | The flags argument can be used to specify special behaviour or specific |
365 | backends to use, and is usually specified as C<0> (or C<EVFLAG_AUTO>). |
365 | backends to use, and is usually specified as C<0> (or C<EVFLAG_AUTO>). |
366 | |
366 | |
367 | The following flags are supported: |
367 | The following flags are supported: |
… | |
… | |
402 | environment variable. |
402 | environment variable. |
403 | |
403 | |
404 | =item C<EVFLAG_NOINOTIFY> |
404 | =item C<EVFLAG_NOINOTIFY> |
405 | |
405 | |
406 | When this flag is specified, then libev will not attempt to use the |
406 | When this flag is specified, then libev will not attempt to use the |
407 | I<inotify> API for it's C<ev_stat> watchers. Apart from debugging and |
407 | I<inotify> API for its C<ev_stat> watchers. Apart from debugging and |
408 | testing, this flag can be useful to conserve inotify file descriptors, as |
408 | testing, this flag can be useful to conserve inotify file descriptors, as |
409 | otherwise each loop using C<ev_stat> watchers consumes one inotify handle. |
409 | otherwise each loop using C<ev_stat> watchers consumes one inotify handle. |
410 | |
410 | |
411 | =item C<EVFLAG_SIGNALFD> |
411 | =item C<EVFLAG_SIGNALFD> |
412 | |
412 | |
413 | When this flag is specified, then libev will attempt to use the |
413 | When this flag is specified, then libev will attempt to use the |
414 | I<signalfd> API for it's C<ev_signal> (and C<ev_child>) watchers. This API |
414 | I<signalfd> API for its C<ev_signal> (and C<ev_child>) watchers. This API |
415 | delivers signals synchronously, which makes it both faster and might make |
415 | delivers signals synchronously, which makes it both faster and might make |
416 | it possible to get the queued signal data. It can also simplify signal |
416 | it possible to get the queued signal data. It can also simplify signal |
417 | handling with threads, as long as you properly block signals in your |
417 | handling with threads, as long as you properly block signals in your |
418 | threads that are not interested in handling them. |
418 | threads that are not interested in handling them. |
419 | |
419 | |
… | |
… | |
464 | |
464 | |
465 | The epoll mechanism deserves honorable mention as the most misdesigned |
465 | The epoll mechanism deserves honorable mention as the most misdesigned |
466 | of the more advanced event mechanisms: mere annoyances include silently |
466 | of the more advanced event mechanisms: mere annoyances include silently |
467 | dropping file descriptors, requiring a system call per change per file |
467 | dropping file descriptors, requiring a system call per change per file |
468 | descriptor (and unnecessary guessing of parameters), problems with dup, |
468 | descriptor (and unnecessary guessing of parameters), problems with dup, |
469 | returning before the timeout value requiring additional iterations and so |
469 | returning before the timeout value, resulting in additional iterations |
|
|
470 | (and only giving 5ms accuracy while select on the same platform gives |
470 | on. The biggest issue is fork races, however - if a program forks then |
471 | 0.1ms) and so on. The biggest issue is fork races, however - if a program |
471 | I<both> parent and child process have to recreate the epoll set, which can |
472 | forks then I<both> parent and child process have to recreate the epoll |
472 | take considerable time (one syscall per file descriptor) and is of course |
473 | set, which can take considerable time (one syscall per file descriptor) |
473 | hard to detect. |
474 | and is of course hard to detect. |
474 | |
475 | |
475 | Epoll is also notoriously buggy - embedding epoll fds I<should> work, but |
476 | Epoll is also notoriously buggy - embedding epoll fds I<should> work, but |
476 | of course I<doesn't>, and epoll just loves to report events for totally |
477 | of course I<doesn't>, and epoll just loves to report events for totally |
477 | I<different> file descriptors (even already closed ones, so one cannot |
478 | I<different> file descriptors (even already closed ones, so one cannot |
478 | even remove them from the set) than registered in the set (especially |
479 | even remove them from the set) than registered in the set (especially |
… | |
… | |
480 | employing an additional generation counter and comparing that against the |
481 | employing an additional generation counter and comparing that against the |
481 | events to filter out spurious ones, recreating the set when required. Last |
482 | events to filter out spurious ones, recreating the set when required. Last |
482 | not least, it also refuses to work with some file descriptors which work |
483 | not least, it also refuses to work with some file descriptors which work |
483 | perfectly fine with C<select> (files, many character devices...). |
484 | perfectly fine with C<select> (files, many character devices...). |
484 | |
485 | |
|
|
486 | Epoll is truly the train wreck analog among event poll mechanisms. |
|
|
487 | |
485 | While stopping, setting and starting an I/O watcher in the same iteration |
488 | While stopping, setting and starting an I/O watcher in the same iteration |
486 | will result in some caching, there is still a system call per such |
489 | will result in some caching, there is still a system call per such |
487 | incident (because the same I<file descriptor> could point to a different |
490 | incident (because the same I<file descriptor> could point to a different |
488 | I<file description> now), so its best to avoid that. Also, C<dup ()>'ed |
491 | I<file description> now), so its best to avoid that. Also, C<dup ()>'ed |
489 | file descriptors might not work very well if you register events for both |
492 | file descriptors might not work very well if you register events for both |
… | |
… | |
616 | This function is normally used on loop objects allocated by |
619 | This function is normally used on loop objects allocated by |
617 | C<ev_loop_new>, but it can also be used on the default loop returned by |
620 | C<ev_loop_new>, but it can also be used on the default loop returned by |
618 | C<ev_default_loop>, in which case it is not thread-safe. |
621 | C<ev_default_loop>, in which case it is not thread-safe. |
619 | |
622 | |
620 | Note that it is not advisable to call this function on the default loop |
623 | Note that it is not advisable to call this function on the default loop |
621 | except in the rare occasion where you really need to free it's resources. |
624 | except in the rare occasion where you really need to free its resources. |
622 | If you need dynamically allocated loops it is better to use C<ev_loop_new> |
625 | If you need dynamically allocated loops it is better to use C<ev_loop_new> |
623 | and C<ev_loop_destroy>. |
626 | and C<ev_loop_destroy>. |
624 | |
627 | |
625 | =item ev_loop_fork (loop) |
628 | =item ev_loop_fork (loop) |
626 | |
629 | |
… | |
… | |
674 | prepare and check phases. |
677 | prepare and check phases. |
675 | |
678 | |
676 | =item unsigned int ev_depth (loop) |
679 | =item unsigned int ev_depth (loop) |
677 | |
680 | |
678 | Returns the number of times C<ev_run> was entered minus the number of |
681 | Returns the number of times C<ev_run> was entered minus the number of |
679 | times C<ev_run> was exited, in other words, the recursion depth. |
682 | times C<ev_run> was exited normally, in other words, the recursion depth. |
680 | |
683 | |
681 | Outside C<ev_run>, this number is zero. In a callback, this number is |
684 | Outside C<ev_run>, this number is zero. In a callback, this number is |
682 | C<1>, unless C<ev_run> was invoked recursively (or from another thread), |
685 | C<1>, unless C<ev_run> was invoked recursively (or from another thread), |
683 | in which case it is higher. |
686 | in which case it is higher. |
684 | |
687 | |
685 | Leaving C<ev_run> abnormally (setjmp/longjmp, cancelling the thread |
688 | Leaving C<ev_run> abnormally (setjmp/longjmp, cancelling the thread, |
686 | etc.), doesn't count as "exit" - consider this as a hint to avoid such |
689 | throwing an exception etc.), doesn't count as "exit" - consider this |
687 | ungentleman-like behaviour unless it's really convenient. |
690 | as a hint to avoid such ungentleman-like behaviour unless it's really |
|
|
691 | convenient, in which case it is fully supported. |
688 | |
692 | |
689 | =item unsigned int ev_backend (loop) |
693 | =item unsigned int ev_backend (loop) |
690 | |
694 | |
691 | Returns one of the C<EVBACKEND_*> flags indicating the event backend in |
695 | Returns one of the C<EVBACKEND_*> flags indicating the event backend in |
692 | use. |
696 | use. |
… | |
… | |
753 | relying on all watchers to be stopped when deciding when a program has |
757 | relying on all watchers to be stopped when deciding when a program has |
754 | finished (especially in interactive programs), but having a program |
758 | finished (especially in interactive programs), but having a program |
755 | that automatically loops as long as it has to and no longer by virtue |
759 | that automatically loops as long as it has to and no longer by virtue |
756 | of relying on its watchers stopping correctly, that is truly a thing of |
760 | of relying on its watchers stopping correctly, that is truly a thing of |
757 | beauty. |
761 | beauty. |
|
|
762 | |
|
|
763 | This function is also I<mostly> exception-safe - you can break out of |
|
|
764 | a C<ev_run> call by calling C<longjmp> in a callback, throwing a C++ |
|
|
765 | exception and so on. This does not decrement the C<ev_depth> value, nor |
|
|
766 | will it clear any outstanding C<EVBREAK_ONE> breaks. |
758 | |
767 | |
759 | A flags value of C<EVRUN_NOWAIT> will look for new events, will handle |
768 | A flags value of C<EVRUN_NOWAIT> will look for new events, will handle |
760 | those events and any already outstanding ones, but will not wait and |
769 | those events and any already outstanding ones, but will not wait and |
761 | block your process in case there are no events and will return after one |
770 | block your process in case there are no events and will return after one |
762 | iteration of the loop. This is sometimes useful to poll and handle new |
771 | iteration of the loop. This is sometimes useful to poll and handle new |
… | |
… | |
824 | Can be used to make a call to C<ev_run> return early (but only after it |
833 | Can be used to make a call to C<ev_run> return early (but only after it |
825 | has processed all outstanding events). The C<how> argument must be either |
834 | has processed all outstanding events). The C<how> argument must be either |
826 | C<EVBREAK_ONE>, which will make the innermost C<ev_run> call return, or |
835 | C<EVBREAK_ONE>, which will make the innermost C<ev_run> call return, or |
827 | C<EVBREAK_ALL>, which will make all nested C<ev_run> calls return. |
836 | C<EVBREAK_ALL>, which will make all nested C<ev_run> calls return. |
828 | |
837 | |
829 | This "break state" will be cleared when entering C<ev_run> again. |
838 | This "break state" will be cleared on the next call to C<ev_run>. |
830 | |
839 | |
831 | It is safe to call C<ev_break> from outside any C<ev_run> calls, too. |
840 | It is safe to call C<ev_break> from outside any C<ev_run> calls, too, in |
|
|
841 | which case it will have no effect. |
832 | |
842 | |
833 | =item ev_ref (loop) |
843 | =item ev_ref (loop) |
834 | |
844 | |
835 | =item ev_unref (loop) |
845 | =item ev_unref (loop) |
836 | |
846 | |
… | |
… | |
983 | |
993 | |
984 | =item ev_userdata (loop) |
994 | =item ev_userdata (loop) |
985 | |
995 | |
986 | Set and retrieve a single C<void *> associated with a loop. When |
996 | Set and retrieve a single C<void *> associated with a loop. When |
987 | C<ev_set_userdata> has never been called, then C<ev_userdata> returns |
997 | C<ev_set_userdata> has never been called, then C<ev_userdata> returns |
988 | C<0.> |
998 | C<0>. |
989 | |
999 | |
990 | These two functions can be used to associate arbitrary data with a loop, |
1000 | These two functions can be used to associate arbitrary data with a loop, |
991 | and are intended solely for the C<invoke_pending_cb>, C<release> and |
1001 | and are intended solely for the C<invoke_pending_cb>, C<release> and |
992 | C<acquire> callbacks described above, but of course can be (ab-)used for |
1002 | C<acquire> callbacks described above, but of course can be (ab-)used for |
993 | any other purpose as well. |
1003 | any other purpose as well. |
… | |
… | |
2257 | |
2267 | |
2258 | =head2 C<ev_signal> - signal me when a signal gets signalled! |
2268 | =head2 C<ev_signal> - signal me when a signal gets signalled! |
2259 | |
2269 | |
2260 | Signal watchers will trigger an event when the process receives a specific |
2270 | Signal watchers will trigger an event when the process receives a specific |
2261 | signal one or more times. Even though signals are very asynchronous, libev |
2271 | signal one or more times. Even though signals are very asynchronous, libev |
2262 | will try it's best to deliver signals synchronously, i.e. as part of the |
2272 | will try its best to deliver signals synchronously, i.e. as part of the |
2263 | normal event processing, like any other event. |
2273 | normal event processing, like any other event. |
2264 | |
2274 | |
2265 | If you want signals to be delivered truly asynchronously, just use |
2275 | If you want signals to be delivered truly asynchronously, just use |
2266 | C<sigaction> as you would do without libev and forget about sharing |
2276 | C<sigaction> as you would do without libev and forget about sharing |
2267 | the signal. You can even use C<ev_async> from a signal handler to |
2277 | the signal. You can even use C<ev_async> from a signal handler to |
… | |
… | |
3378 | =item * Priorities are not currently supported. Initialising priorities |
3388 | =item * Priorities are not currently supported. Initialising priorities |
3379 | will fail and all watchers will have the same priority, even though there |
3389 | will fail and all watchers will have the same priority, even though there |
3380 | is an ev_pri field. |
3390 | is an ev_pri field. |
3381 | |
3391 | |
3382 | =item * In libevent, the last base created gets the signals, in libev, the |
3392 | =item * In libevent, the last base created gets the signals, in libev, the |
3383 | first base created (== the default loop) gets the signals. |
3393 | base that registered the signal gets the signals. |
3384 | |
3394 | |
3385 | =item * Other members are not supported. |
3395 | =item * Other members are not supported. |
3386 | |
3396 | |
3387 | =item * The libev emulation is I<not> ABI compatible to libevent, you need |
3397 | =item * The libev emulation is I<not> ABI compatible to libevent, you need |
3388 | to use the libev header file and library. |
3398 | to use the libev header file and library. |