… | |
… | |
193 | use strict 'vars'; |
193 | use strict 'vars'; |
194 | |
194 | |
195 | use base 'Exporter'; |
195 | use base 'Exporter'; |
196 | |
196 | |
197 | BEGIN { |
197 | BEGIN { |
198 | our $VERSION = '3.1'; |
198 | our $VERSION = '3.16'; |
199 | |
199 | |
200 | our @AIO_REQ = qw(aio_sendfile aio_read aio_write aio_open aio_close |
200 | our @AIO_REQ = qw(aio_sendfile aio_read aio_write aio_open aio_close |
201 | aio_stat aio_lstat aio_unlink aio_rmdir aio_readdir |
201 | aio_stat aio_lstat aio_unlink aio_rmdir aio_readdir |
202 | aio_scandir aio_symlink aio_readlink aio_sync aio_fsync |
202 | aio_scandir aio_symlink aio_readlink aio_sync aio_fsync |
203 | aio_fdatasync aio_pathsync aio_readahead |
203 | aio_fdatasync aio_sync_file_range aio_pathsync aio_readahead |
204 | aio_rename aio_link aio_move aio_copy aio_group |
204 | aio_rename aio_link aio_move aio_copy aio_group |
205 | aio_nop aio_mknod aio_load aio_rmtree aio_mkdir aio_chown |
205 | aio_nop aio_mknod aio_load aio_rmtree aio_mkdir aio_chown |
206 | aio_chmod aio_utime aio_truncate); |
206 | aio_chmod aio_utime aio_truncate); |
207 | |
207 | |
208 | our @EXPORT = (@AIO_REQ, qw(aioreq_pri aioreq_nice)); |
208 | our @EXPORT = (@AIO_REQ, qw(aioreq_pri aioreq_nice)); |
… | |
… | |
855 | callback with the fdatasync result code. |
855 | callback with the fdatasync result code. |
856 | |
856 | |
857 | If this call isn't available because your OS lacks it or it couldn't be |
857 | If this call isn't available because your OS lacks it or it couldn't be |
858 | detected, it will be emulated by calling C<fsync> instead. |
858 | detected, it will be emulated by calling C<fsync> instead. |
859 | |
859 | |
|
|
860 | =item aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status) |
|
|
861 | |
|
|
862 | Sync the data portion of the file specified by C<$offset> and C<$length> |
|
|
863 | to disk (but NOT the metadata), by calling the Linux-specific |
|
|
864 | sync_file_range call. If sync_file_range is not available or it returns |
|
|
865 | ENOSYS, then fdatasync or fsync is being substituted. |
|
|
866 | |
|
|
867 | C<$flags> can be a combination of C<IO::AIO::SYNC_FILE_RANGE_WAIT_BEFORE>, |
|
|
868 | C<IO::AIO::SYNC_FILE_RANGE_WRITE> and |
|
|
869 | C<IO::AIO::SYNC_FILE_RANGE_WAIT_AFTER>: refer to the sync_file_range |
|
|
870 | manpage for details. |
|
|
871 | |
860 | =item aio_pathsync $path, $callback->($status) |
872 | =item aio_pathsync $path, $callback->($status) |
861 | |
873 | |
862 | This request tries to open, fsync and close the given path. This is a |
874 | This request tries to open, fsync and close the given path. This is a |
863 | composite request intended to sync directories after directory operations |
875 | composite request intended to sync directories after directory operations |
864 | (E.g. rename). This might not work on all operating systems or have any |
876 | (E.g. rename). This might not work on all operating systems or have any |
… | |
… | |
1060 | =item feed $grp $callback->($grp) |
1072 | =item feed $grp $callback->($grp) |
1061 | |
1073 | |
1062 | Sets a feeder/generator on this group: every group can have an attached |
1074 | Sets a feeder/generator on this group: every group can have an attached |
1063 | generator that generates requests if idle. The idea behind this is that, |
1075 | generator that generates requests if idle. The idea behind this is that, |
1064 | although you could just queue as many requests as you want in a group, |
1076 | although you could just queue as many requests as you want in a group, |
1065 | this might starve other requests for a potentially long time. For |
1077 | this might starve other requests for a potentially long time. For example, |
1066 | example, C<aio_scandir> might generate hundreds of thousands C<aio_stat> |
1078 | C<aio_scandir> might generate hundreds of thousands C<aio_stat> requests, |
1067 | requests, delaying any later requests for a long time. |
1079 | delaying any later requests for a long time. |
1068 | |
1080 | |
1069 | To avoid this, and allow incremental generation of requests, you can |
1081 | To avoid this, and allow incremental generation of requests, you can |
1070 | instead a group and set a feeder on it that generates those requests. The |
1082 | instead a group and set a feeder on it that generates those requests. The |
1071 | feed callback will be called whenever there are few enough (see C<limit>, |
1083 | feed callback will be called whenever there are few enough (see C<limit>, |
1072 | below) requests active in the group itself and is expected to queue more |
1084 | below) requests active in the group itself and is expected to queue more |