All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: arjanv@redhat.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 09:56:33 -0700	[thread overview]
Message-ID: <41408B41.4030306@am.sony.com> (raw)
In-Reply-To: <1094723597.2801.8.camel@laptop.fenrus.com>

Arjan van de Ven wrote:
> On Thu, 2004-09-09 at 11:45, colin wrote:
>> 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?
> 
> this is not how linux works. programs execute directly from the
> pagecache without copy.

Most other filesystems populate the pagecache with I/O, presumably.
In the case of a ramfs, is the page mapped directly from the fs
into the pagecache without a copy?

=============================
Tim Bird
Architecture Group Co-Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
E-mail: tim.bird@am.sony.com
=============================

  reply	other threads:[~2004-09-09 16:59 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 [this message]
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=41408B41.4030306@am.sony.com \
    --to=tim.bird@am.sony.com \
    --cc=arjanv@redhat.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 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.