From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [ANN] Squashfs 3.0 released Date: Sun, 19 Mar 2006 16:32:50 +0000 Message-ID: <20060319163249.GA3856@ucw.cz> References: <20060317104023.GA28927@wohnheim.fh-wedel.de> <20060317124310.GB28927@wohnheim.fh-wedel.de> <441ADD28.3090303@garzik.org> <0E3DADA8-1A1C-47C5-A3CF-F6A85FF5AFB8@lougher.org.uk> <441AF118.7000902@garzik.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Phillip Lougher , =?iso-8859-1?Q?J=F6rn?= Engel , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Return-path: Received: from gprs189-60.eurotel.cz ([160.218.189.60]:6415 "EHLO spitz.ucw.cz") by vger.kernel.org with ESMTP id S1751751AbWCUPNL (ORCPT ); Tue, 21 Mar 2006 10:13:11 -0500 To: Jeff Garzik Content-Disposition: inline In-Reply-To: <441AF118.7000902@garzik.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Fri 17-03-06 12:25:44, Jeff Garzik wrote: > Phillip Lougher wrote: > >On 17 Mar 2006, at 16:00, Jeff Garzik wrote: > >>J=F6rn Engel wrote: > >>>>>The one still painfully missing is a > >>>>>fixed-endianness disk format. >=20 > >>Fixed endian isn't necessarily a requirement. =20 > >>Detectable endian is. As long as (a) the filesystem=20 > >>mkfs notes the endian-ness and (b) the kernel=20 > >>filesystem code properly handles both types of endian,=20 > >>life is fine. > >> > >That's what is currently done. There are two filesystem=20 > >formats, big endian (donated by Squashfs magic of=20 > >'sqsh') and little endian (denoted by Squashfs magic of=20 > >'hsqs'). The kernel code detects the filesystem=20 > >endianness and swaps if necessary. >=20 > Well, then, I don't see a need to change anything. As I=20 > said, [consistent and] detectable endian is the real=20 > requirement. For SquashFS's users, I would think they=20 > would prefer the current situation (selectable endian) to=20 > fixed endian, because many SquashFS users need to squeeze=20 > every ounce of performance out of severely=20 > resource-constrained devices. >=20 > I have two routers, ADM5120-based Edimax and LinkSys=20 > WRT54G v5, both of which have a mere 2MB of flash, and=20 > both use SquashFS to maximize that space. And both are=20 > el cheapo, slow embedded processors that run far slower=20 > than 300Mhz. I look askance at anyone who wants to make=20 > an arbitrary filesystem design decision imposing tons of=20 > bytesex upon these lowly devices. gzip is already pretty expensive, I'd say. Is not byteswap lost in noise? --=20 Thanks, Sharp! - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html