… | |
… | |
349 | |
349 | |
350 | 1; |
350 | 1; |
351 | |
351 | |
352 | =head2 FORK BEHAVIOUR |
352 | =head2 FORK BEHAVIOUR |
353 | |
353 | |
354 | IO::AIO handles all outstanding AIO requests before the fork, destroys all |
354 | Before the fork IO::AIO first handles all outstanding requests - if other |
355 | AIO threads, and recreates them in both the parent and the child after the |
355 | threads add requests during this period, this time is prolonged. It then |
356 | fork. |
356 | enters a quiescent state where no requests can be added in other threads |
357 | |
357 | and no results will be processed. After the fork the parent simply leaves |
|
|
358 | the quiescent state and continues request processing, while the child will |
|
|
359 | free the request and result queue and start the same number of threads as |
|
|
360 | were in use by the parent. |
358 | |
361 | |
359 | =head1 SEE ALSO |
362 | =head1 SEE ALSO |
360 | |
363 | |
361 | L<Coro>, L<Linux::AIO>. |
364 | L<Coro>, L<Linux::AIO>. |
362 | |
365 | |