From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7413 invoked by alias); 8 Dec 2005 09:09:48 -0000 Received: (qmail 7399 invoked by uid 22791); 8 Dec 2005 09:09:47 -0000 X-Spam-Check-By: sourceware.org Received: from outhub4.tibco.com (HELO outhub4.tibco.com) (63.100.100.170) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 08 Dec 2005 09:09:46 +0000 Received: from na-h-inhub1.tibco.com (tibco-5.tibco.com [63.100.100.5]) by outhub4.tibco.com (8.12.10/8.12.9) with ESMTP id jB899hGL019448 for ; Thu, 8 Dec 2005 01:09:43 -0800 (PST) Received: from NA-PA-VBE01.na.tibco.com (na-pa-be01.tibco.com [10.106.136.121]) by na-h-inhub1.tibco.com (8.12.10/8.12.10) with ESMTP id jB899hNQ015167 for ; Thu, 8 Dec 2005 01:09:43 -0800 (PST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Good Algorithm for "Multiple Readers"/"Multiple Writers" Date: Thu, 08 Dec 2005 09:09:00 -0000 Message-ID: From: "Stephen Croall" To: X-IsSubscribed: yes Mailing-List: contact pthreads-win32-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sourceware.org X-SW-Source: 2005/txt/msg00129.txt.bz2 Hi, I'm looking for a good, performant algorithm for "multiple reader"/"multiple writer" locking. I'm in the process of writing my own but I would rather not fall into any common pitfalls, especially since performance & scalability are critical. Is anyone aware of whether POSIX implements this type of lock? I can't seem to find any reference to it in the POSIX documentation. Cheers, Steve. --=20 J. Senior Software Engineer, Tibco Software Ltd. T. +44 (0) 1792 360773 M. +44 (0) 7788 971394 E. scroall@tibco.com W. www.tibco.com