… | |
… | |
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); |
… | |
… | |
61 | faster on a RAID volume or over NFS when you do a number of stat |
63 | faster on a RAID volume or over NFS when you do a number of stat |
62 | operations concurrently. |
64 | operations concurrently. |
63 | |
65 | |
64 | While most of this works on all types of file descriptors (for example |
66 | While most of this works on all types of file descriptors (for example |
65 | sockets), using these functions on file descriptors that support |
67 | sockets), using these functions on file descriptors that support |
66 | nonblocking operation (again, sockets, pipes etc.) is very inefficient |
68 | nonblocking operation (again, sockets, pipes etc.) is very inefficient. |
67 | or might not work (aio_read fails on sockets/pipes/fifos). Use an event |
|
|
68 | loop for that (such as the Event module): IO::AIO will naturally fit |
69 | Use an event loop for that (such as the Event module): IO::AIO will |
69 | into such an event loop itself. |
70 | naturally fit into such an event loop itself. |
70 | |
71 | |
71 | In this version, a number of threads are started that execute your |
72 | In this version, a number of threads are started that execute your |
72 | requests and signal their completion. You don't need thread support in |
73 | requests and signal their completion. You don't need thread support in |
73 | perl, and the threads created by this module will not be visible to |
74 | perl, and the threads created by this module will not be visible to |
74 | perl. In the future, this module might make use of the native aio |
75 | perl. In the future, this module might make use of the native aio |
… | |
… | |
76 | not well-supported or restricted (GNU/Linux doesn't allow them on normal |
77 | not well-supported or restricted (GNU/Linux doesn't allow them on normal |
77 | files currently, for example), and they would only support aio_read and |
78 | files currently, for example), and they would only support aio_read and |
78 | aio_write, so the remaining functionality would have to be implemented |
79 | aio_write, so the remaining functionality would have to be implemented |
79 | using threads anyway. |
80 | using threads anyway. |
80 | |
81 | |
81 | Although the module will work with in the presence of other (Perl-) |
82 | Although the module will work in the presence of other (Perl-) threads, |
82 | threads, it is currently not reentrant in any way, so use appropriate |
83 | it is currently not reentrant in any way, so use appropriate locking |
83 | locking yourself, always call "poll_cb" from within the same thread, or |
84 | yourself, always call "poll_cb" from within the same thread, or never |
84 | never call "poll_cb" (or other "aio_" functions) recursively. |
85 | call "poll_cb" (or other "aio_" functions) recursively. |
85 | |
86 | |
86 | EXAMPLE |
87 | EXAMPLE |
87 | This is a simple example that uses the Event module and loads |
88 | This is a simple example that uses the Event module and loads |
88 | /etc/passwd asynchronously: |
89 | /etc/passwd asynchronously: |
89 | |
90 | |
… | |
… | |
174 | All the "aio_*" calls are more or less thin wrappers around the syscall |
175 | All the "aio_*" calls are more or less thin wrappers around the syscall |
175 | with the same name (sans "aio_"). The arguments are similar or |
176 | with the same name (sans "aio_"). The arguments are similar or |
176 | identical, and they all accept an additional (and optional) $callback |
177 | identical, and they all accept an additional (and optional) $callback |
177 | argument which must be a code reference. This code reference will get |
178 | argument which must be a code reference. This code reference will get |
178 | called with the syscall return code (e.g. most syscalls return -1 on |
179 | called with the syscall return code (e.g. most syscalls return -1 on |
179 | error, unlike perl, which usually delivers "false") as it's sole |
180 | error, unlike perl, which usually delivers "false") as its sole argument |
180 | argument when the given syscall has been executed asynchronously. |
181 | after the given syscall has been executed asynchronously. |
181 | |
182 | |
182 | All functions expecting a filehandle keep a copy of the filehandle |
183 | All functions expecting a filehandle keep a copy of the filehandle |
183 | internally until the request has finished. |
184 | internally until the request has finished. |
184 | |
185 | |
185 | All functions return request objects of type IO::AIO::REQ that allow |
186 | All functions return request objects of type IO::AIO::REQ that allow |
… | |
… | |
198 | the user environment, d) use Glib::filename_from_unicode on unicode |
199 | the user environment, d) use Glib::filename_from_unicode on unicode |
199 | filenames or e) use something else to ensure your scalar has the correct |
200 | filenames or e) use something else to ensure your scalar has the correct |
200 | contents. |
201 | contents. |
201 | |
202 | |
202 | This works, btw. independent of the internal UTF-8 bit, which IO::AIO |
203 | This works, btw. independent of the internal UTF-8 bit, which IO::AIO |
203 | handles correctly wether it is set or not. |
204 | handles correctly whether it is set or not. |
204 | |
205 | |
205 | $prev_pri = aioreq_pri [$pri] |
206 | $prev_pri = aioreq_pri [$pri] |
206 | Returns the priority value that would be used for the next request |
207 | Returns the priority value that would be used for the next request |
207 | and, if $pri is given, sets the priority for the next aio request. |
208 | and, if $pri is given, sets the priority for the next aio request. |
208 | |
209 | |
… | |
… | |
242 | They are the same as used by "sysopen". |
243 | They are the same as used by "sysopen". |
243 | |
244 | |
244 | Likewise, $mode specifies the mode of the newly created file, if it |
245 | Likewise, $mode specifies the mode of the newly created file, if it |
245 | didn't exist and "O_CREAT" has been given, just like perl's |
246 | didn't exist and "O_CREAT" has been given, just like perl's |
246 | "sysopen", except that it is mandatory (i.e. use 0 if you don't |
247 | "sysopen", except that it is mandatory (i.e. use 0 if you don't |
247 | create new files, and 0666 or 0777 if you do). |
248 | create new files, and 0666 or 0777 if you do). Note that the $mode |
|
|
249 | will be modified by the umask in effect then the request is being |
|
|
250 | executed, so better never change the umask. |
248 | |
251 | |
249 | Example: |
252 | Example: |
250 | |
253 | |
251 | aio_open "/etc/passwd", O_RDONLY, 0, sub { |
254 | aio_open "/etc/passwd", O_RDONLY, 0, sub { |
252 | if ($_[0]) { |
255 | if ($_[0]) { |
… | |
… | |
257 | } |
260 | } |
258 | }; |
261 | }; |
259 | |
262 | |
260 | aio_close $fh, $callback->($status) |
263 | aio_close $fh, $callback->($status) |
261 | Asynchronously close a file and call the callback with the result |
264 | Asynchronously close a file and call the callback with the result |
262 | code. *WARNING:* although accepted, you should not pass in a perl |
265 | code. |
263 | filehandle here, as perl will likely close the file descriptor |
|
|
264 | another time when the filehandle is destroyed. Normally, you can |
|
|
265 | safely call perls "close" or just let filehandles go out of scope. |
|
|
266 | |
266 | |
267 | This is supposed to be a bug in the API, so that might change. It's |
267 | Unfortunately, you can't do this to perl. Perl *insists* very |
268 | therefore best to avoid this function. |
268 | strongly on closing the file descriptor associated with the |
|
|
269 | filehandle itself. |
|
|
270 | |
|
|
271 | Therefore, "aio_close" will not close the filehandle - instead it |
|
|
272 | will use dup2 to overwrite the file descriptor with the write-end of |
|
|
273 | a pipe (the pipe fd will be created on demand and will be cached). |
|
|
274 | |
|
|
275 | Or in other words: the file descriptor will be closed, but it will |
|
|
276 | not be free for reuse until the perl filehandle is closed. |
269 | |
277 | |
270 | aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
278 | aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
271 | aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
279 | aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
272 | Reads or writes "length" bytes from the specified "fh" and "offset" |
280 | Reads or writes $length bytes from the specified $fh and $offset |
273 | into the scalar given by "data" and offset "dataoffset" and calls |
281 | into the scalar given by $data and offset $dataoffset and calls the |
274 | the callback without the actual number of bytes read (or -1 on |
282 | callback without the actual number of bytes read (or -1 on error, |
275 | error, just like the syscall). |
283 | just like the syscall). |
|
|
284 | |
|
|
285 | If $offset is undefined, then the current file descriptor offset |
|
|
286 | will be used (and updated), otherwise the file descriptor offset |
|
|
287 | will not be changed by these calls. |
|
|
288 | |
|
|
289 | If $length is undefined in "aio_write", use the remaining length of |
|
|
290 | $data. |
|
|
291 | |
|
|
292 | If $dataoffset is less than zero, it will be counted from the end of |
|
|
293 | $data. |
276 | |
294 | |
277 | The $data scalar *MUST NOT* be modified in any way while the request |
295 | The $data scalar *MUST NOT* be modified in any way while the request |
278 | is outstanding. Modifying it can result in segfaults or WW3 (if the |
296 | is outstanding. Modifying it can result in segfaults or World War |
279 | necessary/optional hardware is installed). |
297 | III (if the necessary/optional hardware is installed). |
280 | |
298 | |
281 | Example: Read 15 bytes at offset 7 into scalar $buffer, starting at |
299 | Example: Read 15 bytes at offset 7 into scalar $buffer, starting at |
282 | offset 0 within the scalar: |
300 | offset 0 within the scalar: |
283 | |
301 | |
284 | aio_read $fh, 7, 15, $buffer, 0, sub { |
302 | aio_read $fh, 7, 15, $buffer, 0, sub { |
… | |
… | |
342 | aio_stat "/etc/passwd", sub { |
360 | aio_stat "/etc/passwd", sub { |
343 | $_[0] and die "stat failed: $!"; |
361 | $_[0] and die "stat failed: $!"; |
344 | print "size is ", -s _, "\n"; |
362 | print "size is ", -s _, "\n"; |
345 | }; |
363 | }; |
346 | |
364 | |
|
|
365 | aio_utime $fh_or_path, $atime, $mtime, $callback->($status) |
|
|
366 | Works like perl's "utime" function (including the special case of |
|
|
367 | $atime and $mtime being undef). Fractional times are supported if |
|
|
368 | the underlying syscalls support them. |
|
|
369 | |
|
|
370 | When called with a pathname, uses utimes(2) if available, otherwise |
|
|
371 | utime(2). If called on a file descriptor, uses futimes(2) if |
|
|
372 | available, otherwise returns ENOSYS, so this is not portable. |
|
|
373 | |
|
|
374 | Examples: |
|
|
375 | |
|
|
376 | # set atime and mtime to current time (basically touch(1)): |
|
|
377 | aio_utime "path", undef, undef; |
|
|
378 | # set atime to current time and mtime to beginning of the epoch: |
|
|
379 | aio_utime "path", time, undef; # undef==0 |
|
|
380 | |
|
|
381 | aio_chown $fh_or_path, $uid, $gid, $callback->($status) |
|
|
382 | Works like perl's "chown" function, except that "undef" for either |
|
|
383 | $uid or $gid is being interpreted as "do not change" (but -1 can |
|
|
384 | also be used). |
|
|
385 | |
|
|
386 | Examples: |
|
|
387 | |
|
|
388 | # same as "chown root path" in the shell: |
|
|
389 | aio_chown "path", 0, -1; |
|
|
390 | # same as above: |
|
|
391 | aio_chown "path", 0, undef; |
|
|
392 | |
|
|
393 | aio_truncate $fh_or_path, $offset, $callback->($status) |
|
|
394 | Works like truncate(2) or ftruncate(2). |
|
|
395 | |
|
|
396 | aio_chmod $fh_or_path, $mode, $callback->($status) |
|
|
397 | Works like perl's "chmod" function. |
|
|
398 | |
347 | aio_unlink $pathname, $callback->($status) |
399 | aio_unlink $pathname, $callback->($status) |
348 | Asynchronously unlink (delete) a file and call the callback with the |
400 | Asynchronously unlink (delete) a file and call the callback with the |
349 | result code. |
401 | result code. |
350 | |
402 | |
351 | aio_mknod $path, $mode, $dev, $callback->($status) |
403 | aio_mknod $path, $mode, $dev, $callback->($status) |
… | |
… | |
373 | |
425 | |
374 | aio_rename $srcpath, $dstpath, $callback->($status) |
426 | aio_rename $srcpath, $dstpath, $callback->($status) |
375 | Asynchronously rename the object at $srcpath to $dstpath, just as |
427 | Asynchronously rename the object at $srcpath to $dstpath, just as |
376 | rename(2) and call the callback with the result code. |
428 | rename(2) and call the callback with the result code. |
377 | |
429 | |
|
|
430 | aio_mkdir $pathname, $mode, $callback->($status) |
|
|
431 | Asynchronously mkdir (create) a directory and call the callback with |
|
|
432 | the result code. $mode will be modified by the umask at the time the |
|
|
433 | request is executed, so do not change your umask. |
|
|
434 | |
378 | aio_rmdir $pathname, $callback->($status) |
435 | aio_rmdir $pathname, $callback->($status) |
379 | Asynchronously rmdir (delete) a directory and call the callback with |
436 | Asynchronously rmdir (delete) a directory and call the callback with |
380 | the result code. |
437 | the result code. |
381 | |
438 | |
382 | aio_readdir $pathname, $callback->($entries) |
439 | aio_readdir $pathname, $callback->($entries) |
… | |
… | |
394 | aio_copy $srcpath, $dstpath, $callback->($status) |
451 | aio_copy $srcpath, $dstpath, $callback->($status) |
395 | Try to copy the *file* (directories not supported as either source |
452 | Try to copy the *file* (directories not supported as either source |
396 | or destination) from $srcpath to $dstpath and call the callback with |
453 | or destination) from $srcpath to $dstpath and call the callback with |
397 | the 0 (error) or -1 ok. |
454 | the 0 (error) or -1 ok. |
398 | |
455 | |
399 | This is a composite request that it creates the destination file |
456 | This is a composite request that creates the destination file with |
400 | with mode 0200 and copies the contents of the source file into it |
457 | mode 0200 and copies the contents of the source file into it using |
401 | using "aio_sendfile", followed by restoring atime, mtime, access |
458 | "aio_sendfile", followed by restoring atime, mtime, access mode and |
402 | mode and uid/gid, in that order. |
459 | uid/gid, in that order. |
403 | |
460 | |
404 | If an error occurs, the partial destination file will be unlinked, |
461 | If an error occurs, the partial destination file will be unlinked, |
405 | if possible, except when setting atime, mtime, access mode and |
462 | if possible, except when setting atime, mtime, access mode and |
406 | uid/gid, where errors are being ignored. |
463 | uid/gid, where errors are being ignored. |
407 | |
464 | |
408 | aio_move $srcpath, $dstpath, $callback->($status) |
465 | aio_move $srcpath, $dstpath, $callback->($status) |
409 | Try to move the *file* (directories not supported as either source |
466 | Try to move the *file* (directories not supported as either source |
410 | or destination) from $srcpath to $dstpath and call the callback with |
467 | or destination) from $srcpath to $dstpath and call the callback with |
411 | the 0 (error) or -1 ok. |
468 | the 0 (error) or -1 ok. |
412 | |
469 | |
413 | This is a composite request that tries to rename(2) the file first. |
470 | This is a composite request that tries to rename(2) the file first; |
414 | If rename files with "EXDEV", it copies the file with "aio_copy" |
471 | if rename fails with "EXDEV", it copies the file with "aio_copy" |
415 | and, if that is successful, unlinking the $srcpath. |
472 | and, if that is successful, unlinks the $srcpath. |
416 | |
473 | |
417 | aio_scandir $path, $maxreq, $callback->($dirs, $nondirs) |
474 | aio_scandir $path, $maxreq, $callback->($dirs, $nondirs) |
418 | Scans a directory (similar to "aio_readdir") but additionally tries |
475 | Scans a directory (similar to "aio_readdir") but additionally tries |
419 | to efficiently separate the entries of directory $path into two sets |
476 | to efficiently separate the entries of directory $path into two sets |
420 | of names, directories you can recurse into (directories), and ones |
477 | of names, directories you can recurse into (directories), and ones |
… | |
… | |
465 | |
522 | |
466 | It will also likely work on non-POSIX filesystems with reduced |
523 | It will also likely work on non-POSIX filesystems with reduced |
467 | efficiency as those tend to return 0 or 1 as link counts, which |
524 | efficiency as those tend to return 0 or 1 as link counts, which |
468 | disables the directory counting heuristic. |
525 | disables the directory counting heuristic. |
469 | |
526 | |
|
|
527 | aio_rmtree $path, $callback->($status) |
|
|
528 | Delete a directory tree starting (and including) $path, return the |
|
|
529 | status of the final "rmdir" only. This is a composite request that |
|
|
530 | uses "aio_scandir" to recurse into and rmdir directories, and unlink |
|
|
531 | everything else. |
|
|
532 | |
|
|
533 | aio_sync $callback->($status) |
|
|
534 | Asynchronously call sync and call the callback when finished. |
|
|
535 | |
470 | aio_fsync $fh, $callback->($status) |
536 | aio_fsync $fh, $callback->($status) |
471 | Asynchronously call fsync on the given filehandle and call the |
537 | Asynchronously call fsync on the given filehandle and call the |
472 | callback with the fsync result code. |
538 | callback with the fsync result code. |
473 | |
539 | |
474 | aio_fdatasync $fh, $callback->($status) |
540 | aio_fdatasync $fh, $callback->($status) |
475 | Asynchronously call fdatasync on the given filehandle and call the |
541 | Asynchronously call fdatasync on the given filehandle and call the |
476 | callback with the fdatasync result code. |
542 | callback with the fdatasync result code. |
477 | |
543 | |
478 | 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 |
479 | be detected, it will be emulated by calling "fsync" instead. |
545 | be detected, it will be emulated by calling "fsync" instead. |
|
|
546 | |
|
|
547 | aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status) |
|
|
548 | Sync the data portion of the file specified by $offset and $length |
|
|
549 | to disk (but NOT the metadata), by calling the Linux-specific |
|
|
550 | sync_file_range call. If sync_file_range is not available or it |
|
|
551 | returns ENOSYS, then fdatasync or fsync is being substituted. |
|
|
552 | |
|
|
553 | $flags can be a combination of |
|
|
554 | "IO::AIO::SYNC_FILE_RANGE_WAIT_BEFORE", |
|
|
555 | "IO::AIO::SYNC_FILE_RANGE_WRITE" and |
|
|
556 | "IO::AIO::SYNC_FILE_RANGE_WAIT_AFTER": refer to the sync_file_range |
|
|
557 | manpage for details. |
|
|
558 | |
|
|
559 | aio_pathsync $path, $callback->($status) |
|
|
560 | This request tries to open, fsync and close the given path. This is |
|
|
561 | a composite request intended to sync directories after directory |
|
|
562 | operations (E.g. rename). This might not work on all operating |
|
|
563 | systems or have any specific effect, but usually it makes sure that |
|
|
564 | directory changes get written to disc. It works for anything that |
|
|
565 | can be opened for read-only, not just directories. |
|
|
566 | |
|
|
567 | Passes 0 when everything went ok, and -1 on error. |
480 | |
568 | |
481 | aio_group $callback->(...) |
569 | aio_group $callback->(...) |
482 | This is a very special aio request: Instead of doing something, it |
570 | This is a very special aio request: Instead of doing something, it |
483 | is a container for other aio requests, which is useful if you want |
571 | is a container for other aio requests, which is useful if you want |
484 | to bundle many requests into a single, composite, request with a |
572 | to bundle many requests into a single, composite, request with a |
… | |
… | |
566 | }; |
654 | }; |
567 | |
655 | |
568 | This makes it very easy to create composite requests (see the source of |
656 | This makes it very easy to create composite requests (see the source of |
569 | "aio_move" for an application) that work and feel like simple requests. |
657 | "aio_move" for an application) that work and feel like simple requests. |
570 | |
658 | |
571 | * The IO::AIO::GRP objects will be cleaned up during calls to |
659 | * The IO::AIO::GRP objects will be cleaned up during calls to |
572 | "IO::AIO::poll_cb", just like any other request. |
660 | "IO::AIO::poll_cb", just like any other request. |
|
|
661 | |
573 | * They can be canceled like any other request. Canceling will cancel not |
662 | * They can be canceled like any other request. Canceling will cancel |
574 | only the request itself, but also all requests it contains. |
663 | not only the request itself, but also all requests it contains. |
|
|
664 | |
575 | * They can also can also be added to other IO::AIO::GRP objects. |
665 | * They can also can also be added to other IO::AIO::GRP objects. |
|
|
666 | |
576 | * You must not add requests to a group from within the group callback |
667 | * You must not add requests to a group from within the group callback |
577 | (or any later time). |
668 | (or any later time). |
578 | |
669 | |
579 | Their lifetime, simplified, looks like this: when they are empty, they |
670 | Their lifetime, simplified, looks like this: when they are empty, they |
580 | will finish very quickly. If they contain only requests that are in the |
671 | will finish very quickly. If they contain only requests that are in the |
581 | "done" state, they will also finish. Otherwise they will continue to |
672 | "done" state, they will also finish. Otherwise they will continue to |
582 | exist. |
673 | exist. |
583 | |
674 | |
584 | That means after creating a group you have some time to add requests. |
675 | That means after creating a group you have some time to add requests |
585 | And in the callbacks of those requests, you can add further requests to |
676 | (precisely before the callback has been invoked, which is only done |
586 | the group. And only when all those requests have finished will the the |
677 | within the "poll_cb"). And in the callbacks of those requests, you can |
587 | group itself finish. |
678 | add further requests to the group. And only when all those requests have |
|
|
679 | finished will the the group itself finish. |
588 | |
680 | |
589 | add $grp ... |
681 | add $grp ... |
590 | $grp->add (...) |
682 | $grp->add (...) |
591 | Add one or more requests to the group. Any type of IO::AIO::REQ can |
683 | Add one or more requests to the group. Any type of IO::AIO::REQ can |
592 | be added, including other groups, as long as you do not create |
684 | be added, including other groups, as long as you do not create |
… | |
… | |
599 | request itself. Useful when you queued a lot of events but got a |
691 | request itself. Useful when you queued a lot of events but got a |
600 | result early. |
692 | result early. |
601 | |
693 | |
602 | $grp->result (...) |
694 | $grp->result (...) |
603 | Set the result value(s) that will be passed to the group callback |
695 | Set the result value(s) that will be passed to the group callback |
604 | when all subrequests have finished and set thre groups errno to the |
696 | when all subrequests have finished and set the groups errno to the |
605 | current value of errno (just like calling "errno" without an error |
697 | current value of errno (just like calling "errno" without an error |
606 | number). By default, no argument will be passed and errno is zero. |
698 | number). By default, no argument will be passed and errno is zero. |
607 | |
699 | |
608 | $grp->errno ([$errno]) |
700 | $grp->errno ([$errno]) |
609 | Sets the group errno value to $errno, or the current value of errno |
701 | Sets the group errno value to $errno, or the current value of errno |
… | |
… | |
635 | does not impose any limits). |
727 | does not impose any limits). |
636 | |
728 | |
637 | If the feed does not queue more requests when called, it will be |
729 | If the feed does not queue more requests when called, it will be |
638 | automatically removed from the group. |
730 | automatically removed from the group. |
639 | |
731 | |
640 | If the feed limit is 0, it will be set to 2 automatically. |
732 | If the feed limit is 0 when this method is called, it will be set to |
|
|
733 | 2 automatically. |
641 | |
734 | |
642 | Example: |
735 | Example: |
643 | |
736 | |
644 | # stat all files in @files, but only ever use four aio requests concurrently: |
737 | # stat all files in @files, but only ever use four aio requests concurrently: |
645 | |
738 | |
… | |
… | |
655 | limit $grp $num |
748 | limit $grp $num |
656 | Sets the feeder limit for the group: The feeder will be called |
749 | Sets the feeder limit for the group: The feeder will be called |
657 | whenever the group contains less than this many requests. |
750 | whenever the group contains less than this many requests. |
658 | |
751 | |
659 | Setting the limit to 0 will pause the feeding process. |
752 | Setting the limit to 0 will pause the feeding process. |
|
|
753 | |
|
|
754 | The default value for the limit is 0, but note that setting a feeder |
|
|
755 | automatically bumps it up to 2. |
660 | |
756 | |
661 | SUPPORT FUNCTIONS |
757 | SUPPORT FUNCTIONS |
662 | EVENT PROCESSING AND EVENT LOOP INTEGRATION |
758 | EVENT PROCESSING AND EVENT LOOP INTEGRATION |
663 | $fileno = IO::AIO::poll_fileno |
759 | $fileno = IO::AIO::poll_fileno |
664 | Return the *request result pipe file descriptor*. This filehandle |
760 | Return the *request result pipe file descriptor*. This filehandle |
… | |
… | |
668 | |
764 | |
669 | See "poll_cb" for an example. |
765 | See "poll_cb" for an example. |
670 | |
766 | |
671 | IO::AIO::poll_cb |
767 | IO::AIO::poll_cb |
672 | Process some outstanding events on the result pipe. You have to call |
768 | Process some outstanding events on the result pipe. You have to call |
673 | this regularly. Returns the number of events processed. Returns |
769 | this regularly. Returns 0 if all events could be processed, or -1 if |
674 | immediately when no events are outstanding. The amount of events |
770 | it returned earlier for whatever reason. Returns immediately when no |
|
|
771 | events are outstanding. The amount of events processed depends on |
675 | processed depends on the settings of "IO::AIO::max_poll_req" and |
772 | the settings of "IO::AIO::max_poll_req" and |
676 | "IO::AIO::max_poll_time". |
773 | "IO::AIO::max_poll_time". |
677 | |
774 | |
678 | If not all requests were processed for whatever reason, the |
775 | If not all requests were processed for whatever reason, the |
679 | filehandle will still be ready when "poll_cb" returns. |
776 | filehandle will still be ready when "poll_cb" returns, so normally |
|
|
777 | you don't have to do anything special to have it called later. |
680 | |
778 | |
681 | Example: Install an Event watcher that automatically calls |
779 | Example: Install an Event watcher that automatically calls |
682 | IO::AIO::poll_cb with high priority: |
780 | IO::AIO::poll_cb with high priority: |
683 | |
781 | |
684 | Event->io (fd => IO::AIO::poll_fileno, |
782 | Event->io (fd => IO::AIO::poll_fileno, |
… | |
… | |
790 | |
888 | |
791 | The default is probably ok in most situations, especially if thread |
889 | The default is probably ok in most situations, especially if thread |
792 | creation is fast. If thread creation is very slow on your system you |
890 | creation is fast. If thread creation is very slow on your system you |
793 | might want to use larger values. |
891 | might want to use larger values. |
794 | |
892 | |
795 | $oldmaxreqs = IO::AIO::max_outstanding $maxreqs |
893 | IO::AIO::max_outstanding $maxreqs |
796 | This is a very bad function to use in interactive programs because |
894 | This is a very bad function to use in interactive programs because |
797 | it blocks, and a bad way to reduce concurrency because it is |
895 | it blocks, and a bad way to reduce concurrency because it is |
798 | inexact: Better use an "aio_group" together with a feed callback. |
896 | inexact: Better use an "aio_group" together with a feed callback. |
799 | |
897 | |
800 | Sets the maximum number of outstanding requests to $nreqs. If you to |
898 | Sets the maximum number of outstanding requests to $nreqs. If you do |
801 | queue up more than this number of requests, the next call to the |
899 | queue up more than this number of requests, the next call to the |
802 | "poll_cb" (and "poll_some" and other functions calling "poll_cb") |
900 | "poll_cb" (and "poll_some" and other functions calling "poll_cb") |
803 | function will block until the limit is no longer exceeded. |
901 | function will block until the limit is no longer exceeded. |
804 | |
902 | |
805 | The default value is very large, so there is no practical limit on |
903 | The default value is very large, so there is no practical limit on |
806 | the number of outstanding requests. |
904 | the number of outstanding requests. |
807 | |
905 | |
808 | You can still queue as many requests as you want. Therefore, |
906 | You can still queue as many requests as you want. Therefore, |
809 | "max_oustsanding" is mainly useful in simple scripts (with low |
907 | "max_outstanding" is mainly useful in simple scripts (with low |
810 | values) or as a stop gap to shield against fatal memory overflow |
908 | values) or as a stop gap to shield against fatal memory overflow |
811 | (with large values). |
909 | (with large values). |
812 | |
910 | |
813 | STATISTICAL INFORMATION |
911 | STATISTICAL INFORMATION |
814 | IO::AIO::nreqs |
912 | IO::AIO::nreqs |
… | |
… | |
851 | bytes of memory. In addition, stat requests need a stat buffer (possibly |
949 | bytes of memory. In addition, stat requests need a stat buffer (possibly |
852 | a few hundred bytes), readdir requires a result buffer and so on. Perl |
950 | a few hundred bytes), readdir requires a result buffer and so on. Perl |
853 | scalars and other data passed into aio requests will also be locked and |
951 | scalars and other data passed into aio requests will also be locked and |
854 | will consume memory till the request has entered the done state. |
952 | will consume memory till the request has entered the done state. |
855 | |
953 | |
856 | This is now awfully much, so queuing lots of requests is not usually a |
954 | This is not awfully much, so queuing lots of requests is not usually a |
857 | problem. |
955 | problem. |
858 | |
956 | |
859 | Per-thread usage: |
957 | Per-thread usage: |
860 | |
958 | |
861 | In the execution phase, some aio requests require more memory for |
959 | In the execution phase, some aio requests require more memory for |
… | |
… | |
864 | |
962 | |
865 | KNOWN BUGS |
963 | KNOWN BUGS |
866 | Known bugs will be fixed in the next release. |
964 | Known bugs will be fixed in the next release. |
867 | |
965 | |
868 | SEE ALSO |
966 | SEE ALSO |
869 | Coro::AIO. |
967 | AnyEvent::AIO for easy integration into event loops, Coro::AIO for a |
|
|
968 | more natural syntax. |
870 | |
969 | |
871 | AUTHOR |
970 | AUTHOR |
872 | Marc Lehmann <schmorp@schmorp.de> |
971 | Marc Lehmann <schmorp@schmorp.de> |
873 | http://home.schmorp.de/ |
972 | http://home.schmorp.de/ |
874 | |
973 | |