From: Pavel Machek <pavel@suse.cz>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: Phillip Lougher <phillip@lougher.org.uk>,
Al Viro <viro@ftp.linux.org.uk>,
"unlisted-recipients: no To-header on input <;,
Jeff Garzik" <jeff@garzik.org>,
J?rn Engel <joern@wohnheim.fh-wedel.de>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [ANN] Squashfs 3.0 released
Date: Tue, 21 Mar 2006 21:15:41 +0100 [thread overview]
Message-ID: <20060321201541.GF3929@elf.ucw.cz> (raw)
In-Reply-To: <44205C1A.4040408@lougher.demon.co.uk>
Hi!
> >Can you try to benchmark it? I believe it is going to be lost in
> >noise, slow cpus or not.
>
> Good idea, I'll try to benchmark it (on a slow CPU if I can find one :-)
> ). It will probably make no difference.
>
> I don't want the lack of a fixed endianness on disk to become a problem.
> I personally don't think the use of, or lack of a fixed endianness to
> be that important, but I'd prefer not to change the current situation
> and adopt a fixed format. I use big endian systems almost exclusively,
> and I don't like the way fixed formats always tend to be little-endian.
Fix it to big-endian, then. Network protocols are big-endian, anyway,
and PCs tend to be so fast that byteswap will be lost in cache misses,
anyway.
[Funny, it looks like all the big-endian machines are slow :-)))]
Pavel
--
Picture of sleeping (Linux) penguin wanted...
next prev parent reply other threads:[~2006-03-21 20:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 0:45 [ANN] Squashfs 3.0 released Phillip Lougher
[not found] ` <20060317010529.GB30801@schatzie.adilger.int>
2006-03-17 1:30 ` Phillip Lougher
2006-03-17 1:51 ` Samuel Masham
2006-03-17 10:40 ` Jörn Engel
2006-03-17 11:16 ` Phillip Lougher
2006-03-17 12:43 ` Jörn Engel
2006-03-17 16:00 ` Jeff Garzik
2006-03-17 17:04 ` Phillip Lougher
2006-03-17 17:25 ` Jeff Garzik
2006-03-17 20:39 ` Willy Tarreau
2006-03-19 1:38 ` Phillip Lougher
2006-03-21 15:33 ` Francesco Biscani
2006-03-19 1:42 ` Phillip Lougher
2006-03-19 16:32 ` Pavel Machek
2006-03-21 16:01 ` Phillip Lougher
[not found] ` <20060321161452.GG27946@ftp.linux.org.uk>
2006-03-21 19:08 ` Phillip Lougher
2006-03-21 19:11 ` Pavel Machek
2006-03-21 20:03 ` Phillip Lougher
2006-03-21 20:07 ` Al Viro
2006-03-21 22:01 ` Jan Engelhardt
2006-03-21 22:11 ` Jeff Garzik
2006-03-21 22:59 ` Al Viro
2006-03-21 20:15 ` Pavel Machek [this message]
2006-03-21 20:33 ` Al Viro
2006-03-21 21:28 ` Andreas Dilger
2006-03-21 23:24 ` Jörn Engel
2006-03-17 21:32 ` Jan Engelhardt
2006-03-17 15:54 ` Xavier Bestel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060321201541.GF3929@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=jeff@garzik.org \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip@lougher.demon.co.uk \
--cc=phillip@lougher.org.uk \
--cc=viro@ftp.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox