linux-mips
[Top] [All Lists]

Re: Please pull drivers/scsi/dec_esp.c from Linus' git

To: "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: Please pull drivers/scsi/dec_esp.c from Linus' git
From: Jes Sorensen <jes@sgi.com>
Date: Fri, 17 Feb 2006 13:35:12 +0100
Cc: Ralf Baechle <ralf@linux-mips.org>, Martin Michlmayr <tbm@cyrius.com>, linux-mips@linux-mips.org
In-reply-to: <Pine.LNX.4.64N.0602171039320.7169@blysk.ds.pg.gda.pl>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20060213225331.GA5315@deprecation.cyrius.com> <20060215150839.GA27719@linux-mips.org> <Pine.LNX.4.64N.0602161016260.7169@blysk.ds.pg.gda.pl> <20060216145931.GA1633@linux-mips.org> <Pine.LNX.4.64N.0602161504230.7169@blysk.ds.pg.gda.pl> <yq0pslmxsb7.fsf@jaguar.mkp.net> <Pine.LNX.4.64N.0602171039320.7169@blysk.ds.pg.gda.pl>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla Thunderbird 1.0.7 (X11/20051013)
Maciej W. Rozycki wrote:
On Fri, 17 Feb 2006, Jes Sorensen wrote:


Just make mmiowb() strong enough on those platforms. There's really no
reason to introduce yet another variation at this point.


It's just horribly slow and an overkill if it's only ordering of consecutive writes rather than ordering of a read after a write that has to be guaranteed. But perhaps we could keep abusing wmb() for the former...

Depends on where it's happening. If it's the CPU doing it before it hits
the bus then wmb() would probably be ok.

Jes

<Prev in Thread] Current Thread [Next in Thread>