From: Jesse Barnes <jbarnes@sgi.com>
To: Albert Cahalan <albert@users.sourceforge.net>
Subject: Re: [PATCH] I/O space write barrier
Date: Mon, 4 Oct 2004 19:33:25 -0700
User-Agent: KMail/1.7
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
       benh@kernel.crashing.org
References: <1096922369.2666.177.camel@cube> <200410041420.01266.jbarnes@engr.sgi.com> <1096936344.2674.198.camel@cube>
In-Reply-To: <1096936344.2674.198.camel@cube>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200410041933.25522.jbarnes@sgi.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 954
Lines: 25

On Monday, October 04, 2004 5:32 pm, Albert Cahalan wrote:
> Ideally, it would be eieio, and the eieio in each
> of the IO operations would be removed. Finding and
> fixing all the drivers that break looks impossible
> though; most driver developers will be on x86 boxes.

Well, I won't pretend to understand how the PPC ordering rules work, so I'll 
defer to benh on that one.

> In that case: wmmiob
>
> (or something longer, like mmio_write_fence maybe)
>
> As a name, "wmb" sucks almost as much as "cli" and "sti" do.
> It dates back to the Alpha port, where it's an opcode.

The other option I briefly considered was wwjd(), but I don't think He has an 
official position on posted write ordering.

Jesse
-
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/