From: Paulo Marques <pmarques@grupopie.com>
To: colin <colin@realtek.com.tw>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What File System supports Application XIP
Date: Thu, 09 Sep 2004 10:19:07 +0100 [thread overview]
Message-ID: <4140200B.9060408@grupopie.com> (raw)
In-Reply-To: <009901c4964a$be2468e0$8b1a13ac@realtek.com.tw>
colin wrote:
>
> Hi there,
> We are developing embedded Linux system. Performance is our consideration.
> We hope some applications can run as fast as possible,
> and are think if they can be put in a filesystem image, which resides in
> RAM, and run in XIP (eXecute In Place) manners.
> I know that Cramfs has supported Application XIP. Is there any other FS that
> also supports it? Ramdisk? Ramfs? Romfs?
Obvisously cramfs can not support XIP, because the "in-place" image
is compressed (unless you have a processor that can execute compressed
code :)
AFAIK only tmpfs supports XIP because it works on a higher level
without using block devices underneath. Ramdisks are simply RAM
block devices that behave like any other block device.
You can have a compressed image in flash (for instance), decompress
everything into a tmpfs and execute from there.
I'm not sure, however, that this will be such a performance gain.
If you use cramfs (for instance) then the kernel will uncompress
and run only the pages that are needed, and they will be cached in
page cache so that they will be available again when needed. This
way you only waste the RAM you actually need, and can still drop
old pages if the application needs more RAM.
Just my two cents,
--
Paulo Marques - www.grupopie.com
To err is human, but to really foul things up requires a computer.
Farmers' Almanac, 1978
next prev parent reply other threads:[~2004-09-09 9:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 8:55 What File System supports Application XIP colin
2004-09-09 9:18 ` Arjan van de Ven
2004-09-09 9:45 ` colin
2004-09-09 9:53 ` Arjan van de Ven
2004-09-09 16:56 ` Tim Bird
2004-09-09 17:17 ` Arjan van de Ven
2004-09-09 17:38 ` Robert Love
2004-09-10 2:12 ` colin
2004-09-10 2:15 ` Robert Love
2004-09-09 9:19 ` Paulo Marques [this message]
2004-09-09 9:42 ` David Woodhouse
2004-09-09 16:35 ` Tim Bird
2004-09-11 0:06 ` Todd Poynor
2004-09-09 9:58 ` ¡@[*©U§£¶l¥ó*] " colin
2004-09-09 10:43 ` Arnd Bergmann
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=4140200B.9060408@grupopie.com \
--to=pmarques@grupopie.com \
--cc=colin@realtek.com.tw \
--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