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.6 by root, Sun Jul 10 22:19:48 2005 UTC vs.
Revision 1.264 by root, Mon Jul 18 07:48:01 2016 UTC

4 4
5=head1 SYNOPSIS 5=head1 SYNOPSIS
6 6
7 use IO::AIO; 7 use IO::AIO;
8 8
9 aio_open "/etc/passwd", O_RDONLY, 0, sub { 9 aio_open "/etc/passwd", IO::AIO::O_RDONLY, 0, sub {
10 my ($fh) = @_; 10 my $fh = shift
11 or die "/etc/passwd: $!";
11 ... 12 ...
12 }; 13 };
13 14
14 aio_unlink "/tmp/file", sub { }; 15 aio_unlink "/tmp/file", sub { };
15 16
16 aio_read $fh, 30000, 1024, $buffer, 0, sub { 17 aio_read $fh, 30000, 1024, $buffer, 0, sub {
17 $_[0] >= 0 or die "read error: $!"; 18 $_[0] > 0 or die "read error: $!";
18 }; 19 };
19 20
20 # Event 21 # version 2+ has request and group objects
21 Event->io (fd => IO::AIO::poll_fileno, 22 use IO::AIO 2;
22 poll => 'r', async => 1,
23 cb => \&IO::AIO::poll_cb);
24 23
25 # Glib/Gtk2 24 aioreq_pri 4; # give next request a very high priority
26 add_watch Glib::IO IO::AIO::poll_fileno, 25 my $req = aio_unlink "/tmp/file", sub { };
27 \&IO::AIO::poll_cb; 26 $req->cancel; # cancel request if still in queue
28 27
29 # Tk 28 my $grp = aio_group sub { print "all stats done\n" };
30 Tk::Event::IO->fileevent (IO::AIO::poll_fileno, "", 29 add $grp aio_stat "..." for ...;
31 readable => \&IO::AIO::poll_cb);
32 30
33=head1 DESCRIPTION 31=head1 DESCRIPTION
34 32
35This module implements asynchronous I/O using whatever means your 33This module implements asynchronous I/O using whatever means your
36operating system supports. 34operating system supports. It is implemented as an interface to C<libeio>
35(L<http://software.schmorp.de/pkg/libeio.html>).
37 36
37Asynchronous means that operations that can normally block your program
38(e.g. reading from disk) will be done asynchronously: the operation
39will still block, but you can do something else in the meantime. This
40is extremely useful for programs that need to stay interactive even
41when doing heavy I/O (GUI programs, high performance network servers
42etc.), but can also be used to easily do operations in parallel that are
43normally done sequentially, e.g. stat'ing many files, which is much faster
44on a RAID volume or over NFS when you do a number of stat operations
45concurrently.
46
47While most of this works on all types of file descriptors (for
48example sockets), using these functions on file descriptors that
49support nonblocking operation (again, sockets, pipes etc.) is
50very inefficient. Use an event loop for that (such as the L<EV>
51module): IO::AIO will naturally fit into such an event loop itself.
52
38Currently, a number of threads are started that execute your read/writes 53In this version, a number of threads are started that execute your
39and signal their completion. You don't need thread support in your libc or 54requests and signal their completion. You don't need thread support
40perl, and the threads created by this module will not be visible to the 55in perl, and the threads created by this module will not be visible
41pthreads library. In the future, this module might make use of the native 56to perl. In the future, this module might make use of the native aio
42aio functions available on many operating systems. However, they are often 57functions available on many operating systems. However, they are often
43not well-supported (Linux doesn't allow them on normal files currently, 58not well-supported or restricted (GNU/Linux doesn't allow them on normal
44for example), and they would only support aio_read and aio_write, so the 59files currently, for example), and they would only support aio_read and
45remaining functionality would have to be implemented using threads anyway. 60aio_write, so the remaining functionality would have to be implemented
61using threads anyway.
46 62
47Although the module will work with in the presence of other threads, it is 63Although the module will work in the presence of other (Perl-) threads,
48currently not reentrant, so use appropriate locking yourself. 64it is currently not reentrant in any way, so use appropriate locking
65yourself, always call C<poll_cb> from within the same thread, or never
66call C<poll_cb> (or other C<aio_> functions) recursively.
67
68=head2 EXAMPLE
69
70This is a simple example that uses the EV module and loads
71F</etc/passwd> asynchronously:
72
73 use EV;
74 use IO::AIO;
75
76 # register the IO::AIO callback with EV
77 my $aio_w = EV::io IO::AIO::poll_fileno, EV::READ, \&IO::AIO::poll_cb;
78
79 # queue the request to open /etc/passwd
80 aio_open "/etc/passwd", IO::AIO::O_RDONLY, 0, sub {
81 my $fh = shift
82 or die "error while opening: $!";
83
84 # stat'ing filehandles is generally non-blocking
85 my $size = -s $fh;
86
87 # queue a request to read the file
88 my $contents;
89 aio_read $fh, 0, $size, $contents, 0, sub {
90 $_[0] == $size
91 or die "short read: $!";
92
93 close $fh;
94
95 # file contents now in $contents
96 print $contents;
97
98 # exit event loop and program
99 EV::break;
100 };
101 };
102
103 # possibly queue up other requests, or open GUI windows,
104 # check for sockets etc. etc.
105
106 # process events as long as there are some:
107 EV::run;
108
109=head1 REQUEST ANATOMY AND LIFETIME
110
111Every C<aio_*> function creates a request. which is a C data structure not
112directly visible to Perl.
113
114If called in non-void context, every request function returns a Perl
115object representing the request. In void context, nothing is returned,
116which saves a bit of memory.
117
118The perl object is a fairly standard ref-to-hash object. The hash contents
119are not used by IO::AIO so you are free to store anything you like in it.
120
121During their existance, aio requests travel through the following states,
122in order:
123
124=over 4
125
126=item ready
127
128Immediately after a request is created it is put into the ready state,
129waiting for a thread to execute it.
130
131=item execute
132
133A thread has accepted the request for processing and is currently
134executing it (e.g. blocking in read).
135
136=item pending
137
138The request has been executed and is waiting for result processing.
139
140While request submission and execution is fully asynchronous, result
141processing is not and relies on the perl interpreter calling C<poll_cb>
142(or another function with the same effect).
143
144=item result
145
146The request results are processed synchronously by C<poll_cb>.
147
148The C<poll_cb> function will process all outstanding aio requests by
149calling their callbacks, freeing memory associated with them and managing
150any groups they are contained in.
151
152=item done
153
154Request has reached the end of its lifetime and holds no resources anymore
155(except possibly for the Perl object, but its connection to the actual
156aio request is severed and calling its methods will either do nothing or
157result in a runtime error).
158
159=back
49 160
50=cut 161=cut
51 162
52package IO::AIO; 163package IO::AIO;
53 164
165use Carp ();
166
167use common::sense;
168
54use base 'Exporter'; 169use base 'Exporter';
55 170
56use Fcntl ();
57
58BEGIN { 171BEGIN {
59 $VERSION = 0.2; 172 our $VERSION = 4.34;
60 173
61 @EXPORT = qw(aio_read aio_write aio_open aio_close aio_stat aio_lstat aio_unlink 174 our @AIO_REQ = qw(aio_sendfile aio_seek aio_read aio_write aio_open aio_close
62 aio_fsync aio_fdatasync aio_readahead); 175 aio_stat aio_lstat aio_unlink aio_rmdir aio_readdir aio_readdirx
63 @EXPORT_OK = qw(poll_fileno poll_cb min_parallel max_parallel max_outstanding nreqs); 176 aio_scandir aio_symlink aio_readlink aio_realpath aio_fcntl aio_ioctl
177 aio_sync aio_fsync aio_syncfs aio_fdatasync aio_sync_file_range
178 aio_pathsync aio_readahead aio_fiemap aio_allocate
179 aio_rename aio_link aio_move aio_copy aio_group
180 aio_nop aio_mknod aio_load aio_rmtree aio_mkdir aio_chown
181 aio_chmod aio_utime aio_truncate
182 aio_msync aio_mtouch aio_mlock aio_mlockall
183 aio_statvfs
184 aio_wd);
185
186 our @EXPORT = (@AIO_REQ, qw(aioreq_pri aioreq_nice));
187 our @EXPORT_OK = qw(poll_fileno poll_cb poll_wait flush
188 min_parallel max_parallel max_idle idle_timeout
189 nreqs nready npending nthreads
190 max_poll_time max_poll_reqs
191 sendfile fadvise madvise
192 mmap munmap munlock munlockall);
193
194 push @AIO_REQ, qw(aio_busy); # not exported
195
196 @IO::AIO::GRP::ISA = 'IO::AIO::REQ';
64 197
65 require XSLoader; 198 require XSLoader;
66 XSLoader::load IO::AIO, $VERSION; 199 XSLoader::load ("IO::AIO", $VERSION);
67} 200}
68 201
69=head1 FUNCTIONS 202=head1 FUNCTIONS
70 203
71=head2 AIO FUNCTIONS 204=head2 QUICK OVERVIEW
205
206This section simply lists the prototypes most of the functions for
207quick reference. See the following sections for function-by-function
208documentation.
209
210 aio_wd $pathname, $callback->($wd)
211 aio_open $pathname, $flags, $mode, $callback->($fh)
212 aio_close $fh, $callback->($status)
213 aio_seek $fh,$offset,$whence, $callback->($offs)
214 aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval)
215 aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval)
216 aio_sendfile $out_fh, $in_fh, $in_offset, $length, $callback->($retval)
217 aio_readahead $fh,$offset,$length, $callback->($retval)
218 aio_stat $fh_or_path, $callback->($status)
219 aio_lstat $fh, $callback->($status)
220 aio_statvfs $fh_or_path, $callback->($statvfs)
221 aio_utime $fh_or_path, $atime, $mtime, $callback->($status)
222 aio_chown $fh_or_path, $uid, $gid, $callback->($status)
223 aio_chmod $fh_or_path, $mode, $callback->($status)
224 aio_truncate $fh_or_path, $offset, $callback->($status)
225 aio_allocate $fh, $mode, $offset, $len, $callback->($status)
226 aio_fiemap $fh, $start, $length, $flags, $count, $cb->(\@extents)
227 aio_unlink $pathname, $callback->($status)
228 aio_mknod $pathname, $mode, $dev, $callback->($status)
229 aio_link $srcpath, $dstpath, $callback->($status)
230 aio_symlink $srcpath, $dstpath, $callback->($status)
231 aio_readlink $pathname, $callback->($link)
232 aio_realpath $pathname, $callback->($path)
233 aio_rename $srcpath, $dstpath, $callback->($status)
234 aio_mkdir $pathname, $mode, $callback->($status)
235 aio_rmdir $pathname, $callback->($status)
236 aio_readdir $pathname, $callback->($entries)
237 aio_readdirx $pathname, $flags, $callback->($entries, $flags)
238 IO::AIO::READDIR_DENTS IO::AIO::READDIR_DIRS_FIRST
239 IO::AIO::READDIR_STAT_ORDER IO::AIO::READDIR_FOUND_UNKNOWN
240 aio_scandir $pathname, $maxreq, $callback->($dirs, $nondirs)
241 aio_load $pathname, $data, $callback->($status)
242 aio_copy $srcpath, $dstpath, $callback->($status)
243 aio_move $srcpath, $dstpath, $callback->($status)
244 aio_rmtree $pathname, $callback->($status)
245 aio_fcntl $fh, $cmd, $arg, $callback->($status)
246 aio_ioctl $fh, $request, $buf, $callback->($status)
247 aio_sync $callback->($status)
248 aio_syncfs $fh, $callback->($status)
249 aio_fsync $fh, $callback->($status)
250 aio_fdatasync $fh, $callback->($status)
251 aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status)
252 aio_pathsync $pathname, $callback->($status)
253 aio_msync $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status)
254 aio_mtouch $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status)
255 aio_mlock $scalar, $offset = 0, $length = undef, $callback->($status)
256 aio_mlockall $flags, $callback->($status)
257 aio_group $callback->(...)
258 aio_nop $callback->()
259
260 $prev_pri = aioreq_pri [$pri]
261 aioreq_nice $pri_adjust
262
263 IO::AIO::poll_wait
264 IO::AIO::poll_cb
265 IO::AIO::poll
266 IO::AIO::flush
267 IO::AIO::max_poll_reqs $nreqs
268 IO::AIO::max_poll_time $seconds
269 IO::AIO::min_parallel $nthreads
270 IO::AIO::max_parallel $nthreads
271 IO::AIO::max_idle $nthreads
272 IO::AIO::idle_timeout $seconds
273 IO::AIO::max_outstanding $maxreqs
274 IO::AIO::nreqs
275 IO::AIO::nready
276 IO::AIO::npending
277
278 IO::AIO::sendfile $ofh, $ifh, $offset, $count
279 IO::AIO::fadvise $fh, $offset, $len, $advice
280 IO::AIO::mmap $scalar, $length, $prot, $flags[, $fh[, $offset]]
281 IO::AIO::munmap $scalar
282 IO::AIO::madvise $scalar, $offset, $length, $advice
283 IO::AIO::mprotect $scalar, $offset, $length, $protect
284 IO::AIO::munlock $scalar, $offset = 0, $length = undef
285 IO::AIO::munlockall
286
287=head2 API NOTES
72 288
73All the C<aio_*> calls are more or less thin wrappers around the syscall 289All the C<aio_*> calls are more or less thin wrappers around the syscall
74with the same name (sans C<aio_>). The arguments are similar or identical, 290with the same name (sans C<aio_>). The arguments are similar or identical,
75and they all accept an additional C<$callback> argument which must be 291and they all accept an additional (and optional) C<$callback> argument
76a code reference. This code reference will get called with the syscall 292which must be a code reference. This code reference will be called after
293the syscall has been executed in an asynchronous fashion. The results
294of the request will be passed as arguments to the callback (and, if an
295error occured, in C<$!>) - for most requests the syscall return code (e.g.
77return code (e.g. most syscalls return C<-1> on error, unlike perl, which 296most syscalls return C<-1> on error, unlike perl, which usually delivers
78usually delivers "false") as it's sole argument when the given syscall has 297"false").
79been executed asynchronously.
80 298
81All functions that expect a filehandle will also accept a file descriptor. 299Some requests (such as C<aio_readdir>) pass the actual results and
300communicate failures by passing C<undef>.
82 301
302All functions expecting a filehandle keep a copy of the filehandle
303internally until the request has finished.
304
305All functions return request objects of type L<IO::AIO::REQ> that allow
306further manipulation of those requests while they are in-flight.
307
83The filenames you pass to these routines I<must> be absolute. The reason 308The pathnames you pass to these routines I<should> be absolute. The
84is that at the time the request is being executed, the current working 309reason for this is that at the time the request is being executed, the
85directory could have changed. Alternatively, you can make sure that you 310current working directory could have changed. Alternatively, you can
86never change the current working directory. 311make sure that you never change the current working directory anywhere
312in the program and then use relative paths. You can also take advantage
313of IO::AIOs working directory abstraction, that lets you specify paths
314relative to some previously-opened "working directory object" - see the
315description of the C<IO::AIO::WD> class later in this document.
316
317To encode pathnames as octets, either make sure you either: a) always pass
318in filenames you got from outside (command line, readdir etc.) without
319tinkering, b) are in your native filesystem encoding, c) use the Encode
320module and encode your pathnames to the locale (or other) encoding in
321effect in the user environment, d) use Glib::filename_from_unicode on
322unicode filenames or e) use something else to ensure your scalar has the
323correct contents.
324
325This works, btw. independent of the internal UTF-8 bit, which IO::AIO
326handles correctly whether it is set or not.
327
328=head2 AIO REQUEST FUNCTIONS
87 329
88=over 4 330=over 4
89 331
332=item $prev_pri = aioreq_pri [$pri]
333
334Returns the priority value that would be used for the next request and, if
335C<$pri> is given, sets the priority for the next aio request.
336
337The default priority is C<0>, the minimum and maximum priorities are C<-4>
338and C<4>, respectively. Requests with higher priority will be serviced
339first.
340
341The priority will be reset to C<0> after each call to one of the C<aio_*>
342functions.
343
344Example: open a file with low priority, then read something from it with
345higher priority so the read request is serviced before other low priority
346open requests (potentially spamming the cache):
347
348 aioreq_pri -3;
349 aio_open ..., sub {
350 return unless $_[0];
351
352 aioreq_pri -2;
353 aio_read $_[0], ..., sub {
354 ...
355 };
356 };
357
358
359=item aioreq_nice $pri_adjust
360
361Similar to C<aioreq_pri>, but subtracts the given value from the current
362priority, so the effect is cumulative.
363
364
90=item aio_open $pathname, $flags, $mode, $callback 365=item aio_open $pathname, $flags, $mode, $callback->($fh)
91 366
92Asynchronously open or create a file and call the callback with a newly 367Asynchronously open or create a file and call the callback with a newly
93created filehandle for the file. 368created filehandle for the file (or C<undef> in case of an error).
94 369
95The pathname passed to C<aio_open> must be absolute. See API NOTES, above, 370The pathname passed to C<aio_open> must be absolute. See API NOTES, above,
96for an explanation. 371for an explanation.
97 372
98The C<$mode> argument is a bitmask. See the C<Fcntl> module for a 373The C<$flags> argument is a bitmask. See the C<Fcntl> module for a
99list. They are the same as used in C<sysopen>. 374list. They are the same as used by C<sysopen>.
375
376Likewise, C<$mode> specifies the mode of the newly created file, if it
377didn't exist and C<O_CREAT> has been given, just like perl's C<sysopen>,
378except that it is mandatory (i.e. use C<0> if you don't create new files,
379and C<0666> or C<0777> if you do). Note that the C<$mode> will be modified
380by the umask in effect then the request is being executed, so better never
381change the umask.
100 382
101Example: 383Example:
102 384
103 aio_open "/etc/passwd", O_RDONLY, 0, sub { 385 aio_open "/etc/passwd", IO::AIO::O_RDONLY, 0, sub {
104 if ($_[0]) { 386 if ($_[0]) {
105 print "open successful, fh is $_[0]\n"; 387 print "open successful, fh is $_[0]\n";
106 ... 388 ...
107 } else { 389 } else {
108 die "open failed: $!\n"; 390 die "open failed: $!\n";
109 } 391 }
110 }; 392 };
111 393
394In addition to all the common open modes/flags (C<O_RDONLY>, C<O_WRONLY>,
395C<O_RDWR>, C<O_CREAT>, C<O_TRUNC>, C<O_EXCL> and C<O_APPEND>), the
396following POSIX and non-POSIX constants are available (missing ones on
397your system are, as usual, C<0>):
398
399C<O_ASYNC>, C<O_DIRECT>, C<O_NOATIME>, C<O_CLOEXEC>, C<O_NOCTTY>, C<O_NOFOLLOW>,
400C<O_NONBLOCK>, C<O_EXEC>, C<O_SEARCH>, C<O_DIRECTORY>, C<O_DSYNC>,
401C<O_RSYNC>, C<O_SYNC>, C<O_PATH>, C<O_TMPFILE>, and C<O_TTY_INIT>.
402
403
112=item aio_close $fh, $callback 404=item aio_close $fh, $callback->($status)
113 405
114Asynchronously close a file and call the callback with the result 406Asynchronously close a file and call the callback with the result
115code. I<WARNING:> although accepted, you should not pass in a perl 407code.
116filehandle here, as perl will likely close the file descriptor itself when
117the filehandle is destroyed. Normally, you can safely call perls C<close>
118or just let filehandles go out of scope.
119 408
409Unfortunately, you can't do this to perl. Perl I<insists> very strongly on
410closing the file descriptor associated with the filehandle itself.
411
412Therefore, C<aio_close> will not close the filehandle - instead it will
413use dup2 to overwrite the file descriptor with the write-end of a pipe
414(the pipe fd will be created on demand and will be cached).
415
416Or in other words: the file descriptor will be closed, but it will not be
417free for reuse until the perl filehandle is closed.
418
419=cut
420
421=item aio_seek $fh, $offset, $whence, $callback->($offs)
422
423Seeks the filehandle to the new C<$offset>, similarly to perl's
424C<sysseek>. The C<$whence> can use the traditional values (C<0> for
425C<IO::AIO::SEEK_SET>, C<1> for C<IO::AIO::SEEK_CUR> or C<2> for
426C<IO::AIO::SEEK_END>).
427
428The resulting absolute offset will be passed to the callback, or C<-1> in
429case of an error.
430
431In theory, the C<$whence> constants could be different than the
432corresponding values from L<Fcntl>, but perl guarantees they are the same,
433so don't panic.
434
435As a GNU/Linux (and maybe Solaris) extension, also the constants
436C<IO::AIO::SEEK_DATA> and C<IO::AIO::SEEK_HOLE> are available, if they
437could be found. No guarantees about suitability for use in C<aio_seek> or
438Perl's C<sysseek> can be made though, although I would naively assume they
439"just work".
440
120=item aio_read $fh,$offset,$length, $data,$dataoffset,$callback 441=item aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval)
121 442
122=item aio_write $fh,$offset,$length, $data,$dataoffset,$callback 443=item aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval)
123 444
124Reads or writes C<length> bytes from the specified C<fh> and C<offset> 445Reads or writes C<$length> bytes from or to the specified C<$fh> and
125into the scalar given by C<data> and offset C<dataoffset> and calls the 446C<$offset> into the scalar given by C<$data> and offset C<$dataoffset>
126callback without the actual number of bytes read (or -1 on error, just 447and calls the callback without the actual number of bytes read (or -1 on
127like the syscall). 448error, just like the syscall).
128 449
450C<aio_read> will, like C<sysread>, shrink or grow the C<$data> scalar to
451offset plus the actual number of bytes read.
452
453If C<$offset> is undefined, then the current file descriptor offset will
454be used (and updated), otherwise the file descriptor offset will not be
455changed by these calls.
456
457If C<$length> is undefined in C<aio_write>, use the remaining length of
458C<$data>.
459
460If C<$dataoffset> is less than zero, it will be counted from the end of
461C<$data>.
462
463The C<$data> scalar I<MUST NOT> be modified in any way while the request
464is outstanding. Modifying it can result in segfaults or World War III (if
465the necessary/optional hardware is installed).
466
129Example: Read 15 bytes at offset 7 into scalar C<$buffer>, strating at 467Example: Read 15 bytes at offset 7 into scalar C<$buffer>, starting at
130offset C<0> within the scalar: 468offset C<0> within the scalar:
131 469
132 aio_read $fh, 7, 15, $buffer, 0, sub { 470 aio_read $fh, 7, 15, $buffer, 0, sub {
133 $_[0] >= 0 or die "read error: $!"; 471 $_[0] > 0 or die "read error: $!";
134 print "read <$buffer>\n"; 472 print "read $_[0] bytes: <$buffer>\n";
135 }; 473 };
136 474
475
476=item aio_sendfile $out_fh, $in_fh, $in_offset, $length, $callback->($retval)
477
478Tries to copy C<$length> bytes from C<$in_fh> to C<$out_fh>. It starts
479reading at byte offset C<$in_offset>, and starts writing at the current
480file offset of C<$out_fh>. Because of that, it is not safe to issue more
481than one C<aio_sendfile> per C<$out_fh>, as they will interfere with each
482other. The same C<$in_fh> works fine though, as this function does not
483move or use the file offset of C<$in_fh>.
484
485Please note that C<aio_sendfile> can read more bytes from C<$in_fh> than
486are written, and there is no way to find out how many more bytes have been
487read from C<aio_sendfile> alone, as C<aio_sendfile> only provides the
488number of bytes written to C<$out_fh>. Only if the result value equals
489C<$length> one can assume that C<$length> bytes have been read.
490
491Unlike with other C<aio_> functions, it makes a lot of sense to use
492C<aio_sendfile> on non-blocking sockets, as long as one end (typically
493the C<$in_fh>) is a file - the file I/O will then be asynchronous, while
494the socket I/O will be non-blocking. Note, however, that you can run
495into a trap where C<aio_sendfile> reads some data with readahead, then
496fails to write all data, and when the socket is ready the next time, the
497data in the cache is already lost, forcing C<aio_sendfile> to again hit
498the disk. Explicit C<aio_read> + C<aio_write> let's you better control
499resource usage.
500
501This call tries to make use of a native C<sendfile>-like syscall to
502provide zero-copy operation. For this to work, C<$out_fh> should refer to
503a socket, and C<$in_fh> should refer to an mmap'able file.
504
505If a native sendfile cannot be found or it fails with C<ENOSYS>,
506C<EINVAL>, C<ENOTSUP>, C<EOPNOTSUPP>, C<EAFNOSUPPORT>, C<EPROTOTYPE> or
507C<ENOTSOCK>, it will be emulated, so you can call C<aio_sendfile> on any
508type of filehandle regardless of the limitations of the operating system.
509
510As native sendfile syscalls (as practically any non-POSIX interface hacked
511together in a hurry to improve benchmark numbers) tend to be rather buggy
512on many systems, this implementation tries to work around some known bugs
513in Linux and FreeBSD kernels (probably others, too), but that might fail,
514so you really really should check the return value of C<aio_sendfile> -
515fewer bytes than expected might have been transferred.
516
517
137=item aio_readahead $fh,$offset,$length, $callback 518=item aio_readahead $fh,$offset,$length, $callback->($retval)
138 519
139Asynchronously reads the specified byte range into the page cache, using
140the C<readahead> syscall. If that syscall doesn't exist the status will be
141C<-1> and C<$!> is set to ENOSYS.
142
143readahead() populates the page cache with data from a file so that 520C<aio_readahead> populates the page cache with data from a file so that
144subsequent reads from that file will not block on disk I/O. The C<$offset> 521subsequent reads from that file will not block on disk I/O. The C<$offset>
145argument specifies the starting point from which data is to be read and 522argument specifies the starting point from which data is to be read and
146C<$length> specifies the number of bytes to be read. I/O is performed in 523C<$length> specifies the number of bytes to be read. I/O is performed in
147whole pages, so that offset is effectively rounded down to a page boundary 524whole pages, so that offset is effectively rounded down to a page boundary
148and bytes are read up to the next page boundary greater than or equal to 525and bytes are read up to the next page boundary greater than or equal to
149(off-set+length). aio_readahead() does not read beyond the end of the 526(off-set+length). C<aio_readahead> does not read beyond the end of the
150file. The current file offset of the file is left unchanged. 527file. The current file offset of the file is left unchanged.
151 528
529If that syscall doesn't exist (likely if your kernel isn't Linux) it will
530be emulated by simply reading the data, which would have a similar effect.
531
532
152=item aio_stat $fh_or_path, $callback 533=item aio_stat $fh_or_path, $callback->($status)
153 534
154=item aio_lstat $fh, $callback 535=item aio_lstat $fh, $callback->($status)
155 536
156Works like perl's C<stat> or C<lstat> in void context. The callback will 537Works like perl's C<stat> or C<lstat> in void context. The callback will
157be called after the stat and the results will be available using C<stat _> 538be called after the stat and the results will be available using C<stat _>
158or C<-s _> etc... 539or C<-s _> etc...
159 540
161for an explanation. 542for an explanation.
162 543
163Currently, the stats are always 64-bit-stats, i.e. instead of returning an 544Currently, the stats are always 64-bit-stats, i.e. instead of returning an
164error when stat'ing a large file, the results will be silently truncated 545error when stat'ing a large file, the results will be silently truncated
165unless perl itself is compiled with large file support. 546unless perl itself is compiled with large file support.
547
548To help interpret the mode and dev/rdev stat values, IO::AIO offers the
549following constants and functions (if not implemented, the constants will
550be C<0> and the functions will either C<croak> or fall back on traditional
551behaviour).
552
553C<S_IFMT>, C<S_IFIFO>, C<S_IFCHR>, C<S_IFBLK>, C<S_IFLNK>, C<S_IFREG>,
554C<S_IFDIR>, C<S_IFWHT>, C<S_IFSOCK>, C<IO::AIO::major $dev_t>,
555C<IO::AIO::minor $dev_t>, C<IO::AIO::makedev $major, $minor>.
166 556
167Example: Print the length of F</etc/passwd>: 557Example: Print the length of F</etc/passwd>:
168 558
169 aio_stat "/etc/passwd", sub { 559 aio_stat "/etc/passwd", sub {
170 $_[0] and die "stat failed: $!"; 560 $_[0] and die "stat failed: $!";
171 print "size is ", -s _, "\n"; 561 print "size is ", -s _, "\n";
172 }; 562 };
173 563
564
565=item aio_statvfs $fh_or_path, $callback->($statvfs)
566
567Works like the POSIX C<statvfs> or C<fstatvfs> syscalls, depending on
568whether a file handle or path was passed.
569
570On success, the callback is passed a hash reference with the following
571members: C<bsize>, C<frsize>, C<blocks>, C<bfree>, C<bavail>, C<files>,
572C<ffree>, C<favail>, C<fsid>, C<flag> and C<namemax>. On failure, C<undef>
573is passed.
574
575The following POSIX IO::AIO::ST_* constants are defined: C<ST_RDONLY> and
576C<ST_NOSUID>.
577
578The following non-POSIX IO::AIO::ST_* flag masks are defined to
579their correct value when available, or to C<0> on systems that do
580not support them: C<ST_NODEV>, C<ST_NOEXEC>, C<ST_SYNCHRONOUS>,
581C<ST_MANDLOCK>, C<ST_WRITE>, C<ST_APPEND>, C<ST_IMMUTABLE>, C<ST_NOATIME>,
582C<ST_NODIRATIME> and C<ST_RELATIME>.
583
584Example: stat C</wd> and dump out the data if successful.
585
586 aio_statvfs "/wd", sub {
587 my $f = $_[0]
588 or die "statvfs: $!";
589
590 use Data::Dumper;
591 say Dumper $f;
592 };
593
594 # result:
595 {
596 bsize => 1024,
597 bfree => 4333064312,
598 blocks => 10253828096,
599 files => 2050765568,
600 flag => 4096,
601 favail => 2042092649,
602 bavail => 4333064312,
603 ffree => 2042092649,
604 namemax => 255,
605 frsize => 1024,
606 fsid => 1810
607 }
608
609Here is a (likely partial - send me updates!) list of fsid values used by
610Linux - it is safe to hardcode these when C<$^O> is C<linux>:
611
612 0x0000adf5 adfs
613 0x0000adff affs
614 0x5346414f afs
615 0x09041934 anon-inode filesystem
616 0x00000187 autofs
617 0x42465331 befs
618 0x1badface bfs
619 0x42494e4d binfmt_misc
620 0x9123683e btrfs
621 0x0027e0eb cgroupfs
622 0xff534d42 cifs
623 0x73757245 coda
624 0x012ff7b7 coh
625 0x28cd3d45 cramfs
626 0x453dcd28 cramfs-wend (wrong endianness)
627 0x64626720 debugfs
628 0x00001373 devfs
629 0x00001cd1 devpts
630 0x0000f15f ecryptfs
631 0x00414a53 efs
632 0x0000137d ext
633 0x0000ef53 ext2/ext3/ext4
634 0x0000ef51 ext2
635 0xf2f52010 f2fs
636 0x00004006 fat
637 0x65735546 fuseblk
638 0x65735543 fusectl
639 0x0bad1dea futexfs
640 0x01161970 gfs2
641 0x47504653 gpfs
642 0x00004244 hfs
643 0xf995e849 hpfs
644 0x00c0ffee hostfs
645 0x958458f6 hugetlbfs
646 0x2bad1dea inotifyfs
647 0x00009660 isofs
648 0x000072b6 jffs2
649 0x3153464a jfs
650 0x6b414653 k-afs
651 0x0bd00bd0 lustre
652 0x0000137f minix
653 0x0000138f minix 30 char names
654 0x00002468 minix v2
655 0x00002478 minix v2 30 char names
656 0x00004d5a minix v3
657 0x19800202 mqueue
658 0x00004d44 msdos
659 0x0000564c novell
660 0x00006969 nfs
661 0x6e667364 nfsd
662 0x00003434 nilfs
663 0x5346544e ntfs
664 0x00009fa1 openprom
665 0x7461636F ocfs2
666 0x00009fa0 proc
667 0x6165676c pstorefs
668 0x0000002f qnx4
669 0x68191122 qnx6
670 0x858458f6 ramfs
671 0x52654973 reiserfs
672 0x00007275 romfs
673 0x67596969 rpc_pipefs
674 0x73636673 securityfs
675 0xf97cff8c selinux
676 0x0000517b smb
677 0x534f434b sockfs
678 0x73717368 squashfs
679 0x62656572 sysfs
680 0x012ff7b6 sysv2
681 0x012ff7b5 sysv4
682 0x01021994 tmpfs
683 0x15013346 udf
684 0x00011954 ufs
685 0x54190100 ufs byteswapped
686 0x00009fa2 usbdevfs
687 0x01021997 v9fs
688 0xa501fcf5 vxfs
689 0xabba1974 xenfs
690 0x012ff7b4 xenix
691 0x58465342 xfs
692 0x012fd16d xia
693
694=item aio_utime $fh_or_path, $atime, $mtime, $callback->($status)
695
696Works like perl's C<utime> function (including the special case of $atime
697and $mtime being undef). Fractional times are supported if the underlying
698syscalls support them.
699
700When called with a pathname, uses utimes(2) if available, otherwise
701utime(2). If called on a file descriptor, uses futimes(2) if available,
702otherwise returns ENOSYS, so this is not portable.
703
704Examples:
705
706 # set atime and mtime to current time (basically touch(1)):
707 aio_utime "path", undef, undef;
708 # set atime to current time and mtime to beginning of the epoch:
709 aio_utime "path", time, undef; # undef==0
710
711
712=item aio_chown $fh_or_path, $uid, $gid, $callback->($status)
713
714Works like perl's C<chown> function, except that C<undef> for either $uid
715or $gid is being interpreted as "do not change" (but -1 can also be used).
716
717Examples:
718
719 # same as "chown root path" in the shell:
720 aio_chown "path", 0, -1;
721 # same as above:
722 aio_chown "path", 0, undef;
723
724
725=item aio_truncate $fh_or_path, $offset, $callback->($status)
726
727Works like truncate(2) or ftruncate(2).
728
729
730=item aio_allocate $fh, $mode, $offset, $len, $callback->($status)
731
732Allocates or frees disk space according to the C<$mode> argument. See the
733linux C<fallocate> documentation for details.
734
735C<$mode> is usually C<0> or C<IO::AIO::FALLOC_FL_KEEP_SIZE> to allocate
736space, or C<IO::AIO::FALLOC_FL_PUNCH_HOLE | IO::AIO::FALLOC_FL_KEEP_SIZE>,
737to deallocate a file range.
738
739IO::AIO also supports C<FALLOC_FL_COLLAPSE_RANGE>, to remove a range
740(without leaving a hole) and C<FALLOC_FL_ZERO_RANGE>, to zero a range (see
741your L<fallocate(2)> manpage).
742
743The file system block size used by C<fallocate> is presumably the
744C<f_bsize> returned by C<statvfs>.
745
746If C<fallocate> isn't available or cannot be emulated (currently no
747emulation will be attempted), passes C<-1> and sets C<$!> to C<ENOSYS>.
748
749
750=item aio_chmod $fh_or_path, $mode, $callback->($status)
751
752Works like perl's C<chmod> function.
753
754
174=item aio_unlink $pathname, $callback 755=item aio_unlink $pathname, $callback->($status)
175 756
176Asynchronously unlink (delete) a file and call the callback with the 757Asynchronously unlink (delete) a file and call the callback with the
177result code. 758result code.
178 759
760
761=item aio_mknod $pathname, $mode, $dev, $callback->($status)
762
763[EXPERIMENTAL]
764
765Asynchronously create a device node (or fifo). See mknod(2).
766
767The only (POSIX-) portable way of calling this function is:
768
769 aio_mknod $pathname, IO::AIO::S_IFIFO | $mode, 0, sub { ...
770
771See C<aio_stat> for info about some potentially helpful extra constants
772and functions.
773
774=item aio_link $srcpath, $dstpath, $callback->($status)
775
776Asynchronously create a new link to the existing object at C<$srcpath> at
777the path C<$dstpath> and call the callback with the result code.
778
779
780=item aio_symlink $srcpath, $dstpath, $callback->($status)
781
782Asynchronously create a new symbolic link to the existing object at C<$srcpath> at
783the path C<$dstpath> and call the callback with the result code.
784
785
786=item aio_readlink $pathname, $callback->($link)
787
788Asynchronously read the symlink specified by C<$path> and pass it to
789the callback. If an error occurs, nothing or undef gets passed to the
790callback.
791
792
793=item aio_realpath $pathname, $callback->($path)
794
795Asynchronously make the path absolute and resolve any symlinks in
796C<$path>. The resulting path only consists of directories (same as
797L<Cwd::realpath>).
798
799This request can be used to get the absolute path of the current working
800directory by passing it a path of F<.> (a single dot).
801
802
803=item aio_rename $srcpath, $dstpath, $callback->($status)
804
805Asynchronously rename the object at C<$srcpath> to C<$dstpath>, just as
806rename(2) and call the callback with the result code.
807
808On systems that support the AIO::WD working directory abstraction
809natively, the case C<[$wd, "."]> as C<$srcpath> is specialcased - instead
810of failing, C<rename> is called on the absolute path of C<$wd>.
811
812
813=item aio_mkdir $pathname, $mode, $callback->($status)
814
815Asynchronously mkdir (create) a directory and call the callback with
816the result code. C<$mode> will be modified by the umask at the time the
817request is executed, so do not change your umask.
818
819
820=item aio_rmdir $pathname, $callback->($status)
821
822Asynchronously rmdir (delete) a directory and call the callback with the
823result code.
824
825On systems that support the AIO::WD working directory abstraction
826natively, the case C<[$wd, "."]> is specialcased - instead of failing,
827C<rmdir> is called on the absolute path of C<$wd>.
828
829
830=item aio_readdir $pathname, $callback->($entries)
831
832Unlike the POSIX call of the same name, C<aio_readdir> reads an entire
833directory (i.e. opendir + readdir + closedir). The entries will not be
834sorted, and will B<NOT> include the C<.> and C<..> entries.
835
836The callback is passed a single argument which is either C<undef> or an
837array-ref with the filenames.
838
839
840=item aio_readdirx $pathname, $flags, $callback->($entries, $flags)
841
842Quite similar to C<aio_readdir>, but the C<$flags> argument allows one to
843tune behaviour and output format. In case of an error, C<$entries> will be
844C<undef>.
845
846The flags are a combination of the following constants, ORed together (the
847flags will also be passed to the callback, possibly modified):
848
849=over 4
850
851=item IO::AIO::READDIR_DENTS
852
853When this flag is off, then the callback gets an arrayref consisting of
854names only (as with C<aio_readdir>), otherwise it gets an arrayref with
855C<[$name, $type, $inode]> arrayrefs, each describing a single directory
856entry in more detail.
857
858C<$name> is the name of the entry.
859
860C<$type> is one of the C<IO::AIO::DT_xxx> constants:
861
862C<IO::AIO::DT_UNKNOWN>, C<IO::AIO::DT_FIFO>, C<IO::AIO::DT_CHR>, C<IO::AIO::DT_DIR>,
863C<IO::AIO::DT_BLK>, C<IO::AIO::DT_REG>, C<IO::AIO::DT_LNK>, C<IO::AIO::DT_SOCK>,
864C<IO::AIO::DT_WHT>.
865
866C<IO::AIO::DT_UNKNOWN> means just that: readdir does not know. If you need to
867know, you have to run stat yourself. Also, for speed reasons, the C<$type>
868scalars are read-only: you can not modify them.
869
870C<$inode> is the inode number (which might not be exact on systems with 64
871bit inode numbers and 32 bit perls). This field has unspecified content on
872systems that do not deliver the inode information.
873
874=item IO::AIO::READDIR_DIRS_FIRST
875
876When this flag is set, then the names will be returned in an order where
877likely directories come first, in optimal stat order. This is useful when
878you need to quickly find directories, or you want to find all directories
879while avoiding to stat() each entry.
880
881If the system returns type information in readdir, then this is used
882to find directories directly. Otherwise, likely directories are names
883beginning with ".", or otherwise names with no dots, of which names with
884short names are tried first.
885
886=item IO::AIO::READDIR_STAT_ORDER
887
888When this flag is set, then the names will be returned in an order
889suitable for stat()'ing each one. That is, when you plan to stat()
890all files in the given directory, then the returned order will likely
891be fastest.
892
893If both this flag and C<IO::AIO::READDIR_DIRS_FIRST> are specified, then
894the likely dirs come first, resulting in a less optimal stat order.
895
896=item IO::AIO::READDIR_FOUND_UNKNOWN
897
898This flag should not be set when calling C<aio_readdirx>. Instead, it
899is being set by C<aio_readdirx>, when any of the C<$type>'s found were
900C<IO::AIO::DT_UNKNOWN>. The absence of this flag therefore indicates that all
901C<$type>'s are known, which can be used to speed up some algorithms.
902
903=back
904
905
906=item aio_load $pathname, $data, $callback->($status)
907
908This is a composite request that tries to fully load the given file into
909memory. Status is the same as with aio_read.
910
911=cut
912
913sub aio_load($$;$) {
914 my ($path, undef, $cb) = @_;
915 my $data = \$_[1];
916
917 my $pri = aioreq_pri;
918 my $grp = aio_group $cb;
919
920 aioreq_pri $pri;
921 add $grp aio_open $path, O_RDONLY, 0, sub {
922 my $fh = shift
923 or return $grp->result (-1);
924
925 aioreq_pri $pri;
926 add $grp aio_read $fh, 0, (-s $fh), $$data, 0, sub {
927 $grp->result ($_[0]);
928 };
929 };
930
931 $grp
932}
933
934=item aio_copy $srcpath, $dstpath, $callback->($status)
935
936Try to copy the I<file> (directories not supported as either source or
937destination) from C<$srcpath> to C<$dstpath> and call the callback with
938a status of C<0> (ok) or C<-1> (error, see C<$!>).
939
940This is a composite request that creates the destination file with
941mode 0200 and copies the contents of the source file into it using
942C<aio_sendfile>, followed by restoring atime, mtime, access mode and
943uid/gid, in that order.
944
945If an error occurs, the partial destination file will be unlinked, if
946possible, except when setting atime, mtime, access mode and uid/gid, where
947errors are being ignored.
948
949=cut
950
951sub aio_copy($$;$) {
952 my ($src, $dst, $cb) = @_;
953
954 my $pri = aioreq_pri;
955 my $grp = aio_group $cb;
956
957 aioreq_pri $pri;
958 add $grp aio_open $src, O_RDONLY, 0, sub {
959 if (my $src_fh = $_[0]) {
960 my @stat = stat $src_fh; # hmm, might block over nfs?
961
962 aioreq_pri $pri;
963 add $grp aio_open $dst, O_CREAT | O_WRONLY | O_TRUNC, 0200, sub {
964 if (my $dst_fh = $_[0]) {
965 aioreq_pri $pri;
966 add $grp aio_sendfile $dst_fh, $src_fh, 0, $stat[7], sub {
967 if ($_[0] == $stat[7]) {
968 $grp->result (0);
969 close $src_fh;
970
971 my $ch = sub {
972 aioreq_pri $pri;
973 add $grp aio_chmod $dst_fh, $stat[2] & 07777, sub {
974 aioreq_pri $pri;
975 add $grp aio_chown $dst_fh, $stat[4], $stat[5], sub {
976 aioreq_pri $pri;
977 add $grp aio_close $dst_fh;
978 }
979 };
980 };
981
982 aioreq_pri $pri;
983 add $grp aio_utime $dst_fh, $stat[8], $stat[9], sub {
984 if ($_[0] < 0 && $! == ENOSYS) {
985 aioreq_pri $pri;
986 add $grp aio_utime $dst, $stat[8], $stat[9], $ch;
987 } else {
988 $ch->();
989 }
990 };
991 } else {
992 $grp->result (-1);
993 close $src_fh;
994 close $dst_fh;
995
996 aioreq $pri;
997 add $grp aio_unlink $dst;
998 }
999 };
1000 } else {
1001 $grp->result (-1);
1002 }
1003 },
1004
1005 } else {
1006 $grp->result (-1);
1007 }
1008 };
1009
1010 $grp
1011}
1012
1013=item aio_move $srcpath, $dstpath, $callback->($status)
1014
1015Try to move the I<file> (directories not supported as either source or
1016destination) from C<$srcpath> to C<$dstpath> and call the callback with
1017a status of C<0> (ok) or C<-1> (error, see C<$!>).
1018
1019This is a composite request that tries to rename(2) the file first; if
1020rename fails with C<EXDEV>, it copies the file with C<aio_copy> and, if
1021that is successful, unlinks the C<$srcpath>.
1022
1023=cut
1024
1025sub aio_move($$;$) {
1026 my ($src, $dst, $cb) = @_;
1027
1028 my $pri = aioreq_pri;
1029 my $grp = aio_group $cb;
1030
1031 aioreq_pri $pri;
1032 add $grp aio_rename $src, $dst, sub {
1033 if ($_[0] && $! == EXDEV) {
1034 aioreq_pri $pri;
1035 add $grp aio_copy $src, $dst, sub {
1036 $grp->result ($_[0]);
1037
1038 unless ($_[0]) {
1039 aioreq_pri $pri;
1040 add $grp aio_unlink $src;
1041 }
1042 };
1043 } else {
1044 $grp->result ($_[0]);
1045 }
1046 };
1047
1048 $grp
1049}
1050
1051=item aio_scandir $pathname, $maxreq, $callback->($dirs, $nondirs)
1052
1053Scans a directory (similar to C<aio_readdir>) but additionally tries to
1054efficiently separate the entries of directory C<$path> into two sets of
1055names, directories you can recurse into (directories), and ones you cannot
1056recurse into (everything else, including symlinks to directories).
1057
1058C<aio_scandir> is a composite request that creates of many sub requests_
1059C<$maxreq> specifies the maximum number of outstanding aio requests that
1060this function generates. If it is C<< <= 0 >>, then a suitable default
1061will be chosen (currently 4).
1062
1063On error, the callback is called without arguments, otherwise it receives
1064two array-refs with path-relative entry names.
1065
1066Example:
1067
1068 aio_scandir $dir, 0, sub {
1069 my ($dirs, $nondirs) = @_;
1070 print "real directories: @$dirs\n";
1071 print "everything else: @$nondirs\n";
1072 };
1073
1074Implementation notes.
1075
1076The C<aio_readdir> cannot be avoided, but C<stat()>'ing every entry can.
1077
1078If readdir returns file type information, then this is used directly to
1079find directories.
1080
1081Otherwise, after reading the directory, the modification time, size etc.
1082of the directory before and after the readdir is checked, and if they
1083match (and isn't the current time), the link count will be used to decide
1084how many entries are directories (if >= 2). Otherwise, no knowledge of the
1085number of subdirectories will be assumed.
1086
1087Then entries will be sorted into likely directories a non-initial dot
1088currently) and likely non-directories (see C<aio_readdirx>). Then every
1089entry plus an appended C</.> will be C<stat>'ed, likely directories first,
1090in order of their inode numbers. If that succeeds, it assumes that the
1091entry is a directory or a symlink to directory (which will be checked
1092separately). This is often faster than stat'ing the entry itself because
1093filesystems might detect the type of the entry without reading the inode
1094data (e.g. ext2fs filetype feature), even on systems that cannot return
1095the filetype information on readdir.
1096
1097If the known number of directories (link count - 2) has been reached, the
1098rest of the entries is assumed to be non-directories.
1099
1100This only works with certainty on POSIX (= UNIX) filesystems, which
1101fortunately are the vast majority of filesystems around.
1102
1103It will also likely work on non-POSIX filesystems with reduced efficiency
1104as those tend to return 0 or 1 as link counts, which disables the
1105directory counting heuristic.
1106
1107=cut
1108
1109sub aio_scandir($$;$) {
1110 my ($path, $maxreq, $cb) = @_;
1111
1112 my $pri = aioreq_pri;
1113
1114 my $grp = aio_group $cb;
1115
1116 $maxreq = 4 if $maxreq <= 0;
1117
1118 # get a wd object
1119 aioreq_pri $pri;
1120 add $grp aio_wd $path, sub {
1121 $_[0]
1122 or return $grp->result ();
1123
1124 my $wd = [shift, "."];
1125
1126 # stat once
1127 aioreq_pri $pri;
1128 add $grp aio_stat $wd, sub {
1129 return $grp->result () if $_[0];
1130 my $now = time;
1131 my $hash1 = join ":", (stat _)[0,1,3,7,9];
1132
1133 # read the directory entries
1134 aioreq_pri $pri;
1135 add $grp aio_readdirx $wd, READDIR_DIRS_FIRST, sub {
1136 my $entries = shift
1137 or return $grp->result ();
1138
1139 # stat the dir another time
1140 aioreq_pri $pri;
1141 add $grp aio_stat $wd, sub {
1142 my $hash2 = join ":", (stat _)[0,1,3,7,9];
1143
1144 my $ndirs;
1145
1146 # take the slow route if anything looks fishy
1147 if ($hash1 ne $hash2 or (stat _)[9] == $now) {
1148 $ndirs = -1;
1149 } else {
1150 # if nlink == 2, we are finished
1151 # for non-posix-fs's, we rely on nlink < 2
1152 $ndirs = (stat _)[3] - 2
1153 or return $grp->result ([], $entries);
1154 }
1155
1156 my (@dirs, @nondirs);
1157
1158 my $statgrp = add $grp aio_group sub {
1159 $grp->result (\@dirs, \@nondirs);
1160 };
1161
1162 limit $statgrp $maxreq;
1163 feed $statgrp sub {
1164 return unless @$entries;
1165 my $entry = shift @$entries;
1166
1167 aioreq_pri $pri;
1168 $wd->[1] = "$entry/.";
1169 add $statgrp aio_stat $wd, sub {
1170 if ($_[0] < 0) {
1171 push @nondirs, $entry;
1172 } else {
1173 # need to check for real directory
1174 aioreq_pri $pri;
1175 $wd->[1] = $entry;
1176 add $statgrp aio_lstat $wd, sub {
1177 if (-d _) {
1178 push @dirs, $entry;
1179
1180 unless (--$ndirs) {
1181 push @nondirs, @$entries;
1182 feed $statgrp;
1183 }
1184 } else {
1185 push @nondirs, $entry;
1186 }
1187 }
1188 }
1189 };
1190 };
1191 };
1192 };
1193 };
1194 };
1195
1196 $grp
1197}
1198
1199=item aio_rmtree $pathname, $callback->($status)
1200
1201Delete a directory tree starting (and including) C<$path>, return the
1202status of the final C<rmdir> only. This is a composite request that
1203uses C<aio_scandir> to recurse into and rmdir directories, and unlink
1204everything else.
1205
1206=cut
1207
1208sub aio_rmtree;
1209sub aio_rmtree($;$) {
1210 my ($path, $cb) = @_;
1211
1212 my $pri = aioreq_pri;
1213 my $grp = aio_group $cb;
1214
1215 aioreq_pri $pri;
1216 add $grp aio_scandir $path, 0, sub {
1217 my ($dirs, $nondirs) = @_;
1218
1219 my $dirgrp = aio_group sub {
1220 add $grp aio_rmdir $path, sub {
1221 $grp->result ($_[0]);
1222 };
1223 };
1224
1225 (aioreq_pri $pri), add $dirgrp aio_rmtree "$path/$_" for @$dirs;
1226 (aioreq_pri $pri), add $dirgrp aio_unlink "$path/$_" for @$nondirs;
1227
1228 add $grp $dirgrp;
1229 };
1230
1231 $grp
1232}
1233
1234=item aio_fcntl $fh, $cmd, $arg, $callback->($status)
1235
1236=item aio_ioctl $fh, $request, $buf, $callback->($status)
1237
1238These work just like the C<fcntl> and C<ioctl> built-in functions, except
1239they execute asynchronously and pass the return value to the callback.
1240
1241Both calls can be used for a lot of things, some of which make more sense
1242to run asynchronously in their own thread, while some others make less
1243sense. For example, calls that block waiting for external events, such
1244as locking, will also lock down an I/O thread while it is waiting, which
1245can deadlock the whole I/O system. At the same time, there might be no
1246alternative to using a thread to wait.
1247
1248So in general, you should only use these calls for things that do
1249(filesystem) I/O, not for things that wait for other events (network,
1250other processes), although if you are careful and know what you are doing,
1251you still can.
1252
1253The following constants are available (missing ones are, as usual C<0>):
1254
1255C<FIFREEZE>, C<FITHAW>, C<FITRIM>, C<FICLONE>, C<FICLONERANGE>, C<FIDEDUPERANGE>.
1256
1257C<FS_IOC_GETFLAGS>, C<FS_IOC_SETFLAGS>, C<FS_IOC_GETVERSION>, C<FS_IOC_SETVERSION>,
1258C<FS_IOC_FIEMAP>.
1259
1260C<FS_IOC_FSGETXATTR>, C<FS_IOC_FSSETXATTR>, C<FS_IOC_SET_ENCRYPTION_POLICY>,
1261C<FS_IOC_GET_ENCRYPTION_PWSALT>, C<FS_IOC_GET_ENCRYPTION_POLICY>, C<FS_KEY_DESCRIPTOR_SIZE>.
1262
1263C<FS_SECRM_FL>, C<FS_UNRM_FL>, C<FS_COMPR_FL>, C<FS_SYNC_FL>, C<FS_IMMUTABLE_FL>,
1264C<FS_APPEND_FL>, C<FS_NODUMP_FL>, C<FS_NOATIME_FL>, C<FS_DIRTY_FL>,
1265C<FS_COMPRBLK_FL>, C<FS_NOCOMP_FL>, C<FS_ENCRYPT_FL>, C<FS_BTREE_FL>,
1266C<FS_INDEX_FL>, C<FS_JOURNAL_DATA_FL>, C<FS_NOTAIL_FL>, C<FS_DIRSYNC_FL>, C<FS_TOPDIR_FL>,
1267C<FS_FL_USER_MODIFIABLE>.
1268
1269C<FS_XFLAG_REALTIME>, C<FS_XFLAG_PREALLOC>, C<FS_XFLAG_IMMUTABLE>, C<FS_XFLAG_APPEND>,
1270C<FS_XFLAG_SYNC>, C<FS_XFLAG_NOATIME>, C<FS_XFLAG_NODUMP>, C<FS_XFLAG_RTINHERIT>,
1271C<FS_XFLAG_PROJINHERIT>, C<FS_XFLAG_NOSYMLINKS>, C<FS_XFLAG_EXTSIZE>, C<FS_XFLAG_EXTSZINHERIT>,
1272C<FS_XFLAG_NODEFRAG>, C<FS_XFLAG_FILESTREAM>, C<FS_XFLAG_DAX>, C<FS_XFLAG_HASATTR>,
1273
1274=item aio_sync $callback->($status)
1275
1276Asynchronously call sync and call the callback when finished.
1277
179=item aio_fsync $fh, $callback 1278=item aio_fsync $fh, $callback->($status)
180 1279
181Asynchronously call fsync on the given filehandle and call the callback 1280Asynchronously call fsync on the given filehandle and call the callback
182with the fsync result code. 1281with the fsync result code.
183 1282
184=item aio_fdatasync $fh, $callback 1283=item aio_fdatasync $fh, $callback->($status)
185 1284
186Asynchronously call fdatasync on the given filehandle and call the 1285Asynchronously call fdatasync on the given filehandle and call the
187callback with the fdatasync result code. 1286callback with the fdatasync result code.
188 1287
1288If this call isn't available because your OS lacks it or it couldn't be
1289detected, it will be emulated by calling C<fsync> instead.
1290
1291=item aio_syncfs $fh, $callback->($status)
1292
1293Asynchronously call the syncfs syscall to sync the filesystem associated
1294to the given filehandle and call the callback with the syncfs result
1295code. If syncfs is not available, calls sync(), but returns C<-1> and sets
1296errno to C<ENOSYS> nevertheless.
1297
1298=item aio_sync_file_range $fh, $offset, $nbytes, $flags, $callback->($status)
1299
1300Sync the data portion of the file specified by C<$offset> and C<$length>
1301to disk (but NOT the metadata), by calling the Linux-specific
1302sync_file_range call. If sync_file_range is not available or it returns
1303ENOSYS, then fdatasync or fsync is being substituted.
1304
1305C<$flags> can be a combination of C<IO::AIO::SYNC_FILE_RANGE_WAIT_BEFORE>,
1306C<IO::AIO::SYNC_FILE_RANGE_WRITE> and
1307C<IO::AIO::SYNC_FILE_RANGE_WAIT_AFTER>: refer to the sync_file_range
1308manpage for details.
1309
1310=item aio_pathsync $pathname, $callback->($status)
1311
1312This request tries to open, fsync and close the given path. This is a
1313composite request intended to sync directories after directory operations
1314(E.g. rename). This might not work on all operating systems or have any
1315specific effect, but usually it makes sure that directory changes get
1316written to disc. It works for anything that can be opened for read-only,
1317not just directories.
1318
1319Future versions of this function might fall back to other methods when
1320C<fsync> on the directory fails (such as calling C<sync>).
1321
1322Passes C<0> when everything went ok, and C<-1> on error.
1323
1324=cut
1325
1326sub aio_pathsync($;$) {
1327 my ($path, $cb) = @_;
1328
1329 my $pri = aioreq_pri;
1330 my $grp = aio_group $cb;
1331
1332 aioreq_pri $pri;
1333 add $grp aio_open $path, O_RDONLY, 0, sub {
1334 my ($fh) = @_;
1335 if ($fh) {
1336 aioreq_pri $pri;
1337 add $grp aio_fsync $fh, sub {
1338 $grp->result ($_[0]);
1339
1340 aioreq_pri $pri;
1341 add $grp aio_close $fh;
1342 };
1343 } else {
1344 $grp->result (-1);
1345 }
1346 };
1347
1348 $grp
1349}
1350
1351=item aio_msync $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status)
1352
1353This is a rather advanced IO::AIO call, which only works on mmap(2)ed
1354scalars (see the C<IO::AIO::mmap> function, although it also works on data
1355scalars managed by the L<Sys::Mmap> or L<Mmap> modules, note that the
1356scalar must only be modified in-place while an aio operation is pending on
1357it).
1358
1359It calls the C<msync> function of your OS, if available, with the memory
1360area starting at C<$offset> in the string and ending C<$length> bytes
1361later. If C<$length> is negative, counts from the end, and if C<$length>
1362is C<undef>, then it goes till the end of the string. The flags can be
1363a combination of C<IO::AIO::MS_ASYNC>, C<IO::AIO::MS_INVALIDATE> and
1364C<IO::AIO::MS_SYNC>.
1365
1366=item aio_mtouch $scalar, $offset = 0, $length = undef, flags = 0, $callback->($status)
1367
1368This is a rather advanced IO::AIO call, which works best on mmap(2)ed
1369scalars.
1370
1371It touches (reads or writes) all memory pages in the specified
1372range inside the scalar. All caveats and parameters are the same
1373as for C<aio_msync>, above, except for flags, which must be either
1374C<0> (which reads all pages and ensures they are instantiated) or
1375C<IO::AIO::MT_MODIFY>, which modifies the memory pages (by reading and
1376writing an octet from it, which dirties the page).
1377
1378=item aio_mlock $scalar, $offset = 0, $length = undef, $callback->($status)
1379
1380This is a rather advanced IO::AIO call, which works best on mmap(2)ed
1381scalars.
1382
1383It reads in all the pages of the underlying storage into memory (if any)
1384and locks them, so they are not getting swapped/paged out or removed.
1385
1386If C<$length> is undefined, then the scalar will be locked till the end.
1387
1388On systems that do not implement C<mlock>, this function returns C<-1>
1389and sets errno to C<ENOSYS>.
1390
1391Note that the corresponding C<munlock> is synchronous and is
1392documented under L<MISCELLANEOUS FUNCTIONS>.
1393
1394Example: open a file, mmap and mlock it - both will be undone when
1395C<$data> gets destroyed.
1396
1397 open my $fh, "<", $path or die "$path: $!";
1398 my $data;
1399 IO::AIO::mmap $data, -s $fh, IO::AIO::PROT_READ, IO::AIO::MAP_SHARED, $fh;
1400 aio_mlock $data; # mlock in background
1401
1402=item aio_mlockall $flags, $callback->($status)
1403
1404Calls the C<mlockall> function with the given C<$flags> (a combination of
1405C<IO::AIO::MCL_CURRENT> and C<IO::AIO::MCL_FUTURE>).
1406
1407On systems that do not implement C<mlockall>, this function returns C<-1>
1408and sets errno to C<ENOSYS>.
1409
1410Note that the corresponding C<munlockall> is synchronous and is
1411documented under L<MISCELLANEOUS FUNCTIONS>.
1412
1413Example: asynchronously lock all current and future pages into memory.
1414
1415 aio_mlockall IO::AIO::MCL_FUTURE;
1416
1417=item aio_fiemap $fh, $start, $length, $flags, $count, $cb->(\@extents)
1418
1419Queries the extents of the given file (by calling the Linux C<FIEMAP>
1420ioctl, see L<http://cvs.schmorp.de/IO-AIO/doc/fiemap.txt> for details). If
1421the ioctl is not available on your OS, then this request will fail with
1422C<ENOSYS>.
1423
1424C<$start> is the starting offset to query extents for, C<$length> is the
1425size of the range to query - if it is C<undef>, then the whole file will
1426be queried.
1427
1428C<$flags> is a combination of flags (C<IO::AIO::FIEMAP_FLAG_SYNC> or
1429C<IO::AIO::FIEMAP_FLAG_XATTR> - C<IO::AIO::FIEMAP_FLAGS_COMPAT> is also
1430exported), and is normally C<0> or C<IO::AIO::FIEMAP_FLAG_SYNC> to query
1431the data portion.
1432
1433C<$count> is the maximum number of extent records to return. If it is
1434C<undef>, then IO::AIO queries all extents of the range. As a very special
1435case, if it is C<0>, then the callback receives the number of extents
1436instead of the extents themselves (which is unreliable, see below).
1437
1438If an error occurs, the callback receives no arguments. The special
1439C<errno> value C<IO::AIO::EBADR> is available to test for flag errors.
1440
1441Otherwise, the callback receives an array reference with extent
1442structures. Each extent structure is an array reference itself, with the
1443following members:
1444
1445 [$logical, $physical, $length, $flags]
1446
1447Flags is any combination of the following flag values (typically either C<0>
1448or C<IO::AIO::FIEMAP_EXTENT_LAST> (1)):
1449
1450C<IO::AIO::FIEMAP_EXTENT_LAST>, C<IO::AIO::FIEMAP_EXTENT_UNKNOWN>,
1451C<IO::AIO::FIEMAP_EXTENT_DELALLOC>, C<IO::AIO::FIEMAP_EXTENT_ENCODED>,
1452C<IO::AIO::FIEMAP_EXTENT_DATA_ENCRYPTED>, C<IO::AIO::FIEMAP_EXTENT_NOT_ALIGNED>,
1453C<IO::AIO::FIEMAP_EXTENT_DATA_INLINE>, C<IO::AIO::FIEMAP_EXTENT_DATA_TAIL>,
1454C<IO::AIO::FIEMAP_EXTENT_UNWRITTEN>, C<IO::AIO::FIEMAP_EXTENT_MERGED> or
1455C<IO::AIO::FIEMAP_EXTENT_SHARED>.
1456
1457At the time of this writing (Linux 3.2), this requets is unreliable unless
1458C<$count> is C<undef>, as the kernel has all sorts of bugs preventing
1459it to return all extents of a range for files with large number of
1460extents. The code works around all these issues if C<$count> is undef.
1461
1462=item aio_group $callback->(...)
1463
1464This is a very special aio request: Instead of doing something, it is a
1465container for other aio requests, which is useful if you want to bundle
1466many requests into a single, composite, request with a definite callback
1467and the ability to cancel the whole request with its subrequests.
1468
1469Returns an object of class L<IO::AIO::GRP>. See its documentation below
1470for more info.
1471
1472Example:
1473
1474 my $grp = aio_group sub {
1475 print "all stats done\n";
1476 };
1477
1478 add $grp
1479 (aio_stat ...),
1480 (aio_stat ...),
1481 ...;
1482
1483=item aio_nop $callback->()
1484
1485This is a special request - it does nothing in itself and is only used for
1486side effects, such as when you want to add a dummy request to a group so
1487that finishing the requests in the group depends on executing the given
1488code.
1489
1490While this request does nothing, it still goes through the execution
1491phase and still requires a worker thread. Thus, the callback will not
1492be executed immediately but only after other requests in the queue have
1493entered their execution phase. This can be used to measure request
1494latency.
1495
1496=item IO::AIO::aio_busy $fractional_seconds, $callback->() *NOT EXPORTED*
1497
1498Mainly used for debugging and benchmarking, this aio request puts one of
1499the request workers to sleep for the given time.
1500
1501While it is theoretically handy to have simple I/O scheduling requests
1502like sleep and file handle readable/writable, the overhead this creates is
1503immense (it blocks a thread for a long time) so do not use this function
1504except to put your application under artificial I/O pressure.
1505
189=back 1506=back
190 1507
1508
1509=head2 IO::AIO::WD - multiple working directories
1510
1511Your process only has one current working directory, which is used by all
1512threads. This makes it hard to use relative paths (some other component
1513could call C<chdir> at any time, and it is hard to control when the path
1514will be used by IO::AIO).
1515
1516One solution for this is to always use absolute paths. This usually works,
1517but can be quite slow (the kernel has to walk the whole path on every
1518access), and can also be a hassle to implement.
1519
1520Newer POSIX systems have a number of functions (openat, fdopendir,
1521futimensat and so on) that make it possible to specify working directories
1522per operation.
1523
1524For portability, and because the clowns who "designed", or shall I write,
1525perpetrated this new interface were obviously half-drunk, this abstraction
1526cannot be perfect, though.
1527
1528IO::AIO allows you to convert directory paths into a so-called IO::AIO::WD
1529object. This object stores the canonicalised, absolute version of the
1530path, and on systems that allow it, also a directory file descriptor.
1531
1532Everywhere where a pathname is accepted by IO::AIO (e.g. in C<aio_stat>
1533or C<aio_unlink>), one can specify an array reference with an IO::AIO::WD
1534object and a pathname instead (or the IO::AIO::WD object alone, which
1535gets interpreted as C<[$wd, "."]>). If the pathname is absolute, the
1536IO::AIO::WD object is ignored, otherwise the pathname is resolved relative
1537to that IO::AIO::WD object.
1538
1539For example, to get a wd object for F</etc> and then stat F<passwd>
1540inside, you would write:
1541
1542 aio_wd "/etc", sub {
1543 my $etcdir = shift;
1544
1545 # although $etcdir can be undef on error, there is generally no reason
1546 # to check for errors here, as aio_stat will fail with ENOENT
1547 # when $etcdir is undef.
1548
1549 aio_stat [$etcdir, "passwd"], sub {
1550 # yay
1551 };
1552 };
1553
1554The fact that C<aio_wd> is a request and not a normal function shows that
1555creating an IO::AIO::WD object is itself a potentially blocking operation,
1556which is why it is done asynchronously.
1557
1558To stat the directory obtained with C<aio_wd> above, one could write
1559either of the following three request calls:
1560
1561 aio_lstat "/etc" , sub { ... # pathname as normal string
1562 aio_lstat [$wd, "."], sub { ... # "." relative to $wd (i.e. $wd itself)
1563 aio_lstat $wd , sub { ... # shorthand for the previous
1564
1565As with normal pathnames, IO::AIO keeps a copy of the working directory
1566object and the pathname string, so you could write the following without
1567causing any issues due to C<$path> getting reused:
1568
1569 my $path = [$wd, undef];
1570
1571 for my $name (qw(abc def ghi)) {
1572 $path->[1] = $name;
1573 aio_stat $path, sub {
1574 # ...
1575 };
1576 }
1577
1578There are some caveats: when directories get renamed (or deleted), the
1579pathname string doesn't change, so will point to the new directory (or
1580nowhere at all), while the directory fd, if available on the system,
1581will still point to the original directory. Most functions accepting a
1582pathname will use the directory fd on newer systems, and the string on
1583older systems. Some functions (such as realpath) will always rely on the
1584string form of the pathname.
1585
1586So this functionality is mainly useful to get some protection against
1587C<chdir>, to easily get an absolute path out of a relative path for future
1588reference, and to speed up doing many operations in the same directory
1589(e.g. when stat'ing all files in a directory).
1590
1591The following functions implement this working directory abstraction:
1592
1593=over 4
1594
1595=item aio_wd $pathname, $callback->($wd)
1596
1597Asynchonously canonicalise the given pathname and convert it to an
1598IO::AIO::WD object representing it. If possible and supported on the
1599system, also open a directory fd to speed up pathname resolution relative
1600to this working directory.
1601
1602If something goes wrong, then C<undef> is passwd to the callback instead
1603of a working directory object and C<$!> is set appropriately. Since
1604passing C<undef> as working directory component of a pathname fails the
1605request with C<ENOENT>, there is often no need for error checking in the
1606C<aio_wd> callback, as future requests using the value will fail in the
1607expected way.
1608
1609=item IO::AIO::CWD
1610
1611This is a compiletime constant (object) that represents the process
1612current working directory.
1613
1614Specifying this object as working directory object for a pathname is as if
1615the pathname would be specified directly, without a directory object. For
1616example, these calls are functionally identical:
1617
1618 aio_stat "somefile", sub { ... };
1619 aio_stat [IO::AIO::CWD, "somefile"], sub { ... };
1620
1621=back
1622
1623To recover the path associated with an IO::AIO::WD object, you can use
1624C<aio_realpath>:
1625
1626 aio_realpath $wd, sub {
1627 warn "path is $_[0]\n";
1628 };
1629
1630Currently, C<aio_statvfs> always, and C<aio_rename> and C<aio_rmdir>
1631sometimes, fall back to using an absolue path.
1632
1633=head2 IO::AIO::REQ CLASS
1634
1635All non-aggregate C<aio_*> functions return an object of this class when
1636called in non-void context.
1637
1638=over 4
1639
1640=item cancel $req
1641
1642Cancels the request, if possible. Has the effect of skipping execution
1643when entering the B<execute> state and skipping calling the callback when
1644entering the the B<result> state, but will leave the request otherwise
1645untouched (with the exception of readdir). That means that requests that
1646currently execute will not be stopped and resources held by the request
1647will not be freed prematurely.
1648
1649=item cb $req $callback->(...)
1650
1651Replace (or simply set) the callback registered to the request.
1652
1653=back
1654
1655=head2 IO::AIO::GRP CLASS
1656
1657This class is a subclass of L<IO::AIO::REQ>, so all its methods apply to
1658objects of this class, too.
1659
1660A IO::AIO::GRP object is a special request that can contain multiple other
1661aio requests.
1662
1663You create one by calling the C<aio_group> constructing function with a
1664callback that will be called when all contained requests have entered the
1665C<done> state:
1666
1667 my $grp = aio_group sub {
1668 print "all requests are done\n";
1669 };
1670
1671You add requests by calling the C<add> method with one or more
1672C<IO::AIO::REQ> objects:
1673
1674 $grp->add (aio_unlink "...");
1675
1676 add $grp aio_stat "...", sub {
1677 $_[0] or return $grp->result ("error");
1678
1679 # add another request dynamically, if first succeeded
1680 add $grp aio_open "...", sub {
1681 $grp->result ("ok");
1682 };
1683 };
1684
1685This makes it very easy to create composite requests (see the source of
1686C<aio_move> for an application) that work and feel like simple requests.
1687
1688=over 4
1689
1690=item * The IO::AIO::GRP objects will be cleaned up during calls to
1691C<IO::AIO::poll_cb>, just like any other request.
1692
1693=item * They can be canceled like any other request. Canceling will cancel not
1694only the request itself, but also all requests it contains.
1695
1696=item * They can also can also be added to other IO::AIO::GRP objects.
1697
1698=item * You must not add requests to a group from within the group callback (or
1699any later time).
1700
1701=back
1702
1703Their lifetime, simplified, looks like this: when they are empty, they
1704will finish very quickly. If they contain only requests that are in the
1705C<done> state, they will also finish. Otherwise they will continue to
1706exist.
1707
1708That means after creating a group you have some time to add requests
1709(precisely before the callback has been invoked, which is only done within
1710the C<poll_cb>). And in the callbacks of those requests, you can add
1711further requests to the group. And only when all those requests have
1712finished will the the group itself finish.
1713
1714=over 4
1715
1716=item add $grp ...
1717
1718=item $grp->add (...)
1719
1720Add one or more requests to the group. Any type of L<IO::AIO::REQ> can
1721be added, including other groups, as long as you do not create circular
1722dependencies.
1723
1724Returns all its arguments.
1725
1726=item $grp->cancel_subs
1727
1728Cancel all subrequests and clears any feeder, but not the group request
1729itself. Useful when you queued a lot of events but got a result early.
1730
1731The group request will finish normally (you cannot add requests to the
1732group).
1733
1734=item $grp->result (...)
1735
1736Set the result value(s) that will be passed to the group callback when all
1737subrequests have finished and set the groups errno to the current value
1738of errno (just like calling C<errno> without an error number). By default,
1739no argument will be passed and errno is zero.
1740
1741=item $grp->errno ([$errno])
1742
1743Sets the group errno value to C<$errno>, or the current value of errno
1744when the argument is missing.
1745
1746Every aio request has an associated errno value that is restored when
1747the callback is invoked. This method lets you change this value from its
1748default (0).
1749
1750Calling C<result> will also set errno, so make sure you either set C<$!>
1751before the call to C<result>, or call c<errno> after it.
1752
1753=item feed $grp $callback->($grp)
1754
1755Sets a feeder/generator on this group: every group can have an attached
1756generator that generates requests if idle. The idea behind this is that,
1757although you could just queue as many requests as you want in a group,
1758this might starve other requests for a potentially long time. For example,
1759C<aio_scandir> might generate hundreds of thousands of C<aio_stat>
1760requests, delaying any later requests for a long time.
1761
1762To avoid this, and allow incremental generation of requests, you can
1763instead a group and set a feeder on it that generates those requests. The
1764feed callback will be called whenever there are few enough (see C<limit>,
1765below) requests active in the group itself and is expected to queue more
1766requests.
1767
1768The feed callback can queue as many requests as it likes (i.e. C<add> does
1769not impose any limits).
1770
1771If the feed does not queue more requests when called, it will be
1772automatically removed from the group.
1773
1774If the feed limit is C<0> when this method is called, it will be set to
1775C<2> automatically.
1776
1777Example:
1778
1779 # stat all files in @files, but only ever use four aio requests concurrently:
1780
1781 my $grp = aio_group sub { print "finished\n" };
1782 limit $grp 4;
1783 feed $grp sub {
1784 my $file = pop @files
1785 or return;
1786
1787 add $grp aio_stat $file, sub { ... };
1788 };
1789
1790=item limit $grp $num
1791
1792Sets the feeder limit for the group: The feeder will be called whenever
1793the group contains less than this many requests.
1794
1795Setting the limit to C<0> will pause the feeding process.
1796
1797The default value for the limit is C<0>, but note that setting a feeder
1798automatically bumps it up to C<2>.
1799
1800=back
1801
191=head2 SUPPORT FUNCTIONS 1802=head2 SUPPORT FUNCTIONS
192 1803
1804=head3 EVENT PROCESSING AND EVENT LOOP INTEGRATION
1805
193=over 4 1806=over 4
194 1807
195=item $fileno = IO::AIO::poll_fileno 1808=item $fileno = IO::AIO::poll_fileno
196 1809
197Return the I<request result pipe filehandle>. This filehandle must be 1810Return the I<request result pipe file descriptor>. This filehandle must be
198polled for reading by some mechanism outside this module (e.g. Event 1811polled for reading by some mechanism outside this module (e.g. EV, Glib,
199or select, see below). If the pipe becomes readable you have to call 1812select and so on, see below or the SYNOPSIS). If the pipe becomes readable
200C<poll_cb> to check the results. 1813you have to call C<poll_cb> to check the results.
201 1814
202See C<poll_cb> for an example. 1815See C<poll_cb> for an example.
203 1816
204=item IO::AIO::poll_cb 1817=item IO::AIO::poll_cb
205 1818
206Process all outstanding events on the result pipe. You have to call this 1819Process some requests that have reached the result phase (i.e. they have
207regularly. Returns the number of events processed. Returns immediately 1820been executed but the results are not yet reported). You have to call
208when no events are outstanding. 1821this "regularly" to finish outstanding requests.
209 1822
210You can use Event to multiplex, e.g.: 1823Returns C<0> if all events could be processed (or there were no
1824events to process), or C<-1> if it returned earlier for whatever
1825reason. Returns immediately when no events are outstanding. The amount
1826of events processed depends on the settings of C<IO::AIO::max_poll_req>,
1827C<IO::AIO::max_poll_time> and C<IO::AIO::max_outstanding>.
1828
1829If not all requests were processed for whatever reason, the poll file
1830descriptor will still be ready when C<poll_cb> returns, so normally you
1831don't have to do anything special to have it called later.
1832
1833Apart from calling C<IO::AIO::poll_cb> when the event filehandle becomes
1834ready, it can be beneficial to call this function from loops which submit
1835a lot of requests, to make sure the results get processed when they become
1836available and not just when the loop is finished and the event loop takes
1837over again. This function returns very fast when there are no outstanding
1838requests.
1839
1840Example: Install an Event watcher that automatically calls
1841IO::AIO::poll_cb with high priority (more examples can be found in the
1842SYNOPSIS section, at the top of this document):
211 1843
212 Event->io (fd => IO::AIO::poll_fileno, 1844 Event->io (fd => IO::AIO::poll_fileno,
213 poll => 'r', async => 1, 1845 poll => 'r', async => 1,
214 cb => \&IO::AIO::poll_cb); 1846 cb => \&IO::AIO::poll_cb);
215 1847
216=item IO::AIO::poll_wait 1848=item IO::AIO::poll_wait
217 1849
218Wait till the result filehandle becomes ready for reading (simply does a 1850Wait until either at least one request is in the result phase or no
219select on the filehandle. This is useful if you want to synchronously wait 1851requests are outstanding anymore.
220for some requests to finish). 1852
1853This is useful if you want to synchronously wait for some requests to
1854become ready, without actually handling them.
221 1855
222See C<nreqs> for an example. 1856See C<nreqs> for an example.
223 1857
1858=item IO::AIO::poll
1859
1860Waits until some requests have been handled.
1861
1862Returns the number of requests processed, but is otherwise strictly
1863equivalent to:
1864
1865 IO::AIO::poll_wait, IO::AIO::poll_cb
1866
224=item IO::AIO::nreqs 1867=item IO::AIO::flush
225 1868
226Returns the number of requests currently outstanding. 1869Wait till all outstanding AIO requests have been handled.
227 1870
228Example: wait till there are no outstanding requests anymore: 1871Strictly equivalent to:
229 1872
230 IO::AIO::poll_wait, IO::AIO::poll_cb 1873 IO::AIO::poll_wait, IO::AIO::poll_cb
231 while IO::AIO::nreqs; 1874 while IO::AIO::nreqs;
232 1875
1876=item IO::AIO::max_poll_reqs $nreqs
1877
1878=item IO::AIO::max_poll_time $seconds
1879
1880These set the maximum number of requests (default C<0>, meaning infinity)
1881that are being processed by C<IO::AIO::poll_cb> in one call, respectively
1882the maximum amount of time (default C<0>, meaning infinity) spent in
1883C<IO::AIO::poll_cb> to process requests (more correctly the mininum amount
1884of time C<poll_cb> is allowed to use).
1885
1886Setting C<max_poll_time> to a non-zero value creates an overhead of one
1887syscall per request processed, which is not normally a problem unless your
1888callbacks are really really fast or your OS is really really slow (I am
1889not mentioning Solaris here). Using C<max_poll_reqs> incurs no overhead.
1890
1891Setting these is useful if you want to ensure some level of
1892interactiveness when perl is not fast enough to process all requests in
1893time.
1894
1895For interactive programs, values such as C<0.01> to C<0.1> should be fine.
1896
1897Example: Install an Event watcher that automatically calls
1898IO::AIO::poll_cb with low priority, to ensure that other parts of the
1899program get the CPU sometimes even under high AIO load.
1900
1901 # try not to spend much more than 0.1s in poll_cb
1902 IO::AIO::max_poll_time 0.1;
1903
1904 # use a low priority so other tasks have priority
1905 Event->io (fd => IO::AIO::poll_fileno,
1906 poll => 'r', nice => 1,
1907 cb => &IO::AIO::poll_cb);
1908
1909=back
1910
1911=head3 CONTROLLING THE NUMBER OF THREADS
1912
1913=over
1914
233=item IO::AIO::min_parallel $nthreads 1915=item IO::AIO::min_parallel $nthreads
234 1916
235Set the minimum number of AIO threads to C<$nthreads>. The default is 1917Set the minimum number of AIO threads to C<$nthreads>. The current
236C<1>, which means a single asynchronous operation can be done at one time 1918default is C<8>, which means eight asynchronous operations can execute
237(the number of outstanding operations, however, is unlimited). 1919concurrently at any one time (the number of outstanding requests,
1920however, is unlimited).
238 1921
1922IO::AIO starts threads only on demand, when an AIO request is queued and
1923no free thread exists. Please note that queueing up a hundred requests can
1924create demand for a hundred threads, even if it turns out that everything
1925is in the cache and could have been processed faster by a single thread.
1926
239It is recommended to keep the number of threads low, as some Linux 1927It is recommended to keep the number of threads relatively low, as some
240kernel versions will scale negatively with the number of threads (higher 1928Linux kernel versions will scale negatively with the number of threads
241parallelity => MUCH higher latency). With current Linux 2.6 versions, 4-32 1929(higher parallelity => MUCH higher latency). With current Linux 2.6
242threads should be fine. 1930versions, 4-32 threads should be fine.
243 1931
244Under normal circumstances you don't need to call this function, as this 1932Under most circumstances you don't need to call this function, as the
245module automatically starts some threads (the exact number might change, 1933module selects a default that is suitable for low to moderate load.
246and is currently 4).
247 1934
248=item IO::AIO::max_parallel $nthreads 1935=item IO::AIO::max_parallel $nthreads
249 1936
250Sets the maximum number of AIO threads to C<$nthreads>. If more than 1937Sets the maximum number of AIO threads to C<$nthreads>. If more than the
251the specified number of threads are currently running, kill them. This 1938specified number of threads are currently running, this function kills
252function blocks until the limit is reached. 1939them. This function blocks until the limit is reached.
1940
1941While C<$nthreads> are zero, aio requests get queued but not executed
1942until the number of threads has been increased again.
253 1943
254This module automatically runs C<max_parallel 0> at program end, to ensure 1944This module automatically runs C<max_parallel 0> at program end, to ensure
255that all threads are killed and that there are no outstanding requests. 1945that all threads are killed and that there are no outstanding requests.
256 1946
257Under normal circumstances you don't need to call this function. 1947Under normal circumstances you don't need to call this function.
258 1948
1949=item IO::AIO::max_idle $nthreads
1950
1951Limit the number of threads (default: 4) that are allowed to idle
1952(i.e., threads that did not get a request to process within the idle
1953timeout (default: 10 seconds). That means if a thread becomes idle while
1954C<$nthreads> other threads are also idle, it will free its resources and
1955exit.
1956
1957This is useful when you allow a large number of threads (e.g. 100 or 1000)
1958to allow for extremely high load situations, but want to free resources
1959under normal circumstances (1000 threads can easily consume 30MB of RAM).
1960
1961The default is probably ok in most situations, especially if thread
1962creation is fast. If thread creation is very slow on your system you might
1963want to use larger values.
1964
1965=item IO::AIO::idle_timeout $seconds
1966
1967Sets the minimum idle timeout (default 10) after which worker threads are
1968allowed to exit. SEe C<IO::AIO::max_idle>.
1969
259=item $oldnreqs = IO::AIO::max_outstanding $nreqs 1970=item IO::AIO::max_outstanding $maxreqs
260 1971
261Sets the maximum number of outstanding requests to C<$nreqs>. If you 1972Sets the maximum number of outstanding requests to C<$nreqs>. If
262try to queue up more than this number of requests, the caller will block until 1973you do queue up more than this number of requests, the next call to
263some requests have been handled. 1974C<IO::AIO::poll_cb> (and other functions calling C<poll_cb>, such as
1975C<IO::AIO::flush> or C<IO::AIO::poll>) will block until the limit is no
1976longer exceeded.
264 1977
265The default is very large, so normally there is no practical limit. If you 1978In other words, this setting does not enforce a queue limit, but can be
266queue up many requests in a loop it it often improves speed if you set 1979used to make poll functions block if the limit is exceeded.
267this to a relatively low number, such as C<100>.
268 1980
269Under normal circumstances you don't need to call this function. 1981This is a very bad function to use in interactive programs because it
1982blocks, and a bad way to reduce concurrency because it is inexact: Better
1983use an C<aio_group> together with a feed callback.
1984
1985Its main use is in scripts without an event loop - when you want to stat
1986a lot of files, you can write somehting like this:
1987
1988 IO::AIO::max_outstanding 32;
1989
1990 for my $path (...) {
1991 aio_stat $path , ...;
1992 IO::AIO::poll_cb;
1993 }
1994
1995 IO::AIO::flush;
1996
1997The call to C<poll_cb> inside the loop will normally return instantly, but
1998as soon as more thna C<32> reqeusts are in-flight, it will block until
1999some requests have been handled. This keeps the loop from pushing a large
2000number of C<aio_stat> requests onto the queue.
2001
2002The default value for C<max_outstanding> is very large, so there is no
2003practical limit on the number of outstanding requests.
270 2004
271=back 2005=back
272 2006
2007=head3 STATISTICAL INFORMATION
2008
2009=over
2010
2011=item IO::AIO::nreqs
2012
2013Returns the number of requests currently in the ready, execute or pending
2014states (i.e. for which their callback has not been invoked yet).
2015
2016Example: wait till there are no outstanding requests anymore:
2017
2018 IO::AIO::poll_wait, IO::AIO::poll_cb
2019 while IO::AIO::nreqs;
2020
2021=item IO::AIO::nready
2022
2023Returns the number of requests currently in the ready state (not yet
2024executed).
2025
2026=item IO::AIO::npending
2027
2028Returns the number of requests currently in the pending state (executed,
2029but not yet processed by poll_cb).
2030
2031=back
2032
2033=head3 MISCELLANEOUS FUNCTIONS
2034
2035IO::AIO implements some functions that are useful when you want to use
2036some "Advanced I/O" function not available to in Perl, without going the
2037"Asynchronous I/O" route. Many of these have an asynchronous C<aio_*>
2038counterpart.
2039
2040=over 4
2041
2042=item IO::AIO::sendfile $ofh, $ifh, $offset, $count
2043
2044Calls the C<eio_sendfile_sync> function, which is like C<aio_sendfile>,
2045but is blocking (this makes most sense if you know the input data is
2046likely cached already and the output filehandle is set to non-blocking
2047operations).
2048
2049Returns the number of bytes copied, or C<-1> on error.
2050
2051=item IO::AIO::fadvise $fh, $offset, $len, $advice
2052
2053Simply calls the C<posix_fadvise> function (see its
2054manpage for details). The following advice constants are
2055available: C<IO::AIO::FADV_NORMAL>, C<IO::AIO::FADV_SEQUENTIAL>,
2056C<IO::AIO::FADV_RANDOM>, C<IO::AIO::FADV_NOREUSE>,
2057C<IO::AIO::FADV_WILLNEED>, C<IO::AIO::FADV_DONTNEED>.
2058
2059On systems that do not implement C<posix_fadvise>, this function returns
2060ENOSYS, otherwise the return value of C<posix_fadvise>.
2061
2062=item IO::AIO::madvise $scalar, $offset, $len, $advice
2063
2064Simply calls the C<posix_madvise> function (see its
2065manpage for details). The following advice constants are
2066available: C<IO::AIO::MADV_NORMAL>, C<IO::AIO::MADV_SEQUENTIAL>,
2067C<IO::AIO::MADV_RANDOM>, C<IO::AIO::MADV_WILLNEED>, C<IO::AIO::MADV_DONTNEED>,
2068C<IO::AIO::MADV_FREE>.
2069
2070On systems that do not implement C<posix_madvise>, this function returns
2071ENOSYS, otherwise the return value of C<posix_madvise>.
2072
2073=item IO::AIO::mprotect $scalar, $offset, $len, $protect
2074
2075Simply calls the C<mprotect> function on the preferably AIO::mmap'ed
2076$scalar (see its manpage for details). The following protect
2077constants are available: C<IO::AIO::PROT_NONE>, C<IO::AIO::PROT_READ>,
2078C<IO::AIO::PROT_WRITE>, C<IO::AIO::PROT_EXEC>.
2079
2080On systems that do not implement C<mprotect>, this function returns
2081ENOSYS, otherwise the return value of C<mprotect>.
2082
2083=item IO::AIO::mmap $scalar, $length, $prot, $flags, $fh[, $offset]
2084
2085Memory-maps a file (or anonymous memory range) and attaches it to the
2086given C<$scalar>, which will act like a string scalar. Returns true on
2087success, and false otherwise.
2088
2089The only operations allowed on the scalar are C<substr>/C<vec> that don't
2090change the string length, and most read-only operations such as copying it
2091or searching it with regexes and so on.
2092
2093Anything else is unsafe and will, at best, result in memory leaks.
2094
2095The memory map associated with the C<$scalar> is automatically removed
2096when the C<$scalar> is destroyed, or when the C<IO::AIO::mmap> or
2097C<IO::AIO::munmap> functions are called.
2098
2099This calls the C<mmap>(2) function internally. See your system's manual
2100page for details on the C<$length>, C<$prot> and C<$flags> parameters.
2101
2102The C<$length> must be larger than zero and smaller than the actual
2103filesize.
2104
2105C<$prot> is a combination of C<IO::AIO::PROT_NONE>, C<IO::AIO::PROT_EXEC>,
2106C<IO::AIO::PROT_READ> and/or C<IO::AIO::PROT_WRITE>,
2107
2108C<$flags> can be a combination of
2109C<IO::AIO::MAP_SHARED> or
2110C<IO::AIO::MAP_PRIVATE>,
2111or a number of system-specific flags (when not available, the are C<0>):
2112C<IO::AIO::MAP_ANONYMOUS> (which is set to C<MAP_ANON> if your system only provides this constant),
2113C<IO::AIO::MAP_LOCKED>,
2114C<IO::AIO::MAP_NORESERVE>,
2115C<IO::AIO::MAP_POPULATE>,
2116C<IO::AIO::MAP_NONBLOCK>,
2117C<IO::AIO::MAP_FIXED>,
2118C<IO::AIO::MAP_GROWSDOWN>,
2119C<IO::AIO::MAP_32BIT>,
2120C<IO::AIO::MAP_HUGETLB> or
2121C<IO::AIO::MAP_STACK>.
2122
2123If C<$fh> is C<undef>, then a file descriptor of C<-1> is passed.
2124
2125C<$offset> is the offset from the start of the file - it generally must be
2126a multiple of C<IO::AIO::PAGESIZE> and defaults to C<0>.
2127
2128Example:
2129
2130 use Digest::MD5;
2131 use IO::AIO;
2132
2133 open my $fh, "<verybigfile"
2134 or die "$!";
2135
2136 IO::AIO::mmap my $data, -s $fh, IO::AIO::PROT_READ, IO::AIO::MAP_SHARED, $fh
2137 or die "verybigfile: $!";
2138
2139 my $fast_md5 = md5 $data;
2140
2141=item IO::AIO::munmap $scalar
2142
2143Removes a previous mmap and undefines the C<$scalar>.
2144
2145=item IO::AIO::munlock $scalar, $offset = 0, $length = undef
2146
2147Calls the C<munlock> function, undoing the effects of a previous
2148C<aio_mlock> call (see its description for details).
2149
2150=item IO::AIO::munlockall
2151
2152Calls the C<munlockall> function.
2153
2154On systems that do not implement C<munlockall>, this function returns
2155ENOSYS, otherwise the return value of C<munlockall>.
2156
2157=item IO::AIO::splice $r_fh, $r_off, $w_fh, $w_off, $length, $flags
2158
2159Calls the GNU/Linux C<splice(2)> syscall, if available. If C<$r_off> or
2160C<$w_off> are C<undef>, then C<NULL> is passed for these, otherwise they
2161should be the file offset.
2162
2163C<$r_fh> and C<$w_fh> should not refer to the same file, as splice might
2164silently corrupt the data in this case.
2165
2166The following symbol flag values are available: C<IO::AIO::SPLICE_F_MOVE>,
2167C<IO::AIO::SPLICE_F_NONBLOCK>, C<IO::AIO::SPLICE_F_MORE> and
2168C<IO::AIO::SPLICE_F_GIFT>.
2169
2170See the C<splice(2)> manpage for details.
2171
2172=item IO::AIO::tee $r_fh, $w_fh, $length, $flags
2173
2174Calls the GNU/Linux C<tee(2)> syscall, see its manpage and the
2175description for C<IO::AIO::splice> above for details.
2176
2177=item $actual_size = IO::AIO::pipesize $r_fh[, $new_size]
2178
2179Attempts to query or change the pipe buffer size. Obviously works only
2180on pipes, and currently works only on GNU/Linux systems, and fails with
2181C<-1>/C<ENOSYS> everywhere else. If anybody knows how to influence pipe buffer
2182size on other systems, drop me a note.
2183
2184=item ($rfh, $wfh) = IO::AIO::pipe2 [$flags]
2185
2186This is a direct interface to the Linux L<pipe2(2)> system call. If
2187C<$flags> is missing or C<0>, then this should be the same as a call to
2188perl's built-in C<pipe> function and create a new pipe, and works on
2189systems that lack the pipe2 syscall. On win32, this case invokes C<_pipe
2190(..., 4096, O_BINARY)>.
2191
2192If C<$flags> is non-zero, it tries to invoke the pipe2 system call with
2193the given flags (Linux 2.6.27, glibc 2.9).
2194
2195On success, the read and write file handles are returned.
2196
2197On error, nothing will be returned. If the pipe2 syscall is missing and
2198C<$flags> is non-zero, fails with C<ENOSYS>.
2199
2200Please refer to L<pipe2(2)> for more info on the C<$flags>, but at the
2201time of this writing, C<IO::AIO::O_CLOEXEC>, C<IO::AIO::O_NONBLOCK> and
2202C<IO::AIO::O_DIRECT> (Linux 3.4, for packet-based pipes) were supported.
2203
2204=back
2205
273=cut 2206=cut
274 2207
275# support function to convert a fd into a perl filehandle
276sub _fd2fh {
277 return undef if $_[0] < 0;
278
279 # try to be perl5.6-compatible
280 local *AIO_FH;
281 open AIO_FH, "+<&=$_[0]"
282 or return undef;
283
284 *AIO_FH
285}
286
287min_parallel 4; 2208min_parallel 8;
288 2209
289END { 2210END { flush }
290 max_parallel 0;
291}
292 2211
2931; 22121;
294 2213
2214=head1 EVENT LOOP INTEGRATION
2215
2216It is recommended to use L<AnyEvent::AIO> to integrate IO::AIO
2217automatically into many event loops:
2218
2219 # AnyEvent integration (EV, Event, Glib, Tk, POE, urxvt, pureperl...)
2220 use AnyEvent::AIO;
2221
2222You can also integrate IO::AIO manually into many event loops, here are
2223some examples of how to do this:
2224
2225 # EV integration
2226 my $aio_w = EV::io IO::AIO::poll_fileno, EV::READ, \&IO::AIO::poll_cb;
2227
2228 # Event integration
2229 Event->io (fd => IO::AIO::poll_fileno,
2230 poll => 'r',
2231 cb => \&IO::AIO::poll_cb);
2232
2233 # Glib/Gtk2 integration
2234 add_watch Glib::IO IO::AIO::poll_fileno,
2235 in => sub { IO::AIO::poll_cb; 1 };
2236
2237 # Tk integration
2238 Tk::Event::IO->fileevent (IO::AIO::poll_fileno, "",
2239 readable => \&IO::AIO::poll_cb);
2240
2241 # Danga::Socket integration
2242 Danga::Socket->AddOtherFds (IO::AIO::poll_fileno =>
2243 \&IO::AIO::poll_cb);
2244
2245=head2 FORK BEHAVIOUR
2246
2247Usage of pthreads in a program changes the semantics of fork
2248considerably. Specifically, only async-safe functions can be called after
2249fork. Perl doesn't know about this, so in general, you cannot call fork
2250with defined behaviour in perl if pthreads are involved. IO::AIO uses
2251pthreads, so this applies, but many other extensions and (for inexplicable
2252reasons) perl itself often is linked against pthreads, so this limitation
2253applies to quite a lot of perls.
2254
2255This module no longer tries to fight your OS, or POSIX. That means IO::AIO
2256only works in the process that loaded it. Forking is fully supported, but
2257using IO::AIO in the child is not.
2258
2259You might get around by not I<using> IO::AIO before (or after)
2260forking. You could also try to call the L<IO::AIO::reinit> function in the
2261child:
2262
2263=over 4
2264
2265=item IO::AIO::reinit
2266
2267Abandons all current requests and I/O threads and simply reinitialises all
2268data structures. This is not an operation supported by any standards, but
2269happens to work on GNU/Linux and some newer BSD systems.
2270
2271The only reasonable use for this function is to call it after forking, if
2272C<IO::AIO> was used in the parent. Calling it while IO::AIO is active in
2273the process will result in undefined behaviour. Calling it at any time
2274will also result in any undefined (by POSIX) behaviour.
2275
2276=back
2277
2278=head2 MEMORY USAGE
2279
2280Per-request usage:
2281
2282Each aio request uses - depending on your architecture - around 100-200
2283bytes of memory. In addition, stat requests need a stat buffer (possibly
2284a few hundred bytes), readdir requires a result buffer and so on. Perl
2285scalars and other data passed into aio requests will also be locked and
2286will consume memory till the request has entered the done state.
2287
2288This is not awfully much, so queuing lots of requests is not usually a
2289problem.
2290
2291Per-thread usage:
2292
2293In the execution phase, some aio requests require more memory for
2294temporary buffers, and each thread requires a stack and other data
2295structures (usually around 16k-128k, depending on the OS).
2296
2297=head1 KNOWN BUGS
2298
2299Known bugs will be fixed in the next release.
2300
295=head1 SEE ALSO 2301=head1 SEE ALSO
296 2302
297L<Coro>, L<Linux::AIO>. 2303L<AnyEvent::AIO> for easy integration into event loops, L<Coro::AIO> for a
2304more natural syntax.
298 2305
299=head1 AUTHOR 2306=head1 AUTHOR
300 2307
301 Marc Lehmann <schmorp@schmorp.de> 2308 Marc Lehmann <schmorp@schmorp.de>
302 http://home.schmorp.de/ 2309 http://home.schmorp.de/

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines