Date: Wed, 13 Dec 2000 08:39:22 -0700 From: "Justin T. Gibbs" <gibbs@scsiguy.com> To: John Baldwin <jhb@FreeBSD.ORG> Cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, arch@FreeBSD.ORG Subject: Re: An opaque refcount type Message-ID: <200012131539.eBDFdMs27981@aslan.scsiguy.com> In-Reply-To: Your message of "Tue, 12 Dec 2000 13:06:56 PST." <XFMail.001212130656.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>It's opaque in the sense that a user doesn't know what it is inside it. This >means we can freely change around the implementation. For example, in the >INVARIANTS case it adds in lots of extra checks, but to ensure correctness, it >has to add in a mutex to use. My problem with it is that in the instances where you have to acquire a mutex anyway to manage the data, you will not want to use this interface. So, unlike say the LIST macros, there is no chance for our code to standardize on a single refcount API. -- Justin 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?200012131539.eBDFdMs27981>