From: Wolfgang Denk <wd@denx.de>
To: "Rupesh S" <rupeshs@myw.ltindia.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Does ext2 based on MTD acceptable for Embedded Development?
Date: Mon, 30 Aug 2004 10:13:19 +0200 [thread overview]
Message-ID: <20040830081324.EE84DC109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 30 Aug 2004 12:26:11 +0530." <s1331f30.037@EMAIL>
In message <s1331f30.037@EMAIL> you wrote:
>
> >> Is there an advantage to use ext2 instead of cramfs for read only fs?
>
> > Boot time, as you don't need to uncompress the stuff.
>
> Could you pls elaborate the choice of ex2 in the above scenario, instead of romfs. Was it to take advantage of the features that ext2 provides ?
> Romfs should have had a better bootup time than ext2/jffs2/cramfs.
Are you sure of this? Do you have actual benchmark data?
Also, romfs has some restrictions (owner and permission information)
and an inefficient design (pages read from filesystem cannot be
executed directly because of 16 byte file header offset).
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
You see things; and you say ``Why?'' But I dream things that never
were; and I say ``Why not?''
- George Bernard Shaw _Back to Methuselah_ (1921) pt. 1, act 1
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-08-30 8:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 6:56 Does ext2 based on MTD acceptable for Embedded Development? Rupesh S
2004-08-30 8:13 ` Wolfgang Denk [this message]
2004-10-11 6:35 ` RPXlite DW boot time Olympic Games - ext2 Win Out! Sam Song
-- strict thread matches above, loose matches on Subject: below --
2004-08-16 16:21 MPC82xx enet on SCC3 Wolfgang Denk
2004-08-26 10:10 ` Does ext2 based on MTD acceptable for Embedded Development? Song Sam
2004-08-27 7:08 ` Oliver Fuchs
2004-08-27 7:39 ` Wolfgang Denk
2004-08-27 10:05 ` Oliver Fuchs
2004-08-27 14:24 ` Wolfgang Denk
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=20040830081324.EE84DC109F@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rupeshs@myw.ltindia.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).