From: "colin" <colin@realtek.com.tw>
To: <arjanv@redhat.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Re: What File System supports Application XIP
Date: Thu, 9 Sep 2004 17:45:13 +0800 [thread overview]
Message-ID: <00bb01c49651$b7525480$8b1a13ac@realtek.com.tw> (raw)
In-Reply-To: 1094721529.2801.6.camel@laptop.fenrus.com
Hi,
How does ramfs offer application XIP ability?
I mean, when the ramfs image is mounted and the application in it is
executed,
"exec", which is called by sh, should first copy every section of the
application to RAM and then jump to the text section.
How do I avoid the stage copying text section to RAM?
Thanks and regards,
Colin
----- Original Message -----
From: "Arjan van de Ven" <arjanv@redhat.com>
To: "colin" <colin@realtek.com.tw>
Cc: <linux-kernel@vger.kernel.org>
Sent: Thursday, September 09, 2004 5:18 PM
Subject: Re: What File System supports Application XIP
> On Thu, 2004-09-09 at 10:55, colin wrote:
> > Hi there,
> > We are developing embedded Linux system. Performance is our
consideration.
> > We hope some applications can run as fast as possible,
> well ramfs by definition is XIP :)
> but I guess the filesystem comes from flash somewhere at which point
> jffs2 with compression might be a better choice; if you have enough ram
> then the apps run from the pagecache anyway and compression keeps you
> from transfering too much data from the slower flash. It's not XIP but I
> don't think you really want XIP...
next prev parent reply other threads:[~2004-09-09 9:45 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 [this message]
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
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='00bb01c49651$b7525480$8b1a13ac@realtek.com.tw' \
--to=colin@realtek.com.tw \
--cc=arjanv@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.