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.12 by root, Mon Jul 11 01:03:17 2005 UTC vs.
Revision 1.77 by root, Wed Oct 25 17:57:30 2006 UTC

15 15
16 aio_read $fh, 30000, 1024, $buffer, 0, sub { 16 aio_read $fh, 30000, 1024, $buffer, 0, sub {
17 $_[0] > 0 or die "read error: $!"; 17 $_[0] > 0 or die "read error: $!";
18 }; 18 };
19 19
20 # Event 20 # version 2+ has request and group objects
21 use IO::AIO 2;
22
23 aioreq_pri 4; # give next request a very high priority
24 my $req = aio_unlink "/tmp/file", sub { };
25 $req->cancel; # cancel request if still in queue
26
27 my $grp = aio_group sub { print "all stats done\n" };
28 add $grp aio_stat "..." for ...;
29
30 # AnyEvent integration
31 open my $fh, "<&=" . IO::AIO::poll_fileno or die "$!";
32 my $w = AnyEvent->io (fh => $fh, poll => 'r', cb => sub { IO::AIO::poll_cb });
33
34 # Event integration
21 Event->io (fd => IO::AIO::poll_fileno, 35 Event->io (fd => IO::AIO::poll_fileno,
22 poll => 'r', 36 poll => 'r',
23 cb => \&IO::AIO::poll_cb); 37 cb => \&IO::AIO::poll_cb);
24 38
25 # Glib/Gtk2 39 # Glib/Gtk2 integration
26 add_watch Glib::IO IO::AIO::poll_fileno, 40 add_watch Glib::IO IO::AIO::poll_fileno,
27 \&IO::AIO::poll_cb; 41 in => sub { IO::AIO::poll_cb; 1 };
28 42
29 # Tk 43 # Tk integration
30 Tk::Event::IO->fileevent (IO::AIO::poll_fileno, "", 44 Tk::Event::IO->fileevent (IO::AIO::poll_fileno, "",
31 readable => \&IO::AIO::poll_cb); 45 readable => \&IO::AIO::poll_cb);
32 46
33 # Danga::Socket 47 # Danga::Socket integration
34 Danga::Socket->AddOtherFds (IO::AIO::poll_fileno => 48 Danga::Socket->AddOtherFds (IO::AIO::poll_fileno =>
35 \&IO::AIO::poll_cb); 49 \&IO::AIO::poll_cb);
36 50
37
38=head1 DESCRIPTION 51=head1 DESCRIPTION
39 52
40This module implements asynchronous I/O using whatever means your 53This module implements asynchronous I/O using whatever means your
41operating system supports. 54operating system supports.
42 55
43Currently, a number of threads are started that execute your read/writes 56In 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 57requests and signal their completion. You don't need thread support
45perl, and the threads created by this module will not be visible to the 58in 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 59to perl. In the future, this module might make use of the native aio
47aio functions available on many operating systems. However, they are often 60functions available on many operating systems. However, they are often
48not well-supported (Linux doesn't allow them on normal files currently, 61not well-supported or restricted (Linux doesn't allow them on normal
49for example), and they would only support aio_read and aio_write, so the 62files currently, for example), and they would only support aio_read and
50remaining functionality would have to be implemented using threads anyway. 63aio_write, so the remaining functionality would have to be implemented
64using threads anyway.
51 65
52Although the module will work with in the presence of other threads, it is 66Although the module will work with in the presence of other (Perl-)
53currently not reentrant, so use appropriate locking yourself. 67threads, it is currently not reentrant in any way, so use appropriate
68locking yourself, always call C<poll_cb> from within the same thread, or
69never call C<poll_cb> (or other C<aio_> functions) recursively.
70
71=head1 REQUEST ANATOMY AND LIFETIME
72
73Every C<aio_*> function creates a request. which is a C data structure not
74directly visible to Perl.
75
76If called in non-void context, every request function returns a Perl
77object representing the request. In void context, nothing is returned,
78which saves a bit of memory.
79
80The perl object is a fairly standard ref-to-hash object. The hash contents
81are not used by IO::AIO so you are free to store anything you like in it.
82
83During their existance, aio requests travel through the following states,
84in order:
85
86=over 4
87
88=item ready
89
90Immediately after a request is created it is put into the ready state,
91waiting for a thread to execute it.
92
93=item execute
94
95A thread has accepted the request for processing and is currently
96executing it (e.g. blocking in read).
97
98=item pending
99
100The request has been executed and is waiting for result processing.
101
102While request submission and execution is fully asynchronous, result
103processing is not and relies on the perl interpreter calling C<poll_cb>
104(or another function with the same effect).
105
106=item result
107
108The request results are processed synchronously by C<poll_cb>.
109
110The C<poll_cb> function will process all outstanding aio requests by
111calling their callbacks, freeing memory associated with them and managing
112any groups they are contained in.
113
114=item done
115
116Request has reached the end of its lifetime and holds no resources anymore
117(except possibly for the Perl object, but its connection to the actual
118aio request is severed and calling its methods will either do nothing or
119result in a runtime error).
54 120
55=cut 121=cut
56 122
57package IO::AIO; 123package IO::AIO;
58 124
125no warnings;
126use strict 'vars';
127
59use base 'Exporter'; 128use base 'Exporter';
60 129
61use Fcntl ();
62
63BEGIN { 130BEGIN {
64 $VERSION = 0.3; 131 our $VERSION = '2.0';
65 132
66 @EXPORT = qw(aio_read aio_write aio_open aio_close aio_stat aio_lstat aio_unlink 133 our @AIO_REQ = qw(aio_sendfile aio_read aio_write aio_open aio_close aio_stat
67 aio_fsync aio_fdatasync aio_readahead); 134 aio_lstat aio_unlink aio_rmdir aio_readdir aio_scandir aio_symlink
68 @EXPORT_OK = qw(poll_fileno poll_cb min_parallel max_parallel max_outstanding nreqs); 135 aio_fsync aio_fdatasync aio_readahead aio_rename aio_link aio_move
136 aio_group aio_nop);
137 our @EXPORT = (@AIO_REQ, qw(aioreq_pri aioreq_nice));
138 our @EXPORT_OK = qw(poll_fileno poll_cb poll_wait flush
139 min_parallel max_parallel nreqs);
140
141 @IO::AIO::GRP::ISA = 'IO::AIO::REQ';
69 142
70 require XSLoader; 143 require XSLoader;
71 XSLoader::load IO::AIO, $VERSION; 144 XSLoader::load ("IO::AIO", $VERSION);
72} 145}
73 146
74=head1 FUNCTIONS 147=head1 FUNCTIONS
75 148
76=head2 AIO FUNCTIONS 149=head2 AIO FUNCTIONS
77 150
78All the C<aio_*> calls are more or less thin wrappers around the syscall 151All the C<aio_*> calls are more or less thin wrappers around the syscall
79with the same name (sans C<aio_>). The arguments are similar or identical, 152with the same name (sans C<aio_>). The arguments are similar or identical,
80and they all accept an additional C<$callback> argument which must be 153and they all accept an additional (and optional) C<$callback> argument
81a code reference. This code reference will get called with the syscall 154which must be a code reference. This code reference will get called with
82return code (e.g. most syscalls return C<-1> on error, unlike perl, which 155the syscall return code (e.g. most syscalls return C<-1> on error, unlike
83usually delivers "false") as it's sole argument when the given syscall has 156perl, which usually delivers "false") as it's sole argument when the given
84been executed asynchronously. 157syscall has been executed asynchronously.
85 158
86All functions that expect a filehandle will also accept a file descriptor. 159All functions expecting a filehandle keep a copy of the filehandle
160internally until the request has finished.
87 161
162All requests return objects of type L<IO::AIO::REQ> that allow further
163manipulation of those requests while they are in-flight.
164
88The filenames you pass to these routines I<must> be absolute. The reason 165The pathnames you pass to these routines I<must> be absolute and
89is that at the time the request is being executed, the current working 166encoded in byte form. The reason for the former is that at the time the
90directory could have changed. Alternatively, you can make sure that you 167request is being executed, the current working directory could have
168changed. Alternatively, you can make sure that you never change the
91never change the current working directory. 169current working directory.
170
171To encode pathnames to byte form, either make sure you either: a)
172always pass in filenames you got from outside (command line, readdir
173etc.), b) are ASCII or ISO 8859-1, c) use the Encode module and encode
174your pathnames to the locale (or other) encoding in effect in the user
175environment, d) use Glib::filename_from_unicode on unicode filenames or e)
176use something else.
92 177
93=over 4 178=over 4
94 179
180=item aioreq_pri $pri
181
182Sets the priority for the next aio request. The default priority
183is C<0>, the minimum and maximum priorities are C<-4> and C<4>,
184respectively. Requests with higher priority will be serviced first.
185
186The priority will be reset to C<0> after each call to one of the C<aio_>
187functions.
188
189Example: open a file with low priority, then read something from it with
190higher priority so the read request is serviced before other low priority
191open requests (potentially spamming the cache):
192
193 aioreq_pri -3;
194 aio_open ..., sub {
195 return unless $_[0];
196
197 aioreq_pri -2;
198 aio_read $_[0], ..., sub {
199 ...
200 };
201 };
202
203=item aioreq_nice $pri_adjust
204
205Similar to C<aioreq_pri>, but subtracts the given value from the current
206priority, so effects are cumulative.
207
95=item aio_open $pathname, $flags, $mode, $callback 208=item aio_open $pathname, $flags, $mode, $callback->($fh)
96 209
97Asynchronously open or create a file and call the callback with a newly 210Asynchronously open or create a file and call the callback with a newly
98created filehandle for the file. 211created filehandle for the file.
99 212
100The pathname passed to C<aio_open> must be absolute. See API NOTES, above, 213The pathname passed to C<aio_open> must be absolute. See API NOTES, above,
101for an explanation. 214for an explanation.
102 215
103The C<$mode> argument is a bitmask. See the C<Fcntl> module for a 216The C<$flags> argument is a bitmask. See the C<Fcntl> module for a
104list. They are the same as used in C<sysopen>. 217list. They are the same as used by C<sysopen>.
218
219Likewise, C<$mode> specifies the mode of the newly created file, if it
220didn't exist and C<O_CREAT> has been given, just like perl's C<sysopen>,
221except that it is mandatory (i.e. use C<0> if you don't create new files,
222and C<0666> or C<0777> if you do).
105 223
106Example: 224Example:
107 225
108 aio_open "/etc/passwd", O_RDONLY, 0, sub { 226 aio_open "/etc/passwd", O_RDONLY, 0, sub {
109 if ($_[0]) { 227 if ($_[0]) {
112 } else { 230 } else {
113 die "open failed: $!\n"; 231 die "open failed: $!\n";
114 } 232 }
115 }; 233 };
116 234
117=item aio_close $fh, $callback 235=item aio_close $fh, $callback->($status)
118 236
119Asynchronously close a file and call the callback with the result 237Asynchronously close a file and call the callback with the result
120code. I<WARNING:> although accepted, you should not pass in a perl 238code. I<WARNING:> although accepted, you should not pass in a perl
121filehandle here, as perl will likely close the file descriptor itself when 239filehandle here, as perl will likely close the file descriptor another
122the filehandle is destroyed. Normally, you can safely call perls C<close> 240time when the filehandle is destroyed. Normally, you can safely call perls
123or just let filehandles go out of scope. 241C<close> or just let filehandles go out of scope.
124 242
243This is supposed to be a bug in the API, so that might change. It's
244therefore best to avoid this function.
245
125=item aio_read $fh,$offset,$length, $data,$dataoffset,$callback 246=item aio_read $fh,$offset,$length, $data,$dataoffset, $callback->($retval)
126 247
127=item aio_write $fh,$offset,$length, $data,$dataoffset,$callback 248=item aio_write $fh,$offset,$length, $data,$dataoffset, $callback->($retval)
128 249
129Reads or writes C<length> bytes from the specified C<fh> and C<offset> 250Reads or writes C<length> bytes from the specified C<fh> and C<offset>
130into the scalar given by C<data> and offset C<dataoffset> and calls the 251into the scalar given by C<data> and offset C<dataoffset> and calls the
131callback without the actual number of bytes read (or -1 on error, just 252callback without the actual number of bytes read (or -1 on error, just
132like the syscall). 253like the syscall).
133 254
255The C<$data> scalar I<MUST NOT> be modified in any way while the request
256is outstanding. Modifying it can result in segfaults or WW3 (if the
257necessary/optional hardware is installed).
258
134Example: Read 15 bytes at offset 7 into scalar C<$buffer>, strating at 259Example: Read 15 bytes at offset 7 into scalar C<$buffer>, starting at
135offset C<0> within the scalar: 260offset C<0> within the scalar:
136 261
137 aio_read $fh, 7, 15, $buffer, 0, sub { 262 aio_read $fh, 7, 15, $buffer, 0, sub {
138 $_[0] > 0 or die "read error: $!"; 263 $_[0] > 0 or die "read error: $!";
139 print "read $_[0] bytes: <$buffer>\n"; 264 print "read $_[0] bytes: <$buffer>\n";
140 }; 265 };
141 266
267=item aio_move $srcpath, $dstpath, $callback->($status)
268
269Try to move the I<file> (directories not supported as either source or
270destination) from C<$srcpath> to C<$dstpath> and call the callback with
271the C<0> (error) or C<-1> ok.
272
273This is a composite request that tries to rename(2) the file first. If
274rename files with C<EXDEV>, it creates the destination file with mode 0200
275and copies the contents of the source file into it using C<aio_sendfile>,
276followed by restoring atime, mtime, access mode and uid/gid, in that
277order, and unlinking the C<$srcpath>.
278
279If an error occurs, the partial destination file will be unlinked, if
280possible, except when setting atime, mtime, access mode and uid/gid, where
281errors are being ignored.
282
283=cut
284
285sub aio_move($$$) {
286 my ($src, $dst, $cb) = @_;
287
288 my $grp = aio_group $cb;
289
290 add $grp aio_rename $src, $dst, sub {
291 if ($_[0] && $! == EXDEV) {
292 add $grp aio_open $src, O_RDONLY, 0, sub {
293 if (my $src_fh = $_[0]) {
294 my @stat = stat $src_fh;
295
296 add $grp aio_open $dst, O_WRONLY, 0200, sub {
297 if (my $dst_fh = $_[0]) {
298 add $grp aio_sendfile $dst_fh, $src_fh, 0, $stat[7], sub {
299 close $src_fh;
300
301 if ($_[0] == $stat[7]) {
302 utime $stat[8], $stat[9], $dst;
303 chmod $stat[2] & 07777, $dst_fh;
304 chown $stat[4], $stat[5], $dst_fh;
305 close $dst_fh;
306
307 add $grp aio_unlink $src, sub {
308 $grp->result ($_[0]);
309 };
310 } else {
311 my $errno = $!;
312 add $grp aio_unlink $dst, sub {
313 $! = $errno;
314 $grp->result (-1);
315 };
316 }
317 };
318 } else {
319 $grp->result (-1);
320 }
321 },
322
323 } else {
324 $grp->result (-1);
325 }
326 };
327 } else {
328 $grp->result ($_[0]);
329 }
330 };
331
332 $grp
333}
334
335=item aio_sendfile $out_fh, $in_fh, $in_offset, $length, $callback->($retval)
336
337Tries to copy C<$length> bytes from C<$in_fh> to C<$out_fh>. It starts
338reading at byte offset C<$in_offset>, and starts writing at the current
339file offset of C<$out_fh>. Because of that, it is not safe to issue more
340than one C<aio_sendfile> per C<$out_fh>, as they will interfere with each
341other.
342
343This call tries to make use of a native C<sendfile> syscall to provide
344zero-copy operation. For this to work, C<$out_fh> should refer to a
345socket, and C<$in_fh> should refer to mmap'able file.
346
347If the native sendfile call fails or is not implemented, it will be
348emulated, so you can call C<aio_sendfile> on any type of filehandle
349regardless of the limitations of the operating system.
350
351Please note, however, that C<aio_sendfile> can read more bytes from
352C<$in_fh> than are written, and there is no way to find out how many
353bytes have been read from C<aio_sendfile> alone, as C<aio_sendfile> only
354provides the number of bytes written to C<$out_fh>. Only if the result
355value equals C<$length> one can assume that C<$length> bytes have been
356read.
357
142=item aio_readahead $fh,$offset,$length, $callback 358=item aio_readahead $fh,$offset,$length, $callback->($retval)
143 359
144Asynchronously reads the specified byte range into the page cache, using
145the C<readahead> syscall. If that syscall doesn't exist the status will be
146C<-1> and C<$!> is set to ENOSYS.
147
148readahead() populates the page cache with data from a file so that 360C<aio_readahead> populates the page cache with data from a file so that
149subsequent reads from that file will not block on disk I/O. The C<$offset> 361subsequent reads from that file will not block on disk I/O. The C<$offset>
150argument specifies the starting point from which data is to be read and 362argument specifies the starting point from which data is to be read and
151C<$length> specifies the number of bytes to be read. I/O is performed in 363C<$length> specifies the number of bytes to be read. I/O is performed in
152whole pages, so that offset is effectively rounded down to a page boundary 364whole pages, so that offset is effectively rounded down to a page boundary
153and bytes are read up to the next page boundary greater than or equal to 365and bytes are read up to the next page boundary greater than or equal to
154(off-set+length). aio_readahead() does not read beyond the end of the 366(off-set+length). C<aio_readahead> does not read beyond the end of the
155file. The current file offset of the file is left unchanged. 367file. The current file offset of the file is left unchanged.
156 368
369If that syscall doesn't exist (likely if your OS isn't Linux) it will be
370emulated by simply reading the data, which would have a similar effect.
371
157=item aio_stat $fh_or_path, $callback 372=item aio_stat $fh_or_path, $callback->($status)
158 373
159=item aio_lstat $fh, $callback 374=item aio_lstat $fh, $callback->($status)
160 375
161Works like perl's C<stat> or C<lstat> in void context. The callback will 376Works like perl's C<stat> or C<lstat> in void context. The callback will
162be called after the stat and the results will be available using C<stat _> 377be called after the stat and the results will be available using C<stat _>
163or C<-s _> etc... 378or C<-s _> etc...
164 379
174 aio_stat "/etc/passwd", sub { 389 aio_stat "/etc/passwd", sub {
175 $_[0] and die "stat failed: $!"; 390 $_[0] and die "stat failed: $!";
176 print "size is ", -s _, "\n"; 391 print "size is ", -s _, "\n";
177 }; 392 };
178 393
179=item aio_unlink $pathname, $callback 394=item aio_unlink $pathname, $callback->($status)
180 395
181Asynchronously unlink (delete) a file and call the callback with the 396Asynchronously unlink (delete) a file and call the callback with the
182result code. 397result code.
183 398
399=item aio_link $srcpath, $dstpath, $callback->($status)
400
401Asynchronously create a new link to the existing object at C<$srcpath> at
402the path C<$dstpath> and call the callback with the result code.
403
404=item aio_symlink $srcpath, $dstpath, $callback->($status)
405
406Asynchronously create a new symbolic link to the existing object at C<$srcpath> at
407the path C<$dstpath> and call the callback with the result code.
408
409=item aio_rename $srcpath, $dstpath, $callback->($status)
410
411Asynchronously rename the object at C<$srcpath> to C<$dstpath>, just as
412rename(2) and call the callback with the result code.
413
414=item aio_rmdir $pathname, $callback->($status)
415
416Asynchronously rmdir (delete) a directory and call the callback with the
417result code.
418
419=item aio_readdir $pathname, $callback->($entries)
420
421Unlike the POSIX call of the same name, C<aio_readdir> reads an entire
422directory (i.e. opendir + readdir + closedir). The entries will not be
423sorted, and will B<NOT> include the C<.> and C<..> entries.
424
425The callback a single argument which is either C<undef> or an array-ref
426with the filenames.
427
428=item aio_scandir $path, $maxreq, $callback->($dirs, $nondirs)
429
430Scans a directory (similar to C<aio_readdir>) but additionally tries to
431efficiently separate the entries of directory C<$path> into two sets of
432names, directories you can recurse into (directories), and ones you cannot
433recurse into (everything else, including symlinks to directories).
434
435C<aio_scandir> is a composite request that creates of many sub requests_
436C<$maxreq> specifies the maximum number of outstanding aio requests that
437this function generates. If it is C<< <= 0 >>, then a suitable default
438will be chosen (currently 6).
439
440On error, the callback is called without arguments, otherwise it receives
441two array-refs with path-relative entry names.
442
443Example:
444
445 aio_scandir $dir, 0, sub {
446 my ($dirs, $nondirs) = @_;
447 print "real directories: @$dirs\n";
448 print "everything else: @$nondirs\n";
449 };
450
451Implementation notes.
452
453The C<aio_readdir> cannot be avoided, but C<stat()>'ing every entry can.
454
455After reading the directory, the modification time, size etc. of the
456directory before and after the readdir is checked, and if they match (and
457isn't the current time), the link count will be used to decide how many
458entries are directories (if >= 2). Otherwise, no knowledge of the number
459of subdirectories will be assumed.
460
461Then entries will be sorted into likely directories (everything without
462a non-initial dot currently) and likely non-directories (everything
463else). Then every entry plus an appended C</.> will be C<stat>'ed,
464likely directories first. If that succeeds, it assumes that the entry
465is a directory or a symlink to directory (which will be checked
466seperately). This is often faster than stat'ing the entry itself because
467filesystems might detect the type of the entry without reading the inode
468data (e.g. ext2fs filetype feature).
469
470If the known number of directories (link count - 2) has been reached, the
471rest of the entries is assumed to be non-directories.
472
473This only works with certainty on POSIX (= UNIX) filesystems, which
474fortunately are the vast majority of filesystems around.
475
476It will also likely work on non-POSIX filesystems with reduced efficiency
477as those tend to return 0 or 1 as link counts, which disables the
478directory counting heuristic.
479
480=cut
481
482sub aio_scandir($$$) {
483 my ($path, $maxreq, $cb) = @_;
484
485 my $grp = aio_group $cb;
486
487 $maxreq = 6 if $maxreq <= 0;
488
489 # stat once
490 add $grp aio_stat $path, sub {
491 return $grp->result () if $_[0];
492 my $now = time;
493 my $hash1 = join ":", (stat _)[0,1,3,7,9];
494
495 # read the directory entries
496 add $grp aio_readdir $path, sub {
497 my $entries = shift
498 or return $grp->result ();
499
500 # stat the dir another time
501 add $grp aio_stat $path, sub {
502 my $hash2 = join ":", (stat _)[0,1,3,7,9];
503
504 my $ndirs;
505
506 # take the slow route if anything looks fishy
507 if ($hash1 ne $hash2 or (stat _)[9] == $now) {
508 $ndirs = -1;
509 } else {
510 # if nlink == 2, we are finished
511 # on non-posix-fs's, we rely on nlink < 2
512 $ndirs = (stat _)[3] - 2
513 or return $grp->result ([], $entries);
514 }
515
516 # sort into likely dirs and likely nondirs
517 # dirs == files without ".", short entries first
518 $entries = [map $_->[0],
519 sort { $b->[1] cmp $a->[1] }
520 map [$_, sprintf "%s%04d", (/.\./ ? "1" : "0"), length],
521 @$entries];
522
523 my (@dirs, @nondirs);
524
525 my $statgrp = add $grp aio_group sub {
526 $grp->result (\@dirs, \@nondirs);
527 };
528
529 limit $statgrp $maxreq;
530 feed $statgrp sub {
531 return unless @$entries;
532 my $entry = pop @$entries;
533
534 add $statgrp aio_stat "$path/$entry/.", sub {
535 if ($_[0] < 0) {
536 push @nondirs, $entry;
537 } else {
538 # need to check for real directory
539 add $statgrp aio_lstat "$path/$entry", sub {
540 if (-d _) {
541 push @dirs, $entry;
542
543 unless (--$ndirs) {
544 push @nondirs, @$entries;
545 feed $statgrp;
546 }
547 } else {
548 push @nondirs, $entry;
549 }
550 }
551 }
552 };
553 };
554 };
555 };
556 };
557
558 $grp
559}
560
184=item aio_fsync $fh, $callback 561=item aio_fsync $fh, $callback->($status)
185 562
186Asynchronously call fsync on the given filehandle and call the callback 563Asynchronously call fsync on the given filehandle and call the callback
187with the fsync result code. 564with the fsync result code.
188 565
189=item aio_fdatasync $fh, $callback 566=item aio_fdatasync $fh, $callback->($status)
190 567
191Asynchronously call fdatasync on the given filehandle and call the 568Asynchronously call fdatasync on the given filehandle and call the
192callback with the fdatasync result code. 569callback with the fdatasync result code.
193 570
571If this call isn't available because your OS lacks it or it couldn't be
572detected, it will be emulated by calling C<fsync> instead.
573
574=item aio_group $callback->(...)
575
576This is a very special aio request: Instead of doing something, it is a
577container for other aio requests, which is useful if you want to bundle
578many requests into a single, composite, request with a definite callback
579and the ability to cancel the whole request with its subrequests.
580
581Returns an object of class L<IO::AIO::GRP>. See its documentation below
582for more info.
583
584Example:
585
586 my $grp = aio_group sub {
587 print "all stats done\n";
588 };
589
590 add $grp
591 (aio_stat ...),
592 (aio_stat ...),
593 ...;
594
595=item aio_nop $callback->()
596
597This is a special request - it does nothing in itself and is only used for
598side effects, such as when you want to add a dummy request to a group so
599that finishing the requests in the group depends on executing the given
600code.
601
602While this request does nothing, it still goes through the execution
603phase and still requires a worker thread. Thus, the callback will not
604be executed immediately but only after other requests in the queue have
605entered their execution phase. This can be used to measure request
606latency.
607
608=item IO::AIO::aio_busy $fractional_seconds, $callback->() *NOT EXPORTED*
609
610Mainly used for debugging and benchmarking, this aio request puts one of
611the request workers to sleep for the given time.
612
613While it is theoretically handy to have simple I/O scheduling requests
614like sleep and file handle readable/writable, the overhead this creates is
615immense (it blocks a thread for a long time) so do not use this function
616except to put your application under artificial I/O pressure.
617
194=back 618=back
195 619
620=head2 IO::AIO::REQ CLASS
621
622All non-aggregate C<aio_*> functions return an object of this class when
623called in non-void context.
624
625=over 4
626
627=item cancel $req
628
629Cancels the request, if possible. Has the effect of skipping execution
630when entering the B<execute> state and skipping calling the callback when
631entering the the B<result> state, but will leave the request otherwise
632untouched. That means that requests that currently execute will not be
633stopped and resources held by the request will not be freed prematurely.
634
635=item cb $req $callback->(...)
636
637Replace (or simply set) the callback registered to the request.
638
639=back
640
641=head2 IO::AIO::GRP CLASS
642
643This class is a subclass of L<IO::AIO::REQ>, so all its methods apply to
644objects of this class, too.
645
646A IO::AIO::GRP object is a special request that can contain multiple other
647aio requests.
648
649You create one by calling the C<aio_group> constructing function with a
650callback that will be called when all contained requests have entered the
651C<done> state:
652
653 my $grp = aio_group sub {
654 print "all requests are done\n";
655 };
656
657You add requests by calling the C<add> method with one or more
658C<IO::AIO::REQ> objects:
659
660 $grp->add (aio_unlink "...");
661
662 add $grp aio_stat "...", sub {
663 $_[0] or return $grp->result ("error");
664
665 # add another request dynamically, if first succeeded
666 add $grp aio_open "...", sub {
667 $grp->result ("ok");
668 };
669 };
670
671This makes it very easy to create composite requests (see the source of
672C<aio_move> for an application) that work and feel like simple requests.
673
674=over 4
675
676=item * The IO::AIO::GRP objects will be cleaned up during calls to
677C<IO::AIO::poll_cb>, just like any other request.
678
679=item * They can be canceled like any other request. Canceling will cancel not
680only the request itself, but also all requests it contains.
681
682=item * They can also can also be added to other IO::AIO::GRP objects.
683
684=item * You must not add requests to a group from within the group callback (or
685any later time).
686
687=back
688
689Their lifetime, simplified, looks like this: when they are empty, they
690will finish very quickly. If they contain only requests that are in the
691C<done> state, they will also finish. Otherwise they will continue to
692exist.
693
694That means after creating a group you have some time to add requests. And
695in the callbacks of those requests, you can add further requests to the
696group. And only when all those requests have finished will the the group
697itself finish.
698
699=over 4
700
701=item add $grp ...
702
703=item $grp->add (...)
704
705Add one or more requests to the group. Any type of L<IO::AIO::REQ> can
706be added, including other groups, as long as you do not create circular
707dependencies.
708
709Returns all its arguments.
710
711=item $grp->cancel_subs
712
713Cancel all subrequests and clears any feeder, but not the group request
714itself. Useful when you queued a lot of events but got a result early.
715
716=item $grp->result (...)
717
718Set the result value(s) that will be passed to the group callback when all
719subrequests have finished. By default, no argument will be passed.
720
721=item feed $grp $callback->($grp)
722
723Sets a feeder/generator on this group: every group can have an attached
724generator that generates requests if idle. The idea behind this is that,
725although you could just queue as many requests as you want in a group,
726this might starve other requests for a potentially long time. For
727example, C<aio_scandir> might generate hundreds of thousands C<aio_stat>
728requests, delaying any later requests for a long time.
729
730To avoid this, and allow incremental generation of requests, you can
731instead a group and set a feeder on it that generates those requests. The
732feed callback will be called whenever there are few enough (see C<limit>,
733below) requests active in the group itself and is expected to queue more
734requests.
735
736The feed callback can queue as many requests as it likes (i.e. C<add> does
737not impose any limits).
738
739If the feed does not queue more requests when called, it will be
740automatically removed from the group.
741
742If the feed limit is C<0>, it will be set to C<2> automatically.
743
744Example:
745
746 # stat all files in @files, but only ever use four aio requests concurrently:
747
748 my $grp = aio_group sub { print "finished\n" };
749 limit $grp 4;
750 feed $grp sub {
751 my $file = pop @files
752 or return;
753
754 add $grp aio_stat $file, sub { ... };
755 };
756
757=item limit $grp $num
758
759Sets the feeder limit for the group: The feeder will be called whenever
760the group contains less than this many requests.
761
762Setting the limit to C<0> will pause the feeding process.
763
764=back
765
196=head2 SUPPORT FUNCTIONS 766=head2 SUPPORT FUNCTIONS
197 767
198=over 4 768=over 4
199 769
200=item $fileno = IO::AIO::poll_fileno 770=item $fileno = IO::AIO::poll_fileno
201 771
202Return the I<request result pipe filehandle>. This filehandle must be 772Return the I<request result pipe file descriptor>. This filehandle must be
203polled for reading by some mechanism outside this module (e.g. Event 773polled for reading by some mechanism outside this module (e.g. Event or
204or select, see below). If the pipe becomes readable you have to call 774select, see below or the SYNOPSIS). If the pipe becomes readable you have
205C<poll_cb> to check the results. 775to call C<poll_cb> to check the results.
206 776
207See C<poll_cb> for an example. 777See C<poll_cb> for an example.
208 778
209=item IO::AIO::poll_cb 779=item IO::AIO::poll_cb
210 780
211Process all outstanding events on the result pipe. You have to call this 781Process all outstanding events on the result pipe. You have to call this
212regularly. Returns the number of events processed. Returns immediately 782regularly. Returns the number of events processed. Returns immediately
213when no events are outstanding. 783when no events are outstanding.
214 784
215You can use Event to multiplex, e.g.: 785Example: Install an Event watcher that automatically calls
786IO::AIO::poll_cb with high priority:
216 787
217 Event->io (fd => IO::AIO::poll_fileno, 788 Event->io (fd => IO::AIO::poll_fileno,
218 poll => 'r', async => 1, 789 poll => 'r', async => 1,
219 cb => \&IO::AIO::poll_cb); 790 cb => \&IO::AIO::poll_cb);
220 791
221=item IO::AIO::poll_wait 792=item IO::AIO::poll_wait
222 793
223Wait till the result filehandle becomes ready for reading (simply does a 794Wait till the result filehandle becomes ready for reading (simply does a
224select on the filehandle. This is useful if you want to synchronously wait 795C<select> on the filehandle. This is useful if you want to synchronously wait
225for some requests to finish). 796for some requests to finish).
226 797
227See C<nreqs> for an example. 798See C<nreqs> for an example.
228 799
229=item IO::AIO::nreqs 800=item IO::AIO::nreqs
230 801
231Returns the number of requests currently outstanding. 802Returns the number of requests currently outstanding (i.e. for which their
803callback has not been invoked yet).
232 804
233Example: wait till there are no outstanding requests anymore: 805Example: wait till there are no outstanding requests anymore:
234 806
235 IO::AIO::poll_wait, IO::AIO::poll_cb 807 IO::AIO::poll_wait, IO::AIO::poll_cb
236 while IO::AIO::nreqs; 808 while IO::AIO::nreqs;
237 809
238=item IO::AIO::flush 810=item IO::AIO::flush
239 811
240Wait till all outstanding AIO requests have been handled. 812Wait till all outstanding AIO requests have been handled.
241 813
814Strictly equivalent to:
815
816 IO::AIO::poll_wait, IO::AIO::poll_cb
817 while IO::AIO::nreqs;
818
819=item IO::AIO::poll
820
821Waits until some requests have been handled.
822
823Strictly equivalent to:
824
825 IO::AIO::poll_wait, IO::AIO::poll_cb
826 if IO::AIO::nreqs;
827
242=item IO::AIO::min_parallel $nthreads 828=item IO::AIO::min_parallel $nthreads
243 829
244Set the minimum number of AIO threads to C<$nthreads>. The default is 830Set the minimum number of AIO threads to C<$nthreads>. The current
245C<1>, which means a single asynchronous operation can be done at one time 831default is C<8>, which means eight asynchronous operations can execute
246(the number of outstanding operations, however, is unlimited). 832concurrently at any one time (the number of outstanding requests,
833however, is unlimited).
247 834
835IO::AIO starts threads only on demand, when an AIO request is queued and
836no free thread exists.
837
248It is recommended to keep the number of threads low, as some Linux 838It is recommended to keep the number of threads relatively low, as some
249kernel versions will scale negatively with the number of threads (higher 839Linux kernel versions will scale negatively with the number of threads
250parallelity => MUCH higher latency). With current Linux 2.6 versions, 4-32 840(higher parallelity => MUCH higher latency). With current Linux 2.6
251threads should be fine. 841versions, 4-32 threads should be fine.
252 842
253Under normal circumstances you don't need to call this function, as this 843Under most circumstances you don't need to call this function, as the
254module automatically starts some threads (the exact number might change, 844module selects a default that is suitable for low to moderate load.
255and is currently 4).
256 845
257=item IO::AIO::max_parallel $nthreads 846=item IO::AIO::max_parallel $nthreads
258 847
259Sets the maximum number of AIO threads to C<$nthreads>. If more than 848Sets the maximum number of AIO threads to C<$nthreads>. If more than the
260the specified number of threads are currently running, kill them. This 849specified number of threads are currently running, this function kills
261function blocks until the limit is reached. 850them. This function blocks until the limit is reached.
851
852While C<$nthreads> are zero, aio requests get queued but not executed
853until the number of threads has been increased again.
262 854
263This module automatically runs C<max_parallel 0> at program end, to ensure 855This module automatically runs C<max_parallel 0> at program end, to ensure
264that all threads are killed and that there are no outstanding requests. 856that all threads are killed and that there are no outstanding requests.
265 857
266Under normal circumstances you don't need to call this function. 858Under normal circumstances you don't need to call this function.
267 859
268=item $oldnreqs = IO::AIO::max_outstanding $nreqs 860=item $oldnreqs = IO::AIO::max_outstanding $nreqs
269 861
862[REMOVED]
863
864Pre-2.x versions used max_outstanding for a crude request queue length limit.
865
866In 2.x+ you are advised to use a group and a feeder to limit
867concurrency. The max_outstanding feature ran very unstable (endless
868recursions causing segfaults, bad interaction with groups etc.) and was
869removed.
870
871I am deeply sorry, but I am still on the hunt for a good limiting interface.
872
873Original description was as follows:
874
270Sets the maximum number of outstanding requests to C<$nreqs>. If you 875Sets the maximum number of outstanding requests to C<$nreqs>. If you try
271try to queue up more than this number of requests, the caller will block until 876to queue up more than this number of requests, the caller will block until
272some requests have been handled. 877some requests have been handled.
273
274The default is very large, so normally there is no practical limit. If you
275queue up many requests in a loop it it often improves speed if you set
276this to a relatively low number, such as C<100>.
277
278Under normal circumstances you don't need to call this function.
279 878
280=back 879=back
281 880
282=cut 881=cut
283 882
284# support function to convert a fd into a perl filehandle 883# support function to convert a fd into a perl filehandle
285sub _fd2fh { 884sub _fd2fh {
286 return undef if $_[0] < 0; 885 return undef if $_[0] < 0;
287 886
288 # try to be perl5.6-compatible 887 # try to generate nice filehandles
289 local *AIO_FH; 888 my $sym = "IO::AIO::fd#$_[0]";
290 open AIO_FH, "+<&=$_[0]" 889 local *$sym;
890
891 open *$sym, "+<&=$_[0]" # usually works under any unix
892 or open *$sym, "<&=$_[0]" # cygwin needs this
893 or open *$sym, ">&=$_[0]" # or this
291 or return undef; 894 or return undef;
292 895
293 *AIO_FH 896 *$sym
294} 897}
295 898
296min_parallel 4; 899min_parallel 8;
297 900
298END { 901END {
299 max_parallel 0; 902 max_parallel 0;
300} 903}
301 904
3021; 9051;
303 906
907=head2 FORK BEHAVIOUR
908
909This module should do "the right thing" when the process using it forks:
910
911Before the fork, IO::AIO enters a quiescent state where no requests
912can be added in other threads and no results will be processed. After
913the fork the parent simply leaves the quiescent state and continues
914request/result processing, while the child frees the request/result queue
915(so that the requests started before the fork will only be handled in the
916parent). Threads will be started on demand until the limit set in the
917parent process has been reached again.
918
919In short: the parent will, after a short pause, continue as if fork had
920not been called, while the child will act as if IO::AIO has not been used
921yet.
922
923=head2 MEMORY USAGE
924
925Per-request usage:
926
927Each aio request uses - depending on your architecture - around 100-200
928bytes of memory. In addition, stat requests need a stat buffer (possibly
929a few hundred bytes), readdir requires a result buffer and so on. Perl
930scalars and other data passed into aio requests will also be locked and
931will consume memory till the request has entered the done state.
932
933This is now awfully much, so queuing lots of requests is not usually a
934problem.
935
936Per-thread usage:
937
938In the execution phase, some aio requests require more memory for
939temporary buffers, and each thread requires a stack and other data
940structures (usually around 16k-128k, depending on the OS).
941
942=head1 KNOWN BUGS
943
944Known bugs will be fixed in the next release.
945
304=head1 SEE ALSO 946=head1 SEE ALSO
305 947
306L<Coro>, L<Linux::AIO>. 948L<Coro::AIO>.
307 949
308=head1 AUTHOR 950=head1 AUTHOR
309 951
310 Marc Lehmann <schmorp@schmorp.de> 952 Marc Lehmann <schmorp@schmorp.de>
311 http://home.schmorp.de/ 953 http://home.schmorp.de/

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines