29 Sep
2008
29 Sep
'08
6:22 a.m.
Anthony Williams escribió:
Yes. The intention was that the free function launch_in_pool would use an implementation-provided global thread pool that would be as smart as the library implementor could manage.
e.g. I have a working prototype for Windows that initially runs one pool thread per CPU. If a pool thread blocks on a future for a pool task it suspends the current task and runs a new task from the pool.
How do you do that? By re-executing the blocking task or using fibers? Joaquín M López Muñoz Telefónica, Investigación y Desarrollo