… | |
… | |
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 | |
… | |
… | |
259 | } |
260 | } |
260 | }; |
261 | }; |
261 | |
262 | |
262 | aio_close $fh, $callback->($status) |
263 | aio_close $fh, $callback->($status) |
263 | Asynchronously close a file and call the callback with the result |
264 | Asynchronously close a file and call the callback with the result |
264 | code. *WARNING:* although accepted, you should not pass in a perl |
265 | code. |
265 | filehandle here, as perl will likely close the file descriptor |
|
|
266 | another time when the filehandle is destroyed. Normally, you can |
|
|
267 | safely call perls "close" or just let filehandles go out of scope. |
|
|
268 | |
266 | |
269 | 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 |
270 | 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. |
271 | |
277 | |
272 | aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
278 | aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
273 | aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
279 | aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
274 | Reads or writes "length" bytes from the specified "fh" and "offset" |
280 | Reads or writes $length bytes from or to the specified $fh and |
275 | into the scalar given by "data" and offset "dataoffset" and calls |
281 | $offset into the scalar given by $data and offset $dataoffset and |
276 | the callback without the actual number of bytes read (or -1 on |
282 | calls the callback without the actual number of bytes read (or -1 on |
277 | error, just like the syscall). |
283 | error, just like the syscall). |
278 | |
284 | |
|
|
285 | "aio_read" will, like "sysread", shrink or grow the $data scalar to |
|
|
286 | offset plus the actual number of bytes read. |
|
|
287 | |
|
|
288 | If $offset is undefined, then the current file descriptor offset |
|
|
289 | will be used (and updated), otherwise the file descriptor offset |
|
|
290 | will not be changed by these calls. |
|
|
291 | |
|
|
292 | If $length is undefined in "aio_write", use the remaining length of |
|
|
293 | $data. |
|
|
294 | |
|
|
295 | If $dataoffset is less than zero, it will be counted from the end of |
|
|
296 | $data. |
|
|
297 | |
279 | The $data scalar *MUST NOT* be modified in any way while the request |
298 | The $data scalar *MUST NOT* be modified in any way while the request |
280 | is outstanding. Modifying it can result in segfaults or WW3 (if the |
299 | is outstanding. Modifying it can result in segfaults or World War |
281 | necessary/optional hardware is installed). |
300 | III (if the necessary/optional hardware is installed). |
282 | |
301 | |
283 | Example: Read 15 bytes at offset 7 into scalar $buffer, starting at |
302 | Example: Read 15 bytes at offset 7 into scalar $buffer, starting at |
284 | offset 0 within the scalar: |
303 | offset 0 within the scalar: |
285 | |
304 | |
286 | aio_read $fh, 7, 15, $buffer, 0, sub { |
305 | aio_read $fh, 7, 15, $buffer, 0, sub { |
… | |
… | |
344 | aio_stat "/etc/passwd", sub { |
363 | aio_stat "/etc/passwd", sub { |
345 | $_[0] and die "stat failed: $!"; |
364 | $_[0] and die "stat failed: $!"; |
346 | print "size is ", -s _, "\n"; |
365 | print "size is ", -s _, "\n"; |
347 | }; |
366 | }; |
348 | |
367 | |
|
|
368 | aio_utime $fh_or_path, $atime, $mtime, $callback->($status) |
|
|
369 | Works like perl's "utime" function (including the special case of |
|
|
370 | $atime and $mtime being undef). Fractional times are supported if |
|
|
371 | the underlying syscalls support them. |
|
|
372 | |
|
|
373 | When called with a pathname, uses utimes(2) if available, otherwise |
|
|
374 | utime(2). If called on a file descriptor, uses futimes(2) if |
|
|
375 | available, otherwise returns ENOSYS, so this is not portable. |
|
|
376 | |
|
|
377 | Examples: |
|
|
378 | |
|
|
379 | # set atime and mtime to current time (basically touch(1)): |
|
|
380 | aio_utime "path", undef, undef; |
|
|
381 | # set atime to current time and mtime to beginning of the epoch: |
|
|
382 | aio_utime "path", time, undef; # undef==0 |
|
|
383 | |
|
|
384 | aio_chown $fh_or_path, $uid, $gid, $callback->($status) |
|
|
385 | Works like perl's "chown" function, except that "undef" for either |
|
|
386 | $uid or $gid is being interpreted as "do not change" (but -1 can |
|
|
387 | also be used). |
|
|
388 | |
|
|
389 | Examples: |
|
|
390 | |
|
|
391 | # same as "chown root path" in the shell: |
|
|
392 | aio_chown "path", 0, -1; |
|
|
393 | # same as above: |
|
|
394 | aio_chown "path", 0, undef; |
|
|
395 | |
|
|
396 | aio_truncate $fh_or_path, $offset, $callback->($status) |
|
|
397 | Works like truncate(2) or ftruncate(2). |
|
|
398 | |
|
|
399 | aio_chmod $fh_or_path, $mode, $callback->($status) |
|
|
400 | Works like perl's "chmod" function. |
|
|
401 | |
349 | aio_unlink $pathname, $callback->($status) |
402 | aio_unlink $pathname, $callback->($status) |
350 | Asynchronously unlink (delete) a file and call the callback with the |
403 | Asynchronously unlink (delete) a file and call the callback with the |
351 | result code. |
404 | result code. |
352 | |
405 | |
353 | aio_mknod $path, $mode, $dev, $callback->($status) |
406 | aio_mknod $path, $mode, $dev, $callback->($status) |
… | |
… | |
389 | aio_readdir $pathname, $callback->($entries) |
442 | aio_readdir $pathname, $callback->($entries) |
390 | Unlike the POSIX call of the same name, "aio_readdir" reads an |
443 | Unlike the POSIX call of the same name, "aio_readdir" reads an |
391 | entire directory (i.e. opendir + readdir + closedir). The entries |
444 | entire directory (i.e. opendir + readdir + closedir). The entries |
392 | will not be sorted, and will NOT include the "." and ".." entries. |
445 | will not be sorted, and will NOT include the "." and ".." entries. |
393 | |
446 | |
394 | The callback a single argument which is either "undef" or an |
447 | The callback is passed a single argument which is either "undef" or |
395 | array-ref with the filenames. |
448 | an array-ref with the filenames. |
|
|
449 | |
|
|
450 | aio_readdirx $pathname, $flags, $callback->($entries, $flags) |
|
|
451 | Quite similar to "aio_readdir", but the $flags argument allows to |
|
|
452 | tune behaviour and output format. In case of an error, $entries will |
|
|
453 | be "undef". |
|
|
454 | |
|
|
455 | The flags are a combination of the following constants, ORed |
|
|
456 | together (the flags will also be passed to the callback, possibly |
|
|
457 | modified): |
|
|
458 | |
|
|
459 | IO::AIO::READDIR_DENTS |
|
|
460 | When this flag is off, then the callback gets an arrayref with |
|
|
461 | of names only (as with "aio_readdir"), otherwise it gets an |
|
|
462 | arrayref with "[$name, $type, $inode]" arrayrefs, each |
|
|
463 | describing a single directory entry in more detail. |
|
|
464 | |
|
|
465 | $name is the name of the entry. |
|
|
466 | |
|
|
467 | $type is one of the "IO::AIO::DT_xxx" constants: |
|
|
468 | |
|
|
469 | "IO::AIO::DT_UNKNOWN", "IO::AIO::DT_FIFO", "IO::AIO::DT_CHR", |
|
|
470 | "IO::AIO::DT_DIR", "IO::AIO::DT_BLK", "IO::AIO::DT_REG", |
|
|
471 | "IO::AIO::DT_LNK", "IO::AIO::DT_SOCK", "IO::AIO::DT_WHT". |
|
|
472 | |
|
|
473 | "IO::AIO::DT_UNKNOWN" means just that: readdir does not know. If |
|
|
474 | you need to know, you have to run stat yourself. Also, for speed |
|
|
475 | reasons, the $type scalars are read-only: you can not modify |
|
|
476 | them. |
|
|
477 | |
|
|
478 | $inode is the inode number (which might not be exact on systems |
|
|
479 | with 64 bit inode numbers and 32 bit perls). On systems that do |
|
|
480 | not deliver the inode information, this will always be zero. |
|
|
481 | |
|
|
482 | IO::AIO::READDIR_DIRS_FIRST |
|
|
483 | When this flag is set, then the names will be returned in an |
|
|
484 | order where likely directories come first. This is useful when |
|
|
485 | you need to quickly find directories, or you want to find all |
|
|
486 | directories while avoiding to stat() each entry. |
|
|
487 | |
|
|
488 | If the system returns type information in readdir, then this is |
|
|
489 | used to find directories directly. Otherwise, likely directories |
|
|
490 | are files beginning with ".", or otherwise files with no dots, |
|
|
491 | of which files with short names are tried first. |
|
|
492 | |
|
|
493 | IO::AIO::READDIR_STAT_ORDER |
|
|
494 | When this flag is set, then the names will be returned in an |
|
|
495 | order suitable for stat()'ing each one. That is, when you plan |
|
|
496 | to stat() all files in the given directory, then the returned |
|
|
497 | order will likely be fastest. |
|
|
498 | |
|
|
499 | If both this flag and "IO::AIO::READDIR_DIRS_FIRST" are |
|
|
500 | specified, then the likely dirs come first, resulting in a less |
|
|
501 | optimal stat order. |
|
|
502 | |
|
|
503 | IO::AIO::READDIR_FOUND_UNKNOWN |
|
|
504 | This flag should not be set when calling "aio_readdirx". |
|
|
505 | Instead, it is being set by "aio_readdirx", when any of the |
|
|
506 | $type's found were "IO::AIO::DT_UNKNOWN". The absense of this |
|
|
507 | flag therefore indicates that all $type's are known, which can |
|
|
508 | be used to speed up some algorithms. |
396 | |
509 | |
397 | aio_load $path, $data, $callback->($status) |
510 | aio_load $path, $data, $callback->($status) |
398 | This is a composite request that tries to fully load the given file |
511 | This is a composite request that tries to fully load the given file |
399 | into memory. Status is the same as with aio_read. |
512 | into memory. Status is the same as with aio_read. |
400 | |
513 | |
401 | aio_copy $srcpath, $dstpath, $callback->($status) |
514 | aio_copy $srcpath, $dstpath, $callback->($status) |
402 | Try to copy the *file* (directories not supported as either source |
515 | Try to copy the *file* (directories not supported as either source |
403 | or destination) from $srcpath to $dstpath and call the callback with |
516 | or destination) from $srcpath to $dstpath and call the callback with |
404 | the 0 (error) or -1 ok. |
517 | the 0 (error) or -1 ok. |
405 | |
518 | |
406 | This is a composite request that it creates the destination file |
519 | This is a composite request that creates the destination file with |
407 | with mode 0200 and copies the contents of the source file into it |
520 | mode 0200 and copies the contents of the source file into it using |
408 | using "aio_sendfile", followed by restoring atime, mtime, access |
521 | "aio_sendfile", followed by restoring atime, mtime, access mode and |
409 | mode and uid/gid, in that order. |
522 | uid/gid, in that order. |
410 | |
523 | |
411 | If an error occurs, the partial destination file will be unlinked, |
524 | If an error occurs, the partial destination file will be unlinked, |
412 | if possible, except when setting atime, mtime, access mode and |
525 | if possible, except when setting atime, mtime, access mode and |
413 | uid/gid, where errors are being ignored. |
526 | uid/gid, where errors are being ignored. |
414 | |
527 | |
415 | aio_move $srcpath, $dstpath, $callback->($status) |
528 | aio_move $srcpath, $dstpath, $callback->($status) |
416 | Try to move the *file* (directories not supported as either source |
529 | Try to move the *file* (directories not supported as either source |
417 | or destination) from $srcpath to $dstpath and call the callback with |
530 | or destination) from $srcpath to $dstpath and call the callback with |
418 | the 0 (error) or -1 ok. |
531 | the 0 (error) or -1 ok. |
419 | |
532 | |
420 | This is a composite request that tries to rename(2) the file first. |
533 | This is a composite request that tries to rename(2) the file first; |
421 | If rename files with "EXDEV", it copies the file with "aio_copy" |
534 | if rename fails with "EXDEV", it copies the file with "aio_copy" |
422 | and, if that is successful, unlinking the $srcpath. |
535 | and, if that is successful, unlinks the $srcpath. |
423 | |
536 | |
424 | aio_scandir $path, $maxreq, $callback->($dirs, $nondirs) |
537 | aio_scandir $path, $maxreq, $callback->($dirs, $nondirs) |
425 | Scans a directory (similar to "aio_readdir") but additionally tries |
538 | Scans a directory (similar to "aio_readdir") but additionally tries |
426 | to efficiently separate the entries of directory $path into two sets |
539 | to efficiently separate the entries of directory $path into two sets |
427 | of names, directories you can recurse into (directories), and ones |
540 | of names, directories you can recurse into (directories), and ones |
… | |
… | |
447 | Implementation notes. |
560 | Implementation notes. |
448 | |
561 | |
449 | The "aio_readdir" cannot be avoided, but "stat()"'ing every entry |
562 | The "aio_readdir" cannot be avoided, but "stat()"'ing every entry |
450 | can. |
563 | can. |
451 | |
564 | |
|
|
565 | If readdir returns file type information, then this is used directly |
|
|
566 | to find directories. |
|
|
567 | |
452 | After reading the directory, the modification time, size etc. of the |
568 | Otherwise, after reading the directory, the modification time, size |
453 | directory before and after the readdir is checked, and if they match |
569 | etc. of the directory before and after the readdir is checked, and |
454 | (and isn't the current time), the link count will be used to decide |
570 | if they match (and isn't the current time), the link count will be |
455 | how many entries are directories (if >= 2). Otherwise, no knowledge |
571 | used to decide how many entries are directories (if >= 2). |
456 | of the number of subdirectories will be assumed. |
572 | Otherwise, no knowledge of the number of subdirectories will be |
|
|
573 | assumed. |
457 | |
574 | |
458 | Then entries will be sorted into likely directories (everything |
575 | Then entries will be sorted into likely directories a non-initial |
459 | without a non-initial dot currently) and likely non-directories |
576 | dot currently) and likely non-directories (see "aio_readdirx"). Then |
460 | (everything else). Then every entry plus an appended "/." will be |
577 | every entry plus an appended "/." will be "stat"'ed, likely |
461 | "stat"'ed, likely directories first. If that succeeds, it assumes |
578 | directories first, in order of their inode numbers. If that |
462 | that the entry is a directory or a symlink to directory (which will |
579 | succeeds, it assumes that the entry is a directory or a symlink to |
463 | be checked seperately). This is often faster than stat'ing the entry |
580 | directory (which will be checked seperately). This is often faster |
464 | itself because filesystems might detect the type of the entry |
581 | than stat'ing the entry itself because filesystems might detect the |
465 | without reading the inode data (e.g. ext2fs filetype feature). |
582 | type of the entry without reading the inode data (e.g. ext2fs |
|
|
583 | filetype feature), even on systems that cannot return the filetype |
|
|
584 | information on readdir. |
466 | |
585 | |
467 | If the known number of directories (link count - 2) has been |
586 | If the known number of directories (link count - 2) has been |
468 | reached, the rest of the entries is assumed to be non-directories. |
587 | reached, the rest of the entries is assumed to be non-directories. |
469 | |
588 | |
470 | This only works with certainty on POSIX (= UNIX) filesystems, which |
589 | This only works with certainty on POSIX (= UNIX) filesystems, which |
… | |
… | |
478 | Delete a directory tree starting (and including) $path, return the |
597 | Delete a directory tree starting (and including) $path, return the |
479 | status of the final "rmdir" only. This is a composite request that |
598 | status of the final "rmdir" only. This is a composite request that |
480 | uses "aio_scandir" to recurse into and rmdir directories, and unlink |
599 | uses "aio_scandir" to recurse into and rmdir directories, and unlink |
481 | everything else. |
600 | everything else. |
482 | |
601 | |
|
|
602 | aio_sync $callback->($status) |
|
|
603 | Asynchronously call sync and call the callback when finished. |
|
|
604 | |
483 | aio_fsync $fh, $callback->($status) |
605 | aio_fsync $fh, $callback->($status) |
484 | Asynchronously call fsync on the given filehandle and call the |
606 | Asynchronously call fsync on the given filehandle and call the |
485 | callback with the fsync result code. |
607 | callback with the fsync result code. |
486 | |
608 | |
487 | aio_fdatasync $fh, $callback->($status) |
609 | aio_fdatasync $fh, $callback->($status) |
488 | Asynchronously call fdatasync on the given filehandle and call the |
610 | Asynchronously call fdatasync on the given filehandle and call the |
489 | callback with the fdatasync result code. |
611 | callback with the fdatasync result code. |
490 | |
612 | |
491 | If this call isn't available because your OS lacks it or it couldn't |
613 | If this call isn't available because your OS lacks it or it couldn't |
492 | be detected, it will be emulated by calling "fsync" instead. |
614 | be detected, it will be emulated by calling "fsync" instead. |
|
|
615 | |
|
|
616 | aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status) |
|
|
617 | Sync the data portion of the file specified by $offset and $length |
|
|
618 | to disk (but NOT the metadata), by calling the Linux-specific |
|
|
619 | sync_file_range call. If sync_file_range is not available or it |
|
|
620 | returns ENOSYS, then fdatasync or fsync is being substituted. |
|
|
621 | |
|
|
622 | $flags can be a combination of |
|
|
623 | "IO::AIO::SYNC_FILE_RANGE_WAIT_BEFORE", |
|
|
624 | "IO::AIO::SYNC_FILE_RANGE_WRITE" and |
|
|
625 | "IO::AIO::SYNC_FILE_RANGE_WAIT_AFTER": refer to the sync_file_range |
|
|
626 | manpage for details. |
|
|
627 | |
|
|
628 | aio_pathsync $path, $callback->($status) |
|
|
629 | This request tries to open, fsync and close the given path. This is |
|
|
630 | a composite request intended to sync directories after directory |
|
|
631 | operations (E.g. rename). This might not work on all operating |
|
|
632 | systems or have any specific effect, but usually it makes sure that |
|
|
633 | directory changes get written to disc. It works for anything that |
|
|
634 | can be opened for read-only, not just directories. |
|
|
635 | |
|
|
636 | Passes 0 when everything went ok, and -1 on error. |
493 | |
637 | |
494 | aio_group $callback->(...) |
638 | aio_group $callback->(...) |
495 | This is a very special aio request: Instead of doing something, it |
639 | This is a very special aio request: Instead of doing something, it |
496 | is a container for other aio requests, which is useful if you want |
640 | is a container for other aio requests, which is useful if you want |
497 | to bundle many requests into a single, composite, request with a |
641 | to bundle many requests into a single, composite, request with a |
… | |
… | |
579 | }; |
723 | }; |
580 | |
724 | |
581 | This makes it very easy to create composite requests (see the source of |
725 | This makes it very easy to create composite requests (see the source of |
582 | "aio_move" for an application) that work and feel like simple requests. |
726 | "aio_move" for an application) that work and feel like simple requests. |
583 | |
727 | |
584 | * The IO::AIO::GRP objects will be cleaned up during calls to |
728 | * The IO::AIO::GRP objects will be cleaned up during calls to |
585 | "IO::AIO::poll_cb", just like any other request. |
729 | "IO::AIO::poll_cb", just like any other request. |
|
|
730 | |
586 | * They can be canceled like any other request. Canceling will cancel not |
731 | * They can be canceled like any other request. Canceling will cancel |
587 | only the request itself, but also all requests it contains. |
732 | not only the request itself, but also all requests it contains. |
|
|
733 | |
588 | * They can also can also be added to other IO::AIO::GRP objects. |
734 | * They can also can also be added to other IO::AIO::GRP objects. |
|
|
735 | |
589 | * You must not add requests to a group from within the group callback |
736 | * You must not add requests to a group from within the group callback |
590 | (or any later time). |
737 | (or any later time). |
591 | |
738 | |
592 | Their lifetime, simplified, looks like this: when they are empty, they |
739 | Their lifetime, simplified, looks like this: when they are empty, they |
593 | will finish very quickly. If they contain only requests that are in the |
740 | will finish very quickly. If they contain only requests that are in the |
594 | "done" state, they will also finish. Otherwise they will continue to |
741 | "done" state, they will also finish. Otherwise they will continue to |
595 | exist. |
742 | exist. |
596 | |
743 | |
597 | That means after creating a group you have some time to add requests. |
744 | That means after creating a group you have some time to add requests |
598 | And in the callbacks of those requests, you can add further requests to |
745 | (precisely before the callback has been invoked, which is only done |
599 | the group. And only when all those requests have finished will the the |
746 | within the "poll_cb"). And in the callbacks of those requests, you can |
600 | group itself finish. |
747 | add further requests to the group. And only when all those requests have |
|
|
748 | finished will the the group itself finish. |
601 | |
749 | |
602 | add $grp ... |
750 | add $grp ... |
603 | $grp->add (...) |
751 | $grp->add (...) |
604 | Add one or more requests to the group. Any type of IO::AIO::REQ can |
752 | Add one or more requests to the group. Any type of IO::AIO::REQ can |
605 | be added, including other groups, as long as you do not create |
753 | be added, including other groups, as long as you do not create |
… | |
… | |
612 | request itself. Useful when you queued a lot of events but got a |
760 | request itself. Useful when you queued a lot of events but got a |
613 | result early. |
761 | result early. |
614 | |
762 | |
615 | $grp->result (...) |
763 | $grp->result (...) |
616 | Set the result value(s) that will be passed to the group callback |
764 | Set the result value(s) that will be passed to the group callback |
617 | when all subrequests have finished and set thre groups errno to the |
765 | when all subrequests have finished and set the groups errno to the |
618 | current value of errno (just like calling "errno" without an error |
766 | current value of errno (just like calling "errno" without an error |
619 | number). By default, no argument will be passed and errno is zero. |
767 | number). By default, no argument will be passed and errno is zero. |
620 | |
768 | |
621 | $grp->errno ([$errno]) |
769 | $grp->errno ([$errno]) |
622 | Sets the group errno value to $errno, or the current value of errno |
770 | Sets the group errno value to $errno, or the current value of errno |
… | |
… | |
648 | does not impose any limits). |
796 | does not impose any limits). |
649 | |
797 | |
650 | If the feed does not queue more requests when called, it will be |
798 | If the feed does not queue more requests when called, it will be |
651 | automatically removed from the group. |
799 | automatically removed from the group. |
652 | |
800 | |
653 | If the feed limit is 0, it will be set to 2 automatically. |
801 | If the feed limit is 0 when this method is called, it will be set to |
|
|
802 | 2 automatically. |
654 | |
803 | |
655 | Example: |
804 | Example: |
656 | |
805 | |
657 | # stat all files in @files, but only ever use four aio requests concurrently: |
806 | # stat all files in @files, but only ever use four aio requests concurrently: |
658 | |
807 | |
… | |
… | |
668 | limit $grp $num |
817 | limit $grp $num |
669 | Sets the feeder limit for the group: The feeder will be called |
818 | Sets the feeder limit for the group: The feeder will be called |
670 | whenever the group contains less than this many requests. |
819 | whenever the group contains less than this many requests. |
671 | |
820 | |
672 | Setting the limit to 0 will pause the feeding process. |
821 | Setting the limit to 0 will pause the feeding process. |
|
|
822 | |
|
|
823 | The default value for the limit is 0, but note that setting a feeder |
|
|
824 | automatically bumps it up to 2. |
673 | |
825 | |
674 | SUPPORT FUNCTIONS |
826 | SUPPORT FUNCTIONS |
675 | EVENT PROCESSING AND EVENT LOOP INTEGRATION |
827 | EVENT PROCESSING AND EVENT LOOP INTEGRATION |
676 | $fileno = IO::AIO::poll_fileno |
828 | $fileno = IO::AIO::poll_fileno |
677 | Return the *request result pipe file descriptor*. This filehandle |
829 | Return the *request result pipe file descriptor*. This filehandle |
… | |
… | |
681 | |
833 | |
682 | See "poll_cb" for an example. |
834 | See "poll_cb" for an example. |
683 | |
835 | |
684 | IO::AIO::poll_cb |
836 | IO::AIO::poll_cb |
685 | Process some outstanding events on the result pipe. You have to call |
837 | Process some outstanding events on the result pipe. You have to call |
686 | this regularly. Returns the number of events processed. Returns |
838 | this regularly. Returns 0 if all events could be processed, or -1 if |
687 | immediately when no events are outstanding. The amount of events |
839 | it returned earlier for whatever reason. Returns immediately when no |
|
|
840 | events are outstanding. The amount of events processed depends on |
688 | processed depends on the settings of "IO::AIO::max_poll_req" and |
841 | the settings of "IO::AIO::max_poll_req" and |
689 | "IO::AIO::max_poll_time". |
842 | "IO::AIO::max_poll_time". |
690 | |
843 | |
691 | If not all requests were processed for whatever reason, the |
844 | If not all requests were processed for whatever reason, the |
692 | filehandle will still be ready when "poll_cb" returns. |
845 | filehandle will still be ready when "poll_cb" returns, so normally |
|
|
846 | you don't have to do anything special to have it called later. |
693 | |
847 | |
694 | Example: Install an Event watcher that automatically calls |
848 | Example: Install an Event watcher that automatically calls |
695 | IO::AIO::poll_cb with high priority: |
849 | IO::AIO::poll_cb with high priority: |
696 | |
850 | |
697 | Event->io (fd => IO::AIO::poll_fileno, |
851 | Event->io (fd => IO::AIO::poll_fileno, |
… | |
… | |
803 | |
957 | |
804 | The default is probably ok in most situations, especially if thread |
958 | The default is probably ok in most situations, especially if thread |
805 | creation is fast. If thread creation is very slow on your system you |
959 | creation is fast. If thread creation is very slow on your system you |
806 | might want to use larger values. |
960 | might want to use larger values. |
807 | |
961 | |
808 | $oldmaxreqs = IO::AIO::max_outstanding $maxreqs |
962 | IO::AIO::max_outstanding $maxreqs |
809 | This is a very bad function to use in interactive programs because |
963 | This is a very bad function to use in interactive programs because |
810 | it blocks, and a bad way to reduce concurrency because it is |
964 | it blocks, and a bad way to reduce concurrency because it is |
811 | inexact: Better use an "aio_group" together with a feed callback. |
965 | inexact: Better use an "aio_group" together with a feed callback. |
812 | |
966 | |
813 | Sets the maximum number of outstanding requests to $nreqs. If you to |
967 | Sets the maximum number of outstanding requests to $nreqs. If you do |
814 | queue up more than this number of requests, the next call to the |
968 | queue up more than this number of requests, the next call to the |
815 | "poll_cb" (and "poll_some" and other functions calling "poll_cb") |
969 | "poll_cb" (and "poll_some" and other functions calling "poll_cb") |
816 | function will block until the limit is no longer exceeded. |
970 | function will block until the limit is no longer exceeded. |
817 | |
971 | |
818 | The default value is very large, so there is no practical limit on |
972 | The default value is very large, so there is no practical limit on |
819 | the number of outstanding requests. |
973 | the number of outstanding requests. |
820 | |
974 | |
821 | You can still queue as many requests as you want. Therefore, |
975 | You can still queue as many requests as you want. Therefore, |
822 | "max_oustsanding" is mainly useful in simple scripts (with low |
976 | "max_outstanding" is mainly useful in simple scripts (with low |
823 | values) or as a stop gap to shield against fatal memory overflow |
977 | values) or as a stop gap to shield against fatal memory overflow |
824 | (with large values). |
978 | (with large values). |
825 | |
979 | |
826 | STATISTICAL INFORMATION |
980 | STATISTICAL INFORMATION |
827 | IO::AIO::nreqs |
981 | IO::AIO::nreqs |
… | |
… | |
864 | bytes of memory. In addition, stat requests need a stat buffer (possibly |
1018 | bytes of memory. In addition, stat requests need a stat buffer (possibly |
865 | a few hundred bytes), readdir requires a result buffer and so on. Perl |
1019 | a few hundred bytes), readdir requires a result buffer and so on. Perl |
866 | scalars and other data passed into aio requests will also be locked and |
1020 | scalars and other data passed into aio requests will also be locked and |
867 | will consume memory till the request has entered the done state. |
1021 | will consume memory till the request has entered the done state. |
868 | |
1022 | |
869 | This is now awfully much, so queuing lots of requests is not usually a |
1023 | This is not awfully much, so queuing lots of requests is not usually a |
870 | problem. |
1024 | problem. |
871 | |
1025 | |
872 | Per-thread usage: |
1026 | Per-thread usage: |
873 | |
1027 | |
874 | In the execution phase, some aio requests require more memory for |
1028 | In the execution phase, some aio requests require more memory for |
… | |
… | |
877 | |
1031 | |
878 | KNOWN BUGS |
1032 | KNOWN BUGS |
879 | Known bugs will be fixed in the next release. |
1033 | Known bugs will be fixed in the next release. |
880 | |
1034 | |
881 | SEE ALSO |
1035 | SEE ALSO |
882 | Coro::AIO. |
1036 | AnyEvent::AIO for easy integration into event loops, Coro::AIO for a |
|
|
1037 | more natural syntax. |
883 | |
1038 | |
884 | AUTHOR |
1039 | AUTHOR |
885 | Marc Lehmann <schmorp@schmorp.de> |
1040 | Marc Lehmann <schmorp@schmorp.de> |
886 | http://home.schmorp.de/ |
1041 | http://home.schmorp.de/ |
887 | |
1042 | |