From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mpls-qmqp-02.inet.qwest.net ([63.231.195.113]) by bombadil.infradead.org with esmtp (Exim 4.68 #1 (Red Hat Linux)) id 1KU4TN-0004v1-1E for linux-mtd@lists.infradead.org; Fri, 15 Aug 2008 18:56:29 +0000 Message-ID: <48A5D154.2000409@boundarydevices.com> Date: Fri, 15 Aug 2008 11:56:20 -0700 From: Troy Kisky MIME-Version: 1.0 To: David Woodhouse Subject: Re: [RESUBMIT] [PATCH] [MTD] NAND nand_ecc.c: rewrite for improved performance References: <1218472202.2977.12.camel@pmac.infradead.org> <1218535872.2977.133.camel@pmac.infradead.org> <48A48330.70105@boundarydevices.com> <1218789997.3184.64.camel@pmac.infradead.org> <1218793271.3184.77.camel@pmac.infradead.org> <1218795140.3184.84.camel@pmac.infradead.org> In-Reply-To: <1218795140.3184.84.camel@pmac.infradead.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Frans Meulenbroeks , linux-mtd@lists.infradead.org List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , David Woodhouse wrote: > On Fri, 2008-08-15 at 12:04 +0200, Frans Meulenbroeks wrote: >> 2008/8/15, David Woodhouse : >>> On Fri, 2008-08-15 at 11:23 +0200, Frans Meulenbroeks wrote: >>> > 2008/8/15, David Woodhouse : >>> >>> No need -- if you've thought about it and believe it should work, that's >>> probably enough. I just saw some 'unsigned long' data types, which are >>> going to have a different size between 32-bit and 64-bit systems, and >>> wondered if that would introduce differences. >> I was unaware of that. For me unsigned long is more or less a synonym >> for 32 bit. Maybe I'm just getting too old :-( >> Anyway, if you have a suggestion for a better type, I'll happily change things. >> Would uint32_t be better? > > If it needs to be 32-bit, then yes -- uint32_t is the correct type to > use. > > If 64-bit is OK, then 'unsigned long' is likely to be more efficient on > some platforms. > You might also test it on a big endian system to be safe. Troy