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

Comparing libev/ev.pod (file contents):
Revision 1.434 by root, Tue May 6 13:24:39 2014 UTC vs.
Revision 1.437 by root, Sun Oct 11 15:55:48 2015 UTC

… …
416GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence 416GNU/Linux system for example, C<getpid> is actually a simple 5-insn sequence
417without a system call and thus I<very> fast, but my GNU/Linux system also has 417without a system call and thus I<very> fast, but my GNU/Linux system also has
418C<pthread_atfork> which is even faster). 418C<pthread_atfork> which is even faster).
419 419
420The big advantage of this flag is that you can forget about fork (and 420The big advantage of this flag is that you can forget about fork (and
421forget about forgetting to tell libev about forking) when you use this 421forget about forgetting to tell libev about forking, although you still
422flag. 422have to ignore C<SIGPIPE>) when you use this flag.
423 423
424This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS> 424This flag setting cannot be overridden or specified in the C<LIBEV_FLAGS>
425environment variable. 425environment variable.
426 426
427=item C<EVFLAG_NOINOTIFY> 427=item C<EVFLAG_NOINOTIFY>
… …
688to reinitialise the kernel state for backends that have one. Despite 688to reinitialise the kernel state for backends that have one. Despite
689the name, you can call it anytime you are allowed to start or stop 689the name, you can call it anytime you are allowed to start or stop
690watchers (except inside an C<ev_prepare> callback), but it makes most 690watchers (except inside an C<ev_prepare> callback), but it makes most
691sense after forking, in the child process. You I<must> call it (or use 691sense after forking, in the child process. You I<must> call it (or use
692C<EVFLAG_FORKCHECK>) in the child before resuming or calling C<ev_run>. 692C<EVFLAG_FORKCHECK>) in the child before resuming or calling C<ev_run>.
693
694In addition, if you want to reuse a loop (via this function or
695C<EVFLAG_FORKCHECK>), you I<also> have to ignore C<SIGPIPE>.
693 696
694Again, you I<have> to call it on I<any> loop that you want to re-use after 697Again, you I<have> to call it on I<any> loop that you want to re-use after
695a fork, I<even if you do not plan to use the loop in the parent>. This is 698a fork, I<even if you do not plan to use the loop in the parent>. This is
696because some kernel interfaces *cough* I<kqueue> *cough* do funny things 699because some kernel interfaces *cough* I<kqueue> *cough* do funny things
697during fork. 700during fork.
… …
3900To embed libev, see L</EMBEDDING>, but in short, it's easiest to create two 3903To embed libev, see L</EMBEDDING>, but in short, it's easiest to create two
3901files, F<my_ev.h> and F<my_ev.c> that include the respective libev files: 3904files, F<my_ev.h> and F<my_ev.c> that include the respective libev files:
3902 3905
3903 // my_ev.h 3906 // my_ev.h
3904 #define EV_CB_DECLARE(type) struct my_coro *cb; 3907 #define EV_CB_DECLARE(type) struct my_coro *cb;
3905 #define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb); 3908 #define EV_CB_INVOKE(watcher) switch_to ((watcher)->cb)
3906 #include "../libev/ev.h" 3909 #include "../libev/ev.h"
3907 3910
3908 // my_ev.c 3911 // my_ev.c
3909 #define EV_H "my_ev.h" 3912 #define EV_H "my_ev.h"
3910 #include "../libev/ev.c" 3913 #include "../libev/ev.c"

Diff Legend

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