… | |
… | |
168 | use common::sense; |
168 | use common::sense; |
169 | |
169 | |
170 | use base 'Exporter'; |
170 | use base 'Exporter'; |
171 | |
171 | |
172 | BEGIN { |
172 | BEGIN { |
173 | our $VERSION = '3.9'; |
173 | our $VERSION = '4.0'; |
174 | |
174 | |
175 | our @AIO_REQ = qw(aio_sendfile aio_read aio_write aio_open aio_close |
175 | our @AIO_REQ = qw(aio_sendfile aio_read aio_write aio_open aio_close |
176 | aio_stat aio_lstat aio_unlink aio_rmdir aio_readdir aio_readdirx |
176 | aio_stat aio_lstat aio_unlink aio_rmdir aio_readdir aio_readdirx |
177 | aio_scandir aio_symlink aio_readlink aio_sync aio_fsync |
177 | aio_scandir aio_symlink aio_readlink aio_realpath aio_sync |
178 | aio_fdatasync aio_sync_file_range aio_pathsync aio_readahead |
178 | aio_fsync aio_syncfs aio_fdatasync aio_sync_file_range aio_fallocate |
|
|
179 | aio_pathsync aio_readahead |
179 | aio_rename aio_link aio_move aio_copy aio_group |
180 | aio_rename aio_link aio_move aio_copy aio_group |
180 | aio_nop aio_mknod aio_load aio_rmtree aio_mkdir aio_chown |
181 | aio_nop aio_mknod aio_load aio_rmtree aio_mkdir aio_chown |
181 | aio_chmod aio_utime aio_truncate |
182 | aio_chmod aio_utime aio_truncate |
182 | aio_msync aio_mtouch aio_mlock aio_mlockall |
183 | aio_msync aio_mtouch aio_mlock aio_mlockall |
183 | aio_statvfs); |
184 | aio_statvfs |
|
|
185 | aio_wd); |
184 | |
186 | |
185 | our @EXPORT = (@AIO_REQ, qw(aioreq_pri aioreq_nice)); |
187 | our @EXPORT = (@AIO_REQ, qw(aioreq_pri aioreq_nice)); |
186 | our @EXPORT_OK = qw(poll_fileno poll_cb poll_wait flush |
188 | our @EXPORT_OK = qw(poll_fileno poll_cb poll_wait flush |
187 | min_parallel max_parallel max_idle idle_timeout |
189 | min_parallel max_parallel max_idle idle_timeout |
188 | nreqs nready npending nthreads |
190 | nreqs nready npending nthreads |
… | |
… | |
204 | |
206 | |
205 | This section simply lists the prototypes of the most important functions |
207 | This section simply lists the prototypes of the most important functions |
206 | for quick reference. See the following sections for function-by-function |
208 | for quick reference. See the following sections for function-by-function |
207 | documentation. |
209 | documentation. |
208 | |
210 | |
|
|
211 | aio_wd $pathname, $callback->($wd) |
209 | aio_open $pathname, $flags, $mode, $callback->($fh) |
212 | aio_open $pathname, $flags, $mode, $callback->($fh) |
210 | aio_close $fh, $callback->($status) |
213 | aio_close $fh, $callback->($status) |
211 | aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
214 | aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
212 | aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
215 | aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
213 | aio_sendfile $out_fh, $in_fh, $in_offset, $length, $callback->($retval) |
216 | aio_sendfile $out_fh, $in_fh, $in_offset, $length, $callback->($retval) |
… | |
… | |
222 | aio_unlink $pathname, $callback->($status) |
225 | aio_unlink $pathname, $callback->($status) |
223 | aio_mknod $path, $mode, $dev, $callback->($status) |
226 | aio_mknod $path, $mode, $dev, $callback->($status) |
224 | aio_link $srcpath, $dstpath, $callback->($status) |
227 | aio_link $srcpath, $dstpath, $callback->($status) |
225 | aio_symlink $srcpath, $dstpath, $callback->($status) |
228 | aio_symlink $srcpath, $dstpath, $callback->($status) |
226 | aio_readlink $path, $callback->($link) |
229 | aio_readlink $path, $callback->($link) |
|
|
230 | aio_realpath $path, $callback->($link) |
227 | aio_rename $srcpath, $dstpath, $callback->($status) |
231 | aio_rename $srcpath, $dstpath, $callback->($status) |
228 | aio_mkdir $pathname, $mode, $callback->($status) |
232 | aio_mkdir $pathname, $mode, $callback->($status) |
229 | aio_rmdir $pathname, $callback->($status) |
233 | aio_rmdir $pathname, $callback->($status) |
230 | aio_readdir $pathname, $callback->($entries) |
234 | aio_readdir $pathname, $callback->($entries) |
231 | aio_readdirx $pathname, $flags, $callback->($entries, $flags) |
235 | aio_readdirx $pathname, $flags, $callback->($entries, $flags) |
… | |
… | |
235 | aio_copy $srcpath, $dstpath, $callback->($status) |
239 | aio_copy $srcpath, $dstpath, $callback->($status) |
236 | aio_move $srcpath, $dstpath, $callback->($status) |
240 | aio_move $srcpath, $dstpath, $callback->($status) |
237 | aio_scandir $path, $maxreq, $callback->($dirs, $nondirs) |
241 | aio_scandir $path, $maxreq, $callback->($dirs, $nondirs) |
238 | aio_rmtree $path, $callback->($status) |
242 | aio_rmtree $path, $callback->($status) |
239 | aio_sync $callback->($status) |
243 | aio_sync $callback->($status) |
|
|
244 | aio_syncfs $fh, $callback->($status) |
240 | aio_fsync $fh, $callback->($status) |
245 | aio_fsync $fh, $callback->($status) |
241 | aio_fdatasync $fh, $callback->($status) |
246 | aio_fdatasync $fh, $callback->($status) |
242 | aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status) |
247 | aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status) |
243 | aio_pathsync $path, $callback->($status) |
248 | aio_pathsync $path, $callback->($status) |
244 | aio_msync $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status) |
249 | aio_msync $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status) |
… | |
… | |
436 | |
441 | |
437 | Tries to copy C<$length> bytes from C<$in_fh> to C<$out_fh>. It starts |
442 | Tries to copy C<$length> bytes from C<$in_fh> to C<$out_fh>. It starts |
438 | reading at byte offset C<$in_offset>, and starts writing at the current |
443 | reading at byte offset C<$in_offset>, and starts writing at the current |
439 | file offset of C<$out_fh>. Because of that, it is not safe to issue more |
444 | file offset of C<$out_fh>. Because of that, it is not safe to issue more |
440 | than one C<aio_sendfile> per C<$out_fh>, as they will interfere with each |
445 | than one C<aio_sendfile> per C<$out_fh>, as they will interfere with each |
441 | other. |
446 | other. The same C<$in_fh> works fine though, as this function does not |
|
|
447 | move or use the file offset of C<$in_fh>. |
442 | |
448 | |
443 | Please note that C<aio_sendfile> can read more bytes from C<$in_fh> than |
449 | Please note that C<aio_sendfile> can read more bytes from C<$in_fh> than |
444 | are written, and there is no way to find out how many bytes have been read |
450 | are written, and there is no way to find out how many more bytes have been |
445 | from C<aio_sendfile> alone, as C<aio_sendfile> only provides the number of |
451 | read from C<aio_sendfile> alone, as C<aio_sendfile> only provides the |
446 | bytes written to C<$out_fh>. Only if the result value equals C<$length> |
452 | number of bytes written to C<$out_fh>. Only if the result value equals |
447 | one can assume that C<$length> bytes have been read. |
453 | C<$length> one can assume that C<$length> bytes have been read. |
448 | |
454 | |
449 | Unlike with other C<aio_> functions, it makes a lot of sense to use |
455 | Unlike with other C<aio_> functions, it makes a lot of sense to use |
450 | C<aio_sendfile> on non-blocking sockets, as long as one end (typically |
456 | C<aio_sendfile> on non-blocking sockets, as long as one end (typically |
451 | the C<$in_fh>) is a file - the file I/O will then be asynchronous, while |
457 | the C<$in_fh>) is a file - the file I/O will then be asynchronous, while |
452 | the socket I/O will be non-blocking. Note, however, that you can run into |
458 | the socket I/O will be non-blocking. Note, however, that you can run |
453 | a trap where C<aio_sendfile> reads some data with readahead, then fails |
459 | into a trap where C<aio_sendfile> reads some data with readahead, then |
454 | to write all data, and when the socket is ready the next time, the data |
460 | fails to write all data, and when the socket is ready the next time, the |
455 | in the cache is already lost, forcing C<aio_sendfile> to again hit the |
461 | data in the cache is already lost, forcing C<aio_sendfile> to again hit |
456 | disk. Explicit C<aio_read> + C<aio_write> let's you control resource usage |
462 | the disk. Explicit C<aio_read> + C<aio_write> let's you better control |
457 | much better. |
463 | resource usage. |
458 | |
464 | |
459 | This call tries to make use of a native C<sendfile> syscall to provide |
465 | This call tries to make use of a native C<sendfile>-like syscall to |
460 | zero-copy operation. For this to work, C<$out_fh> should refer to a |
466 | provide zero-copy operation. For this to work, C<$out_fh> should refer to |
461 | socket, and C<$in_fh> should refer to an mmap'able file. |
467 | a socket, and C<$in_fh> should refer to an mmap'able file. |
462 | |
468 | |
463 | If a native sendfile cannot be found or it fails with C<ENOSYS>, |
469 | If a native sendfile cannot be found or it fails with C<ENOSYS>, |
464 | C<ENOTSUP>, C<EOPNOTSUPP>, C<EAFNOSUPPORT>, C<EPROTOTYPE> or C<ENOTSOCK>, |
470 | C<EINVAL>, C<ENOTSUP>, C<EOPNOTSUPP>, C<EAFNOSUPPORT>, C<EPROTOTYPE> or |
465 | it will be emulated, so you can call C<aio_sendfile> on any type of |
471 | C<ENOTSOCK>, it will be emulated, so you can call C<aio_sendfile> on any |
466 | filehandle regardless of the limitations of the operating system. |
472 | type of filehandle regardless of the limitations of the operating system. |
|
|
473 | |
|
|
474 | As native sendfile syscalls (as practically any non-POSIX interface hacked |
|
|
475 | together in a hurry to improve benchmark numbers) tend to be rather buggy |
|
|
476 | on many systems, this implementation tries to work around some known bugs |
|
|
477 | in Linux and FreeBSD kernels (probably others, too), but that might fail, |
|
|
478 | so you really really should check the return value of C<aio_sendfile> - |
|
|
479 | fewre bytes than expected might have been transferred. |
467 | |
480 | |
468 | |
481 | |
469 | =item aio_readahead $fh,$offset,$length, $callback->($retval) |
482 | =item aio_readahead $fh,$offset,$length, $callback->($retval) |
470 | |
483 | |
471 | C<aio_readahead> populates the page cache with data from a file so that |
484 | C<aio_readahead> populates the page cache with data from a file so that |
… | |
… | |
635 | Asynchronously read the symlink specified by C<$path> and pass it to |
648 | Asynchronously read the symlink specified by C<$path> and pass it to |
636 | the callback. If an error occurs, nothing or undef gets passed to the |
649 | the callback. If an error occurs, nothing or undef gets passed to the |
637 | callback. |
650 | callback. |
638 | |
651 | |
639 | |
652 | |
|
|
653 | =item aio_realpath $path, $callback->($path) |
|
|
654 | |
|
|
655 | Asynchronously make the path absolute and resolve any symlinks in |
|
|
656 | C<$path>. The resulting path only consists of directories (Same as |
|
|
657 | L<Cwd::realpath>). |
|
|
658 | |
|
|
659 | This request can be used to get the absolute path of the current working |
|
|
660 | directory by passing it a path of F<.> (a single dot). |
|
|
661 | |
|
|
662 | |
640 | =item aio_rename $srcpath, $dstpath, $callback->($status) |
663 | =item aio_rename $srcpath, $dstpath, $callback->($status) |
641 | |
664 | |
642 | Asynchronously rename the object at C<$srcpath> to C<$dstpath>, just as |
665 | Asynchronously rename the object at C<$srcpath> to C<$dstpath>, just as |
643 | rename(2) and call the callback with the result code. |
666 | rename(2) and call the callback with the result code. |
644 | |
667 | |
… | |
… | |
666 | array-ref with the filenames. |
689 | array-ref with the filenames. |
667 | |
690 | |
668 | |
691 | |
669 | =item aio_readdirx $pathname, $flags, $callback->($entries, $flags) |
692 | =item aio_readdirx $pathname, $flags, $callback->($entries, $flags) |
670 | |
693 | |
671 | Quite similar to C<aio_readdir>, but the C<$flags> argument allows to tune |
694 | Quite similar to C<aio_readdir>, but the C<$flags> argument allows one to |
672 | behaviour and output format. In case of an error, C<$entries> will be |
695 | tune behaviour and output format. In case of an error, C<$entries> will be |
673 | C<undef>. |
696 | C<undef>. |
674 | |
697 | |
675 | The flags are a combination of the following constants, ORed together (the |
698 | The flags are a combination of the following constants, ORed together (the |
676 | flags will also be passed to the callback, possibly modified): |
699 | flags will also be passed to the callback, possibly modified): |
677 | |
700 | |
… | |
… | |
724 | |
747 | |
725 | =item IO::AIO::READDIR_FOUND_UNKNOWN |
748 | =item IO::AIO::READDIR_FOUND_UNKNOWN |
726 | |
749 | |
727 | This flag should not be set when calling C<aio_readdirx>. Instead, it |
750 | This flag should not be set when calling C<aio_readdirx>. Instead, it |
728 | is being set by C<aio_readdirx>, when any of the C<$type>'s found were |
751 | is being set by C<aio_readdirx>, when any of the C<$type>'s found were |
729 | C<IO::AIO::DT_UNKNOWN>. The absense of this flag therefore indicates that all |
752 | C<IO::AIO::DT_UNKNOWN>. The absence of this flag therefore indicates that all |
730 | C<$type>'s are known, which can be used to speed up some algorithms. |
753 | C<$type>'s are known, which can be used to speed up some algorithms. |
731 | |
754 | |
732 | =back |
755 | =back |
733 | |
756 | |
734 | |
757 | |
… | |
… | |
862 | if ($_[0] && $! == EXDEV) { |
885 | if ($_[0] && $! == EXDEV) { |
863 | aioreq_pri $pri; |
886 | aioreq_pri $pri; |
864 | add $grp aio_copy $src, $dst, sub { |
887 | add $grp aio_copy $src, $dst, sub { |
865 | $grp->result ($_[0]); |
888 | $grp->result ($_[0]); |
866 | |
889 | |
867 | if (!$_[0]) { |
890 | unless ($_[0]) { |
868 | aioreq_pri $pri; |
891 | aioreq_pri $pri; |
869 | add $grp aio_unlink $src; |
892 | add $grp aio_unlink $src; |
870 | } |
893 | } |
871 | }; |
894 | }; |
872 | } else { |
895 | } else { |
… | |
… | |
916 | Then entries will be sorted into likely directories a non-initial dot |
939 | Then entries will be sorted into likely directories a non-initial dot |
917 | currently) and likely non-directories (see C<aio_readdirx>). Then every |
940 | currently) and likely non-directories (see C<aio_readdirx>). Then every |
918 | entry plus an appended C</.> will be C<stat>'ed, likely directories first, |
941 | entry plus an appended C</.> will be C<stat>'ed, likely directories first, |
919 | in order of their inode numbers. If that succeeds, it assumes that the |
942 | in order of their inode numbers. If that succeeds, it assumes that the |
920 | entry is a directory or a symlink to directory (which will be checked |
943 | entry is a directory or a symlink to directory (which will be checked |
921 | seperately). This is often faster than stat'ing the entry itself because |
944 | separately). This is often faster than stat'ing the entry itself because |
922 | filesystems might detect the type of the entry without reading the inode |
945 | filesystems might detect the type of the entry without reading the inode |
923 | data (e.g. ext2fs filetype feature), even on systems that cannot return |
946 | data (e.g. ext2fs filetype feature), even on systems that cannot return |
924 | the filetype information on readdir. |
947 | the filetype information on readdir. |
925 | |
948 | |
926 | If the known number of directories (link count - 2) has been reached, the |
949 | If the known number of directories (link count - 2) has been reached, the |
… | |
… | |
1064 | callback with the fdatasync result code. |
1087 | callback with the fdatasync result code. |
1065 | |
1088 | |
1066 | If this call isn't available because your OS lacks it or it couldn't be |
1089 | If this call isn't available because your OS lacks it or it couldn't be |
1067 | detected, it will be emulated by calling C<fsync> instead. |
1090 | detected, it will be emulated by calling C<fsync> instead. |
1068 | |
1091 | |
|
|
1092 | =item aio_syncfs $fh, $callback->($status) |
|
|
1093 | |
|
|
1094 | Asynchronously call the syncfs syscall to sync the filesystem associated |
|
|
1095 | to the given filehandle and call the callback with the syncfs result |
|
|
1096 | code. If syncfs is not available, calls sync(), but returns C<-1> and sets |
|
|
1097 | errno to C<ENOSYS> nevertheless. |
|
|
1098 | |
1069 | =item aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status) |
1099 | =item aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status) |
1070 | |
1100 | |
1071 | Sync the data portion of the file specified by C<$offset> and C<$length> |
1101 | Sync the data portion of the file specified by C<$offset> and C<$length> |
1072 | to disk (but NOT the metadata), by calling the Linux-specific |
1102 | to disk (but NOT the metadata), by calling the Linux-specific |
1073 | sync_file_range call. If sync_file_range is not available or it returns |
1103 | sync_file_range call. If sync_file_range is not available or it returns |
… | |
… | |
1564 | Sets the minimum idle timeout (default 10) after which worker threads are |
1594 | Sets the minimum idle timeout (default 10) after which worker threads are |
1565 | allowed to exit. SEe C<IO::AIO::max_idle>. |
1595 | allowed to exit. SEe C<IO::AIO::max_idle>. |
1566 | |
1596 | |
1567 | =item IO::AIO::max_outstanding $maxreqs |
1597 | =item IO::AIO::max_outstanding $maxreqs |
1568 | |
1598 | |
|
|
1599 | Sets the maximum number of outstanding requests to C<$nreqs>. If |
|
|
1600 | you do queue up more than this number of requests, the next call to |
|
|
1601 | C<IO::AIO::poll_cb> (and other functions calling C<poll_cb>, such as |
|
|
1602 | C<IO::AIO::flush> or C<IO::AIO::poll>) will block until the limit is no |
|
|
1603 | longer exceeded. |
|
|
1604 | |
|
|
1605 | In other words, this setting does not enforce a queue limit, but can be |
|
|
1606 | used to make poll functions block if the limit is exceeded. |
|
|
1607 | |
1569 | This is a very bad function to use in interactive programs because it |
1608 | This is a very bad function to use in interactive programs because it |
1570 | blocks, and a bad way to reduce concurrency because it is inexact: Better |
1609 | blocks, and a bad way to reduce concurrency because it is inexact: Better |
1571 | use an C<aio_group> together with a feed callback. |
1610 | use an C<aio_group> together with a feed callback. |
1572 | |
1611 | |
1573 | Sets the maximum number of outstanding requests to C<$nreqs>. If you |
1612 | It's main use is in scripts without an event loop - when you want to stat |
1574 | do queue up more than this number of requests, the next call to the |
1613 | a lot of files, you can write somehting like this: |
1575 | C<poll_cb> (and C<poll_some> and other functions calling C<poll_cb>) |
|
|
1576 | function will block until the limit is no longer exceeded. |
|
|
1577 | |
1614 | |
1578 | The default value is very large, so there is no practical limit on the |
1615 | IO::AIO::max_outstanding 32; |
1579 | number of outstanding requests. |
|
|
1580 | |
1616 | |
1581 | You can still queue as many requests as you want. Therefore, |
1617 | for my $path (...) { |
1582 | C<max_outstanding> is mainly useful in simple scripts (with low values) or |
1618 | aio_stat $path , ...; |
1583 | as a stop gap to shield against fatal memory overflow (with large values). |
1619 | IO::AIO::poll_cb; |
|
|
1620 | } |
|
|
1621 | |
|
|
1622 | IO::AIO::flush; |
|
|
1623 | |
|
|
1624 | The call to C<poll_cb> inside the loop will normally return instantly, but |
|
|
1625 | as soon as more thna C<32> reqeusts are in-flight, it will block until |
|
|
1626 | some requests have been handled. This keeps the loop from pushing a large |
|
|
1627 | number of C<aio_stat> requests onto the queue. |
|
|
1628 | |
|
|
1629 | The default value for C<max_outstanding> is very large, so there is no |
|
|
1630 | practical limit on the number of outstanding requests. |
1584 | |
1631 | |
1585 | =back |
1632 | =back |
1586 | |
1633 | |
1587 | =head3 STATISTICAL INFORMATION |
1634 | =head3 STATISTICAL INFORMATION |
1588 | |
1635 | |
… | |
… | |
1628 | |
1675 | |
1629 | =item IO::AIO::fadvise $fh, $offset, $len, $advice |
1676 | =item IO::AIO::fadvise $fh, $offset, $len, $advice |
1630 | |
1677 | |
1631 | Simply calls the C<posix_fadvise> function (see its |
1678 | Simply calls the C<posix_fadvise> function (see its |
1632 | manpage for details). The following advice constants are |
1679 | manpage for details). The following advice constants are |
1633 | avaiable: C<IO::AIO::FADV_NORMAL>, C<IO::AIO::FADV_SEQUENTIAL>, |
1680 | available: C<IO::AIO::FADV_NORMAL>, C<IO::AIO::FADV_SEQUENTIAL>, |
1634 | C<IO::AIO::FADV_RANDOM>, C<IO::AIO::FADV_NOREUSE>, |
1681 | C<IO::AIO::FADV_RANDOM>, C<IO::AIO::FADV_NOREUSE>, |
1635 | C<IO::AIO::FADV_WILLNEED>, C<IO::AIO::FADV_DONTNEED>. |
1682 | C<IO::AIO::FADV_WILLNEED>, C<IO::AIO::FADV_DONTNEED>. |
1636 | |
1683 | |
1637 | On systems that do not implement C<posix_fadvise>, this function returns |
1684 | On systems that do not implement C<posix_fadvise>, this function returns |
1638 | ENOSYS, otherwise the return value of C<posix_fadvise>. |
1685 | ENOSYS, otherwise the return value of C<posix_fadvise>. |
1639 | |
1686 | |
1640 | =item IO::AIO::madvise $scalar, $offset, $len, $advice |
1687 | =item IO::AIO::madvise $scalar, $offset, $len, $advice |
1641 | |
1688 | |
1642 | Simply calls the C<posix_madvise> function (see its |
1689 | Simply calls the C<posix_madvise> function (see its |
1643 | manpage for details). The following advice constants are |
1690 | manpage for details). The following advice constants are |
1644 | avaiable: C<IO::AIO::MADV_NORMAL>, C<IO::AIO::MADV_SEQUENTIAL>, |
1691 | available: C<IO::AIO::MADV_NORMAL>, C<IO::AIO::MADV_SEQUENTIAL>, |
1645 | C<IO::AIO::MADV_RANDOM>, C<IO::AIO::MADV_WILLNEED>, C<IO::AIO::MADV_DONTNEED>. |
1692 | C<IO::AIO::MADV_RANDOM>, C<IO::AIO::MADV_WILLNEED>, C<IO::AIO::MADV_DONTNEED>. |
1646 | |
1693 | |
1647 | On systems that do not implement C<posix_madvise>, this function returns |
1694 | On systems that do not implement C<posix_madvise>, this function returns |
1648 | ENOSYS, otherwise the return value of C<posix_madvise>. |
1695 | ENOSYS, otherwise the return value of C<posix_madvise>. |
1649 | |
1696 | |
1650 | =item IO::AIO::mprotect $scalar, $offset, $len, $protect |
1697 | =item IO::AIO::mprotect $scalar, $offset, $len, $protect |
1651 | |
1698 | |
1652 | Simply calls the C<mprotect> function on the preferably AIO::mmap'ed |
1699 | Simply calls the C<mprotect> function on the preferably AIO::mmap'ed |
1653 | $scalar (see its manpage for details). The following protect |
1700 | $scalar (see its manpage for details). The following protect |
1654 | constants are avaiable: C<IO::AIO::PROT_NONE>, C<IO::AIO::PROT_READ>, |
1701 | constants are available: C<IO::AIO::PROT_NONE>, C<IO::AIO::PROT_READ>, |
1655 | C<IO::AIO::PROT_WRITE>, C<IO::AIO::PROT_EXEC>. |
1702 | C<IO::AIO::PROT_WRITE>, C<IO::AIO::PROT_EXEC>. |
1656 | |
1703 | |
1657 | On systems that do not implement C<mprotect>, this function returns |
1704 | On systems that do not implement C<mprotect>, this function returns |
1658 | ENOSYS, otherwise the return value of C<mprotect>. |
1705 | ENOSYS, otherwise the return value of C<mprotect>. |
1659 | |
1706 | |
… | |
… | |
1764 | Danga::Socket->AddOtherFds (IO::AIO::poll_fileno => |
1811 | Danga::Socket->AddOtherFds (IO::AIO::poll_fileno => |
1765 | \&IO::AIO::poll_cb); |
1812 | \&IO::AIO::poll_cb); |
1766 | |
1813 | |
1767 | =head2 FORK BEHAVIOUR |
1814 | =head2 FORK BEHAVIOUR |
1768 | |
1815 | |
1769 | This module should do "the right thing" when the process using it forks: |
1816 | Usage of pthreads in a program changes the semantics of fork |
|
|
1817 | considerably. Specifically, only async-safe functions can be called after |
|
|
1818 | fork. Perl doesn't know about this, so in general, you cannot call fork |
|
|
1819 | with defined behaviour in perl if pthreads are involved. IO::AIO uses |
|
|
1820 | pthreads, so this applies, but many other extensions and (for inexplicable |
|
|
1821 | reasons) perl itself often is linked against pthreads, so this limitation |
|
|
1822 | applies to quite a lot of perls. |
1770 | |
1823 | |
1771 | Before the fork, IO::AIO enters a quiescent state where no requests |
1824 | This module no longer tries to fight your OS, or POSIX. That means IO::AIO |
1772 | can be added in other threads and no results will be processed. After |
1825 | only works in the process that loaded it. Forking is fully supported, but |
1773 | the fork the parent simply leaves the quiescent state and continues |
1826 | using IO::AIO in the child is not. |
1774 | request/result processing, while the child frees the request/result queue |
|
|
1775 | (so that the requests started before the fork will only be handled in the |
|
|
1776 | parent). Threads will be started on demand until the limit set in the |
|
|
1777 | parent process has been reached again. |
|
|
1778 | |
1827 | |
1779 | In short: the parent will, after a short pause, continue as if fork had |
1828 | You might get around by not I<using> IO::AIO before (or after) |
1780 | not been called, while the child will act as if IO::AIO has not been used |
1829 | forking. You could also try to call the L<IO::AIO::reinit> function in the |
1781 | yet. |
1830 | child: |
|
|
1831 | |
|
|
1832 | =over 4 |
|
|
1833 | |
|
|
1834 | =item IO::AIO::reinit |
|
|
1835 | |
|
|
1836 | Abandons all current requests and I/O threads and simply reinitialises all |
|
|
1837 | data structures. This is not an operation supported by any standards, but |
|
|
1838 | happens to work on GNU/Linux and some newer BSD systems. |
|
|
1839 | |
|
|
1840 | The only reasonable use for this function is to call it after forking, if |
|
|
1841 | C<IO::AIO> was used in the parent. Calling it while IO::AIO is active in |
|
|
1842 | the process will result in undefined behaviour. Calling it at any time |
|
|
1843 | will also result in any undefined (by POSIX) behaviour. |
|
|
1844 | |
|
|
1845 | =back |
1782 | |
1846 | |
1783 | =head2 MEMORY USAGE |
1847 | =head2 MEMORY USAGE |
1784 | |
1848 | |
1785 | Per-request usage: |
1849 | Per-request usage: |
1786 | |
1850 | |