… | |
… | |
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 | |
… | |
… | |
23 | $req->cancel; # cancel request if still in queue |
24 | $req->cancel; # cancel request if still in queue |
24 | |
25 | |
25 | my $grp = aio_group sub { print "all stats done\n" }; |
26 | my $grp = aio_group sub { print "all stats done\n" }; |
26 | add $grp aio_stat "..." for ...; |
27 | add $grp aio_stat "..." for ...; |
27 | |
28 | |
28 | # AnyEvent integration |
29 | # AnyEvent integration (EV, Event, Glib, Tk, urxvt, pureperl...) |
29 | open my $fh, "<&=" . IO::AIO::poll_fileno or die "$!"; |
30 | open my $fh, "<&=" . IO::AIO::poll_fileno or die "$!"; |
30 | my $w = AnyEvent->io (fh => $fh, poll => 'r', cb => sub { IO::AIO::poll_cb }); |
31 | my $w = AnyEvent->io (fh => $fh, poll => 'r', cb => sub { IO::AIO::poll_cb }); |
|
|
32 | |
|
|
33 | # EV integration |
|
|
34 | my $w = EV::io IO::AIO::poll_fileno, EV::READ, \&IO::AIO::poll_cb; |
31 | |
35 | |
32 | # Event integration |
36 | # Event integration |
33 | Event->io (fd => IO::AIO::poll_fileno, |
37 | Event->io (fd => IO::AIO::poll_fileno, |
34 | poll => 'r', |
38 | poll => 'r', |
35 | cb => \&IO::AIO::poll_cb); |
39 | cb => \&IO::AIO::poll_cb); |
… | |
… | |
60 | faster on a RAID volume or over NFS when you do a number of stat |
64 | faster on a RAID volume or over NFS when you do a number of stat |
61 | operations concurrently. |
65 | operations concurrently. |
62 | |
66 | |
63 | While most of this works on all types of file descriptors (for example |
67 | While most of this works on all types of file descriptors (for example |
64 | sockets), using these functions on file descriptors that support |
68 | sockets), using these functions on file descriptors that support |
65 | nonblocking operation (again, sockets, pipes etc.) is very inefficient |
69 | 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 |
70 | Use an event loop for that (such as the Event module): IO::AIO will |
68 | into such an event loop itself. |
71 | naturally fit into such an event loop itself. |
69 | |
72 | |
70 | In this version, a number of threads are started that execute your |
73 | 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 |
74 | 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 |
75 | 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 |
76 | 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 |
78 | 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 |
79 | files currently, for example), and they would only support aio_read and |
77 | aio_write, so the remaining functionality would have to be implemented |
80 | aio_write, so the remaining functionality would have to be implemented |
78 | using threads anyway. |
81 | using threads anyway. |
79 | |
82 | |
80 | Although the module will work with in the presence of other (Perl-) |
83 | 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 |
84 | 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 |
85 | yourself, always call "poll_cb" from within the same thread, or never |
83 | never call "poll_cb" (or other "aio_" functions) recursively. |
86 | call "poll_cb" (or other "aio_" functions) recursively. |
84 | |
87 | |
85 | EXAMPLE |
88 | EXAMPLE |
86 | This is a simple example that uses the Event module and loads |
89 | This is a simple example that uses the Event module and loads |
87 | /etc/passwd asynchronously: |
90 | /etc/passwd asynchronously: |
88 | |
91 | |
… | |
… | |
95 | poll => 'r', |
98 | poll => 'r', |
96 | cb => \&IO::AIO::poll_cb); |
99 | cb => \&IO::AIO::poll_cb); |
97 | |
100 | |
98 | # queue the request to open /etc/passwd |
101 | # queue the request to open /etc/passwd |
99 | aio_open "/etc/passwd", O_RDONLY, 0, sub { |
102 | aio_open "/etc/passwd", O_RDONLY, 0, sub { |
100 | my $fh = $_[0] |
103 | my $fh = shift |
101 | or die "error while opening: $!"; |
104 | or die "error while opening: $!"; |
102 | |
105 | |
103 | # stat'ing filehandles is generally non-blocking |
106 | # stat'ing filehandles is generally non-blocking |
104 | my $size = -s $fh; |
107 | my $size = -s $fh; |
105 | |
108 | |
… | |
… | |
241 | They are the same as used by "sysopen". |
244 | They are the same as used by "sysopen". |
242 | |
245 | |
243 | Likewise, $mode specifies the mode of the newly created file, if it |
246 | 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 |
247 | 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 |
248 | "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). |
249 | create new files, and 0666 or 0777 if you do). Note that the $mode |
|
|
250 | will be modified by the umask in effect then the request is being |
|
|
251 | executed, so better never change the umask. |
247 | |
252 | |
248 | Example: |
253 | Example: |
249 | |
254 | |
250 | aio_open "/etc/passwd", O_RDONLY, 0, sub { |
255 | aio_open "/etc/passwd", O_RDONLY, 0, sub { |
251 | if ($_[0]) { |
256 | if ($_[0]) { |
… | |
… | |
256 | } |
261 | } |
257 | }; |
262 | }; |
258 | |
263 | |
259 | aio_close $fh, $callback->($status) |
264 | aio_close $fh, $callback->($status) |
260 | Asynchronously close a file and call the callback with the result |
265 | Asynchronously close a file and call the callback with the result |
261 | code. *WARNING:* although accepted, you should not pass in a perl |
266 | 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 | |
267 | |
266 | This is supposed to be a bug in the API, so that might change. It's |
268 | Unfortunately, you can't do this to perl. Perl *insists* very |
267 | therefore best to avoid this function. |
269 | strongly on closing the file descriptor associated with the |
|
|
270 | filehandle itself. Here is what aio_close will try: |
|
|
271 | |
|
|
272 | 1. dup()licate the fd |
|
|
273 | 2. asynchronously close() the duplicated fd |
|
|
274 | 3. dup()licate the fd once more |
|
|
275 | 4. let perl close() the filehandle |
|
|
276 | 5. asynchronously close the duplicated fd |
|
|
277 | |
|
|
278 | The idea is that the first close() flushes stuff to disk that |
|
|
279 | closing an fd will flush, so when perl closes the fd, nothing much |
|
|
280 | will need to be flushed. The second async. close() will then flush |
|
|
281 | stuff to disk that closing the last fd to the file will flush. |
|
|
282 | |
|
|
283 | Just FYI, SuSv3 has this to say on close: |
|
|
284 | |
|
|
285 | All outstanding record locks owned by the process on the file |
|
|
286 | associated with the file descriptor shall be removed. |
|
|
287 | |
|
|
288 | If fildes refers to a socket, close() shall cause the socket to be |
|
|
289 | destroyed. ... close() shall block for up to the current linger |
|
|
290 | interval until all data is transmitted. |
|
|
291 | [this actually sounds like a specification bug, but who knows] |
|
|
292 | |
|
|
293 | And at least Linux additionally actually flushes stuff on every |
|
|
294 | close, even when the file itself is still open. |
|
|
295 | |
|
|
296 | Sounds enourmously inefficient and complicated? Yes... please show |
|
|
297 | me how to nuke perl's fd out of existence... |
268 | |
298 | |
269 | aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
299 | aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
270 | aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
300 | aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
271 | Reads or writes "length" bytes from the specified "fh" and "offset" |
301 | Reads or writes $length bytes from the specified $fh and $offset |
272 | into the scalar given by "data" and offset "dataoffset" and calls |
302 | 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 |
303 | callback without the actual number of bytes read (or -1 on error, |
274 | error, just like the syscall). |
304 | just like the syscall). |
|
|
305 | |
|
|
306 | If $offset is undefined, then the current file descriptor offset |
|
|
307 | will be used (and updated), otherwise the file descriptor offset |
|
|
308 | will not be changed by these calls. |
|
|
309 | |
|
|
310 | If $length is undefined in "aio_write", use the remaining length of |
|
|
311 | $data. |
|
|
312 | |
|
|
313 | If $dataoffset is less than zero, it will be counted from the end of |
|
|
314 | $data. |
275 | |
315 | |
276 | The $data scalar *MUST NOT* be modified in any way while the request |
316 | 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 |
317 | is outstanding. Modifying it can result in segfaults or World War |
278 | necessary/optional hardware is installed). |
318 | III (if the necessary/optional hardware is installed). |
279 | |
319 | |
280 | Example: Read 15 bytes at offset 7 into scalar $buffer, starting at |
320 | Example: Read 15 bytes at offset 7 into scalar $buffer, starting at |
281 | offset 0 within the scalar: |
321 | offset 0 within the scalar: |
282 | |
322 | |
283 | aio_read $fh, 7, 15, $buffer, 0, sub { |
323 | aio_read $fh, 7, 15, $buffer, 0, sub { |
… | |
… | |
341 | aio_stat "/etc/passwd", sub { |
381 | aio_stat "/etc/passwd", sub { |
342 | $_[0] and die "stat failed: $!"; |
382 | $_[0] and die "stat failed: $!"; |
343 | print "size is ", -s _, "\n"; |
383 | print "size is ", -s _, "\n"; |
344 | }; |
384 | }; |
345 | |
385 | |
|
|
386 | aio_utime $fh_or_path, $atime, $mtime, $callback->($status) |
|
|
387 | Works like perl's "utime" function (including the special case of |
|
|
388 | $atime and $mtime being undef). Fractional times are supported if |
|
|
389 | the underlying syscalls support them. |
|
|
390 | |
|
|
391 | When called with a pathname, uses utimes(2) if available, otherwise |
|
|
392 | utime(2). If called on a file descriptor, uses futimes(2) if |
|
|
393 | available, otherwise returns ENOSYS, so this is not portable. |
|
|
394 | |
|
|
395 | Examples: |
|
|
396 | |
|
|
397 | # set atime and mtime to current time (basically touch(1)): |
|
|
398 | aio_utime "path", undef, undef; |
|
|
399 | # set atime to current time and mtime to beginning of the epoch: |
|
|
400 | aio_utime "path", time, undef; # undef==0 |
|
|
401 | |
|
|
402 | aio_chown $fh_or_path, $uid, $gid, $callback->($status) |
|
|
403 | Works like perl's "chown" function, except that "undef" for either |
|
|
404 | $uid or $gid is being interpreted as "do not change" (but -1 can |
|
|
405 | also be used). |
|
|
406 | |
|
|
407 | Examples: |
|
|
408 | |
|
|
409 | # same as "chown root path" in the shell: |
|
|
410 | aio_chown "path", 0, -1; |
|
|
411 | # same as above: |
|
|
412 | aio_chown "path", 0, undef; |
|
|
413 | |
|
|
414 | aio_truncate $fh_or_path, $offset, $callback->($status) |
|
|
415 | Works like truncate(2) or ftruncate(2). |
|
|
416 | |
|
|
417 | aio_chmod $fh_or_path, $mode, $callback->($status) |
|
|
418 | Works like perl's "chmod" function. |
|
|
419 | |
346 | aio_unlink $pathname, $callback->($status) |
420 | aio_unlink $pathname, $callback->($status) |
347 | Asynchronously unlink (delete) a file and call the callback with the |
421 | Asynchronously unlink (delete) a file and call the callback with the |
348 | result code. |
422 | result code. |
349 | |
423 | |
350 | aio_mknod $path, $mode, $dev, $callback->($status) |
424 | aio_mknod $path, $mode, $dev, $callback->($status) |
… | |
… | |
372 | |
446 | |
373 | aio_rename $srcpath, $dstpath, $callback->($status) |
447 | aio_rename $srcpath, $dstpath, $callback->($status) |
374 | Asynchronously rename the object at $srcpath to $dstpath, just as |
448 | Asynchronously rename the object at $srcpath to $dstpath, just as |
375 | rename(2) and call the callback with the result code. |
449 | rename(2) and call the callback with the result code. |
376 | |
450 | |
|
|
451 | aio_mkdir $pathname, $mode, $callback->($status) |
|
|
452 | Asynchronously mkdir (create) a directory and call the callback with |
|
|
453 | the result code. $mode will be modified by the umask at the time the |
|
|
454 | request is executed, so do not change your umask. |
|
|
455 | |
377 | aio_rmdir $pathname, $callback->($status) |
456 | aio_rmdir $pathname, $callback->($status) |
378 | Asynchronously rmdir (delete) a directory and call the callback with |
457 | Asynchronously rmdir (delete) a directory and call the callback with |
379 | the result code. |
458 | the result code. |
380 | |
459 | |
381 | aio_readdir $pathname, $callback->($entries) |
460 | aio_readdir $pathname, $callback->($entries) |
… | |
… | |
383 | entire directory (i.e. opendir + readdir + closedir). The entries |
462 | entire directory (i.e. opendir + readdir + closedir). The entries |
384 | will not be sorted, and will NOT include the "." and ".." entries. |
463 | will not be sorted, and will NOT include the "." and ".." entries. |
385 | |
464 | |
386 | The callback a single argument which is either "undef" or an |
465 | The callback a single argument which is either "undef" or an |
387 | array-ref with the filenames. |
466 | array-ref with the filenames. |
|
|
467 | |
|
|
468 | aio_load $path, $data, $callback->($status) |
|
|
469 | This is a composite request that tries to fully load the given file |
|
|
470 | into memory. Status is the same as with aio_read. |
388 | |
471 | |
389 | aio_copy $srcpath, $dstpath, $callback->($status) |
472 | aio_copy $srcpath, $dstpath, $callback->($status) |
390 | Try to copy the *file* (directories not supported as either source |
473 | Try to copy the *file* (directories not supported as either source |
391 | or destination) from $srcpath to $dstpath and call the callback with |
474 | or destination) from $srcpath to $dstpath and call the callback with |
392 | the 0 (error) or -1 ok. |
475 | the 0 (error) or -1 ok. |
… | |
… | |
460 | |
543 | |
461 | It will also likely work on non-POSIX filesystems with reduced |
544 | 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 |
545 | efficiency as those tend to return 0 or 1 as link counts, which |
463 | disables the directory counting heuristic. |
546 | disables the directory counting heuristic. |
464 | |
547 | |
|
|
548 | aio_rmtree $path, $callback->($status) |
|
|
549 | Delete a directory tree starting (and including) $path, return the |
|
|
550 | status of the final "rmdir" only. This is a composite request that |
|
|
551 | uses "aio_scandir" to recurse into and rmdir directories, and unlink |
|
|
552 | everything else. |
|
|
553 | |
|
|
554 | aio_sync $callback->($status) |
|
|
555 | Asynchronously call sync and call the callback when finished. |
|
|
556 | |
465 | aio_fsync $fh, $callback->($status) |
557 | aio_fsync $fh, $callback->($status) |
466 | Asynchronously call fsync on the given filehandle and call the |
558 | Asynchronously call fsync on the given filehandle and call the |
467 | callback with the fsync result code. |
559 | callback with the fsync result code. |
468 | |
560 | |
469 | aio_fdatasync $fh, $callback->($status) |
561 | aio_fdatasync $fh, $callback->($status) |
470 | Asynchronously call fdatasync on the given filehandle and call the |
562 | Asynchronously call fdatasync on the given filehandle and call the |
471 | callback with the fdatasync result code. |
563 | callback with the fdatasync result code. |
472 | |
564 | |
473 | If this call isn't available because your OS lacks it or it couldn't |
565 | If this call isn't available because your OS lacks it or it couldn't |
474 | be detected, it will be emulated by calling "fsync" instead. |
566 | be detected, it will be emulated by calling "fsync" instead. |
|
|
567 | |
|
|
568 | aio_pathsync $path, $callback->($status) |
|
|
569 | This request tries to open, fsync and close the given path. This is |
|
|
570 | a composite request intended tosync directories after directory |
|
|
571 | operations (E.g. rename). This might not work on all operating |
|
|
572 | systems or have any specific effect, but usually it makes sure that |
|
|
573 | directory changes get written to disc. It works for anything that |
|
|
574 | can be opened for read-only, not just directories. |
|
|
575 | |
|
|
576 | Passes 0 when everything went ok, and -1 on error. |
475 | |
577 | |
476 | aio_group $callback->(...) |
578 | aio_group $callback->(...) |
477 | This is a very special aio request: Instead of doing something, it |
579 | This is a very special aio request: Instead of doing something, it |
478 | is a container for other aio requests, which is useful if you want |
580 | is a container for other aio requests, which is useful if you want |
479 | to bundle many requests into a single, composite, request with a |
581 | to bundle many requests into a single, composite, request with a |
… | |
… | |
561 | }; |
663 | }; |
562 | |
664 | |
563 | This makes it very easy to create composite requests (see the source of |
665 | This makes it very easy to create composite requests (see the source of |
564 | "aio_move" for an application) that work and feel like simple requests. |
666 | "aio_move" for an application) that work and feel like simple requests. |
565 | |
667 | |
566 | * The IO::AIO::GRP objects will be cleaned up during calls to |
668 | * The IO::AIO::GRP objects will be cleaned up during calls to |
567 | "IO::AIO::poll_cb", just like any other request. |
669 | "IO::AIO::poll_cb", just like any other request. |
|
|
670 | |
568 | * They can be canceled like any other request. Canceling will cancel not |
671 | * They can be canceled like any other request. Canceling will cancel |
569 | only the request itself, but also all requests it contains. |
672 | not only the request itself, but also all requests it contains. |
|
|
673 | |
570 | * They can also can also be added to other IO::AIO::GRP objects. |
674 | * They can also can also be added to other IO::AIO::GRP objects. |
|
|
675 | |
571 | * You must not add requests to a group from within the group callback |
676 | * You must not add requests to a group from within the group callback |
572 | (or any later time). |
677 | (or any later time). |
573 | |
678 | |
574 | Their lifetime, simplified, looks like this: when they are empty, they |
679 | Their lifetime, simplified, looks like this: when they are empty, they |
575 | will finish very quickly. If they contain only requests that are in the |
680 | will finish very quickly. If they contain only requests that are in the |
576 | "done" state, they will also finish. Otherwise they will continue to |
681 | "done" state, they will also finish. Otherwise they will continue to |
577 | exist. |
682 | exist. |
… | |
… | |
594 | request itself. Useful when you queued a lot of events but got a |
699 | request itself. Useful when you queued a lot of events but got a |
595 | result early. |
700 | result early. |
596 | |
701 | |
597 | $grp->result (...) |
702 | $grp->result (...) |
598 | Set the result value(s) that will be passed to the group callback |
703 | Set the result value(s) that will be passed to the group callback |
599 | when all subrequests have finished and set thre groups errno to the |
704 | when all subrequests have finished and set the groups errno to the |
600 | current value of errno (just like calling "errno" without an error |
705 | current value of errno (just like calling "errno" without an error |
601 | number). By default, no argument will be passed and errno is zero. |
706 | number). By default, no argument will be passed and errno is zero. |
602 | |
707 | |
603 | $grp->errno ([$errno]) |
708 | $grp->errno ([$errno]) |
604 | Sets the group errno value to $errno, or the current value of errno |
709 | Sets the group errno value to $errno, or the current value of errno |
… | |
… | |
711 | Event->io (fd => IO::AIO::poll_fileno, |
816 | Event->io (fd => IO::AIO::poll_fileno, |
712 | poll => 'r', nice => 1, |
817 | poll => 'r', nice => 1, |
713 | cb => &IO::AIO::poll_cb); |
818 | cb => &IO::AIO::poll_cb); |
714 | |
819 | |
715 | IO::AIO::poll_wait |
820 | IO::AIO::poll_wait |
|
|
821 | If there are any outstanding requests and none of them in the result |
716 | Wait till the result filehandle becomes ready for reading (simply |
822 | phase, wait till the result filehandle becomes ready for reading |
717 | does a "select" on the filehandle. This is useful if you want to |
823 | (simply does a "select" on the filehandle. This is useful if you |
718 | synchronously wait for some requests to finish). |
824 | want to synchronously wait for some requests to finish). |
719 | |
825 | |
720 | See "nreqs" for an example. |
826 | See "nreqs" for an example. |
721 | |
827 | |
722 | IO::AIO::poll |
828 | IO::AIO::poll |
723 | Waits until some requests have been handled. |
829 | Waits until some requests have been handled. |
724 | |
830 | |
|
|
831 | Returns the number of requests processed, but is otherwise strictly |
725 | Strictly equivalent to: |
832 | equivalent to: |
726 | |
833 | |
727 | IO::AIO::poll_wait, IO::AIO::poll_cb |
834 | IO::AIO::poll_wait, IO::AIO::poll_cb |
728 | if IO::AIO::nreqs; |
|
|
729 | |
835 | |
730 | IO::AIO::flush |
836 | IO::AIO::flush |
731 | Wait till all outstanding AIO requests have been handled. |
837 | Wait till all outstanding AIO requests have been handled. |
732 | |
838 | |
733 | Strictly equivalent to: |
839 | Strictly equivalent to: |
… | |
… | |
789 | $oldmaxreqs = IO::AIO::max_outstanding $maxreqs |
895 | $oldmaxreqs = IO::AIO::max_outstanding $maxreqs |
790 | This is a very bad function to use in interactive programs because |
896 | 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 |
897 | it blocks, and a bad way to reduce concurrency because it is |
792 | inexact: Better use an "aio_group" together with a feed callback. |
898 | inexact: Better use an "aio_group" together with a feed callback. |
793 | |
899 | |
794 | Sets the maximum number of outstanding requests to $nreqs. If you to |
900 | 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 |
901 | 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") |
902 | "poll_cb" (and "poll_some" and other functions calling "poll_cb") |
797 | function will block until the limit is no longer exceeded. |
903 | function will block until the limit is no longer exceeded. |
798 | |
904 | |
799 | The default value is very large, so there is no practical limit on |
905 | 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 |
951 | 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 |
952 | 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 |
953 | 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. |
954 | will consume memory till the request has entered the done state. |
849 | |
955 | |
850 | This is now awfully much, so queuing lots of requests is not usually a |
956 | This is not awfully much, so queuing lots of requests is not usually a |
851 | problem. |
957 | problem. |
852 | |
958 | |
853 | Per-thread usage: |
959 | Per-thread usage: |
854 | |
960 | |
855 | In the execution phase, some aio requests require more memory for |
961 | In the execution phase, some aio requests require more memory for |