… | |
… | |
24 | $req->cancel; # cancel request if still in queue |
24 | $req->cancel; # cancel request if still in queue |
25 | |
25 | |
26 | my $grp = aio_group sub { print "all stats done\n" }; |
26 | my $grp = aio_group sub { print "all stats done\n" }; |
27 | add $grp aio_stat "..." for ...; |
27 | add $grp aio_stat "..." for ...; |
28 | |
28 | |
|
|
29 | # AnyEvent integration (EV, Event, Glib, Tk, POE, urxvt, pureperl...) |
|
|
30 | use AnyEvent::AIO; |
|
|
31 | |
29 | # AnyEvent integration |
32 | # EV integration |
30 | open my $fh, "<&=" . IO::AIO::poll_fileno or die "$!"; |
33 | my $w = EV::io IO::AIO::poll_fileno, EV::READ, \&IO::AIO::poll_cb; |
31 | my $w = AnyEvent->io (fh => $fh, poll => 'r', cb => sub { IO::AIO::poll_cb }); |
|
|
32 | |
34 | |
33 | # Event integration |
35 | # Event integration |
34 | Event->io (fd => IO::AIO::poll_fileno, |
36 | Event->io (fd => IO::AIO::poll_fileno, |
35 | poll => 'r', |
37 | poll => 'r', |
36 | cb => \&IO::AIO::poll_cb); |
38 | cb => \&IO::AIO::poll_cb); |
… | |
… | |
262 | Asynchronously close a file and call the callback with the result |
264 | Asynchronously close a file and call the callback with the result |
263 | code. |
265 | code. |
264 | |
266 | |
265 | Unfortunately, you can't do this to perl. Perl *insists* very |
267 | Unfortunately, you can't do this to perl. Perl *insists* very |
266 | strongly on closing the file descriptor associated with the |
268 | strongly on closing the file descriptor associated with the |
267 | filehandle itself. Here is what aio_close will try: |
269 | filehandle itself. |
268 | |
270 | |
269 | 1. dup()licate the fd |
271 | Therefore, "aio_close" will not close the filehandle - instead it |
270 | 2. asynchronously close() the duplicated fd |
272 | will use dup2 to overwrite the file descriptor with the write-end of |
271 | 3. dup()licate the fd once more |
273 | a pipe (the pipe fd will be created on demand and will be cached). |
272 | 4. let perl close() the filehandle |
|
|
273 | 5. asynchronously close the duplicated fd |
|
|
274 | |
274 | |
275 | The idea is that the first close() flushes stuff to disk that |
275 | Or in other words: the file descriptor will be closed, but it will |
276 | closing an fd will flush, so when perl closes the fd, nothing much |
276 | not be free for reuse until the perl filehandle is closed. |
277 | will need to be flushed. The second async. close() will then flush |
|
|
278 | stuff to disk that closing the last fd to the file will flush. |
|
|
279 | |
|
|
280 | Just FYI, SuSv3 has this to say on close: |
|
|
281 | |
|
|
282 | All outstanding record locks owned by the process on the file |
|
|
283 | associated with the file descriptor shall be removed. |
|
|
284 | |
|
|
285 | If fildes refers to a socket, close() shall cause the socket to be |
|
|
286 | destroyed. ... close() shall block for up to the current linger |
|
|
287 | interval until all data is transmitted. |
|
|
288 | [this actually sounds like a specification bug, but who knows] |
|
|
289 | |
|
|
290 | And at least Linux additionally actually flushes stuff on every |
|
|
291 | close, even when the file itself is still open. |
|
|
292 | |
|
|
293 | Sounds enourmously inefficient and complicated? Yes... please show |
|
|
294 | me how to nuke perl's fd out of existence... |
|
|
295 | |
277 | |
296 | aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
278 | aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
297 | aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
279 | aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
298 | Reads or writes $length bytes from the specified $fh and $offset |
280 | Reads or writes $length bytes from the specified $fh and $offset |
299 | into the scalar given by $data and offset $dataoffset and calls the |
281 | into the scalar given by $data and offset $dataoffset and calls the |
… | |
… | |
546 | Delete a directory tree starting (and including) $path, return the |
528 | Delete a directory tree starting (and including) $path, return the |
547 | status of the final "rmdir" only. This is a composite request that |
529 | status of the final "rmdir" only. This is a composite request that |
548 | uses "aio_scandir" to recurse into and rmdir directories, and unlink |
530 | uses "aio_scandir" to recurse into and rmdir directories, and unlink |
549 | everything else. |
531 | everything else. |
550 | |
532 | |
|
|
533 | aio_sync $callback->($status) |
|
|
534 | Asynchronously call sync and call the callback when finished. |
|
|
535 | |
551 | aio_fsync $fh, $callback->($status) |
536 | aio_fsync $fh, $callback->($status) |
552 | Asynchronously call fsync on the given filehandle and call the |
537 | Asynchronously call fsync on the given filehandle and call the |
553 | callback with the fsync result code. |
538 | callback with the fsync result code. |
554 | |
539 | |
555 | aio_fdatasync $fh, $callback->($status) |
540 | aio_fdatasync $fh, $callback->($status) |
556 | Asynchronously call fdatasync on the given filehandle and call the |
541 | Asynchronously call fdatasync on the given filehandle and call the |
557 | callback with the fdatasync result code. |
542 | callback with the fdatasync result code. |
558 | |
543 | |
559 | If this call isn't available because your OS lacks it or it couldn't |
544 | If this call isn't available because your OS lacks it or it couldn't |
560 | be detected, it will be emulated by calling "fsync" instead. |
545 | be detected, it will be emulated by calling "fsync" instead. |
|
|
546 | |
|
|
547 | aio_pathsync $path, $callback->($status) |
|
|
548 | This request tries to open, fsync and close the given path. This is |
|
|
549 | a composite request intended tosync directories after directory |
|
|
550 | operations (E.g. rename). This might not work on all operating |
|
|
551 | systems or have any specific effect, but usually it makes sure that |
|
|
552 | directory changes get written to disc. It works for anything that |
|
|
553 | can be opened for read-only, not just directories. |
|
|
554 | |
|
|
555 | Passes 0 when everything went ok, and -1 on error. |
561 | |
556 | |
562 | aio_group $callback->(...) |
557 | aio_group $callback->(...) |
563 | This is a very special aio request: Instead of doing something, it |
558 | This is a very special aio request: Instead of doing something, it |
564 | is a container for other aio requests, which is useful if you want |
559 | is a container for other aio requests, which is useful if you want |
565 | to bundle many requests into a single, composite, request with a |
560 | to bundle many requests into a single, composite, request with a |
… | |
… | |
647 | }; |
642 | }; |
648 | |
643 | |
649 | This makes it very easy to create composite requests (see the source of |
644 | This makes it very easy to create composite requests (see the source of |
650 | "aio_move" for an application) that work and feel like simple requests. |
645 | "aio_move" for an application) that work and feel like simple requests. |
651 | |
646 | |
652 | * The IO::AIO::GRP objects will be cleaned up during calls to |
647 | * The IO::AIO::GRP objects will be cleaned up during calls to |
653 | "IO::AIO::poll_cb", just like any other request. |
648 | "IO::AIO::poll_cb", just like any other request. |
|
|
649 | |
654 | * They can be canceled like any other request. Canceling will cancel not |
650 | * They can be canceled like any other request. Canceling will cancel |
655 | only the request itself, but also all requests it contains. |
651 | not only the request itself, but also all requests it contains. |
|
|
652 | |
656 | * They can also can also be added to other IO::AIO::GRP objects. |
653 | * They can also can also be added to other IO::AIO::GRP objects. |
|
|
654 | |
657 | * You must not add requests to a group from within the group callback |
655 | * You must not add requests to a group from within the group callback |
658 | (or any later time). |
656 | (or any later time). |
659 | |
657 | |
660 | Their lifetime, simplified, looks like this: when they are empty, they |
658 | Their lifetime, simplified, looks like this: when they are empty, they |
661 | will finish very quickly. If they contain only requests that are in the |
659 | will finish very quickly. If they contain only requests that are in the |
662 | "done" state, they will also finish. Otherwise they will continue to |
660 | "done" state, they will also finish. Otherwise they will continue to |
663 | exist. |
661 | exist. |
… | |
… | |
680 | request itself. Useful when you queued a lot of events but got a |
678 | request itself. Useful when you queued a lot of events but got a |
681 | result early. |
679 | result early. |
682 | |
680 | |
683 | $grp->result (...) |
681 | $grp->result (...) |
684 | Set the result value(s) that will be passed to the group callback |
682 | Set the result value(s) that will be passed to the group callback |
685 | when all subrequests have finished and set thre groups errno to the |
683 | when all subrequests have finished and set the groups errno to the |
686 | current value of errno (just like calling "errno" without an error |
684 | current value of errno (just like calling "errno" without an error |
687 | number). By default, no argument will be passed and errno is zero. |
685 | number). By default, no argument will be passed and errno is zero. |
688 | |
686 | |
689 | $grp->errno ([$errno]) |
687 | $grp->errno ([$errno]) |
690 | Sets the group errno value to $errno, or the current value of errno |
688 | Sets the group errno value to $errno, or the current value of errno |
… | |
… | |
749 | |
747 | |
750 | See "poll_cb" for an example. |
748 | See "poll_cb" for an example. |
751 | |
749 | |
752 | IO::AIO::poll_cb |
750 | IO::AIO::poll_cb |
753 | Process some outstanding events on the result pipe. You have to call |
751 | Process some outstanding events on the result pipe. You have to call |
754 | this regularly. Returns the number of events processed. Returns |
752 | this regularly. Returns 0 if all events could be processed, or -1 if |
755 | immediately when no events are outstanding. The amount of events |
753 | it returned earlier for whatever reason. Returns immediately when no |
|
|
754 | events are outstanding. The amount of events processed depends on |
756 | processed depends on the settings of "IO::AIO::max_poll_req" and |
755 | the settings of "IO::AIO::max_poll_req" and |
757 | "IO::AIO::max_poll_time". |
756 | "IO::AIO::max_poll_time". |
758 | |
757 | |
759 | If not all requests were processed for whatever reason, the |
758 | If not all requests were processed for whatever reason, the |
760 | filehandle will still be ready when "poll_cb" returns. |
759 | filehandle will still be ready when "poll_cb" returns, so normally |
|
|
760 | you don't have to do anything special to have it called later. |
761 | |
761 | |
762 | Example: Install an Event watcher that automatically calls |
762 | Example: Install an Event watcher that automatically calls |
763 | IO::AIO::poll_cb with high priority: |
763 | IO::AIO::poll_cb with high priority: |
764 | |
764 | |
765 | Event->io (fd => IO::AIO::poll_fileno, |
765 | Event->io (fd => IO::AIO::poll_fileno, |
… | |
… | |
871 | |
871 | |
872 | The default is probably ok in most situations, especially if thread |
872 | The default is probably ok in most situations, especially if thread |
873 | creation is fast. If thread creation is very slow on your system you |
873 | creation is fast. If thread creation is very slow on your system you |
874 | might want to use larger values. |
874 | might want to use larger values. |
875 | |
875 | |
876 | $oldmaxreqs = IO::AIO::max_outstanding $maxreqs |
876 | IO::AIO::max_outstanding $maxreqs |
877 | This is a very bad function to use in interactive programs because |
877 | This is a very bad function to use in interactive programs because |
878 | it blocks, and a bad way to reduce concurrency because it is |
878 | it blocks, and a bad way to reduce concurrency because it is |
879 | inexact: Better use an "aio_group" together with a feed callback. |
879 | inexact: Better use an "aio_group" together with a feed callback. |
880 | |
880 | |
881 | Sets the maximum number of outstanding requests to $nreqs. If you do |
881 | Sets the maximum number of outstanding requests to $nreqs. If you do |
… | |
… | |
885 | |
885 | |
886 | The default value is very large, so there is no practical limit on |
886 | The default value is very large, so there is no practical limit on |
887 | the number of outstanding requests. |
887 | the number of outstanding requests. |
888 | |
888 | |
889 | You can still queue as many requests as you want. Therefore, |
889 | You can still queue as many requests as you want. Therefore, |
890 | "max_oustsanding" is mainly useful in simple scripts (with low |
890 | "max_outstanding" is mainly useful in simple scripts (with low |
891 | values) or as a stop gap to shield against fatal memory overflow |
891 | values) or as a stop gap to shield against fatal memory overflow |
892 | (with large values). |
892 | (with large values). |
893 | |
893 | |
894 | STATISTICAL INFORMATION |
894 | STATISTICAL INFORMATION |
895 | IO::AIO::nreqs |
895 | IO::AIO::nreqs |
… | |
… | |
945 | |
945 | |
946 | KNOWN BUGS |
946 | KNOWN BUGS |
947 | Known bugs will be fixed in the next release. |
947 | Known bugs will be fixed in the next release. |
948 | |
948 | |
949 | SEE ALSO |
949 | SEE ALSO |
950 | Coro::AIO. |
950 | AnyEvent::AIO for easy integration into event loops, Coro::AIO for a |
|
|
951 | more natural syntax. |
951 | |
952 | |
952 | AUTHOR |
953 | AUTHOR |
953 | Marc Lehmann <schmorp@schmorp.de> |
954 | Marc Lehmann <schmorp@schmorp.de> |
954 | http://home.schmorp.de/ |
955 | http://home.schmorp.de/ |
955 | |
956 | |