… | |
… | |
3 | |
3 | |
4 | SYNOPSIS |
4 | SYNOPSIS |
5 | use IO::AIO; |
5 | use IO::AIO; |
6 | |
6 | |
7 | aio_open "/etc/passwd", O_RDONLY, 0, sub { |
7 | aio_open "/etc/passwd", O_RDONLY, 0, sub { |
8 | my ($fh) = @_; |
8 | my $fh = shift |
|
|
9 | or die "/etc/passwd: $!"; |
9 | ... |
10 | ... |
10 | }; |
11 | }; |
11 | |
12 | |
12 | aio_unlink "/tmp/file", sub { }; |
13 | aio_unlink "/tmp/file", sub { }; |
13 | |
14 | |
… | |
… | |
60 | faster on a RAID volume or over NFS when you do a number of stat |
61 | faster on a RAID volume or over NFS when you do a number of stat |
61 | operations concurrently. |
62 | operations concurrently. |
62 | |
63 | |
63 | While most of this works on all types of file descriptors (for example |
64 | While most of this works on all types of file descriptors (for example |
64 | sockets), using these functions on file descriptors that support |
65 | sockets), using these functions on file descriptors that support |
65 | nonblocking operation (again, sockets, pipes etc.) is very inefficient |
66 | nonblocking operation (again, sockets, pipes etc.) is very inefficient. |
66 | or might not work (aio_read fails on sockets/pipes/fifos). Use an event |
|
|
67 | loop for that (such as the Event module): IO::AIO will naturally fit |
67 | Use an event loop for that (such as the Event module): IO::AIO will |
68 | into such an event loop itself. |
68 | naturally fit into such an event loop itself. |
69 | |
69 | |
70 | In this version, a number of threads are started that execute your |
70 | In this version, a number of threads are started that execute your |
71 | requests and signal their completion. You don't need thread support in |
71 | requests and signal their completion. You don't need thread support in |
72 | perl, and the threads created by this module will not be visible to |
72 | perl, and the threads created by this module will not be visible to |
73 | perl. In the future, this module might make use of the native aio |
73 | perl. In the future, this module might make use of the native aio |
… | |
… | |
75 | not well-supported or restricted (GNU/Linux doesn't allow them on normal |
75 | not well-supported or restricted (GNU/Linux doesn't allow them on normal |
76 | files currently, for example), and they would only support aio_read and |
76 | files currently, for example), and they would only support aio_read and |
77 | aio_write, so the remaining functionality would have to be implemented |
77 | aio_write, so the remaining functionality would have to be implemented |
78 | using threads anyway. |
78 | using threads anyway. |
79 | |
79 | |
80 | Although the module will work with in the presence of other (Perl-) |
80 | Although the module will work in the presence of other (Perl-) threads, |
81 | threads, it is currently not reentrant in any way, so use appropriate |
81 | it is currently not reentrant in any way, so use appropriate locking |
82 | locking yourself, always call "poll_cb" from within the same thread, or |
82 | yourself, always call "poll_cb" from within the same thread, or never |
83 | never call "poll_cb" (or other "aio_" functions) recursively. |
83 | call "poll_cb" (or other "aio_" functions) recursively. |
84 | |
84 | |
85 | EXAMPLE |
85 | EXAMPLE |
86 | This is a simple example that uses the Event module and loads |
86 | This is a simple example that uses the Event module and loads |
87 | /etc/passwd asynchronously: |
87 | /etc/passwd asynchronously: |
88 | |
88 | |
… | |
… | |
95 | poll => 'r', |
95 | poll => 'r', |
96 | cb => \&IO::AIO::poll_cb); |
96 | cb => \&IO::AIO::poll_cb); |
97 | |
97 | |
98 | # queue the request to open /etc/passwd |
98 | # queue the request to open /etc/passwd |
99 | aio_open "/etc/passwd", O_RDONLY, 0, sub { |
99 | aio_open "/etc/passwd", O_RDONLY, 0, sub { |
100 | my $fh = $_[0] |
100 | my $fh = shift |
101 | or die "error while opening: $!"; |
101 | or die "error while opening: $!"; |
102 | |
102 | |
103 | # stat'ing filehandles is generally non-blocking |
103 | # stat'ing filehandles is generally non-blocking |
104 | my $size = -s $fh; |
104 | my $size = -s $fh; |
105 | |
105 | |
… | |
… | |
241 | They are the same as used by "sysopen". |
241 | They are the same as used by "sysopen". |
242 | |
242 | |
243 | Likewise, $mode specifies the mode of the newly created file, if it |
243 | Likewise, $mode specifies the mode of the newly created file, if it |
244 | didn't exist and "O_CREAT" has been given, just like perl's |
244 | didn't exist and "O_CREAT" has been given, just like perl's |
245 | "sysopen", except that it is mandatory (i.e. use 0 if you don't |
245 | "sysopen", except that it is mandatory (i.e. use 0 if you don't |
246 | create new files, and 0666 or 0777 if you do). |
246 | create new files, and 0666 or 0777 if you do). Note that the $mode |
|
|
247 | will be modified by the umask in effect then the request is being |
|
|
248 | executed, so better never change the umask. |
247 | |
249 | |
248 | Example: |
250 | Example: |
249 | |
251 | |
250 | aio_open "/etc/passwd", O_RDONLY, 0, sub { |
252 | aio_open "/etc/passwd", O_RDONLY, 0, sub { |
251 | if ($_[0]) { |
253 | if ($_[0]) { |
… | |
… | |
256 | } |
258 | } |
257 | }; |
259 | }; |
258 | |
260 | |
259 | aio_close $fh, $callback->($status) |
261 | aio_close $fh, $callback->($status) |
260 | Asynchronously close a file and call the callback with the result |
262 | Asynchronously close a file and call the callback with the result |
261 | code. *WARNING:* although accepted, you should not pass in a perl |
263 | code. |
262 | filehandle here, as perl will likely close the file descriptor |
|
|
263 | another time when the filehandle is destroyed. Normally, you can |
|
|
264 | safely call perls "close" or just let filehandles go out of scope. |
|
|
265 | |
264 | |
266 | This is supposed to be a bug in the API, so that might change. It's |
265 | Unlike the other functions operating on files, this function uses |
267 | therefore best to avoid this function. |
266 | the PerlIO layer to close the filehandle. The reason is that the |
|
|
267 | PerlIO API insists on closing the underlying fd itself, no matter |
|
|
268 | what, and doesn't allow modifications to the fd. Unfortunately, it |
|
|
269 | is not clear that you can call PerlIO from different threads |
|
|
270 | (actually, its quite clear that this won't work in some cases), so |
|
|
271 | while it likely works perfectly with simple file handles (such as |
|
|
272 | the ones created by "aio_open") it might fail in interesting ways |
|
|
273 | for others. |
|
|
274 | |
|
|
275 | Having said that, aio_close tries to clean up the filehandle as much |
|
|
276 | as possible before handing it to an io thread, and generally does |
|
|
277 | work. |
268 | |
278 | |
269 | aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
279 | aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
270 | aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
280 | aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
271 | Reads or writes "length" bytes from the specified "fh" and "offset" |
281 | Reads or writes $length bytes from the specified $fh and $offset |
272 | into the scalar given by "data" and offset "dataoffset" and calls |
282 | into the scalar given by $data and offset $dataoffset and calls the |
273 | the callback without the actual number of bytes read (or -1 on |
283 | callback without the actual number of bytes read (or -1 on error, |
274 | error, just like the syscall). |
284 | just like the syscall). |
|
|
285 | |
|
|
286 | If $offset is undefined, then the current file descriptor offset |
|
|
287 | will be used (and updated), otherwise the file descriptor offset |
|
|
288 | will not be changed by these calls. |
|
|
289 | |
|
|
290 | If $length is undefined in "aio_write", use the remaining length of |
|
|
291 | $data. |
|
|
292 | |
|
|
293 | If $dataoffset is less than zero, it will be counted from the end of |
|
|
294 | $data. |
275 | |
295 | |
276 | The $data scalar *MUST NOT* be modified in any way while the request |
296 | The $data scalar *MUST NOT* be modified in any way while the request |
277 | is outstanding. Modifying it can result in segfaults or WW3 (if the |
297 | is outstanding. Modifying it can result in segfaults or World War |
278 | necessary/optional hardware is installed). |
298 | III (if the necessary/optional hardware is installed). |
279 | |
299 | |
280 | Example: Read 15 bytes at offset 7 into scalar $buffer, starting at |
300 | Example: Read 15 bytes at offset 7 into scalar $buffer, starting at |
281 | offset 0 within the scalar: |
301 | offset 0 within the scalar: |
282 | |
302 | |
283 | aio_read $fh, 7, 15, $buffer, 0, sub { |
303 | aio_read $fh, 7, 15, $buffer, 0, sub { |
… | |
… | |
341 | aio_stat "/etc/passwd", sub { |
361 | aio_stat "/etc/passwd", sub { |
342 | $_[0] and die "stat failed: $!"; |
362 | $_[0] and die "stat failed: $!"; |
343 | print "size is ", -s _, "\n"; |
363 | print "size is ", -s _, "\n"; |
344 | }; |
364 | }; |
345 | |
365 | |
|
|
366 | aio_utime $fh_or_path, $atime, $mtime, $callback->($status) |
|
|
367 | Works like perl's "utime" function (including the special case of |
|
|
368 | $atime and $mtime being undef). Fractional times are supported if |
|
|
369 | the underlying syscalls support them. |
|
|
370 | |
|
|
371 | When called with a pathname, uses utimes(2) if available, otherwise |
|
|
372 | utime(2). If called on a file descriptor, uses futimes(2) if |
|
|
373 | available, otherwise returns ENOSYS, so this is not portable. |
|
|
374 | |
|
|
375 | Examples: |
|
|
376 | |
|
|
377 | # set atime and mtime to current time (basically touch(1)): |
|
|
378 | aio_utime "path", undef, undef; |
|
|
379 | # set atime to current time and mtime to beginning of the epoch: |
|
|
380 | aio_utime "path", time, undef; # undef==0 |
|
|
381 | |
|
|
382 | aio_chown $fh_or_path, $uid, $gid, $callback->($status) |
|
|
383 | Works like perl's "chown" function, except that "undef" for either |
|
|
384 | $uid or $gid is being interpreted as "do not change" (but -1 can |
|
|
385 | also be used). |
|
|
386 | |
|
|
387 | Examples: |
|
|
388 | |
|
|
389 | # same as "chown root path" in the shell: |
|
|
390 | aio_chown "path", 0, -1; |
|
|
391 | # same as above: |
|
|
392 | aio_chown "path", 0, undef; |
|
|
393 | |
|
|
394 | aio_truncate $fh_or_path, $offset, $callback->($status) |
|
|
395 | Works like truncate(2) or ftruncate(2). |
|
|
396 | |
|
|
397 | aio_chmod $fh_or_path, $mode, $callback->($status) |
|
|
398 | Works like perl's "chmod" function. |
|
|
399 | |
346 | aio_unlink $pathname, $callback->($status) |
400 | aio_unlink $pathname, $callback->($status) |
347 | Asynchronously unlink (delete) a file and call the callback with the |
401 | Asynchronously unlink (delete) a file and call the callback with the |
348 | result code. |
402 | result code. |
349 | |
403 | |
350 | aio_mknod $path, $mode, $dev, $callback->($status) |
404 | aio_mknod $path, $mode, $dev, $callback->($status) |
… | |
… | |
372 | |
426 | |
373 | aio_rename $srcpath, $dstpath, $callback->($status) |
427 | aio_rename $srcpath, $dstpath, $callback->($status) |
374 | Asynchronously rename the object at $srcpath to $dstpath, just as |
428 | Asynchronously rename the object at $srcpath to $dstpath, just as |
375 | rename(2) and call the callback with the result code. |
429 | rename(2) and call the callback with the result code. |
376 | |
430 | |
|
|
431 | aio_mkdir $pathname, $mode, $callback->($status) |
|
|
432 | Asynchronously mkdir (create) a directory and call the callback with |
|
|
433 | the result code. $mode will be modified by the umask at the time the |
|
|
434 | request is executed, so do not change your umask. |
|
|
435 | |
377 | aio_rmdir $pathname, $callback->($status) |
436 | aio_rmdir $pathname, $callback->($status) |
378 | Asynchronously rmdir (delete) a directory and call the callback with |
437 | Asynchronously rmdir (delete) a directory and call the callback with |
379 | the result code. |
438 | the result code. |
380 | |
439 | |
381 | aio_readdir $pathname, $callback->($entries) |
440 | aio_readdir $pathname, $callback->($entries) |
… | |
… | |
383 | entire directory (i.e. opendir + readdir + closedir). The entries |
442 | entire directory (i.e. opendir + readdir + closedir). The entries |
384 | will not be sorted, and will NOT include the "." and ".." entries. |
443 | will not be sorted, and will NOT include the "." and ".." entries. |
385 | |
444 | |
386 | The callback a single argument which is either "undef" or an |
445 | The callback a single argument which is either "undef" or an |
387 | array-ref with the filenames. |
446 | array-ref with the filenames. |
|
|
447 | |
|
|
448 | aio_load $path, $data, $callback->($status) |
|
|
449 | This is a composite request that tries to fully load the given file |
|
|
450 | into memory. Status is the same as with aio_read. |
388 | |
451 | |
389 | aio_copy $srcpath, $dstpath, $callback->($status) |
452 | aio_copy $srcpath, $dstpath, $callback->($status) |
390 | Try to copy the *file* (directories not supported as either source |
453 | Try to copy the *file* (directories not supported as either source |
391 | or destination) from $srcpath to $dstpath and call the callback with |
454 | or destination) from $srcpath to $dstpath and call the callback with |
392 | the 0 (error) or -1 ok. |
455 | the 0 (error) or -1 ok. |
… | |
… | |
460 | |
523 | |
461 | It will also likely work on non-POSIX filesystems with reduced |
524 | It will also likely work on non-POSIX filesystems with reduced |
462 | efficiency as those tend to return 0 or 1 as link counts, which |
525 | efficiency as those tend to return 0 or 1 as link counts, which |
463 | disables the directory counting heuristic. |
526 | disables the directory counting heuristic. |
464 | |
527 | |
|
|
528 | aio_rmtree $path, $callback->($status) |
|
|
529 | Delete a directory tree starting (and including) $path, return the |
|
|
530 | status of the final "rmdir" only. This is a composite request that |
|
|
531 | uses "aio_scandir" to recurse into and rmdir directories, and unlink |
|
|
532 | everything else. |
|
|
533 | |
465 | aio_fsync $fh, $callback->($status) |
534 | aio_fsync $fh, $callback->($status) |
466 | Asynchronously call fsync on the given filehandle and call the |
535 | Asynchronously call fsync on the given filehandle and call the |
467 | callback with the fsync result code. |
536 | callback with the fsync result code. |
468 | |
537 | |
469 | aio_fdatasync $fh, $callback->($status) |
538 | aio_fdatasync $fh, $callback->($status) |
… | |
… | |
711 | Event->io (fd => IO::AIO::poll_fileno, |
780 | Event->io (fd => IO::AIO::poll_fileno, |
712 | poll => 'r', nice => 1, |
781 | poll => 'r', nice => 1, |
713 | cb => &IO::AIO::poll_cb); |
782 | cb => &IO::AIO::poll_cb); |
714 | |
783 | |
715 | IO::AIO::poll_wait |
784 | IO::AIO::poll_wait |
|
|
785 | If there are any outstanding requests and none of them in the result |
716 | Wait till the result filehandle becomes ready for reading (simply |
786 | phase, wait till the result filehandle becomes ready for reading |
717 | does a "select" on the filehandle. This is useful if you want to |
787 | (simply does a "select" on the filehandle. This is useful if you |
718 | synchronously wait for some requests to finish). |
788 | want to synchronously wait for some requests to finish). |
719 | |
789 | |
720 | See "nreqs" for an example. |
790 | See "nreqs" for an example. |
721 | |
791 | |
722 | IO::AIO::poll |
792 | IO::AIO::poll |
723 | Waits until some requests have been handled. |
793 | Waits until some requests have been handled. |
724 | |
794 | |
|
|
795 | Returns the number of requests processed, but is otherwise strictly |
725 | Strictly equivalent to: |
796 | equivalent to: |
726 | |
797 | |
727 | IO::AIO::poll_wait, IO::AIO::poll_cb |
798 | IO::AIO::poll_wait, IO::AIO::poll_cb |
728 | if IO::AIO::nreqs; |
|
|
729 | |
799 | |
730 | IO::AIO::flush |
800 | IO::AIO::flush |
731 | Wait till all outstanding AIO requests have been handled. |
801 | Wait till all outstanding AIO requests have been handled. |
732 | |
802 | |
733 | Strictly equivalent to: |
803 | Strictly equivalent to: |
… | |
… | |
789 | $oldmaxreqs = IO::AIO::max_outstanding $maxreqs |
859 | $oldmaxreqs = IO::AIO::max_outstanding $maxreqs |
790 | This is a very bad function to use in interactive programs because |
860 | This is a very bad function to use in interactive programs because |
791 | it blocks, and a bad way to reduce concurrency because it is |
861 | it blocks, and a bad way to reduce concurrency because it is |
792 | inexact: Better use an "aio_group" together with a feed callback. |
862 | inexact: Better use an "aio_group" together with a feed callback. |
793 | |
863 | |
794 | Sets the maximum number of outstanding requests to $nreqs. If you to |
864 | Sets the maximum number of outstanding requests to $nreqs. If you do |
795 | queue up more than this number of requests, the next call to the |
865 | queue up more than this number of requests, the next call to the |
796 | "poll_cb" (and "poll_some" and other functions calling "poll_cb") |
866 | "poll_cb" (and "poll_some" and other functions calling "poll_cb") |
797 | function will block until the limit is no longer exceeded. |
867 | function will block until the limit is no longer exceeded. |
798 | |
868 | |
799 | The default value is very large, so there is no practical limit on |
869 | The default value is very large, so there is no practical limit on |
… | |
… | |
845 | bytes of memory. In addition, stat requests need a stat buffer (possibly |
915 | bytes of memory. In addition, stat requests need a stat buffer (possibly |
846 | a few hundred bytes), readdir requires a result buffer and so on. Perl |
916 | a few hundred bytes), readdir requires a result buffer and so on. Perl |
847 | scalars and other data passed into aio requests will also be locked and |
917 | scalars and other data passed into aio requests will also be locked and |
848 | will consume memory till the request has entered the done state. |
918 | will consume memory till the request has entered the done state. |
849 | |
919 | |
850 | This is now awfully much, so queuing lots of requests is not usually a |
920 | This is not awfully much, so queuing lots of requests is not usually a |
851 | problem. |
921 | problem. |
852 | |
922 | |
853 | Per-thread usage: |
923 | Per-thread usage: |
854 | |
924 | |
855 | In the execution phase, some aio requests require more memory for |
925 | In the execution phase, some aio requests require more memory for |