| 1 | NAME |
1 | NAME |
| 2 | IO::AIO - Asynchronous Input/Output |
2 | IO::AIO - Asynchronous/Advanced Input/Output |
| 3 | |
3 | |
| 4 | SYNOPSIS |
4 | SYNOPSIS |
| 5 | use IO::AIO; |
5 | use IO::AIO; |
| 6 | |
6 | |
| 7 | aio_open "/etc/passwd", IO::AIO::O_RDONLY, 0, sub { |
7 | aio_open "/etc/passwd", IO::AIO::O_RDONLY, 0, sub { |
| … | |
… | |
| 55 | not well-supported or restricted (GNU/Linux doesn't allow them on normal |
55 | not well-supported or restricted (GNU/Linux doesn't allow them on normal |
| 56 | files currently, for example), and they would only support aio_read and |
56 | files currently, for example), and they would only support aio_read and |
| 57 | aio_write, so the remaining functionality would have to be implemented |
57 | aio_write, so the remaining functionality would have to be implemented |
| 58 | using threads anyway. |
58 | using threads anyway. |
| 59 | |
59 | |
|
|
60 | In addition to asynchronous I/O, this module also exports some rather |
|
|
61 | arcane interfaces, such as "madvise" or linux's "splice" system call, |
|
|
62 | which is why the "A" in "AIO" can also mean *advanced*. |
|
|
63 | |
| 60 | Although the module will work in the presence of other (Perl-) threads, |
64 | Although the module will work in the presence of other (Perl-) threads, |
| 61 | it is currently not reentrant in any way, so use appropriate locking |
65 | it is currently not reentrant in any way, so use appropriate locking |
| 62 | yourself, always call "poll_cb" from within the same thread, or never |
66 | yourself, always call "poll_cb" from within the same thread, or never |
| 63 | call "poll_cb" (or other "aio_" functions) recursively. |
67 | call "poll_cb" (or other "aio_" functions) recursively. |
| 64 | |
68 | |
| 65 | EXAMPLE |
69 | EXAMPLE |
| 66 | This is a simple example that uses the EV module and loads /etc/passwd |
70 | This is a simple example that uses the EV module and loads /etc/passwd |
| 67 | asynchronously: |
71 | asynchronously: |
| 68 | |
72 | |
| 69 | use Fcntl; |
|
|
| 70 | use EV; |
73 | use EV; |
| 71 | use IO::AIO; |
74 | use IO::AIO; |
| 72 | |
75 | |
| 73 | # register the IO::AIO callback with EV |
76 | # register the IO::AIO callback with EV |
| 74 | my $aio_w = EV::io IO::AIO::poll_fileno, EV::READ, \&IO::AIO::poll_cb; |
77 | my $aio_w = EV::io IO::AIO::poll_fileno, EV::READ, \&IO::AIO::poll_cb; |
| … | |
… | |
| 91 | |
94 | |
| 92 | # file contents now in $contents |
95 | # file contents now in $contents |
| 93 | print $contents; |
96 | print $contents; |
| 94 | |
97 | |
| 95 | # exit event loop and program |
98 | # exit event loop and program |
| 96 | EV::unloop; |
99 | EV::break; |
| 97 | }; |
100 | }; |
| 98 | }; |
101 | }; |
| 99 | |
102 | |
| 100 | # possibly queue up other requests, or open GUI windows, |
103 | # possibly queue up other requests, or open GUI windows, |
| 101 | # check for sockets etc. etc. |
104 | # check for sockets etc. etc. |
| 102 | |
105 | |
| 103 | # process events as long as there are some: |
106 | # process events as long as there are some: |
| 104 | EV::loop; |
107 | EV::run; |
| 105 | |
108 | |
| 106 | REQUEST ANATOMY AND LIFETIME |
109 | REQUEST ANATOMY AND LIFETIME |
| 107 | Every "aio_*" function creates a request. which is a C data structure |
110 | Every "aio_*" function creates a request. which is a C data structure |
| 108 | not directly visible to Perl. |
111 | not directly visible to Perl. |
| 109 | |
112 | |
| … | |
… | |
| 172 | aio_unlink $pathname, $callback->($status) |
175 | aio_unlink $pathname, $callback->($status) |
| 173 | aio_mknod $pathname, $mode, $dev, $callback->($status) |
176 | aio_mknod $pathname, $mode, $dev, $callback->($status) |
| 174 | aio_link $srcpath, $dstpath, $callback->($status) |
177 | aio_link $srcpath, $dstpath, $callback->($status) |
| 175 | aio_symlink $srcpath, $dstpath, $callback->($status) |
178 | aio_symlink $srcpath, $dstpath, $callback->($status) |
| 176 | aio_readlink $pathname, $callback->($link) |
179 | aio_readlink $pathname, $callback->($link) |
| 177 | aio_realpath $pathname, $callback->($link) |
180 | aio_realpath $pathname, $callback->($path) |
| 178 | aio_rename $srcpath, $dstpath, $callback->($status) |
181 | aio_rename $srcpath, $dstpath, $callback->($status) |
|
|
182 | aio_rename2 $srcpath, $dstpath, $flags, $callback->($status) |
| 179 | aio_mkdir $pathname, $mode, $callback->($status) |
183 | aio_mkdir $pathname, $mode, $callback->($status) |
| 180 | aio_rmdir $pathname, $callback->($status) |
184 | aio_rmdir $pathname, $callback->($status) |
| 181 | aio_readdir $pathname, $callback->($entries) |
185 | aio_readdir $pathname, $callback->($entries) |
| 182 | aio_readdirx $pathname, $flags, $callback->($entries, $flags) |
186 | aio_readdirx $pathname, $flags, $callback->($entries, $flags) |
| 183 | IO::AIO::READDIR_DENTS IO::AIO::READDIR_DIRS_FIRST |
187 | IO::AIO::READDIR_DENTS IO::AIO::READDIR_DIRS_FIRST |
| … | |
… | |
| 185 | aio_scandir $pathname, $maxreq, $callback->($dirs, $nondirs) |
189 | aio_scandir $pathname, $maxreq, $callback->($dirs, $nondirs) |
| 186 | aio_load $pathname, $data, $callback->($status) |
190 | aio_load $pathname, $data, $callback->($status) |
| 187 | aio_copy $srcpath, $dstpath, $callback->($status) |
191 | aio_copy $srcpath, $dstpath, $callback->($status) |
| 188 | aio_move $srcpath, $dstpath, $callback->($status) |
192 | aio_move $srcpath, $dstpath, $callback->($status) |
| 189 | aio_rmtree $pathname, $callback->($status) |
193 | aio_rmtree $pathname, $callback->($status) |
|
|
194 | aio_fcntl $fh, $cmd, $arg, $callback->($status) |
|
|
195 | aio_ioctl $fh, $request, $buf, $callback->($status) |
| 190 | aio_sync $callback->($status) |
196 | aio_sync $callback->($status) |
| 191 | aio_syncfs $fh, $callback->($status) |
197 | aio_syncfs $fh, $callback->($status) |
| 192 | aio_fsync $fh, $callback->($status) |
198 | aio_fsync $fh, $callback->($status) |
| 193 | aio_fdatasync $fh, $callback->($status) |
199 | aio_fdatasync $fh, $callback->($status) |
| 194 | aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status) |
200 | aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status) |
| 195 | aio_pathsync $pathname, $callback->($status) |
201 | aio_pathsync $pathname, $callback->($status) |
| 196 | aio_msync $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status) |
202 | aio_msync $scalar, $offset = 0, $length = undef, flags = MS_SYNC, $callback->($status) |
| 197 | aio_mtouch $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status) |
203 | aio_mtouch $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status) |
| 198 | aio_mlock $scalar, $offset = 0, $length = undef, $callback->($status) |
204 | aio_mlock $scalar, $offset = 0, $length = undef, $callback->($status) |
| 199 | aio_mlockall $flags, $callback->($status) |
205 | aio_mlockall $flags, $callback->($status) |
| 200 | aio_group $callback->(...) |
206 | aio_group $callback->(...) |
| 201 | aio_nop $callback->() |
207 | aio_nop $callback->() |
| … | |
… | |
| 215 | IO::AIO::idle_timeout $seconds |
221 | IO::AIO::idle_timeout $seconds |
| 216 | IO::AIO::max_outstanding $maxreqs |
222 | IO::AIO::max_outstanding $maxreqs |
| 217 | IO::AIO::nreqs |
223 | IO::AIO::nreqs |
| 218 | IO::AIO::nready |
224 | IO::AIO::nready |
| 219 | IO::AIO::npending |
225 | IO::AIO::npending |
|
|
226 | $nfd = IO::AIO::get_fdlimit [EXPERIMENTAL] |
|
|
227 | IO::AIO::min_fdlimit $nfd [EXPERIMENTAL] |
| 220 | |
228 | |
| 221 | IO::AIO::sendfile $ofh, $ifh, $offset, $count |
229 | IO::AIO::sendfile $ofh, $ifh, $offset, $count |
| 222 | IO::AIO::fadvise $fh, $offset, $len, $advice |
230 | IO::AIO::fadvise $fh, $offset, $len, $advice |
| 223 | IO::AIO::mmap $scalar, $length, $prot, $flags[, $fh[, $offset]] |
231 | IO::AIO::mmap $scalar, $length, $prot, $flags[, $fh[, $offset]] |
| 224 | IO::AIO::munmap $scalar |
232 | IO::AIO::munmap $scalar |
| … | |
… | |
| 331 | "O_APPEND"), the following POSIX and non-POSIX constants are |
339 | "O_APPEND"), the following POSIX and non-POSIX constants are |
| 332 | available (missing ones on your system are, as usual, 0): |
340 | available (missing ones on your system are, as usual, 0): |
| 333 | |
341 | |
| 334 | "O_ASYNC", "O_DIRECT", "O_NOATIME", "O_CLOEXEC", "O_NOCTTY", |
342 | "O_ASYNC", "O_DIRECT", "O_NOATIME", "O_CLOEXEC", "O_NOCTTY", |
| 335 | "O_NOFOLLOW", "O_NONBLOCK", "O_EXEC", "O_SEARCH", "O_DIRECTORY", |
343 | "O_NOFOLLOW", "O_NONBLOCK", "O_EXEC", "O_SEARCH", "O_DIRECTORY", |
| 336 | "O_DSYNC", "O_RSYNC", "O_SYNC" and "O_TTY_INIT". |
344 | "O_DSYNC", "O_RSYNC", "O_SYNC", "O_PATH", "O_TMPFILE", and |
|
|
345 | "O_TTY_INIT". |
| 337 | |
346 | |
| 338 | aio_close $fh, $callback->($status) |
347 | aio_close $fh, $callback->($status) |
| 339 | Asynchronously close a file and call the callback with the result |
348 | Asynchronously close a file and call the callback with the result |
| 340 | code. |
349 | code. |
| 341 | |
350 | |
| … | |
… | |
| 371 | |
380 | |
| 372 | aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
381 | aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
| 373 | aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
382 | aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
| 374 | Reads or writes $length bytes from or to the specified $fh and |
383 | Reads or writes $length bytes from or to the specified $fh and |
| 375 | $offset into the scalar given by $data and offset $dataoffset and |
384 | $offset into the scalar given by $data and offset $dataoffset and |
| 376 | calls the callback without the actual number of bytes read (or -1 on |
385 | calls the callback with the actual number of bytes transferred (or |
| 377 | error, just like the syscall). |
386 | -1 on error, just like the syscall). |
| 378 | |
387 | |
| 379 | "aio_read" will, like "sysread", shrink or grow the $data scalar to |
388 | "aio_read" will, like "sysread", shrink or grow the $data scalar to |
| 380 | offset plus the actual number of bytes read. |
389 | offset plus the actual number of bytes read. |
| 381 | |
390 | |
| 382 | If $offset is undefined, then the current file descriptor offset |
391 | If $offset is undefined, then the current file descriptor offset |
| … | |
… | |
| 439 | As native sendfile syscalls (as practically any non-POSIX interface |
448 | As native sendfile syscalls (as practically any non-POSIX interface |
| 440 | hacked together in a hurry to improve benchmark numbers) tend to be |
449 | hacked together in a hurry to improve benchmark numbers) tend to be |
| 441 | rather buggy on many systems, this implementation tries to work |
450 | rather buggy on many systems, this implementation tries to work |
| 442 | around some known bugs in Linux and FreeBSD kernels (probably |
451 | around some known bugs in Linux and FreeBSD kernels (probably |
| 443 | others, too), but that might fail, so you really really should check |
452 | others, too), but that might fail, so you really really should check |
| 444 | the return value of "aio_sendfile" - fewre bytes than expected might |
453 | the return value of "aio_sendfile" - fewer bytes than expected might |
| 445 | have been transferred. |
454 | have been transferred. |
| 446 | |
455 | |
| 447 | aio_readahead $fh,$offset,$length, $callback->($retval) |
456 | aio_readahead $fh,$offset,$length, $callback->($retval) |
| 448 | "aio_readahead" populates the page cache with data from a file so |
457 | "aio_readahead" populates the page cache with data from a file so |
| 449 | that subsequent reads from that file will not block on disk I/O. The |
458 | that subsequent reads from that file will not block on disk I/O. The |
| … | |
… | |
| 453 | to a page boundary and bytes are read up to the next page boundary |
462 | to a page boundary and bytes are read up to the next page boundary |
| 454 | greater than or equal to (off-set+length). "aio_readahead" does not |
463 | greater than or equal to (off-set+length). "aio_readahead" does not |
| 455 | read beyond the end of the file. The current file offset of the file |
464 | read beyond the end of the file. The current file offset of the file |
| 456 | is left unchanged. |
465 | is left unchanged. |
| 457 | |
466 | |
| 458 | If that syscall doesn't exist (likely if your OS isn't Linux) it |
467 | If that syscall doesn't exist (likely if your kernel isn't Linux) it |
| 459 | will be emulated by simply reading the data, which would have a |
468 | will be emulated by simply reading the data, which would have a |
| 460 | similar effect. |
469 | similar effect. |
| 461 | |
470 | |
| 462 | aio_stat $fh_or_path, $callback->($status) |
471 | aio_stat $fh_or_path, $callback->($status) |
| 463 | aio_lstat $fh, $callback->($status) |
472 | aio_lstat $fh, $callback->($status) |
| … | |
… | |
| 530 | namemax => 255, |
539 | namemax => 255, |
| 531 | frsize => 1024, |
540 | frsize => 1024, |
| 532 | fsid => 1810 |
541 | fsid => 1810 |
| 533 | } |
542 | } |
| 534 | |
543 | |
| 535 | Here is a (likely partial) list of fsid values used by Linux - it is |
|
|
| 536 | safe to hardcode these when the $^O is "linux": |
|
|
| 537 | |
|
|
| 538 | 0x0000adf5 adfs |
|
|
| 539 | 0x0000adff affs |
|
|
| 540 | 0x5346414f afs |
|
|
| 541 | 0x09041934 anon-inode filesystem |
|
|
| 542 | 0x00000187 autofs |
|
|
| 543 | 0x42465331 befs |
|
|
| 544 | 0x1badface bfs |
|
|
| 545 | 0x42494e4d binfmt_misc |
|
|
| 546 | 0x9123683e btrfs |
|
|
| 547 | 0x0027e0eb cgroupfs |
|
|
| 548 | 0xff534d42 cifs |
|
|
| 549 | 0x73757245 coda |
|
|
| 550 | 0x012ff7b7 coh |
|
|
| 551 | 0x28cd3d45 cramfs |
|
|
| 552 | 0x453dcd28 cramfs-wend (wrong endianness) |
|
|
| 553 | 0x64626720 debugfs |
|
|
| 554 | 0x00001373 devfs |
|
|
| 555 | 0x00001cd1 devpts |
|
|
| 556 | 0x0000f15f ecryptfs |
|
|
| 557 | 0x00414a53 efs |
|
|
| 558 | 0x0000137d ext |
|
|
| 559 | 0x0000ef53 ext2/ext3 |
|
|
| 560 | 0x0000ef51 ext2 |
|
|
| 561 | 0x00004006 fat |
|
|
| 562 | 0x65735546 fuseblk |
|
|
| 563 | 0x65735543 fusectl |
|
|
| 564 | 0x0bad1dea futexfs |
|
|
| 565 | 0x01161970 gfs2 |
|
|
| 566 | 0x47504653 gpfs |
|
|
| 567 | 0x00004244 hfs |
|
|
| 568 | 0xf995e849 hpfs |
|
|
| 569 | 0x958458f6 hugetlbfs |
|
|
| 570 | 0x2bad1dea inotifyfs |
|
|
| 571 | 0x00009660 isofs |
|
|
| 572 | 0x000072b6 jffs2 |
|
|
| 573 | 0x3153464a jfs |
|
|
| 574 | 0x6b414653 k-afs |
|
|
| 575 | 0x0bd00bd0 lustre |
|
|
| 576 | 0x0000137f minix |
|
|
| 577 | 0x0000138f minix 30 char names |
|
|
| 578 | 0x00002468 minix v2 |
|
|
| 579 | 0x00002478 minix v2 30 char names |
|
|
| 580 | 0x00004d5a minix v3 |
|
|
| 581 | 0x19800202 mqueue |
|
|
| 582 | 0x00004d44 msdos |
|
|
| 583 | 0x0000564c novell |
|
|
| 584 | 0x00006969 nfs |
|
|
| 585 | 0x6e667364 nfsd |
|
|
| 586 | 0x00003434 nilfs |
|
|
| 587 | 0x5346544e ntfs |
|
|
| 588 | 0x00009fa1 openprom |
|
|
| 589 | 0x7461636F ocfs2 |
|
|
| 590 | 0x00009fa0 proc |
|
|
| 591 | 0x6165676c pstorefs |
|
|
| 592 | 0x0000002f qnx4 |
|
|
| 593 | 0x858458f6 ramfs |
|
|
| 594 | 0x52654973 reiserfs |
|
|
| 595 | 0x00007275 romfs |
|
|
| 596 | 0x67596969 rpc_pipefs |
|
|
| 597 | 0x73636673 securityfs |
|
|
| 598 | 0xf97cff8c selinux |
|
|
| 599 | 0x0000517b smb |
|
|
| 600 | 0x534f434b sockfs |
|
|
| 601 | 0x73717368 squashfs |
|
|
| 602 | 0x62656572 sysfs |
|
|
| 603 | 0x012ff7b6 sysv2 |
|
|
| 604 | 0x012ff7b5 sysv4 |
|
|
| 605 | 0x01021994 tmpfs |
|
|
| 606 | 0x15013346 udf |
|
|
| 607 | 0x00011954 ufs |
|
|
| 608 | 0x54190100 ufs byteswapped |
|
|
| 609 | 0x00009fa2 usbdevfs |
|
|
| 610 | 0x01021997 v9fs |
|
|
| 611 | 0xa501fcf5 vxfs |
|
|
| 612 | 0xabba1974 xenfs |
|
|
| 613 | 0x012ff7b4 xenix |
|
|
| 614 | 0x58465342 xfs |
|
|
| 615 | 0x012fd16d xia |
|
|
| 616 | |
|
|
| 617 | aio_utime $fh_or_path, $atime, $mtime, $callback->($status) |
544 | aio_utime $fh_or_path, $atime, $mtime, $callback->($status) |
| 618 | Works like perl's "utime" function (including the special case of |
545 | Works like perl's "utime" function (including the special case of |
| 619 | $atime and $mtime being undef). Fractional times are supported if |
546 | $atime and $mtime being undef). Fractional times are supported if |
| 620 | the underlying syscalls support them. |
547 | the underlying syscalls support them. |
| 621 | |
548 | |
| … | |
… | |
| 644 | |
571 | |
| 645 | aio_truncate $fh_or_path, $offset, $callback->($status) |
572 | aio_truncate $fh_or_path, $offset, $callback->($status) |
| 646 | Works like truncate(2) or ftruncate(2). |
573 | Works like truncate(2) or ftruncate(2). |
| 647 | |
574 | |
| 648 | aio_allocate $fh, $mode, $offset, $len, $callback->($status) |
575 | aio_allocate $fh, $mode, $offset, $len, $callback->($status) |
| 649 | Allocates or freed disk space according to the $mode argument. See |
576 | Allocates or frees disk space according to the $mode argument. See |
| 650 | the linux "fallocate" docuemntation for details. |
577 | the linux "fallocate" documentation for details. |
| 651 | |
578 | |
| 652 | $mode can currently be 0 or "IO::AIO::FALLOC_FL_KEEP_SIZE" to |
579 | $mode is usually 0 or "IO::AIO::FALLOC_FL_KEEP_SIZE" to allocate |
| 653 | allocate space, or "IO::AIO::FALLOC_FL_PUNCH_HOLE | |
580 | space, or "IO::AIO::FALLOC_FL_PUNCH_HOLE | |
| 654 | IO::AIO::FALLOC_FL_KEEP_SIZE", to deallocate a file range. |
581 | IO::AIO::FALLOC_FL_KEEP_SIZE", to deallocate a file range. |
| 655 | |
582 | |
|
|
583 | IO::AIO also supports "FALLOC_FL_COLLAPSE_RANGE", to remove a range |
|
|
584 | (without leaving a hole), "FALLOC_FL_ZERO_RANGE", to zero a range, |
|
|
585 | "FALLOC_FL_INSERT_RANGE" to insert a range and |
|
|
586 | "FALLOC_FL_UNSHARE_RANGE" to unshare shared blocks (see your |
|
|
587 | fallocate(2) manpage). |
|
|
588 | |
| 656 | The file system block size used by "fallocate" is presumably the |
589 | The file system block size used by "fallocate" is presumably the |
| 657 | "f_bsize" returned by "statvfs". |
590 | "f_bsize" returned by "statvfs", but different filesystems and |
|
|
591 | filetypes can dictate other limitations. |
| 658 | |
592 | |
| 659 | If "fallocate" isn't available or cannot be emulated (currently no |
593 | If "fallocate" isn't available or cannot be emulated (currently no |
| 660 | emulation will be attempted), passes -1 and sets $! to "ENOSYS". |
594 | emulation will be attempted), passes -1 and sets $! to "ENOSYS". |
| 661 | |
595 | |
| 662 | aio_chmod $fh_or_path, $mode, $callback->($status) |
596 | aio_chmod $fh_or_path, $mode, $callback->($status) |
| … | |
… | |
| 692 | the callback. If an error occurs, nothing or undef gets passed to |
626 | the callback. If an error occurs, nothing or undef gets passed to |
| 693 | the callback. |
627 | the callback. |
| 694 | |
628 | |
| 695 | aio_realpath $pathname, $callback->($path) |
629 | aio_realpath $pathname, $callback->($path) |
| 696 | Asynchronously make the path absolute and resolve any symlinks in |
630 | Asynchronously make the path absolute and resolve any symlinks in |
| 697 | $path. The resulting path only consists of directories (Same as |
631 | $path. The resulting path only consists of directories (same as |
| 698 | Cwd::realpath). |
632 | Cwd::realpath). |
| 699 | |
633 | |
| 700 | This request can be used to get the absolute path of the current |
634 | This request can be used to get the absolute path of the current |
| 701 | working directory by passing it a path of . (a single dot). |
635 | working directory by passing it a path of . (a single dot). |
| 702 | |
636 | |
| 703 | aio_rename $srcpath, $dstpath, $callback->($status) |
637 | aio_rename $srcpath, $dstpath, $callback->($status) |
| 704 | Asynchronously rename the object at $srcpath to $dstpath, just as |
638 | Asynchronously rename the object at $srcpath to $dstpath, just as |
| 705 | rename(2) and call the callback with the result code. |
639 | rename(2) and call the callback with the result code. |
|
|
640 | |
|
|
641 | On systems that support the AIO::WD working directory abstraction |
|
|
642 | natively, the case "[$wd, "."]" as $srcpath is specialcased - |
|
|
643 | instead of failing, "rename" is called on the absolute path of $wd. |
|
|
644 | |
|
|
645 | aio_rename2 $srcpath, $dstpath, $flags, $callback->($status) |
|
|
646 | Basically a version of "aio_rename" with an additional $flags |
|
|
647 | argument. Calling this with "$flags=0" is the same as calling |
|
|
648 | "aio_rename". |
|
|
649 | |
|
|
650 | Non-zero flags are currently only supported on GNU/Linux systems |
|
|
651 | that support renameat2. Other systems fail with "ENOSYS" in this |
|
|
652 | case. |
|
|
653 | |
|
|
654 | The following constants are available (missing ones are, as usual |
|
|
655 | 0), see renameat2(2) for details: |
|
|
656 | |
|
|
657 | "IO::AIO::RENAME_NOREPLACE", "IO::AIO::RENAME_EXCHANGE" and |
|
|
658 | "IO::AIO::RENAME_WHITEOUT". |
| 706 | |
659 | |
| 707 | aio_mkdir $pathname, $mode, $callback->($status) |
660 | aio_mkdir $pathname, $mode, $callback->($status) |
| 708 | Asynchronously mkdir (create) a directory and call the callback with |
661 | Asynchronously mkdir (create) a directory and call the callback with |
| 709 | the result code. $mode will be modified by the umask at the time the |
662 | the result code. $mode will be modified by the umask at the time the |
| 710 | request is executed, so do not change your umask. |
663 | request is executed, so do not change your umask. |
| 711 | |
664 | |
| 712 | aio_rmdir $pathname, $callback->($status) |
665 | aio_rmdir $pathname, $callback->($status) |
| 713 | Asynchronously rmdir (delete) a directory and call the callback with |
666 | Asynchronously rmdir (delete) a directory and call the callback with |
| 714 | the result code. |
667 | the result code. |
|
|
668 | |
|
|
669 | On systems that support the AIO::WD working directory abstraction |
|
|
670 | natively, the case "[$wd, "."]" is specialcased - instead of |
|
|
671 | failing, "rmdir" is called on the absolute path of $wd. |
| 715 | |
672 | |
| 716 | aio_readdir $pathname, $callback->($entries) |
673 | aio_readdir $pathname, $callback->($entries) |
| 717 | Unlike the POSIX call of the same name, "aio_readdir" reads an |
674 | Unlike the POSIX call of the same name, "aio_readdir" reads an |
| 718 | entire directory (i.e. opendir + readdir + closedir). The entries |
675 | entire directory (i.e. opendir + readdir + closedir). The entries |
| 719 | will not be sorted, and will NOT include the "." and ".." entries. |
676 | will not be sorted, and will NOT include the "." and ".." entries. |
| … | |
… | |
| 781 | Instead, it is being set by "aio_readdirx", when any of the |
738 | Instead, it is being set by "aio_readdirx", when any of the |
| 782 | $type's found were "IO::AIO::DT_UNKNOWN". The absence of this |
739 | $type's found were "IO::AIO::DT_UNKNOWN". The absence of this |
| 783 | flag therefore indicates that all $type's are known, which can |
740 | flag therefore indicates that all $type's are known, which can |
| 784 | be used to speed up some algorithms. |
741 | be used to speed up some algorithms. |
| 785 | |
742 | |
|
|
743 | aio_slurp $pathname, $offset, $length, $data, $callback->($status) |
|
|
744 | Opens, reads and closes the given file. The data is put into $data, |
|
|
745 | which is resized as required. |
|
|
746 | |
|
|
747 | If $offset is negative, then it is counted from the end of the file. |
|
|
748 | |
|
|
749 | If $length is zero, then the remaining length of the file is used. |
|
|
750 | Also, in this case, the same limitations to modifying $data apply as |
|
|
751 | when IO::AIO::mmap is used, i.e. it must only be modified in-place |
|
|
752 | with "substr". If the size of the file is known, specifying a |
|
|
753 | non-zero $length results in a performance advantage. |
|
|
754 | |
|
|
755 | This request is similar to the older "aio_load" request, but since |
|
|
756 | it is a single request, it might be more efficient to use. |
|
|
757 | |
|
|
758 | Example: load /etc/passwd into $passwd. |
|
|
759 | |
|
|
760 | my $passwd; |
|
|
761 | aio_slurp "/etc/passwd", 0, 0, $passwd, sub { |
|
|
762 | $_[0] >= 0 |
|
|
763 | or die "/etc/passwd: $!\n"; |
|
|
764 | |
|
|
765 | printf "/etc/passwd is %d bytes long, and contains:\n", length $passwd; |
|
|
766 | print $passwd; |
|
|
767 | }; |
|
|
768 | IO::AIO::flush; |
|
|
769 | |
| 786 | aio_load $pathname, $data, $callback->($status) |
770 | aio_load $pathname, $data, $callback->($status) |
| 787 | This is a composite request that tries to fully load the given file |
771 | This is a composite request that tries to fully load the given file |
| 788 | into memory. Status is the same as with aio_read. |
772 | into memory. Status is the same as with aio_read. |
|
|
773 | |
|
|
774 | Using "aio_slurp" might be more efficient, as it is a single |
|
|
775 | request. |
| 789 | |
776 | |
| 790 | aio_copy $srcpath, $dstpath, $callback->($status) |
777 | aio_copy $srcpath, $dstpath, $callback->($status) |
| 791 | Try to copy the *file* (directories not supported as either source |
778 | Try to copy the *file* (directories not supported as either source |
| 792 | or destination) from $srcpath to $dstpath and call the callback with |
779 | or destination) from $srcpath to $dstpath and call the callback with |
| 793 | a status of 0 (ok) or -1 (error, see $!). |
780 | a status of 0 (ok) or -1 (error, see $!). |
|
|
781 | |
|
|
782 | Existing destination files will be truncated. |
| 794 | |
783 | |
| 795 | This is a composite request that creates the destination file with |
784 | This is a composite request that creates the destination file with |
| 796 | mode 0200 and copies the contents of the source file into it using |
785 | mode 0200 and copies the contents of the source file into it using |
| 797 | "aio_sendfile", followed by restoring atime, mtime, access mode and |
786 | "aio_sendfile", followed by restoring atime, mtime, access mode and |
| 798 | uid/gid, in that order. |
787 | uid/gid, in that order. |
| … | |
… | |
| 815 | to efficiently separate the entries of directory $path into two sets |
804 | to efficiently separate the entries of directory $path into two sets |
| 816 | of names, directories you can recurse into (directories), and ones |
805 | of names, directories you can recurse into (directories), and ones |
| 817 | you cannot recurse into (everything else, including symlinks to |
806 | you cannot recurse into (everything else, including symlinks to |
| 818 | directories). |
807 | directories). |
| 819 | |
808 | |
| 820 | "aio_scandir" is a composite request that creates of many sub |
809 | "aio_scandir" is a composite request that generates many sub |
| 821 | requests_ $maxreq specifies the maximum number of outstanding aio |
810 | requests. $maxreq specifies the maximum number of outstanding aio |
| 822 | requests that this function generates. If it is "<= 0", then a |
811 | requests that this function generates. If it is "<= 0", then a |
| 823 | suitable default will be chosen (currently 4). |
812 | suitable default will be chosen (currently 4). |
| 824 | |
813 | |
| 825 | On error, the callback is called without arguments, otherwise it |
814 | On error, the callback is called without arguments, otherwise it |
| 826 | receives two array-refs with path-relative entry names. |
815 | receives two array-refs with path-relative entry names. |
| … | |
… | |
| 873 | Delete a directory tree starting (and including) $path, return the |
862 | Delete a directory tree starting (and including) $path, return the |
| 874 | status of the final "rmdir" only. This is a composite request that |
863 | status of the final "rmdir" only. This is a composite request that |
| 875 | uses "aio_scandir" to recurse into and rmdir directories, and unlink |
864 | uses "aio_scandir" to recurse into and rmdir directories, and unlink |
| 876 | everything else. |
865 | everything else. |
| 877 | |
866 | |
|
|
867 | aio_fcntl $fh, $cmd, $arg, $callback->($status) |
|
|
868 | aio_ioctl $fh, $request, $buf, $callback->($status) |
|
|
869 | These work just like the "fcntl" and "ioctl" built-in functions, |
|
|
870 | except they execute asynchronously and pass the return value to the |
|
|
871 | callback. |
|
|
872 | |
|
|
873 | Both calls can be used for a lot of things, some of which make more |
|
|
874 | sense to run asynchronously in their own thread, while some others |
|
|
875 | make less sense. For example, calls that block waiting for external |
|
|
876 | events, such as locking, will also lock down an I/O thread while it |
|
|
877 | is waiting, which can deadlock the whole I/O system. At the same |
|
|
878 | time, there might be no alternative to using a thread to wait. |
|
|
879 | |
|
|
880 | So in general, you should only use these calls for things that do |
|
|
881 | (filesystem) I/O, not for things that wait for other events |
|
|
882 | (network, other processes), although if you are careful and know |
|
|
883 | what you are doing, you still can. |
|
|
884 | |
|
|
885 | The following constants are available (missing ones are, as usual |
|
|
886 | 0): |
|
|
887 | |
|
|
888 | "F_DUPFD_CLOEXEC", |
|
|
889 | |
|
|
890 | "F_OFD_GETLK", "F_OFD_SETLK", "F_OFD_GETLKW", |
|
|
891 | |
|
|
892 | "FIFREEZE", "FITHAW", "FITRIM", "FICLONE", "FICLONERANGE", |
|
|
893 | "FIDEDUPERANGE". |
|
|
894 | |
|
|
895 | "FS_IOC_GETFLAGS", "FS_IOC_SETFLAGS", "FS_IOC_GETVERSION", |
|
|
896 | "FS_IOC_SETVERSION", "FS_IOC_FIEMAP". |
|
|
897 | |
|
|
898 | "FS_IOC_FSGETXATTR", "FS_IOC_FSSETXATTR", |
|
|
899 | "FS_IOC_SET_ENCRYPTION_POLICY", "FS_IOC_GET_ENCRYPTION_PWSALT", |
|
|
900 | "FS_IOC_GET_ENCRYPTION_POLICY", "FS_KEY_DESCRIPTOR_SIZE". |
|
|
901 | |
|
|
902 | "FS_SECRM_FL", "FS_UNRM_FL", "FS_COMPR_FL", "FS_SYNC_FL", |
|
|
903 | "FS_IMMUTABLE_FL", "FS_APPEND_FL", "FS_NODUMP_FL", "FS_NOATIME_FL", |
|
|
904 | "FS_DIRTY_FL", "FS_COMPRBLK_FL", "FS_NOCOMP_FL", "FS_ENCRYPT_FL", |
|
|
905 | "FS_BTREE_FL", "FS_INDEX_FL", "FS_JOURNAL_DATA_FL", "FS_NOTAIL_FL", |
|
|
906 | "FS_DIRSYNC_FL", "FS_TOPDIR_FL", "FS_FL_USER_MODIFIABLE". |
|
|
907 | |
|
|
908 | "FS_XFLAG_REALTIME", "FS_XFLAG_PREALLOC", "FS_XFLAG_IMMUTABLE", |
|
|
909 | "FS_XFLAG_APPEND", "FS_XFLAG_SYNC", "FS_XFLAG_NOATIME", |
|
|
910 | "FS_XFLAG_NODUMP", "FS_XFLAG_RTINHERIT", "FS_XFLAG_PROJINHERIT", |
|
|
911 | "FS_XFLAG_NOSYMLINKS", "FS_XFLAG_EXTSIZE", "FS_XFLAG_EXTSZINHERIT", |
|
|
912 | "FS_XFLAG_NODEFRAG", "FS_XFLAG_FILESTREAM", "FS_XFLAG_DAX", |
|
|
913 | "FS_XFLAG_HASATTR", |
|
|
914 | |
| 878 | aio_sync $callback->($status) |
915 | aio_sync $callback->($status) |
| 879 | Asynchronously call sync and call the callback when finished. |
916 | Asynchronously call sync and call the callback when finished. |
| 880 | |
917 | |
| 881 | aio_fsync $fh, $callback->($status) |
918 | aio_fsync $fh, $callback->($status) |
| 882 | Asynchronously call fsync on the given filehandle and call the |
919 | Asynchronously call fsync on the given filehandle and call the |
| … | |
… | |
| 918 | Future versions of this function might fall back to other methods |
955 | Future versions of this function might fall back to other methods |
| 919 | when "fsync" on the directory fails (such as calling "sync"). |
956 | when "fsync" on the directory fails (such as calling "sync"). |
| 920 | |
957 | |
| 921 | Passes 0 when everything went ok, and -1 on error. |
958 | Passes 0 when everything went ok, and -1 on error. |
| 922 | |
959 | |
| 923 | aio_msync $scalar, $offset = 0, $length = undef, flags = 0, |
960 | aio_msync $scalar, $offset = 0, $length = undef, flags = MS_SYNC, |
| 924 | $callback->($status) |
961 | $callback->($status) |
| 925 | This is a rather advanced IO::AIO call, which only works on |
962 | This is a rather advanced IO::AIO call, which only works on |
| 926 | mmap(2)ed scalars (see the "IO::AIO::mmap" function, although it |
963 | mmap(2)ed scalars (see the "IO::AIO::mmap" function, although it |
| 927 | also works on data scalars managed by the Sys::Mmap or Mmap modules, |
964 | also works on data scalars managed by the Sys::Mmap or Mmap modules, |
| 928 | note that the scalar must only be modified in-place while an aio |
965 | note that the scalar must only be modified in-place while an aio |
| … | |
… | |
| 930 | |
967 | |
| 931 | It calls the "msync" function of your OS, if available, with the |
968 | It calls the "msync" function of your OS, if available, with the |
| 932 | memory area starting at $offset in the string and ending $length |
969 | memory area starting at $offset in the string and ending $length |
| 933 | bytes later. If $length is negative, counts from the end, and if |
970 | bytes later. If $length is negative, counts from the end, and if |
| 934 | $length is "undef", then it goes till the end of the string. The |
971 | $length is "undef", then it goes till the end of the string. The |
| 935 | flags can be a combination of "IO::AIO::MS_ASYNC", |
972 | flags can be either "IO::AIO::MS_ASYNC" or "IO::AIO::MS_SYNC", plus |
| 936 | "IO::AIO::MS_INVALIDATE" and "IO::AIO::MS_SYNC". |
973 | an optional "IO::AIO::MS_INVALIDATE". |
| 937 | |
974 | |
| 938 | aio_mtouch $scalar, $offset = 0, $length = undef, flags = 0, |
975 | aio_mtouch $scalar, $offset = 0, $length = undef, flags = 0, |
| 939 | $callback->($status) |
976 | $callback->($status) |
| 940 | This is a rather advanced IO::AIO call, which works best on |
977 | This is a rather advanced IO::AIO call, which works best on |
| 941 | mmap(2)ed scalars. |
978 | mmap(2)ed scalars. |
| 942 | |
979 | |
| 943 | It touches (reads or writes) all memory pages in the specified range |
980 | It touches (reads or writes) all memory pages in the specified range |
| 944 | inside the scalar. All caveats and parameters are the same as for |
981 | inside the scalar. All caveats and parameters are the same as for |
| 945 | "aio_msync", above, except for flags, which must be either 0 (which |
982 | "aio_msync", above, except for flags, which must be either 0 (which |
| 946 | reads all pages and ensures they are instantiated) or |
983 | reads all pages and ensures they are instantiated) or |
| 947 | "IO::AIO::MT_MODIFY", which modifies the memory page s(by reading |
984 | "IO::AIO::MT_MODIFY", which modifies the memory pages (by reading |
| 948 | and writing an octet from it, which dirties the page). |
985 | and writing an octet from it, which dirties the page). |
| 949 | |
986 | |
| 950 | aio_mlock $scalar, $offset = 0, $length = undef, $callback->($status) |
987 | aio_mlock $scalar, $offset = 0, $length = undef, $callback->($status) |
| 951 | This is a rather advanced IO::AIO call, which works best on |
988 | This is a rather advanced IO::AIO call, which works best on |
| 952 | mmap(2)ed scalars. |
989 | mmap(2)ed scalars. |
| … | |
… | |
| 1027 | "IO::AIO::FIEMAP_EXTENT_DATA_INLINE", |
1064 | "IO::AIO::FIEMAP_EXTENT_DATA_INLINE", |
| 1028 | "IO::AIO::FIEMAP_EXTENT_DATA_TAIL", |
1065 | "IO::AIO::FIEMAP_EXTENT_DATA_TAIL", |
| 1029 | "IO::AIO::FIEMAP_EXTENT_UNWRITTEN", "IO::AIO::FIEMAP_EXTENT_MERGED" |
1066 | "IO::AIO::FIEMAP_EXTENT_UNWRITTEN", "IO::AIO::FIEMAP_EXTENT_MERGED" |
| 1030 | or "IO::AIO::FIEMAP_EXTENT_SHARED". |
1067 | or "IO::AIO::FIEMAP_EXTENT_SHARED". |
| 1031 | |
1068 | |
| 1032 | At the time of this writing (Linux 3.2), this requets is unreliable |
1069 | At the time of this writing (Linux 3.2), this request is unreliable |
| 1033 | unless $count is "undef", as the kernel has all sorts of bugs |
1070 | unless $count is "undef", as the kernel has all sorts of bugs |
| 1034 | preventing it to return all extents of a range for files with large |
1071 | preventing it to return all extents of a range for files with a |
| 1035 | number of extents. The code works around all these issues if $count |
1072 | large number of extents. The code (only) works around all these |
| 1036 | is undef. |
1073 | issues if $count is "undef". |
| 1037 | |
1074 | |
| 1038 | aio_group $callback->(...) |
1075 | aio_group $callback->(...) |
| 1039 | This is a very special aio request: Instead of doing something, it |
1076 | This is a very special aio request: Instead of doing something, it |
| 1040 | is a container for other aio requests, which is useful if you want |
1077 | is a container for other aio requests, which is useful if you want |
| 1041 | to bundle many requests into a single, composite, request with a |
1078 | to bundle many requests into a single, composite, request with a |
| … | |
… | |
| 1121 | aio_stat [$etcdir, "passwd"], sub { |
1158 | aio_stat [$etcdir, "passwd"], sub { |
| 1122 | # yay |
1159 | # yay |
| 1123 | }; |
1160 | }; |
| 1124 | }; |
1161 | }; |
| 1125 | |
1162 | |
| 1126 | That "aio_wd" is a request and not a normal function shows that creating |
1163 | The fact that "aio_wd" is a request and not a normal function shows that |
| 1127 | an IO::AIO::WD object is itself a potentially blocking operation, which |
1164 | creating an IO::AIO::WD object is itself a potentially blocking |
| 1128 | is why it is done asynchronously. |
1165 | operation, which is why it is done asynchronously. |
| 1129 | |
1166 | |
| 1130 | To stat the directory obtained with "aio_wd" above, one could write |
1167 | To stat the directory obtained with "aio_wd" above, one could write |
| 1131 | either of the following three request calls: |
1168 | either of the following three request calls: |
| 1132 | |
1169 | |
| 1133 | aio_lstat "/etc" , sub { ... # pathname as normal string |
1170 | aio_lstat "/etc" , sub { ... # pathname as normal string |
| … | |
… | |
| 1150 | There are some caveats: when directories get renamed (or deleted), the |
1187 | There are some caveats: when directories get renamed (or deleted), the |
| 1151 | pathname string doesn't change, so will point to the new directory (or |
1188 | pathname string doesn't change, so will point to the new directory (or |
| 1152 | nowhere at all), while the directory fd, if available on the system, |
1189 | nowhere at all), while the directory fd, if available on the system, |
| 1153 | will still point to the original directory. Most functions accepting a |
1190 | will still point to the original directory. Most functions accepting a |
| 1154 | pathname will use the directory fd on newer systems, and the string on |
1191 | pathname will use the directory fd on newer systems, and the string on |
| 1155 | older systems. Some functions (such as realpath) will always rely on the |
1192 | older systems. Some functions (such as "aio_realpath") will always rely |
| 1156 | string form of the pathname. |
1193 | on the string form of the pathname. |
| 1157 | |
1194 | |
| 1158 | So this fucntionality is mainly useful to get some protection against |
1195 | So this functionality is mainly useful to get some protection against |
| 1159 | "chdir", to easily get an absolute path out of a relative path for |
1196 | "chdir", to easily get an absolute path out of a relative path for |
| 1160 | future reference, and to speed up doing many operations in the same |
1197 | future reference, and to speed up doing many operations in the same |
| 1161 | directory (e.g. when stat'ing all files in a directory). |
1198 | directory (e.g. when stat'ing all files in a directory). |
| 1162 | |
1199 | |
| 1163 | The following functions implement this working directory abstraction: |
1200 | The following functions implement this working directory abstraction: |
| … | |
… | |
| 1173 | Since passing "undef" as working directory component of a pathname |
1210 | Since passing "undef" as working directory component of a pathname |
| 1174 | fails the request with "ENOENT", there is often no need for error |
1211 | fails the request with "ENOENT", there is often no need for error |
| 1175 | checking in the "aio_wd" callback, as future requests using the |
1212 | checking in the "aio_wd" callback, as future requests using the |
| 1176 | value will fail in the expected way. |
1213 | value will fail in the expected way. |
| 1177 | |
1214 | |
| 1178 | If this call isn't available because your OS lacks it or it couldn't |
|
|
| 1179 | be detected, it will be emulated by calling "fsync" instead. |
|
|
| 1180 | |
|
|
| 1181 | IO::AIO::CWD |
1215 | IO::AIO::CWD |
| 1182 | This is a compiletime constant (object) that represents the process |
1216 | This is a compiletime constant (object) that represents the process |
| 1183 | current working directory. |
1217 | current working directory. |
| 1184 | |
1218 | |
| 1185 | Specifying this object as working directory object for a pathname is |
1219 | Specifying this object as working directory object for a pathname is |
| 1186 | as if the pathname would be specified directly, without a directory |
1220 | as if the pathname would be specified directly, without a directory |
| 1187 | object, e.g., these calls are functionally identical: |
1221 | object. For example, these calls are functionally identical: |
| 1188 | |
1222 | |
| 1189 | aio_stat "somefile", sub { ... }; |
1223 | aio_stat "somefile", sub { ... }; |
| 1190 | aio_stat [IO::AIO::CWD, "somefile"], sub { ... }; |
1224 | aio_stat [IO::AIO::CWD, "somefile"], sub { ... }; |
|
|
1225 | |
|
|
1226 | To recover the path associated with an IO::AIO::WD object, you can use |
|
|
1227 | "aio_realpath": |
|
|
1228 | |
|
|
1229 | aio_realpath $wd, sub { |
|
|
1230 | warn "path is $_[0]\n"; |
|
|
1231 | }; |
|
|
1232 | |
|
|
1233 | Currently, "aio_statvfs" always, and "aio_rename" and "aio_rmdir" |
|
|
1234 | sometimes, fall back to using an absolue path. |
| 1191 | |
1235 | |
| 1192 | IO::AIO::REQ CLASS |
1236 | IO::AIO::REQ CLASS |
| 1193 | All non-aggregate "aio_*" functions return an object of this class when |
1237 | All non-aggregate "aio_*" functions return an object of this class when |
| 1194 | called in non-void context. |
1238 | called in non-void context. |
| 1195 | |
1239 | |
| … | |
… | |
| 1347 | results. |
1391 | results. |
| 1348 | |
1392 | |
| 1349 | See "poll_cb" for an example. |
1393 | See "poll_cb" for an example. |
| 1350 | |
1394 | |
| 1351 | IO::AIO::poll_cb |
1395 | IO::AIO::poll_cb |
| 1352 | Process some outstanding events on the result pipe. You have to call |
1396 | Process some requests that have reached the result phase (i.e. they |
|
|
1397 | have been executed but the results are not yet reported). You have |
|
|
1398 | to call this "regularly" to finish outstanding requests. |
|
|
1399 | |
| 1353 | this regularly. Returns 0 if all events could be processed (or there |
1400 | Returns 0 if all events could be processed (or there were no events |
| 1354 | were no events to process), or -1 if it returned earlier for |
1401 | to process), or -1 if it returned earlier for whatever reason. |
| 1355 | whatever reason. Returns immediately when no events are outstanding. |
1402 | Returns immediately when no events are outstanding. The amount of |
| 1356 | The amount of events processed depends on the settings of |
1403 | events processed depends on the settings of "IO::AIO::max_poll_req", |
| 1357 | "IO::AIO::max_poll_req" and "IO::AIO::max_poll_time". |
1404 | "IO::AIO::max_poll_time" and "IO::AIO::max_outstanding". |
| 1358 | |
1405 | |
| 1359 | If not all requests were processed for whatever reason, the |
1406 | If not all requests were processed for whatever reason, the poll |
| 1360 | filehandle will still be ready when "poll_cb" returns, so normally |
1407 | file descriptor will still be ready when "poll_cb" returns, so |
| 1361 | you don't have to do anything special to have it called later. |
1408 | normally you don't have to do anything special to have it called |
|
|
1409 | later. |
| 1362 | |
1410 | |
| 1363 | Apart from calling "IO::AIO::poll_cb" when the event filehandle |
1411 | Apart from calling "IO::AIO::poll_cb" when the event filehandle |
| 1364 | becomes ready, it can be beneficial to call this function from loops |
1412 | becomes ready, it can be beneficial to call this function from loops |
| 1365 | which submit a lot of requests, to make sure the results get |
1413 | which submit a lot of requests, to make sure the results get |
| 1366 | processed when they become available and not just when the loop is |
1414 | processed when they become available and not just when the loop is |
| … | |
… | |
| 1374 | Event->io (fd => IO::AIO::poll_fileno, |
1422 | Event->io (fd => IO::AIO::poll_fileno, |
| 1375 | poll => 'r', async => 1, |
1423 | poll => 'r', async => 1, |
| 1376 | cb => \&IO::AIO::poll_cb); |
1424 | cb => \&IO::AIO::poll_cb); |
| 1377 | |
1425 | |
| 1378 | IO::AIO::poll_wait |
1426 | IO::AIO::poll_wait |
| 1379 | If there are any outstanding requests and none of them in the result |
1427 | Wait until either at least one request is in the result phase or no |
| 1380 | phase, wait till the result filehandle becomes ready for reading |
1428 | requests are outstanding anymore. |
| 1381 | (simply does a "select" on the filehandle. This is useful if you |
1429 | |
| 1382 | want to synchronously wait for some requests to finish). |
1430 | This is useful if you want to synchronously wait for some requests |
|
|
1431 | to become ready, without actually handling them. |
| 1383 | |
1432 | |
| 1384 | See "nreqs" for an example. |
1433 | See "nreqs" for an example. |
| 1385 | |
1434 | |
| 1386 | IO::AIO::poll |
1435 | IO::AIO::poll |
| 1387 | Waits until some requests have been handled. |
1436 | Waits until some requests have been handled. |
| … | |
… | |
| 1499 | |
1548 | |
| 1500 | This is a very bad function to use in interactive programs because |
1549 | This is a very bad function to use in interactive programs because |
| 1501 | it blocks, and a bad way to reduce concurrency because it is |
1550 | it blocks, and a bad way to reduce concurrency because it is |
| 1502 | inexact: Better use an "aio_group" together with a feed callback. |
1551 | inexact: Better use an "aio_group" together with a feed callback. |
| 1503 | |
1552 | |
| 1504 | It's main use is in scripts without an event loop - when you want to |
1553 | Its main use is in scripts without an event loop - when you want to |
| 1505 | stat a lot of files, you can write somehting like this: |
1554 | stat a lot of files, you can write something like this: |
| 1506 | |
1555 | |
| 1507 | IO::AIO::max_outstanding 32; |
1556 | IO::AIO::max_outstanding 32; |
| 1508 | |
1557 | |
| 1509 | for my $path (...) { |
1558 | for my $path (...) { |
| 1510 | aio_stat $path , ...; |
1559 | aio_stat $path , ...; |
| … | |
… | |
| 1540 | IO::AIO::npending |
1589 | IO::AIO::npending |
| 1541 | Returns the number of requests currently in the pending state |
1590 | Returns the number of requests currently in the pending state |
| 1542 | (executed, but not yet processed by poll_cb). |
1591 | (executed, but not yet processed by poll_cb). |
| 1543 | |
1592 | |
| 1544 | MISCELLANEOUS FUNCTIONS |
1593 | MISCELLANEOUS FUNCTIONS |
| 1545 | IO::AIO implements some functions that might be useful, but are not |
1594 | IO::AIO implements some functions that are useful when you want to use |
| 1546 | asynchronous. |
1595 | some "Advanced I/O" function not available to in Perl, without going the |
|
|
1596 | "Asynchronous I/O" route. Many of these have an asynchronous "aio_*" |
|
|
1597 | counterpart. |
|
|
1598 | |
|
|
1599 | $numfd = IO::AIO::get_fdlimit |
|
|
1600 | This function is *EXPERIMENTAL* and subject to change. |
|
|
1601 | |
|
|
1602 | Tries to find the current file descriptor limit and returns it, or |
|
|
1603 | "undef" and sets $! in case of an error. The limit is one larger |
|
|
1604 | than the highest valid file descriptor number. |
|
|
1605 | |
|
|
1606 | IO::AIO::min_fdlimit [$numfd] |
|
|
1607 | This function is *EXPERIMENTAL* and subject to change. |
|
|
1608 | |
|
|
1609 | Try to increase the current file descriptor limit(s) to at least |
|
|
1610 | $numfd by changing the soft or hard file descriptor resource limit. |
|
|
1611 | If $numfd is missing, it will try to set a very high limit, although |
|
|
1612 | this is not recommended when you know the actual minimum that you |
|
|
1613 | require. |
|
|
1614 | |
|
|
1615 | If the limit cannot be raised enough, the function makes a |
|
|
1616 | best-effort attempt to increase the limit as much as possible, using |
|
|
1617 | various tricks, while still failing. You can query the resulting |
|
|
1618 | limit using "IO::AIO::get_fdlimit". |
|
|
1619 | |
|
|
1620 | If an error occurs, returns "undef" and sets $!, otherwise returns |
|
|
1621 | true. |
| 1547 | |
1622 | |
| 1548 | IO::AIO::sendfile $ofh, $ifh, $offset, $count |
1623 | IO::AIO::sendfile $ofh, $ifh, $offset, $count |
| 1549 | Calls the "eio_sendfile_sync" function, which is like |
1624 | Calls the "eio_sendfile_sync" function, which is like |
| 1550 | "aio_sendfile", but is blocking (this makes most sense if you know |
1625 | "aio_sendfile", but is blocking (this makes most sense if you know |
| 1551 | the input data is likely cached already and the output filehandle is |
1626 | the input data is likely cached already and the output filehandle is |
| … | |
… | |
| 1568 | details). The following advice constants are available: |
1643 | details). The following advice constants are available: |
| 1569 | "IO::AIO::MADV_NORMAL", "IO::AIO::MADV_SEQUENTIAL", |
1644 | "IO::AIO::MADV_NORMAL", "IO::AIO::MADV_SEQUENTIAL", |
| 1570 | "IO::AIO::MADV_RANDOM", "IO::AIO::MADV_WILLNEED", |
1645 | "IO::AIO::MADV_RANDOM", "IO::AIO::MADV_WILLNEED", |
| 1571 | "IO::AIO::MADV_DONTNEED". |
1646 | "IO::AIO::MADV_DONTNEED". |
| 1572 | |
1647 | |
|
|
1648 | If $offset is negative, counts from the end. If $length is negative, |
|
|
1649 | the remaining length of the $scalar is used. If possible, $length |
|
|
1650 | will be reduced to fit into the $scalar. |
|
|
1651 | |
| 1573 | On systems that do not implement "posix_madvise", this function |
1652 | On systems that do not implement "posix_madvise", this function |
| 1574 | returns ENOSYS, otherwise the return value of "posix_madvise". |
1653 | returns ENOSYS, otherwise the return value of "posix_madvise". |
| 1575 | |
1654 | |
| 1576 | IO::AIO::mprotect $scalar, $offset, $len, $protect |
1655 | IO::AIO::mprotect $scalar, $offset, $len, $protect |
| 1577 | Simply calls the "mprotect" function on the preferably AIO::mmap'ed |
1656 | Simply calls the "mprotect" function on the preferably AIO::mmap'ed |
| 1578 | $scalar (see its manpage for details). The following protect |
1657 | $scalar (see its manpage for details). The following protect |
| 1579 | constants are available: "IO::AIO::PROT_NONE", "IO::AIO::PROT_READ", |
1658 | constants are available: "IO::AIO::PROT_NONE", "IO::AIO::PROT_READ", |
| 1580 | "IO::AIO::PROT_WRITE", "IO::AIO::PROT_EXEC". |
1659 | "IO::AIO::PROT_WRITE", "IO::AIO::PROT_EXEC". |
| 1581 | |
1660 | |
|
|
1661 | If $offset is negative, counts from the end. If $length is negative, |
|
|
1662 | the remaining length of the $scalar is used. If possible, $length |
|
|
1663 | will be reduced to fit into the $scalar. |
|
|
1664 | |
| 1582 | On systems that do not implement "mprotect", this function returns |
1665 | On systems that do not implement "mprotect", this function returns |
| 1583 | ENOSYS, otherwise the return value of "mprotect". |
1666 | ENOSYS, otherwise the return value of "mprotect". |
| 1584 | |
1667 | |
| 1585 | IO::AIO::mmap $scalar, $length, $prot, $flags, $fh[, $offset] |
1668 | IO::AIO::mmap $scalar, $length, $prot, $flags, $fh[, $offset] |
| 1586 | Memory-maps a file (or anonymous memory range) and attaches it to |
1669 | Memory-maps a file (or anonymous memory range) and attaches it to |
| 1587 | the given $scalar, which will act like a string scalar. Returns true |
1670 | the given $scalar, which will act like a string scalar. Returns true |
| 1588 | on success, and false otherwise. |
1671 | on success, and false otherwise. |
| 1589 | |
1672 | |
|
|
1673 | The scalar must exist, but its contents do not matter - this means |
|
|
1674 | you cannot use a nonexistant array or hash element. When in doubt, |
|
|
1675 | "undef" the scalar first. |
|
|
1676 | |
| 1590 | The only operations allowed on the scalar are "substr"/"vec" that |
1677 | The only operations allowed on the mmapped scalar are |
| 1591 | don't change the string length, and most read-only operations such |
1678 | "substr"/"vec", which don't change the string length, and most |
| 1592 | as copying it or searching it with regexes and so on. |
1679 | read-only operations such as copying it or searching it with regexes |
|
|
1680 | and so on. |
| 1593 | |
1681 | |
| 1594 | Anything else is unsafe and will, at best, result in memory leaks. |
1682 | Anything else is unsafe and will, at best, result in memory leaks. |
| 1595 | |
1683 | |
| 1596 | The memory map associated with the $scalar is automatically removed |
1684 | The memory map associated with the $scalar is automatically removed |
| 1597 | when the $scalar is destroyed, or when the "IO::AIO::mmap" or |
1685 | when the $scalar is undef'd or destroyed, or when the |
| 1598 | "IO::AIO::munmap" functions are called. |
1686 | "IO::AIO::mmap" or "IO::AIO::munmap" functions are called on it. |
| 1599 | |
1687 | |
| 1600 | This calls the "mmap"(2) function internally. See your system's |
1688 | This calls the "mmap"(2) function internally. See your system's |
| 1601 | manual page for details on the $length, $prot and $flags parameters. |
1689 | manual page for details on the $length, $prot and $flags parameters. |
| 1602 | |
1690 | |
| 1603 | The $length must be larger than zero and smaller than the actual |
1691 | The $length must be larger than zero and smaller than the actual |
| … | |
… | |
| 1607 | "IO::AIO::PROT_EXEC", "IO::AIO::PROT_READ" and/or |
1695 | "IO::AIO::PROT_EXEC", "IO::AIO::PROT_READ" and/or |
| 1608 | "IO::AIO::PROT_WRITE", |
1696 | "IO::AIO::PROT_WRITE", |
| 1609 | |
1697 | |
| 1610 | $flags can be a combination of "IO::AIO::MAP_SHARED" or |
1698 | $flags can be a combination of "IO::AIO::MAP_SHARED" or |
| 1611 | "IO::AIO::MAP_PRIVATE", or a number of system-specific flags (when |
1699 | "IO::AIO::MAP_PRIVATE", or a number of system-specific flags (when |
| 1612 | not available, the are defined as 0): "IO::AIO::MAP_ANONYMOUS" |
1700 | not available, the are 0): "IO::AIO::MAP_ANONYMOUS" (which is set to |
| 1613 | (which is set to "MAP_ANON" if your system only provides this |
1701 | "MAP_ANON" if your system only provides this constant), |
|
|
1702 | "IO::AIO::MAP_LOCKED", "IO::AIO::MAP_NORESERVE", |
| 1614 | constant), "IO::AIO::MAP_HUGETLB", "IO::AIO::MAP_LOCKED", |
1703 | "IO::AIO::MAP_POPULATE", "IO::AIO::MAP_NONBLOCK", |
|
|
1704 | "IO::AIO::MAP_FIXED", "IO::AIO::MAP_GROWSDOWN", |
| 1615 | "IO::AIO::MAP_NORESERVE", "IO::AIO::MAP_POPULATE" or |
1705 | "IO::AIO::MAP_32BIT", "IO::AIO::MAP_HUGETLB" or |
| 1616 | "IO::AIO::MAP_NONBLOCK" |
1706 | "IO::AIO::MAP_STACK". |
| 1617 | |
1707 | |
| 1618 | If $fh is "undef", then a file descriptor of -1 is passed. |
1708 | If $fh is "undef", then a file descriptor of -1 is passed. |
| 1619 | |
1709 | |
| 1620 | $offset is the offset from the start of the file - it generally must |
1710 | $offset is the offset from the start of the file - it generally must |
| 1621 | be a multiple of "IO::AIO::PAGESIZE" and defaults to 0. |
1711 | be a multiple of "IO::AIO::PAGESIZE" and defaults to 0. |
| … | |
… | |
| 1659 | "IO::AIO::SPLICE_F_MORE" and "IO::AIO::SPLICE_F_GIFT". |
1749 | "IO::AIO::SPLICE_F_MORE" and "IO::AIO::SPLICE_F_GIFT". |
| 1660 | |
1750 | |
| 1661 | See the splice(2) manpage for details. |
1751 | See the splice(2) manpage for details. |
| 1662 | |
1752 | |
| 1663 | IO::AIO::tee $r_fh, $w_fh, $length, $flags |
1753 | IO::AIO::tee $r_fh, $w_fh, $length, $flags |
| 1664 | Calls the GNU/Linux tee(2) syscall, see it's manpage and the |
1754 | Calls the GNU/Linux tee(2) syscall, see its manpage and the |
| 1665 | description for "IO::AIO::splice" above for details. |
1755 | description for "IO::AIO::splice" above for details. |
|
|
1756 | |
|
|
1757 | $actual_size = IO::AIO::pipesize $r_fh[, $new_size] |
|
|
1758 | Attempts to query or change the pipe buffer size. Obviously works |
|
|
1759 | only on pipes, and currently works only on GNU/Linux systems, and |
|
|
1760 | fails with -1/"ENOSYS" everywhere else. If anybody knows how to |
|
|
1761 | influence pipe buffer size on other systems, drop me a note. |
|
|
1762 | |
|
|
1763 | ($rfh, $wfh) = IO::AIO::pipe2 [$flags] |
|
|
1764 | This is a direct interface to the Linux pipe2(2) system call. If |
|
|
1765 | $flags is missing or 0, then this should be the same as a call to |
|
|
1766 | perl's built-in "pipe" function and create a new pipe, and works on |
|
|
1767 | systems that lack the pipe2 syscall. On win32, this case invokes |
|
|
1768 | "_pipe (..., 4096, O_BINARY)". |
|
|
1769 | |
|
|
1770 | If $flags is non-zero, it tries to invoke the pipe2 system call with |
|
|
1771 | the given flags (Linux 2.6.27, glibc 2.9). |
|
|
1772 | |
|
|
1773 | On success, the read and write file handles are returned. |
|
|
1774 | |
|
|
1775 | On error, nothing will be returned. If the pipe2 syscall is missing |
|
|
1776 | and $flags is non-zero, fails with "ENOSYS". |
|
|
1777 | |
|
|
1778 | Please refer to pipe2(2) for more info on the $flags, but at the |
|
|
1779 | time of this writing, "IO::AIO::O_CLOEXEC", "IO::AIO::O_NONBLOCK" |
|
|
1780 | and "IO::AIO::O_DIRECT" (Linux 3.4, for packet-based pipes) were |
|
|
1781 | supported. |
|
|
1782 | |
|
|
1783 | Example: create a pipe race-free w.r.t. threads and fork: |
|
|
1784 | |
|
|
1785 | my ($rfh, $wfh) = IO::AIO::pipe2 IO::AIO::O_CLOEXEC |
|
|
1786 | or die "pipe2: $!\n"; |
|
|
1787 | |
|
|
1788 | $fh = IO::AIO::eventfd [$initval, [$flags]] |
|
|
1789 | This is a direct interface to the Linux eventfd(2) system call. The |
|
|
1790 | (unhelpful) defaults for $initval and $flags are 0 for both. |
|
|
1791 | |
|
|
1792 | On success, the new eventfd filehandle is returned, otherwise |
|
|
1793 | returns "undef". If the eventfd syscall is missing, fails with |
|
|
1794 | "ENOSYS". |
|
|
1795 | |
|
|
1796 | Please refer to eventfd(2) for more info on this call. |
|
|
1797 | |
|
|
1798 | The following symbol flag values are available: |
|
|
1799 | "IO::AIO::EFD_CLOEXEC", "IO::AIO::EFD_NONBLOCK" and |
|
|
1800 | "IO::AIO::EFD_SEMAPHORE" (Linux 2.6.30). |
|
|
1801 | |
|
|
1802 | Example: create a new eventfd filehandle: |
|
|
1803 | |
|
|
1804 | $fh = IO::AIO::eventfd 0, IO::AIO::O_CLOEXEC |
|
|
1805 | or die "eventfd: $!\n"; |
|
|
1806 | |
|
|
1807 | $fh = IO::AIO::timerfd_create $clockid[, $flags] |
|
|
1808 | This is a direct interface to the Linux timerfd_create(2) system |
|
|
1809 | call. The (unhelpful) default for $flags is 0. |
|
|
1810 | |
|
|
1811 | On success, the new timerfd filehandle is returned, otherwise |
|
|
1812 | returns "undef". If the eventfd syscall is missing, fails with |
|
|
1813 | "ENOSYS". |
|
|
1814 | |
|
|
1815 | Please refer to timerfd_create(2) for more info on this call. |
|
|
1816 | |
|
|
1817 | The following $clockid values are available: |
|
|
1818 | "IO::AIO::CLOCK_REALTIME", "IO::AIO::CLOCK_MONOTONIC" |
|
|
1819 | "IO::AIO::CLOCK_CLOCK_BOOTTIME" (Linux 3.15) |
|
|
1820 | "IO::AIO::CLOCK_CLOCK_REALTIME_ALARM" (Linux 3.11) and |
|
|
1821 | "IO::AIO::CLOCK_CLOCK_BOOTTIME_ALARM" (Linux 3.11). |
|
|
1822 | |
|
|
1823 | The following $flags values are available (Linux 2.6.27): |
|
|
1824 | "IO::AIO::TFD_NONBLOCK" and "IO::AIO::TFD_CLOEXEC". |
|
|
1825 | |
|
|
1826 | Example: create a new timerfd and set it to one-second repeated |
|
|
1827 | alarms, then wait for two alarms: |
|
|
1828 | |
|
|
1829 | my $fh = IO::AIO::timerfd_create IO::AIO::CLOCK_BOOTTIME, IO::AIO::TFD_CLOEXEC |
|
|
1830 | or die "timerfd_create: $!\n"; |
|
|
1831 | |
|
|
1832 | defined IO::AIO::timerfd_settime $fh, 0, 1, 1 |
|
|
1833 | or die "timerfd_settime: $!\n"; |
|
|
1834 | |
|
|
1835 | for (1..2) { |
|
|
1836 | 8 == sysread $fh, my $buf, 8 |
|
|
1837 | or die "timerfd read failure\n"; |
|
|
1838 | |
|
|
1839 | printf "number of expirations (likely 1): %d\n", |
|
|
1840 | unpack "Q", $buf; |
|
|
1841 | } |
|
|
1842 | |
|
|
1843 | ($cur_interval, $cur_value) = IO::AIO::timerfd_settime $fh, $flags, |
|
|
1844 | $new_interval, $nbw_value |
|
|
1845 | This is a direct interface to the Linux timerfd_settime(2) system |
|
|
1846 | call. Please refer to its manpage for more info on this call. |
|
|
1847 | |
|
|
1848 | The new itimerspec is specified using two (possibly fractional) |
|
|
1849 | second values, $new_interval and $new_value). |
|
|
1850 | |
|
|
1851 | On success, the current interval and value are returned (as per |
|
|
1852 | "timerfd_gettime"). On failure, the empty list is returned. |
|
|
1853 | |
|
|
1854 | The following $flags values are available: |
|
|
1855 | "IO::AIO::TFD_TIMER_ABSTIME" and "IO::AIO::TFD_TIMER_CANCEL_ON_SET". |
|
|
1856 | |
|
|
1857 | See "IO::AIO::timerfd_create" for a full example. |
|
|
1858 | |
|
|
1859 | ($cur_interval, $cur_value) = IO::AIO::timerfd_gettime $fh |
|
|
1860 | This is a direct interface to the Linux timerfd_gettime(2) system |
|
|
1861 | call. Please refer to its manpage for more info on this call. |
|
|
1862 | |
|
|
1863 | On success, returns the current values of interval and value for the |
|
|
1864 | given timerfd (as potentially fractional second values). On failure, |
|
|
1865 | the empty list is returned. |
| 1666 | |
1866 | |
| 1667 | EVENT LOOP INTEGRATION |
1867 | EVENT LOOP INTEGRATION |
| 1668 | It is recommended to use AnyEvent::AIO to integrate IO::AIO |
1868 | It is recommended to use AnyEvent::AIO to integrate IO::AIO |
| 1669 | automatically into many event loops: |
1869 | automatically into many event loops: |
| 1670 | |
1870 | |
| … | |
… | |
| 1720 | forking, if "IO::AIO" was used in the parent. Calling it while |
1920 | forking, if "IO::AIO" was used in the parent. Calling it while |
| 1721 | IO::AIO is active in the process will result in undefined behaviour. |
1921 | IO::AIO is active in the process will result in undefined behaviour. |
| 1722 | Calling it at any time will also result in any undefined (by POSIX) |
1922 | Calling it at any time will also result in any undefined (by POSIX) |
| 1723 | behaviour. |
1923 | behaviour. |
| 1724 | |
1924 | |
|
|
1925 | LINUX-SPECIFIC CALLS |
|
|
1926 | When a call is documented as "linux-specific" then this means it |
|
|
1927 | originated on GNU/Linux. "IO::AIO" will usually try to autodetect the |
|
|
1928 | availability and compatibility of such calls regardless of the platform |
|
|
1929 | it is compiled on, so platforms such as FreeBSD which often implement |
|
|
1930 | these calls will work. When in doubt, call them and see if they fail wth |
|
|
1931 | "ENOSYS". |
|
|
1932 | |
| 1725 | MEMORY USAGE |
1933 | MEMORY USAGE |
| 1726 | Per-request usage: |
1934 | Per-request usage: |
| 1727 | |
1935 | |
| 1728 | Each aio request uses - depending on your architecture - around 100-200 |
1936 | Each aio request uses - depending on your architecture - around 100-200 |
| 1729 | bytes of memory. In addition, stat requests need a stat buffer (possibly |
1937 | bytes of memory. In addition, stat requests need a stat buffer (possibly |
| … | |
… | |
| 1739 | In the execution phase, some aio requests require more memory for |
1947 | In the execution phase, some aio requests require more memory for |
| 1740 | temporary buffers, and each thread requires a stack and other data |
1948 | temporary buffers, and each thread requires a stack and other data |
| 1741 | structures (usually around 16k-128k, depending on the OS). |
1949 | structures (usually around 16k-128k, depending on the OS). |
| 1742 | |
1950 | |
| 1743 | KNOWN BUGS |
1951 | KNOWN BUGS |
| 1744 | Known bugs will be fixed in the next release. |
1952 | Known bugs will be fixed in the next release :) |
|
|
1953 | |
|
|
1954 | KNOWN ISSUES |
|
|
1955 | Calls that try to "import" foreign memory areas (such as "IO::AIO::mmap" |
|
|
1956 | or "IO::AIO::aio_slurp") do not work with generic lvalues, such as |
|
|
1957 | non-created hash slots or other scalars I didn't think of. It's best to |
|
|
1958 | avoid such and either use scalar variables or making sure that the |
|
|
1959 | scalar exists (e.g. by storing "undef") and isn't "funny" (e.g. tied). |
|
|
1960 | |
|
|
1961 | I am not sure anything can be done about this, so this is considered a |
|
|
1962 | known issue, rather than a bug. |
| 1745 | |
1963 | |
| 1746 | SEE ALSO |
1964 | SEE ALSO |
| 1747 | AnyEvent::AIO for easy integration into event loops, Coro::AIO for a |
1965 | AnyEvent::AIO for easy integration into event loops, Coro::AIO for a |
| 1748 | more natural syntax. |
1966 | more natural syntax. |
| 1749 | |
1967 | |
