From: Christoph Hellwig <hch@infradead.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Andi Drebes <lists-receive@programmierforen.de>,
Tomas M <tomas@slax.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: cramfs in big endian
Date: Sat, 10 Nov 2007 15:13:22 +0000 [thread overview]
Message-ID: <20071110151322.GA21768@infradead.org> (raw)
In-Reply-To: <47350345.4010108@zytor.com>
On Fri, Nov 09, 2007 at 05:03:01PM -0800, H. Peter Anvin wrote:
> Endian-independent code is slower than wrong-endian code, because of the
> necessary conditionals. Thus, you DO NOT WANT this(*).
I'd prefer not to have it either. But a someone (pinhead) was smart
enough not to define an endianess for cramfs from the beginning we're
stuck with it.
next prev parent reply other threads:[~2007-11-10 15:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 21:16 cramfs in big endian Andi Drebes
2007-11-07 13:52 ` Tomas M
2007-11-07 20:51 ` Andi Drebes
2007-11-07 22:49 ` Christoph Hellwig
2007-11-08 18:10 ` Andi Drebes
2007-11-10 1:03 ` H. Peter Anvin
2007-11-10 15:13 ` Christoph Hellwig [this message]
2007-11-10 20:19 ` H. Peter Anvin
2007-11-10 20:26 ` Andi Drebes
2007-11-10 20:30 ` H. Peter Anvin
2007-11-11 10:20 ` Andi Drebes
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=20071110151322.GA21768@infradead.org \
--to=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lists-receive@programmierforen.de \
--cc=tomas@slax.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.