… | |
… | |
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.2; |
68 | $VERSION = 1.5; |
69 | |
69 | |
70 | @EXPORT = qw(aio_read aio_write aio_open aio_close aio_stat aio_lstat aio_unlink |
70 | @EXPORT = qw(aio_read aio_write aio_open aio_close aio_stat aio_lstat aio_unlink |
71 | aio_rmdir aio_symlink aio_fsync aio_fdatasync aio_readahead); |
71 | aio_rmdir aio_symlink aio_fsync aio_fdatasync aio_readahead); |
72 | @EXPORT_OK = qw(poll_fileno poll_cb min_parallel max_parallel max_outstanding nreqs); |
72 | @EXPORT_OK = qw(poll_fileno poll_cb min_parallel max_parallel max_outstanding nreqs); |
73 | |
73 | |
… | |
… | |
287 | IO::AIO::poll_wait, IO::AIO::poll_cb |
287 | IO::AIO::poll_wait, IO::AIO::poll_cb |
288 | if IO::AIO::nreqs; |
288 | if IO::AIO::nreqs; |
289 | |
289 | |
290 | =item IO::AIO::min_parallel $nthreads |
290 | =item IO::AIO::min_parallel $nthreads |
291 | |
291 | |
292 | Set the minimum number of AIO threads to C<$nthreads>. The default is |
292 | Set the minimum number of AIO threads to C<$nthreads>. The current default |
293 | C<1>, which means a single asynchronous operation can be done at one time |
293 | is C<4>, which means four asynchronous operations can be done at one time |
294 | (the number of outstanding operations, however, is unlimited). |
294 | (the number of outstanding operations, however, is unlimited). |
|
|
295 | |
|
|
296 | IO::AIO starts threads only on demand, when an AIO request is queued and |
|
|
297 | no free thread exists. |
295 | |
298 | |
296 | It is recommended to keep the number of threads low, as some Linux |
299 | It is recommended to keep the number of threads low, as some Linux |
297 | kernel versions will scale negatively with the number of threads (higher |
300 | kernel versions will scale negatively with the number of threads (higher |
298 | parallelity => MUCH higher latency). With current Linux 2.6 versions, 4-32 |
301 | parallelity => MUCH higher latency). With current Linux 2.6 versions, 4-32 |
299 | threads should be fine. |
302 | threads should be fine. |
300 | |
303 | |
301 | Under normal circumstances you don't need to call this function, as this |
304 | Under most circumstances you don't need to call this function, as the |
302 | module automatically starts some threads (the exact number might change, |
305 | module selects a default that is suitable for low to moderate load. |
303 | and is currently 4). |
|
|
304 | |
306 | |
305 | =item IO::AIO::max_parallel $nthreads |
307 | =item IO::AIO::max_parallel $nthreads |
306 | |
308 | |
307 | Sets the maximum number of AIO threads to C<$nthreads>. If more than |
309 | Sets the maximum number of AIO threads to C<$nthreads>. If more than the |
308 | the specified number of threads are currently running, kill them. This |
310 | specified number of threads are currently running, this function kills |
309 | function blocks until the limit is reached. |
311 | them. This function blocks until the limit is reached. |
|
|
312 | |
|
|
313 | While C<$nthreads> are zero, aio requests get queued but not executed |
|
|
314 | until the number of threads has been increased again. |
310 | |
315 | |
311 | This module automatically runs C<max_parallel 0> at program end, to ensure |
316 | This module automatically runs C<max_parallel 0> at program end, to ensure |
312 | that all threads are killed and that there are no outstanding requests. |
317 | that all threads are killed and that there are no outstanding requests. |
313 | |
318 | |
314 | Under normal circumstances you don't need to call this function. |
319 | Under normal circumstances you don't need to call this function. |
… | |
… | |
318 | Sets the maximum number of outstanding requests to C<$nreqs>. If you |
323 | Sets the maximum number of outstanding requests to C<$nreqs>. If you |
319 | try to queue up more than this number of requests, the caller will block until |
324 | try to queue up more than this number of requests, the caller will block until |
320 | some requests have been handled. |
325 | some requests have been handled. |
321 | |
326 | |
322 | The default is very large, so normally there is no practical limit. If you |
327 | The default is very large, so normally there is no practical limit. If you |
323 | queue up many requests in a loop it it often improves speed if you set |
328 | queue up many requests in a loop it often improves speed if you set |
324 | this to a relatively low number, such as C<100>. |
329 | this to a relatively low number, such as C<100>. |
325 | |
330 | |
326 | Under normal circumstances you don't need to call this function. |
331 | Under normal circumstances you don't need to call this function. |
327 | |
332 | |
328 | =back |
333 | =back |
… | |
… | |
353 | |
358 | |
354 | 1; |
359 | 1; |
355 | |
360 | |
356 | =head2 FORK BEHAVIOUR |
361 | =head2 FORK BEHAVIOUR |
357 | |
362 | |
358 | Before the fork IO::AIO enters a quiescent state where no requests can be |
363 | Before the fork, IO::AIO enters a quiescent state where no requests |
359 | added in other threads and no results will be processed. After the fork |
364 | can be added in other threads and no results will be processed. After |
360 | the parent simply leaves the quiescent state and continues request/result |
365 | the fork the parent simply leaves the quiescent state and continues |
361 | processing, while the child clears the request/result queue and starts the |
366 | request/result processing, while the child clears the request/result |
362 | same number of threads as were in use by the parent. |
367 | queue (so the requests started before the fork will only be handled in |
|
|
368 | the parent). Threats will be started on demand until the limit ste in the |
|
|
369 | parent process has been reached again. |
363 | |
370 | |
364 | =head1 SEE ALSO |
371 | =head1 SEE ALSO |
365 | |
372 | |
366 | L<Coro>, L<Linux::AIO>. |
373 | L<Coro>, L<Linux::AIO>. |
367 | |
374 | |