|
Boost Users : |
Subject: [Boost-users] [thread] Reader/Writer starvation
From: Jérémy Coulon (jeremy.coulon_at_[hidden])
Date: 2010-05-14 13:54:04
Hi,
According to the documentation of Boost 1.34 (before the major rewrite
of boost::thread), the read/write lock was offering different scheduling
policies.
Some of those policies were providing a solution to the starvation
problem that usually occurs with this kind of lock.
http://www.boost.org/doc/libs/1_34_1/doc/html/thread/concepts.html#thread.concepts.read-write-scheduling-policies
http://www.boost.org/doc/libs/1_34_1/doc/html/thread/concepts.html#thread.concepts.sheduling-policies
But I don't find any reference to starvation and scheduling policies in
the current Boost documentation (1.37).
So, I am wondering if this starvation problem is solved in the current
boost::thread implementation ?
What scheduling policy is actually the default one ?
Can the documentation be improved ?
Thanks.
Jeremy
Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net