
4 Sep
2015
4 Sep
'15
8:03 p.m.
2015-09-04 22:13 GMT+02:00 Thomas Heller
On 09/04/2015 09:51 PM, Oliver Kowalke wrote:
2015-09-04 21:39 GMT+02:00 Thomas Heller
: The problematic portion in std::mutex/boost::mutex is exactly the missing
mechanism how to yield in the correct way. Even if you implement a mechanism like in the blog post you mentioned, the problem hasn't been solved.
why would be boost::this_fiber::yield() inappropriate?
It's inappropriate for anything not running in a boost fiber execution context.
it is save to call boost::this_fiber::yield() from main(), e.g. each thread has a main-context/main-fiber