[concurrency-interest] Fork and and timed get

Romain Colle rco at quartetfs.com
Fri Nov 29 08:33:51 EST 2013


On Fri, Nov 29, 2013 at 2:05 PM, √iktor Ҡlang <viktor.klang at gmail.com>wrote:

>  Agreed. However, I'd really like the thread management to be handled by
>> the pool, exactly the way it is done today after trying to help the task in
>> get():
>> tryCompensate() / set SIGNAL / wait / incrementActiveCount().
>> This is in fact doing exactly the managed block that Viktor suggested.
>>
>
> Isn't there a difference in that it doesn't spawn an additional thread?
>

I would say it's exactly the same thing since managedBlock does:
tryCompensate()
/ block / incrementActiveCount()
An extra thread should be created (if possible) to compensate for the
thread doing the blocking get() through the tryCompensate().

Cheers,

-- 
Romain Colle
R&D Project Manager
QuartetFS
2 rue Jean Lantier, 75001 Paris, France
http://www.quartetfs.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20131129/aadb1f7b/attachment.html>


More information about the Concurrency-interest mailing list