From: Ryan Mallon <ryan@bluewatersys.com>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Embedded <linux-embedded@vger.kernel.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Tim Bird <tim.bird@am.sony.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 08/16 v2] pramfs: headers
Date: Thu, 11 Nov 2010 08:09:01 +1300 [thread overview]
Message-ID: <4CDAEDCD.5050603@bluewatersys.com> (raw)
In-Reply-To: <AANLkTik+Vx8W1qXEZ=AqedRSj_D4-k70Xa4h-bnW2MRH@mail.gmail.com>
On 11/10/2010 09:15 PM, Marco Stornelli wrote:
> 2010/11/9 Geert Uytterhoeven <geert@linux-m68k.org>:
>> On Tue, Nov 9, 2010 at 21:35, Ryan Mallon <ryan@bluewatersys.com> wrote:
>>> You can still do all of those things without having a fixed endianess.
>>> You just have to have one extra step of telling the external tools what
>>> the endianess is. IMHO, it is better to have the overhead of the endian
>>> conversion in the tools since it is less costly there than an the
>>> embedded system.
>>>
>>> I'm just trying to understand why the fixed endianess rule cannot be
>>> bent for such a specialised filesystem.
>>
>> When it was decided that filesystems should be fixed-endian and support for
>> big-endian ext2 was dropped, the overhead of doing the fixed conversions was
>> deetermined negligible due to compiler optimization.
>> That was ages ago, and current embedded systems run circles around the
>> machines of those days.
>>
>> Note that this is about metadata only. Actual file contents are always just
>> byte streams.
>>
>
> I can add that the penalties in this case are negligible due to the
> compensation of the very fast access of the media. In addition, from
> performance point of view I'm pretty happy (you can see the some
> benchmark on the project web site).
Thanks for the explanation guys.
~Ryan
--
Bluewater Systems Ltd - ARM Technology Solution Centre
Ryan Mallon 5 Amuri Park, 404 Barbadoes St
ryan@bluewatersys.com PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com New Zealand
Phone: +64 3 3779127 Freecall: Australia 1800 148 751
Fax: +64 3 3779135 USA 1800 261 2934
prev parent reply other threads:[~2010-11-10 19:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 8:58 [PATCH 08/16 v2] pramfs: headers Marco Stornelli
2010-11-07 20:09 ` Ryan Mallon
2010-11-08 7:49 ` Marco Stornelli
2010-11-08 19:50 ` Ryan Mallon
2010-11-09 8:19 ` Marco Stornelli
2010-11-09 20:35 ` Ryan Mallon
2010-11-09 20:56 ` Geert Uytterhoeven
2010-11-10 8:15 ` Marco Stornelli
2010-11-10 19:09 ` Ryan Mallon [this message]
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=4CDAEDCD.5050603@bluewatersys.com \
--to=ryan@bluewatersys.com \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=tim.bird@am.sony.com \
/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;
as well as URLs for NNTP newsgroup(s).