From owner-freebsd-threads@FreeBSD.ORG Tue Jan 6 10:18:14 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0258716A4D0 for ; Tue, 6 Jan 2004 10:18:14 -0800 (PST) Received: from msgbas2x.cos.agilent.com (msgbas2x.cos.agilent.com [192.25.240.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 877EB43D48 for ; Tue, 6 Jan 2004 10:18:10 -0800 (PST) (envelope-from earl_chew@agilent.com) Received: from relcos1.cos.agilent.com (relcos1.cos.agilent.com [130.29.152.239]) by msgbas2x.cos.agilent.com (Postfix) with ESMTP id DF5FB6CC2; Tue, 6 Jan 2004 11:18:09 -0700 (MST) Received: from websvr.canada.agilent.com (websvr.canada.agilent.com [141.184.122.102]) by relcos1.cos.agilent.com (Postfix) with ESMTP id DDA7A102; Tue, 6 Jan 2004 11:18:08 -0700 (MST) Received: from agilent.com (dhcp6burnaby.canada.agilent.com [141.184.123.147]) SMKit7.1.1_Agilent) with ESMTP id i06IHdo27989; Tue, 6 Jan 2004 10:17:39 -0800 (PST) Message-ID: <3FFAFBD7.2030601@agilent.com> Date: Tue, 06 Jan 2004 10:17:59 -0800 From: Earl Chew Organization: Agilent Technologies User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Eischen References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-threads@freebsd.org Subject: Re: misc/24641: pthread_rwlock_rdlock can deadlock X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jan 2004 18:18:14 -0000 Daniel Eischen wrote: > Our current implementation is rather simple, but it does > avoid us from having to build in limits as to how many > rwlocks can be owned by a thread or how many threads can > own a rwlock. I'll add this to my TODO list for libkse > but it will come at a bit of a performance & storage > cost and there will have to be some built-in limits. Thanks for the detailed explanation. Earl