From owner-freebsd-alpha  Fri Dec 15 14:42:27 2000
From owner-freebsd-alpha@FreeBSD.ORG  Fri Dec 15 14:42:26 2000
Return-Path: <owner-freebsd-alpha@FreeBSD.ORG>
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8CDA037B402; Fri, 15 Dec 2000 14:42:25 -0800 (PST)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA09308;
	Fri, 15 Dec 2000 17:42:23 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eBFMgNJ68797;
	Fri, 15 Dec 2000 17:42:23 -0500 (EST)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 15 Dec 2000 17:42:23 -0500 (EST)
To: John Baldwin <jhb@FreeBSD.ORG>
Cc: Bernd Walter <ticso@cicely5.cicely.de>, freebsd-alpha@FreeBSD.ORG
Subject: Re: mb and wmb in atomic_
In-Reply-To: <XFMail.001215131925.jhb@FreeBSD.org>
References: <20001215211930.D62048@cicely5.cicely.de>
	<XFMail.001215131925.jhb@FreeBSD.org>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14906.40438.240204.200341@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


John Baldwin writes:
 > 
 > Can the CPU perform out-of-order execution though?  And out-of-order memory
 > accesses as a result?  That is what memory barriers really protect you against.

Yes, EV6 and better perform out of order execution.

Drew


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message