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