From owner-freebsd-arch Fri Oct 13 2:26:49 2000 Delivered-To: freebsd-arch@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id D630337B502 for ; Fri, 13 Oct 2000 02:26:47 -0700 (PDT) Received: (from daemon@localhost) by smtp03.primenet.com (8.9.3/8.9.3) id CAA04043; Fri, 13 Oct 2000 02:25:11 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp03.primenet.com, id smtpdAAAIJaW3h; Fri Oct 13 02:25:07 2000 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id CAA23043; Fri, 13 Oct 2000 02:26:41 -0700 (MST) From: Terry Lambert Message-Id: <200010130926.CAA23043@usr09.primenet.com> Subject: Re: we need atomic_t To: bright@wintelcom.net (Alfred Perlstein) Date: Fri, 13 Oct 2000 09:26:41 +0000 (GMT) Cc: tlambert@primenet.com (Terry Lambert), arch@FreeBSD.ORG In-Reply-To: <20001012230807.H272@fw.wintelcom.net> from "Alfred Perlstein" at Oct 12, 2000 11:08:07 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What's annoying me here is that everyone wants atomic_t to > do all these amazing things for which i'm not presenting it > for. All I want it for is: > > 1) refcounting in ucred > 2) refcounting in mbuf > 3) refcounting in uidinfo > 4) providing at least 16 bits of atomically-or/and-able bits for > certain flags structures that I may want to have atomic ops for. > > If anyone has a situation that atomic_t as presented here is > unsuitable for then they are welcome to get off my back and > make up some other magic type to address their problem. Why call it "atomic_t" instead of "long", then? Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message