➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author christian.heimes
Recipients Sebastian.Noack, asvetlov, christian.heimes, jyasskin, kristjan.jonsson, mklauber, pitrou, sbt
Date 2012-10-01.13:39:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1349098794.85.0.325696357688.issue8800@psf.upfronthosting.co.za>
In-reply-to
Content 
A RW lock is part of POSIX threads [1]. It's usually a good idea to either use POSIX functions or to mimic their behavior. After all POSIX is an industry standard.

Boost and Java have several lock and rw lock implementations. Wikipedia [2] is a good starting point for the various implementations. The page also mentions a seqlock which looks interesting to me as it's fast for few writers with lots of readers.

[1] http://linux.die.net/man/3/pthread_rwlock_init 
[2] http://en.wikipedia.org/wiki/Readers%E2%80%93writer_lock
History
Date User Action Args
2012-10-01 13:39:54christian.heimessetrecipients: + christian.heimes, pitrou, kristjan.jonsson, jyasskin, asvetlov, sbt, mklauber, Sebastian.Noack
2012-10-01 13:39:54christian.heimessetmessageid: <1349098794.85.0.325696357688.issue8800@psf.upfronthosting.co.za>
2012-10-01 13:39:54christian.heimeslinkissue8800 messages
2012-10-01 13:39:54christian.heimescreate