Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 13 Jan 2003 16:59:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 13 Jan 2003 16:59:10 -0500 Received: from AMarseille-201-1-3-195.abo.wanadoo.fr ([193.253.250.195]:44144 "EHLO zion.wanadoo.fr") by vger.kernel.org with ESMTP id ; Mon, 13 Jan 2003 16:59:03 -0500 Subject: Re: Linux 2.4.21-pre3-ac4 From: Benjamin Herrenschmidt To: root@chaos.analogic.com Cc: Jeff Garzik , Ross Biro , Alan Cox , Alan Cox , Linux Kernel Mailing List In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1042495640.587.30.camel@zion.wanadoo.fr> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 13 Jan 2003 23:07:20 +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2003-01-13 at 22:40, Richard B. Johnson wrote: > There is a well-defined procedure for this. Any "read" anywhere > in the PCI address space, will force all posted writes to complete. > However, the "read" will not be the data one would obtain after > the write completes. Just to avoid confusion, the above is obviously wrong, the read will indeed force pending store queues to complete _in order_, the read will reach the device after the stores are complete and you'll read the value you would get after the write normally. At least on PCI ;) Ben. - 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/