… | |
… | |
171 | use common::sense; |
171 | use common::sense; |
172 | |
172 | |
173 | use base 'Exporter'; |
173 | use base 'Exporter'; |
174 | |
174 | |
175 | BEGIN { |
175 | BEGIN { |
176 | our $VERSION = 4.35; |
176 | our $VERSION = 4.4; |
177 | |
177 | |
178 | our @AIO_REQ = qw(aio_sendfile aio_seek aio_read aio_write aio_open aio_close |
178 | our @AIO_REQ = qw(aio_sendfile aio_seek aio_read aio_write aio_open aio_close |
179 | aio_stat aio_lstat aio_unlink aio_rmdir aio_readdir aio_readdirx |
179 | aio_stat aio_lstat aio_unlink aio_rmdir aio_readdir aio_readdirx |
180 | aio_scandir aio_symlink aio_readlink aio_realpath aio_fcntl aio_ioctl |
180 | aio_scandir aio_symlink aio_readlink aio_realpath aio_fcntl aio_ioctl |
181 | aio_sync aio_fsync aio_syncfs aio_fdatasync aio_sync_file_range |
181 | aio_sync aio_fsync aio_syncfs aio_fdatasync aio_sync_file_range |
… | |
… | |
183 | aio_rename aio_rename2 aio_link aio_move aio_copy aio_group |
183 | aio_rename aio_rename2 aio_link aio_move aio_copy aio_group |
184 | aio_nop aio_mknod aio_load aio_rmtree aio_mkdir aio_chown |
184 | aio_nop aio_mknod aio_load aio_rmtree aio_mkdir aio_chown |
185 | aio_chmod aio_utime aio_truncate |
185 | aio_chmod aio_utime aio_truncate |
186 | aio_msync aio_mtouch aio_mlock aio_mlockall |
186 | aio_msync aio_mtouch aio_mlock aio_mlockall |
187 | aio_statvfs |
187 | aio_statvfs |
|
|
188 | aio_slurp |
188 | aio_wd); |
189 | aio_wd); |
189 | |
190 | |
190 | our @EXPORT = (@AIO_REQ, qw(aioreq_pri aioreq_nice)); |
191 | our @EXPORT = (@AIO_REQ, qw(aioreq_pri aioreq_nice)); |
191 | our @EXPORT_OK = qw(poll_fileno poll_cb poll_wait flush |
192 | our @EXPORT_OK = qw(poll_fileno poll_cb poll_wait flush |
192 | min_parallel max_parallel max_idle idle_timeout |
193 | min_parallel max_parallel max_idle idle_timeout |
… | |
… | |
277 | IO::AIO::idle_timeout $seconds |
278 | IO::AIO::idle_timeout $seconds |
278 | IO::AIO::max_outstanding $maxreqs |
279 | IO::AIO::max_outstanding $maxreqs |
279 | IO::AIO::nreqs |
280 | IO::AIO::nreqs |
280 | IO::AIO::nready |
281 | IO::AIO::nready |
281 | IO::AIO::npending |
282 | IO::AIO::npending |
|
|
283 | $nfd = IO::AIO::get_fdlimit [EXPERIMENTAL] |
|
|
284 | IO::AIO::min_fdlimit $nfd [EXPERIMENTAL] |
282 | |
285 | |
283 | IO::AIO::sendfile $ofh, $ifh, $offset, $count |
286 | IO::AIO::sendfile $ofh, $ifh, $offset, $count |
284 | IO::AIO::fadvise $fh, $offset, $len, $advice |
287 | IO::AIO::fadvise $fh, $offset, $len, $advice |
285 | IO::AIO::mmap $scalar, $length, $prot, $flags[, $fh[, $offset]] |
288 | IO::AIO::mmap $scalar, $length, $prot, $flags[, $fh[, $offset]] |
286 | IO::AIO::munmap $scalar |
289 | IO::AIO::munmap $scalar |
… | |
… | |
609 | namemax => 255, |
612 | namemax => 255, |
610 | frsize => 1024, |
613 | frsize => 1024, |
611 | fsid => 1810 |
614 | fsid => 1810 |
612 | } |
615 | } |
613 | |
616 | |
614 | Here is a (likely partial - send me updates!) list of fsid values used by |
|
|
615 | Linux - it is safe to hardcode these when C<$^O> is C<linux>: |
|
|
616 | |
|
|
617 | 0x0000adf5 adfs |
|
|
618 | 0x0000adff affs |
|
|
619 | 0x5346414f afs |
|
|
620 | 0x09041934 anon-inode filesystem |
|
|
621 | 0x00000187 autofs |
|
|
622 | 0x42465331 befs |
|
|
623 | 0x1badface bfs |
|
|
624 | 0x42494e4d binfmt_misc |
|
|
625 | 0x9123683e btrfs |
|
|
626 | 0x0027e0eb cgroupfs |
|
|
627 | 0xff534d42 cifs |
|
|
628 | 0x73757245 coda |
|
|
629 | 0x012ff7b7 coh |
|
|
630 | 0x28cd3d45 cramfs |
|
|
631 | 0x453dcd28 cramfs-wend (wrong endianness) |
|
|
632 | 0x64626720 debugfs |
|
|
633 | 0x00001373 devfs |
|
|
634 | 0x00001cd1 devpts |
|
|
635 | 0x0000f15f ecryptfs |
|
|
636 | 0x00414a53 efs |
|
|
637 | 0x0000137d ext |
|
|
638 | 0x0000ef53 ext2/ext3/ext4 |
|
|
639 | 0x0000ef51 ext2 |
|
|
640 | 0xf2f52010 f2fs |
|
|
641 | 0x00004006 fat |
|
|
642 | 0x65735546 fuseblk |
|
|
643 | 0x65735543 fusectl |
|
|
644 | 0x0bad1dea futexfs |
|
|
645 | 0x01161970 gfs2 |
|
|
646 | 0x47504653 gpfs |
|
|
647 | 0x00004244 hfs |
|
|
648 | 0xf995e849 hpfs |
|
|
649 | 0x00c0ffee hostfs |
|
|
650 | 0x958458f6 hugetlbfs |
|
|
651 | 0x2bad1dea inotifyfs |
|
|
652 | 0x00009660 isofs |
|
|
653 | 0x000072b6 jffs2 |
|
|
654 | 0x3153464a jfs |
|
|
655 | 0x6b414653 k-afs |
|
|
656 | 0x0bd00bd0 lustre |
|
|
657 | 0x0000137f minix |
|
|
658 | 0x0000138f minix 30 char names |
|
|
659 | 0x00002468 minix v2 |
|
|
660 | 0x00002478 minix v2 30 char names |
|
|
661 | 0x00004d5a minix v3 |
|
|
662 | 0x19800202 mqueue |
|
|
663 | 0x00004d44 msdos |
|
|
664 | 0x0000564c novell |
|
|
665 | 0x00006969 nfs |
|
|
666 | 0x6e667364 nfsd |
|
|
667 | 0x00003434 nilfs |
|
|
668 | 0x5346544e ntfs |
|
|
669 | 0x00009fa1 openprom |
|
|
670 | 0x7461636F ocfs2 |
|
|
671 | 0x00009fa0 proc |
|
|
672 | 0x6165676c pstorefs |
|
|
673 | 0x0000002f qnx4 |
|
|
674 | 0x68191122 qnx6 |
|
|
675 | 0x858458f6 ramfs |
|
|
676 | 0x52654973 reiserfs |
|
|
677 | 0x00007275 romfs |
|
|
678 | 0x67596969 rpc_pipefs |
|
|
679 | 0x73636673 securityfs |
|
|
680 | 0xf97cff8c selinux |
|
|
681 | 0x0000517b smb |
|
|
682 | 0x534f434b sockfs |
|
|
683 | 0x73717368 squashfs |
|
|
684 | 0x62656572 sysfs |
|
|
685 | 0x012ff7b6 sysv2 |
|
|
686 | 0x012ff7b5 sysv4 |
|
|
687 | 0x01021994 tmpfs |
|
|
688 | 0x15013346 udf |
|
|
689 | 0x00011954 ufs |
|
|
690 | 0x54190100 ufs byteswapped |
|
|
691 | 0x00009fa2 usbdevfs |
|
|
692 | 0x01021997 v9fs |
|
|
693 | 0xa501fcf5 vxfs |
|
|
694 | 0xabba1974 xenfs |
|
|
695 | 0x012ff7b4 xenix |
|
|
696 | 0x58465342 xfs |
|
|
697 | 0x012fd16d xia |
|
|
698 | |
|
|
699 | =item aio_utime $fh_or_path, $atime, $mtime, $callback->($status) |
617 | =item aio_utime $fh_or_path, $atime, $mtime, $callback->($status) |
700 | |
618 | |
701 | Works like perl's C<utime> function (including the special case of $atime |
619 | Works like perl's C<utime> function (including the special case of $atime |
702 | and $mtime being undef). Fractional times are supported if the underlying |
620 | and $mtime being undef). Fractional times are supported if the underlying |
703 | syscalls support them. |
621 | syscalls support them. |
… | |
… | |
740 | C<$mode> is usually C<0> or C<IO::AIO::FALLOC_FL_KEEP_SIZE> to allocate |
658 | C<$mode> is usually C<0> or C<IO::AIO::FALLOC_FL_KEEP_SIZE> to allocate |
741 | space, or C<IO::AIO::FALLOC_FL_PUNCH_HOLE | IO::AIO::FALLOC_FL_KEEP_SIZE>, |
659 | space, or C<IO::AIO::FALLOC_FL_PUNCH_HOLE | IO::AIO::FALLOC_FL_KEEP_SIZE>, |
742 | to deallocate a file range. |
660 | to deallocate a file range. |
743 | |
661 | |
744 | IO::AIO also supports C<FALLOC_FL_COLLAPSE_RANGE>, to remove a range |
662 | IO::AIO also supports C<FALLOC_FL_COLLAPSE_RANGE>, to remove a range |
745 | (without leaving a hole) and C<FALLOC_FL_ZERO_RANGE>, to zero a range (see |
663 | (without leaving a hole), C<FALLOC_FL_ZERO_RANGE>, to zero a range, |
746 | your L<fallocate(2)> manpage). |
664 | C<FALLOC_FL_INSERT_RANGE> to insert a range and C<FALLOC_FL_UNSHARE_RANGE> |
|
|
665 | to unshare shared blocks (see your L<fallocate(2)> manpage). |
747 | |
666 | |
748 | The file system block size used by C<fallocate> is presumably the |
667 | The file system block size used by C<fallocate> is presumably the |
749 | C<f_bsize> returned by C<statvfs>. |
668 | C<f_bsize> returned by C<statvfs>, but different filesystems and filetypes |
|
|
669 | can dictate other limitations. |
750 | |
670 | |
751 | If C<fallocate> isn't available or cannot be emulated (currently no |
671 | If C<fallocate> isn't available or cannot be emulated (currently no |
752 | emulation will be attempted), passes C<-1> and sets C<$!> to C<ENOSYS>. |
672 | emulation will be attempted), passes C<-1> and sets C<$!> to C<ENOSYS>. |
753 | |
673 | |
754 | |
674 | |
… | |
… | |
869 | |
789 | |
870 | =over 4 |
790 | =over 4 |
871 | |
791 | |
872 | =item IO::AIO::READDIR_DENTS |
792 | =item IO::AIO::READDIR_DENTS |
873 | |
793 | |
874 | When this flag is off, then the callback gets an arrayref consisting of |
794 | Normally the callback gets an arrayref consisting of names only (as |
875 | names only (as with C<aio_readdir>), otherwise it gets an arrayref with |
795 | with C<aio_readdir>). If this flag is set, then the callback gets an |
876 | C<[$name, $type, $inode]> arrayrefs, each describing a single directory |
796 | arrayref with C<[$name, $type, $inode]> arrayrefs, each describing a |
877 | entry in more detail. |
797 | single directory entry in more detail: |
878 | |
798 | |
879 | C<$name> is the name of the entry. |
799 | C<$name> is the name of the entry. |
880 | |
800 | |
881 | C<$type> is one of the C<IO::AIO::DT_xxx> constants: |
801 | C<$type> is one of the C<IO::AIO::DT_xxx> constants: |
882 | |
802 | |
883 | C<IO::AIO::DT_UNKNOWN>, C<IO::AIO::DT_FIFO>, C<IO::AIO::DT_CHR>, C<IO::AIO::DT_DIR>, |
803 | C<IO::AIO::DT_UNKNOWN>, C<IO::AIO::DT_FIFO>, C<IO::AIO::DT_CHR>, C<IO::AIO::DT_DIR>, |
884 | C<IO::AIO::DT_BLK>, C<IO::AIO::DT_REG>, C<IO::AIO::DT_LNK>, C<IO::AIO::DT_SOCK>, |
804 | C<IO::AIO::DT_BLK>, C<IO::AIO::DT_REG>, C<IO::AIO::DT_LNK>, C<IO::AIO::DT_SOCK>, |
885 | C<IO::AIO::DT_WHT>. |
805 | C<IO::AIO::DT_WHT>. |
886 | |
806 | |
887 | C<IO::AIO::DT_UNKNOWN> means just that: readdir does not know. If you need to |
807 | C<IO::AIO::DT_UNKNOWN> means just that: readdir does not know. If you need |
888 | know, you have to run stat yourself. Also, for speed reasons, the C<$type> |
808 | to know, you have to run stat yourself. Also, for speed/memory reasons, |
889 | scalars are read-only: you can not modify them. |
809 | the C<$type> scalars are read-only: you must not modify them. |
890 | |
810 | |
891 | C<$inode> is the inode number (which might not be exact on systems with 64 |
811 | C<$inode> is the inode number (which might not be exact on systems with 64 |
892 | bit inode numbers and 32 bit perls). This field has unspecified content on |
812 | bit inode numbers and 32 bit perls). This field has unspecified content on |
893 | systems that do not deliver the inode information. |
813 | systems that do not deliver the inode information. |
894 | |
814 | |
… | |
… | |
905 | short names are tried first. |
825 | short names are tried first. |
906 | |
826 | |
907 | =item IO::AIO::READDIR_STAT_ORDER |
827 | =item IO::AIO::READDIR_STAT_ORDER |
908 | |
828 | |
909 | When this flag is set, then the names will be returned in an order |
829 | When this flag is set, then the names will be returned in an order |
910 | suitable for stat()'ing each one. That is, when you plan to stat() |
830 | suitable for stat()'ing each one. That is, when you plan to stat() most or |
911 | all files in the given directory, then the returned order will likely |
831 | all files in the given directory, then the returned order will likely be |
912 | be fastest. |
832 | faster. |
913 | |
833 | |
914 | If both this flag and C<IO::AIO::READDIR_DIRS_FIRST> are specified, then |
834 | If both this flag and C<IO::AIO::READDIR_DIRS_FIRST> are specified, |
915 | the likely dirs come first, resulting in a less optimal stat order. |
835 | then the likely dirs come first, resulting in a less optimal stat order |
|
|
836 | for stat'ing all entries, but likely a more optimal order for finding |
|
|
837 | subdirectories. |
916 | |
838 | |
917 | =item IO::AIO::READDIR_FOUND_UNKNOWN |
839 | =item IO::AIO::READDIR_FOUND_UNKNOWN |
918 | |
840 | |
919 | This flag should not be set when calling C<aio_readdirx>. Instead, it |
841 | This flag should not be set when calling C<aio_readdirx>. Instead, it |
920 | is being set by C<aio_readdirx>, when any of the C<$type>'s found were |
842 | is being set by C<aio_readdirx>, when any of the C<$type>'s found were |
… | |
… | |
922 | C<$type>'s are known, which can be used to speed up some algorithms. |
844 | C<$type>'s are known, which can be used to speed up some algorithms. |
923 | |
845 | |
924 | =back |
846 | =back |
925 | |
847 | |
926 | |
848 | |
|
|
849 | =item aio_slurp $pathname, $offset, $length, $data, $callback->($status) |
|
|
850 | |
|
|
851 | Opens, reads and closes the given file. The data is put into C<$data>, |
|
|
852 | which is resized as required. |
|
|
853 | |
|
|
854 | If C<$offset> is negative, then it is counted from the end of the file. |
|
|
855 | |
|
|
856 | If C<$length> is zero, then the remaining length of the file is |
|
|
857 | used. Also, in this case, the same limitations to modifying C<$data> apply |
|
|
858 | as when IO::AIO::mmap is used, i.e. it must only be modified in-place |
|
|
859 | with C<substr>. If the size of the file is known, specifying a non-zero |
|
|
860 | C<$length> results in a performance advantage. |
|
|
861 | |
|
|
862 | This request is similar to the older C<aio_load> request, but since it is |
|
|
863 | a single request, it might be more efficient to use. |
|
|
864 | |
|
|
865 | Example: load F</etc/passwd> into C<$passwd>. |
|
|
866 | |
|
|
867 | my $passwd; |
|
|
868 | aio_slurp "/etc/passwd", 0, 0, $passwd, sub { |
|
|
869 | $_[0] >= 0 |
|
|
870 | or die "/etc/passwd: $!\n"; |
|
|
871 | |
|
|
872 | printf "/etc/passwd is %d bytes long, and contains:\n", length $passwd; |
|
|
873 | print $passwd; |
|
|
874 | }; |
|
|
875 | IO::AIO::flush; |
|
|
876 | |
|
|
877 | |
927 | =item aio_load $pathname, $data, $callback->($status) |
878 | =item aio_load $pathname, $data, $callback->($status) |
928 | |
879 | |
929 | This is a composite request that tries to fully load the given file into |
880 | This is a composite request that tries to fully load the given file into |
930 | memory. Status is the same as with aio_read. |
881 | memory. Status is the same as with aio_read. |
|
|
882 | |
|
|
883 | Using C<aio_slurp> might be more efficient, as it is a single request. |
931 | |
884 | |
932 | =cut |
885 | =cut |
933 | |
886 | |
934 | sub aio_load($$;$) { |
887 | sub aio_load($$;$) { |
935 | my ($path, undef, $cb) = @_; |
888 | my ($path, undef, $cb) = @_; |
… | |
… | |
955 | =item aio_copy $srcpath, $dstpath, $callback->($status) |
908 | =item aio_copy $srcpath, $dstpath, $callback->($status) |
956 | |
909 | |
957 | Try to copy the I<file> (directories not supported as either source or |
910 | Try to copy the I<file> (directories not supported as either source or |
958 | destination) from C<$srcpath> to C<$dstpath> and call the callback with |
911 | destination) from C<$srcpath> to C<$dstpath> and call the callback with |
959 | a status of C<0> (ok) or C<-1> (error, see C<$!>). |
912 | a status of C<0> (ok) or C<-1> (error, see C<$!>). |
|
|
913 | |
|
|
914 | Existing destination files will be truncated. |
960 | |
915 | |
961 | This is a composite request that creates the destination file with |
916 | This is a composite request that creates the destination file with |
962 | mode 0200 and copies the contents of the source file into it using |
917 | mode 0200 and copies the contents of the source file into it using |
963 | C<aio_sendfile>, followed by restoring atime, mtime, access mode and |
918 | C<aio_sendfile>, followed by restoring atime, mtime, access mode and |
964 | uid/gid, in that order. |
919 | uid/gid, in that order. |
… | |
… | |
1074 | Scans a directory (similar to C<aio_readdir>) but additionally tries to |
1029 | Scans a directory (similar to C<aio_readdir>) but additionally tries to |
1075 | efficiently separate the entries of directory C<$path> into two sets of |
1030 | efficiently separate the entries of directory C<$path> into two sets of |
1076 | names, directories you can recurse into (directories), and ones you cannot |
1031 | names, directories you can recurse into (directories), and ones you cannot |
1077 | recurse into (everything else, including symlinks to directories). |
1032 | recurse into (everything else, including symlinks to directories). |
1078 | |
1033 | |
1079 | C<aio_scandir> is a composite request that creates of many sub requests_ |
1034 | C<aio_scandir> is a composite request that generates many sub requests. |
1080 | C<$maxreq> specifies the maximum number of outstanding aio requests that |
1035 | C<$maxreq> specifies the maximum number of outstanding aio requests that |
1081 | this function generates. If it is C<< <= 0 >>, then a suitable default |
1036 | this function generates. If it is C<< <= 0 >>, then a suitable default |
1082 | will be chosen (currently 4). |
1037 | will be chosen (currently 4). |
1083 | |
1038 | |
1084 | On error, the callback is called without arguments, otherwise it receives |
1039 | On error, the callback is called without arguments, otherwise it receives |
… | |
… | |
1477 | C<IO::AIO::FIEMAP_EXTENT_DATA_ENCRYPTED>, C<IO::AIO::FIEMAP_EXTENT_NOT_ALIGNED>, |
1432 | C<IO::AIO::FIEMAP_EXTENT_DATA_ENCRYPTED>, C<IO::AIO::FIEMAP_EXTENT_NOT_ALIGNED>, |
1478 | C<IO::AIO::FIEMAP_EXTENT_DATA_INLINE>, C<IO::AIO::FIEMAP_EXTENT_DATA_TAIL>, |
1433 | C<IO::AIO::FIEMAP_EXTENT_DATA_INLINE>, C<IO::AIO::FIEMAP_EXTENT_DATA_TAIL>, |
1479 | C<IO::AIO::FIEMAP_EXTENT_UNWRITTEN>, C<IO::AIO::FIEMAP_EXTENT_MERGED> or |
1434 | C<IO::AIO::FIEMAP_EXTENT_UNWRITTEN>, C<IO::AIO::FIEMAP_EXTENT_MERGED> or |
1480 | C<IO::AIO::FIEMAP_EXTENT_SHARED>. |
1435 | C<IO::AIO::FIEMAP_EXTENT_SHARED>. |
1481 | |
1436 | |
1482 | At the time of this writing (Linux 3.2), this requets is unreliable unless |
1437 | At the time of this writing (Linux 3.2), this request is unreliable unless |
1483 | C<$count> is C<undef>, as the kernel has all sorts of bugs preventing |
1438 | C<$count> is C<undef>, as the kernel has all sorts of bugs preventing |
1484 | it to return all extents of a range for files with large number of |
1439 | it to return all extents of a range for files with a large number of |
1485 | extents. The code works around all these issues if C<$count> is undef. |
1440 | extents. The code (only) works around all these issues if C<$count> is |
|
|
1441 | C<undef>. |
1486 | |
1442 | |
1487 | =item aio_group $callback->(...) |
1443 | =item aio_group $callback->(...) |
1488 | |
1444 | |
1489 | This is a very special aio request: Instead of doing something, it is a |
1445 | This is a very special aio request: Instead of doing something, it is a |
1490 | container for other aio requests, which is useful if you want to bundle |
1446 | container for other aio requests, which is useful if you want to bundle |
… | |
… | |
1603 | There are some caveats: when directories get renamed (or deleted), the |
1559 | There are some caveats: when directories get renamed (or deleted), the |
1604 | pathname string doesn't change, so will point to the new directory (or |
1560 | pathname string doesn't change, so will point to the new directory (or |
1605 | nowhere at all), while the directory fd, if available on the system, |
1561 | nowhere at all), while the directory fd, if available on the system, |
1606 | will still point to the original directory. Most functions accepting a |
1562 | will still point to the original directory. Most functions accepting a |
1607 | pathname will use the directory fd on newer systems, and the string on |
1563 | pathname will use the directory fd on newer systems, and the string on |
1608 | older systems. Some functions (such as realpath) will always rely on the |
1564 | older systems. Some functions (such as C<aio_realpath>) will always rely on |
1609 | string form of the pathname. |
1565 | the string form of the pathname. |
1610 | |
1566 | |
1611 | So this functionality is mainly useful to get some protection against |
1567 | So this functionality is mainly useful to get some protection against |
1612 | C<chdir>, to easily get an absolute path out of a relative path for future |
1568 | C<chdir>, to easily get an absolute path out of a relative path for future |
1613 | reference, and to speed up doing many operations in the same directory |
1569 | reference, and to speed up doing many operations in the same directory |
1614 | (e.g. when stat'ing all files in a directory). |
1570 | (e.g. when stat'ing all files in a directory). |
… | |
… | |
2006 | This is a very bad function to use in interactive programs because it |
1962 | This is a very bad function to use in interactive programs because it |
2007 | blocks, and a bad way to reduce concurrency because it is inexact: Better |
1963 | blocks, and a bad way to reduce concurrency because it is inexact: Better |
2008 | use an C<aio_group> together with a feed callback. |
1964 | use an C<aio_group> together with a feed callback. |
2009 | |
1965 | |
2010 | Its main use is in scripts without an event loop - when you want to stat |
1966 | Its main use is in scripts without an event loop - when you want to stat |
2011 | a lot of files, you can write somehting like this: |
1967 | a lot of files, you can write something like this: |
2012 | |
1968 | |
2013 | IO::AIO::max_outstanding 32; |
1969 | IO::AIO::max_outstanding 32; |
2014 | |
1970 | |
2015 | for my $path (...) { |
1971 | for my $path (...) { |
2016 | aio_stat $path , ...; |
1972 | aio_stat $path , ...; |
… | |
… | |
2061 | some "Advanced I/O" function not available to in Perl, without going the |
2017 | some "Advanced I/O" function not available to in Perl, without going the |
2062 | "Asynchronous I/O" route. Many of these have an asynchronous C<aio_*> |
2018 | "Asynchronous I/O" route. Many of these have an asynchronous C<aio_*> |
2063 | counterpart. |
2019 | counterpart. |
2064 | |
2020 | |
2065 | =over 4 |
2021 | =over 4 |
|
|
2022 | |
|
|
2023 | =item $numfd = IO::AIO::get_fdlimit |
|
|
2024 | |
|
|
2025 | This function is I<EXPERIMENTAL> and subject to change. |
|
|
2026 | |
|
|
2027 | Tries to find the current file descriptor limit and returns it, or |
|
|
2028 | C<undef> and sets C<$!> in case of an error. The limit is one larger than |
|
|
2029 | the highest valid file descriptor number. |
|
|
2030 | |
|
|
2031 | =item IO::AIO::min_fdlimit [$numfd] |
|
|
2032 | |
|
|
2033 | This function is I<EXPERIMENTAL> and subject to change. |
|
|
2034 | |
|
|
2035 | Try to increase the current file descriptor limit(s) to at least C<$numfd> |
|
|
2036 | by changing the soft or hard file descriptor resource limit. If C<$numfd> |
|
|
2037 | is missing, it will try to set a very high limit, although this is not |
|
|
2038 | recommended when you know the actual minimum that you require. |
|
|
2039 | |
|
|
2040 | If the limit cannot be raised enough, the function makes a best-effort |
|
|
2041 | attempt to increase the limit as much as possible, using various |
|
|
2042 | tricks, while still failing. You can query the resulting limit using |
|
|
2043 | C<IO::AIO::get_fdlimit>. |
|
|
2044 | |
|
|
2045 | If an error occurs, returns C<undef> and sets C<$!>, otherwise returns |
|
|
2046 | true. |
2066 | |
2047 | |
2067 | =item IO::AIO::sendfile $ofh, $ifh, $offset, $count |
2048 | =item IO::AIO::sendfile $ofh, $ifh, $offset, $count |
2068 | |
2049 | |
2069 | Calls the C<eio_sendfile_sync> function, which is like C<aio_sendfile>, |
2050 | Calls the C<eio_sendfile_sync> function, which is like C<aio_sendfile>, |
2070 | but is blocking (this makes most sense if you know the input data is |
2051 | but is blocking (this makes most sense if you know the input data is |
… | |
… | |
2087 | =item IO::AIO::madvise $scalar, $offset, $len, $advice |
2068 | =item IO::AIO::madvise $scalar, $offset, $len, $advice |
2088 | |
2069 | |
2089 | Simply calls the C<posix_madvise> function (see its |
2070 | Simply calls the C<posix_madvise> function (see its |
2090 | manpage for details). The following advice constants are |
2071 | manpage for details). The following advice constants are |
2091 | available: C<IO::AIO::MADV_NORMAL>, C<IO::AIO::MADV_SEQUENTIAL>, |
2072 | available: C<IO::AIO::MADV_NORMAL>, C<IO::AIO::MADV_SEQUENTIAL>, |
2092 | C<IO::AIO::MADV_RANDOM>, C<IO::AIO::MADV_WILLNEED>, C<IO::AIO::MADV_DONTNEED>, |
2073 | C<IO::AIO::MADV_RANDOM>, C<IO::AIO::MADV_WILLNEED>, |
2093 | C<IO::AIO::MADV_FREE>. |
2074 | C<IO::AIO::MADV_DONTNEED>. |
2094 | |
2075 | |
2095 | If C<$offset> is negative, counts from the end. If C<$length> is negative, |
2076 | If C<$offset> is negative, counts from the end. If C<$length> is negative, |
2096 | the remaining length of the C<$scalar> is used. If possible, C<$length> |
2077 | the remaining length of the C<$scalar> is used. If possible, C<$length> |
2097 | will be reduced to fit into the C<$scalar>. |
2078 | will be reduced to fit into the C<$scalar>. |
2098 | |
2079 | |
… | |
… | |
2236 | |
2217 | |
2237 | Please refer to L<pipe2(2)> for more info on the C<$flags>, but at the |
2218 | Please refer to L<pipe2(2)> for more info on the C<$flags>, but at the |
2238 | time of this writing, C<IO::AIO::O_CLOEXEC>, C<IO::AIO::O_NONBLOCK> and |
2219 | time of this writing, C<IO::AIO::O_CLOEXEC>, C<IO::AIO::O_NONBLOCK> and |
2239 | C<IO::AIO::O_DIRECT> (Linux 3.4, for packet-based pipes) were supported. |
2220 | C<IO::AIO::O_DIRECT> (Linux 3.4, for packet-based pipes) were supported. |
2240 | |
2221 | |
|
|
2222 | Example: create a pipe race-free w.r.t. threads and fork: |
|
|
2223 | |
|
|
2224 | my ($rfh, $wfh) = IO::AIO::pipe2 IO::AIO::O_CLOEXEC |
|
|
2225 | or die "pipe2: $!\n"; |
|
|
2226 | |
|
|
2227 | =item $fh = IO::AIO::eventfd [$initval, [$flags]] |
|
|
2228 | |
|
|
2229 | This is a direct interface to the Linux L<eventfd(2)> system call. The |
|
|
2230 | (unhelpful) defaults for C<$initval> and C<$flags> are C<0> for both. |
|
|
2231 | |
|
|
2232 | On success, the new eventfd filehandle is returned, otherwise returns |
|
|
2233 | C<undef>. If the eventfd syscall is missing, fails with C<ENOSYS>. |
|
|
2234 | |
|
|
2235 | Please refer to L<eventfd(2)> for more info on this call. |
|
|
2236 | |
|
|
2237 | The following symbol flag values are available: C<IO::AIO::EFD_CLOEXEC>, |
|
|
2238 | C<IO::AIO::EFD_NONBLOCK> and C<IO::AIO::EFD_SEMAPHORE> (Linux 2.6.30). |
|
|
2239 | |
|
|
2240 | Example: create a new eventfd filehandle: |
|
|
2241 | |
|
|
2242 | $fh = IO::AIO::eventfd 0, IO::AIO::O_CLOEXEC |
|
|
2243 | or die "eventfd: $!\n"; |
|
|
2244 | |
|
|
2245 | =item $fh = IO::AIO::timerfd_create $clockid[, $flags] |
|
|
2246 | |
|
|
2247 | This is a direct interface to the Linux L<timerfd_create(2)> system call. The |
|
|
2248 | (unhelpful) default for C<$flags> is C<0>. |
|
|
2249 | |
|
|
2250 | On success, the new timerfd filehandle is returned, otherwise returns |
|
|
2251 | C<undef>. If the eventfd syscall is missing, fails with C<ENOSYS>. |
|
|
2252 | |
|
|
2253 | Please refer to L<timerfd_create(2)> for more info on this call. |
|
|
2254 | |
|
|
2255 | The following C<$clockid> values are |
|
|
2256 | available: C<IO::AIO::CLOCK_REALTIME>, C<IO::AIO::CLOCK_MONOTONIC> |
|
|
2257 | C<IO::AIO::CLOCK_CLOCK_BOOTTIME> (Linux 3.15) |
|
|
2258 | C<IO::AIO::CLOCK_CLOCK_REALTIME_ALARM> (Linux 3.11) and |
|
|
2259 | C<IO::AIO::CLOCK_CLOCK_BOOTTIME_ALARM> (Linux 3.11). |
|
|
2260 | |
|
|
2261 | The following C<$flags> values are available (Linux |
|
|
2262 | 2.6.27): C<IO::AIO::TFD_NONBLOCK> and C<IO::AIO::TFD_CLOEXEC>. |
|
|
2263 | |
|
|
2264 | Example: create a new timerfd and set it to one-second repeated alarms, |
|
|
2265 | then wait for two alarms: |
|
|
2266 | |
|
|
2267 | my $fh = IO::AIO::timerfd_create IO::AIO::CLOCK_BOOTTIME, IO::AIO::TFD_CLOEXEC |
|
|
2268 | or die "timerfd_create: $!\n"; |
|
|
2269 | |
|
|
2270 | defined IO::AIO::timerfd_settime $fh, 0, 1, 1 |
|
|
2271 | or die "timerfd_settime: $!\n"; |
|
|
2272 | |
|
|
2273 | for (1..2) { |
|
|
2274 | 8 == sysread $fh, my $buf, 8 |
|
|
2275 | or die "timerfd read failure\n"; |
|
|
2276 | |
|
|
2277 | printf "number of expirations (likely 1): %d\n", |
|
|
2278 | unpack "Q", $buf; |
|
|
2279 | } |
|
|
2280 | |
|
|
2281 | =item ($cur_interval, $cur_value) = IO::AIO::timerfd_settime $fh, $flags, $new_interval, $nbw_value |
|
|
2282 | |
|
|
2283 | This is a direct interface to the Linux L<timerfd_settime(2)> system |
|
|
2284 | call. Please refer to its manpage for more info on this call. |
|
|
2285 | |
|
|
2286 | The new itimerspec is specified using two (possibly fractional) second |
|
|
2287 | values, C<$new_interval> and C<$new_value>). |
|
|
2288 | |
|
|
2289 | On success, the current interval and value are returned (as per |
|
|
2290 | C<timerfd_gettime>). On failure, the empty list is returned. |
|
|
2291 | |
|
|
2292 | The following C<$flags> values are |
|
|
2293 | available: C<IO::AIO::TFD_TIMER_ABSTIME> and |
|
|
2294 | C<IO::AIO::TFD_TIMER_CANCEL_ON_SET>. |
|
|
2295 | |
|
|
2296 | See C<IO::AIO::timerfd_create> for a full example. |
|
|
2297 | |
|
|
2298 | =item ($cur_interval, $cur_value) = IO::AIO::timerfd_gettime $fh |
|
|
2299 | |
|
|
2300 | This is a direct interface to the Linux L<timerfd_gettime(2)> system |
|
|
2301 | call. Please refer to its manpage for more info on this call. |
|
|
2302 | |
|
|
2303 | On success, returns the current values of interval and value for the given |
|
|
2304 | timerfd (as potentially fractional second values). On failure, the empty |
|
|
2305 | list is returned. |
|
|
2306 | |
2241 | =back |
2307 | =back |
2242 | |
2308 | |
2243 | =cut |
2309 | =cut |
2244 | |
2310 | |
2245 | min_parallel 8; |
2311 | min_parallel 8; |
… | |
… | |
2310 | the process will result in undefined behaviour. Calling it at any time |
2376 | the process will result in undefined behaviour. Calling it at any time |
2311 | will also result in any undefined (by POSIX) behaviour. |
2377 | will also result in any undefined (by POSIX) behaviour. |
2312 | |
2378 | |
2313 | =back |
2379 | =back |
2314 | |
2380 | |
|
|
2381 | =head2 LINUX-SPECIFIC CALLS |
|
|
2382 | |
|
|
2383 | When a call is documented as "linux-specific" then this means it |
|
|
2384 | originated on GNU/Linux. C<IO::AIO> will usually try to autodetect the |
|
|
2385 | availability and compatibility of such calls regardless of the platform |
|
|
2386 | it is compiled on, so platforms such as FreeBSD which often implement |
|
|
2387 | these calls will work. When in doubt, call them and see if they fail wth |
|
|
2388 | C<ENOSYS>. |
|
|
2389 | |
2315 | =head2 MEMORY USAGE |
2390 | =head2 MEMORY USAGE |
2316 | |
2391 | |
2317 | Per-request usage: |
2392 | Per-request usage: |
2318 | |
2393 | |
2319 | Each aio request uses - depending on your architecture - around 100-200 |
2394 | Each aio request uses - depending on your architecture - around 100-200 |
… | |
… | |
2331 | temporary buffers, and each thread requires a stack and other data |
2406 | temporary buffers, and each thread requires a stack and other data |
2332 | structures (usually around 16k-128k, depending on the OS). |
2407 | structures (usually around 16k-128k, depending on the OS). |
2333 | |
2408 | |
2334 | =head1 KNOWN BUGS |
2409 | =head1 KNOWN BUGS |
2335 | |
2410 | |
2336 | Known bugs will be fixed in the next release. |
2411 | Known bugs will be fixed in the next release :) |
|
|
2412 | |
|
|
2413 | =head1 KNOWN ISSUES |
|
|
2414 | |
|
|
2415 | Calls that try to "import" foreign memory areas (such as C<IO::AIO::mmap> |
|
|
2416 | or C<IO::AIO::aio_slurp>) do not work with generic lvalues, such as |
|
|
2417 | non-created hash slots or other scalars I didn't think of. It's best to |
|
|
2418 | avoid such and either use scalar variables or making sure that the scalar |
|
|
2419 | exists (e.g. by storing C<undef>) and isn't "funny" (e.g. tied). |
|
|
2420 | |
|
|
2421 | I am not sure anything can be done about this, so this is considered a |
|
|
2422 | known issue, rather than a bug. |
2337 | |
2423 | |
2338 | =head1 SEE ALSO |
2424 | =head1 SEE ALSO |
2339 | |
2425 | |
2340 | L<AnyEvent::AIO> for easy integration into event loops, L<Coro::AIO> for a |
2426 | L<AnyEvent::AIO> for easy integration into event loops, L<Coro::AIO> for a |
2341 | more natural syntax. |
2427 | more natural syntax. |