11 Jan
2014
11 Jan
'14
6:45 p.m.
2014/1/11 Vicente J. Botet Escriba
What would be the advantages of using work-stealing at the fiber level instead of using it at the task level?
it is very simple because you migate a 'first-class' object, e.g. the fiber already is like a continuation.
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.
fiber-stealing is not required in all cases and it has to be provided by the fiber-scheduler hence it has to be part of the scheduler.
I'm wondering also if the algorithm shouldn't be replaced by an enum.
sorry - I don't get it.