… | |
… | |
168 | use common::sense; |
168 | use common::sense; |
169 | |
169 | |
170 | use base 'Exporter'; |
170 | use base 'Exporter'; |
171 | |
171 | |
172 | BEGIN { |
172 | BEGIN { |
173 | our $VERSION = '3.72'; |
173 | our $VERSION = '4.15'; |
174 | |
174 | |
175 | our @AIO_REQ = qw(aio_sendfile aio_read aio_write aio_open aio_close |
175 | our @AIO_REQ = qw(aio_sendfile aio_seek aio_read aio_write aio_open aio_close |
176 | aio_stat aio_lstat aio_unlink aio_rmdir aio_readdir aio_readdirx |
176 | aio_stat aio_lstat aio_unlink aio_rmdir aio_readdir aio_readdirx |
177 | aio_scandir aio_symlink aio_readlink aio_sync aio_fsync |
177 | aio_scandir aio_symlink aio_readlink aio_realpath aio_sync |
178 | aio_fdatasync aio_sync_file_range aio_pathsync aio_readahead |
178 | aio_fsync aio_syncfs aio_fdatasync aio_sync_file_range aio_fallocate |
|
|
179 | aio_pathsync aio_readahead aio_fiemap |
179 | aio_rename aio_link aio_move aio_copy aio_group |
180 | aio_rename aio_link aio_move aio_copy aio_group |
180 | aio_nop aio_mknod aio_load aio_rmtree aio_mkdir aio_chown |
181 | aio_nop aio_mknod aio_load aio_rmtree aio_mkdir aio_chown |
181 | aio_chmod aio_utime aio_truncate |
182 | aio_chmod aio_utime aio_truncate |
182 | aio_msync aio_mtouch aio_mlock aio_mlockall |
183 | aio_msync aio_mtouch aio_mlock aio_mlockall |
183 | aio_statvfs); |
184 | aio_statvfs |
|
|
185 | aio_wd); |
184 | |
186 | |
185 | our @EXPORT = (@AIO_REQ, qw(aioreq_pri aioreq_nice)); |
187 | our @EXPORT = (@AIO_REQ, qw(aioreq_pri aioreq_nice)); |
186 | our @EXPORT_OK = qw(poll_fileno poll_cb poll_wait flush |
188 | our @EXPORT_OK = qw(poll_fileno poll_cb poll_wait flush |
187 | min_parallel max_parallel max_idle idle_timeout |
189 | min_parallel max_parallel max_idle idle_timeout |
188 | nreqs nready npending nthreads |
190 | nreqs nready npending nthreads |
… | |
… | |
200 | |
202 | |
201 | =head1 FUNCTIONS |
203 | =head1 FUNCTIONS |
202 | |
204 | |
203 | =head2 QUICK OVERVIEW |
205 | =head2 QUICK OVERVIEW |
204 | |
206 | |
205 | This section simply lists the prototypes of the most important functions |
207 | This section simply lists the prototypes most of the functions for |
206 | for quick reference. See the following sections for function-by-function |
208 | quick reference. See the following sections for function-by-function |
207 | documentation. |
209 | documentation. |
208 | |
210 | |
|
|
211 | aio_wd $pathname, $callback->($wd) |
209 | aio_open $pathname, $flags, $mode, $callback->($fh) |
212 | aio_open $pathname, $flags, $mode, $callback->($fh) |
210 | aio_close $fh, $callback->($status) |
213 | aio_close $fh, $callback->($status) |
|
|
214 | aio_seek $fh,$offset,$whence, $callback->($offs) |
211 | aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
215 | aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
212 | aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
216 | aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
213 | aio_sendfile $out_fh, $in_fh, $in_offset, $length, $callback->($retval) |
217 | aio_sendfile $out_fh, $in_fh, $in_offset, $length, $callback->($retval) |
214 | aio_readahead $fh,$offset,$length, $callback->($retval) |
218 | aio_readahead $fh,$offset,$length, $callback->($retval) |
215 | aio_stat $fh_or_path, $callback->($status) |
219 | aio_stat $fh_or_path, $callback->($status) |
216 | aio_lstat $fh, $callback->($status) |
220 | aio_lstat $fh, $callback->($status) |
217 | aio_statvfs $fh_or_path, $callback->($statvfs) |
221 | aio_statvfs $fh_or_path, $callback->($statvfs) |
218 | aio_utime $fh_or_path, $atime, $mtime, $callback->($status) |
222 | aio_utime $fh_or_path, $atime, $mtime, $callback->($status) |
219 | aio_chown $fh_or_path, $uid, $gid, $callback->($status) |
223 | aio_chown $fh_or_path, $uid, $gid, $callback->($status) |
|
|
224 | aio_chmod $fh_or_path, $mode, $callback->($status) |
220 | aio_truncate $fh_or_path, $offset, $callback->($status) |
225 | aio_truncate $fh_or_path, $offset, $callback->($status) |
221 | aio_chmod $fh_or_path, $mode, $callback->($status) |
226 | aio_allocate $fh, $mode, $offset, $len, $callback->($status) |
|
|
227 | aio_fiemap $fh, $start, $length, $flags, $count, $cb->(\@extents) |
222 | aio_unlink $pathname, $callback->($status) |
228 | aio_unlink $pathname, $callback->($status) |
223 | aio_mknod $path, $mode, $dev, $callback->($status) |
229 | aio_mknod $pathname, $mode, $dev, $callback->($status) |
224 | aio_link $srcpath, $dstpath, $callback->($status) |
230 | aio_link $srcpath, $dstpath, $callback->($status) |
225 | aio_symlink $srcpath, $dstpath, $callback->($status) |
231 | aio_symlink $srcpath, $dstpath, $callback->($status) |
226 | aio_readlink $path, $callback->($link) |
232 | aio_readlink $pathname, $callback->($link) |
|
|
233 | aio_realpath $pathname, $callback->($link) |
227 | aio_rename $srcpath, $dstpath, $callback->($status) |
234 | aio_rename $srcpath, $dstpath, $callback->($status) |
228 | aio_mkdir $pathname, $mode, $callback->($status) |
235 | aio_mkdir $pathname, $mode, $callback->($status) |
229 | aio_rmdir $pathname, $callback->($status) |
236 | aio_rmdir $pathname, $callback->($status) |
230 | aio_readdir $pathname, $callback->($entries) |
237 | aio_readdir $pathname, $callback->($entries) |
231 | aio_readdirx $pathname, $flags, $callback->($entries, $flags) |
238 | aio_readdirx $pathname, $flags, $callback->($entries, $flags) |
232 | IO::AIO::READDIR_DENTS IO::AIO::READDIR_DIRS_FIRST |
239 | IO::AIO::READDIR_DENTS IO::AIO::READDIR_DIRS_FIRST |
233 | IO::AIO::READDIR_STAT_ORDER IO::AIO::READDIR_FOUND_UNKNOWN |
240 | IO::AIO::READDIR_STAT_ORDER IO::AIO::READDIR_FOUND_UNKNOWN |
|
|
241 | aio_scandir $pathname, $maxreq, $callback->($dirs, $nondirs) |
234 | aio_load $path, $data, $callback->($status) |
242 | aio_load $pathname, $data, $callback->($status) |
235 | aio_copy $srcpath, $dstpath, $callback->($status) |
243 | aio_copy $srcpath, $dstpath, $callback->($status) |
236 | aio_move $srcpath, $dstpath, $callback->($status) |
244 | aio_move $srcpath, $dstpath, $callback->($status) |
237 | aio_scandir $path, $maxreq, $callback->($dirs, $nondirs) |
|
|
238 | aio_rmtree $path, $callback->($status) |
245 | aio_rmtree $pathname, $callback->($status) |
239 | aio_sync $callback->($status) |
246 | aio_sync $callback->($status) |
|
|
247 | aio_syncfs $fh, $callback->($status) |
240 | aio_fsync $fh, $callback->($status) |
248 | aio_fsync $fh, $callback->($status) |
241 | aio_fdatasync $fh, $callback->($status) |
249 | aio_fdatasync $fh, $callback->($status) |
242 | aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status) |
250 | aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status) |
243 | aio_pathsync $path, $callback->($status) |
251 | aio_pathsync $pathname, $callback->($status) |
244 | aio_msync $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status) |
252 | aio_msync $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status) |
245 | aio_mtouch $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status) |
253 | aio_mtouch $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status) |
246 | aio_mlock $scalar, $offset = 0, $length = undef, $callback->($status) |
254 | aio_mlock $scalar, $offset = 0, $length = undef, $callback->($status) |
247 | aio_mlockall $flags, $callback->($status) |
255 | aio_mlockall $flags, $callback->($status) |
248 | aio_group $callback->(...) |
256 | aio_group $callback->(...) |
… | |
… | |
266 | IO::AIO::nready |
274 | IO::AIO::nready |
267 | IO::AIO::npending |
275 | IO::AIO::npending |
268 | |
276 | |
269 | IO::AIO::sendfile $ofh, $ifh, $offset, $count |
277 | IO::AIO::sendfile $ofh, $ifh, $offset, $count |
270 | IO::AIO::fadvise $fh, $offset, $len, $advice |
278 | IO::AIO::fadvise $fh, $offset, $len, $advice |
|
|
279 | IO::AIO::mmap $scalar, $length, $prot, $flags[, $fh[, $offset]] |
|
|
280 | IO::AIO::munmap $scalar |
271 | IO::AIO::madvise $scalar, $offset, $length, $advice |
281 | IO::AIO::madvise $scalar, $offset, $length, $advice |
272 | IO::AIO::mprotect $scalar, $offset, $length, $protect |
282 | IO::AIO::mprotect $scalar, $offset, $length, $protect |
273 | IO::AIO::munlock $scalar, $offset = 0, $length = undef |
283 | IO::AIO::munlock $scalar, $offset = 0, $length = undef |
274 | IO::AIO::munlockall |
284 | IO::AIO::munlockall |
275 | |
285 | |
276 | =head2 AIO REQUEST FUNCTIONS |
286 | =head2 API NOTES |
277 | |
287 | |
278 | All the C<aio_*> calls are more or less thin wrappers around the syscall |
288 | All the C<aio_*> calls are more or less thin wrappers around the syscall |
279 | with the same name (sans C<aio_>). The arguments are similar or identical, |
289 | with the same name (sans C<aio_>). The arguments are similar or identical, |
280 | and they all accept an additional (and optional) C<$callback> argument |
290 | and they all accept an additional (and optional) C<$callback> argument |
281 | which must be a code reference. This code reference will get called with |
291 | which must be a code reference. This code reference will be called after |
282 | the syscall return code (e.g. most syscalls return C<-1> on error, unlike |
292 | the syscall has been executed in an asynchronous fashion. The results |
283 | perl, which usually delivers "false") as its sole argument after the given |
293 | of the request will be passed as arguments to the callback (and, if an |
284 | syscall has been executed asynchronously. |
294 | error occured, in C<$!>) - for most requests the syscall return code (e.g. |
|
|
295 | most syscalls return C<-1> on error, unlike perl, which usually delivers |
|
|
296 | "false"). |
|
|
297 | |
|
|
298 | Some requests (such as C<aio_readdir>) pass the actual results and |
|
|
299 | communicate failures by passing C<undef>. |
285 | |
300 | |
286 | All functions expecting a filehandle keep a copy of the filehandle |
301 | All functions expecting a filehandle keep a copy of the filehandle |
287 | internally until the request has finished. |
302 | internally until the request has finished. |
288 | |
303 | |
289 | All functions return request objects of type L<IO::AIO::REQ> that allow |
304 | All functions return request objects of type L<IO::AIO::REQ> that allow |
290 | further manipulation of those requests while they are in-flight. |
305 | further manipulation of those requests while they are in-flight. |
291 | |
306 | |
292 | The pathnames you pass to these routines I<must> be absolute and |
307 | The pathnames you pass to these routines I<should> be absolute. The |
293 | encoded as octets. The reason for the former is that at the time the |
308 | reason for this is that at the time the request is being executed, the |
294 | request is being executed, the current working directory could have |
309 | current working directory could have changed. Alternatively, you can |
295 | changed. Alternatively, you can make sure that you never change the |
310 | make sure that you never change the current working directory anywhere |
296 | current working directory anywhere in the program and then use relative |
311 | in the program and then use relative paths. You can also take advantage |
297 | paths. |
312 | of IO::AIOs working directory abstraction, that lets you specify paths |
|
|
313 | relative to some previously-opened "working directory object" - see the |
|
|
314 | description of the C<IO::AIO::WD> class later in this document. |
298 | |
315 | |
299 | To encode pathnames as octets, either make sure you either: a) always pass |
316 | To encode pathnames as octets, either make sure you either: a) always pass |
300 | in filenames you got from outside (command line, readdir etc.) without |
317 | in filenames you got from outside (command line, readdir etc.) without |
301 | tinkering, b) are ASCII or ISO 8859-1, c) use the Encode module and encode |
318 | tinkering, b) are in your native filesystem encoding, c) use the Encode |
302 | your pathnames to the locale (or other) encoding in effect in the user |
319 | module and encode your pathnames to the locale (or other) encoding in |
303 | environment, d) use Glib::filename_from_unicode on unicode filenames or e) |
320 | effect in the user environment, d) use Glib::filename_from_unicode on |
304 | use something else to ensure your scalar has the correct contents. |
321 | unicode filenames or e) use something else to ensure your scalar has the |
|
|
322 | correct contents. |
305 | |
323 | |
306 | This works, btw. independent of the internal UTF-8 bit, which IO::AIO |
324 | This works, btw. independent of the internal UTF-8 bit, which IO::AIO |
307 | handles correctly whether it is set or not. |
325 | handles correctly whether it is set or not. |
|
|
326 | |
|
|
327 | =head2 AIO REQUEST FUNCTIONS |
308 | |
328 | |
309 | =over 4 |
329 | =over 4 |
310 | |
330 | |
311 | =item $prev_pri = aioreq_pri [$pri] |
331 | =item $prev_pri = aioreq_pri [$pri] |
312 | |
332 | |
… | |
… | |
342 | |
362 | |
343 | |
363 | |
344 | =item aio_open $pathname, $flags, $mode, $callback->($fh) |
364 | =item aio_open $pathname, $flags, $mode, $callback->($fh) |
345 | |
365 | |
346 | Asynchronously open or create a file and call the callback with a newly |
366 | Asynchronously open or create a file and call the callback with a newly |
347 | created filehandle for the file. |
367 | created filehandle for the file (or C<undef> in case of an error). |
348 | |
368 | |
349 | The pathname passed to C<aio_open> must be absolute. See API NOTES, above, |
369 | The pathname passed to C<aio_open> must be absolute. See API NOTES, above, |
350 | for an explanation. |
370 | for an explanation. |
351 | |
371 | |
352 | The C<$flags> argument is a bitmask. See the C<Fcntl> module for a |
372 | The C<$flags> argument is a bitmask. See the C<Fcntl> module for a |
… | |
… | |
368 | } else { |
388 | } else { |
369 | die "open failed: $!\n"; |
389 | die "open failed: $!\n"; |
370 | } |
390 | } |
371 | }; |
391 | }; |
372 | |
392 | |
|
|
393 | In addition to all the common open modes/flags (C<O_RDONLY>, C<O_WRONLY>, |
|
|
394 | C<O_RDWR>, C<O_CREAT>, C<O_TRUNC>, C<O_EXCL> and C<O_APPEND>), the |
|
|
395 | following POSIX and non-POSIX constants are available (missing ones on |
|
|
396 | your system are, as usual, C<0>): |
|
|
397 | |
|
|
398 | C<O_ASYNC>, C<O_DIRECT>, C<O_NOATIME>, C<O_CLOEXEC>, C<O_NOCTTY>, C<O_NOFOLLOW>, |
|
|
399 | C<O_NONBLOCK>, C<O_EXEC>, C<O_SEARCH>, C<O_DIRECTORY>, C<O_DSYNC>, |
|
|
400 | C<O_RSYNC>, C<O_SYNC> and C<O_TTY_INIT>. |
|
|
401 | |
373 | |
402 | |
374 | =item aio_close $fh, $callback->($status) |
403 | =item aio_close $fh, $callback->($status) |
375 | |
404 | |
376 | Asynchronously close a file and call the callback with the result |
405 | Asynchronously close a file and call the callback with the result |
377 | code. |
406 | code. |
… | |
… | |
385 | |
414 | |
386 | Or in other words: the file descriptor will be closed, but it will not be |
415 | Or in other words: the file descriptor will be closed, but it will not be |
387 | free for reuse until the perl filehandle is closed. |
416 | free for reuse until the perl filehandle is closed. |
388 | |
417 | |
389 | =cut |
418 | =cut |
|
|
419 | |
|
|
420 | =item aio_seek $fh, $offset, $whence, $callback->($offs) |
|
|
421 | |
|
|
422 | Seeks the filehandle to the new C<$offset>, similarly to perl's |
|
|
423 | C<sysseek>. The C<$whence> can use the traditional values (C<0> for |
|
|
424 | C<IO::AIO::SEEK_SET>, C<1> for C<IO::AIO::SEEK_CUR> or C<2> for |
|
|
425 | C<IO::AIO::SEEK_END>). |
|
|
426 | |
|
|
427 | The resulting absolute offset will be passed to the callback, or C<-1> in |
|
|
428 | case of an error. |
|
|
429 | |
|
|
430 | In theory, the C<$whence> constants could be different than the |
|
|
431 | corresponding values from L<Fcntl>, but perl guarantees they are the same, |
|
|
432 | so don't panic. |
|
|
433 | |
|
|
434 | As a GNU/Linux (and maybe Solaris) extension, also the constants |
|
|
435 | C<IO::AIO::SEEK_DATA> and C<IO::AIO::SEEK_HOLE> are available, if they |
|
|
436 | could be found. No guarantees about suitability for use in C<aio_seek> or |
|
|
437 | Perl's C<sysseek> can be made though, although I would naively assume they |
|
|
438 | "just work". |
390 | |
439 | |
391 | =item aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
440 | =item aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
392 | |
441 | |
393 | =item aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
442 | =item aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) |
394 | |
443 | |
… | |
… | |
427 | |
476 | |
428 | Tries to copy C<$length> bytes from C<$in_fh> to C<$out_fh>. It starts |
477 | Tries to copy C<$length> bytes from C<$in_fh> to C<$out_fh>. It starts |
429 | reading at byte offset C<$in_offset>, and starts writing at the current |
478 | reading at byte offset C<$in_offset>, and starts writing at the current |
430 | file offset of C<$out_fh>. Because of that, it is not safe to issue more |
479 | file offset of C<$out_fh>. Because of that, it is not safe to issue more |
431 | than one C<aio_sendfile> per C<$out_fh>, as they will interfere with each |
480 | than one C<aio_sendfile> per C<$out_fh>, as they will interfere with each |
432 | other. |
481 | other. The same C<$in_fh> works fine though, as this function does not |
|
|
482 | move or use the file offset of C<$in_fh>. |
433 | |
483 | |
434 | Please note that C<aio_sendfile> can read more bytes from C<$in_fh> than |
484 | Please note that C<aio_sendfile> can read more bytes from C<$in_fh> than |
435 | are written, and there is no way to find out how many bytes have been read |
485 | are written, and there is no way to find out how many more bytes have been |
436 | from C<aio_sendfile> alone, as C<aio_sendfile> only provides the number of |
486 | read from C<aio_sendfile> alone, as C<aio_sendfile> only provides the |
437 | bytes written to C<$out_fh>. Only if the result value equals C<$length> |
487 | number of bytes written to C<$out_fh>. Only if the result value equals |
438 | one can assume that C<$length> bytes have been read. |
488 | C<$length> one can assume that C<$length> bytes have been read. |
439 | |
489 | |
440 | Unlike with other C<aio_> functions, it makes a lot of sense to use |
490 | Unlike with other C<aio_> functions, it makes a lot of sense to use |
441 | C<aio_sendfile> on non-blocking sockets, as long as one end (typically |
491 | C<aio_sendfile> on non-blocking sockets, as long as one end (typically |
442 | the C<$in_fh>) is a file - the file I/O will then be asynchronous, while |
492 | the C<$in_fh>) is a file - the file I/O will then be asynchronous, while |
443 | the socket I/O will be non-blocking. Note, however, that you can run into |
493 | the socket I/O will be non-blocking. Note, however, that you can run |
444 | a trap where C<aio_sendfile> reads some data with readahead, then fails |
494 | into a trap where C<aio_sendfile> reads some data with readahead, then |
445 | to write all data, and when the socket is ready the next time, the data |
495 | fails to write all data, and when the socket is ready the next time, the |
446 | in the cache is already lost, forcing C<aio_sendfile> to again hit the |
496 | data in the cache is already lost, forcing C<aio_sendfile> to again hit |
447 | disk. Explicit C<aio_read> + C<aio_write> let's you control resource usage |
497 | the disk. Explicit C<aio_read> + C<aio_write> let's you better control |
448 | much better. |
498 | resource usage. |
449 | |
499 | |
450 | This call tries to make use of a native C<sendfile> syscall to provide |
500 | This call tries to make use of a native C<sendfile>-like syscall to |
451 | zero-copy operation. For this to work, C<$out_fh> should refer to a |
501 | provide zero-copy operation. For this to work, C<$out_fh> should refer to |
452 | socket, and C<$in_fh> should refer to an mmap'able file. |
502 | a socket, and C<$in_fh> should refer to an mmap'able file. |
453 | |
503 | |
454 | If a native sendfile cannot be found or it fails with C<ENOSYS>, |
504 | If a native sendfile cannot be found or it fails with C<ENOSYS>, |
455 | C<ENOTSUP>, C<EOPNOTSUPP>, C<EAFNOSUPPORT>, C<EPROTOTYPE> or C<ENOTSOCK>, |
505 | C<EINVAL>, C<ENOTSUP>, C<EOPNOTSUPP>, C<EAFNOSUPPORT>, C<EPROTOTYPE> or |
456 | it will be emulated, so you can call C<aio_sendfile> on any type of |
506 | C<ENOTSOCK>, it will be emulated, so you can call C<aio_sendfile> on any |
457 | filehandle regardless of the limitations of the operating system. |
507 | type of filehandle regardless of the limitations of the operating system. |
|
|
508 | |
|
|
509 | As native sendfile syscalls (as practically any non-POSIX interface hacked |
|
|
510 | together in a hurry to improve benchmark numbers) tend to be rather buggy |
|
|
511 | on many systems, this implementation tries to work around some known bugs |
|
|
512 | in Linux and FreeBSD kernels (probably others, too), but that might fail, |
|
|
513 | so you really really should check the return value of C<aio_sendfile> - |
|
|
514 | fewre bytes than expected might have been transferred. |
458 | |
515 | |
459 | |
516 | |
460 | =item aio_readahead $fh,$offset,$length, $callback->($retval) |
517 | =item aio_readahead $fh,$offset,$length, $callback->($retval) |
461 | |
518 | |
462 | C<aio_readahead> populates the page cache with data from a file so that |
519 | C<aio_readahead> populates the page cache with data from a file so that |
… | |
… | |
583 | =item aio_truncate $fh_or_path, $offset, $callback->($status) |
640 | =item aio_truncate $fh_or_path, $offset, $callback->($status) |
584 | |
641 | |
585 | Works like truncate(2) or ftruncate(2). |
642 | Works like truncate(2) or ftruncate(2). |
586 | |
643 | |
587 | |
644 | |
|
|
645 | =item aio_allocate $fh, $mode, $offset, $len, $callback->($status) |
|
|
646 | |
|
|
647 | Allocates or freed disk space according to the C<$mode> argument. See the |
|
|
648 | linux C<fallocate> docuemntation for details. |
|
|
649 | |
|
|
650 | C<$mode> can currently be C<0> or C<IO::AIO::FALLOC_FL_KEEP_SIZE> |
|
|
651 | to allocate space, or C<IO::AIO::FALLOC_FL_PUNCH_HOLE | |
|
|
652 | IO::AIO::FALLOC_FL_KEEP_SIZE>, to deallocate a file range. |
|
|
653 | |
|
|
654 | The file system block size used by C<fallocate> is presumably the |
|
|
655 | C<f_bsize> returned by C<statvfs>. |
|
|
656 | |
|
|
657 | If C<fallocate> isn't available or cannot be emulated (currently no |
|
|
658 | emulation will be attempted), passes C<-1> and sets C<$!> to C<ENOSYS>. |
|
|
659 | |
|
|
660 | |
588 | =item aio_chmod $fh_or_path, $mode, $callback->($status) |
661 | =item aio_chmod $fh_or_path, $mode, $callback->($status) |
589 | |
662 | |
590 | Works like perl's C<chmod> function. |
663 | Works like perl's C<chmod> function. |
591 | |
664 | |
592 | |
665 | |
… | |
… | |
594 | |
667 | |
595 | Asynchronously unlink (delete) a file and call the callback with the |
668 | Asynchronously unlink (delete) a file and call the callback with the |
596 | result code. |
669 | result code. |
597 | |
670 | |
598 | |
671 | |
599 | =item aio_mknod $path, $mode, $dev, $callback->($status) |
672 | =item aio_mknod $pathname, $mode, $dev, $callback->($status) |
600 | |
673 | |
601 | [EXPERIMENTAL] |
674 | [EXPERIMENTAL] |
602 | |
675 | |
603 | Asynchronously create a device node (or fifo). See mknod(2). |
676 | Asynchronously create a device node (or fifo). See mknod(2). |
604 | |
677 | |
605 | The only (POSIX-) portable way of calling this function is: |
678 | The only (POSIX-) portable way of calling this function is: |
606 | |
679 | |
607 | aio_mknod $path, IO::AIO::S_IFIFO | $mode, 0, sub { ... |
680 | aio_mknod $pathname, IO::AIO::S_IFIFO | $mode, 0, sub { ... |
608 | |
681 | |
609 | See C<aio_stat> for info about some potentially helpful extra constants |
682 | See C<aio_stat> for info about some potentially helpful extra constants |
610 | and functions. |
683 | and functions. |
611 | |
684 | |
612 | =item aio_link $srcpath, $dstpath, $callback->($status) |
685 | =item aio_link $srcpath, $dstpath, $callback->($status) |
… | |
… | |
619 | |
692 | |
620 | Asynchronously create a new symbolic link to the existing object at C<$srcpath> at |
693 | Asynchronously create a new symbolic link to the existing object at C<$srcpath> at |
621 | the path C<$dstpath> and call the callback with the result code. |
694 | the path C<$dstpath> and call the callback with the result code. |
622 | |
695 | |
623 | |
696 | |
624 | =item aio_readlink $path, $callback->($link) |
697 | =item aio_readlink $pathname, $callback->($link) |
625 | |
698 | |
626 | Asynchronously read the symlink specified by C<$path> and pass it to |
699 | Asynchronously read the symlink specified by C<$path> and pass it to |
627 | the callback. If an error occurs, nothing or undef gets passed to the |
700 | the callback. If an error occurs, nothing or undef gets passed to the |
628 | callback. |
701 | callback. |
629 | |
702 | |
630 | |
703 | |
|
|
704 | =item aio_realpath $pathname, $callback->($path) |
|
|
705 | |
|
|
706 | Asynchronously make the path absolute and resolve any symlinks in |
|
|
707 | C<$path>. The resulting path only consists of directories (Same as |
|
|
708 | L<Cwd::realpath>). |
|
|
709 | |
|
|
710 | This request can be used to get the absolute path of the current working |
|
|
711 | directory by passing it a path of F<.> (a single dot). |
|
|
712 | |
|
|
713 | |
631 | =item aio_rename $srcpath, $dstpath, $callback->($status) |
714 | =item aio_rename $srcpath, $dstpath, $callback->($status) |
632 | |
715 | |
633 | Asynchronously rename the object at C<$srcpath> to C<$dstpath>, just as |
716 | Asynchronously rename the object at C<$srcpath> to C<$dstpath>, just as |
634 | rename(2) and call the callback with the result code. |
717 | rename(2) and call the callback with the result code. |
635 | |
718 | |
… | |
… | |
657 | array-ref with the filenames. |
740 | array-ref with the filenames. |
658 | |
741 | |
659 | |
742 | |
660 | =item aio_readdirx $pathname, $flags, $callback->($entries, $flags) |
743 | =item aio_readdirx $pathname, $flags, $callback->($entries, $flags) |
661 | |
744 | |
662 | Quite similar to C<aio_readdir>, but the C<$flags> argument allows to tune |
745 | Quite similar to C<aio_readdir>, but the C<$flags> argument allows one to |
663 | behaviour and output format. In case of an error, C<$entries> will be |
746 | tune behaviour and output format. In case of an error, C<$entries> will be |
664 | C<undef>. |
747 | C<undef>. |
665 | |
748 | |
666 | The flags are a combination of the following constants, ORed together (the |
749 | The flags are a combination of the following constants, ORed together (the |
667 | flags will also be passed to the callback, possibly modified): |
750 | flags will also be passed to the callback, possibly modified): |
668 | |
751 | |
669 | =over 4 |
752 | =over 4 |
670 | |
753 | |
671 | =item IO::AIO::READDIR_DENTS |
754 | =item IO::AIO::READDIR_DENTS |
672 | |
755 | |
673 | When this flag is off, then the callback gets an arrayref with of names |
756 | When this flag is off, then the callback gets an arrayref consisting of |
674 | only (as with C<aio_readdir>), otherwise it gets an arrayref with |
757 | names only (as with C<aio_readdir>), otherwise it gets an arrayref with |
675 | C<[$name, $type, $inode]> arrayrefs, each describing a single directory |
758 | C<[$name, $type, $inode]> arrayrefs, each describing a single directory |
676 | entry in more detail. |
759 | entry in more detail. |
677 | |
760 | |
678 | C<$name> is the name of the entry. |
761 | C<$name> is the name of the entry. |
679 | |
762 | |
… | |
… | |
692 | systems that do not deliver the inode information. |
775 | systems that do not deliver the inode information. |
693 | |
776 | |
694 | =item IO::AIO::READDIR_DIRS_FIRST |
777 | =item IO::AIO::READDIR_DIRS_FIRST |
695 | |
778 | |
696 | When this flag is set, then the names will be returned in an order where |
779 | When this flag is set, then the names will be returned in an order where |
697 | likely directories come first. This is useful when you need to quickly |
780 | likely directories come first, in optimal stat order. This is useful when |
698 | find directories, or you want to find all directories while avoiding to |
781 | you need to quickly find directories, or you want to find all directories |
699 | stat() each entry. |
782 | while avoiding to stat() each entry. |
700 | |
783 | |
701 | If the system returns type information in readdir, then this is used |
784 | If the system returns type information in readdir, then this is used |
702 | to find directories directly. Otherwise, likely directories are files |
785 | to find directories directly. Otherwise, likely directories are names |
703 | beginning with ".", or otherwise files with no dots, of which files with |
786 | beginning with ".", or otherwise names with no dots, of which names with |
704 | short names are tried first. |
787 | short names are tried first. |
705 | |
788 | |
706 | =item IO::AIO::READDIR_STAT_ORDER |
789 | =item IO::AIO::READDIR_STAT_ORDER |
707 | |
790 | |
708 | When this flag is set, then the names will be returned in an order |
791 | When this flag is set, then the names will be returned in an order |
… | |
… | |
715 | |
798 | |
716 | =item IO::AIO::READDIR_FOUND_UNKNOWN |
799 | =item IO::AIO::READDIR_FOUND_UNKNOWN |
717 | |
800 | |
718 | This flag should not be set when calling C<aio_readdirx>. Instead, it |
801 | This flag should not be set when calling C<aio_readdirx>. Instead, it |
719 | is being set by C<aio_readdirx>, when any of the C<$type>'s found were |
802 | is being set by C<aio_readdirx>, when any of the C<$type>'s found were |
720 | C<IO::AIO::DT_UNKNOWN>. The absense of this flag therefore indicates that all |
803 | C<IO::AIO::DT_UNKNOWN>. The absence of this flag therefore indicates that all |
721 | C<$type>'s are known, which can be used to speed up some algorithms. |
804 | C<$type>'s are known, which can be used to speed up some algorithms. |
722 | |
805 | |
723 | =back |
806 | =back |
724 | |
807 | |
725 | |
808 | |
726 | =item aio_load $path, $data, $callback->($status) |
809 | =item aio_load $pathname, $data, $callback->($status) |
727 | |
810 | |
728 | This is a composite request that tries to fully load the given file into |
811 | This is a composite request that tries to fully load the given file into |
729 | memory. Status is the same as with aio_read. |
812 | memory. Status is the same as with aio_read. |
730 | |
813 | |
731 | =cut |
814 | =cut |
… | |
… | |
853 | if ($_[0] && $! == EXDEV) { |
936 | if ($_[0] && $! == EXDEV) { |
854 | aioreq_pri $pri; |
937 | aioreq_pri $pri; |
855 | add $grp aio_copy $src, $dst, sub { |
938 | add $grp aio_copy $src, $dst, sub { |
856 | $grp->result ($_[0]); |
939 | $grp->result ($_[0]); |
857 | |
940 | |
858 | if (!$_[0]) { |
941 | unless ($_[0]) { |
859 | aioreq_pri $pri; |
942 | aioreq_pri $pri; |
860 | add $grp aio_unlink $src; |
943 | add $grp aio_unlink $src; |
861 | } |
944 | } |
862 | }; |
945 | }; |
863 | } else { |
946 | } else { |
… | |
… | |
866 | }; |
949 | }; |
867 | |
950 | |
868 | $grp |
951 | $grp |
869 | } |
952 | } |
870 | |
953 | |
871 | =item aio_scandir $path, $maxreq, $callback->($dirs, $nondirs) |
954 | =item aio_scandir $pathname, $maxreq, $callback->($dirs, $nondirs) |
872 | |
955 | |
873 | Scans a directory (similar to C<aio_readdir>) but additionally tries to |
956 | Scans a directory (similar to C<aio_readdir>) but additionally tries to |
874 | efficiently separate the entries of directory C<$path> into two sets of |
957 | efficiently separate the entries of directory C<$path> into two sets of |
875 | names, directories you can recurse into (directories), and ones you cannot |
958 | names, directories you can recurse into (directories), and ones you cannot |
876 | recurse into (everything else, including symlinks to directories). |
959 | recurse into (everything else, including symlinks to directories). |
… | |
… | |
907 | Then entries will be sorted into likely directories a non-initial dot |
990 | Then entries will be sorted into likely directories a non-initial dot |
908 | currently) and likely non-directories (see C<aio_readdirx>). Then every |
991 | currently) and likely non-directories (see C<aio_readdirx>). Then every |
909 | entry plus an appended C</.> will be C<stat>'ed, likely directories first, |
992 | entry plus an appended C</.> will be C<stat>'ed, likely directories first, |
910 | in order of their inode numbers. If that succeeds, it assumes that the |
993 | in order of their inode numbers. If that succeeds, it assumes that the |
911 | entry is a directory or a symlink to directory (which will be checked |
994 | entry is a directory or a symlink to directory (which will be checked |
912 | seperately). This is often faster than stat'ing the entry itself because |
995 | separately). This is often faster than stat'ing the entry itself because |
913 | filesystems might detect the type of the entry without reading the inode |
996 | filesystems might detect the type of the entry without reading the inode |
914 | data (e.g. ext2fs filetype feature), even on systems that cannot return |
997 | data (e.g. ext2fs filetype feature), even on systems that cannot return |
915 | the filetype information on readdir. |
998 | the filetype information on readdir. |
916 | |
999 | |
917 | If the known number of directories (link count - 2) has been reached, the |
1000 | If the known number of directories (link count - 2) has been reached, the |
… | |
… | |
933 | |
1016 | |
934 | my $grp = aio_group $cb; |
1017 | my $grp = aio_group $cb; |
935 | |
1018 | |
936 | $maxreq = 4 if $maxreq <= 0; |
1019 | $maxreq = 4 if $maxreq <= 0; |
937 | |
1020 | |
938 | # stat once |
1021 | # get a wd object |
939 | aioreq_pri $pri; |
1022 | aioreq_pri $pri; |
940 | add $grp aio_stat $path, sub { |
1023 | add $grp aio_wd $path, sub { |
|
|
1024 | $_[0] |
941 | return $grp->result () if $_[0]; |
1025 | or return $grp->result (); |
942 | my $now = time; |
|
|
943 | my $hash1 = join ":", (stat _)[0,1,3,7,9]; |
|
|
944 | |
1026 | |
945 | # read the directory entries |
1027 | my $wd = [shift, "."]; |
|
|
1028 | |
|
|
1029 | # stat once |
946 | aioreq_pri $pri; |
1030 | aioreq_pri $pri; |
947 | add $grp aio_readdirx $path, READDIR_DIRS_FIRST, sub { |
1031 | add $grp aio_stat $wd, sub { |
948 | my $entries = shift |
|
|
949 | or return $grp->result (); |
1032 | return $grp->result () if $_[0]; |
|
|
1033 | my $now = time; |
|
|
1034 | my $hash1 = join ":", (stat _)[0,1,3,7,9]; |
950 | |
1035 | |
951 | # stat the dir another time |
1036 | # read the directory entries |
952 | aioreq_pri $pri; |
1037 | aioreq_pri $pri; |
|
|
1038 | add $grp aio_readdirx $wd, READDIR_DIRS_FIRST, sub { |
|
|
1039 | my $entries = shift |
|
|
1040 | or return $grp->result (); |
|
|
1041 | |
|
|
1042 | # stat the dir another time |
|
|
1043 | aioreq_pri $pri; |
953 | add $grp aio_stat $path, sub { |
1044 | add $grp aio_stat $wd, sub { |
954 | my $hash2 = join ":", (stat _)[0,1,3,7,9]; |
1045 | my $hash2 = join ":", (stat _)[0,1,3,7,9]; |
955 | |
1046 | |
956 | my $ndirs; |
1047 | my $ndirs; |
957 | |
1048 | |
958 | # take the slow route if anything looks fishy |
1049 | # take the slow route if anything looks fishy |
959 | if ($hash1 ne $hash2 or (stat _)[9] == $now) { |
1050 | if ($hash1 ne $hash2 or (stat _)[9] == $now) { |
960 | $ndirs = -1; |
1051 | $ndirs = -1; |
961 | } else { |
1052 | } else { |
962 | # if nlink == 2, we are finished |
1053 | # if nlink == 2, we are finished |
963 | # for non-posix-fs's, we rely on nlink < 2 |
1054 | # for non-posix-fs's, we rely on nlink < 2 |
964 | $ndirs = (stat _)[3] - 2 |
1055 | $ndirs = (stat _)[3] - 2 |
965 | or return $grp->result ([], $entries); |
1056 | or return $grp->result ([], $entries); |
966 | } |
1057 | } |
967 | |
1058 | |
968 | my (@dirs, @nondirs); |
1059 | my (@dirs, @nondirs); |
969 | |
1060 | |
970 | my $statgrp = add $grp aio_group sub { |
1061 | my $statgrp = add $grp aio_group sub { |
971 | $grp->result (\@dirs, \@nondirs); |
1062 | $grp->result (\@dirs, \@nondirs); |
972 | }; |
1063 | }; |
973 | |
1064 | |
974 | limit $statgrp $maxreq; |
1065 | limit $statgrp $maxreq; |
975 | feed $statgrp sub { |
1066 | feed $statgrp sub { |
976 | return unless @$entries; |
1067 | return unless @$entries; |
977 | my $entry = shift @$entries; |
1068 | my $entry = shift @$entries; |
978 | |
1069 | |
979 | aioreq_pri $pri; |
1070 | aioreq_pri $pri; |
|
|
1071 | $wd->[1] = "$entry/."; |
980 | add $statgrp aio_stat "$path/$entry/.", sub { |
1072 | add $statgrp aio_stat $wd, sub { |
981 | if ($_[0] < 0) { |
1073 | if ($_[0] < 0) { |
982 | push @nondirs, $entry; |
1074 | push @nondirs, $entry; |
983 | } else { |
1075 | } else { |
984 | # need to check for real directory |
1076 | # need to check for real directory |
985 | aioreq_pri $pri; |
1077 | aioreq_pri $pri; |
|
|
1078 | $wd->[1] = $entry; |
986 | add $statgrp aio_lstat "$path/$entry", sub { |
1079 | add $statgrp aio_lstat $wd, sub { |
987 | if (-d _) { |
1080 | if (-d _) { |
988 | push @dirs, $entry; |
1081 | push @dirs, $entry; |
989 | |
1082 | |
990 | unless (--$ndirs) { |
1083 | unless (--$ndirs) { |
991 | push @nondirs, @$entries; |
1084 | push @nondirs, @$entries; |
992 | feed $statgrp; |
1085 | feed $statgrp; |
|
|
1086 | } |
|
|
1087 | } else { |
|
|
1088 | push @nondirs, $entry; |
993 | } |
1089 | } |
994 | } else { |
|
|
995 | push @nondirs, $entry; |
|
|
996 | } |
1090 | } |
997 | } |
1091 | } |
998 | } |
1092 | }; |
999 | }; |
1093 | }; |
1000 | }; |
1094 | }; |
1001 | }; |
1095 | }; |
1002 | }; |
1096 | }; |
1003 | }; |
1097 | }; |
1004 | |
1098 | |
1005 | $grp |
1099 | $grp |
1006 | } |
1100 | } |
1007 | |
1101 | |
1008 | =item aio_rmtree $path, $callback->($status) |
1102 | =item aio_rmtree $pathname, $callback->($status) |
1009 | |
1103 | |
1010 | Delete a directory tree starting (and including) C<$path>, return the |
1104 | Delete a directory tree starting (and including) C<$path>, return the |
1011 | status of the final C<rmdir> only. This is a composite request that |
1105 | status of the final C<rmdir> only. This is a composite request that |
1012 | uses C<aio_scandir> to recurse into and rmdir directories, and unlink |
1106 | uses C<aio_scandir> to recurse into and rmdir directories, and unlink |
1013 | everything else. |
1107 | everything else. |
… | |
… | |
1055 | callback with the fdatasync result code. |
1149 | callback with the fdatasync result code. |
1056 | |
1150 | |
1057 | If this call isn't available because your OS lacks it or it couldn't be |
1151 | If this call isn't available because your OS lacks it or it couldn't be |
1058 | detected, it will be emulated by calling C<fsync> instead. |
1152 | detected, it will be emulated by calling C<fsync> instead. |
1059 | |
1153 | |
|
|
1154 | =item aio_syncfs $fh, $callback->($status) |
|
|
1155 | |
|
|
1156 | Asynchronously call the syncfs syscall to sync the filesystem associated |
|
|
1157 | to the given filehandle and call the callback with the syncfs result |
|
|
1158 | code. If syncfs is not available, calls sync(), but returns C<-1> and sets |
|
|
1159 | errno to C<ENOSYS> nevertheless. |
|
|
1160 | |
1060 | =item aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status) |
1161 | =item aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status) |
1061 | |
1162 | |
1062 | Sync the data portion of the file specified by C<$offset> and C<$length> |
1163 | Sync the data portion of the file specified by C<$offset> and C<$length> |
1063 | to disk (but NOT the metadata), by calling the Linux-specific |
1164 | to disk (but NOT the metadata), by calling the Linux-specific |
1064 | sync_file_range call. If sync_file_range is not available or it returns |
1165 | sync_file_range call. If sync_file_range is not available or it returns |
… | |
… | |
1067 | C<$flags> can be a combination of C<IO::AIO::SYNC_FILE_RANGE_WAIT_BEFORE>, |
1168 | C<$flags> can be a combination of C<IO::AIO::SYNC_FILE_RANGE_WAIT_BEFORE>, |
1068 | C<IO::AIO::SYNC_FILE_RANGE_WRITE> and |
1169 | C<IO::AIO::SYNC_FILE_RANGE_WRITE> and |
1069 | C<IO::AIO::SYNC_FILE_RANGE_WAIT_AFTER>: refer to the sync_file_range |
1170 | C<IO::AIO::SYNC_FILE_RANGE_WAIT_AFTER>: refer to the sync_file_range |
1070 | manpage for details. |
1171 | manpage for details. |
1071 | |
1172 | |
1072 | =item aio_pathsync $path, $callback->($status) |
1173 | =item aio_pathsync $pathname, $callback->($status) |
1073 | |
1174 | |
1074 | This request tries to open, fsync and close the given path. This is a |
1175 | This request tries to open, fsync and close the given path. This is a |
1075 | composite request intended to sync directories after directory operations |
1176 | composite request intended to sync directories after directory operations |
1076 | (E.g. rename). This might not work on all operating systems or have any |
1177 | (E.g. rename). This might not work on all operating systems or have any |
1077 | specific effect, but usually it makes sure that directory changes get |
1178 | specific effect, but usually it makes sure that directory changes get |
… | |
… | |
1174 | |
1275 | |
1175 | Example: asynchronously lock all current and future pages into memory. |
1276 | Example: asynchronously lock all current and future pages into memory. |
1176 | |
1277 | |
1177 | aio_mlockall IO::AIO::MCL_FUTURE; |
1278 | aio_mlockall IO::AIO::MCL_FUTURE; |
1178 | |
1279 | |
|
|
1280 | =item aio_fiemap $fh, $start, $length, $flags, $count, $cb->(\@extents) |
|
|
1281 | |
|
|
1282 | Queries the extents of the given file (by calling the Linux FIEMAP ioctl, |
|
|
1283 | see L<http://cvs.schmorp.de/IO-AIO/doc/fiemap.txt> for details). If the |
|
|
1284 | C<ioctl> is not available on your OS, then this request will fail with |
|
|
1285 | C<ENOSYS>. |
|
|
1286 | |
|
|
1287 | C<$start> is the starting offset to query extents for, C<$length> is the |
|
|
1288 | size of the range to query - if it is C<undef>, then the whole file will |
|
|
1289 | be queried. |
|
|
1290 | |
|
|
1291 | C<$flags> is a combination of flags (C<IO::AIO::FIEMAP_FLAG_SYNC> or |
|
|
1292 | C<IO::AIO::FIEMAP_FLAG_XATTR> - C<IO::AIO::FIEMAP_FLAGS_COMPAT> is also |
|
|
1293 | exported), and is normally C<0> or C<IO::AIO::FIEMAP_FLAG_SYNC> to query |
|
|
1294 | the data portion. |
|
|
1295 | |
|
|
1296 | C<$count> is the maximum number of extent records to return. If it is |
|
|
1297 | C<undef>, then IO::AIO queries all extents of the range. As a very special |
|
|
1298 | case, if it is C<0>, then the callback receives the number of extents |
|
|
1299 | instead of the extents themselves (which is unreliable, see below). |
|
|
1300 | |
|
|
1301 | If an error occurs, the callback receives no arguments. The special |
|
|
1302 | C<errno> value C<IO::AIO::EBADR> is available to test for flag errors. |
|
|
1303 | |
|
|
1304 | Otherwise, the callback receives an array reference with extent |
|
|
1305 | structures. Each extent structure is an array reference itself, with the |
|
|
1306 | following members: |
|
|
1307 | |
|
|
1308 | [$logical, $physical, $length, $flags] |
|
|
1309 | |
|
|
1310 | Flags is any combination of the following flag values (typically either C<0> |
|
|
1311 | or C<IO::AIO::FIEMAP_EXTENT_LAST> (1)): |
|
|
1312 | |
|
|
1313 | C<IO::AIO::FIEMAP_EXTENT_LAST>, C<IO::AIO::FIEMAP_EXTENT_UNKNOWN>, |
|
|
1314 | C<IO::AIO::FIEMAP_EXTENT_DELALLOC>, C<IO::AIO::FIEMAP_EXTENT_ENCODED>, |
|
|
1315 | C<IO::AIO::FIEMAP_EXTENT_DATA_ENCRYPTED>, C<IO::AIO::FIEMAP_EXTENT_NOT_ALIGNED>, |
|
|
1316 | C<IO::AIO::FIEMAP_EXTENT_DATA_INLINE>, C<IO::AIO::FIEMAP_EXTENT_DATA_TAIL>, |
|
|
1317 | C<IO::AIO::FIEMAP_EXTENT_UNWRITTEN>, C<IO::AIO::FIEMAP_EXTENT_MERGED> or |
|
|
1318 | C<IO::AIO::FIEMAP_EXTENT_SHARED>. |
|
|
1319 | |
|
|
1320 | At the time of this writing (Linux 3.2), this requets is unreliable unless |
|
|
1321 | C<$count> is C<undef>, as the kernel has all sorts of bugs preventing |
|
|
1322 | it to return all extents of a range for files with large number of |
|
|
1323 | extents. The code works around all these issues if C<$count> is undef. |
|
|
1324 | |
1179 | =item aio_group $callback->(...) |
1325 | =item aio_group $callback->(...) |
1180 | |
1326 | |
1181 | This is a very special aio request: Instead of doing something, it is a |
1327 | This is a very special aio request: Instead of doing something, it is a |
1182 | container for other aio requests, which is useful if you want to bundle |
1328 | container for other aio requests, which is useful if you want to bundle |
1183 | many requests into a single, composite, request with a definite callback |
1329 | many requests into a single, composite, request with a definite callback |
… | |
… | |
1219 | like sleep and file handle readable/writable, the overhead this creates is |
1365 | like sleep and file handle readable/writable, the overhead this creates is |
1220 | immense (it blocks a thread for a long time) so do not use this function |
1366 | immense (it blocks a thread for a long time) so do not use this function |
1221 | except to put your application under artificial I/O pressure. |
1367 | except to put your application under artificial I/O pressure. |
1222 | |
1368 | |
1223 | =back |
1369 | =back |
|
|
1370 | |
|
|
1371 | |
|
|
1372 | =head2 IO::AIO::WD - multiple working directories |
|
|
1373 | |
|
|
1374 | Your process only has one current working directory, which is used by all |
|
|
1375 | threads. This makes it hard to use relative paths (some other component |
|
|
1376 | could call C<chdir> at any time, and it is hard to control when the path |
|
|
1377 | will be used by IO::AIO). |
|
|
1378 | |
|
|
1379 | One solution for this is to always use absolute paths. This usually works, |
|
|
1380 | but can be quite slow (the kernel has to walk the whole path on every |
|
|
1381 | access), and can also be a hassle to implement. |
|
|
1382 | |
|
|
1383 | Newer POSIX systems have a number of functions (openat, fdopendir, |
|
|
1384 | futimensat and so on) that make it possible to specify working directories |
|
|
1385 | per operation. |
|
|
1386 | |
|
|
1387 | For portability, and because the clowns who "designed", or shall I write, |
|
|
1388 | perpetrated this new interface were obviously half-drunk, this abstraction |
|
|
1389 | cannot be perfect, though. |
|
|
1390 | |
|
|
1391 | IO::AIO allows you to convert directory paths into a so-called IO::AIO::WD |
|
|
1392 | object. This object stores the canonicalised, absolute version of the |
|
|
1393 | path, and on systems that allow it, also a directory file descriptor. |
|
|
1394 | |
|
|
1395 | Everywhere where a pathname is accepted by IO::AIO (e.g. in C<aio_stat> |
|
|
1396 | or C<aio_unlink>), one can specify an array reference with an IO::AIO::WD |
|
|
1397 | object and a pathname instead (or the IO::AIO::WD object alone, which |
|
|
1398 | gets interpreted as C<[$wd, "."]>). If the pathname is absolute, the |
|
|
1399 | IO::AIO::WD object is ignored, otherwise the pathname is resolved relative |
|
|
1400 | to that IO::AIO::WD object. |
|
|
1401 | |
|
|
1402 | For example, to get a wd object for F</etc> and then stat F<passwd> |
|
|
1403 | inside, you would write: |
|
|
1404 | |
|
|
1405 | aio_wd "/etc", sub { |
|
|
1406 | my $etcdir = shift; |
|
|
1407 | |
|
|
1408 | # although $etcdir can be undef on error, there is generally no reason |
|
|
1409 | # to check for errors here, as aio_stat will fail with ENOENT |
|
|
1410 | # when $etcdir is undef. |
|
|
1411 | |
|
|
1412 | aio_stat [$etcdir, "passwd"], sub { |
|
|
1413 | # yay |
|
|
1414 | }; |
|
|
1415 | }; |
|
|
1416 | |
|
|
1417 | That C<aio_wd> is a request and not a normal function shows that creating |
|
|
1418 | an IO::AIO::WD object is itself a potentially blocking operation, which is |
|
|
1419 | why it is done asynchronously. |
|
|
1420 | |
|
|
1421 | To stat the directory obtained with C<aio_wd> above, one could write |
|
|
1422 | either of the following three request calls: |
|
|
1423 | |
|
|
1424 | aio_lstat "/etc" , sub { ... # pathname as normal string |
|
|
1425 | aio_lstat [$wd, "."], sub { ... # "." relative to $wd (i.e. $wd itself) |
|
|
1426 | aio_lstat $wd , sub { ... # shorthand for the previous |
|
|
1427 | |
|
|
1428 | As with normal pathnames, IO::AIO keeps a copy of the working directory |
|
|
1429 | object and the pathname string, so you could write the following without |
|
|
1430 | causing any issues due to C<$path> getting reused: |
|
|
1431 | |
|
|
1432 | my $path = [$wd, undef]; |
|
|
1433 | |
|
|
1434 | for my $name (qw(abc def ghi)) { |
|
|
1435 | $path->[1] = $name; |
|
|
1436 | aio_stat $path, sub { |
|
|
1437 | # ... |
|
|
1438 | }; |
|
|
1439 | } |
|
|
1440 | |
|
|
1441 | There are some caveats: when directories get renamed (or deleted), the |
|
|
1442 | pathname string doesn't change, so will point to the new directory (or |
|
|
1443 | nowhere at all), while the directory fd, if available on the system, |
|
|
1444 | will still point to the original directory. Most functions accepting a |
|
|
1445 | pathname will use the directory fd on newer systems, and the string on |
|
|
1446 | older systems. Some functions (such as realpath) will always rely on the |
|
|
1447 | string form of the pathname. |
|
|
1448 | |
|
|
1449 | So this fucntionality is mainly useful to get some protection against |
|
|
1450 | C<chdir>, to easily get an absolute path out of a relative path for future |
|
|
1451 | reference, and to speed up doing many operations in the same directory |
|
|
1452 | (e.g. when stat'ing all files in a directory). |
|
|
1453 | |
|
|
1454 | The following functions implement this working directory abstraction: |
|
|
1455 | |
|
|
1456 | =over 4 |
|
|
1457 | |
|
|
1458 | =item aio_wd $pathname, $callback->($wd) |
|
|
1459 | |
|
|
1460 | Asynchonously canonicalise the given pathname and convert it to an |
|
|
1461 | IO::AIO::WD object representing it. If possible and supported on the |
|
|
1462 | system, also open a directory fd to speed up pathname resolution relative |
|
|
1463 | to this working directory. |
|
|
1464 | |
|
|
1465 | If something goes wrong, then C<undef> is passwd to the callback instead |
|
|
1466 | of a working directory object and C<$!> is set appropriately. Since |
|
|
1467 | passing C<undef> as working directory component of a pathname fails the |
|
|
1468 | request with C<ENOENT>, there is often no need for error checking in the |
|
|
1469 | C<aio_wd> callback, as future requests using the value will fail in the |
|
|
1470 | expected way. |
|
|
1471 | |
|
|
1472 | If this call isn't available because your OS lacks it or it couldn't be |
|
|
1473 | detected, it will be emulated by calling C<fsync> instead. |
|
|
1474 | |
|
|
1475 | =item IO::AIO::CWD |
|
|
1476 | |
|
|
1477 | This is a compiletime constant (object) that represents the process |
|
|
1478 | current working directory. |
|
|
1479 | |
|
|
1480 | Specifying this object as working directory object for a pathname is as |
|
|
1481 | if the pathname would be specified directly, without a directory object, |
|
|
1482 | e.g., these calls are functionally identical: |
|
|
1483 | |
|
|
1484 | aio_stat "somefile", sub { ... }; |
|
|
1485 | aio_stat [IO::AIO::CWD, "somefile"], sub { ... }; |
|
|
1486 | |
|
|
1487 | =back |
|
|
1488 | |
1224 | |
1489 | |
1225 | =head2 IO::AIO::REQ CLASS |
1490 | =head2 IO::AIO::REQ CLASS |
1226 | |
1491 | |
1227 | All non-aggregate C<aio_*> functions return an object of this class when |
1492 | All non-aggregate C<aio_*> functions return an object of this class when |
1228 | called in non-void context. |
1493 | called in non-void context. |
… | |
… | |
1346 | |
1611 | |
1347 | Sets a feeder/generator on this group: every group can have an attached |
1612 | Sets a feeder/generator on this group: every group can have an attached |
1348 | generator that generates requests if idle. The idea behind this is that, |
1613 | generator that generates requests if idle. The idea behind this is that, |
1349 | although you could just queue as many requests as you want in a group, |
1614 | although you could just queue as many requests as you want in a group, |
1350 | this might starve other requests for a potentially long time. For example, |
1615 | this might starve other requests for a potentially long time. For example, |
1351 | C<aio_scandir> might generate hundreds of thousands C<aio_stat> requests, |
1616 | C<aio_scandir> might generate hundreds of thousands of C<aio_stat> |
1352 | delaying any later requests for a long time. |
1617 | requests, delaying any later requests for a long time. |
1353 | |
1618 | |
1354 | To avoid this, and allow incremental generation of requests, you can |
1619 | To avoid this, and allow incremental generation of requests, you can |
1355 | instead a group and set a feeder on it that generates those requests. The |
1620 | instead a group and set a feeder on it that generates those requests. The |
1356 | feed callback will be called whenever there are few enough (see C<limit>, |
1621 | feed callback will be called whenever there are few enough (see C<limit>, |
1357 | below) requests active in the group itself and is expected to queue more |
1622 | below) requests active in the group itself and is expected to queue more |
… | |
… | |
1406 | |
1671 | |
1407 | See C<poll_cb> for an example. |
1672 | See C<poll_cb> for an example. |
1408 | |
1673 | |
1409 | =item IO::AIO::poll_cb |
1674 | =item IO::AIO::poll_cb |
1410 | |
1675 | |
1411 | Process some outstanding events on the result pipe. You have to call this |
1676 | Process some outstanding events on the result pipe. You have to call |
1412 | regularly. Returns C<0> if all events could be processed, or C<-1> if it |
1677 | this regularly. Returns C<0> if all events could be processed (or there |
1413 | returned earlier for whatever reason. Returns immediately when no events |
1678 | were no events to process), or C<-1> if it returned earlier for whatever |
1414 | are outstanding. The amount of events processed depends on the settings of |
1679 | reason. Returns immediately when no events are outstanding. The amount of |
1415 | C<IO::AIO::max_poll_req> and C<IO::AIO::max_poll_time>. |
1680 | events processed depends on the settings of C<IO::AIO::max_poll_req> and |
|
|
1681 | C<IO::AIO::max_poll_time>. |
1416 | |
1682 | |
1417 | If not all requests were processed for whatever reason, the filehandle |
1683 | If not all requests were processed for whatever reason, the filehandle |
1418 | will still be ready when C<poll_cb> returns, so normally you don't have to |
1684 | will still be ready when C<poll_cb> returns, so normally you don't have to |
1419 | do anything special to have it called later. |
1685 | do anything special to have it called later. |
|
|
1686 | |
|
|
1687 | Apart from calling C<IO::AIO::poll_cb> when the event filehandle becomes |
|
|
1688 | ready, it can be beneficial to call this function from loops which submit |
|
|
1689 | a lot of requests, to make sure the results get processed when they become |
|
|
1690 | available and not just when the loop is finished and the event loop takes |
|
|
1691 | over again. This function returns very fast when there are no outstanding |
|
|
1692 | requests. |
1420 | |
1693 | |
1421 | Example: Install an Event watcher that automatically calls |
1694 | Example: Install an Event watcher that automatically calls |
1422 | IO::AIO::poll_cb with high priority (more examples can be found in the |
1695 | IO::AIO::poll_cb with high priority (more examples can be found in the |
1423 | SYNOPSIS section, at the top of this document): |
1696 | SYNOPSIS section, at the top of this document): |
1424 | |
1697 | |
… | |
… | |
1547 | Sets the minimum idle timeout (default 10) after which worker threads are |
1820 | Sets the minimum idle timeout (default 10) after which worker threads are |
1548 | allowed to exit. SEe C<IO::AIO::max_idle>. |
1821 | allowed to exit. SEe C<IO::AIO::max_idle>. |
1549 | |
1822 | |
1550 | =item IO::AIO::max_outstanding $maxreqs |
1823 | =item IO::AIO::max_outstanding $maxreqs |
1551 | |
1824 | |
|
|
1825 | Sets the maximum number of outstanding requests to C<$nreqs>. If |
|
|
1826 | you do queue up more than this number of requests, the next call to |
|
|
1827 | C<IO::AIO::poll_cb> (and other functions calling C<poll_cb>, such as |
|
|
1828 | C<IO::AIO::flush> or C<IO::AIO::poll>) will block until the limit is no |
|
|
1829 | longer exceeded. |
|
|
1830 | |
|
|
1831 | In other words, this setting does not enforce a queue limit, but can be |
|
|
1832 | used to make poll functions block if the limit is exceeded. |
|
|
1833 | |
1552 | This is a very bad function to use in interactive programs because it |
1834 | This is a very bad function to use in interactive programs because it |
1553 | blocks, and a bad way to reduce concurrency because it is inexact: Better |
1835 | blocks, and a bad way to reduce concurrency because it is inexact: Better |
1554 | use an C<aio_group> together with a feed callback. |
1836 | use an C<aio_group> together with a feed callback. |
1555 | |
1837 | |
1556 | Sets the maximum number of outstanding requests to C<$nreqs>. If you |
1838 | It's main use is in scripts without an event loop - when you want to stat |
1557 | do queue up more than this number of requests, the next call to the |
1839 | a lot of files, you can write somehting like this: |
1558 | C<poll_cb> (and C<poll_some> and other functions calling C<poll_cb>) |
|
|
1559 | function will block until the limit is no longer exceeded. |
|
|
1560 | |
1840 | |
1561 | The default value is very large, so there is no practical limit on the |
1841 | IO::AIO::max_outstanding 32; |
1562 | number of outstanding requests. |
|
|
1563 | |
1842 | |
1564 | You can still queue as many requests as you want. Therefore, |
1843 | for my $path (...) { |
1565 | C<max_outstanding> is mainly useful in simple scripts (with low values) or |
1844 | aio_stat $path , ...; |
1566 | as a stop gap to shield against fatal memory overflow (with large values). |
1845 | IO::AIO::poll_cb; |
|
|
1846 | } |
|
|
1847 | |
|
|
1848 | IO::AIO::flush; |
|
|
1849 | |
|
|
1850 | The call to C<poll_cb> inside the loop will normally return instantly, but |
|
|
1851 | as soon as more thna C<32> reqeusts are in-flight, it will block until |
|
|
1852 | some requests have been handled. This keeps the loop from pushing a large |
|
|
1853 | number of C<aio_stat> requests onto the queue. |
|
|
1854 | |
|
|
1855 | The default value for C<max_outstanding> is very large, so there is no |
|
|
1856 | practical limit on the number of outstanding requests. |
1567 | |
1857 | |
1568 | =back |
1858 | =back |
1569 | |
1859 | |
1570 | =head3 STATISTICAL INFORMATION |
1860 | =head3 STATISTICAL INFORMATION |
1571 | |
1861 | |
… | |
… | |
1611 | |
1901 | |
1612 | =item IO::AIO::fadvise $fh, $offset, $len, $advice |
1902 | =item IO::AIO::fadvise $fh, $offset, $len, $advice |
1613 | |
1903 | |
1614 | Simply calls the C<posix_fadvise> function (see its |
1904 | Simply calls the C<posix_fadvise> function (see its |
1615 | manpage for details). The following advice constants are |
1905 | manpage for details). The following advice constants are |
1616 | avaiable: C<IO::AIO::FADV_NORMAL>, C<IO::AIO::FADV_SEQUENTIAL>, |
1906 | available: C<IO::AIO::FADV_NORMAL>, C<IO::AIO::FADV_SEQUENTIAL>, |
1617 | C<IO::AIO::FADV_RANDOM>, C<IO::AIO::FADV_NOREUSE>, |
1907 | C<IO::AIO::FADV_RANDOM>, C<IO::AIO::FADV_NOREUSE>, |
1618 | C<IO::AIO::FADV_WILLNEED>, C<IO::AIO::FADV_DONTNEED>. |
1908 | C<IO::AIO::FADV_WILLNEED>, C<IO::AIO::FADV_DONTNEED>. |
1619 | |
1909 | |
1620 | On systems that do not implement C<posix_fadvise>, this function returns |
1910 | On systems that do not implement C<posix_fadvise>, this function returns |
1621 | ENOSYS, otherwise the return value of C<posix_fadvise>. |
1911 | ENOSYS, otherwise the return value of C<posix_fadvise>. |
1622 | |
1912 | |
1623 | =item IO::AIO::madvise $scalar, $offset, $len, $advice |
1913 | =item IO::AIO::madvise $scalar, $offset, $len, $advice |
1624 | |
1914 | |
1625 | Simply calls the C<posix_madvise> function (see its |
1915 | Simply calls the C<posix_madvise> function (see its |
1626 | manpage for details). The following advice constants are |
1916 | manpage for details). The following advice constants are |
1627 | avaiable: C<IO::AIO::MADV_NORMAL>, C<IO::AIO::MADV_SEQUENTIAL>, |
1917 | available: C<IO::AIO::MADV_NORMAL>, C<IO::AIO::MADV_SEQUENTIAL>, |
1628 | C<IO::AIO::MADV_RANDOM>, C<IO::AIO::MADV_WILLNEED>, C<IO::AIO::MADV_DONTNEED>. |
1918 | C<IO::AIO::MADV_RANDOM>, C<IO::AIO::MADV_WILLNEED>, C<IO::AIO::MADV_DONTNEED>. |
1629 | |
1919 | |
1630 | On systems that do not implement C<posix_madvise>, this function returns |
1920 | On systems that do not implement C<posix_madvise>, this function returns |
1631 | ENOSYS, otherwise the return value of C<posix_madvise>. |
1921 | ENOSYS, otherwise the return value of C<posix_madvise>. |
1632 | |
1922 | |
1633 | =item IO::AIO::mprotect $scalar, $offset, $len, $protect |
1923 | =item IO::AIO::mprotect $scalar, $offset, $len, $protect |
1634 | |
1924 | |
1635 | Simply calls the C<mprotect> function on the preferably AIO::mmap'ed |
1925 | Simply calls the C<mprotect> function on the preferably AIO::mmap'ed |
1636 | $scalar (see its manpage for details). The following protect |
1926 | $scalar (see its manpage for details). The following protect |
1637 | constants are avaiable: C<IO::AIO::PROT_NONE>, C<IO::AIO::PROT_READ>, |
1927 | constants are available: C<IO::AIO::PROT_NONE>, C<IO::AIO::PROT_READ>, |
1638 | C<IO::AIO::PROT_WRITE>, C<IO::AIO::PROT_EXEC>. |
1928 | C<IO::AIO::PROT_WRITE>, C<IO::AIO::PROT_EXEC>. |
1639 | |
1929 | |
1640 | On systems that do not implement C<mprotect>, this function returns |
1930 | On systems that do not implement C<mprotect>, this function returns |
1641 | ENOSYS, otherwise the return value of C<mprotect>. |
1931 | ENOSYS, otherwise the return value of C<mprotect>. |
1642 | |
1932 | |
1643 | =item IO::AIO::mmap $scalar, $length, $prot, $flags, $fh[, $offset] |
1933 | =item IO::AIO::mmap $scalar, $length, $prot, $flags, $fh[, $offset] |
1644 | |
1934 | |
1645 | Memory-maps a file (or anonymous memory range) and attaches it to the |
1935 | Memory-maps a file (or anonymous memory range) and attaches it to the |
1646 | given C<$scalar>, which will act like a string scalar. |
1936 | given C<$scalar>, which will act like a string scalar. Returns true on |
|
|
1937 | success, and false otherwise. |
1647 | |
1938 | |
1648 | The only operations allowed on the scalar are C<substr>/C<vec> that don't |
1939 | The only operations allowed on the scalar are C<substr>/C<vec> that don't |
1649 | change the string length, and most read-only operations such as copying it |
1940 | change the string length, and most read-only operations such as copying it |
1650 | or searching it with regexes and so on. |
1941 | or searching it with regexes and so on. |
1651 | |
1942 | |
… | |
… | |
1704 | Calls the C<munlockall> function. |
1995 | Calls the C<munlockall> function. |
1705 | |
1996 | |
1706 | On systems that do not implement C<munlockall>, this function returns |
1997 | On systems that do not implement C<munlockall>, this function returns |
1707 | ENOSYS, otherwise the return value of C<munlockall>. |
1998 | ENOSYS, otherwise the return value of C<munlockall>. |
1708 | |
1999 | |
|
|
2000 | =item IO::AIO::splice $r_fh, $r_off, $w_fh, $w_off, $length, $flags |
|
|
2001 | |
|
|
2002 | Calls the GNU/Linux C<splice(2)> syscall, if available. If C<$r_off> or |
|
|
2003 | C<$w_off> are C<undef>, then C<NULL> is passed for these, otherwise they |
|
|
2004 | should be the file offset. |
|
|
2005 | |
|
|
2006 | C<$r_fh> and C<$w_fh> should not refer to the same file, as splice might |
|
|
2007 | silently corrupt the data in this case. |
|
|
2008 | |
|
|
2009 | The following symbol flag values are available: C<IO::AIO::SPLICE_F_MOVE>, |
|
|
2010 | C<IO::AIO::SPLICE_F_NONBLOCK>, C<IO::AIO::SPLICE_F_MORE> and |
|
|
2011 | C<IO::AIO::SPLICE_F_GIFT>. |
|
|
2012 | |
|
|
2013 | See the C<splice(2)> manpage for details. |
|
|
2014 | |
|
|
2015 | =item IO::AIO::tee $r_fh, $w_fh, $length, $flags |
|
|
2016 | |
|
|
2017 | Calls the GNU/Linux C<tee(2)> syscall, see it's manpage and the |
|
|
2018 | description for C<IO::AIO::splice> above for details. |
|
|
2019 | |
1709 | =back |
2020 | =back |
1710 | |
2021 | |
1711 | =cut |
2022 | =cut |
1712 | |
2023 | |
1713 | min_parallel 8; |
2024 | min_parallel 8; |
… | |
… | |
1747 | Danga::Socket->AddOtherFds (IO::AIO::poll_fileno => |
2058 | Danga::Socket->AddOtherFds (IO::AIO::poll_fileno => |
1748 | \&IO::AIO::poll_cb); |
2059 | \&IO::AIO::poll_cb); |
1749 | |
2060 | |
1750 | =head2 FORK BEHAVIOUR |
2061 | =head2 FORK BEHAVIOUR |
1751 | |
2062 | |
1752 | This module should do "the right thing" when the process using it forks: |
2063 | Usage of pthreads in a program changes the semantics of fork |
|
|
2064 | considerably. Specifically, only async-safe functions can be called after |
|
|
2065 | fork. Perl doesn't know about this, so in general, you cannot call fork |
|
|
2066 | with defined behaviour in perl if pthreads are involved. IO::AIO uses |
|
|
2067 | pthreads, so this applies, but many other extensions and (for inexplicable |
|
|
2068 | reasons) perl itself often is linked against pthreads, so this limitation |
|
|
2069 | applies to quite a lot of perls. |
1753 | |
2070 | |
1754 | Before the fork, IO::AIO enters a quiescent state where no requests |
2071 | This module no longer tries to fight your OS, or POSIX. That means IO::AIO |
1755 | can be added in other threads and no results will be processed. After |
2072 | only works in the process that loaded it. Forking is fully supported, but |
1756 | the fork the parent simply leaves the quiescent state and continues |
2073 | using IO::AIO in the child is not. |
1757 | request/result processing, while the child frees the request/result queue |
|
|
1758 | (so that the requests started before the fork will only be handled in the |
|
|
1759 | parent). Threads will be started on demand until the limit set in the |
|
|
1760 | parent process has been reached again. |
|
|
1761 | |
2074 | |
1762 | In short: the parent will, after a short pause, continue as if fork had |
2075 | You might get around by not I<using> IO::AIO before (or after) |
1763 | not been called, while the child will act as if IO::AIO has not been used |
2076 | forking. You could also try to call the L<IO::AIO::reinit> function in the |
1764 | yet. |
2077 | child: |
|
|
2078 | |
|
|
2079 | =over 4 |
|
|
2080 | |
|
|
2081 | =item IO::AIO::reinit |
|
|
2082 | |
|
|
2083 | Abandons all current requests and I/O threads and simply reinitialises all |
|
|
2084 | data structures. This is not an operation supported by any standards, but |
|
|
2085 | happens to work on GNU/Linux and some newer BSD systems. |
|
|
2086 | |
|
|
2087 | The only reasonable use for this function is to call it after forking, if |
|
|
2088 | C<IO::AIO> was used in the parent. Calling it while IO::AIO is active in |
|
|
2089 | the process will result in undefined behaviour. Calling it at any time |
|
|
2090 | will also result in any undefined (by POSIX) behaviour. |
|
|
2091 | |
|
|
2092 | =back |
1765 | |
2093 | |
1766 | =head2 MEMORY USAGE |
2094 | =head2 MEMORY USAGE |
1767 | |
2095 | |
1768 | Per-request usage: |
2096 | Per-request usage: |
1769 | |
2097 | |