| … | |
… | |
| 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.06'; |
198 | our $VERSION = '3.07'; |
| 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_pathsync aio_readahead |
| … | |
… | |
| 565 | |
565 | |
| 566 | Try to copy the I<file> (directories not supported as either source or |
566 | Try to copy the I<file> (directories not supported as either source or |
| 567 | destination) from C<$srcpath> to C<$dstpath> and call the callback with |
567 | destination) from C<$srcpath> to C<$dstpath> and call the callback with |
| 568 | the C<0> (error) or C<-1> ok. |
568 | the C<0> (error) or C<-1> ok. |
| 569 | |
569 | |
| 570 | This is a composite request that it creates the destination file with |
570 | This is a composite request that creates the destination file with |
| 571 | mode 0200 and copies the contents of the source file into it using |
571 | mode 0200 and copies the contents of the source file into it using |
| 572 | C<aio_sendfile>, followed by restoring atime, mtime, access mode and |
572 | C<aio_sendfile>, followed by restoring atime, mtime, access mode and |
| 573 | uid/gid, in that order. |
573 | uid/gid, in that order. |
| 574 | |
574 | |
| 575 | If an error occurs, the partial destination file will be unlinked, if |
575 | If an error occurs, the partial destination file will be unlinked, if |
| … | |
… | |
| 1013 | Their lifetime, simplified, looks like this: when they are empty, they |
1013 | Their lifetime, simplified, looks like this: when they are empty, they |
| 1014 | will finish very quickly. If they contain only requests that are in the |
1014 | will finish very quickly. If they contain only requests that are in the |
| 1015 | C<done> state, they will also finish. Otherwise they will continue to |
1015 | C<done> state, they will also finish. Otherwise they will continue to |
| 1016 | exist. |
1016 | exist. |
| 1017 | |
1017 | |
| 1018 | That means after creating a group you have some time to add requests. And |
1018 | That means after creating a group you have some time to add requests |
| 1019 | in the callbacks of those requests, you can add further requests to the |
1019 | (precisely before the callback has been invoked, which is only done within |
| 1020 | group. And only when all those requests have finished will the the group |
1020 | the C<poll_cb>). And in the callbacks of those requests, you can add |
| 1021 | itself finish. |
1021 | further requests to the group. And only when all those requests have |
|
|
1022 | finished will the the group itself finish. |
| 1022 | |
1023 | |
| 1023 | =over 4 |
1024 | =over 4 |
| 1024 | |
1025 | |
| 1025 | =item add $grp ... |
1026 | =item add $grp ... |
| 1026 | |
1027 | |
