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

Comparing libev/ev.pod (file contents):
Revision 1.440 by root, Tue Jan 31 09:31:43 2017 UTC vs.
Revision 1.441 by root, Thu Jul 13 10:46:52 2017 UTC

… …
411make libev check for a fork in each iteration by enabling this flag. 411make libev check for a fork in each iteration by enabling this flag.
412 412
413This works by calling C<getpid ()> on every iteration of the loop, 413This works by calling C<getpid ()> on every iteration of the loop,
414and thus this might slow down your event loop if you do a lot of loop 414and thus this might slow down your event loop if you do a lot of loop
415iterations and little real work, but is usually not noticeable (on my 415iterations and little real work, but is usually not noticeable (on my
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
417without a system call and thus I<very> fast, but my GNU/Linux system also has 417sequence without a system call and thus I<very> fast, but my GNU/Linux
418C<pthread_atfork> which is even faster). 418system also has C<pthread_atfork> which is even faster). (Update: glibc
419versions 2.25 apparently removed the C<getpid> optimisation again).
419 420
420The big advantage of this flag is that you can forget about fork (and 421The big advantage of this flag is that you can forget about fork (and
421forget about forgetting to tell libev about forking, although you still 422forget about forgetting to tell libev about forking, although you still
422have to ignore C<SIGPIPE>) when you use this flag. 423have to ignore C<SIGPIPE>) when you use this flag.
423 424

Diff Legend

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