From: Daniel Marmier <daniel.marmier@lightning.ch>
To: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
Cc: Jeremy Puhlman <jpuhlman@mvista.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Endianness-aware mkcramfs
Date: Wed, 05 Dec 2001 13:23:04 +0100 [thread overview]
Message-ID: <3C0E11A8.A3057B7D@lightning.ch> (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> <3C0D6CB6.7000905@zytor.com> <20011204164941.A29968@one-eyed-alien.net> <20011204170235.M25671@mvista.com> <20011204173819.C29968@one-eyed-alien.net>
Matthew Dharm wrote:
>
> The speed reduction is going to be minimal. Implement it via macros, like
> it's done everywhere else. If the endianness is one way, the macros get
> optimized away. If it's the other way, then they convert into an inlined
> byte swap.
>
> Yes, there can be a small performance hit, but it's absolutely tiny.
>
Approved. Byteswapping some metadata fields has a negligible cost.
I did not post this patch in the hope it would be integrated, but
because Jeremy needed it.
If there is consensus about the "always little-endian cramfs" idea,
let's go for it and please ignore this patch.
Have a nice day,
Daniel Marmier
next prev parent reply other threads:[~2001-12-05 12:23 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
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 [this message]
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=3C0E11A8.A3057B7D@lightning.ch \
--to=daniel.marmier@lightning.ch \
--cc=hpa@zytor.com \
--cc=ingo.oeser@informatik.tu-chemnitz.de \
--cc=jpuhlman@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdharm-kernel@one-eyed-alien.net \
/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