From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Endianness-aware mkcramfs
Date: Tue, 04 Dec 2001 16:39:18 -0800 [thread overview]
Message-ID: <3C0D6CB6.7000905@zytor.com> (raw)
In-Reply-To: <3C0BD8FD.F9F94BE0@mvista.com> <3C0CB59B.EEA251AB@lightning.ch> <9uj5fb$1fm$1@cesium.transmeta.com> <20011205013630.C717@nightmaster.csn.tu-chemnitz.de>
Ingo Oeser wrote:
>
> Yes, from a CS point of view.
>
> But practically cramfs is created once to contain some kind of
> ROM for embedded devices. So if we never modify these data again,
> why not creating it in the required byte order?
>
> Why wasting kernel cycles for le<->be conversion? Just because
> it's more general? For writable general purpose file systems it
> makes sense, but to none of romfs, cramfs etc.
>
Because otherwise you far too easily end up in a situation where every
system suddenly need to be able to support *BOTH* endianisms, at which
point you're really screwed; supporting dual endianism is significantly
more expensive than supporting the "wrong" endianism, and it affects all
systems.
Nip this one in the bud.
-hpa
next prev parent reply other threads:[~2001-12-05 0:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C0BD8FD.F9F94BE0@mvista.com>
2001-12-04 11:38 ` [PATCH] Endianness-aware mkcramfs Daniel Marmier
2001-12-04 18:42 ` H. Peter Anvin
2001-12-05 0:36 ` Ingo Oeser
2001-12-05 0:39 ` H. Peter Anvin [this message]
2001-12-05 0:49 ` Matthew Dharm
2001-12-05 1:02 ` Jeremy Puhlman
2001-12-05 1:12 ` H. Peter Anvin
2001-12-05 1:38 ` Matthew Dharm
2001-12-05 12:23 ` Daniel Marmier
2001-12-06 6:04 ` H. Peter Anvin
2001-12-06 14:12 ` Pavel Machek
2001-12-18 2:52 ` Daniel Quinlan
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=3C0D6CB6.7000905@zytor.com \
--to=hpa@zytor.com \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=linux-kernel@vger.kernel.org \
/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