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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines