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

From: Johan Torp (johan.torp_at_[hidden])
Date: 2008-06-03 05:09:30

Peter Dimov-5 wrote:
> 
> It can deadlock, but it cannot deadlock unexpectedly. That is, it will not 
> turn code that didn't deadlock into code that deadlocks. Your example:
> -snip-
> already deadlocks without reuse. 
> 

You're right, I didn't see that. 

In a previous post you said "Limiting the reuse to pool threads eliminates
most other (theoretical IMO)
problems.". What theoretical problems has been identified with thread
re-use? 

Does existing threadpools (such as java.util.concurrency.ExecutorService)
offer thread re-use and if so is it considered an success?

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