… | |
… | |
63 | use base 'Exporter'; |
63 | use base 'Exporter'; |
64 | |
64 | |
65 | use Fcntl (); |
65 | use Fcntl (); |
66 | |
66 | |
67 | BEGIN { |
67 | BEGIN { |
68 | $VERSION = 1.5; |
68 | $VERSION = 1.6; |
69 | |
69 | |
70 | @EXPORT = qw(aio_read aio_write aio_open aio_close aio_stat aio_lstat aio_unlink |
70 | @EXPORT = qw(aio_sendfile aio_read aio_write aio_open aio_close aio_stat |
|
|
71 | aio_lstat aio_unlink aio_rmdir aio_readdir aio_symlink |
71 | aio_rmdir aio_symlink aio_fsync aio_fdatasync aio_readahead); |
72 | aio_fsync aio_fdatasync aio_readahead); |
72 | @EXPORT_OK = qw(poll_fileno poll_cb min_parallel max_parallel max_outstanding nreqs); |
73 | @EXPORT_OK = qw(poll_fileno poll_cb min_parallel max_parallel |
|
|
74 | max_outstanding nreqs); |
73 | |
75 | |
74 | require XSLoader; |
76 | require XSLoader; |
75 | XSLoader::load IO::AIO, $VERSION; |
77 | XSLoader::load IO::AIO, $VERSION; |
76 | } |
78 | } |
77 | |
79 | |
… | |
… | |
175 | This call tries to make use of a native C<sendfile> syscall to provide |
177 | This call tries to make use of a native C<sendfile> syscall to provide |
176 | zero-copy operation. For this to work, C<$out_fh> should refer to a |
178 | zero-copy operation. For this to work, C<$out_fh> should refer to a |
177 | socket, and C<$in_fh> should refer to mmap'able file. |
179 | socket, and C<$in_fh> should refer to mmap'able file. |
178 | |
180 | |
179 | If the native sendfile call fails or is not implemented, it will be |
181 | If the native sendfile call fails or is not implemented, it will be |
180 | emulated, so you can call C<aio_sendfile> on any filehandles regardless of |
182 | emulated, so you can call C<aio_sendfile> on any type of filehandle |
181 | the limitations of the OS. |
183 | regardless of the limitations of the operating system. |
182 | |
184 | |
183 | Please note, however, that C<aio_sendfile> can read more bytes from |
185 | Please note, however, that C<aio_sendfile> can read more bytes from |
184 | C<$in_fh> than are written, and there is no way to find out how many |
186 | C<$in_fh> than are written, and there is no way to find out how many |
185 | bytes have been read form C<aio_sendfile> alone, as C<aio_sendfile> only |
187 | bytes have been read from C<aio_sendfile> alone, as C<aio_sendfile> only |
186 | provides the number of bytes written to C<$out_fh>. Only if the return |
188 | provides the number of bytes written to C<$out_fh>. Only if the result |
187 | value (the value provided to the callback) equals C<$length> one can |
189 | value equals C<$length> one can assume that C<$length> bytes have been |
188 | assume that C<$length> bytes have been read. |
190 | read. |
189 | |
191 | |
190 | =item aio_readahead $fh,$offset,$length, $callback |
192 | =item aio_readahead $fh,$offset,$length, $callback |
191 | |
193 | |
192 | C<aio_readahead> populates the page cache with data from a file so that |
194 | C<aio_readahead> populates the page cache with data from a file so that |
193 | subsequent reads from that file will not block on disk I/O. The C<$offset> |
195 | subsequent reads from that file will not block on disk I/O. The C<$offset> |
… | |
… | |
231 | =item aio_rmdir $pathname, $callback |
233 | =item aio_rmdir $pathname, $callback |
232 | |
234 | |
233 | Asynchronously rmdir (delete) a directory and call the callback with the |
235 | Asynchronously rmdir (delete) a directory and call the callback with the |
234 | result code. |
236 | result code. |
235 | |
237 | |
|
|
238 | =item aio_readdir $pathname $callback |
|
|
239 | |
|
|
240 | Unlike the POSIX call of the same name, C<aio_readdir> reads an entire |
|
|
241 | directory (i.e. opendir + readdir + closedir). The entries will not be |
|
|
242 | sorted, and will B<NOT> include the C<.> and C<..> entries. |
|
|
243 | |
|
|
244 | The callback a single argument which is either C<undef> or an array-ref |
|
|
245 | with the filenames. |
|
|
246 | |
236 | =item aio_fsync $fh, $callback |
247 | =item aio_fsync $fh, $callback |
237 | |
248 | |
238 | Asynchronously call fsync on the given filehandle and call the callback |
249 | Asynchronously call fsync on the given filehandle and call the callback |
239 | with the fsync result code. |
250 | with the fsync result code. |
240 | |
251 | |