| … | |
… | |
| 384 | |
384 | |
| 385 | Future versions of this module might do this automatically. |
385 | Future versions of this module might do this automatically. |
| 386 | |
386 | |
| 387 | =back |
387 | =back |
| 388 | |
388 | |
| 389 | =head1 BUGS |
389 | =head1 BUGS & LIMITATIONS |
| 390 | |
390 | |
| 391 | =over 4 |
391 | =over 4 |
| 392 | |
392 | |
| 393 | =item (OS-) threads are never released |
393 | =item (OS-) threads are never released |
| 394 | |
394 | |
| … | |
… | |
| 401 | GNU/Linux + glibc, each thread takes about 8KiB of userspace memory + |
401 | GNU/Linux + glibc, each thread takes about 8KiB of userspace memory + |
| 402 | whatever the kernel needs (probably less than 8KiB). |
402 | whatever the kernel needs (probably less than 8KiB). |
| 403 | |
403 | |
| 404 | Future versions will likely lift this limitation. |
404 | Future versions will likely lift this limitation. |
| 405 | |
405 | |
| 406 | =item AnyEvent is initalised at module load time |
406 | =item The enable_times feature of Coro is messed up |
| 407 | |
407 | |
| 408 | AnyEvent is initialised on module load, as opposed to at a later time. |
408 | The enable_times feature uses the per-thread timer to measure per-thread |
| 409 | |
409 | execution time, but since Coro::Multicore runs threads on different |
| 410 | Future versions will likely change this. |
410 | pthreads it will get the wrong times. Real times are not affected. |
| 411 | |
411 | |
| 412 | =back |
412 | =back |
| 413 | |
413 | |
| 414 | =head1 AUTHOR |
414 | =head1 AUTHOR |
| 415 | |
415 | |
