Boost logo

Boost :

Subject: Re: [boost] [threadpool] work-stealing support
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2008-09-29 07:24:06

----- Original Message -----
From: <k-oli_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Monday, September 29, 2008 1:01 PM
Subject: Re: [boost] [threadpool] work-stealing support

> Hello Vicente,
> thanks for your response - I'll remove lazy and adaptive strategy and
> release
> the new version in the boost vault soon.
> Please note that the work-stealing is not fork-join as you requested in
> some
> of your previous emails (so please don't be disapointed).

No problem. I 'm looking for the feature not the form.

> For fork-join two possible strategies are possible - one like in JAVA
> (from
> Doug Lea) which blocks in pool::submit() until the main task and its
> sub-tasks are finished - the other solution would require stack switching
> as
> it is provided by the coroutines lib in the vault.
> I would prefere the stack switching solution but it seams to become a
> complex
> implementation.

Yes, I understand. A thread pool on top of the coroutine library is an
excelent idea.



Boost list run by bdawes at, gregod at, cpdaniel at, john at