mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Paulo Marques <pmarques@grupopie.com>
Cc: colin <colin@realtek.com.tw>, linux-kernel@vger.kernel.org
Subject: Re: What File System supports Application XIP
Date: Thu, 09 Sep 2004 10:42:57 +0100	[thread overview]
Message-ID: <1094722976.4083.1550.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <4140200B.9060408@grupopie.com>

On Thu, 2004-09-09 at 10:19 +0100, Paulo Marques wrote:
> 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 :)

Actually there are hacks floating around which do let you use XIP with
cramfs -- obviously you have to dispense with compression for the files
you want to access that way.

You won't gain at runtime by using XIP though. Your code and data will
end up in RAM _whatever_ file system you use, and you'll be running from
page cache.

You may get a _slightly_ faster startup time after reboot if you use XIP
from flash, because it doesn't have to be loaded into RAM first. But
that comes at the cost of making it all a low slower during normal
operation -- it's a lot slower to fetch icache lines from flash than it
is from RAM.

Arjan's right -- you almost certainly don't really want XIP. 

-- 
dwmw2


  reply	other threads:[~2004-09-09  9:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-09  8:55 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
2004-09-09  9:42   ` David Woodhouse [this message]
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=1094722976.4083.1550.camel@hades.cambridge.redhat.com \
    --to=dwmw2@infradead.org \
    --cc=colin@realtek.com.tw \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmarques@grupopie.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

all inboxes | Powered by JetHome®