From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17022 invoked by alias); 8 Dec 2005 15:09:23 -0000 Received: (qmail 17015 invoked by uid 22791); 8 Dec 2005 15:09:23 -0000 X-Spam-Check-By: sourceware.org Received: from outhub3.tibco.com (HELO outhub3.tibco.com) (63.100.100.166) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 08 Dec 2005 15:09:22 +0000 Received: from na-h-inhub1.tibco.com (na-h-inhub1 [10.106.128.33]) by outhub3.tibco.com (8.12.10/8.12.9) with ESMTP id jB8F7VhD008010; Thu, 8 Dec 2005 07:07:31 -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 jB8F7UNQ014582; Thu, 8 Dec 2005 07:07:30 -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: RE: Good Algorithm for "Multiple Readers"/"Multiple Writers" Date: Thu, 08 Dec 2005 15:09:00 -0000 Message-ID: From: "Stephen Croall" To: "Evstiounin, Mikhail" , , 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/msg00141.txt.bz2 This is the best alogorithm I have seen so far:=20 http://www.cs.umd.edu/~hollings/cs412/s96/synch/synch1.html=20 --=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 -----Original Message----- From: Evstiounin, Mikhail [mailto:Mikhail.Evstiounin@ca.com]=20 Sent: 08 December 2005 15:03 To: Stephen Croall; RKindred@SwRI.edu; pthreads-win32@sources.redhat.com Subject: RE: Good Algorithm for "Multiple Readers"/"Multiple Writers" Frankly, how do you think it is possible to be able to write to resource in parallel and keep integrity of this resource all the time? There is a reason why writer gains an exclusive lock on a resource.=20 -----Original Message----- From: pthreads-win32-owner@sourceware.org [mailto:pthreads-win32-owner@sourceware.org] On Behalf Of Stephen Croall Sent: Thursday, December 08, 2005 9:49 AM To: RKindred@SwRI.edu; pthreads-win32@sources.redhat.com Subject: RE: Good Algorithm for "Multiple Readers"/"Multiple Writers" But that is for "single writer"/"multiple readers" - it doesn't support multiple writers. 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 -----Original Message----- From: Robert Kindred [mailto:RKindred@SwRI.edu]=20 Sent: 08 December 2005 14:47 To: Stephen Croall; pthreads-win32@sources.redhat.com Subject: RE: Good Algorithm for "Multiple Readers"/"Multiple Writers" I use the pthread_rwlock_t in pthreads-win32, and it works fine. Robert Kindred > -----Original Message----- > From: pthreads-win32-owner@sourceware.org > [mailto:pthreads-win32-owner@sourceware.org]On Behalf Of Stephen Croall > Sent: Thursday, December 08, 2005 3:10 AM > To: pthreads-win32@sources.redhat.com > Subject: Good Algorithm for "Multiple Readers"/"Multiple Writers" >=20 >=20 > Hi, >=20 > I'm looking for a good, performant algorithm for "multiple > reader"/"multiple writer" locking. >=20 > 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. >=20 > 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. >=20 > Cheers, Steve. >=20 > --=20 >=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 >=20