To: Jes Sorensen <jes@sgi.com>
Cc: "Bryan O'Sullivan" <bos@pathscale.com>, Andrew Morton <akpm@osdl.org>,
       Andi Kleen <ak@suse.de>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Define wc_wmb, a write barrier for PCI write combining
References: <1140841250.2587.33.camel@localhost.localdomain>
	<yq08xrvhkee.fsf@jaguar.mkp.net>
	<1141149475.24103.18.camel@camp4.serpentine.com>
	<44057B46.1010403@sgi.com>
From: Roland Dreier <rdreier@cisco.com>
Date: Wed, 01 Mar 2006 09:04:29 -0800
In-Reply-To: <44057B46.1010403@sgi.com> (Jes Sorensen's message of "Wed, 01 Mar 2006 11:45:26 +0100")
Message-ID: <adawtfeyu3m.fsf@cisco.com>
User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.18 (linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 742
Lines: 16

    Jes> Anyway, based on Jesse and Jeremy's comments, then maybe the
    Jes> semantics here are different. However I do think the name
    Jes> wc_wmb() isn't quite defining it. If it's only to be used on
    Jes> mmio space, something like mmio_wc_wmb() would probably be
    Jes> more descriptive.

I don't see any restriction to MMIO space -- it would be a strange
thing to do, but conceivable one might want to order writes that are
made to ordinary RAM via a write-combining mapping.

 - R.
-
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/