… | |
… | |
63 | use base 'Exporter'; |
63 | use base 'Exporter'; |
64 | |
64 | |
65 | use Fcntl (); |
65 | use Fcntl (); |
66 | |
66 | |
67 | BEGIN { |
67 | BEGIN { |
68 | $VERSION = 1.1; |
68 | $VERSION = 1.6; |
69 | |
69 | |
70 | @EXPORT = qw(aio_read aio_write aio_open aio_close aio_stat aio_lstat aio_unlink |
70 | @EXPORT = qw(aio_sendfile aio_read aio_write aio_open aio_close stat |
|
|
71 | aio_aio_lstat aio_unlink aio_rmdir aio_readdir aio_symlink |
71 | aio_rmdir aio_symlink aio_fsync aio_fdatasync aio_readahead); |
72 | aio_fsync aio_fdatasync aio_readahead); |
72 | @EXPORT_OK = qw(poll_fileno poll_cb min_parallel max_parallel max_outstanding nreqs); |
73 | @EXPORT_OK = qw(poll_fileno poll_cb min_parallel max_parallel |
|
|
74 | max_outstanding nreqs); |
73 | |
75 | |
74 | require XSLoader; |
76 | require XSLoader; |
75 | XSLoader::load IO::AIO, $VERSION; |
77 | XSLoader::load IO::AIO, $VERSION; |
76 | } |
78 | } |
77 | |
79 | |
… | |
… | |
88 | syscall has been executed asynchronously. |
90 | syscall has been executed asynchronously. |
89 | |
91 | |
90 | All functions expecting a filehandle keep a copy of the filehandle |
92 | All functions expecting a filehandle keep a copy of the filehandle |
91 | internally until the request has finished. |
93 | internally until the request has finished. |
92 | |
94 | |
93 | The filenames you pass to these routines I<must> be absolute. The reason |
95 | The pathnames you pass to these routines I<must> be absolute and |
94 | for this is that at the time the request is being executed, the current |
96 | encoded in byte form. The reason for the former is that at the time the |
95 | working directory could have changed. Alternatively, you can make sure |
97 | request is being executed, the current working directory could have |
96 | that you never change the current working directory. |
98 | changed. Alternatively, you can make sure that you never change the |
|
|
99 | current working directory. |
|
|
100 | |
|
|
101 | To encode pathnames to byte form, either make sure you either: a) |
|
|
102 | always pass in filenames you got from outside (command line, readdir |
|
|
103 | etc.), b) are ASCII or ISO 8859-1, c) use the Encode module and encode |
|
|
104 | your pathnames to the locale (or other) encoding in effect in the user |
|
|
105 | environment, d) use Glib::filename_from_unicode on unicode filenames or e) |
|
|
106 | use something else. |
97 | |
107 | |
98 | =over 4 |
108 | =over 4 |
99 | |
109 | |
100 | =item aio_open $pathname, $flags, $mode, $callback |
110 | =item aio_open $pathname, $flags, $mode, $callback |
101 | |
111 | |
… | |
… | |
142 | Reads or writes C<length> bytes from the specified C<fh> and C<offset> |
152 | Reads or writes C<length> bytes from the specified C<fh> and C<offset> |
143 | into the scalar given by C<data> and offset C<dataoffset> and calls the |
153 | into the scalar given by C<data> and offset C<dataoffset> and calls the |
144 | callback without the actual number of bytes read (or -1 on error, just |
154 | callback without the actual number of bytes read (or -1 on error, just |
145 | like the syscall). |
155 | like the syscall). |
146 | |
156 | |
|
|
157 | The C<$data> scalar I<MUST NOT> be modified in any way while the request |
|
|
158 | is outstanding. Modifying it can result in segfaults or WW3 (if the |
|
|
159 | necessary/optional hardware is installed). |
|
|
160 | |
147 | Example: Read 15 bytes at offset 7 into scalar C<$buffer>, starting at |
161 | Example: Read 15 bytes at offset 7 into scalar C<$buffer>, starting at |
148 | offset C<0> within the scalar: |
162 | offset C<0> within the scalar: |
149 | |
163 | |
150 | aio_read $fh, 7, 15, $buffer, 0, sub { |
164 | aio_read $fh, 7, 15, $buffer, 0, sub { |
151 | $_[0] > 0 or die "read error: $!"; |
165 | $_[0] > 0 or die "read error: $!"; |
152 | print "read $_[0] bytes: <$buffer>\n"; |
166 | print "read $_[0] bytes: <$buffer>\n"; |
153 | }; |
167 | }; |
|
|
168 | |
|
|
169 | =item aio_sendfile $out_fh, $in_fh, $in_offset, $length, $callback |
|
|
170 | |
|
|
171 | Tries to copy C<$length> bytes from C<$in_fh> to C<$out_fh>. It starts |
|
|
172 | reading at byte offset C<$in_offset>, and starts writing at the current |
|
|
173 | file offset of C<$out_fh>. Because of that, it is not safe to issue more |
|
|
174 | than one C<aio_sendfile> per C<$out_fh>, as they will interfere with each |
|
|
175 | other. |
|
|
176 | |
|
|
177 | This call tries to make use of a native C<sendfile> syscall to provide |
|
|
178 | zero-copy operation. For this to work, C<$out_fh> should refer to a |
|
|
179 | socket, and C<$in_fh> should refer to mmap'able file. |
|
|
180 | |
|
|
181 | If the native sendfile call fails or is not implemented, it will be |
|
|
182 | emulated, so you can call C<aio_sendfile> on any type of filehandle |
|
|
183 | regardless of the limitations of the operating system. |
|
|
184 | |
|
|
185 | Please note, however, that C<aio_sendfile> can read more bytes from |
|
|
186 | C<$in_fh> than are written, and there is no way to find out how many |
|
|
187 | bytes have been read from C<aio_sendfile> alone, as C<aio_sendfile> only |
|
|
188 | provides the number of bytes written to C<$out_fh>. Only if the result |
|
|
189 | value equals C<$length> one can assume that C<$length> bytes have been |
|
|
190 | read. |
154 | |
191 | |
155 | =item aio_readahead $fh,$offset,$length, $callback |
192 | =item aio_readahead $fh,$offset,$length, $callback |
156 | |
193 | |
157 | C<aio_readahead> populates the page cache with data from a file so that |
194 | C<aio_readahead> populates the page cache with data from a file so that |
158 | subsequent reads from that file will not block on disk I/O. The C<$offset> |
195 | subsequent reads from that file will not block on disk I/O. The C<$offset> |
… | |
… | |
196 | =item aio_rmdir $pathname, $callback |
233 | =item aio_rmdir $pathname, $callback |
197 | |
234 | |
198 | Asynchronously rmdir (delete) a directory and call the callback with the |
235 | Asynchronously rmdir (delete) a directory and call the callback with the |
199 | result code. |
236 | result code. |
200 | |
237 | |
|
|
238 | =item aio_readdir $pathname $callback |
|
|
239 | |
|
|
240 | Unlike the POSIX call of the same name, C<aio_readdir> reads an entire |
|
|
241 | directory (i.e. opendir + readdir + closedir). The entries will not be |
|
|
242 | sorted, and will B<NOT> include the C<.> and C<..> entries. |
|
|
243 | |
|
|
244 | The callback a single argument which is either C<undef> or an array-ref |
|
|
245 | with the filenames. |
|
|
246 | |
201 | =item aio_fsync $fh, $callback |
247 | =item aio_fsync $fh, $callback |
202 | |
248 | |
203 | Asynchronously call fsync on the given filehandle and call the callback |
249 | Asynchronously call fsync on the given filehandle and call the callback |
204 | with the fsync result code. |
250 | with the fsync result code. |
205 | |
251 | |
… | |
… | |
275 | IO::AIO::poll_wait, IO::AIO::poll_cb |
321 | IO::AIO::poll_wait, IO::AIO::poll_cb |
276 | if IO::AIO::nreqs; |
322 | if IO::AIO::nreqs; |
277 | |
323 | |
278 | =item IO::AIO::min_parallel $nthreads |
324 | =item IO::AIO::min_parallel $nthreads |
279 | |
325 | |
280 | Set the minimum number of AIO threads to C<$nthreads>. The default is |
326 | Set the minimum number of AIO threads to C<$nthreads>. The current default |
281 | C<1>, which means a single asynchronous operation can be done at one time |
327 | is C<4>, which means four asynchronous operations can be done at one time |
282 | (the number of outstanding operations, however, is unlimited). |
328 | (the number of outstanding operations, however, is unlimited). |
|
|
329 | |
|
|
330 | IO::AIO starts threads only on demand, when an AIO request is queued and |
|
|
331 | no free thread exists. |
283 | |
332 | |
284 | It is recommended to keep the number of threads low, as some Linux |
333 | It is recommended to keep the number of threads low, as some Linux |
285 | kernel versions will scale negatively with the number of threads (higher |
334 | kernel versions will scale negatively with the number of threads (higher |
286 | parallelity => MUCH higher latency). With current Linux 2.6 versions, 4-32 |
335 | parallelity => MUCH higher latency). With current Linux 2.6 versions, 4-32 |
287 | threads should be fine. |
336 | threads should be fine. |
288 | |
337 | |
289 | Under normal circumstances you don't need to call this function, as this |
338 | Under most circumstances you don't need to call this function, as the |
290 | module automatically starts some threads (the exact number might change, |
339 | module selects a default that is suitable for low to moderate load. |
291 | and is currently 4). |
|
|
292 | |
340 | |
293 | =item IO::AIO::max_parallel $nthreads |
341 | =item IO::AIO::max_parallel $nthreads |
294 | |
342 | |
295 | Sets the maximum number of AIO threads to C<$nthreads>. If more than |
343 | Sets the maximum number of AIO threads to C<$nthreads>. If more than the |
296 | the specified number of threads are currently running, kill them. This |
344 | specified number of threads are currently running, this function kills |
297 | function blocks until the limit is reached. |
345 | them. This function blocks until the limit is reached. |
|
|
346 | |
|
|
347 | While C<$nthreads> are zero, aio requests get queued but not executed |
|
|
348 | until the number of threads has been increased again. |
298 | |
349 | |
299 | This module automatically runs C<max_parallel 0> at program end, to ensure |
350 | This module automatically runs C<max_parallel 0> at program end, to ensure |
300 | that all threads are killed and that there are no outstanding requests. |
351 | that all threads are killed and that there are no outstanding requests. |
301 | |
352 | |
302 | Under normal circumstances you don't need to call this function. |
353 | Under normal circumstances you don't need to call this function. |
… | |
… | |
306 | Sets the maximum number of outstanding requests to C<$nreqs>. If you |
357 | Sets the maximum number of outstanding requests to C<$nreqs>. If you |
307 | try to queue up more than this number of requests, the caller will block until |
358 | try to queue up more than this number of requests, the caller will block until |
308 | some requests have been handled. |
359 | some requests have been handled. |
309 | |
360 | |
310 | The default is very large, so normally there is no practical limit. If you |
361 | The default is very large, so normally there is no practical limit. If you |
311 | queue up many requests in a loop it it often improves speed if you set |
362 | queue up many requests in a loop it often improves speed if you set |
312 | this to a relatively low number, such as C<100>. |
363 | this to a relatively low number, such as C<100>. |
313 | |
364 | |
314 | Under normal circumstances you don't need to call this function. |
365 | Under normal circumstances you don't need to call this function. |
315 | |
366 | |
316 | =back |
367 | =back |
… | |
… | |
341 | |
392 | |
342 | 1; |
393 | 1; |
343 | |
394 | |
344 | =head2 FORK BEHAVIOUR |
395 | =head2 FORK BEHAVIOUR |
345 | |
396 | |
346 | IO::AIO handles all outstanding AIO requests before the fork, destroys all |
397 | Before the fork, IO::AIO enters a quiescent state where no requests |
347 | AIO threads, and recreates them in both the parent and the child after the |
398 | can be added in other threads and no results will be processed. After |
348 | fork. |
399 | the fork the parent simply leaves the quiescent state and continues |
349 | |
400 | request/result processing, while the child clears the request/result |
|
|
401 | queue (so the requests started before the fork will only be handled in |
|
|
402 | the parent). Threats will be started on demand until the limit ste in the |
|
|
403 | parent process has been reached again. |
350 | |
404 | |
351 | =head1 SEE ALSO |
405 | =head1 SEE ALSO |
352 | |
406 | |
353 | L<Coro>, L<Linux::AIO>. |
407 | L<Coro>, L<Linux::AIO>. |
354 | |
408 | |