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