[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100512230841.GA10090@n2100.arm.linux.org.uk>
Date: Thu, 13 May 2010 00:08:41 +0100
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc: Jamie Lokier <jamie@...reable.org>,
Saeed Bishara <saeed@...vell.com>,
Nicolas Pitre <nico@...vell.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"James E.J. Bottomley" <jejb@...isc-linux.org>,
FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
"Shilimkar, Santosh" <santosh.shilimkar@...com>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: Rampant ext3/4 corruption on 2.6.34-rc7 with VIVT ARM (Marvell
88f5182)
On Thu, May 13, 2010 at 08:47:11AM +1000, Benjamin Herrenschmidt wrote:
> Now, in the case at hand, which is my ARM based NAS, I believe this
> is non cache-coherent and thus uses cache flush ops. I don't know ARM
> well enough but I would expect these to be implicit barriers. Russell ?
> Nico ?
ARMv5 doesn't have a weak memory ordering model, and doesn't have any
memory barrier instructions.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists