Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751638AbWCHRyg (ORCPT ); Wed, 8 Mar 2006 12:54:36 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751792AbWCHRyg (ORCPT ); Wed, 8 Mar 2006 12:54:36 -0500 Received: from [81.2.110.250] ([81.2.110.250]:20969 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S1751638AbWCHRyg (ORCPT ); Wed, 8 Mar 2006 12:54:36 -0500 Subject: Re: [PATCH] Document Linux's memory barriers From: Alan Cox To: Christoph Lameter Cc: David Howells , linux-kernel@vger.kernel.org In-Reply-To: References: <31492.1141753245@warthog.cambridge.redhat.com> <10414.1141839308@warthog.cambridge.redhat.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Wed, 08 Mar 2006 17:59:43 +0000 Message-Id: <1141840783.7605.54.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 453 Lines: 11 > i386 does not fully implement things like write barriers since they have > an implicit ordering of stores. Except when they don't (PPro errata cases, and the explicit support for this in the IDT Winchip) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/