1 | =head1 NAME |
1 | =head1 NAME |
2 | |
2 | |
3 | IO::AIO - Asynchronous Input/Output |
3 | IO::AIO - Asynchronous/Advanced Input/Output |
4 | |
4 | |
5 | =head1 SYNOPSIS |
5 | =head1 SYNOPSIS |
6 | |
6 | |
7 | use IO::AIO; |
7 | use IO::AIO; |
8 | |
8 | |
… | |
… | |
57 | functions available on many operating systems. However, they are often |
57 | functions available on many operating systems. However, they are often |
58 | not well-supported or restricted (GNU/Linux doesn't allow them on normal |
58 | not well-supported or restricted (GNU/Linux doesn't allow them on normal |
59 | files currently, for example), and they would only support aio_read and |
59 | files currently, for example), and they would only support aio_read and |
60 | aio_write, so the remaining functionality would have to be implemented |
60 | aio_write, so the remaining functionality would have to be implemented |
61 | using threads anyway. |
61 | using threads anyway. |
|
|
62 | |
|
|
63 | In addition to asynchronous I/O, this module also exports some rather |
|
|
64 | arcane interfaces, such as C<madvise> or linux's C<splice> system call, |
|
|
65 | which is why the C<A> in C<AIO> can also mean I<advanced>. |
62 | |
66 | |
63 | Although the module will work in the presence of other (Perl-) threads, |
67 | Although the module will work in the presence of other (Perl-) threads, |
64 | it is currently not reentrant in any way, so use appropriate locking |
68 | it is currently not reentrant in any way, so use appropriate locking |
65 | yourself, always call C<poll_cb> from within the same thread, or never |
69 | yourself, always call C<poll_cb> from within the same thread, or never |
66 | call C<poll_cb> (or other C<aio_> functions) recursively. |
70 | call C<poll_cb> (or other C<aio_> functions) recursively. |
… | |
… | |
441 | =item aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
445 | =item aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
442 | |
446 | |
443 | =item aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
447 | =item aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
444 | |
448 | |
445 | Reads or writes C<$length> bytes from or to the specified C<$fh> and |
449 | Reads or writes C<$length> bytes from or to the specified C<$fh> and |
446 | C<$offset> into the scalar given by C<$data> and offset C<$dataoffset> |
450 | C<$offset> into the scalar given by C<$data> and offset C<$dataoffset> and |
447 | and calls the callback without the actual number of bytes read (or -1 on |
451 | calls the callback with the actual number of bytes transferred (or -1 on |
448 | error, just like the syscall). |
452 | error, just like the syscall). |
449 | |
453 | |
450 | C<aio_read> will, like C<sysread>, shrink or grow the C<$data> scalar to |
454 | C<aio_read> will, like C<sysread>, shrink or grow the C<$data> scalar to |
451 | offset plus the actual number of bytes read. |
455 | offset plus the actual number of bytes read. |
452 | |
456 | |
… | |
… | |
510 | As native sendfile syscalls (as practically any non-POSIX interface hacked |
514 | As native sendfile syscalls (as practically any non-POSIX interface hacked |
511 | together in a hurry to improve benchmark numbers) tend to be rather buggy |
515 | together in a hurry to improve benchmark numbers) tend to be rather buggy |
512 | on many systems, this implementation tries to work around some known bugs |
516 | on many systems, this implementation tries to work around some known bugs |
513 | in Linux and FreeBSD kernels (probably others, too), but that might fail, |
517 | in Linux and FreeBSD kernels (probably others, too), but that might fail, |
514 | so you really really should check the return value of C<aio_sendfile> - |
518 | so you really really should check the return value of C<aio_sendfile> - |
515 | fewre bytes than expected might have been transferred. |
519 | fewer bytes than expected might have been transferred. |
516 | |
520 | |
517 | |
521 | |
518 | =item aio_readahead $fh,$offset,$length, $callback->($retval) |
522 | =item aio_readahead $fh,$offset,$length, $callback->($retval) |
519 | |
523 | |
520 | C<aio_readahead> populates the page cache with data from a file so that |
524 | C<aio_readahead> populates the page cache with data from a file so that |
… | |
… | |
524 | whole pages, so that offset is effectively rounded down to a page boundary |
528 | whole pages, so that offset is effectively rounded down to a page boundary |
525 | and bytes are read up to the next page boundary greater than or equal to |
529 | and bytes are read up to the next page boundary greater than or equal to |
526 | (off-set+length). C<aio_readahead> does not read beyond the end of the |
530 | (off-set+length). C<aio_readahead> does not read beyond the end of the |
527 | file. The current file offset of the file is left unchanged. |
531 | file. The current file offset of the file is left unchanged. |
528 | |
532 | |
529 | If that syscall doesn't exist (likely if your OS isn't Linux) it will be |
533 | If that syscall doesn't exist (likely if your kernel isn't Linux) it will |
530 | emulated by simply reading the data, which would have a similar effect. |
534 | be emulated by simply reading the data, which would have a similar effect. |
531 | |
535 | |
532 | |
536 | |
533 | =item aio_stat $fh_or_path, $callback->($status) |
537 | =item aio_stat $fh_or_path, $callback->($status) |
534 | |
538 | |
535 | =item aio_lstat $fh, $callback->($status) |
539 | =item aio_lstat $fh, $callback->($status) |
… | |
… | |
1248 | So in general, you should only use these calls for things that do |
1252 | So in general, you should only use these calls for things that do |
1249 | (filesystem) I/O, not for things that wait for other events (network, |
1253 | (filesystem) I/O, not for things that wait for other events (network, |
1250 | other processes), although if you are careful and know what you are doing, |
1254 | other processes), although if you are careful and know what you are doing, |
1251 | you still can. |
1255 | you still can. |
1252 | |
1256 | |
|
|
1257 | The following constants are available (missing ones are, as usual C<0>): |
|
|
1258 | |
|
|
1259 | C<FIFREEZE>, C<FITHAW>, C<FITRIM>, C<FICLONE>, C<FICLONERANGE>, C<FIDEDUPERANGE>. |
|
|
1260 | |
|
|
1261 | C<FS_IOC_GETFLAGS>, C<FS_IOC_SETFLAGS>, C<FS_IOC_GETVERSION>, C<FS_IOC_SETVERSION>, |
|
|
1262 | C<FS_IOC_FIEMAP>. |
|
|
1263 | |
|
|
1264 | C<FS_IOC_FSGETXATTR>, C<FS_IOC_FSSETXATTR>, C<FS_IOC_SET_ENCRYPTION_POLICY>, |
|
|
1265 | C<FS_IOC_GET_ENCRYPTION_PWSALT>, C<FS_IOC_GET_ENCRYPTION_POLICY>, C<FS_KEY_DESCRIPTOR_SIZE>. |
|
|
1266 | |
|
|
1267 | C<FS_SECRM_FL>, C<FS_UNRM_FL>, C<FS_COMPR_FL>, C<FS_SYNC_FL>, C<FS_IMMUTABLE_FL>, |
|
|
1268 | C<FS_APPEND_FL>, C<FS_NODUMP_FL>, C<FS_NOATIME_FL>, C<FS_DIRTY_FL>, |
|
|
1269 | C<FS_COMPRBLK_FL>, C<FS_NOCOMP_FL>, C<FS_ENCRYPT_FL>, C<FS_BTREE_FL>, |
|
|
1270 | C<FS_INDEX_FL>, C<FS_JOURNAL_DATA_FL>, C<FS_NOTAIL_FL>, C<FS_DIRSYNC_FL>, C<FS_TOPDIR_FL>, |
|
|
1271 | C<FS_FL_USER_MODIFIABLE>. |
|
|
1272 | |
|
|
1273 | C<FS_XFLAG_REALTIME>, C<FS_XFLAG_PREALLOC>, C<FS_XFLAG_IMMUTABLE>, C<FS_XFLAG_APPEND>, |
|
|
1274 | C<FS_XFLAG_SYNC>, C<FS_XFLAG_NOATIME>, C<FS_XFLAG_NODUMP>, C<FS_XFLAG_RTINHERIT>, |
|
|
1275 | C<FS_XFLAG_PROJINHERIT>, C<FS_XFLAG_NOSYMLINKS>, C<FS_XFLAG_EXTSIZE>, C<FS_XFLAG_EXTSZINHERIT>, |
|
|
1276 | C<FS_XFLAG_NODEFRAG>, C<FS_XFLAG_FILESTREAM>, C<FS_XFLAG_DAX>, C<FS_XFLAG_HASATTR>, |
|
|
1277 | |
1253 | =item aio_sync $callback->($status) |
1278 | =item aio_sync $callback->($status) |
1254 | |
1279 | |
1255 | Asynchronously call sync and call the callback when finished. |
1280 | Asynchronously call sync and call the callback when finished. |
1256 | |
1281 | |
1257 | =item aio_fsync $fh, $callback->($status) |
1282 | =item aio_fsync $fh, $callback->($status) |
… | |
… | |
2041 | =item IO::AIO::madvise $scalar, $offset, $len, $advice |
2066 | =item IO::AIO::madvise $scalar, $offset, $len, $advice |
2042 | |
2067 | |
2043 | Simply calls the C<posix_madvise> function (see its |
2068 | Simply calls the C<posix_madvise> function (see its |
2044 | manpage for details). The following advice constants are |
2069 | manpage for details). The following advice constants are |
2045 | available: C<IO::AIO::MADV_NORMAL>, C<IO::AIO::MADV_SEQUENTIAL>, |
2070 | available: C<IO::AIO::MADV_NORMAL>, C<IO::AIO::MADV_SEQUENTIAL>, |
2046 | C<IO::AIO::MADV_RANDOM>, C<IO::AIO::MADV_WILLNEED>, C<IO::AIO::MADV_DONTNEED>. |
2071 | C<IO::AIO::MADV_RANDOM>, C<IO::AIO::MADV_WILLNEED>, C<IO::AIO::MADV_DONTNEED>, |
|
|
2072 | C<IO::AIO::MADV_FREE>. |
2047 | |
2073 | |
2048 | On systems that do not implement C<posix_madvise>, this function returns |
2074 | On systems that do not implement C<posix_madvise>, this function returns |
2049 | ENOSYS, otherwise the return value of C<posix_madvise>. |
2075 | ENOSYS, otherwise the return value of C<posix_madvise>. |
2050 | |
2076 | |
2051 | =item IO::AIO::mprotect $scalar, $offset, $len, $protect |
2077 | =item IO::AIO::mprotect $scalar, $offset, $len, $protect |