From owner-freebsd-ia64 Wed Oct 10 10:23:54 2001 Delivered-To: freebsd-ia64@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 1A37E37B405; Wed, 10 Oct 2001 10:23:51 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id f9AHNo805885; Wed, 10 Oct 2001 10:23:50 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 10 Oct 2001 10:23:50 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: John Baldwin Subject: RE: rtld -- atomic ops Cc: ia64@FreeBSD.org, Doug Rabson Sender: owner-freebsd-ia64@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org John Baldwin wrote: > > One quick question. Now that we have a MI atomic operation interface one can > get from that includes atomic_cmpset_acq_int(), > atomic_add_acq_int(), and atomic_add_rel_int(), why not use these instead of > re-rolling the atomic operations each time? I realize that do to the quirky > nature of the 386, you would still have to have a hack for the x86 platform, > but at least for 486+ and other arch's you could just use the pre-existent API > so that we only have to code up atomic ops in one place. > > Comments? That would be great, as far as I'm concerned. Note, the reader/writer locks used by the dynamic linker require something resembling an atomic compare and exchange operation. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ia64" in the body of the message