11 Jan
2014
11 Jan
'14
5:25 p.m.
Le 11/01/14 18:12, Vicente J. Botet Escriba a écrit :
Le 06/01/14 14:07, Nat Goodspeed a écrit :
Hi all,
The review of Boost.Fiber by Oliver Kowalke begins today, Monday January 6th, and closes Wednesday January 15th.
More question about stealing.
What would be the advantages of using work-stealing at the fiber level instead of using it at the task level?
I wonder if the steel and migrate functions shouldn't be an internal detail of the library and that the library should provide a fiber_pool. I'm wondering also if the algorithm shouldn't be replaced by an enum.
What do you think?
BTW what is the state of a fiber after a steal_from() operation? Vicente