… | |
… | |
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.52; |
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 |
182 | aio_pathsync aio_readahead aio_fiemap aio_allocate |
182 | aio_pathsync aio_readahead aio_fiemap aio_allocate |
183 | aio_rename 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 |
193 | nreqs nready npending nthreads |
194 | nreqs nready npending nthreads |
194 | max_poll_time max_poll_reqs |
195 | max_poll_time max_poll_reqs |
195 | sendfile fadvise madvise |
196 | sendfile fadvise madvise |
196 | mmap munmap munlock munlockall); |
197 | mmap munmap mremap munlock munlockall); |
197 | |
198 | |
198 | push @AIO_REQ, qw(aio_busy); # not exported |
199 | push @AIO_REQ, qw(aio_busy); # not exported |
199 | |
200 | |
200 | @IO::AIO::GRP::ISA = 'IO::AIO::REQ'; |
201 | @IO::AIO::GRP::ISA = 'IO::AIO::REQ'; |
201 | |
202 | |
… | |
… | |
233 | aio_link $srcpath, $dstpath, $callback->($status) |
234 | aio_link $srcpath, $dstpath, $callback->($status) |
234 | aio_symlink $srcpath, $dstpath, $callback->($status) |
235 | aio_symlink $srcpath, $dstpath, $callback->($status) |
235 | aio_readlink $pathname, $callback->($link) |
236 | aio_readlink $pathname, $callback->($link) |
236 | aio_realpath $pathname, $callback->($path) |
237 | aio_realpath $pathname, $callback->($path) |
237 | aio_rename $srcpath, $dstpath, $callback->($status) |
238 | aio_rename $srcpath, $dstpath, $callback->($status) |
|
|
239 | aio_rename2 $srcpath, $dstpath, $flags, $callback->($status) |
238 | aio_mkdir $pathname, $mode, $callback->($status) |
240 | aio_mkdir $pathname, $mode, $callback->($status) |
239 | aio_rmdir $pathname, $callback->($status) |
241 | aio_rmdir $pathname, $callback->($status) |
240 | aio_readdir $pathname, $callback->($entries) |
242 | aio_readdir $pathname, $callback->($entries) |
241 | aio_readdirx $pathname, $flags, $callback->($entries, $flags) |
243 | aio_readdirx $pathname, $flags, $callback->($entries, $flags) |
242 | IO::AIO::READDIR_DENTS IO::AIO::READDIR_DIRS_FIRST |
244 | IO::AIO::READDIR_DENTS IO::AIO::READDIR_DIRS_FIRST |
… | |
… | |
276 | IO::AIO::idle_timeout $seconds |
278 | IO::AIO::idle_timeout $seconds |
277 | IO::AIO::max_outstanding $maxreqs |
279 | IO::AIO::max_outstanding $maxreqs |
278 | IO::AIO::nreqs |
280 | IO::AIO::nreqs |
279 | IO::AIO::nready |
281 | IO::AIO::nready |
280 | IO::AIO::npending |
282 | IO::AIO::npending |
|
|
283 | $nfd = IO::AIO::get_fdlimit [EXPERIMENTAL] |
|
|
284 | IO::AIO::min_fdlimit $nfd [EXPERIMENTAL] |
281 | |
285 | |
282 | IO::AIO::sendfile $ofh, $ifh, $offset, $count |
286 | IO::AIO::sendfile $ofh, $ifh, $offset, $count |
283 | IO::AIO::fadvise $fh, $offset, $len, $advice |
287 | IO::AIO::fadvise $fh, $offset, $len, $advice |
284 | IO::AIO::mmap $scalar, $length, $prot, $flags[, $fh[, $offset]] |
288 | IO::AIO::mmap $scalar, $length, $prot, $flags[, $fh[, $offset]] |
285 | IO::AIO::munmap $scalar |
289 | IO::AIO::munmap $scalar |
|
|
290 | IO::AIO::mremap $scalar, $new_length, $flags[, $new_address] |
286 | IO::AIO::madvise $scalar, $offset, $length, $advice |
291 | IO::AIO::madvise $scalar, $offset, $length, $advice |
287 | IO::AIO::mprotect $scalar, $offset, $length, $protect |
292 | IO::AIO::mprotect $scalar, $offset, $length, $protect |
288 | IO::AIO::munlock $scalar, $offset = 0, $length = undef |
293 | IO::AIO::munlock $scalar, $offset = 0, $length = undef |
289 | IO::AIO::munlockall |
294 | IO::AIO::munlockall |
290 | |
295 | |
… | |
… | |
400 | following POSIX and non-POSIX constants are available (missing ones on |
405 | following POSIX and non-POSIX constants are available (missing ones on |
401 | your system are, as usual, C<0>): |
406 | your system are, as usual, C<0>): |
402 | |
407 | |
403 | C<O_ASYNC>, C<O_DIRECT>, C<O_NOATIME>, C<O_CLOEXEC>, C<O_NOCTTY>, C<O_NOFOLLOW>, |
408 | C<O_ASYNC>, C<O_DIRECT>, C<O_NOATIME>, C<O_CLOEXEC>, C<O_NOCTTY>, C<O_NOFOLLOW>, |
404 | C<O_NONBLOCK>, C<O_EXEC>, C<O_SEARCH>, C<O_DIRECTORY>, C<O_DSYNC>, |
409 | C<O_NONBLOCK>, C<O_EXEC>, C<O_SEARCH>, C<O_DIRECTORY>, C<O_DSYNC>, |
405 | C<O_RSYNC>, C<O_SYNC>, C<O_PATH>, C<O_TMPFILE>, and C<O_TTY_INIT>. |
410 | C<O_RSYNC>, C<O_SYNC>, C<O_PATH>, C<O_TMPFILE>, C<O_TTY_INIT> and C<O_ACCMODE>. |
406 | |
411 | |
407 | |
412 | |
408 | =item aio_close $fh, $callback->($status) |
413 | =item aio_close $fh, $callback->($status) |
409 | |
414 | |
410 | Asynchronously close a file and call the callback with the result |
415 | Asynchronously close a file and call the callback with the result |
… | |
… | |
555 | behaviour). |
560 | behaviour). |
556 | |
561 | |
557 | C<S_IFMT>, C<S_IFIFO>, C<S_IFCHR>, C<S_IFBLK>, C<S_IFLNK>, C<S_IFREG>, |
562 | C<S_IFMT>, C<S_IFIFO>, C<S_IFCHR>, C<S_IFBLK>, C<S_IFLNK>, C<S_IFREG>, |
558 | C<S_IFDIR>, C<S_IFWHT>, C<S_IFSOCK>, C<IO::AIO::major $dev_t>, |
563 | C<S_IFDIR>, C<S_IFWHT>, C<S_IFSOCK>, C<IO::AIO::major $dev_t>, |
559 | C<IO::AIO::minor $dev_t>, C<IO::AIO::makedev $major, $minor>. |
564 | C<IO::AIO::minor $dev_t>, C<IO::AIO::makedev $major, $minor>. |
|
|
565 | |
|
|
566 | To access higher resolution stat timestamps, see L<SUBSECOND STAT TIME |
|
|
567 | ACCESS>. |
560 | |
568 | |
561 | Example: Print the length of F</etc/passwd>: |
569 | Example: Print the length of F</etc/passwd>: |
562 | |
570 | |
563 | aio_stat "/etc/passwd", sub { |
571 | aio_stat "/etc/passwd", sub { |
564 | $_[0] and die "stat failed: $!"; |
572 | $_[0] and die "stat failed: $!"; |
… | |
… | |
608 | namemax => 255, |
616 | namemax => 255, |
609 | frsize => 1024, |
617 | frsize => 1024, |
610 | fsid => 1810 |
618 | fsid => 1810 |
611 | } |
619 | } |
612 | |
620 | |
613 | Here is a (likely partial - send me updates!) list of fsid values used by |
|
|
614 | Linux - it is safe to hardcode these when C<$^O> is C<linux>: |
|
|
615 | |
|
|
616 | 0x0000adf5 adfs |
|
|
617 | 0x0000adff affs |
|
|
618 | 0x5346414f afs |
|
|
619 | 0x09041934 anon-inode filesystem |
|
|
620 | 0x00000187 autofs |
|
|
621 | 0x42465331 befs |
|
|
622 | 0x1badface bfs |
|
|
623 | 0x42494e4d binfmt_misc |
|
|
624 | 0x9123683e btrfs |
|
|
625 | 0x0027e0eb cgroupfs |
|
|
626 | 0xff534d42 cifs |
|
|
627 | 0x73757245 coda |
|
|
628 | 0x012ff7b7 coh |
|
|
629 | 0x28cd3d45 cramfs |
|
|
630 | 0x453dcd28 cramfs-wend (wrong endianness) |
|
|
631 | 0x64626720 debugfs |
|
|
632 | 0x00001373 devfs |
|
|
633 | 0x00001cd1 devpts |
|
|
634 | 0x0000f15f ecryptfs |
|
|
635 | 0x00414a53 efs |
|
|
636 | 0x0000137d ext |
|
|
637 | 0x0000ef53 ext2/ext3/ext4 |
|
|
638 | 0x0000ef51 ext2 |
|
|
639 | 0xf2f52010 f2fs |
|
|
640 | 0x00004006 fat |
|
|
641 | 0x65735546 fuseblk |
|
|
642 | 0x65735543 fusectl |
|
|
643 | 0x0bad1dea futexfs |
|
|
644 | 0x01161970 gfs2 |
|
|
645 | 0x47504653 gpfs |
|
|
646 | 0x00004244 hfs |
|
|
647 | 0xf995e849 hpfs |
|
|
648 | 0x00c0ffee hostfs |
|
|
649 | 0x958458f6 hugetlbfs |
|
|
650 | 0x2bad1dea inotifyfs |
|
|
651 | 0x00009660 isofs |
|
|
652 | 0x000072b6 jffs2 |
|
|
653 | 0x3153464a jfs |
|
|
654 | 0x6b414653 k-afs |
|
|
655 | 0x0bd00bd0 lustre |
|
|
656 | 0x0000137f minix |
|
|
657 | 0x0000138f minix 30 char names |
|
|
658 | 0x00002468 minix v2 |
|
|
659 | 0x00002478 minix v2 30 char names |
|
|
660 | 0x00004d5a minix v3 |
|
|
661 | 0x19800202 mqueue |
|
|
662 | 0x00004d44 msdos |
|
|
663 | 0x0000564c novell |
|
|
664 | 0x00006969 nfs |
|
|
665 | 0x6e667364 nfsd |
|
|
666 | 0x00003434 nilfs |
|
|
667 | 0x5346544e ntfs |
|
|
668 | 0x00009fa1 openprom |
|
|
669 | 0x7461636F ocfs2 |
|
|
670 | 0x00009fa0 proc |
|
|
671 | 0x6165676c pstorefs |
|
|
672 | 0x0000002f qnx4 |
|
|
673 | 0x68191122 qnx6 |
|
|
674 | 0x858458f6 ramfs |
|
|
675 | 0x52654973 reiserfs |
|
|
676 | 0x00007275 romfs |
|
|
677 | 0x67596969 rpc_pipefs |
|
|
678 | 0x73636673 securityfs |
|
|
679 | 0xf97cff8c selinux |
|
|
680 | 0x0000517b smb |
|
|
681 | 0x534f434b sockfs |
|
|
682 | 0x73717368 squashfs |
|
|
683 | 0x62656572 sysfs |
|
|
684 | 0x012ff7b6 sysv2 |
|
|
685 | 0x012ff7b5 sysv4 |
|
|
686 | 0x01021994 tmpfs |
|
|
687 | 0x15013346 udf |
|
|
688 | 0x00011954 ufs |
|
|
689 | 0x54190100 ufs byteswapped |
|
|
690 | 0x00009fa2 usbdevfs |
|
|
691 | 0x01021997 v9fs |
|
|
692 | 0xa501fcf5 vxfs |
|
|
693 | 0xabba1974 xenfs |
|
|
694 | 0x012ff7b4 xenix |
|
|
695 | 0x58465342 xfs |
|
|
696 | 0x012fd16d xia |
|
|
697 | |
|
|
698 | =item aio_utime $fh_or_path, $atime, $mtime, $callback->($status) |
621 | =item aio_utime $fh_or_path, $atime, $mtime, $callback->($status) |
699 | |
622 | |
700 | Works like perl's C<utime> function (including the special case of $atime |
623 | Works like perl's C<utime> function (including the special case of $atime |
701 | and $mtime being undef). Fractional times are supported if the underlying |
624 | and $mtime being undef). Fractional times are supported if the underlying |
702 | syscalls support them. |
625 | syscalls support them. |
… | |
… | |
739 | C<$mode> is usually C<0> or C<IO::AIO::FALLOC_FL_KEEP_SIZE> to allocate |
662 | C<$mode> is usually C<0> or C<IO::AIO::FALLOC_FL_KEEP_SIZE> to allocate |
740 | space, or C<IO::AIO::FALLOC_FL_PUNCH_HOLE | IO::AIO::FALLOC_FL_KEEP_SIZE>, |
663 | space, or C<IO::AIO::FALLOC_FL_PUNCH_HOLE | IO::AIO::FALLOC_FL_KEEP_SIZE>, |
741 | to deallocate a file range. |
664 | to deallocate a file range. |
742 | |
665 | |
743 | IO::AIO also supports C<FALLOC_FL_COLLAPSE_RANGE>, to remove a range |
666 | IO::AIO also supports C<FALLOC_FL_COLLAPSE_RANGE>, to remove a range |
744 | (without leaving a hole) and C<FALLOC_FL_ZERO_RANGE>, to zero a range (see |
667 | (without leaving a hole), C<FALLOC_FL_ZERO_RANGE>, to zero a range, |
745 | your L<fallocate(2)> manpage). |
668 | C<FALLOC_FL_INSERT_RANGE> to insert a range and C<FALLOC_FL_UNSHARE_RANGE> |
|
|
669 | to unshare shared blocks (see your L<fallocate(2)> manpage). |
746 | |
670 | |
747 | The file system block size used by C<fallocate> is presumably the |
671 | The file system block size used by C<fallocate> is presumably the |
748 | C<f_bsize> returned by C<statvfs>. |
672 | C<f_bsize> returned by C<statvfs>, but different filesystems and filetypes |
|
|
673 | can dictate other limitations. |
749 | |
674 | |
750 | If C<fallocate> isn't available or cannot be emulated (currently no |
675 | If C<fallocate> isn't available or cannot be emulated (currently no |
751 | emulation will be attempted), passes C<-1> and sets C<$!> to C<ENOSYS>. |
676 | emulation will be attempted), passes C<-1> and sets C<$!> to C<ENOSYS>. |
752 | |
677 | |
753 | |
678 | |
… | |
… | |
812 | On systems that support the AIO::WD working directory abstraction |
737 | On systems that support the AIO::WD working directory abstraction |
813 | natively, the case C<[$wd, "."]> as C<$srcpath> is specialcased - instead |
738 | natively, the case C<[$wd, "."]> as C<$srcpath> is specialcased - instead |
814 | of failing, C<rename> is called on the absolute path of C<$wd>. |
739 | of failing, C<rename> is called on the absolute path of C<$wd>. |
815 | |
740 | |
816 | |
741 | |
|
|
742 | =item aio_rename2 $srcpath, $dstpath, $flags, $callback->($status) |
|
|
743 | |
|
|
744 | Basically a version of C<aio_rename> with an additional C<$flags> |
|
|
745 | argument. Calling this with C<$flags=0> is the same as calling |
|
|
746 | C<aio_rename>. |
|
|
747 | |
|
|
748 | Non-zero flags are currently only supported on GNU/Linux systems that |
|
|
749 | support renameat2. Other systems fail with C<ENOSYS> in this case. |
|
|
750 | |
|
|
751 | The following constants are available (missing ones are, as usual C<0>), |
|
|
752 | see renameat2(2) for details: |
|
|
753 | |
|
|
754 | C<IO::AIO::RENAME_NOREPLACE>, C<IO::AIO::RENAME_EXCHANGE> |
|
|
755 | and C<IO::AIO::RENAME_WHITEOUT>. |
|
|
756 | |
|
|
757 | |
817 | =item aio_mkdir $pathname, $mode, $callback->($status) |
758 | =item aio_mkdir $pathname, $mode, $callback->($status) |
818 | |
759 | |
819 | Asynchronously mkdir (create) a directory and call the callback with |
760 | Asynchronously mkdir (create) a directory and call the callback with |
820 | the result code. C<$mode> will be modified by the umask at the time the |
761 | the result code. C<$mode> will be modified by the umask at the time the |
821 | request is executed, so do not change your umask. |
762 | request is executed, so do not change your umask. |
… | |
… | |
852 | |
793 | |
853 | =over 4 |
794 | =over 4 |
854 | |
795 | |
855 | =item IO::AIO::READDIR_DENTS |
796 | =item IO::AIO::READDIR_DENTS |
856 | |
797 | |
857 | When this flag is off, then the callback gets an arrayref consisting of |
798 | Normally the callback gets an arrayref consisting of names only (as |
858 | names only (as with C<aio_readdir>), otherwise it gets an arrayref with |
799 | with C<aio_readdir>). If this flag is set, then the callback gets an |
859 | C<[$name, $type, $inode]> arrayrefs, each describing a single directory |
800 | arrayref with C<[$name, $type, $inode]> arrayrefs, each describing a |
860 | entry in more detail. |
801 | single directory entry in more detail: |
861 | |
802 | |
862 | C<$name> is the name of the entry. |
803 | C<$name> is the name of the entry. |
863 | |
804 | |
864 | C<$type> is one of the C<IO::AIO::DT_xxx> constants: |
805 | C<$type> is one of the C<IO::AIO::DT_xxx> constants: |
865 | |
806 | |
866 | C<IO::AIO::DT_UNKNOWN>, C<IO::AIO::DT_FIFO>, C<IO::AIO::DT_CHR>, C<IO::AIO::DT_DIR>, |
807 | C<IO::AIO::DT_UNKNOWN>, C<IO::AIO::DT_FIFO>, C<IO::AIO::DT_CHR>, C<IO::AIO::DT_DIR>, |
867 | C<IO::AIO::DT_BLK>, C<IO::AIO::DT_REG>, C<IO::AIO::DT_LNK>, C<IO::AIO::DT_SOCK>, |
808 | C<IO::AIO::DT_BLK>, C<IO::AIO::DT_REG>, C<IO::AIO::DT_LNK>, C<IO::AIO::DT_SOCK>, |
868 | C<IO::AIO::DT_WHT>. |
809 | C<IO::AIO::DT_WHT>. |
869 | |
810 | |
870 | C<IO::AIO::DT_UNKNOWN> means just that: readdir does not know. If you need to |
811 | C<IO::AIO::DT_UNKNOWN> means just that: readdir does not know. If you need |
871 | know, you have to run stat yourself. Also, for speed reasons, the C<$type> |
812 | to know, you have to run stat yourself. Also, for speed/memory reasons, |
872 | scalars are read-only: you can not modify them. |
813 | the C<$type> scalars are read-only: you must not modify them. |
873 | |
814 | |
874 | C<$inode> is the inode number (which might not be exact on systems with 64 |
815 | C<$inode> is the inode number (which might not be exact on systems with 64 |
875 | bit inode numbers and 32 bit perls). This field has unspecified content on |
816 | bit inode numbers and 32 bit perls). This field has unspecified content on |
876 | systems that do not deliver the inode information. |
817 | systems that do not deliver the inode information. |
877 | |
818 | |
… | |
… | |
888 | short names are tried first. |
829 | short names are tried first. |
889 | |
830 | |
890 | =item IO::AIO::READDIR_STAT_ORDER |
831 | =item IO::AIO::READDIR_STAT_ORDER |
891 | |
832 | |
892 | When this flag is set, then the names will be returned in an order |
833 | When this flag is set, then the names will be returned in an order |
893 | suitable for stat()'ing each one. That is, when you plan to stat() |
834 | suitable for stat()'ing each one. That is, when you plan to stat() most or |
894 | all files in the given directory, then the returned order will likely |
835 | all files in the given directory, then the returned order will likely be |
895 | be fastest. |
836 | faster. |
896 | |
837 | |
897 | If both this flag and C<IO::AIO::READDIR_DIRS_FIRST> are specified, then |
838 | If both this flag and C<IO::AIO::READDIR_DIRS_FIRST> are specified, |
898 | the likely dirs come first, resulting in a less optimal stat order. |
839 | then the likely dirs come first, resulting in a less optimal stat order |
|
|
840 | for stat'ing all entries, but likely a more optimal order for finding |
|
|
841 | subdirectories. |
899 | |
842 | |
900 | =item IO::AIO::READDIR_FOUND_UNKNOWN |
843 | =item IO::AIO::READDIR_FOUND_UNKNOWN |
901 | |
844 | |
902 | This flag should not be set when calling C<aio_readdirx>. Instead, it |
845 | This flag should not be set when calling C<aio_readdirx>. Instead, it |
903 | is being set by C<aio_readdirx>, when any of the C<$type>'s found were |
846 | is being set by C<aio_readdirx>, when any of the C<$type>'s found were |
… | |
… | |
905 | C<$type>'s are known, which can be used to speed up some algorithms. |
848 | C<$type>'s are known, which can be used to speed up some algorithms. |
906 | |
849 | |
907 | =back |
850 | =back |
908 | |
851 | |
909 | |
852 | |
|
|
853 | =item aio_slurp $pathname, $offset, $length, $data, $callback->($status) |
|
|
854 | |
|
|
855 | Opens, reads and closes the given file. The data is put into C<$data>, |
|
|
856 | which is resized as required. |
|
|
857 | |
|
|
858 | If C<$offset> is negative, then it is counted from the end of the file. |
|
|
859 | |
|
|
860 | If C<$length> is zero, then the remaining length of the file is |
|
|
861 | used. Also, in this case, the same limitations to modifying C<$data> apply |
|
|
862 | as when IO::AIO::mmap is used, i.e. it must only be modified in-place |
|
|
863 | with C<substr>. If the size of the file is known, specifying a non-zero |
|
|
864 | C<$length> results in a performance advantage. |
|
|
865 | |
|
|
866 | This request is similar to the older C<aio_load> request, but since it is |
|
|
867 | a single request, it might be more efficient to use. |
|
|
868 | |
|
|
869 | Example: load F</etc/passwd> into C<$passwd>. |
|
|
870 | |
|
|
871 | my $passwd; |
|
|
872 | aio_slurp "/etc/passwd", 0, 0, $passwd, sub { |
|
|
873 | $_[0] >= 0 |
|
|
874 | or die "/etc/passwd: $!\n"; |
|
|
875 | |
|
|
876 | printf "/etc/passwd is %d bytes long, and contains:\n", length $passwd; |
|
|
877 | print $passwd; |
|
|
878 | }; |
|
|
879 | IO::AIO::flush; |
|
|
880 | |
|
|
881 | |
910 | =item aio_load $pathname, $data, $callback->($status) |
882 | =item aio_load $pathname, $data, $callback->($status) |
911 | |
883 | |
912 | This is a composite request that tries to fully load the given file into |
884 | This is a composite request that tries to fully load the given file into |
913 | memory. Status is the same as with aio_read. |
885 | memory. Status is the same as with aio_read. |
|
|
886 | |
|
|
887 | Using C<aio_slurp> might be more efficient, as it is a single request. |
914 | |
888 | |
915 | =cut |
889 | =cut |
916 | |
890 | |
917 | sub aio_load($$;$) { |
891 | sub aio_load($$;$) { |
918 | my ($path, undef, $cb) = @_; |
892 | my ($path, undef, $cb) = @_; |
… | |
… | |
938 | =item aio_copy $srcpath, $dstpath, $callback->($status) |
912 | =item aio_copy $srcpath, $dstpath, $callback->($status) |
939 | |
913 | |
940 | Try to copy the I<file> (directories not supported as either source or |
914 | Try to copy the I<file> (directories not supported as either source or |
941 | destination) from C<$srcpath> to C<$dstpath> and call the callback with |
915 | destination) from C<$srcpath> to C<$dstpath> and call the callback with |
942 | a status of C<0> (ok) or C<-1> (error, see C<$!>). |
916 | a status of C<0> (ok) or C<-1> (error, see C<$!>). |
|
|
917 | |
|
|
918 | Existing destination files will be truncated. |
943 | |
919 | |
944 | This is a composite request that creates the destination file with |
920 | This is a composite request that creates the destination file with |
945 | mode 0200 and copies the contents of the source file into it using |
921 | mode 0200 and copies the contents of the source file into it using |
946 | C<aio_sendfile>, followed by restoring atime, mtime, access mode and |
922 | C<aio_sendfile>, followed by restoring atime, mtime, access mode and |
947 | uid/gid, in that order. |
923 | uid/gid, in that order. |
… | |
… | |
1057 | Scans a directory (similar to C<aio_readdir>) but additionally tries to |
1033 | Scans a directory (similar to C<aio_readdir>) but additionally tries to |
1058 | efficiently separate the entries of directory C<$path> into two sets of |
1034 | efficiently separate the entries of directory C<$path> into two sets of |
1059 | names, directories you can recurse into (directories), and ones you cannot |
1035 | names, directories you can recurse into (directories), and ones you cannot |
1060 | recurse into (everything else, including symlinks to directories). |
1036 | recurse into (everything else, including symlinks to directories). |
1061 | |
1037 | |
1062 | C<aio_scandir> is a composite request that creates of many sub requests_ |
1038 | C<aio_scandir> is a composite request that generates many sub requests. |
1063 | C<$maxreq> specifies the maximum number of outstanding aio requests that |
1039 | C<$maxreq> specifies the maximum number of outstanding aio requests that |
1064 | this function generates. If it is C<< <= 0 >>, then a suitable default |
1040 | this function generates. If it is C<< <= 0 >>, then a suitable default |
1065 | will be chosen (currently 4). |
1041 | will be chosen (currently 4). |
1066 | |
1042 | |
1067 | On error, the callback is called without arguments, otherwise it receives |
1043 | On error, the callback is called without arguments, otherwise it receives |
… | |
… | |
1254 | other processes), although if you are careful and know what you are doing, |
1230 | other processes), although if you are careful and know what you are doing, |
1255 | you still can. |
1231 | you still can. |
1256 | |
1232 | |
1257 | The following constants are available (missing ones are, as usual C<0>): |
1233 | The following constants are available (missing ones are, as usual C<0>): |
1258 | |
1234 | |
|
|
1235 | C<F_DUPFD_CLOEXEC>, |
|
|
1236 | |
|
|
1237 | C<F_OFD_GETLK>, C<F_OFD_SETLK>, C<F_OFD_GETLKW>, |
|
|
1238 | |
1259 | C<FIFREEZE>, C<FITHAW>, C<FITRIM>, C<FICLONE>, C<FICLONERANGE>, C<FIDEDUPERANGE>. |
1239 | C<FIFREEZE>, C<FITHAW>, C<FITRIM>, C<FICLONE>, C<FICLONERANGE>, C<FIDEDUPERANGE>. |
1260 | |
1240 | |
1261 | C<FS_IOC_GETFLAGS>, C<FS_IOC_SETFLAGS>, C<FS_IOC_GETVERSION>, C<FS_IOC_SETVERSION>, |
1241 | C<FS_IOC_GETFLAGS>, C<FS_IOC_SETFLAGS>, C<FS_IOC_GETVERSION>, C<FS_IOC_SETVERSION>, |
1262 | C<FS_IOC_FIEMAP>. |
1242 | C<FS_IOC_FIEMAP>. |
1263 | |
1243 | |
… | |
… | |
1456 | C<IO::AIO::FIEMAP_EXTENT_DATA_ENCRYPTED>, C<IO::AIO::FIEMAP_EXTENT_NOT_ALIGNED>, |
1436 | C<IO::AIO::FIEMAP_EXTENT_DATA_ENCRYPTED>, C<IO::AIO::FIEMAP_EXTENT_NOT_ALIGNED>, |
1457 | C<IO::AIO::FIEMAP_EXTENT_DATA_INLINE>, C<IO::AIO::FIEMAP_EXTENT_DATA_TAIL>, |
1437 | C<IO::AIO::FIEMAP_EXTENT_DATA_INLINE>, C<IO::AIO::FIEMAP_EXTENT_DATA_TAIL>, |
1458 | C<IO::AIO::FIEMAP_EXTENT_UNWRITTEN>, C<IO::AIO::FIEMAP_EXTENT_MERGED> or |
1438 | C<IO::AIO::FIEMAP_EXTENT_UNWRITTEN>, C<IO::AIO::FIEMAP_EXTENT_MERGED> or |
1459 | C<IO::AIO::FIEMAP_EXTENT_SHARED>. |
1439 | C<IO::AIO::FIEMAP_EXTENT_SHARED>. |
1460 | |
1440 | |
1461 | At the time of this writing (Linux 3.2), this requets is unreliable unless |
1441 | At the time of this writing (Linux 3.2), this request is unreliable unless |
1462 | C<$count> is C<undef>, as the kernel has all sorts of bugs preventing |
1442 | C<$count> is C<undef>, as the kernel has all sorts of bugs preventing |
1463 | it to return all extents of a range for files with large number of |
1443 | it to return all extents of a range for files with a large number of |
1464 | extents. The code works around all these issues if C<$count> is undef. |
1444 | extents. The code (only) works around all these issues if C<$count> is |
|
|
1445 | C<undef>. |
1465 | |
1446 | |
1466 | =item aio_group $callback->(...) |
1447 | =item aio_group $callback->(...) |
1467 | |
1448 | |
1468 | This is a very special aio request: Instead of doing something, it is a |
1449 | This is a very special aio request: Instead of doing something, it is a |
1469 | container for other aio requests, which is useful if you want to bundle |
1450 | container for other aio requests, which is useful if you want to bundle |
… | |
… | |
1582 | There are some caveats: when directories get renamed (or deleted), the |
1563 | There are some caveats: when directories get renamed (or deleted), the |
1583 | pathname string doesn't change, so will point to the new directory (or |
1564 | pathname string doesn't change, so will point to the new directory (or |
1584 | nowhere at all), while the directory fd, if available on the system, |
1565 | nowhere at all), while the directory fd, if available on the system, |
1585 | will still point to the original directory. Most functions accepting a |
1566 | will still point to the original directory. Most functions accepting a |
1586 | pathname will use the directory fd on newer systems, and the string on |
1567 | pathname will use the directory fd on newer systems, and the string on |
1587 | older systems. Some functions (such as realpath) will always rely on the |
1568 | older systems. Some functions (such as C<aio_realpath>) will always rely on |
1588 | string form of the pathname. |
1569 | the string form of the pathname. |
1589 | |
1570 | |
1590 | So this functionality is mainly useful to get some protection against |
1571 | So this functionality is mainly useful to get some protection against |
1591 | C<chdir>, to easily get an absolute path out of a relative path for future |
1572 | C<chdir>, to easily get an absolute path out of a relative path for future |
1592 | reference, and to speed up doing many operations in the same directory |
1573 | reference, and to speed up doing many operations in the same directory |
1593 | (e.g. when stat'ing all files in a directory). |
1574 | (e.g. when stat'ing all files in a directory). |
… | |
… | |
1985 | This is a very bad function to use in interactive programs because it |
1966 | This is a very bad function to use in interactive programs because it |
1986 | blocks, and a bad way to reduce concurrency because it is inexact: Better |
1967 | blocks, and a bad way to reduce concurrency because it is inexact: Better |
1987 | use an C<aio_group> together with a feed callback. |
1968 | use an C<aio_group> together with a feed callback. |
1988 | |
1969 | |
1989 | Its main use is in scripts without an event loop - when you want to stat |
1970 | Its main use is in scripts without an event loop - when you want to stat |
1990 | a lot of files, you can write somehting like this: |
1971 | a lot of files, you can write something like this: |
1991 | |
1972 | |
1992 | IO::AIO::max_outstanding 32; |
1973 | IO::AIO::max_outstanding 32; |
1993 | |
1974 | |
1994 | for my $path (...) { |
1975 | for my $path (...) { |
1995 | aio_stat $path , ...; |
1976 | aio_stat $path , ...; |
… | |
… | |
2032 | Returns the number of requests currently in the pending state (executed, |
2013 | Returns the number of requests currently in the pending state (executed, |
2033 | but not yet processed by poll_cb). |
2014 | but not yet processed by poll_cb). |
2034 | |
2015 | |
2035 | =back |
2016 | =back |
2036 | |
2017 | |
|
|
2018 | =head3 SUBSECOND STAT TIME ACCESS |
|
|
2019 | |
|
|
2020 | Both C<aio_stat>/C<aio_lstat> and perl's C<stat>/C<lstat> functions can |
|
|
2021 | generally find access/modification and change times with subsecond time |
|
|
2022 | accuracy of the system supports it, but perl's built-in functions only |
|
|
2023 | return the integer part. |
|
|
2024 | |
|
|
2025 | The following functions return the timestamps of the most recent |
|
|
2026 | stat with subsecond precision on most systems and work both after |
|
|
2027 | C<aio_stat>/C<aio_lstat> and perl's C<stat>/C<lstat> calls. Their return |
|
|
2028 | value is only meaningful after a successful C<stat>/C<lstat> call, or |
|
|
2029 | during/after a successful C<aio_stat>/C<aio_lstat> callback. |
|
|
2030 | |
|
|
2031 | This is similar to the L<Time::HiRes> C<stat> functions, but can return |
|
|
2032 | full resolution without rounding and work with standard perl C<stat>, |
|
|
2033 | alleviating the need to call the special C<Time::HiRes> functions, which |
|
|
2034 | do not act like their perl counterparts. |
|
|
2035 | |
|
|
2036 | On operating systems or file systems where subsecond time resolution is |
|
|
2037 | not supported or could not be detected, a fractional part of C<0> is |
|
|
2038 | returned, so it is always safe to call these functions. |
|
|
2039 | |
|
|
2040 | =over 4 |
|
|
2041 | |
|
|
2042 | =item $seconds = IO::AIO::st_atime, IO::AIO::st_mtime, IO::AIO::st_ctime |
|
|
2043 | |
|
|
2044 | Return the access, modication or change time, respectively, including |
|
|
2045 | fractional part. Due to the limited precision of floating point, the |
|
|
2046 | accuracy on most platforms is only a bit better than milliseconds for |
|
|
2047 | times around now - see the I<nsec> function family, below, for full |
|
|
2048 | accuracy. |
|
|
2049 | |
|
|
2050 | =item ($atime, $mtime, $ctime, ...) = IO::AIO::st_xtime |
|
|
2051 | |
|
|
2052 | Returns access, modification and change time all in one go, and maybe more |
|
|
2053 | times in the future version. |
|
|
2054 | |
|
|
2055 | =item $nanoseconds = IO::AIO::st_atimensec, IO::AIO::st_mtimensec, IO::AIO::st_ctimensec |
|
|
2056 | |
|
|
2057 | Return the fractional access, modifcation or change time, in nanoseconds, |
|
|
2058 | as an integer in the range C<0> to C<999999999>. |
|
|
2059 | |
|
|
2060 | =item ($atime, $mtime, $ctime, ...) = IO::AIO::st_xtimensec |
|
|
2061 | |
|
|
2062 | Like the functions above, but returns all three times in one go (and maybe |
|
|
2063 | more in future versions). |
|
|
2064 | |
|
|
2065 | =back |
|
|
2066 | |
|
|
2067 | Example: print the high resolution modification time of F</etc>, using |
|
|
2068 | C<stat>, and C<IO::AIO::aio_stat>. |
|
|
2069 | |
|
|
2070 | if (stat "/etc") { |
|
|
2071 | printf "stat(/etc) mtime: %f\n", IO::AIO::st_mtime; |
|
|
2072 | } |
|
|
2073 | |
|
|
2074 | IO::AIO::aio_stat "/etc", sub { |
|
|
2075 | $_[0] |
|
|
2076 | and return; |
|
|
2077 | |
|
|
2078 | printf "aio_stat(/etc) mtime: %d.%09d\n", (stat _)[9], IO::AIO::st_mtimensec; |
|
|
2079 | }; |
|
|
2080 | |
|
|
2081 | IO::AIO::flush; |
|
|
2082 | |
|
|
2083 | Output of the awbove on my system, showing reduced and full accuracy: |
|
|
2084 | |
|
|
2085 | stat(/etc) mtime: 1534043702.020808 |
|
|
2086 | aio_stat(/etc) mtime: 1534043702.020807792 |
|
|
2087 | |
2037 | =head3 MISCELLANEOUS FUNCTIONS |
2088 | =head3 MISCELLANEOUS FUNCTIONS |
2038 | |
2089 | |
2039 | IO::AIO implements some functions that are useful when you want to use |
2090 | IO::AIO implements some functions that are useful when you want to use |
2040 | some "Advanced I/O" function not available to in Perl, without going the |
2091 | some "Advanced I/O" function not available to in Perl, without going the |
2041 | "Asynchronous I/O" route. Many of these have an asynchronous C<aio_*> |
2092 | "Asynchronous I/O" route. Many of these have an asynchronous C<aio_*> |
2042 | counterpart. |
2093 | counterpart. |
2043 | |
2094 | |
2044 | =over 4 |
2095 | =over 4 |
|
|
2096 | |
|
|
2097 | =item $numfd = IO::AIO::get_fdlimit |
|
|
2098 | |
|
|
2099 | This function is I<EXPERIMENTAL> and subject to change. |
|
|
2100 | |
|
|
2101 | Tries to find the current file descriptor limit and returns it, or |
|
|
2102 | C<undef> and sets C<$!> in case of an error. The limit is one larger than |
|
|
2103 | the highest valid file descriptor number. |
|
|
2104 | |
|
|
2105 | =item IO::AIO::min_fdlimit [$numfd] |
|
|
2106 | |
|
|
2107 | This function is I<EXPERIMENTAL> and subject to change. |
|
|
2108 | |
|
|
2109 | Try to increase the current file descriptor limit(s) to at least C<$numfd> |
|
|
2110 | by changing the soft or hard file descriptor resource limit. If C<$numfd> |
|
|
2111 | is missing, it will try to set a very high limit, although this is not |
|
|
2112 | recommended when you know the actual minimum that you require. |
|
|
2113 | |
|
|
2114 | If the limit cannot be raised enough, the function makes a best-effort |
|
|
2115 | attempt to increase the limit as much as possible, using various |
|
|
2116 | tricks, while still failing. You can query the resulting limit using |
|
|
2117 | C<IO::AIO::get_fdlimit>. |
|
|
2118 | |
|
|
2119 | If an error occurs, returns C<undef> and sets C<$!>, otherwise returns |
|
|
2120 | true. |
2045 | |
2121 | |
2046 | =item IO::AIO::sendfile $ofh, $ifh, $offset, $count |
2122 | =item IO::AIO::sendfile $ofh, $ifh, $offset, $count |
2047 | |
2123 | |
2048 | Calls the C<eio_sendfile_sync> function, which is like C<aio_sendfile>, |
2124 | Calls the C<eio_sendfile_sync> function, which is like C<aio_sendfile>, |
2049 | but is blocking (this makes most sense if you know the input data is |
2125 | but is blocking (this makes most sense if you know the input data is |
… | |
… | |
2066 | =item IO::AIO::madvise $scalar, $offset, $len, $advice |
2142 | =item IO::AIO::madvise $scalar, $offset, $len, $advice |
2067 | |
2143 | |
2068 | Simply calls the C<posix_madvise> function (see its |
2144 | Simply calls the C<posix_madvise> function (see its |
2069 | manpage for details). The following advice constants are |
2145 | manpage for details). The following advice constants are |
2070 | available: C<IO::AIO::MADV_NORMAL>, C<IO::AIO::MADV_SEQUENTIAL>, |
2146 | available: C<IO::AIO::MADV_NORMAL>, C<IO::AIO::MADV_SEQUENTIAL>, |
2071 | C<IO::AIO::MADV_RANDOM>, C<IO::AIO::MADV_WILLNEED>, C<IO::AIO::MADV_DONTNEED>, |
2147 | C<IO::AIO::MADV_RANDOM>, C<IO::AIO::MADV_WILLNEED>, |
2072 | C<IO::AIO::MADV_FREE>. |
2148 | C<IO::AIO::MADV_DONTNEED>. |
|
|
2149 | |
|
|
2150 | If C<$offset> is negative, counts from the end. If C<$length> is negative, |
|
|
2151 | the remaining length of the C<$scalar> is used. If possible, C<$length> |
|
|
2152 | will be reduced to fit into the C<$scalar>. |
2073 | |
2153 | |
2074 | On systems that do not implement C<posix_madvise>, this function returns |
2154 | On systems that do not implement C<posix_madvise>, this function returns |
2075 | ENOSYS, otherwise the return value of C<posix_madvise>. |
2155 | ENOSYS, otherwise the return value of C<posix_madvise>. |
2076 | |
2156 | |
2077 | =item IO::AIO::mprotect $scalar, $offset, $len, $protect |
2157 | =item IO::AIO::mprotect $scalar, $offset, $len, $protect |
2078 | |
2158 | |
2079 | Simply calls the C<mprotect> function on the preferably AIO::mmap'ed |
2159 | Simply calls the C<mprotect> function on the preferably AIO::mmap'ed |
2080 | $scalar (see its manpage for details). The following protect |
2160 | $scalar (see its manpage for details). The following protect |
2081 | constants are available: C<IO::AIO::PROT_NONE>, C<IO::AIO::PROT_READ>, |
2161 | constants are available: C<IO::AIO::PROT_NONE>, C<IO::AIO::PROT_READ>, |
2082 | C<IO::AIO::PROT_WRITE>, C<IO::AIO::PROT_EXEC>. |
2162 | C<IO::AIO::PROT_WRITE>, C<IO::AIO::PROT_EXEC>. |
|
|
2163 | |
|
|
2164 | If C<$offset> is negative, counts from the end. If C<$length> is negative, |
|
|
2165 | the remaining length of the C<$scalar> is used. If possible, C<$length> |
|
|
2166 | will be reduced to fit into the C<$scalar>. |
2083 | |
2167 | |
2084 | On systems that do not implement C<mprotect>, this function returns |
2168 | On systems that do not implement C<mprotect>, this function returns |
2085 | ENOSYS, otherwise the return value of C<mprotect>. |
2169 | ENOSYS, otherwise the return value of C<mprotect>. |
2086 | |
2170 | |
2087 | =item IO::AIO::mmap $scalar, $length, $prot, $flags, $fh[, $offset] |
2171 | =item IO::AIO::mmap $scalar, $length, $prot, $flags, $fh[, $offset] |
… | |
… | |
2148 | |
2232 | |
2149 | =item IO::AIO::munmap $scalar |
2233 | =item IO::AIO::munmap $scalar |
2150 | |
2234 | |
2151 | Removes a previous mmap and undefines the C<$scalar>. |
2235 | Removes a previous mmap and undefines the C<$scalar>. |
2152 | |
2236 | |
|
|
2237 | =item IO::AIO::mremap $scalar, $new_length, $flags = MREMAP_MAYMOVE[, $new_address = 0] |
|
|
2238 | |
|
|
2239 | Calls the Linux-specific mremap(2) system call. The C<$scalar> must have |
|
|
2240 | been mapped by C<IO::AIO::mmap>, and C<$flags> must currently either be |
|
|
2241 | C<0> or C<IO::AIO::MREMAP_MAYMOVE>. |
|
|
2242 | |
|
|
2243 | Returns true if successful, and false otherwise. If the underlying mmapped |
|
|
2244 | region has changed address, then the true value has the numerical value |
|
|
2245 | C<1>, otherwise it has the numerical value C<0>: |
|
|
2246 | |
|
|
2247 | my $success = IO::AIO::mremap $mmapped, 8192, IO::AIO::MREMAP_MAYMOVE |
|
|
2248 | or die "mremap: $!"; |
|
|
2249 | |
|
|
2250 | if ($success*1) { |
|
|
2251 | warn "scalar has chanegd address in memory\n"; |
|
|
2252 | } |
|
|
2253 | |
|
|
2254 | C<IO::AIO::MREMAP_FIXED> and the C<$new_address> argument are currently |
|
|
2255 | implemented, but not supported and might go away in a future version. |
|
|
2256 | |
|
|
2257 | On systems where this call is not supported or is not emulated, this call |
|
|
2258 | returns falls and sets C<$!> to C<ENOSYS>. |
|
|
2259 | |
2153 | =item IO::AIO::munlock $scalar, $offset = 0, $length = undef |
2260 | =item IO::AIO::munlock $scalar, $offset = 0, $length = undef |
2154 | |
2261 | |
2155 | Calls the C<munlock> function, undoing the effects of a previous |
2262 | Calls the C<munlock> function, undoing the effects of a previous |
2156 | C<aio_mlock> call (see its description for details). |
2263 | C<aio_mlock> call (see its description for details). |
2157 | |
2264 | |
… | |
… | |
2206 | C<$flags> is non-zero, fails with C<ENOSYS>. |
2313 | C<$flags> is non-zero, fails with C<ENOSYS>. |
2207 | |
2314 | |
2208 | Please refer to L<pipe2(2)> for more info on the C<$flags>, but at the |
2315 | Please refer to L<pipe2(2)> for more info on the C<$flags>, but at the |
2209 | time of this writing, C<IO::AIO::O_CLOEXEC>, C<IO::AIO::O_NONBLOCK> and |
2316 | time of this writing, C<IO::AIO::O_CLOEXEC>, C<IO::AIO::O_NONBLOCK> and |
2210 | C<IO::AIO::O_DIRECT> (Linux 3.4, for packet-based pipes) were supported. |
2317 | C<IO::AIO::O_DIRECT> (Linux 3.4, for packet-based pipes) were supported. |
|
|
2318 | |
|
|
2319 | Example: create a pipe race-free w.r.t. threads and fork: |
|
|
2320 | |
|
|
2321 | my ($rfh, $wfh) = IO::AIO::pipe2 IO::AIO::O_CLOEXEC |
|
|
2322 | or die "pipe2: $!\n"; |
|
|
2323 | |
|
|
2324 | =item $fh = IO::AIO::eventfd [$initval, [$flags]] |
|
|
2325 | |
|
|
2326 | This is a direct interface to the Linux L<eventfd(2)> system call. The |
|
|
2327 | (unhelpful) defaults for C<$initval> and C<$flags> are C<0> for both. |
|
|
2328 | |
|
|
2329 | On success, the new eventfd filehandle is returned, otherwise returns |
|
|
2330 | C<undef>. If the eventfd syscall is missing, fails with C<ENOSYS>. |
|
|
2331 | |
|
|
2332 | Please refer to L<eventfd(2)> for more info on this call. |
|
|
2333 | |
|
|
2334 | The following symbol flag values are available: C<IO::AIO::EFD_CLOEXEC>, |
|
|
2335 | C<IO::AIO::EFD_NONBLOCK> and C<IO::AIO::EFD_SEMAPHORE> (Linux 2.6.30). |
|
|
2336 | |
|
|
2337 | Example: create a new eventfd filehandle: |
|
|
2338 | |
|
|
2339 | $fh = IO::AIO::eventfd 0, IO::AIO::O_CLOEXEC |
|
|
2340 | or die "eventfd: $!\n"; |
|
|
2341 | |
|
|
2342 | =item $fh = IO::AIO::timerfd_create $clockid[, $flags] |
|
|
2343 | |
|
|
2344 | This is a direct interface to the Linux L<timerfd_create(2)> system call. The |
|
|
2345 | (unhelpful) default for C<$flags> is C<0>. |
|
|
2346 | |
|
|
2347 | On success, the new timerfd filehandle is returned, otherwise returns |
|
|
2348 | C<undef>. If the eventfd syscall is missing, fails with C<ENOSYS>. |
|
|
2349 | |
|
|
2350 | Please refer to L<timerfd_create(2)> for more info on this call. |
|
|
2351 | |
|
|
2352 | The following C<$clockid> values are |
|
|
2353 | available: C<IO::AIO::CLOCK_REALTIME>, C<IO::AIO::CLOCK_MONOTONIC> |
|
|
2354 | C<IO::AIO::CLOCK_CLOCK_BOOTTIME> (Linux 3.15) |
|
|
2355 | C<IO::AIO::CLOCK_CLOCK_REALTIME_ALARM> (Linux 3.11) and |
|
|
2356 | C<IO::AIO::CLOCK_CLOCK_BOOTTIME_ALARM> (Linux 3.11). |
|
|
2357 | |
|
|
2358 | The following C<$flags> values are available (Linux |
|
|
2359 | 2.6.27): C<IO::AIO::TFD_NONBLOCK> and C<IO::AIO::TFD_CLOEXEC>. |
|
|
2360 | |
|
|
2361 | Example: create a new timerfd and set it to one-second repeated alarms, |
|
|
2362 | then wait for two alarms: |
|
|
2363 | |
|
|
2364 | my $fh = IO::AIO::timerfd_create IO::AIO::CLOCK_BOOTTIME, IO::AIO::TFD_CLOEXEC |
|
|
2365 | or die "timerfd_create: $!\n"; |
|
|
2366 | |
|
|
2367 | defined IO::AIO::timerfd_settime $fh, 0, 1, 1 |
|
|
2368 | or die "timerfd_settime: $!\n"; |
|
|
2369 | |
|
|
2370 | for (1..2) { |
|
|
2371 | 8 == sysread $fh, my $buf, 8 |
|
|
2372 | or die "timerfd read failure\n"; |
|
|
2373 | |
|
|
2374 | printf "number of expirations (likely 1): %d\n", |
|
|
2375 | unpack "Q", $buf; |
|
|
2376 | } |
|
|
2377 | |
|
|
2378 | =item ($cur_interval, $cur_value) = IO::AIO::timerfd_settime $fh, $flags, $new_interval, $nbw_value |
|
|
2379 | |
|
|
2380 | This is a direct interface to the Linux L<timerfd_settime(2)> system |
|
|
2381 | call. Please refer to its manpage for more info on this call. |
|
|
2382 | |
|
|
2383 | The new itimerspec is specified using two (possibly fractional) second |
|
|
2384 | values, C<$new_interval> and C<$new_value>). |
|
|
2385 | |
|
|
2386 | On success, the current interval and value are returned (as per |
|
|
2387 | C<timerfd_gettime>). On failure, the empty list is returned. |
|
|
2388 | |
|
|
2389 | The following C<$flags> values are |
|
|
2390 | available: C<IO::AIO::TFD_TIMER_ABSTIME> and |
|
|
2391 | C<IO::AIO::TFD_TIMER_CANCEL_ON_SET>. |
|
|
2392 | |
|
|
2393 | See C<IO::AIO::timerfd_create> for a full example. |
|
|
2394 | |
|
|
2395 | =item ($cur_interval, $cur_value) = IO::AIO::timerfd_gettime $fh |
|
|
2396 | |
|
|
2397 | This is a direct interface to the Linux L<timerfd_gettime(2)> system |
|
|
2398 | call. Please refer to its manpage for more info on this call. |
|
|
2399 | |
|
|
2400 | On success, returns the current values of interval and value for the given |
|
|
2401 | timerfd (as potentially fractional second values). On failure, the empty |
|
|
2402 | list is returned. |
2211 | |
2403 | |
2212 | =back |
2404 | =back |
2213 | |
2405 | |
2214 | =cut |
2406 | =cut |
2215 | |
2407 | |
… | |
… | |
2281 | the process will result in undefined behaviour. Calling it at any time |
2473 | the process will result in undefined behaviour. Calling it at any time |
2282 | will also result in any undefined (by POSIX) behaviour. |
2474 | will also result in any undefined (by POSIX) behaviour. |
2283 | |
2475 | |
2284 | =back |
2476 | =back |
2285 | |
2477 | |
|
|
2478 | =head2 LINUX-SPECIFIC CALLS |
|
|
2479 | |
|
|
2480 | When a call is documented as "linux-specific" then this means it |
|
|
2481 | originated on GNU/Linux. C<IO::AIO> will usually try to autodetect the |
|
|
2482 | availability and compatibility of such calls regardless of the platform |
|
|
2483 | it is compiled on, so platforms such as FreeBSD which often implement |
|
|
2484 | these calls will work. When in doubt, call them and see if they fail wth |
|
|
2485 | C<ENOSYS>. |
|
|
2486 | |
2286 | =head2 MEMORY USAGE |
2487 | =head2 MEMORY USAGE |
2287 | |
2488 | |
2288 | Per-request usage: |
2489 | Per-request usage: |
2289 | |
2490 | |
2290 | Each aio request uses - depending on your architecture - around 100-200 |
2491 | Each aio request uses - depending on your architecture - around 100-200 |
… | |
… | |
2302 | temporary buffers, and each thread requires a stack and other data |
2503 | temporary buffers, and each thread requires a stack and other data |
2303 | structures (usually around 16k-128k, depending on the OS). |
2504 | structures (usually around 16k-128k, depending on the OS). |
2304 | |
2505 | |
2305 | =head1 KNOWN BUGS |
2506 | =head1 KNOWN BUGS |
2306 | |
2507 | |
2307 | Known bugs will be fixed in the next release. |
2508 | Known bugs will be fixed in the next release :) |
|
|
2509 | |
|
|
2510 | =head1 KNOWN ISSUES |
|
|
2511 | |
|
|
2512 | Calls that try to "import" foreign memory areas (such as C<IO::AIO::mmap> |
|
|
2513 | or C<IO::AIO::aio_slurp>) do not work with generic lvalues, such as |
|
|
2514 | non-created hash slots or other scalars I didn't think of. It's best to |
|
|
2515 | avoid such and either use scalar variables or making sure that the scalar |
|
|
2516 | exists (e.g. by storing C<undef>) and isn't "funny" (e.g. tied). |
|
|
2517 | |
|
|
2518 | I am not sure anything can be done about this, so this is considered a |
|
|
2519 | known issue, rather than a bug. |
2308 | |
2520 | |
2309 | =head1 SEE ALSO |
2521 | =head1 SEE ALSO |
2310 | |
2522 | |
2311 | L<AnyEvent::AIO> for easy integration into event loops, L<Coro::AIO> for a |
2523 | L<AnyEvent::AIO> for easy integration into event loops, L<Coro::AIO> for a |
2312 | more natural syntax. |
2524 | more natural syntax. |