[ViewVC] Diff of: cvs/IO-AIO/AIO.pm

Comparing IO-AIO/AIO.pm (file contents):
Revision 1.72 by root, Tue Oct 24 14:25:53 2006 UTC vs.
Revision 1.73 by root, Tue Oct 24 16:35:04 2006 UTC

 request/result processing, while the child frees the request/result queue
 (so that the requests started before the fork will only be handled in the
 parent). Threads will be started on demand until the limit set in the
 parent process has been reached again.
-Temporary memory that was allocated for request processing is not
-reclaimed in the child, however. While this is possible in some cases, it
-is almost impossible in others (threads are evil you know), so you will
-have to live with it. This is around 64k buffer (for sendfile, readahead
-emulation) + the size of the directory being scanned (readdir).
 In short: the parent will, after a short pause, continue as if fork had
 not been called, while the child will act as if IO::AIO has not been used
 yet.
 =head2 MEMORY USAGE
 temporary buffers, and each thread requires a stack and other data
 structures (usually around 16k-128k, depending on the OS).
 =head1 KNOWN BUGS
-See FORK BEHAVIOUR, above.
+Known bugs will be fixed in the next release.
 =head1 SEE ALSO
 L<Coro::AIO>.

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