Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932671AbWBYEoV (ORCPT ); Fri, 24 Feb 2006 23:44:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932672AbWBYEoV (ORCPT ); Fri, 24 Feb 2006 23:44:21 -0500 Received: from cantor2.suse.de ([195.135.220.15]:51128 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S932671AbWBYEoV (ORCPT ); Fri, 24 Feb 2006 23:44:21 -0500 From: Andi Kleen To: "Bryan O'Sullivan" Subject: Re: [PATCH] Define wc_wmb, a write barrier for PCI write combining Date: Sat, 25 Feb 2006 05:43:21 +0100 User-Agent: KMail/1.9.1 Cc: Andrew Morton , linux-kernel References: <1140841250.2587.33.camel@localhost.localdomain> In-Reply-To: <1140841250.2587.33.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200602250543.22421.ak@suse.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 792 Lines: 24 On Saturday 25 February 2006 05:20, Bryan O'Sullivan wrote: > On some platforms, a regular wmb() is not sufficient to guarantee that > PCI writes have been flushed to the bus if write combining is in effect. On what platforms? > It does so by way of a new header file, . This header > can be a site for oft-replicated code from , but isn't > just yet. linux/system.h looks unnatural to me. > We also define a version of wc_wmb() with the required semantics > on x86_64. Leaving i386 out in the cold? -Andi - 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/