Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 97630 invoked by uid 500); 15 Jun 2003 18:28:36 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 97614 invoked from network); 15 Jun 2003 18:28:36 -0000 From: "Marc M. Adkins" To: Subject: RE: read/write lockout Date: Sun, 15 Jun 2003 12:08:55 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 In-Reply-To: Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I have code that uses a rwlock, a mutex, a condition, and an atomic variable to provide something approaching fairness (on W2K, I haven't gotten around to testing this on Linux yet). I can post it if anyone is interested. mma > -----Original Message----- > From: Marc M. Adkins [mailto:mmadki@Doorways.org] > Sent: Thursday, June 12, 2003 4:30 PM > To: dev@apr.apache.org > Subject: read/write lockout > > > On W2K, read/write locks can result in writer starvation. If there are a > lot of readers a writer may never get a chance to lock at all. > I'm assuming > that 'fairness' in this sense is simply not guaranteed by APR. I was > wondering if anyone else had run up against this and how they solved it. > > mma > >