Re: [boost] [thread-pool/futures] Explicit yielding (fork/join)

From: Kowalke Oliver (QD IT PA AS) (Oliver.Kowalke_at_[hidden])
Date: 2008-06-13 05:03:03

> 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.

I did a look in the papers for for/join and work stealing algorithms.
Is it correct that each fork of a subtask would create a new thread (which get joined later)?
If so then this pattern introduces the overhead of thread creation and destruction again.
Some platforms the number of threads pro process are limited (255 on Linux).

I'm wondering why fork/join is so hip?!

Oliver