Subject: Re: [boost] [threadpool] new version v12
From: Vicente Botet Escriba (vicente.botet_at_[hidden])
Date: 2008-11-01 14:35:23
> Am Samstag, 1. November 2008 00:53:11 schrieb Michael Marcin:
>> k-oli_at_[hidden] wrote:
>> > Hello,
>> > the new version of Boost.Threadpool depends on Boost.Fiber.
>> What are the benefits of using them in a threadpool?
> Hello Michael,
> using fibers in a threadpool enables fork/join semantics (algorithms which
> recursively splitt an action into smaller sub-actions; forking the
> sub-actions into separate worker threads, so that they run in parallel on
> multiple cores)
IMO, the implementation of the fork/join semantics do not need fibers.
The wait/get functions can call to the thread_pool scheduler without
context-switch. Which are the advantages of using fibers over calling
recursively to the scheduler?
-- View this message in context: http://www.nabble.com/-threadpool--new-version-v12-tp20274374p20283153.html Sent from the Boost - Dev mailing list archive at Nabble.com.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk