ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/IO-AIO/AIO.pm
(Generate patch)

Comparing IO-AIO/AIO.pm (file contents):
Revision 1.195 by root, Fri May 27 19:56:31 2011 UTC vs.
Revision 1.286 by root, Sun Jul 22 20:39:19 2018 UTC

1=head1 NAME 1=head1 NAME
2 2
3IO::AIO - Asynchronous Input/Output 3IO::AIO - Asynchronous/Advanced Input/Output
4 4
5=head1 SYNOPSIS 5=head1 SYNOPSIS
6 6
7 use IO::AIO; 7 use IO::AIO;
8 8
58not well-supported or restricted (GNU/Linux doesn't allow them on normal 58not well-supported or restricted (GNU/Linux doesn't allow them on normal
59files currently, for example), and they would only support aio_read and 59files currently, for example), and they would only support aio_read and
60aio_write, so the remaining functionality would have to be implemented 60aio_write, so the remaining functionality would have to be implemented
61using threads anyway. 61using threads anyway.
62 62
63In addition to asynchronous I/O, this module also exports some rather
64arcane interfaces, such as C<madvise> or linux's C<splice> system call,
65which is why the C<A> in C<AIO> can also mean I<advanced>.
66
63Although the module will work in the presence of other (Perl-) threads, 67Although the module will work in the presence of other (Perl-) threads,
64it is currently not reentrant in any way, so use appropriate locking 68it is currently not reentrant in any way, so use appropriate locking
65yourself, always call C<poll_cb> from within the same thread, or never 69yourself, always call C<poll_cb> from within the same thread, or never
66call C<poll_cb> (or other C<aio_> functions) recursively. 70call C<poll_cb> (or other C<aio_> functions) recursively.
67 71
68=head2 EXAMPLE 72=head2 EXAMPLE
69 73
70This is a simple example that uses the EV module and loads 74This is a simple example that uses the EV module and loads
71F</etc/passwd> asynchronously: 75F</etc/passwd> asynchronously:
72 76
73 use Fcntl;
74 use EV; 77 use EV;
75 use IO::AIO; 78 use IO::AIO;
76 79
77 # register the IO::AIO callback with EV 80 # register the IO::AIO callback with EV
78 my $aio_w = EV::io IO::AIO::poll_fileno, EV::READ, \&IO::AIO::poll_cb; 81 my $aio_w = EV::io IO::AIO::poll_fileno, EV::READ, \&IO::AIO::poll_cb;
95 98
96 # file contents now in $contents 99 # file contents now in $contents
97 print $contents; 100 print $contents;
98 101
99 # exit event loop and program 102 # exit event loop and program
100 EV::unloop; 103 EV::break;
101 }; 104 };
102 }; 105 };
103 106
104 # possibly queue up other requests, or open GUI windows, 107 # possibly queue up other requests, or open GUI windows,
105 # check for sockets etc. etc. 108 # check for sockets etc. etc.
106 109
107 # process events as long as there are some: 110 # process events as long as there are some:
108 EV::loop; 111 EV::run;
109 112
110=head1 REQUEST ANATOMY AND LIFETIME 113=head1 REQUEST ANATOMY AND LIFETIME
111 114
112Every C<aio_*> function creates a request. which is a C data structure not 115Every C<aio_*> function creates a request. which is a C data structure not
113directly visible to Perl. 116directly visible to Perl.
168use common::sense; 171use common::sense;
169 172
170use base 'Exporter'; 173use base 'Exporter';
171 174
172BEGIN { 175BEGIN {
173 our $VERSION = '3.9'; 176 our $VERSION = 4.42;
174 177
175 our @AIO_REQ = qw(aio_sendfile aio_read aio_write aio_open aio_close 178 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 179 aio_stat aio_lstat aio_unlink aio_rmdir aio_readdir aio_readdirx
177 aio_scandir aio_symlink aio_readlink aio_sync aio_fsync 180 aio_scandir aio_symlink aio_readlink aio_realpath aio_fcntl aio_ioctl
178 aio_fdatasync aio_sync_file_range aio_pathsync aio_readahead 181 aio_sync aio_fsync aio_syncfs aio_fdatasync aio_sync_file_range
182 aio_pathsync aio_readahead aio_fiemap aio_allocate
179 aio_rename aio_link aio_move aio_copy aio_group 183 aio_rename aio_rename2 aio_link aio_move aio_copy aio_group
180 aio_nop aio_mknod aio_load aio_rmtree aio_mkdir aio_chown 184 aio_nop aio_mknod aio_load aio_rmtree aio_mkdir aio_chown
181 aio_chmod aio_utime aio_truncate 185 aio_chmod aio_utime aio_truncate
182 aio_msync aio_mtouch aio_mlock aio_mlockall 186 aio_msync aio_mtouch aio_mlock aio_mlockall
183 aio_statvfs); 187 aio_statvfs
188 aio_slurp
189 aio_wd);
184 190
185 our @EXPORT = (@AIO_REQ, qw(aioreq_pri aioreq_nice)); 191 our @EXPORT = (@AIO_REQ, qw(aioreq_pri aioreq_nice));
186 our @EXPORT_OK = qw(poll_fileno poll_cb poll_wait flush 192 our @EXPORT_OK = qw(poll_fileno poll_cb poll_wait flush
187 min_parallel max_parallel max_idle idle_timeout 193 min_parallel max_parallel max_idle idle_timeout
188 nreqs nready npending nthreads 194 nreqs nready npending nthreads
189 max_poll_time max_poll_reqs 195 max_poll_time max_poll_reqs
190 sendfile fadvise madvise 196 sendfile fadvise madvise
191 mmap munmap munlock munlockall); 197 mmap munmap mremap munlock munlockall);
192 198
193 push @AIO_REQ, qw(aio_busy); # not exported 199 push @AIO_REQ, qw(aio_busy); # not exported
194 200
195 @IO::AIO::GRP::ISA = 'IO::AIO::REQ'; 201 @IO::AIO::GRP::ISA = 'IO::AIO::REQ';
196 202
200 206
201=head1 FUNCTIONS 207=head1 FUNCTIONS
202 208
203=head2 QUICK OVERVIEW 209=head2 QUICK OVERVIEW
204 210
205This section simply lists the prototypes of the most important functions 211This section simply lists the prototypes most of the functions for
206for quick reference. See the following sections for function-by-function 212quick reference. See the following sections for function-by-function
207documentation. 213documentation.
208 214
215 aio_wd $pathname, $callback->($wd)
209 aio_open $pathname, $flags, $mode, $callback->($fh) 216 aio_open $pathname, $flags, $mode, $callback->($fh)
210 aio_close $fh, $callback->($status) 217 aio_close $fh, $callback->($status)
218 aio_seek $fh,$offset,$whence, $callback->($offs)
211 aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) 219 aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval)
212 aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) 220 aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval)
213 aio_sendfile $out_fh, $in_fh, $in_offset, $length, $callback->($retval) 221 aio_sendfile $out_fh, $in_fh, $in_offset, $length, $callback->($retval)
214 aio_readahead $fh,$offset,$length, $callback->($retval) 222 aio_readahead $fh,$offset,$length, $callback->($retval)
215 aio_stat $fh_or_path, $callback->($status) 223 aio_stat $fh_or_path, $callback->($status)
216 aio_lstat $fh, $callback->($status) 224 aio_lstat $fh, $callback->($status)
217 aio_statvfs $fh_or_path, $callback->($statvfs) 225 aio_statvfs $fh_or_path, $callback->($statvfs)
218 aio_utime $fh_or_path, $atime, $mtime, $callback->($status) 226 aio_utime $fh_or_path, $atime, $mtime, $callback->($status)
219 aio_chown $fh_or_path, $uid, $gid, $callback->($status) 227 aio_chown $fh_or_path, $uid, $gid, $callback->($status)
228 aio_chmod $fh_or_path, $mode, $callback->($status)
220 aio_truncate $fh_or_path, $offset, $callback->($status) 229 aio_truncate $fh_or_path, $offset, $callback->($status)
221 aio_chmod $fh_or_path, $mode, $callback->($status) 230 aio_allocate $fh, $mode, $offset, $len, $callback->($status)
231 aio_fiemap $fh, $start, $length, $flags, $count, $cb->(\@extents)
222 aio_unlink $pathname, $callback->($status) 232 aio_unlink $pathname, $callback->($status)
223 aio_mknod $path, $mode, $dev, $callback->($status) 233 aio_mknod $pathname, $mode, $dev, $callback->($status)
224 aio_link $srcpath, $dstpath, $callback->($status) 234 aio_link $srcpath, $dstpath, $callback->($status)
225 aio_symlink $srcpath, $dstpath, $callback->($status) 235 aio_symlink $srcpath, $dstpath, $callback->($status)
226 aio_readlink $path, $callback->($link) 236 aio_readlink $pathname, $callback->($link)
237 aio_realpath $pathname, $callback->($path)
227 aio_rename $srcpath, $dstpath, $callback->($status) 238 aio_rename $srcpath, $dstpath, $callback->($status)
239 aio_rename2 $srcpath, $dstpath, $flags, $callback->($status)
228 aio_mkdir $pathname, $mode, $callback->($status) 240 aio_mkdir $pathname, $mode, $callback->($status)
229 aio_rmdir $pathname, $callback->($status) 241 aio_rmdir $pathname, $callback->($status)
230 aio_readdir $pathname, $callback->($entries) 242 aio_readdir $pathname, $callback->($entries)
231 aio_readdirx $pathname, $flags, $callback->($entries, $flags) 243 aio_readdirx $pathname, $flags, $callback->($entries, $flags)
232 IO::AIO::READDIR_DENTS IO::AIO::READDIR_DIRS_FIRST 244 IO::AIO::READDIR_DENTS IO::AIO::READDIR_DIRS_FIRST
233 IO::AIO::READDIR_STAT_ORDER IO::AIO::READDIR_FOUND_UNKNOWN 245 IO::AIO::READDIR_STAT_ORDER IO::AIO::READDIR_FOUND_UNKNOWN
246 aio_scandir $pathname, $maxreq, $callback->($dirs, $nondirs)
234 aio_load $path, $data, $callback->($status) 247 aio_load $pathname, $data, $callback->($status)
235 aio_copy $srcpath, $dstpath, $callback->($status) 248 aio_copy $srcpath, $dstpath, $callback->($status)
236 aio_move $srcpath, $dstpath, $callback->($status) 249 aio_move $srcpath, $dstpath, $callback->($status)
237 aio_scandir $path, $maxreq, $callback->($dirs, $nondirs)
238 aio_rmtree $path, $callback->($status) 250 aio_rmtree $pathname, $callback->($status)
251 aio_fcntl $fh, $cmd, $arg, $callback->($status)
252 aio_ioctl $fh, $request, $buf, $callback->($status)
239 aio_sync $callback->($status) 253 aio_sync $callback->($status)
254 aio_syncfs $fh, $callback->($status)
240 aio_fsync $fh, $callback->($status) 255 aio_fsync $fh, $callback->($status)
241 aio_fdatasync $fh, $callback->($status) 256 aio_fdatasync $fh, $callback->($status)
242 aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status) 257 aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status)
243 aio_pathsync $path, $callback->($status) 258 aio_pathsync $pathname, $callback->($status)
244 aio_msync $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status) 259 aio_msync $scalar, $offset = 0, $length = undef, flags = MS_SYNC, $callback->($status)
245 aio_mtouch $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status) 260 aio_mtouch $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status)
246 aio_mlock $scalar, $offset = 0, $length = undef, $callback->($status) 261 aio_mlock $scalar, $offset = 0, $length = undef, $callback->($status)
247 aio_mlockall $flags, $callback->($status) 262 aio_mlockall $flags, $callback->($status)
248 aio_group $callback->(...) 263 aio_group $callback->(...)
249 aio_nop $callback->() 264 aio_nop $callback->()
263 IO::AIO::idle_timeout $seconds 278 IO::AIO::idle_timeout $seconds
264 IO::AIO::max_outstanding $maxreqs 279 IO::AIO::max_outstanding $maxreqs
265 IO::AIO::nreqs 280 IO::AIO::nreqs
266 IO::AIO::nready 281 IO::AIO::nready
267 IO::AIO::npending 282 IO::AIO::npending
283 $nfd = IO::AIO::get_fdlimit [EXPERIMENTAL]
284 IO::AIO::min_fdlimit $nfd [EXPERIMENTAL]
268 285
269 IO::AIO::sendfile $ofh, $ifh, $offset, $count 286 IO::AIO::sendfile $ofh, $ifh, $offset, $count
270 IO::AIO::fadvise $fh, $offset, $len, $advice 287 IO::AIO::fadvise $fh, $offset, $len, $advice
288 IO::AIO::mmap $scalar, $length, $prot, $flags[, $fh[, $offset]]
289 IO::AIO::munmap $scalar
290 IO::AIO::mremap $scalar, $new_length, $flags[, $new_address]
271 IO::AIO::madvise $scalar, $offset, $length, $advice 291 IO::AIO::madvise $scalar, $offset, $length, $advice
272 IO::AIO::mprotect $scalar, $offset, $length, $protect 292 IO::AIO::mprotect $scalar, $offset, $length, $protect
273 IO::AIO::munlock $scalar, $offset = 0, $length = undef 293 IO::AIO::munlock $scalar, $offset = 0, $length = undef
274 IO::AIO::munlockall 294 IO::AIO::munlockall
275 295
276=head2 AIO REQUEST FUNCTIONS 296=head2 API NOTES
277 297
278All the C<aio_*> calls are more or less thin wrappers around the syscall 298All the C<aio_*> calls are more or less thin wrappers around the syscall
279with the same name (sans C<aio_>). The arguments are similar or identical, 299with the same name (sans C<aio_>). The arguments are similar or identical,
280and they all accept an additional (and optional) C<$callback> argument 300and they all accept an additional (and optional) C<$callback> argument
281which must be a code reference. This code reference will get called with 301which must be a code reference. This code reference will be called after
282the syscall return code (e.g. most syscalls return C<-1> on error, unlike 302the syscall has been executed in an asynchronous fashion. The results
283perl, which usually delivers "false") as its sole argument after the given 303of the request will be passed as arguments to the callback (and, if an
284syscall has been executed asynchronously. 304error occured, in C<$!>) - for most requests the syscall return code (e.g.
305most syscalls return C<-1> on error, unlike perl, which usually delivers
306"false").
307
308Some requests (such as C<aio_readdir>) pass the actual results and
309communicate failures by passing C<undef>.
285 310
286All functions expecting a filehandle keep a copy of the filehandle 311All functions expecting a filehandle keep a copy of the filehandle
287internally until the request has finished. 312internally until the request has finished.
288 313
289All functions return request objects of type L<IO::AIO::REQ> that allow 314All functions return request objects of type L<IO::AIO::REQ> that allow
290further manipulation of those requests while they are in-flight. 315further manipulation of those requests while they are in-flight.
291 316
292The pathnames you pass to these routines I<must> be absolute and 317The pathnames you pass to these routines I<should> be absolute. The
293encoded as octets. The reason for the former is that at the time the 318reason for this is that at the time the request is being executed, the
294request is being executed, the current working directory could have 319current working directory could have changed. Alternatively, you can
295changed. Alternatively, you can make sure that you never change the 320make sure that you never change the current working directory anywhere
296current working directory anywhere in the program and then use relative 321in the program and then use relative paths. You can also take advantage
297paths. 322of IO::AIOs working directory abstraction, that lets you specify paths
323relative to some previously-opened "working directory object" - see the
324description of the C<IO::AIO::WD> class later in this document.
298 325
299To encode pathnames as octets, either make sure you either: a) always pass 326To encode pathnames as octets, either make sure you either: a) always pass
300in filenames you got from outside (command line, readdir etc.) without 327in filenames you got from outside (command line, readdir etc.) without
301tinkering, b) are ASCII or ISO 8859-1, c) use the Encode module and encode 328tinkering, b) are in your native filesystem encoding, c) use the Encode
302your pathnames to the locale (or other) encoding in effect in the user 329module and encode your pathnames to the locale (or other) encoding in
303environment, d) use Glib::filename_from_unicode on unicode filenames or e) 330effect in the user environment, d) use Glib::filename_from_unicode on
304use something else to ensure your scalar has the correct contents. 331unicode filenames or e) use something else to ensure your scalar has the
332correct contents.
305 333
306This works, btw. independent of the internal UTF-8 bit, which IO::AIO 334This works, btw. independent of the internal UTF-8 bit, which IO::AIO
307handles correctly whether it is set or not. 335handles correctly whether it is set or not.
336
337=head2 AIO REQUEST FUNCTIONS
308 338
309=over 4 339=over 4
310 340
311=item $prev_pri = aioreq_pri [$pri] 341=item $prev_pri = aioreq_pri [$pri]
312 342
342 372
343 373
344=item aio_open $pathname, $flags, $mode, $callback->($fh) 374=item aio_open $pathname, $flags, $mode, $callback->($fh)
345 375
346Asynchronously open or create a file and call the callback with a newly 376Asynchronously open or create a file and call the callback with a newly
347created filehandle for the file. 377created filehandle for the file (or C<undef> in case of an error).
348 378
349The pathname passed to C<aio_open> must be absolute. See API NOTES, above, 379The pathname passed to C<aio_open> must be absolute. See API NOTES, above,
350for an explanation. 380for an explanation.
351 381
352The C<$flags> argument is a bitmask. See the C<Fcntl> module for a 382The C<$flags> argument is a bitmask. See the C<Fcntl> module for a
375following POSIX and non-POSIX constants are available (missing ones on 405following POSIX and non-POSIX constants are available (missing ones on
376your system are, as usual, C<0>): 406your system are, as usual, C<0>):
377 407
378C<O_ASYNC>, C<O_DIRECT>, C<O_NOATIME>, C<O_CLOEXEC>, C<O_NOCTTY>, C<O_NOFOLLOW>, 408C<O_ASYNC>, C<O_DIRECT>, C<O_NOATIME>, C<O_CLOEXEC>, C<O_NOCTTY>, C<O_NOFOLLOW>,
379C<O_NONBLOCK>, C<O_EXEC>, C<O_SEARCH>, C<O_DIRECTORY>, C<O_DSYNC>, 409C<O_NONBLOCK>, C<O_EXEC>, C<O_SEARCH>, C<O_DIRECTORY>, C<O_DSYNC>,
380C<O_RSYNC>, C<O_SYNC> and C<O_TTY_INIT>. 410C<O_RSYNC>, C<O_SYNC>, C<O_PATH>, C<O_TMPFILE>, C<O_TTY_INIT> and C<O_ACCMODE>.
381 411
382 412
383=item aio_close $fh, $callback->($status) 413=item aio_close $fh, $callback->($status)
384 414
385Asynchronously close a file and call the callback with the result 415Asynchronously close a file and call the callback with the result
395Or in other words: the file descriptor will be closed, but it will not be 425Or in other words: the file descriptor will be closed, but it will not be
396free for reuse until the perl filehandle is closed. 426free for reuse until the perl filehandle is closed.
397 427
398=cut 428=cut
399 429
430=item aio_seek $fh, $offset, $whence, $callback->($offs)
431
432Seeks the filehandle to the new C<$offset>, similarly to perl's
433C<sysseek>. The C<$whence> can use the traditional values (C<0> for
434C<IO::AIO::SEEK_SET>, C<1> for C<IO::AIO::SEEK_CUR> or C<2> for
435C<IO::AIO::SEEK_END>).
436
437The resulting absolute offset will be passed to the callback, or C<-1> in
438case of an error.
439
440In theory, the C<$whence> constants could be different than the
441corresponding values from L<Fcntl>, but perl guarantees they are the same,
442so don't panic.
443
444As a GNU/Linux (and maybe Solaris) extension, also the constants
445C<IO::AIO::SEEK_DATA> and C<IO::AIO::SEEK_HOLE> are available, if they
446could be found. No guarantees about suitability for use in C<aio_seek> or
447Perl's C<sysseek> can be made though, although I would naively assume they
448"just work".
449
400=item aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval) 450=item aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval)
401 451
402=item aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval) 452=item aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval)
403 453
404Reads or writes C<$length> bytes from or to the specified C<$fh> and 454Reads or writes C<$length> bytes from or to the specified C<$fh> and
405C<$offset> into the scalar given by C<$data> and offset C<$dataoffset> 455C<$offset> into the scalar given by C<$data> and offset C<$dataoffset> and
406and calls the callback without the actual number of bytes read (or -1 on 456calls the callback with the actual number of bytes transferred (or -1 on
407error, just like the syscall). 457error, just like the syscall).
408 458
409C<aio_read> will, like C<sysread>, shrink or grow the C<$data> scalar to 459C<aio_read> will, like C<sysread>, shrink or grow the C<$data> scalar to
410offset plus the actual number of bytes read. 460offset plus the actual number of bytes read.
411 461
436 486
437Tries to copy C<$length> bytes from C<$in_fh> to C<$out_fh>. It starts 487Tries to copy C<$length> bytes from C<$in_fh> to C<$out_fh>. It starts
438reading at byte offset C<$in_offset>, and starts writing at the current 488reading at byte offset C<$in_offset>, and starts writing at the current
439file offset of C<$out_fh>. Because of that, it is not safe to issue more 489file offset of C<$out_fh>. Because of that, it is not safe to issue more
440than one C<aio_sendfile> per C<$out_fh>, as they will interfere with each 490than one C<aio_sendfile> per C<$out_fh>, as they will interfere with each
441other. 491other. The same C<$in_fh> works fine though, as this function does not
492move or use the file offset of C<$in_fh>.
442 493
443Please note that C<aio_sendfile> can read more bytes from C<$in_fh> than 494Please note that C<aio_sendfile> can read more bytes from C<$in_fh> than
444are written, and there is no way to find out how many bytes have been read 495are written, and there is no way to find out how many more bytes have been
445from C<aio_sendfile> alone, as C<aio_sendfile> only provides the number of 496read from C<aio_sendfile> alone, as C<aio_sendfile> only provides the
446bytes written to C<$out_fh>. Only if the result value equals C<$length> 497number of bytes written to C<$out_fh>. Only if the result value equals
447one can assume that C<$length> bytes have been read. 498C<$length> one can assume that C<$length> bytes have been read.
448 499
449Unlike with other C<aio_> functions, it makes a lot of sense to use 500Unlike with other C<aio_> functions, it makes a lot of sense to use
450C<aio_sendfile> on non-blocking sockets, as long as one end (typically 501C<aio_sendfile> on non-blocking sockets, as long as one end (typically
451the C<$in_fh>) is a file - the file I/O will then be asynchronous, while 502the C<$in_fh>) is a file - the file I/O will then be asynchronous, while
452the socket I/O will be non-blocking. Note, however, that you can run into 503the socket I/O will be non-blocking. Note, however, that you can run
453a trap where C<aio_sendfile> reads some data with readahead, then fails 504into a trap where C<aio_sendfile> reads some data with readahead, then
454to write all data, and when the socket is ready the next time, the data 505fails to write all data, and when the socket is ready the next time, the
455in the cache is already lost, forcing C<aio_sendfile> to again hit the 506data in the cache is already lost, forcing C<aio_sendfile> to again hit
456disk. Explicit C<aio_read> + C<aio_write> let's you control resource usage 507the disk. Explicit C<aio_read> + C<aio_write> let's you better control
457much better. 508resource usage.
458 509
459This call tries to make use of a native C<sendfile> syscall to provide 510This call tries to make use of a native C<sendfile>-like syscall to
460zero-copy operation. For this to work, C<$out_fh> should refer to a 511provide zero-copy operation. For this to work, C<$out_fh> should refer to
461socket, and C<$in_fh> should refer to an mmap'able file. 512a socket, and C<$in_fh> should refer to an mmap'able file.
462 513
463If a native sendfile cannot be found or it fails with C<ENOSYS>, 514If a native sendfile cannot be found or it fails with C<ENOSYS>,
464C<ENOTSUP>, C<EOPNOTSUPP>, C<EAFNOSUPPORT>, C<EPROTOTYPE> or C<ENOTSOCK>, 515C<EINVAL>, C<ENOTSUP>, C<EOPNOTSUPP>, C<EAFNOSUPPORT>, C<EPROTOTYPE> or
465it will be emulated, so you can call C<aio_sendfile> on any type of 516C<ENOTSOCK>, it will be emulated, so you can call C<aio_sendfile> on any
466filehandle regardless of the limitations of the operating system. 517type of filehandle regardless of the limitations of the operating system.
518
519As native sendfile syscalls (as practically any non-POSIX interface hacked
520together in a hurry to improve benchmark numbers) tend to be rather buggy
521on many systems, this implementation tries to work around some known bugs
522in Linux and FreeBSD kernels (probably others, too), but that might fail,
523so you really really should check the return value of C<aio_sendfile> -
524fewer bytes than expected might have been transferred.
467 525
468 526
469=item aio_readahead $fh,$offset,$length, $callback->($retval) 527=item aio_readahead $fh,$offset,$length, $callback->($retval)
470 528
471C<aio_readahead> populates the page cache with data from a file so that 529C<aio_readahead> populates the page cache with data from a file so that
475whole pages, so that offset is effectively rounded down to a page boundary 533whole pages, so that offset is effectively rounded down to a page boundary
476and bytes are read up to the next page boundary greater than or equal to 534and bytes are read up to the next page boundary greater than or equal to
477(off-set+length). C<aio_readahead> does not read beyond the end of the 535(off-set+length). C<aio_readahead> does not read beyond the end of the
478file. The current file offset of the file is left unchanged. 536file. The current file offset of the file is left unchanged.
479 537
480If that syscall doesn't exist (likely if your OS isn't Linux) it will be 538If that syscall doesn't exist (likely if your kernel isn't Linux) it will
481emulated by simply reading the data, which would have a similar effect. 539be emulated by simply reading the data, which would have a similar effect.
482 540
483 541
484=item aio_stat $fh_or_path, $callback->($status) 542=item aio_stat $fh_or_path, $callback->($status)
485 543
486=item aio_lstat $fh, $callback->($status) 544=item aio_lstat $fh, $callback->($status)
555 namemax => 255, 613 namemax => 255,
556 frsize => 1024, 614 frsize => 1024,
557 fsid => 1810 615 fsid => 1810
558 } 616 }
559 617
560
561=item aio_utime $fh_or_path, $atime, $mtime, $callback->($status) 618=item aio_utime $fh_or_path, $atime, $mtime, $callback->($status)
562 619
563Works like perl's C<utime> function (including the special case of $atime 620Works like perl's C<utime> function (including the special case of $atime
564and $mtime being undef). Fractional times are supported if the underlying 621and $mtime being undef). Fractional times are supported if the underlying
565syscalls support them. 622syscalls support them.
592=item aio_truncate $fh_or_path, $offset, $callback->($status) 649=item aio_truncate $fh_or_path, $offset, $callback->($status)
593 650
594Works like truncate(2) or ftruncate(2). 651Works like truncate(2) or ftruncate(2).
595 652
596 653
654=item aio_allocate $fh, $mode, $offset, $len, $callback->($status)
655
656Allocates or frees disk space according to the C<$mode> argument. See the
657linux C<fallocate> documentation for details.
658
659C<$mode> is usually C<0> or C<IO::AIO::FALLOC_FL_KEEP_SIZE> to allocate
660space, or C<IO::AIO::FALLOC_FL_PUNCH_HOLE | IO::AIO::FALLOC_FL_KEEP_SIZE>,
661to deallocate a file range.
662
663IO::AIO also supports C<FALLOC_FL_COLLAPSE_RANGE>, to remove a range
664(without leaving a hole), C<FALLOC_FL_ZERO_RANGE>, to zero a range,
665C<FALLOC_FL_INSERT_RANGE> to insert a range and C<FALLOC_FL_UNSHARE_RANGE>
666to unshare shared blocks (see your L<fallocate(2)> manpage).
667
668The file system block size used by C<fallocate> is presumably the
669C<f_bsize> returned by C<statvfs>, but different filesystems and filetypes
670can dictate other limitations.
671
672If C<fallocate> isn't available or cannot be emulated (currently no
673emulation will be attempted), passes C<-1> and sets C<$!> to C<ENOSYS>.
674
675
597=item aio_chmod $fh_or_path, $mode, $callback->($status) 676=item aio_chmod $fh_or_path, $mode, $callback->($status)
598 677
599Works like perl's C<chmod> function. 678Works like perl's C<chmod> function.
600 679
601 680
603 682
604Asynchronously unlink (delete) a file and call the callback with the 683Asynchronously unlink (delete) a file and call the callback with the
605result code. 684result code.
606 685
607 686
608=item aio_mknod $path, $mode, $dev, $callback->($status) 687=item aio_mknod $pathname, $mode, $dev, $callback->($status)
609 688
610[EXPERIMENTAL] 689[EXPERIMENTAL]
611 690
612Asynchronously create a device node (or fifo). See mknod(2). 691Asynchronously create a device node (or fifo). See mknod(2).
613 692
614The only (POSIX-) portable way of calling this function is: 693The only (POSIX-) portable way of calling this function is:
615 694
616 aio_mknod $path, IO::AIO::S_IFIFO | $mode, 0, sub { ... 695 aio_mknod $pathname, IO::AIO::S_IFIFO | $mode, 0, sub { ...
617 696
618See C<aio_stat> for info about some potentially helpful extra constants 697See C<aio_stat> for info about some potentially helpful extra constants
619and functions. 698and functions.
620 699
621=item aio_link $srcpath, $dstpath, $callback->($status) 700=item aio_link $srcpath, $dstpath, $callback->($status)
628 707
629Asynchronously create a new symbolic link to the existing object at C<$srcpath> at 708Asynchronously create a new symbolic link to the existing object at C<$srcpath> at
630the path C<$dstpath> and call the callback with the result code. 709the path C<$dstpath> and call the callback with the result code.
631 710
632 711
633=item aio_readlink $path, $callback->($link) 712=item aio_readlink $pathname, $callback->($link)
634 713
635Asynchronously read the symlink specified by C<$path> and pass it to 714Asynchronously read the symlink specified by C<$path> and pass it to
636the callback. If an error occurs, nothing or undef gets passed to the 715the callback. If an error occurs, nothing or undef gets passed to the
637callback. 716callback.
638 717
639 718
719=item aio_realpath $pathname, $callback->($path)
720
721Asynchronously make the path absolute and resolve any symlinks in
722C<$path>. The resulting path only consists of directories (same as
723L<Cwd::realpath>).
724
725This request can be used to get the absolute path of the current working
726directory by passing it a path of F<.> (a single dot).
727
728
640=item aio_rename $srcpath, $dstpath, $callback->($status) 729=item aio_rename $srcpath, $dstpath, $callback->($status)
641 730
642Asynchronously rename the object at C<$srcpath> to C<$dstpath>, just as 731Asynchronously rename the object at C<$srcpath> to C<$dstpath>, just as
643rename(2) and call the callback with the result code. 732rename(2) and call the callback with the result code.
733
734On systems that support the AIO::WD working directory abstraction
735natively, the case C<[$wd, "."]> as C<$srcpath> is specialcased - instead
736of failing, C<rename> is called on the absolute path of C<$wd>.
737
738
739=item aio_rename2 $srcpath, $dstpath, $flags, $callback->($status)
740
741Basically a version of C<aio_rename> with an additional C<$flags>
742argument. Calling this with C<$flags=0> is the same as calling
743C<aio_rename>.
744
745Non-zero flags are currently only supported on GNU/Linux systems that
746support renameat2. Other systems fail with C<ENOSYS> in this case.
747
748The following constants are available (missing ones are, as usual C<0>),
749see renameat2(2) for details:
750
751C<IO::AIO::RENAME_NOREPLACE>, C<IO::AIO::RENAME_EXCHANGE>
752and C<IO::AIO::RENAME_WHITEOUT>.
644 753
645 754
646=item aio_mkdir $pathname, $mode, $callback->($status) 755=item aio_mkdir $pathname, $mode, $callback->($status)
647 756
648Asynchronously mkdir (create) a directory and call the callback with 757Asynchronously mkdir (create) a directory and call the callback with
653=item aio_rmdir $pathname, $callback->($status) 762=item aio_rmdir $pathname, $callback->($status)
654 763
655Asynchronously rmdir (delete) a directory and call the callback with the 764Asynchronously rmdir (delete) a directory and call the callback with the
656result code. 765result code.
657 766
767On systems that support the AIO::WD working directory abstraction
768natively, the case C<[$wd, "."]> is specialcased - instead of failing,
769C<rmdir> is called on the absolute path of C<$wd>.
770
658 771
659=item aio_readdir $pathname, $callback->($entries) 772=item aio_readdir $pathname, $callback->($entries)
660 773
661Unlike the POSIX call of the same name, C<aio_readdir> reads an entire 774Unlike the POSIX call of the same name, C<aio_readdir> reads an entire
662directory (i.e. opendir + readdir + closedir). The entries will not be 775directory (i.e. opendir + readdir + closedir). The entries will not be
666array-ref with the filenames. 779array-ref with the filenames.
667 780
668 781
669=item aio_readdirx $pathname, $flags, $callback->($entries, $flags) 782=item aio_readdirx $pathname, $flags, $callback->($entries, $flags)
670 783
671Quite similar to C<aio_readdir>, but the C<$flags> argument allows to tune 784Quite similar to C<aio_readdir>, but the C<$flags> argument allows one to
672behaviour and output format. In case of an error, C<$entries> will be 785tune behaviour and output format. In case of an error, C<$entries> will be
673C<undef>. 786C<undef>.
674 787
675The flags are a combination of the following constants, ORed together (the 788The flags are a combination of the following constants, ORed together (the
676flags will also be passed to the callback, possibly modified): 789flags will also be passed to the callback, possibly modified):
677 790
678=over 4 791=over 4
679 792
680=item IO::AIO::READDIR_DENTS 793=item IO::AIO::READDIR_DENTS
681 794
682When this flag is off, then the callback gets an arrayref consisting of 795Normally the callback gets an arrayref consisting of names only (as
683names only (as with C<aio_readdir>), otherwise it gets an arrayref with 796with C<aio_readdir>). If this flag is set, then the callback gets an
684C<[$name, $type, $inode]> arrayrefs, each describing a single directory 797arrayref with C<[$name, $type, $inode]> arrayrefs, each describing a
685entry in more detail. 798single directory entry in more detail:
686 799
687C<$name> is the name of the entry. 800C<$name> is the name of the entry.
688 801
689C<$type> is one of the C<IO::AIO::DT_xxx> constants: 802C<$type> is one of the C<IO::AIO::DT_xxx> constants:
690 803
691C<IO::AIO::DT_UNKNOWN>, C<IO::AIO::DT_FIFO>, C<IO::AIO::DT_CHR>, C<IO::AIO::DT_DIR>, 804C<IO::AIO::DT_UNKNOWN>, C<IO::AIO::DT_FIFO>, C<IO::AIO::DT_CHR>, C<IO::AIO::DT_DIR>,
692C<IO::AIO::DT_BLK>, C<IO::AIO::DT_REG>, C<IO::AIO::DT_LNK>, C<IO::AIO::DT_SOCK>, 805C<IO::AIO::DT_BLK>, C<IO::AIO::DT_REG>, C<IO::AIO::DT_LNK>, C<IO::AIO::DT_SOCK>,
693C<IO::AIO::DT_WHT>. 806C<IO::AIO::DT_WHT>.
694 807
695C<IO::AIO::DT_UNKNOWN> means just that: readdir does not know. If you need to 808C<IO::AIO::DT_UNKNOWN> means just that: readdir does not know. If you need
696know, you have to run stat yourself. Also, for speed reasons, the C<$type> 809to know, you have to run stat yourself. Also, for speed/memory reasons,
697scalars are read-only: you can not modify them. 810the C<$type> scalars are read-only: you must not modify them.
698 811
699C<$inode> is the inode number (which might not be exact on systems with 64 812C<$inode> is the inode number (which might not be exact on systems with 64
700bit inode numbers and 32 bit perls). This field has unspecified content on 813bit inode numbers and 32 bit perls). This field has unspecified content on
701systems that do not deliver the inode information. 814systems that do not deliver the inode information.
702 815
713short names are tried first. 826short names are tried first.
714 827
715=item IO::AIO::READDIR_STAT_ORDER 828=item IO::AIO::READDIR_STAT_ORDER
716 829
717When this flag is set, then the names will be returned in an order 830When this flag is set, then the names will be returned in an order
718suitable for stat()'ing each one. That is, when you plan to stat() 831suitable for stat()'ing each one. That is, when you plan to stat() most or
719all files in the given directory, then the returned order will likely 832all files in the given directory, then the returned order will likely be
720be fastest. 833faster.
721 834
722If both this flag and C<IO::AIO::READDIR_DIRS_FIRST> are specified, then 835If both this flag and C<IO::AIO::READDIR_DIRS_FIRST> are specified,
723the likely dirs come first, resulting in a less optimal stat order. 836then the likely dirs come first, resulting in a less optimal stat order
837for stat'ing all entries, but likely a more optimal order for finding
838subdirectories.
724 839
725=item IO::AIO::READDIR_FOUND_UNKNOWN 840=item IO::AIO::READDIR_FOUND_UNKNOWN
726 841
727This flag should not be set when calling C<aio_readdirx>. Instead, it 842This flag should not be set when calling C<aio_readdirx>. Instead, it
728is being set by C<aio_readdirx>, when any of the C<$type>'s found were 843is being set by C<aio_readdirx>, when any of the C<$type>'s found were
729C<IO::AIO::DT_UNKNOWN>. The absense of this flag therefore indicates that all 844C<IO::AIO::DT_UNKNOWN>. The absence of this flag therefore indicates that all
730C<$type>'s are known, which can be used to speed up some algorithms. 845C<$type>'s are known, which can be used to speed up some algorithms.
731 846
732=back 847=back
733 848
734 849
850=item aio_slurp $pathname, $offset, $length, $data, $callback->($status)
851
852Opens, reads and closes the given file. The data is put into C<$data>,
853which is resized as required.
854
855If C<$offset> is negative, then it is counted from the end of the file.
856
857If C<$length> is zero, then the remaining length of the file is
858used. Also, in this case, the same limitations to modifying C<$data> apply
859as when IO::AIO::mmap is used, i.e. it must only be modified in-place
860with C<substr>. If the size of the file is known, specifying a non-zero
861C<$length> results in a performance advantage.
862
863This request is similar to the older C<aio_load> request, but since it is
864a single request, it might be more efficient to use.
865
866Example: load F</etc/passwd> into C<$passwd>.
867
868 my $passwd;
869 aio_slurp "/etc/passwd", 0, 0, $passwd, sub {
870 $_[0] >= 0
871 or die "/etc/passwd: $!\n";
872
873 printf "/etc/passwd is %d bytes long, and contains:\n", length $passwd;
874 print $passwd;
875 };
876 IO::AIO::flush;
877
878
735=item aio_load $path, $data, $callback->($status) 879=item aio_load $pathname, $data, $callback->($status)
736 880
737This is a composite request that tries to fully load the given file into 881This is a composite request that tries to fully load the given file into
738memory. Status is the same as with aio_read. 882memory. Status is the same as with aio_read.
883
884Using C<aio_slurp> might be more efficient, as it is a single request.
739 885
740=cut 886=cut
741 887
742sub aio_load($$;$) { 888sub aio_load($$;$) {
743 my ($path, undef, $cb) = @_; 889 my ($path, undef, $cb) = @_;
763=item aio_copy $srcpath, $dstpath, $callback->($status) 909=item aio_copy $srcpath, $dstpath, $callback->($status)
764 910
765Try to copy the I<file> (directories not supported as either source or 911Try to copy the I<file> (directories not supported as either source or
766destination) from C<$srcpath> to C<$dstpath> and call the callback with 912destination) from C<$srcpath> to C<$dstpath> and call the callback with
767a status of C<0> (ok) or C<-1> (error, see C<$!>). 913a status of C<0> (ok) or C<-1> (error, see C<$!>).
914
915Existing destination files will be truncated.
768 916
769This is a composite request that creates the destination file with 917This is a composite request that creates the destination file with
770mode 0200 and copies the contents of the source file into it using 918mode 0200 and copies the contents of the source file into it using
771C<aio_sendfile>, followed by restoring atime, mtime, access mode and 919C<aio_sendfile>, followed by restoring atime, mtime, access mode and
772uid/gid, in that order. 920uid/gid, in that order.
862 if ($_[0] && $! == EXDEV) { 1010 if ($_[0] && $! == EXDEV) {
863 aioreq_pri $pri; 1011 aioreq_pri $pri;
864 add $grp aio_copy $src, $dst, sub { 1012 add $grp aio_copy $src, $dst, sub {
865 $grp->result ($_[0]); 1013 $grp->result ($_[0]);
866 1014
867 if (!$_[0]) { 1015 unless ($_[0]) {
868 aioreq_pri $pri; 1016 aioreq_pri $pri;
869 add $grp aio_unlink $src; 1017 add $grp aio_unlink $src;
870 } 1018 }
871 }; 1019 };
872 } else { 1020 } else {
875 }; 1023 };
876 1024
877 $grp 1025 $grp
878} 1026}
879 1027
880=item aio_scandir $path, $maxreq, $callback->($dirs, $nondirs) 1028=item aio_scandir $pathname, $maxreq, $callback->($dirs, $nondirs)
881 1029
882Scans a directory (similar to C<aio_readdir>) but additionally tries to 1030Scans a directory (similar to C<aio_readdir>) but additionally tries to
883efficiently separate the entries of directory C<$path> into two sets of 1031efficiently separate the entries of directory C<$path> into two sets of
884names, directories you can recurse into (directories), and ones you cannot 1032names, directories you can recurse into (directories), and ones you cannot
885recurse into (everything else, including symlinks to directories). 1033recurse into (everything else, including symlinks to directories).
886 1034
887C<aio_scandir> is a composite request that creates of many sub requests_ 1035C<aio_scandir> is a composite request that generates many sub requests.
888C<$maxreq> specifies the maximum number of outstanding aio requests that 1036C<$maxreq> specifies the maximum number of outstanding aio requests that
889this function generates. If it is C<< <= 0 >>, then a suitable default 1037this function generates. If it is C<< <= 0 >>, then a suitable default
890will be chosen (currently 4). 1038will be chosen (currently 4).
891 1039
892On error, the callback is called without arguments, otherwise it receives 1040On error, the callback is called without arguments, otherwise it receives
916Then entries will be sorted into likely directories a non-initial dot 1064Then entries will be sorted into likely directories a non-initial dot
917currently) and likely non-directories (see C<aio_readdirx>). Then every 1065currently) and likely non-directories (see C<aio_readdirx>). Then every
918entry plus an appended C</.> will be C<stat>'ed, likely directories first, 1066entry plus an appended C</.> will be C<stat>'ed, likely directories first,
919in order of their inode numbers. If that succeeds, it assumes that the 1067in order of their inode numbers. If that succeeds, it assumes that the
920entry is a directory or a symlink to directory (which will be checked 1068entry is a directory or a symlink to directory (which will be checked
921seperately). This is often faster than stat'ing the entry itself because 1069separately). This is often faster than stat'ing the entry itself because
922filesystems might detect the type of the entry without reading the inode 1070filesystems might detect the type of the entry without reading the inode
923data (e.g. ext2fs filetype feature), even on systems that cannot return 1071data (e.g. ext2fs filetype feature), even on systems that cannot return
924the filetype information on readdir. 1072the filetype information on readdir.
925 1073
926If the known number of directories (link count - 2) has been reached, the 1074If the known number of directories (link count - 2) has been reached, the
942 1090
943 my $grp = aio_group $cb; 1091 my $grp = aio_group $cb;
944 1092
945 $maxreq = 4 if $maxreq <= 0; 1093 $maxreq = 4 if $maxreq <= 0;
946 1094
947 # stat once 1095 # get a wd object
948 aioreq_pri $pri; 1096 aioreq_pri $pri;
949 add $grp aio_stat $path, sub { 1097 add $grp aio_wd $path, sub {
1098 $_[0]
950 return $grp->result () if $_[0]; 1099 or return $grp->result ();
951 my $now = time;
952 my $hash1 = join ":", (stat _)[0,1,3,7,9];
953 1100
954 # read the directory entries 1101 my $wd = [shift, "."];
1102
1103 # stat once
955 aioreq_pri $pri; 1104 aioreq_pri $pri;
956 add $grp aio_readdirx $path, READDIR_DIRS_FIRST, sub { 1105 add $grp aio_stat $wd, sub {
957 my $entries = shift
958 or return $grp->result (); 1106 return $grp->result () if $_[0];
1107 my $now = time;
1108 my $hash1 = join ":", (stat _)[0,1,3,7,9];
959 1109
960 # stat the dir another time 1110 # read the directory entries
961 aioreq_pri $pri; 1111 aioreq_pri $pri;
1112 add $grp aio_readdirx $wd, READDIR_DIRS_FIRST, sub {
1113 my $entries = shift
1114 or return $grp->result ();
1115
1116 # stat the dir another time
1117 aioreq_pri $pri;
962 add $grp aio_stat $path, sub { 1118 add $grp aio_stat $wd, sub {
963 my $hash2 = join ":", (stat _)[0,1,3,7,9]; 1119 my $hash2 = join ":", (stat _)[0,1,3,7,9];
964 1120
965 my $ndirs; 1121 my $ndirs;
966 1122
967 # take the slow route if anything looks fishy 1123 # take the slow route if anything looks fishy
968 if ($hash1 ne $hash2 or (stat _)[9] == $now) { 1124 if ($hash1 ne $hash2 or (stat _)[9] == $now) {
969 $ndirs = -1; 1125 $ndirs = -1;
970 } else { 1126 } else {
971 # if nlink == 2, we are finished 1127 # if nlink == 2, we are finished
972 # for non-posix-fs's, we rely on nlink < 2 1128 # for non-posix-fs's, we rely on nlink < 2
973 $ndirs = (stat _)[3] - 2 1129 $ndirs = (stat _)[3] - 2
974 or return $grp->result ([], $entries); 1130 or return $grp->result ([], $entries);
975 } 1131 }
976 1132
977 my (@dirs, @nondirs); 1133 my (@dirs, @nondirs);
978 1134
979 my $statgrp = add $grp aio_group sub { 1135 my $statgrp = add $grp aio_group sub {
980 $grp->result (\@dirs, \@nondirs); 1136 $grp->result (\@dirs, \@nondirs);
981 }; 1137 };
982 1138
983 limit $statgrp $maxreq; 1139 limit $statgrp $maxreq;
984 feed $statgrp sub { 1140 feed $statgrp sub {
985 return unless @$entries; 1141 return unless @$entries;
986 my $entry = shift @$entries; 1142 my $entry = shift @$entries;
987 1143
988 aioreq_pri $pri; 1144 aioreq_pri $pri;
1145 $wd->[1] = "$entry/.";
989 add $statgrp aio_stat "$path/$entry/.", sub { 1146 add $statgrp aio_stat $wd, sub {
990 if ($_[0] < 0) { 1147 if ($_[0] < 0) {
991 push @nondirs, $entry; 1148 push @nondirs, $entry;
992 } else { 1149 } else {
993 # need to check for real directory 1150 # need to check for real directory
994 aioreq_pri $pri; 1151 aioreq_pri $pri;
1152 $wd->[1] = $entry;
995 add $statgrp aio_lstat "$path/$entry", sub { 1153 add $statgrp aio_lstat $wd, sub {
996 if (-d _) { 1154 if (-d _) {
997 push @dirs, $entry; 1155 push @dirs, $entry;
998 1156
999 unless (--$ndirs) { 1157 unless (--$ndirs) {
1000 push @nondirs, @$entries; 1158 push @nondirs, @$entries;
1001 feed $statgrp; 1159 feed $statgrp;
1160 }
1161 } else {
1162 push @nondirs, $entry;
1002 } 1163 }
1003 } else {
1004 push @nondirs, $entry;
1005 } 1164 }
1006 } 1165 }
1007 } 1166 };
1008 }; 1167 };
1009 }; 1168 };
1010 }; 1169 };
1011 }; 1170 };
1012 }; 1171 };
1013 1172
1014 $grp 1173 $grp
1015} 1174}
1016 1175
1017=item aio_rmtree $path, $callback->($status) 1176=item aio_rmtree $pathname, $callback->($status)
1018 1177
1019Delete a directory tree starting (and including) C<$path>, return the 1178Delete a directory tree starting (and including) C<$path>, return the
1020status of the final C<rmdir> only. This is a composite request that 1179status of the final C<rmdir> only. This is a composite request that
1021uses C<aio_scandir> to recurse into and rmdir directories, and unlink 1180uses C<aio_scandir> to recurse into and rmdir directories, and unlink
1022everything else. 1181everything else.
1023 1182
1024=cut 1183=cut
1025 1184
1047 }; 1206 };
1048 1207
1049 $grp 1208 $grp
1050} 1209}
1051 1210
1211=item aio_fcntl $fh, $cmd, $arg, $callback->($status)
1212
1213=item aio_ioctl $fh, $request, $buf, $callback->($status)
1214
1215These work just like the C<fcntl> and C<ioctl> built-in functions, except
1216they execute asynchronously and pass the return value to the callback.
1217
1218Both calls can be used for a lot of things, some of which make more sense
1219to run asynchronously in their own thread, while some others make less
1220sense. For example, calls that block waiting for external events, such
1221as locking, will also lock down an I/O thread while it is waiting, which
1222can deadlock the whole I/O system. At the same time, there might be no
1223alternative to using a thread to wait.
1224
1225So in general, you should only use these calls for things that do
1226(filesystem) I/O, not for things that wait for other events (network,
1227other processes), although if you are careful and know what you are doing,
1228you still can.
1229
1230The following constants are available (missing ones are, as usual C<0>):
1231
1232C<F_DUPFD_CLOEXEC>,
1233
1234C<F_OFD_GETLK>, C<F_OFD_SETLK>, C<F_OFD_GETLKW>,
1235
1236C<FIFREEZE>, C<FITHAW>, C<FITRIM>, C<FICLONE>, C<FICLONERANGE>, C<FIDEDUPERANGE>.
1237
1238C<FS_IOC_GETFLAGS>, C<FS_IOC_SETFLAGS>, C<FS_IOC_GETVERSION>, C<FS_IOC_SETVERSION>,
1239C<FS_IOC_FIEMAP>.
1240
1241C<FS_IOC_FSGETXATTR>, C<FS_IOC_FSSETXATTR>, C<FS_IOC_SET_ENCRYPTION_POLICY>,
1242C<FS_IOC_GET_ENCRYPTION_PWSALT>, C<FS_IOC_GET_ENCRYPTION_POLICY>, C<FS_KEY_DESCRIPTOR_SIZE>.
1243
1244C<FS_SECRM_FL>, C<FS_UNRM_FL>, C<FS_COMPR_FL>, C<FS_SYNC_FL>, C<FS_IMMUTABLE_FL>,
1245C<FS_APPEND_FL>, C<FS_NODUMP_FL>, C<FS_NOATIME_FL>, C<FS_DIRTY_FL>,
1246C<FS_COMPRBLK_FL>, C<FS_NOCOMP_FL>, C<FS_ENCRYPT_FL>, C<FS_BTREE_FL>,
1247C<FS_INDEX_FL>, C<FS_JOURNAL_DATA_FL>, C<FS_NOTAIL_FL>, C<FS_DIRSYNC_FL>, C<FS_TOPDIR_FL>,
1248C<FS_FL_USER_MODIFIABLE>.
1249
1250C<FS_XFLAG_REALTIME>, C<FS_XFLAG_PREALLOC>, C<FS_XFLAG_IMMUTABLE>, C<FS_XFLAG_APPEND>,
1251C<FS_XFLAG_SYNC>, C<FS_XFLAG_NOATIME>, C<FS_XFLAG_NODUMP>, C<FS_XFLAG_RTINHERIT>,
1252C<FS_XFLAG_PROJINHERIT>, C<FS_XFLAG_NOSYMLINKS>, C<FS_XFLAG_EXTSIZE>, C<FS_XFLAG_EXTSZINHERIT>,
1253C<FS_XFLAG_NODEFRAG>, C<FS_XFLAG_FILESTREAM>, C<FS_XFLAG_DAX>, C<FS_XFLAG_HASATTR>,
1254
1052=item aio_sync $callback->($status) 1255=item aio_sync $callback->($status)
1053 1256
1054Asynchronously call sync and call the callback when finished. 1257Asynchronously call sync and call the callback when finished.
1055 1258
1056=item aio_fsync $fh, $callback->($status) 1259=item aio_fsync $fh, $callback->($status)
1063Asynchronously call fdatasync on the given filehandle and call the 1266Asynchronously call fdatasync on the given filehandle and call the
1064callback with the fdatasync result code. 1267callback with the fdatasync result code.
1065 1268
1066If this call isn't available because your OS lacks it or it couldn't be 1269If this call isn't available because your OS lacks it or it couldn't be
1067detected, it will be emulated by calling C<fsync> instead. 1270detected, it will be emulated by calling C<fsync> instead.
1271
1272=item aio_syncfs $fh, $callback->($status)
1273
1274Asynchronously call the syncfs syscall to sync the filesystem associated
1275to the given filehandle and call the callback with the syncfs result
1276code. If syncfs is not available, calls sync(), but returns C<-1> and sets
1277errno to C<ENOSYS> nevertheless.
1068 1278
1069=item aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status) 1279=item aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status)
1070 1280
1071Sync the data portion of the file specified by C<$offset> and C<$length> 1281Sync the data portion of the file specified by C<$offset> and C<$length>
1072to disk (but NOT the metadata), by calling the Linux-specific 1282to disk (but NOT the metadata), by calling the Linux-specific
1076C<$flags> can be a combination of C<IO::AIO::SYNC_FILE_RANGE_WAIT_BEFORE>, 1286C<$flags> can be a combination of C<IO::AIO::SYNC_FILE_RANGE_WAIT_BEFORE>,
1077C<IO::AIO::SYNC_FILE_RANGE_WRITE> and 1287C<IO::AIO::SYNC_FILE_RANGE_WRITE> and
1078C<IO::AIO::SYNC_FILE_RANGE_WAIT_AFTER>: refer to the sync_file_range 1288C<IO::AIO::SYNC_FILE_RANGE_WAIT_AFTER>: refer to the sync_file_range
1079manpage for details. 1289manpage for details.
1080 1290
1081=item aio_pathsync $path, $callback->($status) 1291=item aio_pathsync $pathname, $callback->($status)
1082 1292
1083This request tries to open, fsync and close the given path. This is a 1293This request tries to open, fsync and close the given path. This is a
1084composite request intended to sync directories after directory operations 1294composite request intended to sync directories after directory operations
1085(E.g. rename). This might not work on all operating systems or have any 1295(E.g. rename). This might not work on all operating systems or have any
1086specific effect, but usually it makes sure that directory changes get 1296specific effect, but usually it makes sure that directory changes get
1117 }; 1327 };
1118 1328
1119 $grp 1329 $grp
1120} 1330}
1121 1331
1122=item aio_msync $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status) 1332=item aio_msync $scalar, $offset = 0, $length = undef, flags = MS_SYNC, $callback->($status)
1123 1333
1124This is a rather advanced IO::AIO call, which only works on mmap(2)ed 1334This is a rather advanced IO::AIO call, which only works on mmap(2)ed
1125scalars (see the C<IO::AIO::mmap> function, although it also works on data 1335scalars (see the C<IO::AIO::mmap> function, although it also works on data
1126scalars managed by the L<Sys::Mmap> or L<Mmap> modules, note that the 1336scalars managed by the L<Sys::Mmap> or L<Mmap> modules, note that the
1127scalar must only be modified in-place while an aio operation is pending on 1337scalar must only be modified in-place while an aio operation is pending on
1129 1339
1130It calls the C<msync> function of your OS, if available, with the memory 1340It calls the C<msync> function of your OS, if available, with the memory
1131area starting at C<$offset> in the string and ending C<$length> bytes 1341area starting at C<$offset> in the string and ending C<$length> bytes
1132later. If C<$length> is negative, counts from the end, and if C<$length> 1342later. If C<$length> is negative, counts from the end, and if C<$length>
1133is C<undef>, then it goes till the end of the string. The flags can be 1343is C<undef>, then it goes till the end of the string. The flags can be
1134a combination of C<IO::AIO::MS_ASYNC>, C<IO::AIO::MS_INVALIDATE> and 1344either C<IO::AIO::MS_ASYNC> or C<IO::AIO::MS_SYNC>, plus an optional
1135C<IO::AIO::MS_SYNC>. 1345C<IO::AIO::MS_INVALIDATE>.
1136 1346
1137=item aio_mtouch $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status) 1347=item aio_mtouch $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status)
1138 1348
1139This is a rather advanced IO::AIO call, which works best on mmap(2)ed 1349This is a rather advanced IO::AIO call, which works best on mmap(2)ed
1140scalars. 1350scalars.
1141 1351
1142It touches (reads or writes) all memory pages in the specified 1352It touches (reads or writes) all memory pages in the specified
1143range inside the scalar. All caveats and parameters are the same 1353range inside the scalar. All caveats and parameters are the same
1144as for C<aio_msync>, above, except for flags, which must be either 1354as for C<aio_msync>, above, except for flags, which must be either
1145C<0> (which reads all pages and ensures they are instantiated) or 1355C<0> (which reads all pages and ensures they are instantiated) or
1146C<IO::AIO::MT_MODIFY>, which modifies the memory page s(by reading and 1356C<IO::AIO::MT_MODIFY>, which modifies the memory pages (by reading and
1147writing an octet from it, which dirties the page). 1357writing an octet from it, which dirties the page).
1148 1358
1149=item aio_mlock $scalar, $offset = 0, $length = undef, $callback->($status) 1359=item aio_mlock $scalar, $offset = 0, $length = undef, $callback->($status)
1150 1360
1151This is a rather advanced IO::AIO call, which works best on mmap(2)ed 1361This is a rather advanced IO::AIO call, which works best on mmap(2)ed
1182documented under L<MISCELLANEOUS FUNCTIONS>. 1392documented under L<MISCELLANEOUS FUNCTIONS>.
1183 1393
1184Example: asynchronously lock all current and future pages into memory. 1394Example: asynchronously lock all current and future pages into memory.
1185 1395
1186 aio_mlockall IO::AIO::MCL_FUTURE; 1396 aio_mlockall IO::AIO::MCL_FUTURE;
1397
1398=item aio_fiemap $fh, $start, $length, $flags, $count, $cb->(\@extents)
1399
1400Queries the extents of the given file (by calling the Linux C<FIEMAP>
1401ioctl, see L<http://cvs.schmorp.de/IO-AIO/doc/fiemap.txt> for details). If
1402the ioctl is not available on your OS, then this request will fail with
1403C<ENOSYS>.
1404
1405C<$start> is the starting offset to query extents for, C<$length> is the
1406size of the range to query - if it is C<undef>, then the whole file will
1407be queried.
1408
1409C<$flags> is a combination of flags (C<IO::AIO::FIEMAP_FLAG_SYNC> or
1410C<IO::AIO::FIEMAP_FLAG_XATTR> - C<IO::AIO::FIEMAP_FLAGS_COMPAT> is also
1411exported), and is normally C<0> or C<IO::AIO::FIEMAP_FLAG_SYNC> to query
1412the data portion.
1413
1414C<$count> is the maximum number of extent records to return. If it is
1415C<undef>, then IO::AIO queries all extents of the range. As a very special
1416case, if it is C<0>, then the callback receives the number of extents
1417instead of the extents themselves (which is unreliable, see below).
1418
1419If an error occurs, the callback receives no arguments. The special
1420C<errno> value C<IO::AIO::EBADR> is available to test for flag errors.
1421
1422Otherwise, the callback receives an array reference with extent
1423structures. Each extent structure is an array reference itself, with the
1424following members:
1425
1426 [$logical, $physical, $length, $flags]
1427
1428Flags is any combination of the following flag values (typically either C<0>
1429or C<IO::AIO::FIEMAP_EXTENT_LAST> (1)):
1430
1431C<IO::AIO::FIEMAP_EXTENT_LAST>, C<IO::AIO::FIEMAP_EXTENT_UNKNOWN>,
1432C<IO::AIO::FIEMAP_EXTENT_DELALLOC>, C<IO::AIO::FIEMAP_EXTENT_ENCODED>,
1433C<IO::AIO::FIEMAP_EXTENT_DATA_ENCRYPTED>, C<IO::AIO::FIEMAP_EXTENT_NOT_ALIGNED>,
1434C<IO::AIO::FIEMAP_EXTENT_DATA_INLINE>, C<IO::AIO::FIEMAP_EXTENT_DATA_TAIL>,
1435C<IO::AIO::FIEMAP_EXTENT_UNWRITTEN>, C<IO::AIO::FIEMAP_EXTENT_MERGED> or
1436C<IO::AIO::FIEMAP_EXTENT_SHARED>.
1437
1438At the time of this writing (Linux 3.2), this request is unreliable unless
1439C<$count> is C<undef>, as the kernel has all sorts of bugs preventing
1440it to return all extents of a range for files with a large number of
1441extents. The code (only) works around all these issues if C<$count> is
1442C<undef>.
1187 1443
1188=item aio_group $callback->(...) 1444=item aio_group $callback->(...)
1189 1445
1190This is a very special aio request: Instead of doing something, it is a 1446This is a very special aio request: Instead of doing something, it is a
1191container for other aio requests, which is useful if you want to bundle 1447container for other aio requests, which is useful if you want to bundle
1228like sleep and file handle readable/writable, the overhead this creates is 1484like sleep and file handle readable/writable, the overhead this creates is
1229immense (it blocks a thread for a long time) so do not use this function 1485immense (it blocks a thread for a long time) so do not use this function
1230except to put your application under artificial I/O pressure. 1486except to put your application under artificial I/O pressure.
1231 1487
1232=back 1488=back
1489
1490
1491=head2 IO::AIO::WD - multiple working directories
1492
1493Your process only has one current working directory, which is used by all
1494threads. This makes it hard to use relative paths (some other component
1495could call C<chdir> at any time, and it is hard to control when the path
1496will be used by IO::AIO).
1497
1498One solution for this is to always use absolute paths. This usually works,
1499but can be quite slow (the kernel has to walk the whole path on every
1500access), and can also be a hassle to implement.
1501
1502Newer POSIX systems have a number of functions (openat, fdopendir,
1503futimensat and so on) that make it possible to specify working directories
1504per operation.
1505
1506For portability, and because the clowns who "designed", or shall I write,
1507perpetrated this new interface were obviously half-drunk, this abstraction
1508cannot be perfect, though.
1509
1510IO::AIO allows you to convert directory paths into a so-called IO::AIO::WD
1511object. This object stores the canonicalised, absolute version of the
1512path, and on systems that allow it, also a directory file descriptor.
1513
1514Everywhere where a pathname is accepted by IO::AIO (e.g. in C<aio_stat>
1515or C<aio_unlink>), one can specify an array reference with an IO::AIO::WD
1516object and a pathname instead (or the IO::AIO::WD object alone, which
1517gets interpreted as C<[$wd, "."]>). If the pathname is absolute, the
1518IO::AIO::WD object is ignored, otherwise the pathname is resolved relative
1519to that IO::AIO::WD object.
1520
1521For example, to get a wd object for F</etc> and then stat F<passwd>
1522inside, you would write:
1523
1524 aio_wd "/etc", sub {
1525 my $etcdir = shift;
1526
1527 # although $etcdir can be undef on error, there is generally no reason
1528 # to check for errors here, as aio_stat will fail with ENOENT
1529 # when $etcdir is undef.
1530
1531 aio_stat [$etcdir, "passwd"], sub {
1532 # yay
1533 };
1534 };
1535
1536The fact that C<aio_wd> is a request and not a normal function shows that
1537creating an IO::AIO::WD object is itself a potentially blocking operation,
1538which is why it is done asynchronously.
1539
1540To stat the directory obtained with C<aio_wd> above, one could write
1541either of the following three request calls:
1542
1543 aio_lstat "/etc" , sub { ... # pathname as normal string
1544 aio_lstat [$wd, "."], sub { ... # "." relative to $wd (i.e. $wd itself)
1545 aio_lstat $wd , sub { ... # shorthand for the previous
1546
1547As with normal pathnames, IO::AIO keeps a copy of the working directory
1548object and the pathname string, so you could write the following without
1549causing any issues due to C<$path> getting reused:
1550
1551 my $path = [$wd, undef];
1552
1553 for my $name (qw(abc def ghi)) {
1554 $path->[1] = $name;
1555 aio_stat $path, sub {
1556 # ...
1557 };
1558 }
1559
1560There are some caveats: when directories get renamed (or deleted), the
1561pathname string doesn't change, so will point to the new directory (or
1562nowhere at all), while the directory fd, if available on the system,
1563will still point to the original directory. Most functions accepting a
1564pathname will use the directory fd on newer systems, and the string on
1565older systems. Some functions (such as C<aio_realpath>) will always rely on
1566the string form of the pathname.
1567
1568So this functionality is mainly useful to get some protection against
1569C<chdir>, to easily get an absolute path out of a relative path for future
1570reference, and to speed up doing many operations in the same directory
1571(e.g. when stat'ing all files in a directory).
1572
1573The following functions implement this working directory abstraction:
1574
1575=over 4
1576
1577=item aio_wd $pathname, $callback->($wd)
1578
1579Asynchonously canonicalise the given pathname and convert it to an
1580IO::AIO::WD object representing it. If possible and supported on the
1581system, also open a directory fd to speed up pathname resolution relative
1582to this working directory.
1583
1584If something goes wrong, then C<undef> is passwd to the callback instead
1585of a working directory object and C<$!> is set appropriately. Since
1586passing C<undef> as working directory component of a pathname fails the
1587request with C<ENOENT>, there is often no need for error checking in the
1588C<aio_wd> callback, as future requests using the value will fail in the
1589expected way.
1590
1591=item IO::AIO::CWD
1592
1593This is a compiletime constant (object) that represents the process
1594current working directory.
1595
1596Specifying this object as working directory object for a pathname is as if
1597the pathname would be specified directly, without a directory object. For
1598example, these calls are functionally identical:
1599
1600 aio_stat "somefile", sub { ... };
1601 aio_stat [IO::AIO::CWD, "somefile"], sub { ... };
1602
1603=back
1604
1605To recover the path associated with an IO::AIO::WD object, you can use
1606C<aio_realpath>:
1607
1608 aio_realpath $wd, sub {
1609 warn "path is $_[0]\n";
1610 };
1611
1612Currently, C<aio_statvfs> always, and C<aio_rename> and C<aio_rmdir>
1613sometimes, fall back to using an absolue path.
1233 1614
1234=head2 IO::AIO::REQ CLASS 1615=head2 IO::AIO::REQ CLASS
1235 1616
1236All non-aggregate C<aio_*> functions return an object of this class when 1617All non-aggregate C<aio_*> functions return an object of this class when
1237called in non-void context. 1618called in non-void context.
1355 1736
1356Sets a feeder/generator on this group: every group can have an attached 1737Sets a feeder/generator on this group: every group can have an attached
1357generator that generates requests if idle. The idea behind this is that, 1738generator that generates requests if idle. The idea behind this is that,
1358although you could just queue as many requests as you want in a group, 1739although you could just queue as many requests as you want in a group,
1359this might starve other requests for a potentially long time. For example, 1740this might starve other requests for a potentially long time. For example,
1360C<aio_scandir> might generate hundreds of thousands C<aio_stat> requests, 1741C<aio_scandir> might generate hundreds of thousands of C<aio_stat>
1361delaying any later requests for a long time. 1742requests, delaying any later requests for a long time.
1362 1743
1363To avoid this, and allow incremental generation of requests, you can 1744To avoid this, and allow incremental generation of requests, you can
1364instead a group and set a feeder on it that generates those requests. The 1745instead a group and set a feeder on it that generates those requests. The
1365feed callback will be called whenever there are few enough (see C<limit>, 1746feed callback will be called whenever there are few enough (see C<limit>,
1366below) requests active in the group itself and is expected to queue more 1747below) requests active in the group itself and is expected to queue more
1415 1796
1416See C<poll_cb> for an example. 1797See C<poll_cb> for an example.
1417 1798
1418=item IO::AIO::poll_cb 1799=item IO::AIO::poll_cb
1419 1800
1420Process some outstanding events on the result pipe. You have to call 1801Process some requests that have reached the result phase (i.e. they have
1802been executed but the results are not yet reported). You have to call
1803this "regularly" to finish outstanding requests.
1804
1421this regularly. Returns C<0> if all events could be processed (or there 1805Returns C<0> if all events could be processed (or there were no
1422were no events to process), or C<-1> if it returned earlier for whatever 1806events to process), or C<-1> if it returned earlier for whatever
1423reason. Returns immediately when no events are outstanding. The amount of 1807reason. Returns immediately when no events are outstanding. The amount
1424events processed depends on the settings of C<IO::AIO::max_poll_req> and 1808of events processed depends on the settings of C<IO::AIO::max_poll_req>,
1425C<IO::AIO::max_poll_time>. 1809C<IO::AIO::max_poll_time> and C<IO::AIO::max_outstanding>.
1426 1810
1427If not all requests were processed for whatever reason, the filehandle 1811If not all requests were processed for whatever reason, the poll file
1428will still be ready when C<poll_cb> returns, so normally you don't have to 1812descriptor will still be ready when C<poll_cb> returns, so normally you
1429do anything special to have it called later. 1813don't have to do anything special to have it called later.
1430 1814
1431Apart from calling C<IO::AIO::poll_cb> when the event filehandle becomes 1815Apart from calling C<IO::AIO::poll_cb> when the event filehandle becomes
1432ready, it can be beneficial to call this function from loops which submit 1816ready, it can be beneficial to call this function from loops which submit
1433a lot of requests, to make sure the results get processed when they become 1817a lot of requests, to make sure the results get processed when they become
1434available and not just when the loop is finished and the event loop takes 1818available and not just when the loop is finished and the event loop takes
1443 poll => 'r', async => 1, 1827 poll => 'r', async => 1,
1444 cb => \&IO::AIO::poll_cb); 1828 cb => \&IO::AIO::poll_cb);
1445 1829
1446=item IO::AIO::poll_wait 1830=item IO::AIO::poll_wait
1447 1831
1448If there are any outstanding requests and none of them in the result 1832Wait until either at least one request is in the result phase or no
1449phase, wait till the result filehandle becomes ready for reading (simply 1833requests are outstanding anymore.
1450does a C<select> on the filehandle. This is useful if you want to 1834
1451synchronously wait for some requests to finish). 1835This is useful if you want to synchronously wait for some requests to
1836become ready, without actually handling them.
1452 1837
1453See C<nreqs> for an example. 1838See C<nreqs> for an example.
1454 1839
1455=item IO::AIO::poll 1840=item IO::AIO::poll
1456 1841
1577 1962
1578This is a very bad function to use in interactive programs because it 1963This is a very bad function to use in interactive programs because it
1579blocks, and a bad way to reduce concurrency because it is inexact: Better 1964blocks, and a bad way to reduce concurrency because it is inexact: Better
1580use an C<aio_group> together with a feed callback. 1965use an C<aio_group> together with a feed callback.
1581 1966
1582It's main use is in scripts without an event loop - when you want to stat 1967Its main use is in scripts without an event loop - when you want to stat
1583a lot of files, you can write somehting like this: 1968a lot of files, you can write something like this:
1584 1969
1585 IO::AIO::max_outstanding 32; 1970 IO::AIO::max_outstanding 32;
1586 1971
1587 for my $path (...) { 1972 for my $path (...) {
1588 aio_stat $path , ...; 1973 aio_stat $path , ...;
1627 2012
1628=back 2013=back
1629 2014
1630=head3 MISCELLANEOUS FUNCTIONS 2015=head3 MISCELLANEOUS FUNCTIONS
1631 2016
1632IO::AIO implements some functions that might be useful, but are not 2017IO::AIO implements some functions that are useful when you want to use
1633asynchronous. 2018some "Advanced I/O" function not available to in Perl, without going the
2019"Asynchronous I/O" route. Many of these have an asynchronous C<aio_*>
2020counterpart.
1634 2021
1635=over 4 2022=over 4
2023
2024=item $numfd = IO::AIO::get_fdlimit
2025
2026This function is I<EXPERIMENTAL> and subject to change.
2027
2028Tries to find the current file descriptor limit and returns it, or
2029C<undef> and sets C<$!> in case of an error. The limit is one larger than
2030the highest valid file descriptor number.
2031
2032=item IO::AIO::min_fdlimit [$numfd]
2033
2034This function is I<EXPERIMENTAL> and subject to change.
2035
2036Try to increase the current file descriptor limit(s) to at least C<$numfd>
2037by changing the soft or hard file descriptor resource limit. If C<$numfd>
2038is missing, it will try to set a very high limit, although this is not
2039recommended when you know the actual minimum that you require.
2040
2041If the limit cannot be raised enough, the function makes a best-effort
2042attempt to increase the limit as much as possible, using various
2043tricks, while still failing. You can query the resulting limit using
2044C<IO::AIO::get_fdlimit>.
2045
2046If an error occurs, returns C<undef> and sets C<$!>, otherwise returns
2047true.
1636 2048
1637=item IO::AIO::sendfile $ofh, $ifh, $offset, $count 2049=item IO::AIO::sendfile $ofh, $ifh, $offset, $count
1638 2050
1639Calls the C<eio_sendfile_sync> function, which is like C<aio_sendfile>, 2051Calls the C<eio_sendfile_sync> function, which is like C<aio_sendfile>,
1640but is blocking (this makes most sense if you know the input data is 2052but is blocking (this makes most sense if you know the input data is
1645 2057
1646=item IO::AIO::fadvise $fh, $offset, $len, $advice 2058=item IO::AIO::fadvise $fh, $offset, $len, $advice
1647 2059
1648Simply calls the C<posix_fadvise> function (see its 2060Simply calls the C<posix_fadvise> function (see its
1649manpage for details). The following advice constants are 2061manpage for details). The following advice constants are
1650avaiable: C<IO::AIO::FADV_NORMAL>, C<IO::AIO::FADV_SEQUENTIAL>, 2062available: C<IO::AIO::FADV_NORMAL>, C<IO::AIO::FADV_SEQUENTIAL>,
1651C<IO::AIO::FADV_RANDOM>, C<IO::AIO::FADV_NOREUSE>, 2063C<IO::AIO::FADV_RANDOM>, C<IO::AIO::FADV_NOREUSE>,
1652C<IO::AIO::FADV_WILLNEED>, C<IO::AIO::FADV_DONTNEED>. 2064C<IO::AIO::FADV_WILLNEED>, C<IO::AIO::FADV_DONTNEED>.
1653 2065
1654On systems that do not implement C<posix_fadvise>, this function returns 2066On systems that do not implement C<posix_fadvise>, this function returns
1655ENOSYS, otherwise the return value of C<posix_fadvise>. 2067ENOSYS, otherwise the return value of C<posix_fadvise>.
1656 2068
1657=item IO::AIO::madvise $scalar, $offset, $len, $advice 2069=item IO::AIO::madvise $scalar, $offset, $len, $advice
1658 2070
1659Simply calls the C<posix_madvise> function (see its 2071Simply calls the C<posix_madvise> function (see its
1660manpage for details). The following advice constants are 2072manpage for details). The following advice constants are
1661avaiable: C<IO::AIO::MADV_NORMAL>, C<IO::AIO::MADV_SEQUENTIAL>, 2073available: C<IO::AIO::MADV_NORMAL>, C<IO::AIO::MADV_SEQUENTIAL>,
1662C<IO::AIO::MADV_RANDOM>, C<IO::AIO::MADV_WILLNEED>, C<IO::AIO::MADV_DONTNEED>. 2074C<IO::AIO::MADV_RANDOM>, C<IO::AIO::MADV_WILLNEED>,
2075C<IO::AIO::MADV_DONTNEED>.
2076
2077If C<$offset> is negative, counts from the end. If C<$length> is negative,
2078the remaining length of the C<$scalar> is used. If possible, C<$length>
2079will be reduced to fit into the C<$scalar>.
1663 2080
1664On systems that do not implement C<posix_madvise>, this function returns 2081On systems that do not implement C<posix_madvise>, this function returns
1665ENOSYS, otherwise the return value of C<posix_madvise>. 2082ENOSYS, otherwise the return value of C<posix_madvise>.
1666 2083
1667=item IO::AIO::mprotect $scalar, $offset, $len, $protect 2084=item IO::AIO::mprotect $scalar, $offset, $len, $protect
1668 2085
1669Simply calls the C<mprotect> function on the preferably AIO::mmap'ed 2086Simply calls the C<mprotect> function on the preferably AIO::mmap'ed
1670$scalar (see its manpage for details). The following protect 2087$scalar (see its manpage for details). The following protect
1671constants are avaiable: C<IO::AIO::PROT_NONE>, C<IO::AIO::PROT_READ>, 2088constants are available: C<IO::AIO::PROT_NONE>, C<IO::AIO::PROT_READ>,
1672C<IO::AIO::PROT_WRITE>, C<IO::AIO::PROT_EXEC>. 2089C<IO::AIO::PROT_WRITE>, C<IO::AIO::PROT_EXEC>.
2090
2091If C<$offset> is negative, counts from the end. If C<$length> is negative,
2092the remaining length of the C<$scalar> is used. If possible, C<$length>
2093will be reduced to fit into the C<$scalar>.
1673 2094
1674On systems that do not implement C<mprotect>, this function returns 2095On systems that do not implement C<mprotect>, this function returns
1675ENOSYS, otherwise the return value of C<mprotect>. 2096ENOSYS, otherwise the return value of C<mprotect>.
1676 2097
1677=item IO::AIO::mmap $scalar, $length, $prot, $flags, $fh[, $offset] 2098=item IO::AIO::mmap $scalar, $length, $prot, $flags, $fh[, $offset]
1678 2099
1679Memory-maps a file (or anonymous memory range) and attaches it to the 2100Memory-maps a file (or anonymous memory range) and attaches it to the
1680given C<$scalar>, which will act like a string scalar. 2101given C<$scalar>, which will act like a string scalar. Returns true on
2102success, and false otherwise.
1681 2103
2104The scalar must exist, but its contents do not matter - this means you
2105cannot use a nonexistant array or hash element. When in doubt, C<undef>
2106the scalar first.
2107
1682The only operations allowed on the scalar are C<substr>/C<vec> that don't 2108The only operations allowed on the mmapped scalar are C<substr>/C<vec>,
1683change the string length, and most read-only operations such as copying it 2109which don't change the string length, and most read-only operations such
1684or searching it with regexes and so on. 2110as copying it or searching it with regexes and so on.
1685 2111
1686Anything else is unsafe and will, at best, result in memory leaks. 2112Anything else is unsafe and will, at best, result in memory leaks.
1687 2113
1688The memory map associated with the C<$scalar> is automatically removed 2114The memory map associated with the C<$scalar> is automatically removed
1689when the C<$scalar> is destroyed, or when the C<IO::AIO::mmap> or 2115when the C<$scalar> is undef'd or destroyed, or when the C<IO::AIO::mmap>
1690C<IO::AIO::munmap> functions are called. 2116or C<IO::AIO::munmap> functions are called on it.
1691 2117
1692This calls the C<mmap>(2) function internally. See your system's manual 2118This calls the C<mmap>(2) function internally. See your system's manual
1693page for details on the C<$length>, C<$prot> and C<$flags> parameters. 2119page for details on the C<$length>, C<$prot> and C<$flags> parameters.
1694 2120
1695The C<$length> must be larger than zero and smaller than the actual 2121The C<$length> must be larger than zero and smaller than the actual
1696filesize. 2122filesize.
1697 2123
1698C<$prot> is a combination of C<IO::AIO::PROT_NONE>, C<IO::AIO::PROT_EXEC>, 2124C<$prot> is a combination of C<IO::AIO::PROT_NONE>, C<IO::AIO::PROT_EXEC>,
1699C<IO::AIO::PROT_READ> and/or C<IO::AIO::PROT_WRITE>, 2125C<IO::AIO::PROT_READ> and/or C<IO::AIO::PROT_WRITE>,
1700 2126
1701C<$flags> can be a combination of C<IO::AIO::MAP_SHARED> or 2127C<$flags> can be a combination of
1702C<IO::AIO::MAP_PRIVATE>, or a number of system-specific flags (when 2128C<IO::AIO::MAP_SHARED> or
1703not available, the are defined as 0): C<IO::AIO::MAP_ANONYMOUS> 2129C<IO::AIO::MAP_PRIVATE>,
2130or a number of system-specific flags (when not available, the are C<0>):
1704(which is set to C<MAP_ANON> if your system only provides this 2131C<IO::AIO::MAP_ANONYMOUS> (which is set to C<MAP_ANON> if your system only provides this constant),
1705constant), C<IO::AIO::MAP_HUGETLB>, C<IO::AIO::MAP_LOCKED>, 2132C<IO::AIO::MAP_LOCKED>,
1706C<IO::AIO::MAP_NORESERVE>, C<IO::AIO::MAP_POPULATE> or 2133C<IO::AIO::MAP_NORESERVE>,
2134C<IO::AIO::MAP_POPULATE>,
1707C<IO::AIO::MAP_NONBLOCK> 2135C<IO::AIO::MAP_NONBLOCK>,
2136C<IO::AIO::MAP_FIXED>,
2137C<IO::AIO::MAP_GROWSDOWN>,
2138C<IO::AIO::MAP_32BIT>,
2139C<IO::AIO::MAP_HUGETLB> or
2140C<IO::AIO::MAP_STACK>.
1708 2141
1709If C<$fh> is C<undef>, then a file descriptor of C<-1> is passed. 2142If C<$fh> is C<undef>, then a file descriptor of C<-1> is passed.
1710 2143
1711C<$offset> is the offset from the start of the file - it generally must be 2144C<$offset> is the offset from the start of the file - it generally must be
1712a multiple of C<IO::AIO::PAGESIZE> and defaults to C<0>. 2145a multiple of C<IO::AIO::PAGESIZE> and defaults to C<0>.
1726 2159
1727=item IO::AIO::munmap $scalar 2160=item IO::AIO::munmap $scalar
1728 2161
1729Removes a previous mmap and undefines the C<$scalar>. 2162Removes a previous mmap and undefines the C<$scalar>.
1730 2163
2164=item IO::AIO::mremap $scalar, $new_length, $flags = 0[, $new_address = 0]
2165
2166Calls the Linux-specific mremap(2) system call. The C<$scalar> must have
2167been mapped by C<IO::AIO::mmap>, and C<$flags> must currently either be
2168C<0> or C<IO::AIO::MREMAP_MAYMOVE>.
2169
2170Returns true if successful, and false otherwise. If the underlying mmapped
2171region has changed address, then the true value has the numerical value
2172C<1>, otherwise it has the numerical value C<0>:
2173
2174 my $success = IO::AIO::mremap $mmapped, 8192, IO::AIO::MREMAP_MAYMOVE
2175 or die "mremap: $!";
2176
2177 if ($success*1) {
2178 warn "scalar has chanegd address in memory\n";
2179 }
2180
2181C<IO::AIO::MREMAP_FIXED> and the C<$new_address> argument are currently
2182implemented, but not supported and might go away in a future version.
2183
2184On systems where this call is not supported or is not emulated, this call
2185returns falls and sets C<$!> to C<ENOSYS>.
2186
1731=item IO::AIO::munlock $scalar, $offset = 0, $length = undef 2187=item IO::AIO::munlock $scalar, $offset = 0, $length = undef
1732 2188
1733Calls the C<munlock> function, undoing the effects of a previous 2189Calls the C<munlock> function, undoing the effects of a previous
1734C<aio_mlock> call (see its description for details). 2190C<aio_mlock> call (see its description for details).
1735 2191
1737 2193
1738Calls the C<munlockall> function. 2194Calls the C<munlockall> function.
1739 2195
1740On systems that do not implement C<munlockall>, this function returns 2196On systems that do not implement C<munlockall>, this function returns
1741ENOSYS, otherwise the return value of C<munlockall>. 2197ENOSYS, otherwise the return value of C<munlockall>.
2198
2199=item IO::AIO::splice $r_fh, $r_off, $w_fh, $w_off, $length, $flags
2200
2201Calls the GNU/Linux C<splice(2)> syscall, if available. If C<$r_off> or
2202C<$w_off> are C<undef>, then C<NULL> is passed for these, otherwise they
2203should be the file offset.
2204
2205C<$r_fh> and C<$w_fh> should not refer to the same file, as splice might
2206silently corrupt the data in this case.
2207
2208The following symbol flag values are available: C<IO::AIO::SPLICE_F_MOVE>,
2209C<IO::AIO::SPLICE_F_NONBLOCK>, C<IO::AIO::SPLICE_F_MORE> and
2210C<IO::AIO::SPLICE_F_GIFT>.
2211
2212See the C<splice(2)> manpage for details.
2213
2214=item IO::AIO::tee $r_fh, $w_fh, $length, $flags
2215
2216Calls the GNU/Linux C<tee(2)> syscall, see its manpage and the
2217description for C<IO::AIO::splice> above for details.
2218
2219=item $actual_size = IO::AIO::pipesize $r_fh[, $new_size]
2220
2221Attempts to query or change the pipe buffer size. Obviously works only
2222on pipes, and currently works only on GNU/Linux systems, and fails with
2223C<-1>/C<ENOSYS> everywhere else. If anybody knows how to influence pipe buffer
2224size on other systems, drop me a note.
2225
2226=item ($rfh, $wfh) = IO::AIO::pipe2 [$flags]
2227
2228This is a direct interface to the Linux L<pipe2(2)> system call. If
2229C<$flags> is missing or C<0>, then this should be the same as a call to
2230perl's built-in C<pipe> function and create a new pipe, and works on
2231systems that lack the pipe2 syscall. On win32, this case invokes C<_pipe
2232(..., 4096, O_BINARY)>.
2233
2234If C<$flags> is non-zero, it tries to invoke the pipe2 system call with
2235the given flags (Linux 2.6.27, glibc 2.9).
2236
2237On success, the read and write file handles are returned.
2238
2239On error, nothing will be returned. If the pipe2 syscall is missing and
2240C<$flags> is non-zero, fails with C<ENOSYS>.
2241
2242Please refer to L<pipe2(2)> for more info on the C<$flags>, but at the
2243time of this writing, C<IO::AIO::O_CLOEXEC>, C<IO::AIO::O_NONBLOCK> and
2244C<IO::AIO::O_DIRECT> (Linux 3.4, for packet-based pipes) were supported.
2245
2246Example: create a pipe race-free w.r.t. threads and fork:
2247
2248 my ($rfh, $wfh) = IO::AIO::pipe2 IO::AIO::O_CLOEXEC
2249 or die "pipe2: $!\n";
2250
2251=item $fh = IO::AIO::eventfd [$initval, [$flags]]
2252
2253This is a direct interface to the Linux L<eventfd(2)> system call. The
2254(unhelpful) defaults for C<$initval> and C<$flags> are C<0> for both.
2255
2256On success, the new eventfd filehandle is returned, otherwise returns
2257C<undef>. If the eventfd syscall is missing, fails with C<ENOSYS>.
2258
2259Please refer to L<eventfd(2)> for more info on this call.
2260
2261The following symbol flag values are available: C<IO::AIO::EFD_CLOEXEC>,
2262C<IO::AIO::EFD_NONBLOCK> and C<IO::AIO::EFD_SEMAPHORE> (Linux 2.6.30).
2263
2264Example: create a new eventfd filehandle:
2265
2266 $fh = IO::AIO::eventfd 0, IO::AIO::O_CLOEXEC
2267 or die "eventfd: $!\n";
2268
2269=item $fh = IO::AIO::timerfd_create $clockid[, $flags]
2270
2271This is a direct interface to the Linux L<timerfd_create(2)> system call. The
2272(unhelpful) default for C<$flags> is C<0>.
2273
2274On success, the new timerfd filehandle is returned, otherwise returns
2275C<undef>. If the eventfd syscall is missing, fails with C<ENOSYS>.
2276
2277Please refer to L<timerfd_create(2)> for more info on this call.
2278
2279The following C<$clockid> values are
2280available: C<IO::AIO::CLOCK_REALTIME>, C<IO::AIO::CLOCK_MONOTONIC>
2281C<IO::AIO::CLOCK_CLOCK_BOOTTIME> (Linux 3.15)
2282C<IO::AIO::CLOCK_CLOCK_REALTIME_ALARM> (Linux 3.11) and
2283C<IO::AIO::CLOCK_CLOCK_BOOTTIME_ALARM> (Linux 3.11).
2284
2285The following C<$flags> values are available (Linux
22862.6.27): C<IO::AIO::TFD_NONBLOCK> and C<IO::AIO::TFD_CLOEXEC>.
2287
2288Example: create a new timerfd and set it to one-second repeated alarms,
2289then wait for two alarms:
2290
2291 my $fh = IO::AIO::timerfd_create IO::AIO::CLOCK_BOOTTIME, IO::AIO::TFD_CLOEXEC
2292 or die "timerfd_create: $!\n";
2293
2294 defined IO::AIO::timerfd_settime $fh, 0, 1, 1
2295 or die "timerfd_settime: $!\n";
2296
2297 for (1..2) {
2298 8 == sysread $fh, my $buf, 8
2299 or die "timerfd read failure\n";
2300
2301 printf "number of expirations (likely 1): %d\n",
2302 unpack "Q", $buf;
2303 }
2304
2305=item ($cur_interval, $cur_value) = IO::AIO::timerfd_settime $fh, $flags, $new_interval, $nbw_value
2306
2307This is a direct interface to the Linux L<timerfd_settime(2)> system
2308call. Please refer to its manpage for more info on this call.
2309
2310The new itimerspec is specified using two (possibly fractional) second
2311values, C<$new_interval> and C<$new_value>).
2312
2313On success, the current interval and value are returned (as per
2314C<timerfd_gettime>). On failure, the empty list is returned.
2315
2316The following C<$flags> values are
2317available: C<IO::AIO::TFD_TIMER_ABSTIME> and
2318C<IO::AIO::TFD_TIMER_CANCEL_ON_SET>.
2319
2320See C<IO::AIO::timerfd_create> for a full example.
2321
2322=item ($cur_interval, $cur_value) = IO::AIO::timerfd_gettime $fh
2323
2324This is a direct interface to the Linux L<timerfd_gettime(2)> system
2325call. Please refer to its manpage for more info on this call.
2326
2327On success, returns the current values of interval and value for the given
2328timerfd (as potentially fractional second values). On failure, the empty
2329list is returned.
1742 2330
1743=back 2331=back
1744 2332
1745=cut 2333=cut
1746 2334
1781 Danga::Socket->AddOtherFds (IO::AIO::poll_fileno => 2369 Danga::Socket->AddOtherFds (IO::AIO::poll_fileno =>
1782 \&IO::AIO::poll_cb); 2370 \&IO::AIO::poll_cb);
1783 2371
1784=head2 FORK BEHAVIOUR 2372=head2 FORK BEHAVIOUR
1785 2373
1786This module should do "the right thing" when the process using it forks: 2374Usage of pthreads in a program changes the semantics of fork
2375considerably. Specifically, only async-safe functions can be called after
2376fork. Perl doesn't know about this, so in general, you cannot call fork
2377with defined behaviour in perl if pthreads are involved. IO::AIO uses
2378pthreads, so this applies, but many other extensions and (for inexplicable
2379reasons) perl itself often is linked against pthreads, so this limitation
2380applies to quite a lot of perls.
1787 2381
1788Before the fork, IO::AIO enters a quiescent state where no requests 2382This module no longer tries to fight your OS, or POSIX. That means IO::AIO
1789can be added in other threads and no results will be processed. After 2383only works in the process that loaded it. Forking is fully supported, but
1790the fork the parent simply leaves the quiescent state and continues 2384using IO::AIO in the child is not.
1791request/result processing, while the child frees the request/result queue
1792(so that the requests started before the fork will only be handled in the
1793parent). Threads will be started on demand until the limit set in the
1794parent process has been reached again.
1795 2385
1796In short: the parent will, after a short pause, continue as if fork had 2386You might get around by not I<using> IO::AIO before (or after)
1797not been called, while the child will act as if IO::AIO has not been used 2387forking. You could also try to call the L<IO::AIO::reinit> function in the
1798yet. 2388child:
2389
2390=over 4
2391
2392=item IO::AIO::reinit
2393
2394Abandons all current requests and I/O threads and simply reinitialises all
2395data structures. This is not an operation supported by any standards, but
2396happens to work on GNU/Linux and some newer BSD systems.
2397
2398The only reasonable use for this function is to call it after forking, if
2399C<IO::AIO> was used in the parent. Calling it while IO::AIO is active in
2400the process will result in undefined behaviour. Calling it at any time
2401will also result in any undefined (by POSIX) behaviour.
2402
2403=back
2404
2405=head2 LINUX-SPECIFIC CALLS
2406
2407When a call is documented as "linux-specific" then this means it
2408originated on GNU/Linux. C<IO::AIO> will usually try to autodetect the
2409availability and compatibility of such calls regardless of the platform
2410it is compiled on, so platforms such as FreeBSD which often implement
2411these calls will work. When in doubt, call them and see if they fail wth
2412C<ENOSYS>.
1799 2413
1800=head2 MEMORY USAGE 2414=head2 MEMORY USAGE
1801 2415
1802Per-request usage: 2416Per-request usage:
1803 2417
1816temporary buffers, and each thread requires a stack and other data 2430temporary buffers, and each thread requires a stack and other data
1817structures (usually around 16k-128k, depending on the OS). 2431structures (usually around 16k-128k, depending on the OS).
1818 2432
1819=head1 KNOWN BUGS 2433=head1 KNOWN BUGS
1820 2434
1821Known bugs will be fixed in the next release. 2435Known bugs will be fixed in the next release :)
2436
2437=head1 KNOWN ISSUES
2438
2439Calls that try to "import" foreign memory areas (such as C<IO::AIO::mmap>
2440or C<IO::AIO::aio_slurp>) do not work with generic lvalues, such as
2441non-created hash slots or other scalars I didn't think of. It's best to
2442avoid such and either use scalar variables or making sure that the scalar
2443exists (e.g. by storing C<undef>) and isn't "funny" (e.g. tied).
2444
2445I am not sure anything can be done about this, so this is considered a
2446known issue, rather than a bug.
1822 2447
1823=head1 SEE ALSO 2448=head1 SEE ALSO
1824 2449
1825L<AnyEvent::AIO> for easy integration into event loops, L<Coro::AIO> for a 2450L<AnyEvent::AIO> for easy integration into event loops, L<Coro::AIO> for a
1826more natural syntax. 2451more natural syntax.

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines