1 | Revision history for IO::AIO |
1 | Revision history for IO::AIO |
2 | |
2 | |
3 | TODO: better autoconf.pm that can return LIBS etc. |
3 | TODO: better autoconf.pm that can return LIBS etc. |
4 | TODO: aio_cptree/mvtree |
4 | TODO: aio_cptree/mvtree |
5 | TODO: reduce condvar fairness: schedule hot-cache-threads first? |
5 | TODO: reduce condvar fairness: schedule hot-cache-threads first? |
6 | TODO: fix setsig |
|
|
7 | TODO: splice/tee/vmsplice/sync_file_range? (http://kerneltrap.org/node/6505 http://lwn.net/Articles/178199/) |
6 | TODO: splice/tee/vmsplice/sync_file_range? (http://kerneltrap.org/node/6505 http://lwn.net/Articles/178199/) |
|
|
7 | TODO: aio_fcntl, at least for file-locking |
8 | |
8 | |
9 | 2.6 |
9 | 2.61 Wed Apr 16 18:45:02 CEST 2008 |
|
|
10 | - fix treescan output duplication and improve output ordering. |
|
|
11 | also display files given on the commandline. |
|
|
12 | - use a different algorithm for aio_close that is faster |
|
|
13 | and probably has even lower chances of blocking. |
|
|
14 | - do our own stack memory management for threads - linux |
|
|
15 | allocates outrageous amounts of VM (not so bad unless you |
|
|
16 | use mlockall...), which severely limits the number of threads |
|
|
17 | on 32-bit arches: stack size is the larger of PTHREAD_STACK_MIN |
|
|
18 | and 4096 * sizeof (long) (usually this is 16..64k). |
|
|
19 | |
|
|
20 | 2.6 Sun Mar 30 08:28:11 CEST 2008 |
10 | - added aio_sync. |
21 | - added aio_sync. |
11 | - added aio_pathsync. |
22 | - added aio_pathsync. |
|
|
23 | - fix prototypes of (void) functions. |
12 | |
24 | |
13 | 2.51 Sat Oct 6 16:04:54 CEST 2007 |
25 | 2.51 Sat Oct 6 16:04:54 CEST 2007 |
14 | - perlio isn't generally threadsafe, so aio_close could not work reliably. |
26 | - perlio isn't generally threadsafe, so aio_close could not work reliably. |
15 | aio_close now tries a safe hack that might not be that asynchronous |
27 | aio_close now tries a safe hack that might not be that asynchronous |
16 | (see the manpage for details). |
28 | (see the manpage for details). |