public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "colin" <colin@realtek.com.tw>
To: "Robert Love" <rml@ximian.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re:  Re: What File System supports Application XIP
Date: Fri, 10 Sep 2004 10:12:14 +0800	[thread overview]
Message-ID: <011001c496db$99dc6aa0$8b1a13ac@realtek.com.tw> (raw)
In-Reply-To: 1094751525.6833.61.camel@betsy.boston.ximian.com

Hi Robert,
Sorry. I donot quite understand. My English is poor... :-(
Do you mean there wonot be another duplicated text section in RAM when
application in Ramfs is executed?

Regards,
Colin


----- Original Message ----- 
From: "Robert Love" <rml@ximian.com>
To: "Tim Bird" <tim.bird@am.sony.com>
Cc: <arjanv@redhat.com>; "colin" <colin@realtek.com.tw>;
<linux-kernel@vger.kernel.org>
Sent: Friday, September 10, 2004 1:38 AM
Subject:  [*垃圾郵件*] Re: What File System supports Application XIP


> On Thu, 2004-09-09 at 09:56 -0700, Tim Bird wrote:
>
> > 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?
>
> ramfs _is_ pagecache.
>
> it is cool like that.
>
> Robert Love
>
>
>



  reply	other threads:[~2004-09-10  2:15 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 [this message]
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='011001c496db$99dc6aa0$8b1a13ac@realtek.com.tw' \
    --to=colin@realtek.com.tw \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@ximian.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