| … | |
… | |
| 510 | As native sendfile syscalls (as practically any non-POSIX interface hacked |
510 | As native sendfile syscalls (as practically any non-POSIX interface hacked |
| 511 | together in a hurry to improve benchmark numbers) tend to be rather buggy |
511 | together in a hurry to improve benchmark numbers) tend to be rather buggy |
| 512 | on many systems, this implementation tries to work around some known bugs |
512 | on many systems, this implementation tries to work around some known bugs |
| 513 | in Linux and FreeBSD kernels (probably others, too), but that might fail, |
513 | in Linux and FreeBSD kernels (probably others, too), but that might fail, |
| 514 | so you really really should check the return value of C<aio_sendfile> - |
514 | so you really really should check the return value of C<aio_sendfile> - |
| 515 | fewre bytes than expected might have been transferred. |
515 | fewer bytes than expected might have been transferred. |
| 516 | |
516 | |
| 517 | |
517 | |
| 518 | =item aio_readahead $fh,$offset,$length, $callback->($retval) |
518 | =item aio_readahead $fh,$offset,$length, $callback->($retval) |
| 519 | |
519 | |
| 520 | C<aio_readahead> populates the page cache with data from a file so that |
520 | C<aio_readahead> populates the page cache with data from a file so that |
| … | |
… | |
| 524 | whole pages, so that offset is effectively rounded down to a page boundary |
524 | whole pages, so that offset is effectively rounded down to a page boundary |
| 525 | and bytes are read up to the next page boundary greater than or equal to |
525 | and bytes are read up to the next page boundary greater than or equal to |
| 526 | (off-set+length). C<aio_readahead> does not read beyond the end of the |
526 | (off-set+length). C<aio_readahead> does not read beyond the end of the |
| 527 | file. The current file offset of the file is left unchanged. |
527 | file. The current file offset of the file is left unchanged. |
| 528 | |
528 | |
| 529 | If that syscall doesn't exist (likely if your OS isn't Linux) it will be |
529 | If that syscall doesn't exist (likely if your kernel isn't Linux) it will |
| 530 | emulated by simply reading the data, which would have a similar effect. |
530 | be emulated by simply reading the data, which would have a similar effect. |
| 531 | |
531 | |
| 532 | |
532 | |
| 533 | =item aio_stat $fh_or_path, $callback->($status) |
533 | =item aio_stat $fh_or_path, $callback->($status) |
| 534 | |
534 | |
| 535 | =item aio_lstat $fh, $callback->($status) |
535 | =item aio_lstat $fh, $callback->($status) |
