--- IO-AIO/AIO.pm	2008/10/05 16:56:08	1.137
+++ IO-AIO/AIO.pm	2009/04/19 19:17:59	1.144
@@ -195,12 +195,12 @@
 use base 'Exporter';
 
 BEGIN {
-   our $VERSION = '3.1';
+   our $VERSION = '3.18';
 
    our @AIO_REQ = qw(aio_sendfile aio_read aio_write aio_open aio_close
                      aio_stat aio_lstat aio_unlink aio_rmdir aio_readdir
                      aio_scandir aio_symlink aio_readlink aio_sync aio_fsync
-                     aio_fdatasync aio_pathsync aio_readahead
+                     aio_fdatasync aio_sync_file_range aio_pathsync aio_readahead
                      aio_rename aio_link aio_move aio_copy aio_group
                      aio_nop aio_mknod aio_load aio_rmtree aio_mkdir aio_chown
                      aio_chmod aio_utime aio_truncate);
@@ -211,6 +211,8 @@
                        nreqs nready npending nthreads
                        max_poll_time max_poll_reqs);
 
+   push @AIO_REQ, qw(aio_busy); # not exported
+
    @IO::AIO::GRP::ISA = 'IO::AIO::REQ';
 
    require XSLoader;
@@ -857,6 +859,18 @@
 If this call isn't available because your OS lacks it or it couldn't be
 detected, it will be emulated by calling C<fsync> instead.
 
+=item aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status)
+
+Sync the data portion of the file specified by C<$offset> and C<$length>
+to disk (but NOT the metadata), by calling the Linux-specific
+sync_file_range call. If sync_file_range is not available or it returns
+ENOSYS, then fdatasync or fsync is being substituted.
+
+C<$flags> can be a combination of C<IO::AIO::SYNC_FILE_RANGE_WAIT_BEFORE>,
+C<IO::AIO::SYNC_FILE_RANGE_WRITE> and
+C<IO::AIO::SYNC_FILE_RANGE_WAIT_AFTER>: refer to the sync_file_range
+manpage for details.
+
 =item aio_pathsync $path, $callback->($status)
 
 This request tries to open, fsync and close the given path. This is a
@@ -1062,9 +1076,9 @@
 Sets a feeder/generator on this group: every group can have an attached
 generator that generates requests if idle. The idea behind this is that,
 although you could just queue as many requests as you want in a group,
-this might starve other requests for a potentially long time.  For
-example, C<aio_scandir> might generate hundreds of thousands C<aio_stat>
-requests, delaying any later requests for a long time.
+this might starve other requests for a potentially long time. For example,
+C<aio_scandir> might generate hundreds of thousands C<aio_stat> requests,
+delaying any later requests for a long time.
 
 To avoid this, and allow incremental generation of requests, you can
 instead a group and set a feeder on it that generates those requests. The
@@ -1078,7 +1092,8 @@
 If the feed does not queue more requests when called, it will be
 automatically removed from the group.
 
-If the feed limit is C<0>, it will be set to C<2> automatically.
+If the feed limit is C<0> when this method is called, it will be set to
+C<2> automatically.
 
 Example:
 
@@ -1100,6 +1115,9 @@
 
 Setting the limit to C<0> will pause the feeding process.
 
+The default value for the limit is C<0>, but note that setting a feeder
+automatically bumps it up to C<2>.
+
 =back
 
 =head2 SUPPORT FUNCTIONS