public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Phillip Lougher <phillip@lougher.demon.co.uk>,
	Pavel Machek <pavel@ucw.cz>,
	Phillip Lougher <phillip@lougher.org.uk>,
	Al Viro <viro@ftp.linux.org.uk>, Jeff Garzik <jeff@garzik.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [ANN] Squashfs 3.0 released
Date: Wed, 22 Mar 2006 00:24:12 +0100	[thread overview]
Message-ID: <20060321232412.GA9044@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20060321212853.GV6199@schatzie.adilger.int>

On Tue, 21 March 2006 14:28:53 -0700, Andreas Dilger wrote:
> On Mar 21, 2006  20:03 +0000, Phillip Lougher wrote:
> > 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.
> 
> If you want to squeak every last ounce of performance out of the filesystem,
> just have it declare two filesystem types - one for the little-endian, and
> one for the bit endian.  Generate one of them via "sed" from the other, to
> rename the functions, exports, etc, so they don't conflict.  Then, depending
> on the superblock magic it will mount the right filesystem, depending on
> endianness.  Since they are separate filesystems, normally only one module
> or the other need to be loaded at a time, and there is no runtime overhead.

That would be an interesting idea for quite another purpose:
measurement.

So far, there has been a lack of numbers in this thread.  Al mentioned
that conditional branches can be more expensive and I usually trust
his words, but actual cold hard numbers would help more.

> 	"unlisted-recipients: no To-header on input <;, Jeff Garzik" <jeff@garzik.org>,

I fixed this up.  No idea what garbled the header.

Jörn

-- 
My second remark is that our intellectual powers are rather geared to
master static relations and that our powers to visualize processes
evolving in time are relatively poorly developed.
-- Edsger W. Dijkstra

  reply	other threads:[~2006-03-21 23:24 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
2006-03-21 20:33                           ` Al Viro
2006-03-21 21:28                         ` Andreas Dilger
2006-03-21 23:24                           ` Jörn Engel [this message]
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=20060321232412.GA9044@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=jeff@garzik.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --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