--- IO-AIO/AIO.pm 2005/08/17 04:47:02 1.29 +++ IO-AIO/AIO.pm 2005/08/28 11:05:50 1.39 @@ -65,11 +65,13 @@ use Fcntl (); BEGIN { - $VERSION = 1.2; + $VERSION = 1.6; - @EXPORT = qw(aio_read aio_write aio_open aio_close aio_stat aio_lstat aio_unlink - aio_rmdir aio_symlink aio_fsync aio_fdatasync aio_readahead); - @EXPORT_OK = qw(poll_fileno poll_cb min_parallel max_parallel max_outstanding nreqs); + @EXPORT = qw(aio_sendfile aio_read aio_write aio_open aio_close aio_stat + aio_lstat aio_unlink aio_rmdir aio_readdir aio_symlink + aio_fsync aio_fdatasync aio_readahead); + @EXPORT_OK = qw(poll_fileno poll_cb min_parallel max_parallel + max_outstanding nreqs); require XSLoader; XSLoader::load IO::AIO, $VERSION; @@ -152,6 +154,10 @@ callback without the actual number of bytes read (or -1 on error, just like the syscall). +The C<$data> scalar I be modified in any way while the request +is outstanding. Modifying it can result in segfaults or WW3 (if the +necessary/optional hardware is installed). + Example: Read 15 bytes at offset 7 into scalar C<$buffer>, starting at offset C<0> within the scalar: @@ -160,6 +166,29 @@ print "read $_[0] bytes: <$buffer>\n"; }; +=item aio_sendfile $out_fh, $in_fh, $in_offset, $length, $callback + +Tries to copy C<$length> bytes from C<$in_fh> to C<$out_fh>. It starts +reading at byte offset C<$in_offset>, and starts writing at the current +file offset of C<$out_fh>. Because of that, it is not safe to issue more +than one C per C<$out_fh>, as they will interfere with each +other. + +This call tries to make use of a native C syscall to provide +zero-copy operation. For this to work, C<$out_fh> should refer to a +socket, and C<$in_fh> should refer to mmap'able file. + +If the native sendfile call fails or is not implemented, it will be +emulated, so you can call C on any type of filehandle +regardless of the limitations of the operating system. + +Please note, however, that C can read more bytes from +C<$in_fh> than are written, and there is no way to find out how many +bytes have been read from C alone, as C only +provides the number of bytes written to C<$out_fh>. Only if the result +value equals C<$length> one can assume that C<$length> bytes have been +read. + =item aio_readahead $fh,$offset,$length, $callback C populates the page cache with data from a file so that @@ -206,6 +235,15 @@ Asynchronously rmdir (delete) a directory and call the callback with the result code. +=item aio_readdir $pathname $callback + +Unlike the POSIX call of the same name, C reads an entire +directory (i.e. opendir + readdir + closedir). The entries will not be +sorted, and will B include the C<.> and C<..> entries. + +The callback a single argument which is either C or an array-ref +with the filenames. + =item aio_fsync $fh, $callback Asynchronously call fsync on the given filehandle and call the callback @@ -285,24 +323,29 @@ =item IO::AIO::min_parallel $nthreads -Set the minimum number of AIO threads to C<$nthreads>. The default is -C<1>, which means a single asynchronous operation can be done at one time +Set the minimum number of AIO threads to C<$nthreads>. The current default +is C<4>, which means four asynchronous operations can be done at one time (the number of outstanding operations, however, is unlimited). +IO::AIO starts threads only on demand, when an AIO request is queued and +no free thread exists. + It is recommended to keep the number of threads low, as some Linux kernel versions will scale negatively with the number of threads (higher parallelity => MUCH higher latency). With current Linux 2.6 versions, 4-32 threads should be fine. -Under normal circumstances you don't need to call this function, as this -module automatically starts some threads (the exact number might change, -and is currently 4). +Under most circumstances you don't need to call this function, as the +module selects a default that is suitable for low to moderate load. =item IO::AIO::max_parallel $nthreads -Sets the maximum number of AIO threads to C<$nthreads>. If more than -the specified number of threads are currently running, kill them. This -function blocks until the limit is reached. +Sets the maximum number of AIO threads to C<$nthreads>. If more than the +specified number of threads are currently running, this function kills +them. This function blocks until the limit is reached. + +While C<$nthreads> are zero, aio requests get queued but not executed +until the number of threads has been increased again. This module automatically runs C at program end, to ensure that all threads are killed and that there are no outstanding requests. @@ -316,7 +359,7 @@ some requests have been handled. The default is very large, so normally there is no practical limit. If you -queue up many requests in a loop it it often improves speed if you set +queue up many requests in a loop it often improves speed if you set this to a relatively low number, such as C<100>. Under normal circumstances you don't need to call this function. @@ -351,13 +394,13 @@ =head2 FORK BEHAVIOUR -Before the fork IO::AIO first handles all outstanding requests - if other -threads add requests during this period, this time is prolonged. It then -enters a quiescent state where no requests can be added in other threads -and no results will be processed. After the fork the parent simply leaves -the quiescent state and continues request processing, while the child will -free the request and result queue and start the same number of threads as -were in use by the parent. +Before the fork, IO::AIO enters a quiescent state where no requests +can be added in other threads and no results will be processed. After +the fork the parent simply leaves the quiescent state and continues +request/result processing, while the child clears the request/result +queue (so the requests started before the fork will only be handled in +the parent). Threats will be started on demand until the limit ste in the +parent process has been reached again. =head1 SEE ALSO