From owner-cvs-all Wed Nov 29 10:58: 3 2000 Delivered-To: cvs-all@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id B37DA37B401; Wed, 29 Nov 2000 10:57:58 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp246.osd.bsdi.com [204.216.28.246]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eATIvkC27908; Wed, 29 Nov 2000 10:57:46 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001129105239.N8051@fw.wintelcom.net> Date: Wed, 29 Nov 2000 10:58:03 -0800 (PST) From: John Baldwin To: Alfred Perlstein Subject: Re: cvs commit: src/sys/kern kern_mutex.c Cc: cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Nov-00 Alfred Perlstein wrote: > * John Baldwin [001129 10:41] wrote: >> jhb 2000/11/29 10:41:19 PST >> >> Modified files: >> sys/kern kern_mutex.c >> Log: >> Use an atomic operation with an appropriate memory barrier when releasing >> a contested sleep mutex in the case that at least two processes are >> blocked >> on the contested mutex. > > You remeber the fiasco with the MPlock Matt Dillon went through, are > you sure that we perform barriers when releasing locks on archs that > have loosely ordered memory models? It is done via the atomic operations that contain memory barriers (see atomic(9)) which are MD code and as part of their spec must enforce an appropriate memory barrier. To my knowledge each of ia64, i386, and alpha have compliant atomic operations. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message