From owner-freebsd-current Wed Nov 14 15:31:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from mta11.onebox.com (mta11.onebox.com [64.68.76.121]) by hub.freebsd.org (Postfix) with ESMTP id E8DAF37B405 for ; Wed, 14 Nov 2001 15:31:28 -0800 (PST) Received: from onebox.com ([10.1.101.6]) by mta11.onebox.com (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP id <20011114233128.VSPB29441.mta11.onebox.com@onebox.com> for ; Wed, 14 Nov 2001 15:31:28 -0800 Received: from [66.32.40.34] by onebox.com with HTTP; Wed, 14 Nov 2001 15:31:28 -0800 Date: Wed, 14 Nov 2001 15:31:28 -0800 Subject: Re: RE: lock order reversal for today's -CURRENT From: "Glenn Gombert" To: current@FreeBSD.ORG Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Message-Id: <20011114233128.VSPB29441.mta11.onebox.com@onebox.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is there a good , current description of how & why the various mutexe's & conditon variables are used for somewhere?? I see what they are doing in the code, but would like to get the big picture of why they are used in one place (and not another type).. Thanks, Glenn G. > I'm not against the concept of multiple pools, but I'm not really > for it either. The various mutexes are already far too complex > for their own good... look at SX locks, for example. The > struct sx is about 8 times as big as it needs to be to implement > reasonable functionality. I would scrap the upgrade and > downgrade API and I would scrap the condition variables > and go with a simple shared/exclusive counter. > > -Matt > Matthew Dillon > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > __________________________________________________ FREE voicemail, email, and fax...all in one place. Sign Up Now! http://www.onebox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message