Re: [boost] [thread-pool/futures] Explicit yielding

From: Johan Torp (johan.torp_at_[hidden])
Date: 2008-06-09 15:29:37

Kowalke Oliver (QD IT PA AS) wrote:
> 
> For what would be 'task-stealing' be usefull?
> Wouldn't be one task-queue on which worker threads are waiting be
> sufficient?
> Polling of one thread in task-queues of other threads seams to be
> expensive.
> Oliver
> 

Tasks can internally re-submit child tasks and then wait on the child task.
This is probably a quite common usecase, see the paper.

Also, somebody else might start working on your child task. Instead of
waiting for them to complete you could start working on other worker
threads' problems or top-level tasks. This can cause some problems though,
such as unexpected deadlocks.

Johan
-- 
View this message in context: http://www.nabble.com/-thread-pool-futures--Explicit-yielding-tp17606225p17739961.html
Sent from the Boost - Dev mailing list archive at Nabble.com.