From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail2.shareable.org ([80.68.89.115]) by bombadil.infradead.org with esmtps (Exim 4.68 #1 (Red Hat Linux)) id 1KyKLJ-0001Gh-SF for linux-mtd@lists.infradead.org; Fri, 07 Nov 2008 05:57:14 +0000 Date: Fri, 7 Nov 2008 05:57:08 +0000 From: Jamie Lokier To: Trent Piepho Subject: Re: flash read performance Message-ID: <20081107055708.GG17593@shareable.org> References: <49097176.5010506@thomson.net> <49098716.1010404@thomson.net> <490F096D.5060208@imms.de> <20081104114229.GA1673@shareable.org> <49105CAB.3000706@imms.de> <20081107040200.GB17593@shareable.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: Arnaud Mouiche , Andre Puschman , MTD mailing list List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Trent Piepho wrote: > On Fri, 7 Nov 2008, Jamie Lokier wrote: > > Based on Andre's observation, I will soon try enabling cache for my > > NOR, and see if it makes a difference to cold-cache read performance. > > I don't expect it, but it's worth a try. > > It possible it could help by efficiently doing the reads back-to-back with > no wasted cycles between them. I think it's necessary if you want to > benefit from page mode, but that's something I haven't tried yet. > > > You might also find the write operation to be unreliable, if the > > caching mode is write-back rather than write-through. > > Proper use of "sync" instructions, or whatever the arch uses to insure that > writel() is strictly ordered should fix that. I think that won't work because strongly ordered writes don't translate directly to bus transactions when the region is mapped with ioremap_cached(). The flash wants exact bus transactions. -- Jamie