|
|
1 | =encoding utf-8 |
|
|
2 | |
1 | =head1 NAME |
3 | =head1 NAME |
2 | |
4 | |
3 | libev - a high performance full-featured event loop written in C |
5 | libev - a high performance full-featured event loop written in C |
4 | |
6 | |
5 | =head1 SYNOPSIS |
7 | =head1 SYNOPSIS |
… | |
… | |
396 | |
398 | |
397 | If this flag bit is or'ed into the flag value (or the program runs setuid |
399 | If this flag bit is or'ed into the flag value (or the program runs setuid |
398 | or setgid) then libev will I<not> look at the environment variable |
400 | or setgid) then libev will I<not> look at the environment variable |
399 | C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will |
401 | C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will |
400 | override the flags completely if it is found in the environment. This is |
402 | override the flags completely if it is found in the environment. This is |
401 | useful to try out specific backends to test their performance, or to work |
403 | useful to try out specific backends to test their performance, to work |
402 | around bugs. |
404 | around bugs, or to make libev threadsafe (accessing environment variables |
|
|
405 | cannot be done in a threadsafe way, but usually it works if no other |
|
|
406 | thread modifies them). |
403 | |
407 | |
404 | =item C<EVFLAG_FORKCHECK> |
408 | =item C<EVFLAG_FORKCHECK> |
405 | |
409 | |
406 | Instead of calling C<ev_loop_fork> manually after a fork, you can also |
410 | Instead of calling C<ev_loop_fork> manually after a fork, you can also |
407 | make libev check for a fork in each iteration by enabling this flag. |
411 | make libev check for a fork in each iteration by enabling this flag. |
… | |
… | |
684 | reinitialise the kernel state for backends that have one. Despite the |
688 | reinitialise the kernel state for backends that have one. Despite the |
685 | name, you can call it anytime, but it makes most sense after forking, in |
689 | name, you can call it anytime, but it makes most sense after forking, in |
686 | the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the |
690 | the child process. You I<must> call it (or use C<EVFLAG_FORKCHECK>) in the |
687 | child before resuming or calling C<ev_run>. |
691 | child before resuming or calling C<ev_run>. |
688 | |
692 | |
689 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
693 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
690 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
694 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
691 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
695 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
692 | during fork. |
696 | during fork. |
693 | |
697 | |
694 | On the other hand, you only need to call this function in the child |
698 | On the other hand, you only need to call this function in the child |
… | |
… | |
2409 | only within the same loop, i.e. you can watch for C<SIGINT> in your |
2413 | only within the same loop, i.e. you can watch for C<SIGINT> in your |
2410 | default loop and for C<SIGIO> in another loop, but you cannot watch for |
2414 | default loop and for C<SIGIO> in another loop, but you cannot watch for |
2411 | C<SIGINT> in both the default loop and another loop at the same time. At |
2415 | C<SIGINT> in both the default loop and another loop at the same time. At |
2412 | the moment, C<SIGCHLD> is permanently tied to the default loop. |
2416 | the moment, C<SIGCHLD> is permanently tied to the default loop. |
2413 | |
2417 | |
2414 | When the first watcher gets started will libev actually register something |
2418 | Only after the first watcher for a signal is started will libev actually |
2415 | with the kernel (thus it coexists with your own signal handlers as long as |
2419 | register something with the kernel. It thus coexists with your own signal |
2416 | you don't register any with libev for the same signal). |
2420 | handlers as long as you don't register any with libev for the same signal. |
2417 | |
2421 | |
2418 | If possible and supported, libev will install its handlers with |
2422 | If possible and supported, libev will install its handlers with |
2419 | C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should |
2423 | C<SA_RESTART> (or equivalent) behaviour enabled, so system calls should |
2420 | not be unduly interrupted. If you have a problem with system calls getting |
2424 | not be unduly interrupted. If you have a problem with system calls getting |
2421 | interrupted by signals you can block all signals in an C<ev_check> watcher |
2425 | interrupted by signals you can block all signals in an C<ev_check> watcher |
… | |
… | |
3980 | Libev comes with some simplistic wrapper classes for C++ that mainly allow |
3984 | Libev comes with some simplistic wrapper classes for C++ that mainly allow |
3981 | you to use some convenience methods to start/stop watchers and also change |
3985 | you to use some convenience methods to start/stop watchers and also change |
3982 | the callback model to a model using method callbacks on objects. |
3986 | the callback model to a model using method callbacks on objects. |
3983 | |
3987 | |
3984 | To use it, |
3988 | To use it, |
3985 | |
3989 | |
3986 | #include <ev++.h> |
3990 | #include <ev++.h> |
3987 | |
3991 | |
3988 | This automatically includes F<ev.h> and puts all of its definitions (many |
3992 | This automatically includes F<ev.h> and puts all of its definitions (many |
3989 | of them macros) into the global namespace. All C++ specific things are |
3993 | of them macros) into the global namespace. All C++ specific things are |
3990 | put into the C<ev> namespace. It should support all the same embedding |
3994 | put into the C<ev> namespace. It should support all the same embedding |
… | |
… | |
4618 | different cpus (or different cpu cores). This reduces dependencies |
4622 | different cpus (or different cpu cores). This reduces dependencies |
4619 | and makes libev faster. |
4623 | and makes libev faster. |
4620 | |
4624 | |
4621 | =item EV_NO_THREADS |
4625 | =item EV_NO_THREADS |
4622 | |
4626 | |
4623 | If defined to be C<1>, libev will assume that it will never be called |
4627 | If defined to be C<1>, libev will assume that it will never be called from |
4624 | from different threads, which is a stronger assumption than C<EV_NO_SMP>, |
4628 | different threads (that includes signal handlers), which is a stronger |
4625 | above. This reduces dependencies and makes libev faster. |
4629 | assumption than C<EV_NO_SMP>, above. This reduces dependencies and makes |
|
|
4630 | libev faster. |
4626 | |
4631 | |
4627 | =item EV_ATOMIC_T |
4632 | =item EV_ATOMIC_T |
4628 | |
4633 | |
4629 | Libev requires an integer type (suitable for storing C<0> or C<1>) whose |
4634 | Libev requires an integer type (suitable for storing C<0> or C<1>) whose |
4630 | access is atomic with respect to other threads or signal contexts. No |
4635 | access is atomic with respect to other threads or signal contexts. No |
… | |
… | |
5426 | =over 4 |
5431 | =over 4 |
5427 | |
5432 | |
5428 | =item C<EV_COMPAT3> backwards compatibility mechanism |
5433 | =item C<EV_COMPAT3> backwards compatibility mechanism |
5429 | |
5434 | |
5430 | The backward compatibility mechanism can be controlled by |
5435 | The backward compatibility mechanism can be controlled by |
5431 | C<EV_COMPAT3>. See L</PREPROCESSOR SYMBOLS/MACROS> in the L</EMBEDDING> |
5436 | C<EV_COMPAT3>. See L</"PREPROCESSOR SYMBOLS/MACROS"> in the L</EMBEDDING> |
5432 | section. |
5437 | section. |
5433 | |
5438 | |
5434 | =item C<ev_default_destroy> and C<ev_default_fork> have been removed |
5439 | =item C<ev_default_destroy> and C<ev_default_fork> have been removed |
5435 | |
5440 | |
5436 | These calls can be replaced easily by their C<ev_loop_xxx> counterparts: |
5441 | These calls can be replaced easily by their C<ev_loop_xxx> counterparts: |