Date: Mon, 12 Nov 2001 16:10:25 -0800 (PST)
From: Julian Elischer <julian@elischer.org>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: John Baldwin <jhb@FreeBSD.org>, Terry Lambert <tlambert2@mindspring.com>, Robert Watson <rwatson@FreeBSD.org>, freebsd-arch@FreeBSD.org
Subject: Re: cur{thread/proc}, or not.
Message-ID: <Pine.BSF.4.21.0111121608240.94926-100000@InterJet.elischer.org>
In-Reply-To: <200111122350.fACNojg07127@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0111121608240.94926-100000>