Re: [Threads-devel] reader/writer locks

From: Anthony Williams (anthony_at_[hidden])
Date: 2007-08-03 10:26:48

"Allen Pulsifer" <pulsifer3_at_[hidden]> writes:

>> I believe that all the code there works. It passes all the 
>> tests on Windows for certain, and I think it passes all the 
>> test on Linux too. When I move it over to trunk I'll verify 
>> that everything works.
>
> Hello Anthony,
>
> Thanks for the reply.
>
> Just to double check, the warning at
> http://www.boost.org/doc/html/boost/read_write_mutex.html said:
>
> "...discussions on the mailing list led to the conclusion that the current
> concepts need to be rethought. In particular the schedulings Inter-Class
> Scheduling Policies are deemed unnecessary. There seems to be common belief
> that a fair scheme suffices."
>
> However, in the file
> http://svn.boost.org/svn/boost/tags/thread_rewrite_1/boost/boost/thread/deta
> il/read_write_scheduling_policy.hpp, I see:

That's the wrong place to look. I didn't read the URL you posted before
closely enough, sorry.

The new implementation is at

http://svn.boost.org/svn/boost/branches/thread_rewrite/boost/boost/thread/

> My question is, do the Scheduling Policies work, or is there any special
> usage restrictions to be aware of?

Scheduling policies are no longer supported. The interface is different to the
old (broken) one --- it is more along the lines of the proposed TR2 interface
with shareable/upgradeable/exclusive locks. One thing I will have to do on the
merge to trunk is update the documentation to describe the new interface.

Anthony
-- 
Anthony Williams
Just Software Solutions Ltd - http://www.justsoftwaresolutions.co.uk
Registered in England, Company Number 5478976.
Registered Office: 15 Carrallack Mews, St Just, Cornwall, TR19 7UL