… | |
… | |
299 | } |
299 | } |
300 | |
300 | |
301 | ... |
301 | ... |
302 | ev_set_syserr_cb (fatal_error); |
302 | ev_set_syserr_cb (fatal_error); |
303 | |
303 | |
|
|
304 | =item ev_feed_signal (int signum) |
|
|
305 | |
|
|
306 | This function can be used to "simulate" a signal receive. It is completely |
|
|
307 | safe to call this function at any time, from any context, including signal |
|
|
308 | handlers or random threads. |
|
|
309 | |
|
|
310 | Its main use is to customise signal handling in your process, especially |
|
|
311 | in the presence of threads. For example, you could block signals |
|
|
312 | by default in all threads (and specifying C<EVFLAG_NOSIGMASK> when |
|
|
313 | creating any loops), and in one thread, use C<sigwait> or any other |
|
|
314 | mechanism to wait for signals, then "deliver" them to libev by calling |
|
|
315 | C<ev_feed_signal>. |
|
|
316 | |
304 | =back |
317 | =back |
305 | |
318 | |
306 | =head1 FUNCTIONS CONTROLLING EVENT LOOPS |
319 | =head1 FUNCTIONS CONTROLLING EVENT LOOPS |
307 | |
320 | |
308 | An event loop is described by a C<struct ev_loop *> (the C<struct> is |
321 | An event loop is described by a C<struct ev_loop *> (the C<struct> is |
… | |
… | |
418 | threads that are not interested in handling them. |
431 | threads that are not interested in handling them. |
419 | |
432 | |
420 | Signalfd will not be used by default as this changes your signal mask, and |
433 | Signalfd will not be used by default as this changes your signal mask, and |
421 | there are a lot of shoddy libraries and programs (glib's threadpool for |
434 | there are a lot of shoddy libraries and programs (glib's threadpool for |
422 | example) that can't properly initialise their signal masks. |
435 | example) that can't properly initialise their signal masks. |
|
|
436 | |
|
|
437 | =item C<EVFLAG_NOSIGMASK> |
|
|
438 | |
|
|
439 | When this flag is specified, then libev will avoid to modify the signal |
|
|
440 | mask. Specifically, this means you ahve to make sure signals are unblocked |
|
|
441 | when you want to receive them. |
|
|
442 | |
|
|
443 | This behaviour is useful when you want to do your own signal handling, or |
|
|
444 | want to handle signals only in specific threads and want to avoid libev |
|
|
445 | unblocking the signals. |
|
|
446 | |
|
|
447 | This flag's behaviour will become the default in future versions of libev. |
423 | |
448 | |
424 | =item C<EVBACKEND_SELECT> (value 1, portable select backend) |
449 | =item C<EVBACKEND_SELECT> (value 1, portable select backend) |
425 | |
450 | |
426 | This is your standard select(2) backend. Not I<completely> standard, as |
451 | This is your standard select(2) backend. Not I<completely> standard, as |
427 | libev tries to roll its own fd_set with no limits on the number of fds, |
452 | libev tries to roll its own fd_set with no limits on the number of fds, |
… | |
… | |
557 | =item C<EVBACKEND_PORT> (value 32, Solaris 10) |
582 | =item C<EVBACKEND_PORT> (value 32, Solaris 10) |
558 | |
583 | |
559 | This uses the Solaris 10 event port mechanism. As with everything on Solaris, |
584 | This uses the Solaris 10 event port mechanism. As with everything on Solaris, |
560 | it's really slow, but it still scales very well (O(active_fds)). |
585 | it's really slow, but it still scales very well (O(active_fds)). |
561 | |
586 | |
562 | Please note that Solaris event ports can deliver a lot of spurious |
|
|
563 | notifications, so you need to use non-blocking I/O or other means to avoid |
|
|
564 | blocking when no data (or space) is available. |
|
|
565 | |
|
|
566 | While this backend scales well, it requires one system call per active |
587 | While this backend scales well, it requires one system call per active |
567 | file descriptor per loop iteration. For small and medium numbers of file |
588 | file descriptor per loop iteration. For small and medium numbers of file |
568 | descriptors a "slow" C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> backend |
589 | descriptors a "slow" C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> backend |
569 | might perform better. |
590 | might perform better. |
570 | |
591 | |
571 | On the positive side, with the exception of the spurious readiness |
592 | On the positive side, this backend actually performed fully to |
572 | notifications, this backend actually performed fully to specification |
|
|
573 | in all tests and is fully embeddable, which is a rare feat among the |
593 | specification in all tests and is fully embeddable, which is a rare feat |
574 | OS-specific backends (I vastly prefer correctness over speed hacks). |
594 | among the OS-specific backends (I vastly prefer correctness over speed |
|
|
595 | hacks). |
|
|
596 | |
|
|
597 | On the negative side, the interface is I<bizarre>, with the event polling |
|
|
598 | function sometimes returning events to the caller even though an error |
|
|
599 | occured, but with no indication whether it has done so or not (yes, it's |
|
|
600 | even documented that way) - deadly for edge-triggered interfaces, but |
|
|
601 | fortunately libev seems to be able to work around it. |
575 | |
602 | |
576 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
603 | This backend maps C<EV_READ> and C<EV_WRITE> in the same way as |
577 | C<EVBACKEND_POLL>. |
604 | C<EVBACKEND_POLL>. |
578 | |
605 | |
579 | =item C<EVBACKEND_ALL> |
606 | =item C<EVBACKEND_ALL> |
580 | |
607 | |
581 | Try all backends (even potentially broken ones that wouldn't be tried |
608 | Try all backends (even potentially broken ones that wouldn't be tried |
582 | with C<EVFLAG_AUTO>). Since this is a mask, you can do stuff such as |
609 | with C<EVFLAG_AUTO>). Since this is a mask, you can do stuff such as |
583 | C<EVBACKEND_ALL & ~EVBACKEND_KQUEUE>. |
610 | C<EVBACKEND_ALL & ~EVBACKEND_KQUEUE>. |
584 | |
611 | |
585 | It is definitely not recommended to use this flag. |
612 | It is definitely not recommended to use this flag, use whatever |
|
|
613 | C<ev_recommended_backends ()> returns, or simply do not specify a backend |
|
|
614 | at all. |
|
|
615 | |
|
|
616 | =item C<EVBACKEND_MASK> |
|
|
617 | |
|
|
618 | Not a backend at all, but a mask to select all backend bits from a |
|
|
619 | C<flags> value, in case you want to mask out any backends from a flags |
|
|
620 | value (e.g. when modifying the C<LIBEV_FLAGS> environment variable). |
586 | |
621 | |
587 | =back |
622 | =back |
588 | |
623 | |
589 | If one or more of the backend flags are or'ed into the flags value, |
624 | If one or more of the backend flags are or'ed into the flags value, |
590 | then only these backends will be tried (in the reverse order as listed |
625 | then only these backends will be tried (in the reverse order as listed |
… | |
… | |
867 | running when nothing else is active. |
902 | running when nothing else is active. |
868 | |
903 | |
869 | ev_signal exitsig; |
904 | ev_signal exitsig; |
870 | ev_signal_init (&exitsig, sig_cb, SIGINT); |
905 | ev_signal_init (&exitsig, sig_cb, SIGINT); |
871 | ev_signal_start (loop, &exitsig); |
906 | ev_signal_start (loop, &exitsig); |
872 | evf_unref (loop); |
907 | ev_unref (loop); |
873 | |
908 | |
874 | Example: For some weird reason, unregister the above signal handler again. |
909 | Example: For some weird reason, unregister the above signal handler again. |
875 | |
910 | |
876 | ev_ref (loop); |
911 | ev_ref (loop); |
877 | ev_signal_stop (loop, &exitsig); |
912 | ev_signal_stop (loop, &exitsig); |
… | |
… | |
2319 | I<has> to modify the signal mask, at least temporarily. |
2354 | I<has> to modify the signal mask, at least temporarily. |
2320 | |
2355 | |
2321 | So I can't stress this enough: I<If you do not reset your signal mask when |
2356 | So I can't stress this enough: I<If you do not reset your signal mask when |
2322 | you expect it to be empty, you have a race condition in your code>. This |
2357 | you expect it to be empty, you have a race condition in your code>. This |
2323 | is not a libev-specific thing, this is true for most event libraries. |
2358 | is not a libev-specific thing, this is true for most event libraries. |
|
|
2359 | |
|
|
2360 | =head3 The special problem of threads signal handling |
|
|
2361 | |
|
|
2362 | POSIX threads has problematic signal handling semantics, specifically, |
|
|
2363 | a lot of functionality (sigfd, sigwait etc.) only really works if all |
|
|
2364 | threads in a process block signals, which is hard to achieve. |
|
|
2365 | |
|
|
2366 | When you want to use sigwait (or mix libev signal handling with your own |
|
|
2367 | for the same signals), you can tackle this problem by globally blocking |
|
|
2368 | all signals before creating any threads (or creating them with a fully set |
|
|
2369 | sigprocmask) and also specifying the C<EVFLAG_NOSIGMASK> when creating |
|
|
2370 | loops. Then designate one thread as "signal receiver thread" which handles |
|
|
2371 | these signals. You can pass on any signals that libev might be interested |
|
|
2372 | in by calling C<ev_feed_signal>. |
2324 | |
2373 | |
2325 | =head3 Watcher-Specific Functions and Data Members |
2374 | =head3 Watcher-Specific Functions and Data Members |
2326 | |
2375 | |
2327 | =over 4 |
2376 | =over 4 |
2328 | |
2377 | |
… | |
… | |
3175 | it by calling C<ev_async_send>, which is thread- and signal safe. |
3224 | it by calling C<ev_async_send>, which is thread- and signal safe. |
3176 | |
3225 | |
3177 | This functionality is very similar to C<ev_signal> watchers, as signals, |
3226 | This functionality is very similar to C<ev_signal> watchers, as signals, |
3178 | too, are asynchronous in nature, and signals, too, will be compressed |
3227 | too, are asynchronous in nature, and signals, too, will be compressed |
3179 | (i.e. the number of callback invocations may be less than the number of |
3228 | (i.e. the number of callback invocations may be less than the number of |
3180 | C<ev_async_sent> calls). |
3229 | C<ev_async_sent> calls). In fact, you could use signal watchers as a kind |
|
|
3230 | of "global async watchers" by using a watcher on an otherwise unused |
|
|
3231 | signal, and C<ev_feed_signal> to signal this watcher from another thread, |
|
|
3232 | even without knowing which loop owns the signal. |
3181 | |
3233 | |
3182 | Unlike C<ev_signal> watchers, C<ev_async> works with any event loop, not |
3234 | Unlike C<ev_signal> watchers, C<ev_async> works with any event loop, not |
3183 | just the default loop. |
3235 | just the default loop. |
3184 | |
3236 | |
3185 | =head3 Queueing |
3237 | =head3 Queueing |
… | |
… | |
3361 | Feed an event on the given fd, as if a file descriptor backend detected |
3413 | Feed an event on the given fd, as if a file descriptor backend detected |
3362 | the given events it. |
3414 | the given events it. |
3363 | |
3415 | |
3364 | =item ev_feed_signal_event (loop, int signum) |
3416 | =item ev_feed_signal_event (loop, int signum) |
3365 | |
3417 | |
3366 | Feed an event as if the given signal occurred (C<loop> must be the default |
3418 | Feed an event as if the given signal occurred. See also C<ev_feed_signal>, |
3367 | loop!). |
3419 | which is async-safe. |
|
|
3420 | |
|
|
3421 | =back |
|
|
3422 | |
|
|
3423 | |
|
|
3424 | =head1 COMMON OR USEFUL IDIOMS (OR BOTH) |
|
|
3425 | |
|
|
3426 | This section explains some common idioms that are not immediately |
|
|
3427 | obvious. Note that examples are sprinkled over the whole manual, and this |
|
|
3428 | section only contains stuff that wouldn't fit anywhere else. |
|
|
3429 | |
|
|
3430 | =over 4 |
|
|
3431 | |
|
|
3432 | =item Model/nested event loop invocations and exit conditions. |
|
|
3433 | |
|
|
3434 | Often (especially in GUI toolkits) there are places where you have |
|
|
3435 | I<modal> interaction, which is most easily implemented by recursively |
|
|
3436 | invoking C<ev_run>. |
|
|
3437 | |
|
|
3438 | This brings the problem of exiting - a callback might want to finish the |
|
|
3439 | main C<ev_run> call, but not the nested one (e.g. user clicked "Quit", but |
|
|
3440 | a modal "Are you sure?" dialog is still waiting), or just the nested one |
|
|
3441 | and not the main one (e.g. user clocked "Ok" in a modal dialog), or some |
|
|
3442 | other combination: In these cases, C<ev_break> will not work alone. |
|
|
3443 | |
|
|
3444 | The solution is to maintain "break this loop" variable for each C<ev_run> |
|
|
3445 | invocation, and use a loop around C<ev_run> until the condition is |
|
|
3446 | triggered, using C<EVRUN_ONCE>: |
|
|
3447 | |
|
|
3448 | // main loop |
|
|
3449 | int exit_main_loop = 0; |
|
|
3450 | |
|
|
3451 | while (!exit_main_loop) |
|
|
3452 | ev_run (EV_DEFAULT_ EVRUN_ONCE); |
|
|
3453 | |
|
|
3454 | // in a model watcher |
|
|
3455 | int exit_nested_loop = 0; |
|
|
3456 | |
|
|
3457 | while (!exit_nested_loop) |
|
|
3458 | ev_run (EV_A_ EVRUN_ONCE); |
|
|
3459 | |
|
|
3460 | To exit from any of these loops, just set the corresponding exit variable: |
|
|
3461 | |
|
|
3462 | // exit modal loop |
|
|
3463 | exit_nested_loop = 1; |
|
|
3464 | |
|
|
3465 | // exit main program, after modal loop is finished |
|
|
3466 | exit_main_loop = 1; |
|
|
3467 | |
|
|
3468 | // exit both |
|
|
3469 | exit_main_loop = exit_nested_loop = 1; |
3368 | |
3470 | |
3369 | =back |
3471 | =back |
3370 | |
3472 | |
3371 | |
3473 | |
3372 | =head1 LIBEVENT EMULATION |
3474 | =head1 LIBEVENT EMULATION |
3373 | |
3475 | |
3374 | Libev offers a compatibility emulation layer for libevent. It cannot |
3476 | Libev offers a compatibility emulation layer for libevent. It cannot |
3375 | emulate the internals of libevent, so here are some usage hints: |
3477 | emulate the internals of libevent, so here are some usage hints: |
3376 | |
3478 | |
3377 | =over 4 |
3479 | =over 4 |
|
|
3480 | |
|
|
3481 | =item * Only the libevent-1.4.1-beta API is being emulated. |
|
|
3482 | |
|
|
3483 | This was the newest libevent version available when libev was implemented, |
|
|
3484 | and is still mostly unchanged in 2010. |
3378 | |
3485 | |
3379 | =item * Use it by including <event.h>, as usual. |
3486 | =item * Use it by including <event.h>, as usual. |
3380 | |
3487 | |
3381 | =item * The following members are fully supported: ev_base, ev_callback, |
3488 | =item * The following members are fully supported: ev_base, ev_callback, |
3382 | ev_arg, ev_fd, ev_res, ev_events. |
3489 | ev_arg, ev_fd, ev_res, ev_events. |
… | |
… | |
3417 | Care has been taken to keep the overhead low. The only data member the C++ |
3524 | Care has been taken to keep the overhead low. The only data member the C++ |
3418 | classes add (compared to plain C-style watchers) is the event loop pointer |
3525 | classes add (compared to plain C-style watchers) is the event loop pointer |
3419 | that the watcher is associated with (or no additional members at all if |
3526 | that the watcher is associated with (or no additional members at all if |
3420 | you disable C<EV_MULTIPLICITY> when embedding libev). |
3527 | you disable C<EV_MULTIPLICITY> when embedding libev). |
3421 | |
3528 | |
3422 | Currently, functions, and static and non-static member functions can be |
3529 | Currently, functions, static and non-static member functions and classes |
3423 | used as callbacks. Other types should be easy to add as long as they only |
3530 | with C<operator ()> can be used as callbacks. Other types should be easy |
3424 | need one additional pointer for context. If you need support for other |
3531 | to add as long as they only need one additional pointer for context. If |
3425 | types of functors please contact the author (preferably after implementing |
3532 | you need support for other types of functors please contact the author |
3426 | it). |
3533 | (preferably after implementing it). |
3427 | |
3534 | |
3428 | Here is a list of things available in the C<ev> namespace: |
3535 | Here is a list of things available in the C<ev> namespace: |
3429 | |
3536 | |
3430 | =over 4 |
3537 | =over 4 |
3431 | |
3538 | |