ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/IO-AIO/AIO.pm
(Generate patch)

Comparing IO-AIO/AIO.pm (file contents):
Revision 1.258 by root, Thu Jan 21 23:04:46 2016 UTC vs.
Revision 1.259 by root, Tue Feb 23 19:42:43 2016 UTC

171BEGIN { 171BEGIN {
172 our $VERSION = 4.33; 172 our $VERSION = 4.33;
173 173
174 our @AIO_REQ = qw(aio_sendfile aio_seek aio_read aio_write aio_open aio_close 174 our @AIO_REQ = qw(aio_sendfile aio_seek aio_read aio_write aio_open aio_close
175 aio_stat aio_lstat aio_unlink aio_rmdir aio_readdir aio_readdirx 175 aio_stat aio_lstat aio_unlink aio_rmdir aio_readdir aio_readdirx
176 aio_scandir aio_symlink aio_readlink aio_realpath aio_sync 176 aio_scandir aio_symlink aio_readlink aio_realpath aio_fcntl aio_ioctl
177 aio_fsync aio_syncfs aio_fdatasync aio_sync_file_range aio_allocate 177 aio_sync aio_fsync aio_syncfs aio_fdatasync aio_sync_file_range
178 aio_pathsync aio_readahead aio_fiemap 178 aio_pathsync aio_readahead aio_fiemap aio_allocate
179 aio_rename aio_link aio_move aio_copy aio_group 179 aio_rename aio_link aio_move aio_copy aio_group
180 aio_nop aio_mknod aio_load aio_rmtree aio_mkdir aio_chown 180 aio_nop aio_mknod aio_load aio_rmtree aio_mkdir aio_chown
181 aio_chmod aio_utime aio_truncate 181 aio_chmod aio_utime aio_truncate
182 aio_msync aio_mtouch aio_mlock aio_mlockall 182 aio_msync aio_mtouch aio_mlock aio_mlockall
183 aio_statvfs 183 aio_statvfs
240 aio_scandir $pathname, $maxreq, $callback->($dirs, $nondirs) 240 aio_scandir $pathname, $maxreq, $callback->($dirs, $nondirs)
241 aio_load $pathname, $data, $callback->($status) 241 aio_load $pathname, $data, $callback->($status)
242 aio_copy $srcpath, $dstpath, $callback->($status) 242 aio_copy $srcpath, $dstpath, $callback->($status)
243 aio_move $srcpath, $dstpath, $callback->($status) 243 aio_move $srcpath, $dstpath, $callback->($status)
244 aio_rmtree $pathname, $callback->($status) 244 aio_rmtree $pathname, $callback->($status)
245 aio_fcntl $fh, $cmd, $arg, $callback->($status)
246 aio_ioctl $fh, $request, $buf, $callback->($status)
245 aio_sync $callback->($status) 247 aio_sync $callback->($status)
246 aio_syncfs $fh, $callback->($status) 248 aio_syncfs $fh, $callback->($status)
247 aio_fsync $fh, $callback->($status) 249 aio_fsync $fh, $callback->($status)
248 aio_fdatasync $fh, $callback->($status) 250 aio_fdatasync $fh, $callback->($status)
249 aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status) 251 aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status)
1227 }; 1229 };
1228 1230
1229 $grp 1231 $grp
1230} 1232}
1231 1233
1234=item aio_fcntl $fh, $cmd, $arg, $callback->($status)
1235
1236=item aio_ioctl $fh, $request, $buf, $callback->($status)
1237
1238These work just like the C<fcntl> and C<ioctl> built-in functions, except
1239they execute asynchronously and pass the return value to the callback.
1240
1241Both calls can be used for a lot of things, some of which make more sense
1242to run asynchronously in their own thread, while some others make less
1243sense. For example, calls that block waiting for external events, such
1244as locking, will also lock down an I/O thread while it is waiting, which
1245can deadlock the whole I/O system. At the same time, there might be no
1246alternative to using a thread to wait.
1247
1248So 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,
1250other processes), although if you are careful and know what you are doing,
1251you still can.
1252
1232=item aio_sync $callback->($status) 1253=item aio_sync $callback->($status)
1233 1254
1234Asynchronously call sync and call the callback when finished. 1255Asynchronously call sync and call the callback when finished.
1235 1256
1236=item aio_fsync $fh, $callback->($status) 1257=item aio_fsync $fh, $callback->($status)

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines