… | |
… | |
345 | useful to try out specific backends to test their performance, or to work |
345 | useful to try out specific backends to test their performance, or to work |
346 | around bugs. |
346 | around bugs. |
347 | |
347 | |
348 | =item C<EVFLAG_FORKCHECK> |
348 | =item C<EVFLAG_FORKCHECK> |
349 | |
349 | |
350 | Instead of calling C<ev_default_fork> or C<ev_loop_fork> manually after |
350 | Instead of calling C<ev_loop_fork> manually after a fork, you can also |
351 | a fork, you can also make libev check for a fork in each iteration by |
351 | make libev check for a fork in each iteration by enabling this flag. |
352 | enabling this flag. |
|
|
353 | |
352 | |
354 | This works by calling C<getpid ()> on every iteration of the loop, |
353 | This works by calling C<getpid ()> on every iteration of the loop, |
355 | and thus this might slow down your event loop if you do a lot of loop |
354 | and thus this might slow down your event loop if you do a lot of loop |
356 | iterations and little real work, but is usually not noticeable (on my |
355 | iterations and little real work, but is usually not noticeable (on my |
357 | GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence |
356 | GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence |
… | |
… | |
567 | ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE); |
566 | ev_default_loop (ev_recommended_backends () | EVBACKEND_KQUEUE); |
568 | |
567 | |
569 | =item struct ev_loop *ev_loop_new (unsigned int flags) |
568 | =item struct ev_loop *ev_loop_new (unsigned int flags) |
570 | |
569 | |
571 | Similar to C<ev_default_loop>, but always creates a new event loop that is |
570 | Similar to C<ev_default_loop>, but always creates a new event loop that is |
572 | always distinct from the default loop. Unlike the default loop, it cannot |
571 | always distinct from the default loop. |
573 | handle signal and child watchers, and attempts to do so will be greeted by |
|
|
574 | undefined behaviour (or a failed assertion if assertions are enabled). |
|
|
575 | |
572 | |
576 | Note that this function I<is> thread-safe, and the recommended way to use |
573 | Note that this function I<is> thread-safe, and one common way to use |
577 | libev with threads is indeed to create one loop per thread, and using the |
574 | libev with threads is indeed to create one loop per thread, and using the |
578 | default loop in the "main" or "initial" thread. |
575 | default loop in the "main" or "initial" thread. |
579 | |
576 | |
580 | Example: Try to create a event loop that uses epoll and nothing else. |
577 | Example: Try to create a event loop that uses epoll and nothing else. |
581 | |
578 | |
… | |
… | |
583 | if (!epoller) |
580 | if (!epoller) |
584 | fatal ("no epoll found here, maybe it hides under your chair"); |
581 | fatal ("no epoll found here, maybe it hides under your chair"); |
585 | |
582 | |
586 | =item ev_default_destroy () |
583 | =item ev_default_destroy () |
587 | |
584 | |
588 | Destroys the default loop again (frees all memory and kernel state |
585 | Destroys the default loop (frees all memory and kernel state etc.). None |
589 | etc.). None of the active event watchers will be stopped in the normal |
586 | of the active event watchers will be stopped in the normal sense, so |
590 | sense, so e.g. C<ev_is_active> might still return true. It is your |
587 | e.g. C<ev_is_active> might still return true. It is your responsibility to |
591 | responsibility to either stop all watchers cleanly yourself I<before> |
588 | either stop all watchers cleanly yourself I<before> calling this function, |
592 | calling this function, or cope with the fact afterwards (which is usually |
589 | or cope with the fact afterwards (which is usually the easiest thing, you |
593 | the easiest thing, you can just ignore the watchers and/or C<free ()> them |
590 | can just ignore the watchers and/or C<free ()> them for example). |
594 | for example). |
|
|
595 | |
591 | |
596 | Note that certain global state, such as signal state (and installed signal |
592 | Note that certain global state, such as signal state (and installed signal |
597 | handlers), will not be freed by this function, and related watchers (such |
593 | handlers), will not be freed by this function, and related watchers (such |
598 | as signal and child watchers) would need to be stopped manually. |
594 | as signal and child watchers) would need to be stopped manually. |
599 | |
595 | |
… | |
… | |
614 | name, you can call it anytime, but it makes most sense after forking, in |
610 | name, you can call it anytime, but it makes most sense after forking, in |
615 | the child process (or both child and parent, but that again makes little |
611 | the child process (or both child and parent, but that again makes little |
616 | sense). You I<must> call it in the child before using any of the libev |
612 | sense). You I<must> call it in the child before using any of the libev |
617 | functions, and it will only take effect at the next C<ev_loop> iteration. |
613 | functions, and it will only take effect at the next C<ev_loop> iteration. |
618 | |
614 | |
|
|
615 | Again, you I<have> to call it on I<any> loop that you want to re-use after |
|
|
616 | a fork, I<even if you do not plan to use the loop in the parent>. This is |
|
|
617 | because some kernel interfaces *cough* I<kqueue> *cough* do funny things |
|
|
618 | during fork. |
|
|
619 | |
619 | On the other hand, you only need to call this function in the child |
620 | On the other hand, you only need to call this function in the child |
620 | process if and only if you want to use the event library in the child. If |
621 | process if and only if you want to use the event loop in the child. If you |
621 | you just fork+exec, you don't have to call it at all. |
622 | just fork+exec or create a new loop in the child, you don't have to call |
|
|
623 | it at all. |
622 | |
624 | |
623 | The function itself is quite fast and it's usually not a problem to call |
625 | The function itself is quite fast and it's usually not a problem to call |
624 | it just in case after a fork. To make this easy, the function will fit in |
626 | it just in case after a fork. To make this easy, the function will fit in |
625 | quite nicely into a call to C<pthread_atfork>: |
627 | quite nicely into a call to C<pthread_atfork>: |
626 | |
628 | |
… | |
… | |
628 | |
630 | |
629 | =item ev_loop_fork (loop) |
631 | =item ev_loop_fork (loop) |
630 | |
632 | |
631 | Like C<ev_default_fork>, but acts on an event loop created by |
633 | Like C<ev_default_fork>, but acts on an event loop created by |
632 | C<ev_loop_new>. Yes, you have to call this on every allocated event loop |
634 | C<ev_loop_new>. Yes, you have to call this on every allocated event loop |
633 | after fork that you want to re-use in the child, and how you do this is |
635 | after fork that you want to re-use in the child, and how you keep track of |
634 | entirely your own problem. |
636 | them is entirely your own problem. |
635 | |
637 | |
636 | =item int ev_is_default_loop (loop) |
638 | =item int ev_is_default_loop (loop) |
637 | |
639 | |
638 | Returns true when the given loop is, in fact, the default loop, and false |
640 | Returns true when the given loop is, in fact, the default loop, and false |
639 | otherwise. |
641 | otherwise. |
640 | |
642 | |
641 | =item unsigned int ev_loop_count (loop) |
643 | =item unsigned int ev_iteration (loop) |
642 | |
644 | |
643 | Returns the count of loop iterations for the loop, which is identical to |
645 | Returns the current iteration count for the loop, which is identical to |
644 | the number of times libev did poll for new events. It starts at C<0> and |
646 | the number of times libev did poll for new events. It starts at C<0> and |
645 | happily wraps around with enough iterations. |
647 | happily wraps around with enough iterations. |
646 | |
648 | |
647 | This value can sometimes be useful as a generation counter of sorts (it |
649 | This value can sometimes be useful as a generation counter of sorts (it |
648 | "ticks" the number of loop iterations), as it roughly corresponds with |
650 | "ticks" the number of loop iterations), as it roughly corresponds with |
649 | C<ev_prepare> and C<ev_check> calls. |
651 | C<ev_prepare> and C<ev_check> calls - and is incremented between the |
|
|
652 | prepare and check phases. |
650 | |
653 | |
651 | =item unsigned int ev_loop_depth (loop) |
654 | =item unsigned int ev_depth (loop) |
652 | |
655 | |
653 | Returns the number of times C<ev_loop> was entered minus the number of |
656 | Returns the number of times C<ev_loop> was entered minus the number of |
654 | times C<ev_loop> was exited, in other words, the recursion depth. |
657 | times C<ev_loop> was exited, in other words, the recursion depth. |
655 | |
658 | |
656 | Outside C<ev_loop>, this number is zero. In a callback, this number is |
659 | Outside C<ev_loop>, this number is zero. In a callback, this number is |
657 | C<1>, unless C<ev_loop> was invoked recursively (or from another thread), |
660 | C<1>, unless C<ev_loop> was invoked recursively (or from another thread), |
658 | in which case it is higher. |
661 | in which case it is higher. |
659 | |
662 | |
660 | Leaving C<ev_loop> abnormally (setjmp/longjmp, cancelling the thread |
663 | Leaving C<ev_loop> abnormally (setjmp/longjmp, cancelling the thread |
661 | etc.), doesn't count as exit. |
664 | etc.), doesn't count as "exit" - consider this as a hint to avoid such |
|
|
665 | ungentleman behaviour unless it's really convenient. |
662 | |
666 | |
663 | =item unsigned int ev_backend (loop) |
667 | =item unsigned int ev_backend (loop) |
664 | |
668 | |
665 | Returns one of the C<EVBACKEND_*> flags indicating the event backend in |
669 | Returns one of the C<EVBACKEND_*> flags indicating the event backend in |
666 | use. |
670 | use. |
… | |
… | |
4621 | involves iterating over all running async watchers or all signal numbers. |
4625 | involves iterating over all running async watchers or all signal numbers. |
4622 | |
4626 | |
4623 | =back |
4627 | =back |
4624 | |
4628 | |
4625 | |
4629 | |
4626 | =head1 PORTING FROM 3.X TO 4.X |
4630 | =head1 PORTING FROM LIBEV 3.X TO 4.X |
4627 | |
4631 | |
4628 | The major version 4 introduced some minor incompatible changes to the API. |
4632 | The major version 4 introduced some minor incompatible changes to the API. |
4629 | |
4633 | |
|
|
4634 | At the moment, the C<ev.h> header file tries to implement superficial |
|
|
4635 | compatibility, so most programs should still compile. Those might be |
|
|
4636 | removed in later versions of libev, so better update early than late. |
|
|
4637 | |
4630 | =over 4 |
4638 | =over 4 |
4631 | |
4639 | |
|
|
4640 | =item C<ev_loop_count> renamed to C<ev_iteration> |
|
|
4641 | |
|
|
4642 | =item C<ev_loop_depth> renamed to C<ev_depth> |
|
|
4643 | |
|
|
4644 | =item C<ev_loop_verify> renamed to C<ev_verify> |
|
|
4645 | |
|
|
4646 | Most functions working on C<struct ev_loop> objects don't have an |
|
|
4647 | C<ev_loop_> prefix, so it was removed. Note that C<ev_loop_fork> is |
|
|
4648 | still called C<ev_loop_fork> because it would otherwise clash with the |
|
|
4649 | C<ev_frok> typedef. |
|
|
4650 | |
4632 | =item C<EV_TIMEOUT> replaced by C<EV_TIMER> in C<revents> |
4651 | =item C<EV_TIMEOUT> renamed to C<EV_TIMER> in C<revents> |
4633 | |
4652 | |
4634 | This is a simple rename - all other watcher types use their name |
4653 | This is a simple rename - all other watcher types use their name |
4635 | as revents flag, and now C<ev_timer> does, too. |
4654 | as revents flag, and now C<ev_timer> does, too. |
4636 | |
4655 | |
4637 | Both C<EV_TIMER> and C<EV_TIMEOUT> symbols were present in 3.x versions |
4656 | Both C<EV_TIMER> and C<EV_TIMEOUT> symbols were present in 3.x versions |