|
Boost : |
Subject: Re: [boost] Lock free condition_variable or using shared_lock
From: Niall Douglas (s_sourceforge_at_[hidden])
Date: 2014-07-30 09:24:23
On 29 Jul 2014 at 22:57, Kirk Liberty wrote:
> I'm not too familiar with the mechanisms which underlie mutexs and
> conditionals, which is why I'm asking this question.
>
> Is it possible to modify condition_variable so that wait() can be called on
> shared_lock? The use case would be it is acceptable to release all threads
> waiting on a condition_variable when notify_all() is called. Using a
> unique_lock, every thread who wakes up will then have to obtain the lock
> before proceeding; this being a potential bottleneck.
Doesn't condition_variable_any already do this?
Niall
-- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk