Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161309AbWASKDN (ORCPT ); Thu, 19 Jan 2006 05:03:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161311AbWASKDN (ORCPT ); Thu, 19 Jan 2006 05:03:13 -0500 Received: from vanessarodrigues.com ([192.139.46.150]:13231 "EHLO jaguar.mkp.net") by vger.kernel.org with ESMTP id S1161309AbWASKDM (ORCPT ); Thu, 19 Jan 2006 05:03:12 -0500 To: Andi Kleen Cc: discuss@x86-64.org, "Bryan O'Sullivan" , linux-kernel@vger.kernel.org Subject: Re: [discuss] Re: Why is wmb() a no-op on x86_64? References: <1137601417.4757.38.camel@serpentine.pathscale.com> <1137603169.4757.50.camel@serpentine.pathscale.com> <200601181831.01688.ak@suse.de> From: Jes Sorensen Date: 19 Jan 2006 05:03:11 -0500 In-Reply-To: <200601181831.01688.ak@suse.de> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 577 Lines: 13 >>>>> "Andi" == Andi Kleen writes: Andi> On Wednesday 18 January 2006 18:06, Jes Sorensen wrote: >> A job for mmiowb() perhaps? Andi> No, normal IO mappings are also not write combining on x86, so Andi> it's not needed there. True, just seemed nasty to have yet another special purpose wmb() variation. Cheers, Jes - 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/