From owner-freebsd-arch Mon Nov 12 16:20:18 2001 Delivered-To: freebsd-arch@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 8B62137B41B; Mon, 12 Nov 2001 16:20:10 -0800 (PST) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA95611; Mon, 12 Nov 2001 16:10:26 -0800 (PST) Date: Mon, 12 Nov 2001 16:10:25 -0800 (PST) From: Julian Elischer To: Matthew Dillon Cc: John Baldwin , Terry Lambert , Robert Watson , freebsd-arch@FreeBSD.org Subject: Re: cur{thread/proc}, or not. In-Reply-To: <200111122350.fACNojg07127@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 12 Nov 2001, Matthew Dillon wrote: > You want to be very careful not to bloat the concept. We > already have severe bloatage in the mutex code and that has > led to a lot of unnecessary complexity. A huge amount, > in fact. We have so many types of mutexes it makes my > head spin and I'm not very happy about it. Forget about > 'shared' verses 'exclusive'. A reference count is a > reference count, that's all. If you keep the concept > simple you can implement more functionality horizontally > rather then implementing more complexity vertically. > > For example, consider this API for pool mutexes. [...] weren't you just complaining that there were too many kinds of mutex? I'm not sure how this fits under "reference counting API" ANyhow can you explain the idea of a pool mutex more clearly? > > > And there you have it. An utterly simple API of four > routines (refcnt routines and pool routines), with a huge > amount of capability. > > -Matt > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message